Related
I've been running Warm 2.2 for a couple of months now, but lately I've been getting a lot of internet connection issues, today - I spent the entire day not being able to connect to 3G, don't know why so I figured I'd update the Radio,
Whatever that means..
managed to find updated versions on this website of the Radio, Wimax, Hboot and all those PIC, PICM, whatever it's called..
Rebooted to recovery, and flashed all the zip files, and now i'm STUCK there. Every time the phone restarts it just brings me back to the same old screen that says:
SUPERSONIC EVT2-2 SHIP S-ON
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010
HBOOT
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
What do I do now? can I flash a new ROM using the USB cable? I don't think i have a micro sd card reader on me...
Anyway to fix this? I'd rather not wipe my device, but I can do it if I have to.
HELP
THANK YOU.
i might be wrong but i think your s-on means you lost root. but is you see the recovery option, i would go in there and try to restore a backup, hopefully you have one
Ahha.. a backup.. that would be nice :\
no backup here..
yoerz said:
I've been running Warm 2.2 for a couple of months now, but lately I've been getting a lot of internet connection issues, today - I spent the entire day not being able to connect to 3G, don't know why so I figured I'd update the Radio,
Whatever that means..
managed to find updated versions on this website of the Radio, Wimax, Hboot and all those PIC, PICM, whatever it's called..
Rebooted to recovery, and flashed all the zip files, and now i'm STUCK there. Every time the phone restarts it just brings me back to the same old screen that says:
SUPERSONIC EVT2-2 SHIP S-ON
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010
HBOOT
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
What do I do now? can I flash a new ROM using the USB cable? I don't think i have a micro sd card reader on me...
Anyway to fix this? I'd rather not wipe my device, but I can do it if I have to.
HELP
THANK YOU.
Click to expand...
Click to collapse
Go to the following site http://forum.xda-developers.com/showthread.php?t=715485 and download the EVO_Radio, the WiMAX, PRI and NV "individually". Afterwards, connect your EVO to your computer and boot up. If you're taken to the bootloader screen like you stated in your post, select recovery from the list of options. Hopefully, you're using amon RA v2.3. Anyway, If you can get into recovery, select the MS-USB option. Your computer should detect your SD card shortly afterward. Copy the files you downloaded to your SD card. When complete, eject/unmount the SD card from your computer first and then push the power button on your EVO to unmount from within recovery. Now go to the wipe menu and wipe the cache & dalvik. After that, go to the flash menu and flash the PRI. You should reboot to the radio update screen. Be patient and DO NOT PULL THE BATTERY. When complete, you should reboot back into recovery. If you happen to reboot back to the bootloader, simply select recovery from the available options. Now flash the EVO_Radio. Like before, you will reboot to the radio update screen. Be patient and DO NOT PULL THE BATTERY. After some time, you should reboot back into recovery. If not, get to recovery from within the bootloader screen. Do the same thing for the NV and the WiMAX. You *may* have to reflash the HBOOT. Anyway, after you've updated your radios, reflash the recovery. I HIGHLY recommend RA v2.3 You can download the PC36IMG.zip file for it here: http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=PC36IMG.zip
After that, see if you can boot to your homescreen. If you can, great. If you cannot, try reflashing the rom. Remember, after flashing the radios and preparing to boot to your homescreen, you will appear to hang at the white EVO screen. Be patient and DO NOT PULL THE BATTERY. It will eventually clear. Hopefully, this will help you. Take care.
emcp422 said:
i might be wrong but i think your s-on means you lost root. /QUOTE]
Great catch!...... I totally missed seeing the "S-ON" in the OP's post and you're right, that usually means he is no longer rooted and need to re-root his device. OP, disregard my last post and RE-ROOT your device.
Click to expand...
Click to collapse
yoerz said:
I've been running Warm 2.2 for a couple of months now, but lately I've been getting a lot of internet connection issues, today - I spent the entire day not being able to connect to 3G, don't know why so I figured I'd update the Radio,
Whatever that means..
managed to find updated versions on this website of the Radio, Wimax, Hboot and all those PIC, PICM, whatever it's called..
Rebooted to recovery, and flashed all the zip files, and now i'm STUCK there. Every time the phone restarts it just brings me back to the same old screen that says:
SUPERSONIC EVT2-2 SHIP S-ON
HBOOT-2.10.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Oct 15 2010
HBOOT
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
What do I do now? can I flash a new ROM using the USB cable? I don't think i have a micro sd card reader on me...
Anyway to fix this? I'd rather not wipe my device, but I can do it if I have to.
HELP
THANK YOU.
Click to expand...
Click to collapse
Well, if you can get to the bootloader, it's unlikely that you're bricked. You *should* be able to recover here. The other guy is correct, since you're now S on, you lost root. Do you still have recovery? When you select 'recovery' from the bootloader, what result are you left with? (do you successfully boot to custom recovery, does it bring you back to the bootloader, or does it show you a black screen with a red triangle in it? If you still have recovery (I doubt you do, for some reason), then you should be able to flash the Unrevoked Forever S off tool, to set you back to S off. From that point, you should be able to flash a new rom.
However, I'm guessing that you lost recovery (for whatever reason), and you'll probably need to run an RUU, to try to flash the phone back to stock. From that point, you could re root again.
You can find an RUU here, http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu. Download the newest one, i believe it's the first on the page (3.70 software).
Edit: And about wiping your device, it seems as though that's already happened, ha. I don't think your stuff is coming back. Your only hope to get it back would be a nandroid backup, but you said you don't have one. We don't even know if you have recovery or not. Once you find that out, we'll know a lot more. If you're lucky, and still have recovery, it will be quick and easy for you to get back up and running.
Double Edit: OP. What recovery were you using? Did the radio flash seem to be successful, and then you just couldn't boot up afterward? Did you recieve any error messages when flashing it or anything like that?
Bricked means it won't even turn on...you just lost root. Do what the other posters said and please, read and take your time. You don't seem to have a firm grip on the whole rooting process.
You probably upgraded your hboot which is why you lost s-off and your phone won't boot. You can flash a kernel to get it to boot but you will need to get s-off back before you will be able to flash the radios.
Sent from my PC36100 using XDA Premium App
Just put pc36img.zip to root of sdcard and let it do its update then go from there.
Sent from my PC36100 using XDA Premium App
I've been looking through threads for hours and have tried a lot of what has been suggested. At first it just started randomly bootlooping ( white htc screen, restart). I then tried some guide on a thread that had me ADB then RUU, once that was all done It got to the white htc evo screen, turned black then vibrated 5 times and the green light started to flash. I can't get into the recovery menu, I click it and it just goes straight to white htc screen. I've flashed multiple PC36IMG's with different recoveries, with no luck.
My fuse is burnin low...
Supersonic EVT2-3 SHIP S-OFF
HBOOT-0.79.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-1.39.00.04.26
APR 14 2010, 15:41:34
*update-
I tried another RUU, a newer version.
http://forum.xda-developers.com/showthread.php?p=7529500#post7529500
Now it seems to be in a bootloop, no 5 vibrate+ flashing light though..
IxHaku said:
*update-
I tried another RUU, a newer version.
http://forum.xda-developers.com/showthread.php?p=7529500#post7529500
Now it seems to be in a bootloop, no 5 vibrate+ flashing light though..
Click to expand...
Click to collapse
OK......so basically you got no RECOVERY?....so when you boot into the BOOTLOADER to install the PC36IMG....does it recognize the image?.......and does it ask u to install and reboot?......we'll start there
What rom were you running? Some users have had a bootloop of death, no coming out of it, on CM7. I think it has happened on other AOSP roms as well, but you mainly see it on CM7 - probably because of the larger user base.
I have yet to see a solution for it, I think everyone else had to report it lost and pay the $100 deductible through insurance. The only hope is to keep running RUUs and hopefully one will stick.
(from... Evo/MIUI/Tapatalk)
Yeah I can see the image and to install and reboot.
And I was running CM7. FFFFFF I don't have insurance... Don't really want to take it to the sprint store with S-off.. So i guess ill keep trying to run RUU's... probably wont work though
IxHaku said:
Yeah I can see the image and to install and reboot.
And I was running CM7. FFFFFF I don't have insurance... Don't really want to take it to the sprint store with S-off.. So i guess ill keep trying to run RUU's... probably wont work though
Click to expand...
Click to collapse
If the pc RUU isn't working, trying using the same firmware RUU, but in PC36IMG file, which you flash in the bootloader.
@plainjane : For those that had the issue on CM7 [some users on MIUI], and they we chalked it up to bad nand blocks? But we still have no 'cure' for it.
teh roxxorz said:
If the pc RUU isn't working, trying using the same firmware RUU, but in PC36IMG file, which you flash in the bootloader.
@plainjane : For those that had the issue on CM7 [some users on MIUI], and they we chalked it up to bad nand blocks? But we still have no 'cure' for it.
Click to expand...
Click to collapse
Does it matter which RUU I use? (2.1,2.2)
reverepats said:
OK......so basically you got no RECOVERY?....so when you boot into the BOOTLOADER to install the PC36IMG....does it recognize the image?.......and does it ask u to install and reboot?......we'll start there
Click to expand...
Click to collapse
Exactly! Do not worry about flashing a RUU at this time. Click on amon RA in my signature to download the PC36IMG.zip for amon RA and place it on the root of your SD card. Remove any other file with that name. Boot onto the bootloader (simultaneously press the DOWN volume & power button until your device starts) and then follow the prompts to install. Installation should take no more than 10 seconds. Afterwards, enter your new recovery, connect your device to your computer, select the USB-MS option and then copy the contents of your SD card onto a folder on your computer. After that, select the USB-MS option again to disengage. Now go to the wipe menu and wipe EVERYTHING it. When you're done, download a fresh copy of the rom you want to flash and flash it or copy a nandroid backup to your SD card and restore it. Be patient, either way, with the initial bootup.
pecking & swyping from my EVO 4G (XDA Premium)
Alright so I tried everything I could... So I took it into a sprint store. Told the guy this happened when doing the most recent update. Right there he went into the bootloader menu, I thought I was screwed... but he didn't say anything about the S-OFF. Eventually I came back and they ordered me another one.. probably a refurb. He said it was going to be free, and I don't have insurance. Guess I got lucky.
Thanks everyone for the input.
I know. It looks like a lengthy read. But all the information you could possibly need I've provided. Please let me know what you think. Also, I've done some searchign around but none of the scenarios I found were a result to flash back to stock sprint RUU.
The error reads as follows: "Attention. A network error has occurred. Retry, or cancel and return to the previous screen."
What actually happens: Anytime I open Marketplace, Facebook app, send a message through KakaoTalk or GroupMe, pretty much anything that uses the 3G, 4G data, it doesn't work. The message only comes up when I try to use the marketplace app. All other apps just say there was a connection error, connecting to the server, etc.
When I hit "Retry" it goes right back to the same dialog pop up, as if it doesnt even re"try". The top notification bar goes from 3G and then disappears, then goes from 3G and just continually disappears. It doesnt matter if I have 4G on or WiFi, it will just goes back to 3G when attempting to gain data, and then disappears and the error happens.
My Timeline of events: I first had been running Synergy and everything was fine. Suddenly my wall charger (or any wall charger for that matter) stopped working when plugged in. The car charger still works, but no HTC wall chargers, odd. So I decided to use that insurance for good and bring it into sprint. Gotta unroot and all that jazz first though. I downloaded the "RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe" and found a way to connect my phone to the PC, and finished the wizard. Mind you, before I did this, I went into recovery (while on synergy) and did a dalvik cache wipe, data/factory wipe and cache wipe, then went back into hboot and ran the wizard from there. Everything went fine, the ROM install was successful, I no longer have recovery and it was the stock sprint ROM.
Where things got fishy...: After it was running through all the constant reboots and things, I let the phone sit while I did other things. I came back to it, signed into my gmail and facebook fine, then went to marketplace. I started downloading all my purchased apps and since that was going to take some time, I let it sit again and went off.
Fishy part: I come back to he phone, and would normally just pull down notification taskbar, and hit clear all notifications, since it said a bunch of things had sucessfully installed, but I notcied it also said "System update complete." Hmmm, I didn't start any system update...did it do it automatically? It had to of. I went to check for an OTA (HTC software update) and it found "System upgrade 1.47.651.1 (30.15 MB) - FOTA update." I canceled it since I pretty sure doing an OTA update on a rooted ROM is a no-no.
So what the heck is the problem here, I never had these issues before until I went back to the stock sprint ROM. I've already updated PRL a few times, does nothing.
Should I go back and reflash it and this time make sure it doesnt do a system upgrade until I've turned S-OFF back to S-ON? Once the phone is S-ON is it safe to update OTA?
My About Phone details are a sfollows:
Firmware version: 2.1-update1
Baseband version: 1.39.00.05.31
Kernal version: 2.6.29-a2443432
Build number: 1.32.651.6 CL171253 release-keys
Software number: 1.32.651.6
Browser version: WebKit 3.1
PRI version: 1.90_003
PRL version: 60683
Any help, advice, suggestions are welcome!!!!! Please hook me up fellas, I'm a little bogged down about the upset.
UPDATE:
Okay. Since I am an impatient person and the last resort was going to re-flash the RUU, I'm just going to do that. And then make sure there is no system update. Once that is done, I'll run the S-ON tool from somewhere, hopefully I won't need recovery for anything, aaand then we'll see where we are. If you're reading all this PLEASE reply with something, anything to let me know somewhere out there is alive! lol, please.
With phone s on and stock ruu loaded it should be fine to accept update...wow u might get froyo lol. And it might help with your data issue...idk much but I know a little.
Edit: maybe try a newer ruu that might help with the data as well. not sure how HTC updates but i think it goes one at a time instead of newest available
Sent from my PG86100 using xda premium
Well the phone is still S-OFF right now, but now that I'm on the stock sprint RUU I dont have a custom recovery anymore, so how am i supposed to flash the unrevoked-forever-son.zip and the PCIMG36 thing!!??! How do I get back a recovery, do I just reflash something like synergy...!?
Here is amon ra recovery. Put on root of SD card and flash in bootloader. http://db.tt/TOsdM52P
This should get u recovery back so u can flash the s on tool. Then run a newer ruu, there is a thread in the EVO dev section with the latest, and hopefully it will also fix your data problems
Sent from my PG86100 using xda premium
gunfromsako said:
Here is amon ra recovery. Put on root of SD card and flash in bootloader. http://db.tt/TOsdM52P
This should get u recovery back so u can flash the s on tool. Then run a newer ruu, there is a thread in the EVO dev section with the latest, and hopefully it will also fix your data problems
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Okay, I downloaded the file, put it on SD card, unplugged it, opened hboot and it tried loading the PC36IMG file, it said wrong image or soemthing like that about 6 times and then went back to the regular screen. Although, it has ALWAYS said wrong image for me, so I'm not worried about that.
So now I just went down and hit recovery and its a no go.
OKAY! Now my phone goes straight to the black screen with a Phone on it, and a little red triable with an exclamation point inside everytime now. It used to only come up when i tried going into recovery. now it comes up everytime i load up the phone. does this mean, its bricked...
EDIT: nvm, I was able to load HBOOT thank god, but still having trouble getting the damn recovery.
Well go to amon ra thread in the EVO dev section and dl th pc36img from there...maybe u got a bad dl...
It's here: recovery-RA-supersonic-v2.3.img - MD5Sum: c00243750cc79e4a1dd4888db175b19f
Sent from my PG86100 using xda premium
Okay, so downloaded the file "recovery-RA-supersonic-v2.3.img", put it (recovery-RA-supersonic-v2.3.img) on SD, turned phone off, and now powering on in HBOOT.
After its finished doing whatever it does, can i go straight to recovery, or do i need to reboot again for changes to take effect?
Well, it did the wrong image no image thing again like it always does, and then i tried going into recovery aaaand it didnt work.
Also u should read these I think:
http://forum.xda-developers.com/showthread.php?t=1151733
How to Unroot Your Phone if Using Unrevoked 3
Or
http://forum.xda-developers.com/showthread.php?t=1245649
***How to unROOT Revolutionary from HTC Evo 4G*** EASY! UnROOT and ROOT! 10/20/11
Depending on which method you used to root your phone..
Sent from my PG86100 using xda premium
Did u rename it PC36IMG.ZIP? Be sure not to name it PC36IMG.ZIP.ZIP Sometimes windows hides extentions
Sent from my PG86100 using xda premium
gunfromsako said:
Did u rename it PC36IMG.ZIP? Be sure not to name it PC36IMG.ZIP.ZIP Sometimes windows hides extentions
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Yyyeeaaah, about that. I forgot to rename it. *facepalm* Just did it, powering in through HBOOT AGAIN. still did the wrong image no image thing, but this time, about it actually did some progress bar thing on the right hand side. but just for a second, and then went back to saying it was the wrong image or no image.
I highlighted the entier file name "recovery-RA-supersonic-v2.3.img" and renamed it to "PC36IMG.ZIP" and then it turned into a zip file. restarted the phone in nboot and didnt work.
Oops I posted the .img for adb sorry here is the pc36img...*facepalm*
PC36IMG.zip - MD5SUM: 6dbb98f9cfa35033982c3803d2520466
Sent from my PG86100 using xda premium
Okay, so check it out.
I ran the "RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_rele ase_171253.exe" before and flashed that, but i remember that i had to unroot my gf's phone back in june, so i went to my downlaod list and saw that i used "RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe"
So I just did that, and the 3G data seems to be fine. [email protected] Now onward to unrooting.
Now that I have stock ROM, do I just run a S-ON tool and fix it? But I dont have custom recovery, wtf this is effing confusing...
gunfromsako said:
Oops I posted the .img for adb sorry here is the pc36img...
PC36IMG.zip - MD5SUM: 6dbb98f9cfa35033982c3803d2520466
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
AH HA! lol, okay cool. So when I download this, and put it on my SD and then reboot into hboot, i'll have custom recovery? and then i can run s-on with 3.70? then eventually update OTA...?
Maybe I am wrong and it won't flash recovery with a non rooted ROM but I thought would because of s-off it should... Should of flashed the s on before u ran the ruu. It's signed with HTC keys and would of been fine.
Sent from my PG86100 using xda premium
gunfromsako said:
Maybe I am wrong and it won't flash recovery with a non rooted ROM but I thought would because of s-off it should... Should of flashed the s on before u ran the ruu. It's signed with HTC keys and would of been fine.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
YOU DID IT! Horrayy!!!! Thank you my kind, kind kind kind sir!
I am on recovery right now. So now do i follow these instructions...
How to Unroot the HTC EVO 4G
◄●REQUIRED DOWNLOADS●►
Unrevoked S-On Tool
PC36IMG
◄●SIMPLE INSTRUCTIONS●►
If you're comfortable with everything Android related(flashing, recovery, etc.) then its just 2 simple steps:
If you used Unrevoked Forever at any time, flash unrevoked-forever-son.zip from recovery until hboot shows S-ON
Flash the PC36IMG.zip from hboot
◄●DETAILED INSTRUCTIONS●►
If you need a little more guidance, follow these instructions.
◄●If you have used Unrevoked forever, start here●►
Make sure you have downloaded the files linked above. Do not extract them
Connect your phone to your computer via USB and change to "Disk Drive" by dragging down from the notification bar.
If you have NOT used Unrevoked Forever, skip to the instructions below. If you have, transfer unrevoked-forever-son.zip to the root of your sdcard. Do NOT transfer the PC36IMG yet. It'll only cause a hassle and make this take longer.
Once complete, power off the phone
reboot into the recovery by holding VOL DOWN + POWER until it boots to the white screen. Then select RECOVERY.
Depending on what recovery you're using, you need to flash a zip. Select the unrevoked-foreverson.zip that you just transferred and complete the flash.
When complete, power off the phone. Reboot into the bootloader by holding VOL DOWN + POWER until it boots to the white screen. If it says S-ON at the top, select RECOVERY and skip to step 9. If it says S-OFF, repeat steps 5-7 Until it does.
◄●If you have NEVER used Unrevoked forever, start here●►
Power off the phone and reboot into the recovery by holding VOL DOWN + POWER until it boots to the white screen. Then select RECOVERY.
Connect via USB. There is an option for this in both Amon RA and Clockwork.
Transfer the PC36IMG.zip to the root of your sdcard.
EJECT THE PHONE FROM THE COMPUTER and then turn off USB in Recovery
Power off the phone and reboot into the bootloader by holding VOL DOWN + POWER until it boots to the white screen.
It should check the PC36IMG.zip and then ask you YES/NO to apply the update. Press VOL UP for YES
Once complete, Press VOL UP to reboot.
You are now unrooted!
Have I ever used unrevoked? idk if i have! where do i start, or do i just run the s-on tool...?
Yes as long as u rooted with unrevoked and NOT REVOLUTIONARY... make sure to remove/rename the recovery pc36img on root of SD...once s on is achieved either run a ruu or the pc36img from that thread...off to kickboxing I go glad I could help...
Sent from my PG86100 using xda premium
How did u root your phone? When did u root it?
Sent from my PG86100 using xda premium
Remember the group of people sometime last year who got into infinite bootloops, with access to bootloader but no recovery?
Yeah. That's me right now. Problem is, I can't remember if we ever found a solution, if anything would work. So I come before y'all for any help
Was running latest CM build before with Tiamat 4.1.0, just shut off during Google Navigation while charging and entered infinite bootloop.
004 Evo
2.18.0001 HBOOT S-OFF
Newest radio, Wimax, PRI, NV
Amon Ra (No access)
It does charge (or says it does - light is on)
So yeah. Access to HBOOT, no access to recovery, still have S-Off. Any help appreciated
tropicalbrit said:
Remember the group of people sometime last year who got into infinite bootloops, with access to bootloader but no recovery?
Yeah. That's me right now. Problem is, I can't remember if we ever found a solution, if anything would work. So I come before y'all for any help
Was running latest CM build before with Tiamat 4.1.0, just shut off during Google Navigation while charging and entered infinite bootloop.
004 Evo
2.18.0001 HBOOT S-OFF
Newest radio, Wimax, PRI, NV
Amon Ra (No access)
It does charge (or says it does - light is on)
So yeah. Access to HBOOT, no access to recovery, still have S-Off. Any help appreciated
Click to expand...
Click to collapse
have you attempted to reflash recovery?
Had this happen the other day and pulled battery and then held power button and volume button down and it went right into Recovery... 1st time ever for me
Just reflashed recovery. Still nothing. Goes into bootloop as I enter recovery.
Note: It does not show boot animation, only splash screen. Just clarifying
Give it some time some times after a crash/hotstart takes a little longer..
Sent from my EVO using XDA App
tropicalbrit said:
Just reflashed recovery. Still nothing. Goes into bootloop as I enter recovery.
Note: It does not show boot animation, only splash screen. Just clarifying
Click to expand...
Click to collapse
Tried a ruu yet?
Sent from my PC36100 using XDA App
evo4gnoob said:
Tried a ruu yet?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Just did. 2.16.0001 HBOOT S-OFF with 2.15.00.0808 radio.
No access to recovery (HTC or custom after flashing recovery)
Same bootloop.
tropicalbrit said:
Just did. 2.16.0001 HBOOT S-OFF with 2.15.00.0808 radio.
No access to recovery (HTC or custom after flashing recovery)
Same bootloop.
Click to expand...
Click to collapse
might need to wait till Captian_Throwback gets online he'll probably know a way to fix it. He fixed his when he got bricked by TWRP
No, there never was a solution, other than the doc I attached, which may not work and again.. someone running CM get's this Boot Loop issue....
evo4gnoob said:
might need to wait till Captian_Throwback gets online he'll probably know a way to fix it. He fixed his when he got bricked by TWRP
Click to expand...
Click to collapse
Nice of you to think of me!
Umm, yeah . . . my problem was a little bit different, as I was still able to boot into a ROM. So, any suggestions I offer here will be purely theoretical. But, perhaps the same fix will apply. Maybe the misc partition needs to be "reset"? Since you have access to fastboot, we'll need you to flash a bootloader version where fastboot commands will work. Since you have a hardware 0004, I think 2.18 is the only option. Get that from here: PC36IMG_HBOOT_2.18.0001.zip (flashable via bootloader). You'll also need to download the "mtd-eng.img" file from toast's thread here: mtd.eng.zip, and you'll need the fastboot.exe from the Android SDK.
After you get the 2.18 HBOOT flashed, select fastboot to get into FASTBOOT USB mode. I assume you already have the fastboot drivers installed on your computer, so I won't get into detail on that.
Put the mtd-eng.img in the folder with fastboot and open a command prompt. Navigate to that folder and issue the commandEDIT: I just tried this and it didn't work. I think you're going to have to go with the above method . It was a good ol' college try, I guess.
Code:
fastboot flash misc mtd-eng.img
It should flash successfully, since you're S-OFF. Once that's done, try rebooting the bootloader, and see if you can get into recovery.
The mtd partition seems to be the thing that messes everything up, so I figure that's the best place to start and see if it's that easy to fix .
EDIT: I guess if the above doesn't work, HipKat's method will be the next thing to try. I don't envy you if you have to try that . . .
Captain_Throwback said:
Since you have a hardware 0004, I think 2.18 is the only option. Get that from here: PC36IMG_HBOOT_2.18.0001.zip (flashable via bootloader). You'll also need to download the "mtd-eng.img" file from toast's thread here: mtd.eng.zip, and you'll need the fastboot.exe from the Android SDK.
After you get the 2.18 HBOOT flashed, select fastboot to get into FASTBOOT USB mode. I assume you already have the fastboot drivers installed on your computer, so I won't get into detail on that.
Click to expand...
Click to collapse
I get the error attached below in attachments, fails to write. I am up to 2.18.0001 HBOOT S-OFF with the HBOOT you included
HipKat, the RUU is downloading. The Evo Softbrick.zip link you have in there leads to me to: "The file link that you requested is not valid."
very simple
reflash by doing adb push update update.zip then format sd
by adb mount/sdcard
then adb erase sdcard
then do fastboot flash update update.zip
erase all data
then should be good to go.....
thats how i fixed mine
HipKat said:
No, there never was a solution, other than the doc I attached, which may not work and again.. someone running CM get's this Boot Loop issue....
Click to expand...
Click to collapse
I just ran the RUU, that is all I've done because of the down link. I'm now at 0.79.0000 HBOOT S-OFF with 1.39.00.0426 radio. Now whenever I turn on my phone it goes straight to bootloader. Entering recovery gives me 5 vibrations with notification light blinking green
Edit: It no longer goes to bootloader whenever I turn it on. It gives me 5 vibrations with blinking green notification light. Still have access to HBOOT
That means it's in maintenance mode. As for that document, it's s few months old.maybe you can do a search for that missing file.
Swyped From The Hippest MIUI'd phone Using XDA Premium
I now have HBOOT 2.10 ENG S-OFF (Hex-edited one from here). So I have fastboot command capabilities. Trying to flash mtd-eng.img gives me the attached error.
Going to start searching for that file. I have fastboot capabilities, so I think I need the nv.img so it's time to go hunting
Edit: So I had HBOOT 2.10 ENG S-OFF. I followed the document HipKat posted, was unable to erase nv, microp, and radio. I flashed nv.img, then I ran the RUU again.
Back to .79 HBOOT S-OFF. Turning the phone on vibrates it 5 times and flashes green light. No access to recovery either.
Starting to think we are out/almost out of options... Guess it is time to start talking about getting S-On with somewhat recent HBOOT and radios.
you don't have to get S-on. If all it does is go to that Maintenance Mode, then just take it to Sprint. They'll probably replace it
HipKat said:
you don't have to get S-on. If all it does is go to that Maintenance Mode, then just take it to Sprint. They'll probably replace it
Click to expand...
Click to collapse
I can still access HBOOT, however. I have a couple of friends at the local Sprint store (due to a Samsung Intercept for my sister - worst phone ever). The problem is, several of the managers there check the HBOOT. They've checked it in front of me (I had S-On) and for recovery on the Intercept. When I asked why they checked, they said they support repairs but not replacements (could go through Asurion) with rooted devices.
Sent from my SPH-M900 using xda premium
Wow, that's the first time I've seen that someone at Sprint checks for Root.
HipKat said:
Wow, that's the first time I've seen that someone at Sprint checks for Root.
Click to expand...
Click to collapse
They do check them. I had mine checked the two times I needed service. Last time they even updated the phone to the latest 4.67 update without consent.
atapia984 said:
They do check them. I had mine checked the two times I needed service. Last time they even updated the phone to the latest 4.67 update without consent.
Click to expand...
Click to collapse
I've seen so many posts about Sprint doing updates without consent. If you ask them to not do the update, they ask questions.
Well, I shall search for a way to get S-On with no access to recovery; I'll continue flashing to see if I can get something to stick before that though. My fallback plan is a Samsung Moment I have sitting around...
Hello all,
A friend has bought a DHD online and it came from Asia (CID 44)
He tried to downgrade using a guide found here but he forgot to read the small print that syas that you must not use this guide if you were in 3.xxx
SO now the phone appears to have its bootloader damaged, and I'm trying to bring it back from zombieland
When I press start nothing happens, after 5 minutes (yes 5 minutes) the phone lights, white HTC screen, no text, after 2 minutes it starts vibrating for 5 minutes and then the vibration stops and I am left with the white screen, greeen HTC, NO "quietly brillant" and nothing happens, I've left it like that all night but it does not go further.
What can i do to solve this ?
Thanks a lot
The Advanced Ace Hack Kit (AAHK) will be able to restore the correct bootloader (fingers crossed). Look up it's thread in the DHD development section.
Sent from my Desire HD using xda premium
Well i've benn asking questions in this thread but i got told that it was not an aahk problem (which is right) and that i had to solve my bootloader issue first....so here i am
Thanks
Update :
If i remove the battery, then power and hold vol down (for about 12 minutes....) I get to the bootloader screen...BUT it is inactive and locked on fastboot
I have now
ACE PVT SHIP S-ON
HBOOT-0.85.0007
MICROP-0438
RADIO-26.03.02.26_M
eMMC-boot
Oct 11 2010,12:47:02
HBOOT
and then the usual vol up, vol down and the choices
fastboot (on which I am stuck, vol up, vol down and power have no effect)
recovery
factory reset
simlock
image crc
I've tried to use adb shell to see if I could get the control over it but I get a "device not found".
What can I try now ?
Thanks
What I meant was that AAHK has an option to flash the correct bootloader. The bootloader you're running is an old one. If the device was shipped with Froyo then you should have the 0.85.2007 bootloader. If was shipped with Gingerbread then it should be 2.xx.xxxx bootloader. Try installing the correct bootloader using AAHK (there's an option for installing ENG S-off bootloaders for both Froyo shipped devices and GB shipped ones.
Sent from my Desire HD using xda premium
The trouble is that AAHK cannot access the phone since it is blocked BEFORE sense and so on, so when i run AAHK version from 12/06 I get told that phone is not plugged, or driver is not installed or USB debugging is not enabled, and of course they are all running.
So i need to unblock the phone in "manual" mode and then I'll be able to run AAHK or make a goldcard or whatever....
Thanks for the help
Can you boot into hboot menu?
Sent from my DH eriseD CTH With Dolby Mobile using XDA
Ok, what about flashing an RUU? Have you tried that already?
Sent from my Desire HD using xda premium
sashank said:
Ok, what about flashing an RUU? Have you tried that already?
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
that helped me 3 times
Sent from my DH eriseD CTH With Dolby Mobile using XDA
I can boot into fastboot menu but then it is locked. See the first post, it's like the phone is super super super slow, and when i get to the fastboot menu it does not respond at all, or maybe it would respond in a super slow way.
Assuming I have control over it what am i supposed to do when i get to fastboot menu ?
Flashing the RUU seems a good idea, but which one and where do i get it ?
Thanks a lot
You said the phone came from Asia right? Then this is the latest RUU for Asia WWE (World Wide Edition) - RUU Ace Asia WWE 3.13.707.4
It's from http://www.shipped-roms.com which has collections of RUUs for many HTC devices.
noob question - can OP flash the 1.32.405 RUU directly instead of 3.13.707?
k1p2n3g4 said:
noob question - can OP flash the 1.32.405 RUU directly instead of 3.13.707?
Click to expand...
Click to collapse
That's essentially what caused the problem. 1.32 is froyo based. Devices shipped with gb should not install a froyo boot(eng soff) or downgrade to a froyo based ruu/pd98img. The op best bet at this moment is to flash a pd98img that's meant for his phone. I don't think the ruu will recognize the device in its current state. Will say though that it will take forever to flash bit eventually will.(I believe its 30+ min)
What I would try is put phone in boot then run
Fastboot erase cache
Fastboot oem rebootRUU
Fastboot flash zip xxxxx.zip (xxxxx being the name of your pd98/rom.zip
Sent from my Inspire 4G using xda app-developers app
Thanks a lot, I'm getting the RUU right now and I'll try tonight.
So I Boot with volume down, get to the main menu (after the 12 mins HTC logo time and the 5 mins vibration time) and then try to access the phone by adb shell and fastboot erase cache and so on ?
Sorry for the stupid questions but it's the first time (and hopefully the last) that I do this.
Thanks.
Correct. To take out the rom.zip from the ruu. Simply run the ruu first two steps, then go into your temp folder and look for it. The place it in your fast boot folder.
You can try just running the ruu while in hboot. Usually this works but with a damaged boot loader i believe its gets stuck at waiting for bootloader
Sent from my Inspire 4G using XDA
ok, thanks, I'm in the "power+vol down" boot mode, the entry is on "fastboot" (it is higlighted in color) but nothing happens when I press power (or vol up or vol down)....
What can I try ?
Thanks
. Its going to be a long process. But from that screen plug in your phone and try the fast boot commands
Sent from my Inspire 4G using XDA
So here's the update
I renamed the rom.zip which i extracted from the RUU to PD98IMG.zip and put iut at the root of the SD card...
I rebooted the phone (long time), got in the fastboot screen, nothing happened, tried to use the dos commands (fastboot erase cache), got the "waiting for device" message in the dos windows....
I got fed up and went for diner leaving the phone as it was, I just came back and now I have the green message "checking [PD98IMG.zip] and so it looks like it might be a good sign, I'll leave it plugged on tonight and see what happens....
More to come in 8 hours
Thanks for the help
Ok, got it running
So here's the procedure in case someone else has the same problem.
1) Find the RUU you need to go back to what you had before, in my case it was the 3.17 asia
2) Get the rom.zip from this file : start install and when it tells you that it is not possible go to your my documents/user/local files/temp folder, sort the folders by DATE so that you have the latest used on top and open it, in this folder there will be the rom.zip file
3) Rename this rom.zip file to PD98IMG.zip, send it to the root of the SD (best way is to get the SD out of the phone and do it from the computer)
4) Launch the phone in recovery (power and then hold VOL DOWN) the phone will ALWAYS try to check PD98IMG.zip and if it checks it will ask you if you want to install it, just say yes (for me it took all night)
5) when you're back to your latest rom, you can use the aahk, for me I had to run it 2 times but in the end it it S-OFF and then install whatever rom you want.
Thanks to everybody who has helped me on this
my last rom build number is 1.32.405.1 , which rom i must choose ?