How in THE hell is that .exe changing hboot only? This is not good. When we do get a legit copy of the RUU, I'm afraid it may fail on main version older. We'll see.
Can anybody help this guy out with a legit link to final GB RUU? I'll check my PC when I get home but I'm not sure I still have it either.
The Following User Says Thank You to iowabowtech For This Useful Post:
How in THE hell is that .exe changing hboot only? This is not good. When we do get a legit copy of the RUU, I'm afraid it may fail on main version older. We'll see.
Can anybody help this guy out with a legit link to final GB RUU? I'll check my PC when I get home but I'm not sure I still have it either.
Yeah, I might be screwed. Both RUU's are saying they are unable to work with this bootloader.
Yeah, I might be screwed. Both RUU's are saying they are unable to work with this bootloader.
There's another possible option. There's a thread nearby where a guy went from HTC dev unlock to s-off. If you could make a similar transition, you might be able to get out of this. I'll check into this more soon.
How in THE hell is that .exe changing hboot only? This is not good. When we do get a legit copy of the RUU, I'm afraid it may fail on main version older. We'll see.
Can anybody help this guy out with a legit link to final GB RUU? I'll check my PC when I get home but I'm not sure I still have it either.
The RUU that is on the htc dev site only changes the bootloader. Haven't tried the one on pvillecomp site though.
There's another possible option. There's a thread nearby where a guy went from HTC dev unlock to s-off. If you could make a similar transition, you might be able to get out of this. I'll check into this more soon.
Alright, so I was able to put it back to S-Off, downloaded a clockwork update.zip file, and now I'm in the process of restoring a CM7 backup. Booting back up now.
Reason I was returning to stock is that this phone only charges when its off and I made a warranty claim to Assurion. Phone was a refurb from my first phone that died.
hboot is still 1.02
Last edited by Bmr4life; February 12th, 2012 at 03:23 PM.
The Following User Says Thank You to Bmr4life For This Useful Post:
Alright, so I was able to put it back to S-Off, downloaded a clockwork update.zip file, and now I'm in the process of restoring a CM7 backup. Booting back up now.
Reason I was returning to stock is that this phone only charges when its off and I made a warranty claim to Assurion. Phone was a refurb from my first phone that died.
hboot is still 1.02
Hey nice job. What steps did you take to get s-off back? Anyway I was thinking maybe you could load 0.92 hboot, then perhaps just do the froyo ruu and then let gb come via ota update?
The Following User Says Thank You to iowabowtech For This Useful Post:
Hey nice job. What steps did you take to get s-off back? Anyway I was thinking maybe you could load 0.92 hboot, then perhaps just do the froyo ruu and then let gb come via ota update?
I tried to use the simple root program, but it wouldn't see my phone. So I went back to the link in the OP public:forever [RootWiki] and followed the directions for S-Off and it worked.
I then downloaded a CWM recovery file that got me to the rooted traingle with ! symbol. Then I was in the CWM recovery menu and was able to reload like normal.
I tried to use the simple root program, but it wouldn't see my phone. So I went back to the link in the OP public:forever [RootWiki] and followed the directions for S-Off and it worked.
I then downloaded a CWM recovery file that got me to the rooted traingle with ! symbol. Then I was in the CWM recovery menu and was able to reload like normal.
Ok so evidently you never lost root through all that. Strange stuff. Anyway if you still want to go back to stock, you would ideally downgrade your hboot to 0.92. The file is at the pcvillecomp site you started out at. Its loaded in hboot as a PB31IMG. Next apply the s-on file again. This time run the Froyo RUU which good files exist for. Then just accept the ota for gingerbread and you should be good.
The Following User Says Thank You to iowabowtech For This Useful Post:
Ok so evidently you never lost root through all that. Strange stuff. Anyway if you still want to go back to stock, you would ideally downgrade your hboot to 0.92. The file is at the pcvillecomp site you started out at. Its loaded in hboot as a PB31IMG. Next apply the s-on file again. This time run the Froyo RUU which good files exist for. Then just accept the ota for gingerbread and you should be good.
I have finally located the full Gingerbread RUU. Meaning the full version of 4.08.605.2 that is a full system update. Not the chopped up POS that is causing everybody problems and updating their bootloaders into a corner for some.
I am in the process of uploading to Mediafire and mirroring to my personal Dropbox account as an extreme backup to avoid losing this thing forever. I'm going to have to let it upload through the night, I will update all associated links tomorrow.
The Following User Says Thank You to iowabowtech For This Useful Post:
I have finally located the full Gingerbread RUU. Meaning the full version of 4.08.605.2 that is a full system update. Not the chopped up POS that is causing everybody problems and updating their bootloaders into a corner for some.
I am in the process of uploading to Mediafire and mirroring to my personal Dropbox account as an extreme backup to avoid losing this thing forever. I'm going to have to let it upload through the night, I will update all associated links tomorrow.
I followed the steps in option 2, skipping the S-On step, hoping it would fix problems I have been having with my phone. My phone would not connect to cell towers. It shows bars, but would not connect. However, my phone will connect to my network extender (samsung network extender scs-26uc4) at home and work fine. Everything reset back to android 2.3.4 as expected but still would not connect to cell tower after the reset. If I complete the steps again and turn S-ON and return the phone for a replacement (I have a couple of weeks left of the 12 month warranty) is there any way that Verizon they can tell that the phone was once rooted. Verizon told me that they would send me a replacement, but if the phone I sent back to them had been rooted, they would charge me the full price (over $400). Thanks,
I followed the steps in option 2, skipping the S-On step, hoping it would fix problems I have been having with my phone. My phone would not connect to cell towers. It shows bars, but would not connect. However, my phone will connect to my network extender (samsung network extender scs-26uc4) at home and work fine. Everything reset back to android 2.3.4 as expected but still would not connect to cell tower after the reset. If I complete the steps again and turn S-ON and return the phone for a replacement (I have a couple of weeks left of the 12 month warranty) is there any way that Verizon they can tell that the phone was once rooted. Verizon told me that they would send me a replacement, but if the phone I sent back to them had been rooted, they would charge me the full price (over $400). Thanks,
If it is s-on they can NOT tell. The only possible exception to that rule is those who use the newer HTC dev unlock method of unlocking the boot loader which leaves a trail behind and marks the bootloader as such. If you rooted using Unrevoked, you're golden.
If it is s-on they can NOT tell. The only possible exception to that rule is those who use the newer HTC dev unlock method of unlocking the boot loader which leaves a trail behind and marks the bootloader as such. If you rooted using Unrevoked, you're golden.
Since I already ran all the steps but the s-on tool and my baseband version is now 2.15.10.07.07 will the s-on tool still work? That baseband version is not listed under supported devices for HTC Droid Incredible on the unrevoked forever website... or does the baseband version only matter for turning s-off?
Since I already ran all the steps but the s-on tool and my baseband version is now 2.15.10.07.07 will the s-on tool still work? That baseband version is not listed under supported devices for HTC Droid Incredible on the unrevoked forever website... or does the baseband version only matter for turning s-off?
You will need to flash the froyo radio through hboot and then flash clockwork through hboot. Use clockwork to flash the s-on file. Then install gingerbread either through ruu or through hboot.
Since I already ran all the steps but the s-on tool and my baseband version is now 2.15.10.07.07 will the s-on tool still work? That baseband version is not listed under supported devices for HTC Droid Incredible on the unrevoked forever website... or does the baseband version only matter for turning s-off?
Excellent question. This tutorial was orginally created for Froyo, I just quickly adapted it for GB and changed the title after it was released. Any interest in trying it with the GB radio and letting us know? If not, I would follow sdrawkcab's advice of downgrading the radio first. That would be playing it on the safe side because we KNOW it works on that radio. I will have to edit the OP if this turns out to be the case.
If you decide to downgrade the radio, download the 2.15.00.07.28 from here: Radios | PvilleComp's
Rename it to PB31IMG, place on sd card and flash it through hboot, not recovery.
Last edited by iowabowtech; February 21st, 2012 at 05:49 PM.
Hi, I am trying to unroot my incredible because all apps are keep force closing...
mine is android 2.3.3 and rooted with unrevoked. it's running on Cyanogenmod7.
I tried both of the options above but it's not working :'(
option 1, it runs but it doesn't go to the next option, where I am supposed to click up-volume button.
option 2, when I run the program, it says it cannot find my device even though it's connected to pc.
Please help me.. I can't do anything with my phone right now cause it force closes everything D:
Your problem sounds more like the known issue with Dinc using CM7. Try using a different version of cyano before you unroot. There's lots of specifics on the cyano website forum.
Hi, I am trying to unroot my incredible because all apps are keep force closing...
mine is android 2.3.3 and rooted with unrevoked. it's running on Cyanogenmod7.
I tried both of the options above but it's not working :'(
option 1, it runs but it doesn't go to the next option, where I am supposed to click up-volume button.
option 2, when I run the program, it says it cannot find my device even though it's connected to pc.
Please help me.. I can't do anything with my phone right now cause it force closes everything D:
There is no 2.3.3 is there? Maybe I missed that one though idk. I'm guessing #1 failed due to the SD card not being formatted to fat32 or the format didn't take. As for running the RUU (.exe) program, did you install HTC sync as advised in the OP? If so, please uninstall before running the RUU. You only want the drivers that come packaged with the download. Finally, you do own an original Droid Incredible correct? Just making sure.
There is no 2.3.3 is there? Maybe I missed that one though idk. I'm guessing #1 failed due to the SD card not being formatted to fat32 or the format didn't take. As for running the RUU (.exe) program, did you install HTC sync as advised in the OP? If so, please uninstall before running the RUU. You only want the drivers that come packaged with the download. Finally, you do own an original Droid Incredible correct? Just making sure.
I can't upgrade CM7 cause it force closes rom manager. It says android version 2.3.3 on my phone; and my SD card is formatted to FAT32. I did install HTC sync as advised in the OP. I will uninstall it and try it again, then. and I do have an original Droid Incredible...
I can't upgrade CM7 cause it force closes rom manager. It says android version 2.3.3 on my phone; and my SD card is formatted to FAT32. I did install HTC sync as advised in the OP. I will uninstall it and try it again, then. and I do have an original Droid Incredible...
i would just try booting into recovery and try formatting the cache and data partition and see if that solves your force closes.
I have 23 of these phones that I needed to get to stock. 18 of them had reboot loop or white screen problems. I bricked the first two I tried from 2 roms I downloaded elsewhere. Grabbed a third from pvillecomp.com that enabled me to flash all but 3 of them, but the boot loops / white screens remained. 1 bricked and 2 said they couldn't be flashed due to older version.
After two days of this, I stumbled onto this thread. All phones, with the exception of the 3 bricks, are now flashed and working. You are truly my hero!
I have 23 of these phones that I needed to get to stock. 18 of them had reboot loop or white screen problems. I bricked the first two I tried from 2 roms I downloaded elsewhere. Grabbed a third from pvillecomp.com that enabled me to flash all but 3 of them, but the boot loops / white screens remained. 1 bricked and 2 said they couldn't be flashed due to older version.
After two days of this, I stumbled onto this thread. All phones, with the exception of the 3 bricks, are now flashed and working. You are truly my hero!
Hi, I am trying to unroot my incredible because all apps are keep force closing...
mine is android 2.3.3 and rooted with unrevoked. it's running on Cyanogenmod7.
I tried both of the options above but it's not working :'(
option 1, it runs but it doesn't go to the next option, where I am supposed to click up-volume button.
option 2, when I run the program, it says it cannot find my device even though it's connected to pc.
Please help me.. I can't do anything with my phone right now cause it force closes everything D:
Mine was also forcing close apps on CM7.1. Eventually figured out my /data/data partition was completely full. Quick fix was to clear data on the facebook app to free up some space, it had swelled to some ungodly amount. Then i used 1Tap cleaner to clear the caches on a bunch of the apps. This is how I am still running, as I haven't gotten around to doing the EXT4 4 all fix yet.
Most generally that is because the card is not formatted to FAT32 or you did format it to FAT32 and it didn't take the format well. Have you tried the .exe RUU method listed in the OP? It may be a better option for you.
Most generally that is because the card is not formatted to FAT32 or you did format it to FAT32 and it didn't take the format well. Have you tried the .exe RUU method listed in the OP? It may be a better option for you.
oops, ninja'd by sdrawkcab
i formatted it twice on 2 different sdcards and nothing. i tried the ruu but it fails cause of something not being compatible
wait, nevermind. this is for a evo 4g. idk how i got into incredible
Ahh ok no problem. I was just going to ask you for your hboot details but nevermind.
You should be able to use the same methods on the Evo, just different files of course. Hopefully they have them posted somewhere over in the Evo 4G forum. Good luck!
I am currently rooted, running the AOKP ROM, unlocked bootloader, S-ON.
I would eventually like to return to a state of stock, rooted, Gingerbread, but I am not making any progress.
When I try method one, HBOOT sees the PB31IMG.zip file, it loads it, and then it returns to the main HBOOT screen with no option to flash the image. When I try to run the RUU, it gets to a certain point, and then I get an ERROR 155; every time.
Has anyone had these issues?
The Following User Says Thank You to troar For This Useful Post:
I'm here because my Droid Incredible has been insisting on downloading and installing the latest software build, almost to the point of paralyzing the phone. However when I try to install the update normally, it fails to reboot and install the upgrade. After talking to Verizon today, they said this is a common issue for rooted phones. The tech recommended unrooting the phone, performing the upgrade, and then I can root it again or whatever I want.
The phone is s-off, and I was hoping that by running the RUU everything would be fine, but though RUU seems to have run perfectly I'm still unable to install the update. I guess being unrooted is not enough.
So I guess I do need to be s-on, but in order to get there I have to re-root the phone, install CWM, and load the s-on zip. I've got software build 4.08.605.2 installed, and baseband (radio) 2.15.00.07.28 (the Froyo radio required to do s-on). UnrEVOked 3.34 is unable to root the phone, and suggests my firmware may be too new (wasn't s-off supposed to address this?)
So I guess I do need to be s-on, but in order to get there I have to re-root the phone, install CWM, and load the s-on zip. I've got software build 4.08.605.2 installed, and baseband (radio) 2.15.00.07.28 (the Froyo radio required to do s-on). UnrEVOked 3.34 is unable to root the phone, and suggests my firmware may be too new (wasn't s-off supposed to address this?)
I got a little further -- noticing that several apps I installed before the last flash were still installed, I removed the SD card and used the HBOOT FACTORY RESET option to totally wipe the phone.
This time, when it was ready to install 4.08.605.15 it, properly rebooted, but I got the dreaded red triangle and exclamation point. After a battery pull and a reboot, I'm still using software 4.08.605.2.
UnrEVOked is still not working, though.
Last edited by cputrdoc; July 16th, 2012 at 01:08 AM.
I got a little further -- noticing that several apps I installed before the last flash were still installed, I removed the SD card and used the HBOOT FACTORY RESET option to totally wipe the phone.
This time, when it was ready to install 4.08.605.15 it, properly rebooted, but I got the dreaded red triangle and exclamation point. After a battery pull and a reboot, I'm still using software 4.08.605.2.
UnrEVOked is still not working, though.
You don't need to go back to s-on to install the update. You only need the stock recovery, which you already have. The update itself is very glitchy, there is a lot users reporting problems trying to install it and most of them were never rooted.
For reference though, this is how you would get root back: [How To] Regain Root With S-Off or HTC unlocked bootloader, but all you need to do to get s-on is flash clockwork, install the s-on file, then install the stock recovery again. (I highly recommend you do NOT go back to s-on though)
Unrevoked is not needed since you are s-off.
Last edited by sdrawkcab25; July 16th, 2012 at 05:08 AM.
Yeah I would echo the above advice of NOT going s-on. Are you just stock, rooted? If so, I would either flash a stockish rom or we can look at perhaps modifying the build.prop to make the update server think you are updated so it quits trying to update your phone. We just need to figure out the new update's build fingerprint.
I am currently rooted, running the AOKP ROM, unlocked bootloader, S-ON.
I would eventually like to return to a state of stock, rooted, Gingerbread, but I am not making any progress.
When I try method one, HBOOT sees the PB31IMG.zip file, it loads it, and then it returns to the main HBOOT screen with no option to flash the image. When I try to run the RUU, it gets to a certain point, and then I get an ERROR 155; every time.
Has anyone had these issues?
troar, I'm in the identical situation that you are. Same starting point, same errors, etc.
Here's something else that I saw, and no idea if this has anything to do with it. When I first tried using Unrevoked to go S-ON, I put both the Unrevoked ZIP file AND the PB31IMG.ZIP on a blank card. When I HBOOTed, it saw and read PB31IMG and prompted me to install, and realizing what happened I said no. I then went to S-ON, confirmed that it took, then redid the SD card (with just PB31IMG) and HBOOTed again, only now it loads PB31IMG but won't prompt to install.
Weird, huh? It's almost as though it wants to be S-OFF before it will install.
Oh, the PB31IMG is the one from Mediafire in this sticky. Checked the MD5 and it was OK.
I am currently rooted, running the AOKP ROM, unlocked bootloader, S-ON.
I would eventually like to return to a state of stock, rooted, Gingerbread, but I am not making any progress.
When I try method one, HBOOT sees the PB31IMG.zip file, it loads it, and then it returns to the main HBOOT screen with no option to flash the image. When I try to run the RUU, it gets to a certain point, and then I get an ERROR 155; every time.
Has anyone had these issues?
troar, late-breaking update: I had success this afternoon by going S-OFF and then was able to do method 1 straightaway. Don't know why...I'm still trying to get my bearings in this world.
I been using HTC Incredible S 710e for more than a year now. I never meesed up with phone by Rooting it or changing ROM or any such thing.
Now My phone is stuck in continuous reboot loop through out the day & night, even if I shut it off. The only way out is to remove the battery.
1) IPhone doesn't get rebooted if it plugged in charger.
2) I've already tried the phone with another Battery... problem still exists.
3) Tried formating SD Card.... Factory Reset ..... Wipe Data/ Factory Reset.... Recovery... Wipe Cache.... Nothing Helped !!!
4) I gave it for reloading the OS... Still the problem is not solved.
5) During "Wipe Data/ Factory Reset" the message on the screen is something like " e:/ can't open data......, Can't open...., Can't open.... Cashe Wiped"
Can you please help me getting it fixed.... Thanks in Advance !!!!
I been using HTC Incredible S 710e for more than a year now. I never meesed up with phone by Rooting it or changing ROM or any such thing.
Now My phone is stuck in continuous reboot loop through out the day & night, even if I shut it off. The only way out is to remove the battery.
1) IPhone doesn't get rebooted if it plugged in charger.
2) I've already tried the phone with another Battery... problem still exists.
3) Tried formating SD Card.... Factory Reset ..... Wipe Data/ Factory Reset.... Recovery... Wipe Cache.... Nothing Helped !!!
4) I gave it for reloading the OS... Still the problem is not solved.
5) During "Wipe Data/ Factory Reset" the message on the screen is something like " e:/ can't open data......, Can't open...., Can't open.... Cashe Wiped"
Can you please help me getting it fixed.... Thanks in Advance !!!!
Are you using the files posted in this thread? If so that will be the problem. We would need to find you the files for the Incredible S since the posted files are for the original Droid Incredible.
1Likes
Help please! Not having any luck...
