Hey all,
***ISSUE*** I can only boot into recovery or a ROM once. ***ISSUE***
I recently replaced my EVO through Sprint, and rooted. (unsuccessfully with unRevoked, but successfully with AutoRoot). After I used unRevoked (but before using AutoRoot) this issue started popping up.
I can flash a recovery image via Bootloader/Hboot or PARTICULAR ROMs, Sprint Lover's seems to be the most reliable, CM7 does not seem to work at all, and be able to access them once, and upon reboot I get the white "htc EVO 4G" screen and it hangs there until I reboot. Once that happens I cannot access recovery or boot into the ROM until I reflash from a PC36IMG.zip in Hboot/bootloader.
Here's my hardware info:
SUPERSONIC EVT2-3 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.11.19
Hardware Revision #3
My Evo was originally on HBOOT 2.10, but I flashed an eng-PC36IMG.zip that let me install the ENG bootloader on it, which has made it so things flash more reliably.
Anyone have any advice? It seems really odd to me that software would work once and not again. Any suggestions would be appreciated.
There could be something from the rooting process that's affecting your phone somehow, although that's really strange. I would suggest unrooting, getting fully back to stock, & rooting again. If you're not going to be able to reboot your phone without reflashing, which seems like a pain, it might be best to redo it.
Other than that, I'm baffled :/
Sent from my badass HTC Supersonic (Evo 4g) using XDA Premium App
Thanks for the reply, plainjane!
I am in the process of unrooting now to see if that works. I installed the unrevoked-son via ClockworkMod Recovery 3.0.0.5, but I still had S-OFF when I went to HBoot. I'm not sure, but I think I remember somewhere that the ENG bootloader does that.
Regardless, I'm installing the latest (3.70) RUU now and will see what that does.
RandomViolence said:
Thanks for the reply, plainjane!
I am in the process of unrooting now to see if that works. I installed the unrevoked-son via ClockworkMod Recovery 3.0.0.5, but I still had S-OFF when I went to HBoot. I'm not sure, but I think I remember somewhere that the ENG bootloader does that.
Regardless, I'm installing the latest (3.70) RUU now and will see what that does.
Click to expand...
Click to collapse
Yea, im pretty sure the. 76 eng hboot is permanently s off. Also, I was unaware that hboot version 2.1 was downgradeable, I thought it wasn't able to be changed. Interesting. Maybe that's part of your problem, im really not sure. Sounds annoying though. Hopefully unrooting and starting fresh will help.
Sent from my PC36100 using XDA App
Thanks for the reply k2buckley!
I've now run the S-ON tool and used the 3.70 RUU to unroot my Evo. After the RUU completed its process my EVO rebooted and has not left the white "HTC EVO 4G" screen. (EDIT: I checked in Hboot and am now S-ON and on the 2.10 bootloader.) I've let it run for about ten minutes now and I'm not hopeful.
Now that I have it in a state where I can return it to Sprint I don't think I'm going I'm going to mess with it any more. It's such a shame. My first Evo was wonderful until an odd software glitch bricked it, and now this. It's been a really frustrating couple of weeks.
After this experience I don't think I'll be using unrevoked again. I loved having the speed and features of CM7 on my first Evo, but I'm debating rooting at all at this point.
RandomViolence said:
Thanks for the reply k2buckley!
I've now run the S-ON tool and used the 3.70 RUU to unroot my Evo. After the RUU completed its process my EVO rebooted and has not left the white "HTC EVO 4G" screen. (EDIT: I checked in Hboot and am now S-ON and on the 2.10 bootloader.) I've let it run for about ten minutes now and I'm not hopeful.
Now that I have it in a state where I can return it to Sprint I don't think I'm going I'm going to mess with it any more. It's such a shame. My first Evo was wonderful until an odd software glitch bricked it, and now this. It's been a really frustrating couple of weeks.
After this experience I don't think I'll be using unrevoked again. I loved having the speed and features of CM7 on my first Evo, but I'm debating rooting at all at this point.
Click to expand...
Click to collapse
If you do, root it manually - save yourself from all these headaches of the autoroot programs.
Thanks for the advice Heaterz16!
I'd love to root manually to ensure everything goes well. The guide that I saw indicating how to manually root was taken down and linked to AutoRoot as the way to go. Could you point me towards a guide for manual rooting?
Take it back to Sprint. I had one that would rarely boot, it would take 20 or so tries. When it finally did boot, the screen would freeze up & I'd have to pull the battery. They gave me a new one, no questions asked & I had it the next day. That phone was never rooted, it was only two weeks old. I have insurance, so all of my replacements have been free. I had the one before that 3-4 weeks before the usb port gave out. I got my third one three months ago, rooted it, and have had no problems since. I hated the Evo for about a month when mine kept breaking.
I would also suggest manually rooting. The "one-click" methods are easy to do but difficult to troubleshoot. Manual methods are a little more difficult to do but cause far less problems.
Just remember to delete any evidence of rooting from your sd card or just remove it entirely before taking the phone to Sprint. I hope everything works out for you!
Sent from my badass HTC Supersonic (Evo 4g) using XDA Premium App
plainjane said:
Take it back to Sprint. I had one that would rarely boot, it would take 20 or so tries. When it finally did boot, the screen would freeze up & I'd have to pull the battery. They gave me a new one, no questions asked & I had it the next day. That phone was never rooted, it was only two weeks old. I have insurance, so all of my replacements have been free. I had the one before that 3-4 weeks before the usb port gave out. I got my third one three months ago, rooted it, and have had no problems since. I hated the Evo for about a month when mine kept breaking.
I would also suggest manually rooting. The "one-click" methods are easy to do but difficult to troubleshoot. Manual methods are a little more difficult to do but cause far less problems.
Just remember to delete any evidence of rooting from your sd card or just remove it entirely before taking the phone to Sprint. I hope everything works out for you!
Sent from my badass HTC Supersonic (Evo 4g) using XDA Premium App
Click to expand...
Click to collapse
Thanks for the advice. I plan to just go to Sprint without my SD card and tell them the situation.
If you could point me towards a good guide for manual rooting I'd be grateful. After this last experience I'd much rather just do it myself and ensure it goes correctly.
Unrevoked gives issues like this. Try to start with autoroot this time.
Do not try to downgrade your bootloader this time. Make sure you nandroid back up and flash different ROMs and ensure things are working before you set anything up. Also make sure you are wiping everything. I suggest using Caulkin's Format All and flashing that in recovery.
sekigah84 said:
Unrevoked gives issues like this. Try to start with autoroot this time.
Do not try to downgrade your bootloader this time. Make sure you nandroid back up and flash different ROMs and ensure things are working before you set anything up. Also make sure you are wiping everything. I suggest using Caulkin's Format All and flashing that in recovery.
Click to expand...
Click to collapse
Thanks for chiming in, sekigah84.
The reason I tried downgrading my bootloader last time was that the issue appeared consistently with the 2.10 bootloader (tried flashing various recoveries, ROMs, radio versions, etc, over four days on that bootloader) and I thought reverting to ENG 0.76 might help correct the problem. I was very careful about doing nandroid backups and wiping cache, dalvik before installing ROMs, etc. when I could access recovery. Restoring from a backup was never possible because upon reboot I'd simply get the white HTC screen.
The problem seemed to start immediately after using unrevoked and didn't go away regardless of what I flashed or how many times I RUUed.
I definitely won't use unrevoked again. I'd consider using AutoRoot, but I'd prefer just to do a manual root process, or maybe not root at all.
RandomViolence said:
Thanks for the advice. I plan to just go to Sprint without my SD card and tell them the situation.
If you could point me towards a good guide for manual rooting I'd be grateful. After this last experience I'd much rather just do it myself and ensure it goes correctly.
Click to expand...
Click to collapse
Here's a link for you. As you said, this post has been retired, and it links you to xhausx's autoroot, however it still contains all of the info and instructions, and that method will still work for you. It's not outdated yet. So if you want to run it manually, follow Zikronix's instructions within the first post of this thread. Have fun!
http://forum.xda-developers.com/showthread.php?t=829045&highlight=root
Related
I've been going back and forth on whether or not to root my evo for the past week, and I think I'm finally up for it. I've done some basic looking around and I believe that I need to follow this method http://forum.xda-developers.com/showthread.php?t=765496. I would like to keep 2.2 and not have to go back down to 2.1. One thing that I did notice was the whole HBOOT ordeal. I checked and I have the .97 version. Is there anything special that I need to do before following the instructions in the link above? I plan on using the stock 2.2 rom and possibly experimenting with different roms in the future. I'd say I'm experienced with computers, although I will admit that I'm new to rooting and have yet to toil with coding. If anyone has any suggestions or a better method, I'm all ears.
i would suggest you follow this method instead: http://forum.xda-developers.com/showthread.php?t=838448
i rooted my evo with the method that you mentioned but that is an older process, it involves downgrading and then upgrading. even though the process will still work, you will be better off using an updated method.
spalding1028 said:
I've been going back and forth on whether or not to root my evo for the past week, and I think I'm finally up for it. I've done some basic looking around and I believe that I need to follow this method http://forum.xda-developers.com/showthread.php?t=765496. I would like to keep 2.2 and not have to go back down to 2.1. One thing that I did notice was the whole HBOOT ordeal. I checked and I have the .97 version. Is there anything special that I need to do before following the instructions in the link above? I plan on using the stock 2.2 rom and possibly experimenting with different roms in the future. I'd say I'm experienced with computers, although I will admit that I'm new to rooting and have yet to toil with coding. If anyone has any suggestions or a better method, I'm all ears.
Click to expand...
Click to collapse
With your hboot you can use unrevoked 3.21 and not have a problem them just download Rom manager and get amon ra recovery img and flash that through Rom manager and you have full root nand unlock and a good custom recovery. Plus its ten times easier
Sent from my EVO at the edge of hell
rajas_evo said:
i would suggest you follow this method instead: http://forum.xda-developers.com/showthread.php?t=838448
i rooted my evo with the method that you mentioned but that is an older process, it involves downgrading and then upgrading. even though the process will still work, you will be better off using an updated method.
Click to expand...
Click to collapse
Thanks! I was hoping that my post would bring about results or suggestions. I think I'm gonna hold off on Rooting until tomorrow night since it's already 3 am and I would prefer doing this with a fresh mind, haha. Thanks again. I'll make sure to post my success!
Jbcarrera said:
With your hboot you can use unrevoked 3.21 and not have a problem them just download Rom manager and get amon ra recovery img and flash that through Rom manager and you have full root nand unlock and a good custom recovery. Plus its ten times easier
Sent from my EVO at the edge of hell
Click to expand...
Click to collapse
unrevoked.com/recovery/ just download the exe from that link and run it? Sorry for being a bit confused >.<
I'll link you djrez's instructions when I get home but its really simple
Thanks a bunch! I'm sure this'll help other "newbies"
here is djrez's thread link and a link to unrevoked's download areahttp://forum.xda-developers.com/showthread.php?t=787304
and this is for unrevoked download unrevoked3 painless root
http://www.unrevoked.com/#evo
Not to hijack your thread, but I'm also considering rooting my phone to stock android, but have never rooted and have a couple questions.
Why do it? And the software (I guess?) That Evo comes with is designed to work specifically with the Evo(right?)...well if I rooted, is that software or whatever its called (yes, I'm a newbie) designed to take advantage of the Evo hardware etc..?
Thanks
Edit: oh and if I don't like it can I undo it like I never did it in the first place?
Sent from my HTC EVO 4G.
First off, Jbcarrera thank you so much for the links (and I LOVE your avater, being a huge AC fan)! I just rooted my evo in I'd have to say about 10 minutes. That's a good question for the seniors here, josh. My phone right now (rooted) looks exactly the same as it did beforehand. All apps still there, sense is still on it, and for me, I'm going to use this to turn on my mobile hotspot feature for free. My way of seeing it (and I'm sure others see it this way too) is that android is OPEN SOURCE carriers will lock features down, and rooting just unleashes the full potential. again, thanks to everyone here, I am sure to visit back often for many tips and tricks!
Hmmm if I were to root I'd want just deadstock original froyo 2.2. No sense no nothing lol.
10 mins is all it took? I'm just nervous, my luck I'll ruin my phone lol
Sent from my HTC EVO 4G.
josh995 said:
Hmmm if I were to root I'd want just deadstock original froyo 2.2. No sense no nothing lol.
10 mins is all it took? I'm just nervous, my luck I'll ruin my phone lol
Sent from my HTC EVO 4G.
Click to expand...
Click to collapse
firstly what hboot do you have? 10 mins is for anything with hboot under 2.02. if you don't know how to get to your hboot its easy just turn off your phone and let it power all the way down, next your hold the volume down and power button at the same time and voiala you are in hboot at the top of the phone it will state a few things one of them says hboot that number is your version of hboot if it says .97 or below your good to go if not then you will have to root with a more complicated method.
spalding1028 said:
First off, Jbcarrera thank you so much for the links (and I LOVE your avater, being a huge AC fan)!
Click to expand...
Click to collapse
thank you it took me a while to find it
Jbcarrera said:
firstly what hboot do you have? 10 mins is for anything with hboot under 2.02. if you don't know how to get to your hboot its easy just turn off your phone and let it power all the way down, next your hold the volume down and power button at the same time and voiala you are in hboot at the top of the phone it will state a few things one of them says hboot that number is your version of hboot if it says .97 or below your good to go if not then you will have to root with a more complicated method.
Click to expand...
Click to collapse
Says 0.97.0000
So if I follow the method you posted earlier, I'll have stock 2.2?
Sent from my HTC EVO 4G.
josh995 said:
Says 0.97.0000
So if I follow the method you posted earlier, I'll have stock 2.2?
Sent from my HTC EVO 4G.
Click to expand...
Click to collapse
yeah now to answer your other question a no sense rom there are a few that do this but to my knowledge no 4g on these roms one is cyanogen i have never tried it but there are very good reports very very few bug almost non existant and then there is virus airborne i belive both awsome no sense roms they're others but i don't know much about them feel free to search the development section of the forum for more info now sense roms i can name some very good ones but i'll let you decide after you decide what to do
Ok I will check those out. Thanks
And thanks spalding for starting this thread. I think it helped me in my decision to root!
Sent from my HTC EVO 4G.
No problem! I'm glad it wasn't a waste of time for people! By the way, wifi tether works like a champ! not sure if I can post the how to for that on here or not, so I will leave it up to a senior/admin to post if it's allowed.
Scared S!ht-less
I recently purchased a White Evo a few weeks ago. I've been reading the forums and in a few months i'll probably look back at this post and LOL at myself. Anyways I have HBOOT 2.02 with S-On. I tried installing Unrevoked when i first got the phone (easier way), but got the infamous "misc error"
I want to make sure I do this right and root the right way. I want to do a complete back up of the stock rom, but i tried doing a recovery with the HBOOT and all i got was a phone with a red triangle. I pulled the battery out and the phone restarted. Got scared.... So how do i do this the right way? Looks like I need to do some sort of nandroid backup, but what and where do i download nandroid? I also want to install this ROM http://forum.xda-developers.com/showthread.php?t=808656 I also don't want any radio problems since i have great 4g service. Do i need to do a backup of radio files since i also want to do this mod http://forum.xda-developers.com/showthread.php?t=696073
Thanks and hope you can help me out.
Hardware version 0004
Build Number 3.30.651.3
Yeah - This Thread is pretty helpful to me as well... Im still reading greek 'cause - although Im no noob when it comes to tech challenges I am a noob to rooting. I taught my self Homebrew for PSP, How to build themes for my PS3, how to write HTML for my website and have always been good at learning this kind of stuff on my own, BBUUTTTT I also like to read ALOT before I do some thing. This thread is now book marked and will probably be referred back to a million times...lol - THANKS!!
I have a ton of questions but I am searching the forums for the answers - I will probably be posting up my own thread when I get done doing my current research.
Jbcarrera said:
firstly what hboot do you have? 10 mins is for anything with hboot under 2.02. if you don't know how to get to your hboot its easy just turn off your phone and let it power all the way down, next your hold the volume down and power button at the same time and voiala you are in hboot at the top of the phone it will state a few things one of them says hboot that number is your version of hboot if it says .97 or below your good to go if not then you will have to root with a more complicated method.
Click to expand...
Click to collapse
Exactly if you have .97 or below simply use unrevoked3 one click root works great and installs clockworkmod recovery bootloader. My one recommendation after that is to then download Rom Manager and flash the bootloader to Amon_RA and do a nandroid backup before deciding to flash any roms. Clockwork does not create a wimax image and people have been having issues while trying to flash the wimax. I personally created a nandroid using clockwork then flashed to Amon and did another backup with it. Safe is better then sorry.
I didnt think this was possible but I think I bricked my phone by using Visionary and permroot.
I clicked on the permroot, the icon went on, rebooted and got stuck at the HTC green screen.
After pulling the battery;
I tried doing a factory reset, nothing.
I tried a stock image of tmobile, nothing (at least I think I did this right)
ADB doesnt recognize the device in windows
I have only seen a red triangle and exclamation point after trying several posts suggestions.
I'm stuck on what to do, and have a replacement coming, but not soon enough.
Can I do anything with this? Like get the original Tmobile image back on? If so, how? I'm not the brightest bulb when it comes to this, as the g1 was so much easier. A bit of instructions would be great.
Thank you!
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
You didn't read the post which said you should not try to install the stock rom?
fastludeh22 said:
Ok mods, I know this normally isn't the place, but I think this is very important as I'm seeing more and more semi bricks, some of which are not recoverable without HTC signing keys!
So I ask you mods, please don't lock this, if anything it really needs to be a sticky!
That being said, if you are s-off, do NOT flash the signed offical PC10IMG.zip. if you don't have the correct rom on there when you do, as per the unroot thread you will get stuck.
Let me give u an example of what I've been seeing and why its happening so everyone understands. Example: you perm root/s-off your phone. You decide to do some rom playing. You end up boot looping and can't fully boot into android. So u say hey, ill reload pc10 and start over, WRONG.
What happens is s-off does no checks, sigs, version number etc. So when you load it up it starts to flash. Hboot(s-on) is first, then recovery, then radio. Thing is it has to reboot to do radio, so it reboots, at this point your s-on so it does a version check. "Main is older" then it quits before ever touching the system.img or boot.img. at this point you are locked. You have s-on, stock recovery, and can't boot android. Long story short, your screwed.
Now depending on the rom/kernel u had/have installed you may have adb access. At this point you have a small chance of recovering, which is better then some. I just spent the last 5 hours working with someone on a fix and think we got it, but the bat has died and will have to pick back up tomo. If this works or not, I also have one more idea we can try. I will update OP with any fixes we find.
*If your system was bootable when you started this, it may still boot. but you will be s-on, stock recovery, and still on whatever rom you were running. at this point you will have to hex edit to downgrade, or wpthis.ko if there is one for your kernel to get back to s-off.
*ive seen some people saying. i did it, it worked for me, but don't add any supporting info. this is bad for people new to android cause it makes them feel they will be ok. the only way this can work is if you have a version installed as old or older then the official img, or if you take hboot out of the update which then makes it no longer the official update. but my question is why are you flashing this? if you want to fully unroot, then follow the unroot guide. if you just want to go back to stock w/root, grab one of the stock w/root roms.
Long story short, do your rom flashing from recovery. Stay out of hboot unless you are following proven instructions to a T, or being walked though be a "pro". I hope this helps save some people!
* if you just read all this going DAMN, i already did that, then go here:
http://forum.xda-developers.com/showthread.php?t=842495
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
@ddgarcia05 - that should be ok if he wasn't at S-OFF with the eng hboot though, which I don't believe that Visionary applies.
ibemad1 said:
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I checked and it said S-On and this was in recovery
ddgarcia05 said:
You didn't read the post which said you should not try to install the stock rom?
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
ADB doesnt recognize the device in windows and this was also in recovery
Anyone? Bueller?
cwis said:
ADB doesnt recognize the device in windows and this was also in recovery
Click to expand...
Click to collapse
Check out the adb guide at http://forum.xda-developers.com/showthread.php?t=865685
If you install the HTC Sync software, as mentioned in that guide, that should give you the drivers that you need.
This looks bad. Being that you're new. this can be very bad.
You have three choices:
1: study each thread about Bricking G2.
2:find a more experienced person to help you unbrick your phone.
3:find a very strong magnet and place it on your phone leave it there for an hour and bring it back.
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.
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?