Related
Hi,
I spent 6-7 hours of reading all kind of suggestions and etc, how to bring a brick to life. the only closest to my situation is http://forum.xda-developers.com/showthread.php?t=295623
I flashed my phone several times and i hadnt much of problems until i tried to put wm6 update.
The last time I tried to downgrade to CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE and the phone freezed to the start screen (that picture with the beer). I restarted it several times but it never went beyond it.
Then I tried to put the previous ROM that worked. I entered bootload mode and started the upgrade wizard. I waited it to finish, but it didnt! When it reached 98% it suddenly got back to 95%(!?) and after few seconds a message for connecition interupted appeared on the computer. The phone stayed on 95% for some time more and nothing happened. Then i clicked on the "how to restore" button of the upgrade wizard. I followed the instructions which stated on step 3 "remove the battery of the phone".
After I did that, my phone died and since then i cant do anything with it. The screen is all black. Of course I tried hard reset, bootloader mode and etc - all failed. It doesnt go into bootloader mode or do hard reset. The computer does not detect any USB connections. The charger doesnt appear to be detected by the phone (LED doesnt light up). There should be 50-60% battery power left. It was working perfectly before flashing.
I think the main problem now is how to enter the Bootloader.
Im not quite familiar with SD flashing, but i think i have the necessary hardware, just please advise is it possible and how I can do it.
Edit: Now I found that my SD card is unreadable too
Please help
Sorry
Greetings,
Sorry for your situation, but do you have G4 or G3 wizard.
If G4 was it CID locked or unlocked.
samy.3660 said:
Greetings,
Sorry for your situation, but do you have G4 or G3 wizard.
If G4 was it CID locked or unlocked.
Click to expand...
Click to collapse
it is g4 cid locked
edit: i now remember that IPL & SPL had different versions like 1.x & 2.x after downgrading. I didnt know that I have to reflash in that case i found it in the forum too late
You should have read more before trying to flash your phone...
That downgrade that you made bricked your phone. That ROM was intended for G3 ONLY. If you have a G4 you should flash only G4-ROMS (or read how to extract ipl & spl from a G3 ROM) ... I am afraid there are no known solutions, because IPL and SPL on a G4 can`t be succesfully upgraded/reflashed (the hardware doesn`t allow that)
(the hardware doesn`t allow that)
Click to expand...
Click to collapse
so how i did broke them in the first place?
anyway i'm trying to cook a SD card image, but the typhoon 5 tool doesnt convert the files to sd image format
Code:
C:\work>typho5.exe -r ipl=nk.nbf -d az.img
read 04741800 for ipl from nk.nbf
no IPL at 4 in IPL image
my idea is to either get a packeded file with all the modules or put them to the SD card one by one at the appropriate offset as it is described in the Wiki (using the winhex disk editor). Is the *.nb format the same as the modules in the SD card image? I mean can i directly paste the contents of the .nb files into the apropriate offset to the empty SD card?
Your only solutions are to get a new board or to get a JTAG device and discover the JTAG pins on the board since it's the only way you can access the flash chip without a bootloader. Problem is until now no one has managed to find the JTAG pins (or bothered).
What you have done was flashing an IPL (Initial Program Loader) that is for G3 DOC chips only (with a 130 nm manufacturing process) ; and since you have a G4 DOC chip (90 nm manufacturing process) the process fails.
This is the IPL:
A small XIP memory (ROM, NOR flash or DiskOnChip boot block) that contains code to
perform minimal system initialization: It must at least initialize the chip-select unit so that
the ROM (if any), RAM, and DiskOnChip can be accessed.
Click to expand...
Click to collapse
3.2. The Boot Process
• Power up and initialization: After system power up, the IPL code that resides on the XIP
block of the DiskOnChip is executed. The IPL code initializes the DiskOnChip controller
and the RAM.
• Copying the SPL code from DiskOnChip to RAM: After initialization, the IPL reads and
loads the SPL code from the DiskOnChip binary partition to RAM. It then jumps to the SPL
start address in RAM and executes the SPL.
Notes: 1. In general, the IPL is limited in size to several KB (the size limitation varies,
depending on the device type), so it is not possible to include both the system
initialization code and the error correction code. The absence of the error correction
code in the IPL is the reason why the boot process is divided into the IPL stage and
SPL stage. The actual loading of the OS image to RAM is done by the SPL code.
Since the SPL runs in the system RAM, there is no limit on code size and it can
include the error correction code.
Click to expand...
Click to collapse
As you can see on step 2 the IPL can't load SPL since they are for different chip versions.
cheers
mestrini said:
Your only solutions are to get a new board or to get a JTAG device and discover the JTAG pins on the board since it's the only way you can access the flash chip without a bootloader. Problem is until now no one has managed to find the JTAG pins (or bothered).
What you have done was flashing an IPL (Initial Program Loader) that is for G3 DOC chips only (with a 130 nm manufacturing process) ; and since you have a G4 DOC chip (90 nm manufacturing process) the process fails.
This is the IPL:
As you can see on step 2 the IPL can't load SPL since they are for different chip versions.
cheers
Click to expand...
Click to collapse
yes, it seems that happened, but after flashing the g3 version, the phone still enters the bootloader. It died completely AFTER i tried to return the g4 version, and may be all happened because it didnt finish the instalation (which interupted for no reason) and stayed with messed up versions.
Anyway seems I need a new mobo, but i'm not sure i could find it here (i'm from Bulgaria) the closest vodafone store is in Romania. The phone is from Germany, a friend of mine bought it there.
Guys, I'm frustrated now. I've refreshed the ROM of my G4 version of Dopod 818pro (2.15.0001 or something I just can't remember). Unfortunately it fails and I cannot even turn the power on. My WinCE colleague told me that the Boot Loader was damaged. I am now seeking for some place to re-program the chip and hope if someone can provide me boot loader program. I really appreciate your guys help!!!
Are your Bootloader Realy damage? You mean you cant enter it? Or you havent Power to start your Device?
SD Flashing doesnt work without Bootloader!!
JTAG Flashing (hardware nearest Flashing!!) isnt developed for G4 Plattform. (i think so ... look in the Wizard board ... they talk about JTAG flashing and Wizard G4 must simulare like Prophet G4!!)
the bootloader really damaged, I cannot enter the three stripe screen by holding CAM, PWR button and hit reset hole. Do you mean that I even cannot use JTag to burn the chip???
I do have two fully charged batteries. But it should not be a problem of battery, I tried to connect it to charger but it gives no response, no LED
Using JTAG to revive a wizard is either a myth, or an undiscovered secret. If you cant get into bootloader, your chances of reviving your device are slim.
JTAG isnt a secret ... its more like ... hardware knowlage. If you know what IC is your ROM. You can found over the IC Spec the right Pins for JTAG Programming. If i can get a G4 S200, i can try my best.
yes, I know that using Jtag to rewrite boot loader is complex, but it seems like it's my last chance. NetrunnerAT I really appreciate your help but I'm in Shanghai, China so I have to find someone locally who can help me with that. Wish me good luck and I'll keep you guys updated about the result
If I can find someone who can help Jtag my phone, where can I find the correct bootloader program for my cell? is it downloadable?
guys, I finally found a place to revive my prophet. However, they don't know how to jtag it either, neither do they have a programer to rewrite the chip because they say the programer is very very very expensive. They just changed the old chip with one which has correct ROM and now my G4 Prophet turns to a G3 one...anyway, I can use it now.
Thx!
You have change your rom and it is now G3!!
Can you say me what IC they have exchange! If i know it ... and get a damage device, its possible to found a solution for all Prophet users!
No problem, I kept the damaged IC at home, I'll check the model No. and will let you know
er... One more question, I want to dump the current ROM to my SD card, however the wiki doc says it needs to unlock G3 first. But another doc also says unlocking G3 will downgrade my OS to 1.0.13.21. It's like a kind of deadlock, can I just unlock G3 without changing OS?
uhm ... i think you must downgrade your OS first to CID unlock ... after that you can upgrade to your rom and make SD-Dump!
ok, then that is to say i'll never be able to get a backup of the ROM I currently have.
I'll wait for some weeks and will try to "torture" my prophet again. It was just fixed and I'm supposed to "rest" it for some days, but sooner or later it'll be unlocked, hey heyhey....
Hi, I'm back, the chip is a "M-System MD8832-d16-v3-xp" with a clearly name "Disk On Chip" on it, hope this can help you locate the chip
http://www.m-systems.com/NR/rdonlyr.../0/EOL_DOC_G3_P3.pdf|EOL_DiskOnChip_G3_P3.pdf
Cool ... i read some PDFs ... this is are very nice entry in the PDF!
Compatibility Issues
The recommended replacement, DiskOnChip G4 1Gb/2Gb 9x12mm FBGA, and H1 2Gb
12x18mm FBGA are ball to ball compatible with DiskOnChip G3/P3 7x10mm, 9x10mm FBGA
products that are being discontinued. It is necessary to upgrade software based on TrueFFS 6.2.x
to TrueFFS 6.3.2 and above when upgrading to DiskOnChip G4.
If the different betwen G3 and G4 is the TrueFFS Driver and the G4/H1 is Pin Conpatibel ... possible if i get a half damage device i try to solder a H1 DOC on the PBC and reformat it.
[edit]Holly ****! THX i have found the Migration Document with JTAG Pins!!!
http://www.m-systems.com/NR/rdonlyr...MigrationGuideDOC_G4_1Gb_to_H3_1Gb_Rev0.2.pdf
how are you going to access the pins on a FBGA?
yanuk said:
how are you going to access the pins on a FBGA?
Click to expand...
Click to collapse
you dont. you take a bricked one, de-solder it, and manually trace them to somewhere on the motherboard using a multimeter.
can any body help me with a jtag points for a g4 wizard doomed with a incorrect ipl
Give me a damage Wizard board and i say the JTAG Pins! G4 and G3 have the same JTAG Pins.
I search for a damage Prophet to but i doesnt want pay over 80€ for a community project without any payment. It some on give me a wizard or prophet Board ... i desolder the IC ... search for JTAG Pins ... and reflash it ... send it back but working :->
the device doesnt damage if i resolder the DOC ... i have the right soldering mashine.
NetrunnerAT
Where you saw on DOC points jtag ?
You need the signals TDO TCK TMS TRST TDI.
DOC only memory and there no these signal.
What jtag you will use? And no program for flash DOC through jtag - see about Universal jtag.
I flashed HardSPL 2.30olipro and it wont boot the OS when I reset, the screen stays black like its still off and the green light at the top stays on, I can still access the bootloader and use MTTY, I have tried flashing various ROMs and the "set 14 0" but nothing works, At the moment I have :
IPL-1.00
SPL-2.30.Olipro
Anyone have any ideas?
Well, it appears you can get to mtty...
Try Task 28 (this usually works when stuck in boot screen - not sure exactly where you are stuck)
or...
Try flashing a new ROM.
todd_jg said:
Well, it appears you can get to mtty...
Click to expand...
Click to collapse
Yea no problems getting into the bootloader and using MTTY
todd_jg said:
not sure exactly where you are stuck
Click to expand...
Click to collapse
I'm stuck as soon as I turn it on, blank screen like its still off and green light at the top is on the whole time, but not when i go to the bootloader.
Thanks for the help
My problem of noot being able to see any splashes and not being able to turn on for that matter is weird, Who knows a way that I can erase all of the phone totally except for the bits that cant be likle the SPL and IPL, Is there any way possible to flash someones dumped rom, and use the wlan fixing method to set yourself a new Mac adress etc.
In the memory map it says the Radio and bootloader are at "0x????????" does anyone know whats under the mysterious question marks?
deleted post
Korpse said:
My problem of noot being able to see any splashes and not being able to turn on for that matter is weird, Who knows a way that I can erase all of the phone totally except for the bits that cant be likle the SPL and IPL, Is there any way possible to flash someones dumped rom, and use the wlan fixing method to set yourself a new Mac adress etc.
In the memory map it says the Radio and bootloader are at "0x????????" does anyone know whats under the mysterious question marks?
Click to expand...
Click to collapse
Have you tried to reflash the HARDSPL?
binky11 said:
Have you tried to reflash the HARDSPL?
Click to expand...
Click to collapse
Thanks for helping me
It wont actually let me write over it because it has that protection on it to stop roms overwriting it with an older version, would it work (and be safe) to delete the SPL using the erase command then reset the hermes and write the SPL again?
Hi! i also got same problem, can still access bootloader and mtty only
Any solution that i can do? the mtty command " erase [StartAddr [Len]] " can it?
Cmd>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 610
Storage Total block: 326
Total Bad Block in CE: 0
NeedToEraseBlockStart: 623
NeedToEraseBlockEnd: 936
Storage format success
Cmd>checkimage
IPL CRC checksum = 0x856C952E
SPL CRC checksum = 0x738D6562
CE CRC checksum = 0x92C76E00
ExtROM CRC checksum = 0x2F8830F2
Radio Image CRC checksum = 0xB3F22A62
Thanks first.....
Korpse said:
Thanks for helping me
It wont actually let me write over it because it has that protection on it to stop roms overwriting it with an older version, would it work (and be safe) to delete the SPL using the erase command then reset the hermes and write the SPL again?
Click to expand...
Click to collapse
The SPL area is touchy. If you were to erase the Bootloader, I am not sure you would ever be able to flash anything, since it uses bootloader commands to do it. Check the MrVanx downgrade guides. There are instructions for overwriting the latest HardSPL. It is a two step process, first using SSPL. Give it a shot.
Im having to same problem,
IPL 1.04
SPL 2.30 Olipro
Cmd>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 13
Storage start block: 462
Storage Total block: 474
Total Bad Block in CE: 0
NeedToEraseBlockStart: 475
Storage format success
Cmd>checkimage
IPL CRC checksum = 0xC1AC9D2F
SPL CRC checksum = 0x327DEB48
CE CRC checksum = 0x4E705577
ExtROM CRC checksum = 0x85083D45
Radio Image CRC checksum = Checksum: Wait interpreter timeout
0x0
Cmd>
when I try to reflash any rom I get an error, usually hangs around 12%
Hey guys,
Anyone got a resolution to this problem yet?
Heres whats happening:
When I turn on the device I get the green led light but nothing shows on the screen at all, I can still access the boot loader the normal way.
- Tried Task 28
- Can flash any ROM but doesn't fix issue at all
- Happened after i updated to HardSPL 2.30, but cant downgrade because I need access to the OS to use SSPL.
Thank you for any help
Same problem.
Hi,
don't know if this will work for you, but it did for me. the difference is that mine wasn't hardspl.
I had the same problem when i was trying to upgrade to WM6 a friends JasJam (i had a USB connection problem). i tried alot of flashing, and the only one that seemed to work for me was the Official I-Mate ROM i got from this thread:
http://forum.xda-developers.com/showthread.php?t=348436
and flashed it after going into the bootloader.
after flashing this, i loaded the hardspl v7 from this one.
http://forum.xda-developers.com/showthread.php?t=296722
and after that, flashing any ROM works perfectly.
Hope this helps.
I'm going to try that but I'm not sure if it will work.
I am already running:
IPL-1.00
SPL-2.30.Olipro
so it will not let me override it with HardSPLv7
Not sure if I can be of much help but I had the exact same problem after a flash, then just booted into the bootloader and loaded a ROM from my MiniSD card (CRCs Rom) and that seemed to fix my problem. I also have HardSPL 2.30 installed
try
cmd>set 16 0
Hope it works, normally when i get stuck in the bootloader its what i do, soft reset, plug it to usb run mty and do that comand. after it says write nand soft reset the device, it should load the os with no problems ^^
I have the same problem too. I ran the hermes unlocker v3a and after 100% it won't boot, but the green light turns on at the top. I can get into bootloader and MMTY. IPL 1.01 and SPL 1.4 Olipro
I'm a total noob so please somebody help!
OK guys, here it is... Hard-SPL for all of you that want to **** around with your devices a little bit more than everyone else.
It's 2.60 and has an unrestricted rbmc as well as allowing you to lnb files and once again access the AT interpreter/Bootloader via rtask, although I should point out that the command for the AT interpreter is now "rtask 7" - "rtask b" performs a security check that wastes time... I put this in for completeness more than anything to have a similarity to the newer MFG bootloaders.
and yes... I can count, I know I've gone from V7 to V9, but there was a previous build I made internally.
and finally... when it flashes, it will go to 100% then your device will restart; the RUU will throw an error but just click the exit button, all is well.
This bootloader will also allow you to overwrite it... but this requires especially modifying the NBH to do so... otherwise it's just skipped
Code:
[b]CURRENT FEATURES[/b]
-SuperCID
-no file signing required
-no password required to authenticate with bootloader
-bad NAND can be recovered with "task 2a"
-bad NAND can be recovered by flashing an OS
-SPL protected from all HTC retail SPLs being flashed by accident (to bypass, use SSPL)
-IPL protected from all flashes; protection against bogus NBH's
-bad NAND can again be checked for with "info 8"
-version displays 2.60.Olipro
-no longer tries to read bad NAND - should fix whitescreen issue
-lnbs command converted to lnb
-rtask command ported back; "rtask 7" replaces "rtask b"
-can be overwritten with a special NBH
[b]ChangeLog[/b]
[b]Hard-SPL-2.60[/b]
-ported rtask back into the bootloader
-special NBH can be made to overwrite SPL
-lnbs now converted to lnb
-special credits in info 7 command :)
[b]Hard-SPL-2.30[/b]
-Unlocked RBMC command; internal release only
[b]Hard-SPL-2.10[/b]
-based on a newer SPL base; bugfixes.
-IPL flashing disabled to prevent bogus NBHs bricking your device.
[b]Hard-SPL-1.40[/b]
-repairs a bug that affected SPL being replaced by retail ones.
[b]Hard-SPL-1.35[/b]
-addresses an issue for those with Real Bad Blocks to prevent whitescreens.
[b]Hard-SPL-1.30[/b]
- removed password for wdata commands and rbmc etc.
- activated "task 2a" to allow recovering bad blocks as well as flashing valid OS.
- Disabled SPL flashing; this SPL protects you from writing over it by accident.
- Bad Blocks "info 8" command works now allowing you to check for bad blocks.
[b]Hard-SPL-1.13[/b]
- Patched NAND check; bad NAND ignored, valid OS can be flashed to recover bad blocks.
[b]Hard-SPL-1.11[/b]
- Flashing Radio BL 0108 now supported
- Downgrading SPL no longer allowed.
- rtask command removed.
- new RUU interface required to flash ROM files.
[b]Hard-SPL-1.10[/b]
-Initial release; SuperCID and no signing required
-Compatible only with Radio BL 0107
-has rtask commands for accessing radio facilities.
2-3 times I try to flash, but without success. Always have a error 262 or 260 and progress bar stay on 0%....After 20 min I tried again and some thinks happened very fast that I can't explain, but latter I see ipl 1.10 olines, or similar, and see spl 2.60. After soft reset I see my "old" spl 2.30Olipro. One more time I start and now is ok. IPL -1.03 SPL-2.60.Olipro
10x Oli.
Great works
well... I was pretty chuffed myself
Great one buddy!
太棒了。
Good job，thanks
Necessity to replace v7 with v9?
Hi Olipro,
Congratulations on the new version of Hard-SPL.
One quick question though, is it advisable to replace the v7 with this new v9 on our phones at present?
I mean is the level of protection more or less the same for the average person who does not want to piss around with phone flashing as much as the pro's do.
Regards.
Trezona said:
Hi Olipro,
Congratulations on the new version of Hard-SPL.
One quick question though, is it advisable to replace the v7 with this new v9 on our phones at present?
I mean is the level of protection more or less the same for the average person who does not want to piss around with phone flashing as much as the pro's do.
Regards.
Click to expand...
Click to collapse
why don't you read the feature list and figure it out for yourself
Olipro said:
OK guys, here it is... Hard-SPL for all of you that want to **** around with your devices a little bit more than everyone else.
It's 2.60 and has an unrestricted rbmc as well as allowing you to lnb files and once again access the AT interpreter/Bootloader via rtask, although I should point out that the command for the AT interpreter is now "rtask 7" - "rtask b" performs a security check that wastes time... I put this in for completeness more than anything to have a similarity to the newer MFG bootloaders.
and yes... I can count, I know I've gone from V7 to V9, but there was a previous build I made internally.
and finally... when it flashes, it will go to 100% then your device will restart; the RUU will throw an error but just click the exit button, all is well.
This bootloader will also allow you to overwrite it... but this requires especially modifying the NBH to do so... otherwise it's just skipped
Code:
[b]CURRENT FEATURES[/b]
-SuperCID
-no file signing required
-no password required to authenticate with bootloader
-bad NAND can be recovered with "task 2a"
-bad NAND can be recovered by flashing an OS
-SPL protected from all HTC retail SPLs being flashed by accident (to bypass, use SSPL)
-IPL protected from all flashes; protection against bogus NBH's
-bad NAND can again be checked for with "info 8"
-version displays 2.60.Olipro
-no longer tries to read bad NAND - should fix whitescreen issue
-lnbs command converted to lnb
-rtask command ported back; "rtask 7" replaces "rtask b"
-can be overwritten with a special NBH
[b]ChangeLog[/b]
[b]Hard-SPL-2.60[/b]
-ported rtask back into the bootloader
-special NBH can be made to overwrite SPL
-lnbs now converted to lnb
-special credits in info 7 command :)
[b]Hard-SPL-2.30[/b]
-Unlocked RBMC command; internal release only
[b]Hard-SPL-2.10[/b]
-based on a newer SPL base; bugfixes.
-IPL flashing disabled to prevent bogus NBHs bricking your device.
[b]Hard-SPL-1.40[/b]
-repairs a bug that affected SPL being replaced by retail ones.
[b]Hard-SPL-1.35[/b]
-addresses an issue for those with Real Bad Blocks to prevent whitescreens.
[b]Hard-SPL-1.30[/b]
- removed password for wdata commands and rbmc etc.
- activated "task 2a" to allow recovering bad blocks as well as flashing valid OS.
- Disabled SPL flashing; this SPL protects you from writing over it by accident.
- Bad Blocks "info 8" command works now allowing you to check for bad blocks.
[b]Hard-SPL-1.13[/b]
- Patched NAND check; bad NAND ignored, valid OS can be flashed to recover bad blocks.
[b]Hard-SPL-1.11[/b]
- Flashing Radio BL 0108 now supported
- Downgrading SPL no longer allowed.
- rtask command removed.
- new RUU interface required to flash ROM files.
[b]Hard-SPL-1.10[/b]
-Initial release; SuperCID and no signing required
-Compatible only with Radio BL 0107
-has rtask commands for accessing radio facilities.
Click to expand...
Click to collapse
I stuck in Tri-Color Screen, how can restore !?
Please help
cm1437 said:
I stuck in Tri-Color Screen, how can restore !?
Please help
Click to expand...
Click to collapse
Kill yourself.
Dear Oilpro,
I mean during flashing 2.60, it shown error msg,
then i try to recovery, but it can't.
Now i reboot it, it stuck in Tri-Color Screen,
What can i do!?
Please comment
cm1437 said:
Dear Oilpro,
I mean during flashing 2.60, it shown error msg,
then i try to recovery, but it can't.
Now i reboot it, it stuck in Tri-Color Screen,
What can i do!?
Please comment
Click to expand...
Click to collapse
run the rtask command for completing the flash
What's meaning of rtask?
Where can i found it?
pasan said:
run the rtask command for completing the flash
Click to expand...
Click to collapse
err... no, don't... that's not what it's for at all
Olipro said:
Kill yourself.
Click to expand...
Click to collapse
You are right... there is no stupid question... just offensive answers...
Olipro said:
Kill yourself.
Click to expand...
Click to collapse
Thats funny
cm1437 said:
Dear Oilpro,
I mean during flashing 2.60, it shown error msg,
then i try to recovery, but it can't.
Now i reboot it, it stuck in Tri-Color Screen,
What can i do!?
Please comment
Click to expand...
Click to collapse
Exactly the same problem. I was using 2.30.Olipro.
Stuck in bootloader.
Tried set 14 0 without success...
Please, ¿any idea?.
I've talked with Olipro in the chat and he kindly help me to manage the problem:
- Disconnect Active Sync USB connection.
- Start MTTY
- Push Enter to saw CMD> or USB>
- Type
set 16 0
and pres ENTER
and it's solved....
My error was a noobs error; I started the bootloader manually but the RUU starts a SoftSPL so it doesn't runs. Now, I've upgraded to 2.60.olipro without problems. I recognized that I'm stupid
Thanks Olipro!!!!!
Got error 282 and prompted with view documentation or recovery. Used mtty and set 16 0 to recover back.
Tried a couple of times but with same error.
Yes, get the same tri color Bootloader screen.
I reflash a new OS, problem solved for me att least.
i found out that several people encountered problem with changing bootloader.
i also found out that there is suggestion that this problem is connected to NAND memory bad blocks. So, as i understand it, phone can work well on wm6 or wm6.5 without problem ,but in process of upgrading bootloader may come to light bad sectors and in extreme situation upgrading to such a corupted NAND, can cause dead phone.
But is it for sure problem with bad blocks in NAND memory ?
Isn't it a too common problem ? Maybe the method which we use in some cases will cause a problem ?
In my case i used Mirolg guide and i didn't try another method(Nokser guide is no longer available due to missing files).
With Mirolg guide, when i'm trying upgrade bootloader to wp7bootloader with tg downloader, i get checksum error on 99% while verifying FOTA .
From this moment i can upload wp7 rom ,but after that phone won't start.
And i can go back to wm6.5 bootloader and then upload wm6.5 ROM without problem.
And phone works fine with wm 6.5
So, i have few questions.
Someone, have files which are needed to proceed Nokser method 1 and 2 ?
Anyone know is there a way to check NAND memory for bad sectors ?(for example with mtty) - i just want to confirm that my upgrading problem is caused by bad blocks
NAND chip has bad blocks.This can't erase use riff jtag box!
Depending if these blocks contain no data, or it holds something important, phone may work or no.
If these blocks contain no data or not important,it may work!
If these blocks contain important data,it may not work!
Upgrade bootloader to wp7bootloader have two ways with tg downloader ,
you can Search my Posts ,
If you upload wp7 rom successfu ,but won't start,you may flash all file,all mbn and bin.(NPRG8650.hex /partition.mbn /dbl.mbn /dsp1.mbn /fsbl.mbn /osbl.mbn /amss.mbn /apps.mbn(0) /appsboot.mbn /flash.bin .etc)
You can use ZTEiT Common downloader or other tool (qpst / acer euu etc..)
Good luck！
checksum error
Hello,
The first thing I would like to thank the dev team for its work exelente.
Now to my problem, after flashing the boot loader checksum error occurs.
I have an almost new TG01 by orang Switzerland, I do not think it's broken.
Winmobil 6.5 is no problem to flash.
At the moment running the MIROM 0321radio
Thank you for your efforts
qinwengui said:
Upgrade bootloader to wp7bootloader have two ways with tg downloader ,
you can Search my Posts ,
Click to expand...
Click to collapse
by mentioning two ways of upgrading ,are you talking about this:
"1. wm6 to wp7 bootloader
Short pin 1,3 or 0321rom Camera+Power ,on Download mode,use TG-Downloader
file tg01 wm6 Update wp7 Bootloader.bin, no os" ?
In other words one method is to short pins
and second method is 0321rom Camera+Power
Or i overlooked this another method of upgrading bootloader in your posts?
Is there a way to format or test NAND without JTAG ?
no,http://forum.xda-developers.com/showpost.php?p=18800260&postcount=135
Thanks for help.
First advice was good.
Problem was solved by flashing all files.
You can download missing files here:
http://hotfile.com/dl/148417552/39f77d9/wp7OS_files.zip.html