Related
I have tried flashing about 3 different ROMS and they the RUU stops them at 99%. The bar on the phone goes RED.
Please dont get confused with my signature, the phone is a Wizard and is running SPL 2.16.001 (G4).
The phone remains in bootloader mode (Red Green Blue screen)
What do i do from now?
Just tried again and it stopped at 100% and then went RED.
Been reading on all wizrd forums, and I dont think this has happened before.. (Well I cant seem to read it anywhere).....
Any help would be much appreciated...
Thanx
From EquinoXe:
Soft SPL only allows you ONE update, so phone is CID unlocked only when Soft SPL is loaded.
It's normal for the RUU to stick on 99 % for a couple of minutes, The whole update will take aprox 10 minutes.
You can try the hard SPL from there you are semi-permanently CID unlocked.
Good luck,
EquinoXe
Thanx for your quick response...
After it goes red an error pops up with the option of recovering...
I have tried the RUU that came with the SoftSPL package and MUN's RUU...
i think even if its a red Bar its still updating. just wait.
hi, sorry if nobody responded before, i dont know if they did so i dont know if you are being sarcastic. Leave it. Literally. Put it on, and let it update until it says something else. dont cancel it or unplug it. leave it doing it. then if a PC error comes up copy it here. Simple as that
Flash back to your original stock ROM/Wizard Love ROM first, then use SSPL again and flash your next ROM.
starkwong said:
Flash back to your original stock ROM/Wizard Love ROM first, then use SSPL again and flash your next ROM.
Click to expand...
Click to collapse
Thanx! That Wizard Love ROM manages to do the trick!
I think some of the ROM's you did would of been fine. You just have to be patient. Let it do it, watch some TV while its doing it. Wait for the PC to give you a successful message or an error message!
I'm tooooooo , plz help meeeeeeeeeee
iuemne.com said:
I'm tooooooo , plz help meeeeeeeeeee
Click to expand...
Click to collapse
As already stated above, this is NORMAL phenomenon.
Whenever I flash a new ROM onto my wizard, it always reaches 99% quick, and then, seems to be stucked there for ages. No big deal.
Just wait, the bar turns red, so what? it doesn't matter. After a while, it will complete the 1% left that take so long. I don't know the reason either, but it doesn't affect the flashing, nor it does for the phone itself. You just have to wait, patiently.
G4 stuck at 99%
hi man,
i ahve a wizard G4, i tried to upgrade to TNT WM6.0 and in between flashing my power went out...now i'm not able to flash....the upgrade bar reaches 99% then goes to recovery mode...no other rom is flashable
please advise buddy
nash
The bar turning red is a very normal phenomenon... Basically to make this very simple for all who don't believe us or freak out every time you see a red bar, this is what your wizard is doing.
GREEN:: Rom is flashing
RED:: Rom flashing is TEMPORARILY paused while RUU adjusts it's speed to finish the job.
BLUE:: Rom flashing is complete.
My suggestion to all who are flashing roms and are too impatient to take your eyes off the screen: go smoke a cigarette or get a bite to eat out of the fridge or watch some TV or hell, go for a quick drive to the convenience store down the street to buy a pack of gum to kick your computer addiction. It works for cigarettes...
In other words... BE PATIENT. It is not the end of the world if it goes red. Now if it gives you an error message it's still not the end of the world. Just flash back to your carriers original rom or give it a little Wizard Love and then try again...
Best of luck to you all...
Just wait patiently when red bar is shown (Official meaning of red bar is adjusting write method of flash memory).
It may stuck at 100% with red bar for as long as 5 minutes.
I got the same probleme with my trinity, RUU got stuck at 99% and then I get an update error from RUU and I can't flash nor restore any flash !
I am now stuck in bootloader and looking for a real solution, what can I do to have a working rom !?
same problem
I have a qtek 9100 and still 99%, but now, dosent respond, i tried soft and hard reset but only i have a black screen, no lights... nothing...
I removed the batery for a day... but still black..
Pleeeease.. Help me.
thanks
i installed Olipro 2.10 1 month ago and flashed my phone with VP3G's rom. Phone worked fine for many months. Today, i restarted my phone... now it wants to stay on the tri color screen on the restart.... Every now and then it will let me boot the phone up normally, the phone will work fine, till i restart. It will be stuck again. I can reinstall the rom and it keep hanging on the restart. I feel I had read through all these forums, but can seem to get it going. Any sugestions would be nice.
bharper1977 said:
i installed Olipro 2.10 1 month ago and flashed my phone with VP3G's rom. Phone worked fine for many months. Today, i restarted my phone... now it wants to stay on the tri color screen on the restart.... Every now and then it will let me boot the phone up normally, the phone will work fine, till i restart. It will be stuck again. I can reinstall the rom and it keep hanging on the restart. I feel I had read through all these forums, but can seem to get it going. Any sugestions would be nice.
Click to expand...
Click to collapse
Thats odd... Could be a few things -Have you tried taking the battery out for a few moments and then doing a hard reset - If not it's worth a try...
Have you tried the steps listed under problem 4 here - if so what happened and is your radio OK?
Mikeapollo said:
Thats odd... Could be a few things -Have you tried taking the battery out for a few moments and then doing a hard reset - If not it's worth a try...
Have you tried the steps listed under problem 4 here - if so what happened and is your radio OK?
Click to expand...
Click to collapse
I left the battery out for about for a few minutes. It will let me do a hard reset, but it is still on the same screen. I have been to the page ya linked to me, i couldn't get it working with that info.
i am trying mtty.exe again. I am typeing in "set 14 0" at the command line, using the usb option. I also typed in "set 16 0" at the command line, with nothing different.
I just ran Mtty, use the checkimage comand, got
IPL CRC checksum = 0x6FFCE832
SPL CRC checksum = 0xC27E0E42
CE CRC checksum = 0x7C63DA31
ExtROM CRC checksum = 0xA47162D9
Radio Image CRC checksum = 0x9A7FAE7
My phone booted up again, went through the startup screen . i configured the touchscreen, Rebooted then everything was fine. I was able to call out with it. I tried to restart it again just to see if the triscreen would come up again... it did.
does it connects to usb? or rejects the connection..try to flash any branded rom...whiich cam with ur device...
malhaar said:
does it connects to usb? or rejects the connection..try to flash any branded rom...whiich cam with ur device...
Click to expand...
Click to collapse
It is usb sencing. I can flash the rom over and over. Seems i have to keep taking the battery in and out to have a chance in it booting up.
bharper1977 said:
It is usb sencing. I can flash the rom over and over. Seems i have to keep taking the battery in and out to have a chance in it booting up.
Click to expand...
Click to collapse
Bizarre! This is a daft question, but your OK button (or any other buttons) isn't sticking is it?
I called ATT this morning. They told me to do a soft reset, then once it rebooted... Do a hard reset. It's been fine ever sence. I'll let yall know if it comes back.
So for some reason my nike WILL NOT flash a rom fully it will always stop at like half way or a random percent..
Does anyone know why/ and or can help me?
try holding the USB cable in the Niki while flashing, or give it a wiggle before flashing to see if charging light stays on, my usb is fuxd! and has failed a couple of times due to bad connectivity. so now i always hold it in firmly whenever flashing.
Thats not the problem.... Every time i flash a rom
For instance If i flash mary's rom..
It will stop at 73% every time.
OR Rome O.s
68% every time...
Like whats going on?
Check your SPL
Try turning off your Tocuh first.... then power it up by pressing <Power> + <Camera> button....
Look at the startup message carefully...
If you still using S-SPL then you have to reflash HardSPL or USPL.... before you are good to go for another flash...
make sure you also download the latest HardSPL or USPL from the forum.... Older SPL sometime cann't sucessfully map all the memory for flashing....
another detail
here is another good flashing guide from our good ol' pal <netrunnerAT>...
http://forum.xda-developers.com/showthread.php?t=409690
Before 1 month start all the problems.
My hd2 didn't load the system...
I make some tests and i have make an update everything to the last leo,hspl.
The phone after the update was ok but after a week stop working at all.
Black screen.
I have buy new battery htc official but still nothing.
It doesnt start....
Please help...
Are there any way to start the phone?
Sorry for my bad english...
anyone?
What ROM/RADIO?SPL versions did you flash?
Is it a TMOUS HD2?
Is there a red light when you connect the phone to the charger?
hspl 2.08
Radio Leo 2.15.50.14
Energy.Leo.21916.Sense2.5.Cookie.2.0.Jan.06
no doesnt light the led when i put it on charger.
I try with htc and they say 350 euro for changing the main board...
But after some hours i put it to another charger and the phone start in boot loader
mode.
i tryed to change radio bur crash and again the same stop working.
Any tip?
I thing i am not the one this have happent again...
And one another thing.
Today my hd2 start to the bootloader and with HSPL2_RUN i have downgrade hspl 2.08 to 1.66.
On the screen inform me success and again doesnt start up....
Probably the phone is ok but everything start with the soft...
but it still didnt start again.
Yesterday start 4 times to the tricolor mode
At first i have put the nbh file as the post to the sd and after downgrare the radio to Leo RADIO 2.07.50.27_2 from Radio_2_12_50_02_2.
The hspl became spl 2.08
After this again the same nothing and again didnt start..
I dont unterstand
i will try task 29 and after this i will flash oriinal rom if it starts...
All these say to me that it is not a hardware problem but only software...
Please help...
If hspl.exe says success, but doesn't change when you go back into bootloader, this is often connected to a stuck radio.
The only thing I can suggest is flashing your phones correct stock rom from SD,and pay attention to the blue writing,see if any part fails.
Any tip to wake
Any tip to wake up the phone?
It doesnt start again....
It drive me cazy....
Please any tip?
Anyone....?
By "wake up," do you mean turning it on?
If you're having problems turning the phone on, I usually have to pull the battery out for a good 5 minutes before putting it back in and rebooting.
My HD2 has the same problems as you man Hope there's a solution, and I really hope it's not a hardware problem. Best of luck to you!
Yes
By wake up i mean to start working, turning on....
I cant unterstant why the phone didnt start.
I don't know where to begin so I'll just list the problems I have been encountering why trying to flash a stock ROM into my TMO HD2.
Preloaded with Android Gingerbread 2.3+HSPL 2.08+Magldr 1.11
Stuck at 123456 Go Go Go
Digitizer cracked & removed
Tried flashing stock TMO 3.14 ROM to ascertain if it is lack of digitizer causing problem
Was able to perform Task 29 normally initially
Could not run 3.14 RUU successfully nor via SD card method with HSPL 2.08 intact. RUU stuck at 8% & SD method stuck at Radio forever
Upgraded HSPL to 3.03 successfully using HSPL 4
Still could not run 3.14 RUU; same as above
Rolled back to SPL 2.08.000 using HSPL 4
Started having problems with Task 29; could not complete properly
Tried MTTY (v.1.42) but could not format NAND
Upgraded to HSPL 2.08 using HSPL3
Still could not perform Task 29 successfully. Sometimes successful & other times not. Mostly met with limited success using SD card method & CustomRUU Task 29 met with numerous connection error (262, 266, 284)
.....
Now, managed to roll back to HSPL 2.08 after redoing SPL 2.08.0000 even though 'We hacked it' screen stayed on with HSPL3 tool 'Critical error'
Trying to flash stock 3.14 RUU met with Error 284
Tried flashing from SD card, screen displayed 'Loading...' perpetually
After pulling battery for about 10 mins, powering up to 'Stick Together' splash screen without any red letters
Now when trying to flash using RUU, it would fail with Error 284/266 & the driver would spontaneously change from HTC USB Sync to Qualcomm Diagnostic Interface 3197 (COM17)??!!
Question:
I think my phone is not bricked but can it be salvaged?
Will the lack of a digitizer prevent it from being flashed?
Can it be salvaged with JTAG?
I cannot charge the battery in the phone now even with power off. Would the remaining battery power prevent or negatively influence the flashing?
Anyone who have met with success in recovering from something like this...or anyone who has dealt with similar symptoms, please advise me what to do from here.
I really need help.
Thanks!
Konker
RUU stuck at 8% & SD method stuck at Radio forever
Click to expand...
Click to collapse
Stuck radio, not a good sign,, (often sticks at 9% too, anything from 7 to 10 is usually the radio)
Can it be salvaged with JTAG?
Click to expand...
Click to collapse
probably your only option, though I would guess at a hardware issue, bad nand blocks, or similar with a ll the varied errors.
You could also try chilling teh phone in eth fridge, in a sealed bag for half an hour, with teh sd card ready to flash stock rom straight away, , if this is sucessfull, then you have thermal issues.
samsamuel said:
Stuck radio, not a good sign,, (often sticks at 9% too, anything from 7 to 10 is usually the radio)
probably your only option, though I would guess at a hardware issue, bad nand blocks, or similar with a ll the varied errors.
You could also try chilling teh phone in eth fridge, in a sealed bag for half an hour, with teh sd card ready to flash stock rom straight away, , if this is sucessfull, then you have thermal issues.
Click to expand...
Click to collapse
Thanks for the response!
Am I suppose to see the R... at the bottom of the splash screen if the radio is working normally despite having completed Task 29?
I know the OS is wiped but the radio is still there....I think.
Does JTAG restore the radio?
The phone does not get anywhere near hot or very warm when I'm doing all these steps so will putting it in the freezer make a difference? I was under the impression that this works when the device has been exposed to heat or is hot for an extended period of time.
Task 29 doesnt touch the radio, only the rom. You may be able to flash cooked roms, and maybe magldr, just not anything with a radio included. Fridge probbly won't help if you're happy that it isn't heat related.
samsamuel said:
Task 29 doesnt touch the radio, only the rom. You may be able to flash cooked roms, and maybe magldr, just not anything with a radio included. Fridge probbly won't help if you're happy that it isn't heat related.
Click to expand...
Click to collapse
I'm not seeing the R... at the bottom of the splash screen now so does that mean that my radio is fried?
Also, can you comment if not having a digitizer installed would prevent WM6.5 from flashing properly? I've read in the Android thread that it will prevent Android from booting, which is why I decided to flash a WM ROM first to ascertain the hardware condition.
I'll give the 'cold treatment' a try & see how it goes & am in the process of downloading a custom ROM to try. The current HSPL is 2.08 but I'm not sure if it is working properly since the last HSPL attempt ended with the 'We hacked it' stuck on the screen without a reboot & a critical error for the HSPL tool.
Lastly, any idea why it would switch from standard driver to diagnostics driver? It's weird & I can't explain it.
konker said:
i'm not seeing the r... at the bottom of the splash screen now so does that mean that my radio is fried?
Samsamuel... it's a bad sign, but there are situations where that info doesn't show, however combined with it sticking at 8%, which is about when the radio gets flashed.....
Also, can you comment if not having a digitizer installed would prevent wm6.5 from flashing properly? I've read in the android thread that it will prevent android from booting, which is why i decided to flash a wm rom first to ascertain the hardware condition.
Samsamuel........ No, people have flashed successfully with broken digitizers, shouldn't affect winmo, up until it requires input after initial boot.
I'll give the 'cold treatment' a try & see how it goes & am in the process of downloading a custom rom to try. The current hspl is 2.08 but i'm not sure if it is working properly since the last hspl attempt ended with the 'we hacked it' stuck on the screen without a reboot & a critical error for the hspl tool.
Samsamuel....... Id try a different pc if at all posible, though i have had to pull battery myself at the hacked it screen, (not even sure it does reboot itself, from memory, hehe)
lastly, any idea why it would switch from standard driver to diagnostics driver? It's weird & i can't explain it.
Click to expand...
Click to collapse
that's worrying, too, because that's what happens when tmous gets radio bricked,,,phone becomes utterly unresponsive and pc searches for qualomm diagnostic drivers.
I too in similar situation. I can't get NAND android to boot up get stuck on 123456 GO GO GO! Try flashing the stock rom and get stuck on 8% Task 29 still work for me. If I flash Task29 you think I'm able to flash a custom rom that doesn't touch the radio? The only problem is that i was able to flash the radio with no problem.
itzstevo said:
I too in similar situation. I can't get NAND android to boot up get stuck on 123456 GO GO GO! Try flashing the stock rom and get stuck on 8% Task 29 still work for me. If I flash Task29 you think I'm able to flash a custom rom that doesn't touch the radio? The only problem is that i was able to flash the radio with no problem.
Click to expand...
Click to collapse
Do you still have magldr on the phone?
If not, do you see the R...when the default splash screen shows up after powering up the phone?
If not, you might be in a similar situation as me.
I cannot ascertain if my radio is really bricked as there's no way to see or detect that & as samsamuel indicated, having the PC detect a diagnostic port might suggest that my radio is bricked.
I did try to flash a compatible radio to my phone but it failed everytime.
Magldr is still on the phone. I am able to flash new radio with no problem. are you able to flash just a rom and not a a rom & radio?
samsamuel said:
Stuck radio, not a good sign,, (often sticks at 9% too, anything from 7 to 10 is usually the radio)
probably your only option, though I would guess at a hardware issue, bad nand blocks, or similar with a ll the varied errors.
You could also try chilling teh phone in eth fridge, in a sealed bag for half an hour, with teh sd card ready to flash stock rom straight away, , if this is sucessfull, then you have thermal issues.
Click to expand...
Click to collapse
yes you are right my bro ... had same problem ... after cooling phone in fridge for 5-10 min it will go perfect BUT still it wouldnt boot into winm so i decided to try android in nand , flashing went ok but after that it wouldnt boot Fatal hit ( magdlr) so i put phone in fridge again for 5-10 min and Yes it booted in android - tried same with WP7 ... But after using a while it will get hot and will stock or restart
konker said:
[*]Can it be salvaged with JTAG?
Click to expand...
Click to collapse
No my bro... jtag only writes boot - repair files
itzstevo said:
Magldr is still on the phone. I am able to flash new radio with no problem. are you able to flash just a rom and not a a rom & radio?
Click to expand...
Click to collapse
I think your HD2 is in a lot better shape than mine.
At least you can flash your radio...I can't flash either ROM or radio.
But I suspect your problems might be due to corrupted NAND.
Have you tried Task 29 with mtty?
At least you can see error messages with mtty when doing Task 29.
ubejd said:
yes you are right my bro ... had same problem ... after cooling phone in fridge for 5-10 min it will go perfect BUT still it wouldnt boot into winm so i decided to try android in nand , flashing went ok but after that it wouldnt boot Fatal hit ( magdlr) so i put phone in fridge again for 5-10 min and Yes it booted in android - tried same with WP7 ... But after using a while it will get hot and will stock or restart
Click to expand...
Click to collapse
ubejd, you gave your HD2 the 'cold treatment' after it turned warm & refused to boot or rebooted automatically am I right?
Would it do my HD2 any good to put it in the freezer when it is cool as room temperature? It has been sitting there unplugged & unpowered for at least 8 hours. I have not tried the 'cold treatment' but flashing custom ROMs with HSPL 2.08 also failed.
Seems like a combination of radio brick & NAND failure...
konker said:
ubejd, you gave your HD2 the 'cold treatment' after it turned warm & refused to boot or rebooted automatically am I right?
Would it do my HD2 any good to put it in the freezer when it is cool as room temperature? It has been sitting there unplugged & unpowered for at least 8 hours. I have not tried the 'cold treatment' but flashing custom ROMs with HSPL 2.08 also failed.
Seems like a combination of radio brick & NAND failure...
Click to expand...
Click to collapse
yes you are right my Bro
you can try, it wouldnt do any harm but just put in isolated place - bag before putting in the fridge - to keep safe phone from getting wet and dont let more then 5-10 min maximum... but as i told it will not boot again in win mob - i hope it does but i doubt ... if it fails to boot than consider to go with android or winp7
i have one question how it began to act like this... did it fall or you bought like that
i hope you success
best regards from me
Gave it a go with the freezer test. I was surprise that i was able to boot up into CWM, & load up Android. Now I can only use the phone for maybe 20 min or so before it get hot again and I have to put it back in the freezer. Is there a way to tell which HD2 is bad batch?
I first one had no problem beside the bad screen, my 2nd HD2 is having heating issues. Seem like I can't win.
itzstevo said:
Gave it a go with the freezer test. I was surprise that i was able to boot up into CWM, & load up Android. Now I can only use the phone for maybe 20 min or so before it get hot again and I have to put it back in the freezer. Is there a way to tell which HD2 is bad batch?
I first one had no problem beside the bad screen, my 2nd HD2 is having heating issues. Seem like I can't win.
Click to expand...
Click to collapse
I gave my HD2 the 'cold treatment' & I was mildly surprised that it reached the 2/3 mark when using the SD card method to flash a custom ROM but that was it. Back to square 1...
itzstevo said:
I first one had no problem beside the bad screen, my 2nd HD2 is having heating issues. Seem like I can't win.
Click to expand...
Click to collapse
if you have both of them take motherboard from the one who has bad screen and put in one who has heating issues this way you will have at last one working hd2...
I had the same problem too. I knew I wasn't the only one with this problem.
Now I'm sure, MAGLDR makes the NAND corrupted (over 8%). My phone won't charge too, gets stuck at 8%, get stuck on splash screen and doesn't show any red lines...
PasSlert said:
I had the same problem too. I knew I wasn't the only one with this problem.
Now I'm sure, MAGLDR makes the NAND corrupted (over 8%). My phone won't charge too, gets stuck at 8%, get stuck on splash screen and doesn't show any red lines...
Click to expand...
Click to collapse
Flash failing at 8/9% has been happening long before magldr, , and seems to be connected to the radio being corrupted.
But I can flash a radio via RUU... if my radio were corrupted, flashing a radio should not be possible. Am I right ?
With RUU : I'm stuck about 1 minute on 8% then the process resume up to 100% without any error, but whatever the ROM I flash, no one reach splash screen.
With SD : No problem.
Like the OP, my phone is acting weird when I plug on charge.
With cable to PC : autoboot (MAGLDR 1.13 issue)
With cable to AC : red led but when I plug off the cable, the red led is still on (until I remove the battery).
It's clear that in any way, MAGLDR is not completly removed of my HD2 (yeah, I flashed some stock ROM with SD card).
I think I'll send it to repair, I'll leave feedback if I send it.