Hi Guys, I posted this in Android Software and Hacking General, but I didn't get a reply. Probably the wrong section!
my HTC Desire GSM is stuck in Fastboot and won't boot into the ROM. The background to this issue is that I installed S-Off and then ClockworkMod and flashed Cyogenmod 7 to see if it would fix a reboot issue on the phone. The damn thing just reboots itself when the CPU is used heavily...
Anywho, after realising that Cyogen wouldn't resolve the issue I flashed the standard Virgin UK rom back over it and upgraded to 2.22.351.2 via the system update feature. The problem was that ClockwordMod was still installed and I had to get rid of it to sent the phone off for repair to Virgin!
So I did further research and found that I could flash HBoot via the AlphaRev.nl downgrader tool. I downloaded it and popped it into the root of my SD card and it flashed the bootloader back to Hboot 0.80.0000. That should have been it, but all of the sudden the phone no longer boots into the Rom. All it does is to power on and then go into Fastboot. That's it! When I try putting the standard Virgin Rom back onto the SD it tries to load it and then says "Main Version is older!" "Update Fail!".
How do I get around this now? The phone doesn't boot, so I can't re-flash S-Off and start again, not am I able to run the stock Virgin Rom within Windows because it complains about the versions.
Is there any ways around this situation? I just want to get the phone back to stock so I can send it to Virgin and get it repaired.
P.S. I *have* used the search function and spent the last 4 hours testing various things but I'm now stuck.
Cheers Guys!
Mich
Well you obviously fckd up with the Downgrader, you should have run it first BEFORE RUU. Also did you flashed Stock Hboot prior to Downgrader? (if you used CM7 earlier)
I never played around with the hboot downgrading etc. so i wont be able to help you but im sure there is some workaround...
as your returning your phone anyway why don't you try the official HTC gingerbread update from the HTC developer site (sorry I don't have a link). It should return your phone to stock and when you get it back you need to use revolutionary to get s-off back. Also, there is a sticky from user bortac which has loads of help and trouble shooting advice.
iain2510 said:
as your returning your phone anyway why don't you try the official HTC gingerbread update from the HTC developer site (sorry I don't have a link). It should return your phone to stock and when you get it back you need to use revolutionary to get s-off back. Also, there is a sticky from user bortac which has loads of help and trouble shooting advice.
Click to expand...
Click to collapse
Any advice that uses the 2.3.3 RUU to fix something is plain bad advice - it can just make your problem a LOT worse.
@OP Go onto my guide, look at RUU problems for help
What you need to do:
-Make a goldcard (there is a tutorial there)
-Flash the WWE RUU
Guys, upgrading to Gingerbread has actually brought the phone back from the dead! =) And I can now return it to Virgin to get it repaired properly. The symptoms are that while the phone is plugged in and charging, and I'm doing stuff (taxing the CPU), the phone will eventually simply rebooting itself. Just *BANG*! And it's gone. And once it starts it's a bit of a run-away thing and just keeps on doing it until you leave the phone alone for a bit. Virgin had a look at it and simply re-flashed it, thinking that they could away with that. Typical, overworked, non-creative call centre workers..... I'm well pissed off with them!
Gonna send it back next week and force them to swap the motherboard or something, cause this is a serious fault with the phone.
Related
Hi guys, I'm at the end of my tether now!
My phone kept rebooting when using Navigation yesterday, then after the 3rd time it has just been stuck on the HTC boot screen and nothing will fix it.
I can't even get into recovery, so I cant do a nandroid restore.
I have been using Leedroid 2.2e with no problems before this.
I have tried flashing the latest RUU but because I had the latest Froyo already installed it wont work as it needs to be an older version on the phone.
I cant downgrade Froyo to an older version as I cant get into the phone to turn on USB debugging.
I have only had the phone 2 weeks, please help if possible.
If you use the 2.10.405.2 or 2.29.405.2 RUUs they should flash with no issues. Might be worth extracting out the ROM.zip from the RUU, rename it PB99IMG.zip, copy it to the sd card and go into HBOOT and it should revert back to stock (assuming it can read the card)
I tried flashing the 2.10.405.2 RUU but it fails halfway with a Customer ID error, and I know the goldcard is good so I thought it must be failing the check for older software version.
I also tried renaming and flashing the rom from the card, but the phone read the file and a progress bar went up the right hand side of the screen, then nothing, it just stopped.
I'm not really clued up on these things, but I have been doing a lot of reading on various forums.
Hey EddyOS, thanks for the heads up on the 2.29.405.2 RUU, that was what I needed to flash over my current rom.
All back and running now, after being up all night trying to fix it.
I'm scared to root and put a custom rom on now in case it happens again and I have to send it in for a warranty repair, that was my biggest worry.
Thanks again!
I've searched the forums and have not found a situation that really matches mine.
I've been running on a Cyanogen nightly build for probably two months with no problems. Out of nowhere this morning my phone reboots itself (while it was idle; I wasn't even touching it) and then gets stuck in a boot loop. I get the White HTC Evo 4G screen, then it powers off and comes back up to the white screen again. Over and over.
All I can get do is hboot. Even telling hboot to go into the recovery mode puts my back into the boot loop. Fastboot, clear storage, and hboot usb all seem to work though. I've tried downloading the PC36IMG.zip file (http://forum.xda-developers.com/showthread.php?t=780141) in that thread, but hboot loads it and tells me that it is older than my current version, and only gives me the option to reboot, or not to reboot. Doesn't load the image.
Here is the information on my hboot screen:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.97.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Aug 19 2010, 14:29:08
Anybody have any ideas? Thanks!
you lost root, s-on
you can still start the bootloader so it's not a brick
need to get s-off before you can load recovery again and reflash your rom
have you tried the RUU? if it installs and defaults you then you can unrevoked to root
NewZJ said:
you lost root, s-on
you can still start the bootloader so it's not a brick
need to get s-off before you can load recovery again and reflash your rom
have you tried the RUU? if it installs and defaults you then you can unrevoked to root
Click to expand...
Click to collapse
Trying the RUU here now: http://forum.xda-developers.com/showthread.php?t=874091
Wish me luck!
luck has been wished
Kuhmo said:
Trying the RUU here now: http://forum.xda-developers.com/showthread.php?t=874091
Wish me luck!
Click to expand...
Click to collapse
This didn't work. Everything is still the same, except that my hboot version is now 2.10.0001. Any other thoughts?
still won't not into any rom? did you get errors?
NewZJ said:
still won't not into any rom? did you get errors?
Click to expand...
Click to collapse
No, the app on the PC said everything was successful. The progress bar on the phone progressed without errors too.
what happens when you reboot the phone not going into bootloader?
Just the HTC EVO 4G splash screen. Over and over and over...
does it show the boot animation or just stuck on splash?
Just the splash. No animation.
pull the battery, remove your sdcard, put the battery back in, see if it gets to the animation
Doh, you upgraded your hboot. It's alright though, just run the ruu one more time and your should be ok
Sent from my PC36100 using XDA App
Wrong button..
xHausx said:
Doh, you upgraded your hboot. It's alright though, just run the ruu one more time and your should be ok
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I asked my wife to check this thread from the car on the way to dinner. Saw the response. So I took my laptop inside with us and used the RUU one more time. No luck. I decided that it must be a hardware issue. I took the SD out and removed the evidence that the phone had been rooted, then took it to the sprint service center up the road. They just replaced it for me. Thanks for your time! I DO want to root my phone again, the ROMs are just so much better than the stock installation. Should I not install the OTA updates if I'm going to root it? Which guide should I follow for rooting?
never do OTA when rooted, use unrevoked to root, unrevoked.com
NewZJ said:
never do OTA when rooted, use unrevoked to root, unrevoked.com
Click to expand...
Click to collapse
Not when rooted. I meant should I update to the latest OTA UNTIL I decide to do the root again? Is the latest OTA unrootable?
Same deal.
Here is the post that I put in the wrong forum that I was about to post here until I saw this thread...
Wellp. I win.
I win a no expenses paid trip to my nearest Sprint dealer.
Ever since I used unrevoked to root my phone in November, I've been voraciously digging through these forums for tasty roms. I've been snorting lines of Cyanogen, MIUI, and a myriad of other, well-designed roms.
Using a on older version of hboot (pre 1 methinks) I was able to avoid the latest hassles with ClockworkMod (plus, I down(up?)graded to 2.6 via RomManager).
Tonight, as I was enjoying some tasty foodstuffs at my local foodstuff vendor, my phone rebooted. Then, it rebooted again. Then again. I once made the folly of flashing a new rom without running the appropriate wipes, and was no stranger to the bootloop. I patiently fired up hboot (my poor volume rocker is all but wore out) and ordered up the trusty recovery mode.
...then it rebooted again... and again... and again.
PusSidiasus: ONOES! I HAVE THE WTFBBRICKED MY PRECIOUS!
SmartAsSidiasus: Hang on for a second, let's check the internet. Try this link: tinyurl.com/4vgeyeg
PusSidiasus: ...
Unfortunately, my internal dialogues are not nearly as witty. Also, my best attempts to de-brick-ify were for naught. Fastboot gave some wacky error message when I tried to flash a new recovery, and installing via PC36IMG.zip did nothing to improve the situation. I even went so far as to install a stock image someone pulled from an RUU (with a 2.02hboot, so as to avoid wimax woes)...
Still, a whole lotta nothing. I can't do anything beyond hboot, and whatever recovery image I install (Clockworkmod, AmanRa) the machine still bootloops.
At this juncture, I've resigned to taking the phone into the sprint store and playing dumb. It is a stock rom, though I hope the attendant misses the S-OFF bit at boot. Which brings me to my proper question:
1) Has anyone run aground a similar issue and found a way out?
OR...
2) Anyone know how to turn S-(back)ON in my current situation?
Any insight would be greatly appreciated. Also, you can rest assured that I'll be rooting again whatever phone I walk away with, and the work that is exhibited in these forums is amazing. Keep churning out wonderful roms and guides.
Sidiasus
(Currently, Sadiasus... )
run the ruu to s-on then trade for another
NewZJ said:
run the ruu to s-on then trade for another
Click to expand...
Click to collapse
Ack, sorry... didn't mention in previous post. I fired up windows to run the RUU (I don't trust wine to that stuff) but it couldn't detect the device.
I know theres probably a thousand topics on this but none of them seem to have the same exact problem or they do and dont have a solution. I can boot my ROM and i cant boot recovery. the only thing i can get to is HBOOT. I have tried many of the PB31IMG.zip files but none of them work. i have also tried the RUU exe program but that did not work either. im kinda graspin at straws here cuz i dont have a phone right now. im also wondering if i should just take it to verizon, but with that im worried about them finding out its rooted, because it still says "S-off" on the HBOOT menu. Any suggestions on what to do?
To my knowledge if you are in a bootloop with no secondary recovery such as Amon-Ra or CWR, the only other option is the RUU downgrade your Inc through the Android HBOOT Recovery. Use these guides here:
http://www.droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html
I have tried that exact process, both options, to no avail...thanks though. Is there any way to revert S-Off back to S-on through HBOOT?
gdaysoccer said:
I have tried that exact process, both options, to no avail...thanks though. Is there any way to revert S-Off back to S-on through HBOOT?
Click to expand...
Click to collapse
For whatever it's worth, my phone was s-off when I took it in to Verizon. (I was having the vibrations-of-death)
They saw the phone wasn't booting up, and even saw my unrevoked splash screen, and that was good enough for them to send me a new phone.
Honestly, I don't think a majority of those sales reps would even know how to get into hboot, and really don't know a whole lot about Android. I'm not saying it'd be impossible to get someone that lurks XDA in their spare time, but... it's unlikely.
And if they did lurk xda they probably wouldn't make an issue of you being rooted
Sent from my ADR6300 using XDA App
I actually just had the same issue as you and spent around 21 hours trying to get things fixed with a few devs and we had no luck. basically the phone would act as if it would take the ruu flash and claim it did and update the hboot like it did but made no change in order to complete a boot cycle. I had no recovery no rom just hboot and fastboot worked. every other option failed. we chalked this up to a hardware failure of some sort. I flashed the lastest Ruu and called *611 explained the problem and they overnighted me a new inc. I still have S-off on the phone but every other item radio/hboot/kernal is all stock. I doubht they wil lreally notice the S-off. all in all the phone is back to stock full wipe. Good luck.
I ended up taking it to the Verizon store today and the rep thought it might have been the battery so he tried a new one of those, but that wasnt the issue. I'm pretty sure he booted into HBOOT because he was playing around with the power and volume buttons, but he didnt ask me anything about it being s-off or rooted or anything and so theyre sending me a new phone, because unluckily they didnt have any in stock at the store i went to, and i have to send this one back. So, so far, it looks like no one really cares or even knows where to check for it being rooted.
Hello everyone, I'm running into a bit of a problem here with my sister's HTC EVO 4G.
You see her phone is a remanufactured replacement model from Sprint, and naturally it has a few minor problems with it. She wasn't thrilled with the battery life, so I rooted and flashed CM7.1 on her phone. She liked the rom and liked the extra battery life after I did some tweaking. Two Months later, for some odd reason, her phone will not connect to the data network at all. I flashed CM 7.2, same problem. Contacted sprint, where they refreshed the signal to the phone, no luck. So I concluded that it was a hardware error. Problem is, Sprint won't work on the phone without the Stock Sense Rom installed. I thought: "No big deal, I'll just flash it back to the stock sense rom" right? WRONG.
Never have I ever been so enraged by a cellphone. No matter what I do, no matter what I try, this phone absolutely REFUSES to go back to the stock rom. I've tried flashing several PC36IMG.zip files from the sdcard in HBOOT, and I have also tried several RUU updates from my PC while having the phone in Fastboot USB mode.
Quick Info:
Phone: HTC EVO 4G
Baseband: 2.15.00.12.19
HBOOT: 2.18.0001
Bootloader = Unlocked
Security = ON (S-ON)
Trying to flash PC36IMG.zip from HBOOT results in the phone loading the zip (with the little vertical progress bar on the side) and after loading completely, it just goes on it's merry way, checking for any other zip files and then HBOOT loads normally.
Running the RUU .exe files on my computer goes smoothly right up until somewhere in the update progress I get Error 155 (Unknown Error).
Now, it's my understanding that I don't need S-OFF to go back to the stock Sense rom, but I figured I should try to get S-OFF anyways. So I downloaded unrevoked and try to apply it from CWM, and it fails stating that it's not compatible with my radio version. Funny thing is, in all the radio lists for the HTC EVO 4G, I don't see 2.15.00.12.19 anywhere. In fact, 2.15.00.08.08 seems to be the newest one, unless I'm reading the lists wrong.
Either way I'm completely stuck here, and now I have a whining teenage sister screaming at me because she doesn't have a phone on a friday night. Go Figure.. Please guys, I know I'm a noobie here, but do me a solid. Please help me out, I'm stuck, frustrated, and I'm getting to the point where it's time to crack open a beer or 3 and say "f**k it".
Thanks in advance,
Alcolawl
you dont need s-off to return to stock..try the guide below in my signature to unroot and return to stock
XenonV said:
you dont need s-off to return to stock..try the guide below in my signature to unroot and return to stock
Click to expand...
Click to collapse
Does it matter which RUU version I download? (I've been extracting the rom.zips from the RUU's temporary files). I have the most current one on my computer named: "RUU_SuperSonic_GB_Sprint_WWE_4.67.651.3_Radio_2.15.00.12.19_NV_2.33_release_234563_signed". I usually take the Rom from that, rename it PC36IMG.zip, place it on a freshly formatted sdcard, and reboot into bootloader and hope for the best.
well, if you want the bootloader to be returned to factory stock settings then you can follow the guide below, BUT if you just want to UN ROOT, just copy a stock rom like the one you named, and flash it thru RECOVERY menu (install zip from sd card), dont install it from the bootloader (white screen)
XenonV said:
well, if you want the bootloader to be returned to factory stock settings then you can follow the guide below, BUT if you just want to UN ROOT, just copy a stock rom like the one you named, and flash it thru RECOVERY menu (install zip from sd card), dont install it from the bootloader (white screen)
Click to expand...
Click to collapse
Sounds easy enough. While messing around and waiting for Dominos to arrive, I decided to flash MikG (first time doing so, so I wasn't sure what to expect). Lo and Behold, I updated the PRL and Data Profile, and her Data works again. She also likes how Sense looks more so than CM7. Aesthetics > Functionality in her book I guess. If it comes down to having to bring the phone to the Sprint store, I'll try flashing the image through Recovery instead of Hboot.
Thanks for the help man, really appreciate it.
Alcolawl said:
Sounds easy enough. While messing around and waiting for Dominos to arrive, I decided to flash MikG (first time doing so, so I wasn't sure what to expect). Lo and Behold, I updated the PRL and Data Profile, and her Data works again. She also likes how Sense looks more so than CM7. Aesthetics > Functionality in her book I guess. If it comes down to having to bring the phone to the Sprint store, I'll try flashing the image through Recovery instead of Hboot.
Thanks for the help man, really appreciate it.
Click to expand...
Click to collapse
no problem :good::fingers-crossed:
Incrediblec XD ship S-On
Hboot-0.92.0000
microp-0417
touch panel-atmelc03_16ac
Radio-2.15.10.07.07
Jul 23 2010, 18:06:51
Hello, first thank you for an amazing and current forum, I'd been researching my issue for a while, but most things are dated around 2010. I've experience rooting and ROMing a Droid X with multiple ROMS, but I use the original Incredible as my main phone because I still love it. Well, I originally rooted my Inc with Unrevoked3 I believe. I left the ROM as stock up until a couple months ago when I put CM7.2.0 on it.
About a week ago, the phone would always have working mobile data. Yet, if I received or tried to make a call, I couldn't and then I would lose texting ability. Then, a couple days ago, I was using the Inc for wifi tethering when suddenly it went into an Incredible bootloop. I tried booting to the cyanogen recovery, but it will quickly loop out of it as well.
I went to pvillecomp.com/ and downloaded all the stock Inc software. I individually renamed files to PB31IMG.zip and tried to have HBoot pick up on them. Hboot will see the files, but then do nothing. Except, the originally ROM will get checked and come back and say that the current version is older and can't be flashed.
I've always tried the RUU software for hboot and the original ROM. I either get a usb error or a low battery error even if the battery is charged. Granted, I'm trying the RUU from the phone's bootloader screen.
Does anyone have some support they could throw this way? I use my phone for internet and everything. Thank you all.
-Nevin
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
did you flash any radios? Flashing radios always ends up bad.
NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.
I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
123421342 said:
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.
Click to expand...
Click to collapse
Btw, no I didn't flash the radio. That was the only thing I didn't attempt to flash. Yet, when attempting to flash anything else, nothing worked. Still wondering about getting S-off before using TWRP, but hopeful to still get it working. Thank you again.
NevinInc said:
I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
Click to expand...
Click to collapse
BUMP/UPDATE:
Yes, I'm still at it trying to get my Dinc out of it's bootloop and up/running. It's difficult at this point to say what all I've tried. At one point I wanted to use htcdev.com to ensure the bootloader was unlocked/etc. I've had much trouble trying to get fastboot to work correctly on my pc. I've seem to get stuck on "waiting for device" which appears to be a driver error.
I gave up on that and started focusing on the RUU process. I've tried to install the entire Gingerbread 605.3 file. I fixed the error usb 170 by updated or changing htc sync software. Now I'm left with error 140 bootloader error.
I've also updated hboot using the ruu process for version 605.2. This worked on my pc and got me partially excited. Now my hboot shows up as "Locked" now at the top. I also downloaded a different Stock.img file. Hboot detected this and begun the install process. Everything came up as complete and upon reboot went right back into the white screen/incredible bootloop.
So since posting before I've updated htc sync on my pc and have officially relocked my bootloader. I don't mind RUU'ing things to stock, but now gotta get past the Error 140. Any ideas?
So I'm not sure how many are looking at this or have had ideas, but I was able to use htcdev to unlock the bootloader.
Before unlocking the bootloader I was able to RUU to image .15. After this is when I unlocked the booloader. The RUU said it was complete, but I still only bootloop on the incredible white screen. Now, some of the pb31img.zip files I've come across don't even try to install. This includes signed and unsigned .15 img files. Currently these are the new settings to the phone:
Bootloader: unlocked, s-on
hboot 1.07.0000
radio - 2.15.10.12.20
Image version: 4.08.605.15
The last option I can think of is to try using fastboot, but won't that essentially do the same thing? If you think fastboot is the way to go, can u link me or give me some basics on using it. Obviously I used it for unlocking the bootloader so it can't be that complicated.
Are there any other ideas or should I give up on my Dinc? Looking forward to hear what you think. Thanx.
-Nevin
somebody recommended you install TWRP and install a stable Jellybean ROM. Did you try that?