The Following User Says Thank You to whinnycius For This Useful Post: | ||
|
2017-12-24
, 09:17
|
|
Posts: 4,118 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#2
|
The Following User Says Thank You to peterleinchen For This Useful Post: | ||
|
2017-12-24
, 09:36
|
Posts: 1,293 |
Thanked: 4,319 times |
Joined on Oct 2014
|
#3
|
The Following 3 Users Say Thank You to nieldk For This Useful Post: | ||
|
2017-12-24
, 20:14
|
Posts: 4 |
Thanked: 12 times |
Joined on Dec 2017
|
#4
|
Strange pic! Never seen before!
What does flasher state in case of eMMC interrupt?
Something like RAW transfer? I had this years ago and that device worked perfectly until the "all telephony disabled" thing.
Normally I would expect the missing image in case of rootfs first and then eMMC...
Just a thought
Did you check MD5 of the downloaded images ?
Could be a bad image
The Following 2 Users Say Thank You to whinnycius For This Useful Post: | ||
|
2017-12-25
, 00:32
|
Posts: 4 |
Thanked: 10 times |
Joined on Dec 2017
|
#5
|
The Following 3 Users Say Thank You to CarlessDriver For This Useful Post: | ||
Tags |
flasher, nokia n900 |
|
Today I tried to reflash the internal memory of my (third) N900, using Flasher in Windows XP and the most current RootFS / eMMC file. RootFS flashed without problems, but the eMMC flash process does not exceed 20%.
It was curious to note that when I did the process indicated in the tutorial (eMMC first, then RootFS after), the device starts in a strange way, according to the photos attached here: https://imgur.com/a/NCRJC
Doing the reverse process (RoorFS first, then eMMC), despite the error when flashing eMMC, the device starts without problems.
can anybody help me? I know it's not strictly necessary to flash the eMMC after the process, but I'm afraid the memory might corrupt later, just like another N900 I had.
Thank you all, a merry christmas and a prosperous new year!