Hi all, I followed Prototype7's method for gaining root and S-OFF via Tacoroot. I then proceeded to install Revolutionary with the CWM recovery.
I am now trying to go back to stock following CondemnedSoul's method, but whenever the PG32IMG.zip update installs, it skips [3] Bootloader and says "Bypassed". It also says "Bypassed" for [7] TP.
The update will say "Complete...", I can boot the phone once and use it normally, but every subsequent attempt to reboot the phone results in boot loops!
What am I doing wrong? Is there some way to flash the bootloader separately? Does my SD card need to be reformatted? Thanks in advance...
swenpro said:
Hi all, I followed Prototype7's method for gaining root and S-OFF via Tacoroot. I then proceeded to install Revolutionary with the CWM recovery.
I am now trying to go back to stock following CondemnedSoul's method, but whenever the PG32IMG.zip update installs, it skips [3] Bootloader and says "Bypassed". It also says "Bypassed" for [7] TP.
The update will say "Complete...", I can boot the phone once and use it normally, but every subsequent attempt to reboot the phone results in boot loops!
What am I doing wrong? Is there some way to flash the bootloader separately? Does my SD card need to be reformatted? Thanks in advance...
Click to expand...
Click to collapse
Did you flash a new radio? Can you tell us what radio you are on (settings > about phone > baseband version).
I did nothing more than the instructions given in the links I posted. To gain root via the tacoroot method I had to flash the 1.09.01.0312_vivow_Radio_PG32IMG.zip after flashing the initial RUU. But note that my radio and everything else, except the bootloader, was successfully updated using the stock image provided by CondemnedSoul.
swenpro said:
I did nothing more than the instructions given in the links I posted. To gain root via the tacoroot method I had to flash the 1.09.01.0312_vivow_Radio_PG32IMG.zip after flashing the initial RUU. But note that my radio and everything else, except the bootloader, was successfully updated using the stock image provided by CondemnedSoul.
Click to expand...
Click to collapse
I didn't use tacoroot (I rooted before it was needed), so I'm not 100% familiar with it. You'll probably have to wait for someone more familiar with it. I was just suggesting something that I've read about other users doing that tripped them up. Good luck with it, you shouldn't have to wait long for someone more helpful to come along.
Thanks for your effort.
Anyone able to help me on this?
Not sure what the [7] is, but the bootloader gets bypassed by Revolutionary's custom hboot so it can't be overwritten by an RUU or OTA, which is why you don't lose S-OFF unless you manually overwrite the hboot partition.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 07:49 AM ---------- Previous post was at 07:43 AM ----------
As for your issue, reflash the .0312 (or .0320, that's the one from the ICS leak) radio, the one from CS's image isn't an upgrade even though it probably is version .0622 or something like that, HTC has some weird version naming scheme that they don't even follow half the time.
Sent from my SCH-I535 using Tapatalk 2
prototype7 said:
Not sure what the [7] is, but the bootloader gets bypassed by Revolutionary's custom hboot so it can't be overwritten by an RUU or OTA, which is why you don't lose S-OFF unless you manually overwrite the hboot partition.
Sent from my SCH-I535 using Tapatalk 2
---------- Post added at 07:49 AM ---------- Previous post was at 07:43 AM ----------
As for your issue, reflash the .0312 (or .0320, that's the one from the ICS leak) radio, the one from CS's image isn't an upgrade even though it probably is version .0622 or something like that, HTC has some weird version naming scheme that they don't even follow half the time.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thank you! Flashing the new radio (.0312) seems to have fixed the problem, so far no bootlooping anymore.
By the way, I was on a .1111 radio after flashing the stock image. I would have wrote that sooner, but did not know until I had reflashed the phone once again where I could look at the baseband version, since it was bootlooping.
This is not a necessity, but... I was wondering how a person would flash the stock bootloader and turn it back to S-ON? Just in case I decide to sell my phone in the future, it would be "all stock".
swenpro said:
Thank you! Flashing the new radio (.0312) seems to have fixed the problem, so far no bootlooping anymore.
By the way, I was on a .1111 radio after flashing the stock image. I would have wrote that sooner, but did not know until I had reflashed the phone once again where I could look at the baseband version, since it was bootlooping.
This is not a necessity, but... I was wondering how a person would flash the stock bootloader and turn it back to S-ON? Just in case I decide to sell my phone in the future, it would be "all stock".
Click to expand...
Click to collapse
There's a guide in the general section, basically you have to flash the RUU, then extract the hboot and manually write it to the partition, it's fairly easy to do, easier than rooting it.
Sent from my SCH-I535 using Tapatalk 2
Thanks again! There are so many sections to this forum I had never noticed that sticky. Appreciate the help.
My silly n00b Question(s)
prototype7 said:
There's a guide in the general section, basically you have to flash the RUU, then extract the hboot and manually write it to the partition, it's fairly easy to do, easier than rooting it.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Ok, i can't figure out what a sticky is, nevermind where to find the one you reference... Sorry.
I love XDA, it helped me root my dInc2 replacement, and that one's replacement (both after the previous phone's charge port died), and i just love it, BUT i've never had to use it except these two times, so i haven't figured out the forum stuff - like stickies - especially since i usually use NoScript normally and i don't really understand the general vs Q&A distinctions between groups of threads...
In any case - i haven't been able to find the sticky you referenced, and my searches have failed to find recent instructions regarding manually flashing the Hboot -- everything i found had download links that didn't work, except CS's stock ROM (as mentioned by the OP in this thread) - and now i've got that installed on my phone-to-send-back, so i've have successfully returned the ROM to a stock 2.3.4 GB using CS's post here on XDA, and from what i can tell/remember, flashing the HBOOT to stock (.97) will put it back exactly how it was when i got it last year - as i had to downgrade the OS but i don't think i had to touch the HBOOT (i got this phone in late March 2012)
So i'm now trying to rectify the issue that i don't know where to get the Hboot to manually flash, and, even if i had the file, i haven't found out if there is a ADB over TCP-IP that works when your USB/charge port has basically disconnected itself from the motherboard.
I was hoping that someone here might be able to help me either find the hboot file or extract what i need from CondemnedSoul's RUU (as seems to be described in prototype7's post), and give me the commands i need to do the manual flash...
If i could also get ADB over TCPIP advice, that would be awesome, but the former would be a good start...
Verizon has started to nag me for not returning the old phone sooner...
Thank you!
Also - thanks to Prototype7 for his awesome guide to s-off methods/rooting the Dinc2 -- was a life-saver for rooting the new phone so i could make use of my clockworkrecovery backup... (after some boot-looping horror, when i got an error during the update of the radio using the tacoroot method -- i restarted again from a different windows machine and it worked fine - i think the issue was the drivers on the other machine -- i'd used it to root the earlier phone, and i think it had weird drivers or something)
wntrequinx said:
Ok, i can't figure out what a sticky is, nevermind where to find the one you reference... Sorry.
I love XDA, it helped me root my dInc2 replacement, and that one's replacement (both after the previous phone's charge port died), and i just love it, BUT i've never had to use it except these two times, so i haven't figured out the forum stuff - like stickies - especially since i usually use NoScript normally and i don't really understand the general vs Q&A distinctions between groups of threads...
In any case - i haven't been able to find the sticky you referenced, and my searches have failed to find recent instructions regarding manually flashing the Hboot -- everything i found had download links that didn't work, except CS's stock ROM (as mentioned by the OP in this thread) - and now i've got that installed on my phone-to-send-back, so i've have successfully returned the ROM to a stock 2.3.4 GB using CS's post here on XDA, and from what i can tell/remember, flashing the HBOOT to stock (.97) will put it back exactly how it was when i got it last year - as i had to downgrade the OS but i don't think i had to touch the HBOOT (i got this phone in late March 2012)
So i'm now trying to rectify the issue that i don't know where to get the Hboot to manually flash, and, even if i had the file, i haven't found out if there is a ADB over TCP-IP that works when your USB/charge port has basically disconnected itself from the motherboard.
I was hoping that someone here might be able to help me either find the hboot file or extract what i need from CondemnedSoul's RUU (as seems to be described in prototype7's post), and give me the commands i need to do the manual flash...
If i could also get ADB over TCPIP advice, that would be awesome, but the former would be a good start...
Verizon has started to nag me for not returning the old phone sooner...
Thank you!
Click to expand...
Click to collapse
This is the guide I was referencing: http://forum.xda-developers.com/showthread.php?t=1466295
For ADB over TCPIP, I use ADBWireless off the market, but instead of using the adb connect command with the info it shows, use your phone's IP address shown under About phone>Status (I think that's where it is).
prototype7 said:
This is the guide I was referencing: http://forum.xda-developers.com/showthread.php?t=1466295
For ADB over TCPIP, I use ADBWireless off the market, but instead of using the adb connect command with the info it shows, use your phone's IP address shown under About phone>Status (I think that's where it is).
Click to expand...
Click to collapse
YOU ROCK. - thanks for the quick reply.
I read the guide you referenced - but the links are down, so i'll add a reply and see if that thread's OP can re-upload. If that seems to still be the correct way to un-root/S-on, then i'll see what i can do..
I had a bunch of questions, but i think I figured out the answers... i just need to go home from work and actually try out following those directions...
wntrequinx said:
YOU ROCK. - thanks for the quick reply.
I read the guide you referenced - but the links are down, so i'll add a reply and see if that thread's OP can re-upload. If that seems to still be the correct way to un-root/S-on, then i'll see what i can do..
I had a bunch of questions, but i think I figured out the answers... i just need to go home from work and actually try out following those directions...
Click to expand...
Click to collapse
See my reply in that thread, gave you updated links.
Related
Just wanted to get this out there. I have been trying to root all night with no luck. Hoping others with same issue will come for an offer help. Free evo accessory for anyone that can get this solved for me.
You need to provide a few more details what you've done to try and achieve root. What method did you try? What are seeing on the screen at the various steps.
I used the long method listed Here. If you're using the .exe file in the other thread, its not as reliable.
I am having the sane issue. I have tried regaw's method, the manual method listed in the hboot S-off thread, and the automated method in the other hboot thread. Everything works except flashing pc36img.zip....it throws the error he mentioned when updating radio v2, plus it throws fail-ic when trying to update bootloader (it does not say "bootloader skipped" as indicated it should in the guide). From this point forward, it will not boot past white HTC splash w/o running ruu. You can even do the rest of the guide and get a custom recovery flashed (i have done both amon-ra, and clockwork). After running ruu, S-off sticks (meaning unrevoked worked, I suppose), but you obviously don't have root. If you try to flash a custom Rom, even just a rooted version of the ruu, it throws a symlink error (something like E:fail can't symlink bin/lsmod....can't remember exact syntax, I posted it in another thread though, I'll see if u can find it). I have tried doing this from custom recovery and from toast's pc-based recovery. Is there a way for me to pull a log of what is happening when the pc36img has its errors? That may be the only way for me to give you more info than I have.
funnyrocket said:
Just wanted to get this out there. I have been trying to root all night with no luck. Hoping others with same issue will come for an offer help. Free evo accessory for anyone that can get this solved for me.
Click to expand...
Click to collapse
Look at this guys thread and also ask them to move your thread to the right forum so you can get the proper views and help
http://forum.xda-developers.com/showthread.php?t=831915
i followed the manual method, it failed with the radio pu, i completed the method, my phone would not boot it was stuck at the "htc evo" screen. So after some research I found the correct file to make my phone boot, The manual steps worked and i rotted my phone but i am unable to put a custom rom on
dl this file rename it pc36img and push it to you phone and reboot in the hboot and let it install it should pass you will have root access and clockworks custom recovery but until someone fixes the roms or gives a answer they wont work they will fail but you will have a phone and root admin.
http://forum.xda-developers.com/showthread.php?t=791019
flipper12 said:
You need to provide a few more details what you've done to try and achieve root. What method did you try? What are seeing on the screen at the various steps.
Click to expand...
Click to collapse
I used Method 3 from this zikronix's [TOOL][GUIDE] HBoot 2.02 S-OFF thread. Everything works great until I have to flash PC36IMG. It starts but gives the Radio-V2 Fail-PU and Bootloader-Fail-IC. The screen shows updated failed. Upon restart I'm at the red triangle boot screen. Can't do anything else from there.
kc_sheets said:
i followed the manual method, it failed with the radio pu, i completed the method, my phone would not boot it was stuck at the "htc evo" screen. So after some research I found the correct file to make my phone boot, The manual steps worked and i rotted my phone but i am unable to put a custom rom on
dl this file rename it pc36img and push it to you phone and reboot in the hboot and let it install it should pass you will have root access and clockworks custom recovery but until someone fixes the roms or gives a answer they wont work they will fail but you will have a phone and root admin.
I don't see what this will do for me since I don't have S-Off status yet. I can't get that far. Plus, this isn't a comeplete root. I have another Evo here that has the exact same specs, right down to Hardware 003 and I just did the Method 3 root and it went through with flying colors. So...
Click to expand...
Click to collapse
I think it is the bad blocks issue popping up again. I read about it in toast's root thread, I believe. If I am right, toast figured out a fix before. We may have to find a way to use his fix again. It was for a different bootloader, though. Might not work straight out of the box. I'm no dev, but this seems to me to be what is happening.
tejasrichard, i didnt know you got an Evo.
Come see us in #HTC-EVO on irc.freenode.net
Alot of devs hang out in irc so you guys might be able to get help there.
Use clockwork.
For some reason, amon ra doesn't work right away. You'll get fail-pu with it.
OtisFeelgood said:
tejasrichard, i didnt know you got an Evo.
Come see us in #HTC-EVO on irc.freenode.net
Alot of devs hang out in irc so you guys might be able to get help there.
Click to expand...
Click to collapse
Sup Otis! Yeah, I finally got my upgrade, lol! I'm a little late to the party, but better late than never, right? I'll stop by tomorrow and say hi (promised the missus some quality time tonight). I've got a few more things I want to try, but I'm betting whatever toast did b4 to get around the bad blocks will work again. Need to pm him and see what he thinks.
I need to bring my phone back to sprint I tried all UNROOT methods but my USB is broke and when I try to USE the PC36IMG.zip I get an error saying something like (update is older ect..) so I got the idea that if I flash a old rom before the updates and just update my phone it will unroot me but the problem I cant find a flashable rom thats old since we moved on so much since the EVO came out???
I just had to do this two days ago. You need an updated image file, it's posted in the unrooting thread in this forum. I'm on my cell so it'll take me a while to post a link. Give me a minute.
forum.xda-developers.com/showthread.php?t=780141
There's a copy of the updated file in that thread.
did you find this when you searched?
http://forum.xda-developers.com/showthread.php?t=695878
They only look for the superuser application. Flash a stock rooted rom. Remove the superuser app and you will be good to go.
Sent from my EVO using Tapatalk
DomSim said:
did you find this when you searched?
http://forum.xda-developers.com/showthread.php?t=695878
Click to expand...
Click to collapse
Your so helpful!
Sent from my EVO using Tapatalk
Unless they see his s-off in hboot.
They know to check the bootloader. Just install one of the official ruu to unroot. Simple as that. I've done it.
Official RUU
Just flash an official ruu and you will be good to go. You can find them all over the place in here.
3.70 (latest RUU)
Below is a link to the very latest RUU possible so that you're phone can be brought back to stock status without root. I would recommend flashing the S-On tool also which I'll post as the second link too. The first link is to the RUU. Good luck
Official RUU (will unroot your phone/rom)
http://forum.xda-developers.com/showthread.php?t=874091&highlight=ruus
The Unrevoked S-On Tool:
http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip
EDIT: Also, I was thinking, if the above won't work due to your USB issues, maybe you could flash another rom, a sense based rom, like from Flipz or someone, and then run the "system update" program from the phone and maybe it'll update you to the latest RUU using the OTA Update program. That may solve your issues for getting the phone back to stock status without SU app and without root. Then, if that works, I would reboot the phone in to the bootloader and check to see if it says S-off or S-on. If it says S-on, you're fine and ready to go to sprint. If it says S-off, download and run the unrevoked S-on tool I posted above. Hopefully you won't need USB for it to run properly, but hey, you never know. Either way, if it does, there's got to be a way to use a S-on tool out there that doesn't need USB access. Hope this info helps you out in any way possible
EDIT #2: Read the stuff in this post to help with things if the above won't work.
http://forum.xda-developers.com/showthread.php?t=780141&highlight=ruus
When it says to connect USB and put the files on the SD Card, just use a card reader via a laptop or something to put the files on the SD Card and continue on.
I have taken my phone to sprint service centers 3 times. 2 speaker replacements, 2 screen replacements, a camera lens replacement (combined with a screen replacement, and they replaced the whole front of the phone - no more dents all around the shiny black bezel).
I always insisted they not replace the phone, as I wanna keep my 0002 HW. My phone was root with custom rom, but with a ''back to stock" theme flashed on it (thanks Virus)
My bootscreen is black (not white) with white evo 4g text, so, as soon as they turn my phone on it's obvious it's custom.
I know this isn't as helpful as previous posts, I'm just saying worst-case-scenario flash a stock theme and you'll probably be fine. I've had more than one tech tell me 'as long as you try to make it look stock, make the effort, that's good enough'.
Especially given that it's a hardware related issue, rather than a SW issue - I mean, they wont blame root access for your USB port not working.
Good luck, hope you get it sorted either way.
Sent from my PC36100 using XDA Premium App
Thread moved to Q&A.
GENEius said:
forum.xda-developers.com/showthread.php?t=780141
There's a copy of the updated file in that thread.
Click to expand...
Click to collapse
I tried that first and I can not get it to work, so I was looking for a older rom to flash then update it but cant find a old rom in a zip thats flashable!!
corelle said:
I tried that first and I can not get it to work, so I was looking for a older rom to flash then update it but cant find a old rom in a zip thats flashable!!
Click to expand...
Click to collapse
How old of a ROM are you looking for? There are plenty of 3.30 Software roms. Myn's RLS4 is 3.30 software, RLS3 is 3.29, etc. http://forum.xda-developers.com/showthread.php?p=8341836 That's a link to Myn's thread. Look in post #3, all of his older releases are linked there. Also, if you look in Myn's Signature, there's a link to OTA Supersonic 3.29, stock, rooted base rom.
With all that said, I don't think that will remedy you're 'main version older' problem. I believe it checks your hboot version, or radio versions or something. Not the actual software version. I could be wrong, but I believe that's the case. I would try a couple of the different PC36IMG's in this thread here http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu. It has all of the recent versions. If thew newest PC36IMG doesn't work, try the next older one (3.30) etc. One of them is bound to work for you. Good luck.
Some people have a 2nd Gmail account that isn't tied to any root apps incase the techs at sprint get nosey and look where they shouldn't be....
.........at 8 am today someone poisons the coffee....do not drink the coffee. More instructions will follow.
Cordially,
Future Dwight
may be late to the party, but check out some of these theres a **** load of old ROM's lol...
http://forum.ppcgeeks.com/cdma-htc-...m-database-163-2-new-roms-kernal-updates.html
http://forum.ppcgeeks.com/cdma-htc-...m-database-163-2-new-roms-kernal-updates.html
...bookmark it
When I did unroot, I restored my nandroid from before I installed ota 3.70, then unistall superuser (won't go away if you do a wipe), once your good to go, then use ra recovery to flash the official 3.70 ota, don't reboot once that completes, then flash s-on, then reboot you phone. I would recomend pulling ur sd card before taking it in, and doing a data wipe just to make sure all signs of root are gone
Sent from my Evo using the XDA app
OK so it looks like I keep getting that error code was because the files i was using was all corrupted I used (md5 checker) and it answered that for me...so I need a uncorrupted PG36IMG file!!!!
corelle said:
OK so it looks like I keep getting that error code was because the files i was using was all corrupted I used (md5 checker) and it answered that for me...so I need a uncorrupted PG36IMG file!!!!
Click to expand...
Click to collapse
Looking for an RUU?
corelle said:
OK so it looks like I keep getting that error code was because the files i was using was all corrupted I used (md5 checker) and it answered that for me...so I need a uncorrupted PG36IMG file!!!!
Click to expand...
Click to collapse
Where did you try downloading from? I've never got a corrupted one from the link I posted above. Did you try redownloading? Do you have a good internet connection?
I was able to run an older version of Unrevoked to establish SU access, but Unrevoked Forever is incompatible with my radio version. So, I have SU access, but I cannot remove or convert any applications using Titanium Backup. TB runs, but it reboots the phone if I try to remove system apps. HBOOT shows S-ON since Unrevoked Forever was not able to complete due to the radio version. So, am I stuck with S-ON? Is Unrevoked Forever going to continue developing releases to cover 2.15.10.07.07?
If I understand correctly, I cannot flash an older radio version with S-ON. Please correct me if I am wrong.
Thanks!
HTC Incredible
2.3.4
Baseband: 2.15.10.07.07
you are correct,s-on will only let you go forward with "approved by htc" files. that means no backpeddling firmware to a rootable version,no flashing only a radio or recovery. im surprised that unrevoked even worked to get you su access,i was under the impression that all exploits had been patched in 2.3.4 source code. what happens if you try and install clockwork?
if you truly have su access,it seems it may be possible to use adb to rewrite the misc image,and thus be able to flash backwards in firmware.
however,from the sounds of the behavior youre describing for tibu,i dont believe you have su access. it prolly only put the app in the drawer,and was unable to place the matching binary.
we have been telling folks for months that they should become s-offed before the GB update,as it would be unrootable.
i bought an xtc clip awhile back that is supposed to support the incredible. i dont know that it will actually work,ill know for sure when it gets here. im told it only works with sim card phones,wich the inc is not,but its clearly listed in the supported devices.
your only real hope at this point is that someone finde a new exploit that will allow temp root and re-writing of the misc image so that you can flash older rootable firmware,or that alpharev/unrevoked can add the incredible to its supported devices list,as they use some sort of hboot trickery to get a hard patched permanent s-off hboot onto the phone first. from there you load a recovery thru hboot,then flash su in recovery.
sorry this isnt the news youre hoping for.
Thank you for the help.
It is odd. I definitely have su access through terminal, and I am running opengarden and barnacle wi-fi tether. I ran an older version of Unrevoked, and it did not complete the final step of s-off. Clockworkmod installed successfully, and I created a recovery image. Can we expect some way to root after the GB update? Is this just an HTC thing? I'm sorry for all of the questions, but I was soooo close!
efizzle said:
Thank you for the help.
It is odd. I definitely have su access through terminal, and I am running opengarden and barnacle wi-fi tether. I ran an older version of Unrevoked, and it did not complete the final step of s-off. Clockworkmod installed successfully, and I created a recovery image. Can we expect some way to root after the GB update? Is this just an HTC thing? I'm sorry for all of the questions, but I was soooo close!
Click to expand...
Click to collapse
If you already have clockwork mod, flash the unrevoked forever zip from here
When I flash the zip file, I get E:/ unsupported radio version. E: update failed.
Do you have adb set up and running? Are you fairly comfortable copy/pasting commands?
Sent from my ADR6400L using XDA Premium App
still with us? waiting for an answer to the above so we can procede
also is it possible you can post or PM me a link to the version of unrevoked you used?
if you dont have a link,just email me the whole file( [email protected] ) im extremely interested in trying to duplicate your condition and figuring out a reliable way for folks to downgrade and root.
Scotty,
I'm sorry for the delayed response.
I do not have ADB setup, but I have no problem following directions to get S-off and reclaim some memory!
I have emailed you the Unrevoked file to your email address. This should run perfectly on 2.3.4 with the exception of the last step of flashing unrevoked.zip for S-off. You will see the "unsupported radio version" errors on the phone's screen. Please let me know if there is anything else that I can do to help. Thank you for your help with this.
I got your email. I will put some stuff together for you,and try it out and see if it all works the way I hope it will. If so ill upload a mini-adb with some exploits files and post a guide. Basically,were just going to rewrite the misc image so you can downgrade back to froyo and run unrevoked forever. After you reroot and get s-off back,you can restore a backup of what you have now.
Sent from my ADR6400L using XDA Premium App
Subscribing to thread. Looks interesting, Im hopeful it works out. Good luck!
Sent from my ADR6300 using XDA App
Ok after reading this thread again. My guide for the merge on froyo or the stuff I have for gingerbread for the merge will not work on a non emmc device. 2nd who buys a xtc clip and doesn't look what they buy? The way it works is with the sim card slot. Inc doesn't have one so it isn't going to work. It also isn't listed as supported as it would be pointless to say it does.
If I am not mistake with s-on you can't flash the recovery partition. So how did you get clockworkmod? If you have clockworkmod then you can flash non htc files. Well actually I am not sure how that would work as you have s-on but clockworkmod. Since I have never been in that boat I am unsure.
So are we talking about the inc or inc 2? If inc I am trying to think back to the desire and what was possible on s-on. If I remember right you can dump the misc then flash a lower version ruu. I just can't remember if it doesn't even flash or if it does and doesn't downgrade the radio. By the way I got it in a pm/here scotty was planning to base helping you off my merge guide. By the sounds of it anyway.
Where the commands are not the same. As the partitions would be different. The misc-image is also not the same so if he had you flash the merge misc it will more than likely bork stuff. I am more than willing to help though. How ever I do not check the forums so you are better off pming me. I will say that nothing will probably work until unrevoked supports the new radio.
Edit: If the incredible works with a goldcard. Dump the misc partition and edit it for the firmware version you want to downgrade to. Then run a lower version ruu. When that is done run unrevoked. Of course I don't have a inc so I am not sure if that will work either. I also jumped a bit to conclusions so sorry for that. I also do not get your one post about the xtc clip here, yet in that other post say the clip doesn't support the inc.
thanks for your input,but rest assured we are in no way shape or form refering to anything to do with drellisdees's guide,your copy of it,or any other files,guides,etc. you have linked or posted on this site or yours.
he allready has root access and a recovery partition.
again,thanks for your input,but please stop confusing the issue with your references to merge guides.
for others watching this,a crude guide is now up on android forums:
http://androidforums.com/incredible-all-things-root/427344-2-3-4-root-downgrade-s-off.html
root 2.3.4 with unrevoked 3.22 has now been done successfully twice,and 1 has successfully roled back to 2.2.
more testers welcome
Confirmed. Worked for me. Was s on 2.3.4.
Sent from my ADR6300 using XDA App
My Incredible also is S-on with Verizon 2.3.4 OTA and never rooted. I'll give that "crude guide" a try tonight and report back how it went.
I'm just tired of all the low memory notifications and the constant force closes. Hopefully, I can have a custom mod installed tonight if things go well.
SUCCESS!!
Instructions from the website flawlessly for me.
I first rooted the phone. Then I tested it with some root only apps. They all worked. So ideally you can stop here if all you want is root but next OTA will take away root and then you'll be stuck again.
I completed all the steps and they worked. I was able to downgrade to 2.2 and then run unrevoke3 to root and also turn S-off. It did wipe the data clean. No files from my SDcard were deleted.
This is the time i've rooted my phone and the whole process took me an hour because I was being extra careful not to miss any steps. It all went smoothly.
glad it worked out for you. we finally worked out enuff bugs i put it up here as well: http://forum.xda-developers.com/showthread.php?t=1306400
efizzle seems to have dropped off the face of the earth everyone who reads this should make sure to click the "thanks" button in his first post. we wouldnt have it if hadnt figured out the 3.22 secret.(we would still have zergRush,but not root with access and the ability to make nandroids and backups with tibu so easily).
once again,thanks efizzle
Worked like a champ. I did a recovery back to 2.3.4 and it worked as expected. Also brought back all my force close issues. So I used ROM Manager and installed Cyanogen7 and am loving it.
clicking the thanks button a few times for this help
Ok, I'm on Linux, Ubuntu Lucid Lynx 10.04.3 to be exact, and I have adb installed. Where can I find the Linux version of unrevoked 3.22. I have found several places on the interwebz but I'm not sure if I trust those sources.
Help Please
Just like the op I have a Dinc that is on Gingerbread 2.3.4 and baseband 2.15.10.07.07 and desperate to have root. S-OFF would be nice, but root would be just fine for now.
More than happy to be the Guinea-pig on a Linux system.
sorry,i have no idea. i did a quick search and couldnt even find the windows version of 3.22 that i uploaded... i wanted to link it at its source,since it was emailed to me,but im not sure where he downloaded it from. you might follow the link in the first post credits to the original xda thread and ask on that thread,or send efizzle a private message and see if he can help you. in a worse case scenario,as long as you have 3.32 for linux,you could get temp root and downgrade with the "zergRush" method described in past #2. it doesnt require 3.22,but you wont be able to make a backup,or run titanium unless you can push SU,the binary,and busybox to their respective locations after acquiring a temp root.
Hi everyone
I was advising somebody on rooting their Desire HD.
We got as far as installing the 1.32 stock ROM and I stupidly (and now I regret it so damn much) forgot about radio S-offing the device first so we tried Eng-S-Off. That said do not turn off the device because the bootloader is corrupt.
Then we tried the Radio S off tool and that said Unknown error, possibly connection.
How can we fix this?
EDIT: Will installing an RUU fix it?
raze599 said:
Hi everyone
I was advising somebody on rooting their Desire HD.
We got as far as installing the 1.32 stock ROM and I stupidly (and now I regret it so damn much) forgot about radio S-offing the device first so we tried Eng-S-Off. That said do not turn off the device because the bootloader is corrupt.
Then we tried the Radio S off tool and that said Unknown error, possibly connection.
How can we fix this?
EDIT: Will installing an RUU fix it?
Click to expand...
Click to collapse
Ya it will just do that way and do the rooting again after following these steps.....
find the stock splash screen here: http://forum.xda-developers.com/showthread.php?p=15430340&highlight=stock#post15430340
Uncompress that and put the .img file in the same folder as your fastboot file (in the Android SDK, it used to be in the Tools folder but nowadays they put it in the Platform-Tools folder), then open a CMD window, (Make sure the file is called splash1.img) and type:
fastboot flash splash1 splash1.img
That will restore the stock splash screen.
To restore the software you have to:
1: Find a 1.32.405.6 RUU that matches the original state of your phone. 2: Flash that RUU 3: Use Visionary R14 to Temproot and then Permroot 4: The Jkoljo's Easy Radio Tool to change the CID back to stock (If you phone was unbranded it will be HTC__001)
Now its ready to root again...
Hope that helps.
No I'm saying because the bootloader is corrupt, will installing an RUU restore the original bootloader?
There is no custom splash screen. We got as far as installing the 1.32 ROM.
raze599 said:
No I'm saying because the bootloader is corrupt, will installing an RUU restore the original bootloader?
There is no custom splash screen. We got as far as installing the 1.32 ROM.
Click to expand...
Click to collapse
I honestly think people are just copying and pasting stuff they've read somewhere without thinking about what they're saying. The bulk of that is nothing to do with the query you asked (apart from maybe the line about the RUU); I mean, replacing the splash image?! How's that going to help with a corrupted bootloader? Let alone telling you to download the full Android SDK just for that
On topic: the RUU should do it, but I've never tried it myself so you're probably safer waiting for someone with some actual experience to confirm before you flash. I have seen that error mentioned in one of the guides I used back when I rooted (January time), so I'll see if I can dig that out.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
---------- Post added at 08:07 AM ---------- Previous post was at 07:42 AM ----------
Okay, found it: a few people were having "bootloader corrupt" issues using the One-click ENG S-OFF tool.
Try the advice in that post (or maybe search that thread a bit further for mentions of "corrupt") before you waste time flashing a RUU. IIRC you can do Radio S-OFF & ENG S-OFF in any order (the ENG S-OFF tool has a box to tick whether you have Radio S-OFF or not); I don't think that's the problem here.
Thanks I will try that later. It seems like from the thread that if you didnt get a superuser message on the phone, nothing actually happened to the bootloader. We didnt get a superuser message on the phone. So could it be a false alarm and safe to reboot?
EDIT: By the way what the other user copied and pasted, I wrote originally lol but I didnt want to say that then in response.
raze599 said:
Thanks I will try that later. It seems like from the thread that if you didnt get a superuser message on the phone, nothing actually happened to the bootloader. We didnt get a superuser message on the phone. So could it be a false alarm and safe to reboot?
Click to expand...
Click to collapse
Yeah, that should be fine. If you didn't allow it root access when you ran it then it's not going to have been able to do anything. Reboot, clear the request in your superuser app and start again.
You don't mention it, but I assume you've already used Visionary to permroot before you tried the S-OFF tool? Just a thought when you mentioned you didn't get the su request on the phone.
raze599 said:
EDIT: By the way what the other user copied and pasted, I wrote originally lol but I didnt want to say that then in response.
Click to expand...
Click to collapse
Lol this is quite funny. I was actually instructing him over skype and then when I left Skype last night he did something and it worked lol THANK GOD!
I have no idea what he did but wierd things happen when I'm not looking lmao
Still though, since we have had some major problems, do you recommend that we install an RUU and start again from scratch? Just to avoid any future problems?
EDIT: Yes it was Permrooted, the superuser came up when he tried it himself and it worked.
I wouldn't bother personally; as long as you're s-off it doesn't matter how you got there. It's not like the phone's going to be left half s-on or something.
Besides, why let him waste time redoing that when he should be using that time to flash a load of new ROMs
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
Thanks very much
After many hours of reading threads and trying different things, I am posting this.
I have HTC Incredible
Incredible XC Ship S-On
HBoot 0.92.0000
Radio: 2.15.10.07.07
Recovery: CWM v2.5.0.5
Was running Cyanogenmod 7
All was great with this phone (about 1 year) until it randomly started to constantly reboot 1 month ago. I tried to follow some other threads by downloading PB31IMG files, adding them to FAT32 sd card and running in HBOOT. I tried first upgrading the cyanogenmod7, then going to froyo 2.2 and a GB one. Some threads mentioned changing radio version first, tried that but nothing.
When I load PB31Img files from SD, froyo 2.2 says something along the lines of main version old.
When I try to change radio, PB31Img starts to load but does not let me continue and returns to HBoot with no new radio.
I am really not familiar with any phone and I would like to get this back to working. Any help is appreciated, but please be very clear. All I want is this phone to go back to stock, unrooted is fine. Anything to make it work.
Thanks,
griplegraple
griplegraple said:
After many hours of reading threads and trying different things, I am posting this.
I have HTC Incredible
Incredible XC Ship S-On
HBoot 0.92.0000
Radio: 2.15.10.07.07
Recovery: CWM v2.5.0.5
Was running Cyanogenmod 7
All was great with this phone (about 1 year) until it randomly started to constantly reboot 1 month ago. I tried to follow some other threads by downloading PB31IMG files, adding them to FAT32 sd card and running in HBOOT. I tried first upgrading the cyanogenmod7, then going to froyo 2.2 and a GB one. Some threads mentioned changing radio version first, tried that but nothing.
When I load PB31Img files from SD, froyo 2.2 says something along the lines of main version old.
When I try to change radio, PB31Img starts to load but does not let me continue and returns to HBoot with no new radio.
I am really not familiar with any phone and I would like to get this back to working. Any help is appreciated, but please be very clear. All I want is this phone to go back to stock, unrooted is fine. Anything to make it work.
Thanks,
griplegraple
Click to expand...
Click to collapse
Since you're s-on, it's useless to try flashing radios. You're very limited as to what you can do, as you're finding out. Your best bet would be to try the latest RUU (also known as PB31IMG.zip) from here:
http://dinc.does-it.net/Stock_Images/4.08.605.15/
You should be able to flash that through HBOOT even though you are s-on, as it is a stock image.
If you can't get any of the stock images to flash, the next line of attack would be to upgrade HBOOT and unlock the bootloader using HTCdev, as described in this guide:
http://forum.xda-developers.com/showthread.php?t=1600904
If you follow the instructions for downgrading, you will be able to flash the stock image of your choice. Then, re-lock the bootloader using HTCdev and you will be back to stock. Of course, if you follow the whole guide and get s-off, you'll have a lot more options of ways to tackle problems like this.
musical_chairs said:
Since you're s-on, it's useless to try flashing radios. You're very limited as to what you can do, as you're finding out. Your best bet would be to try the latest RUU (also known as PB31IMG.zip) from here:
http://dinc.does-it.net/Stock_Images/4.08.605.15/
You should be able to flash that through HBOOT even though you are s-on, as it is a stock image.
If you can't get any of the stock images to flash, the next line of attack would be to upgrade HBOOT and unlock the bootloader using HTCdev, as described in this guide:
http://forum.xda-developers.com/showthread.php?t=1600904
If you follow the instructions for downgrading, you will be able to flash the stock image of your choice. Then, re-lock the bootloader using HTCdev and you will be back to stock. Of course, if you follow the whole guide and get s-off, you'll have a lot more options of ways to tackle problems like this.
Click to expand...
Click to collapse
The first option above worked in my case. Phone is able to load up and seems to be working fine.
Thread moved. Please post all question threads here in Q&A in future.
Thanks
AvRS
Sent from my Nexus 4 using xda premium
griplegraple said:
Thanks for the reply. I will try the first option, but one thing I have noticed before is that when I use the adb method, I can't get "adb devices" command to work. It outputs "List of devices attached". In my device manager, I have ADB Interface ->HTC Bootloader with the android USB driver installed... Not sure if you can help on this.
Click to expand...
Click to collapse
That could be caused by having adb or the drivers improperly set up on your computer, or it could be because you didn't have USB debugging enabled in the phone's settings. You could try booting your phone into recovery and seeing if you can access it with adb from there if all else fails.