So recently I decided to delve into the world of Rooting. So i did a little research and finally decided it was time.
So I rooted my Evo 4G LTE using regawmod
Well it worked all fine and dandy. Until I decided to unroot and use an RUU so that i could root in a different method and flash a ROM on it then.
First i went into SuperSU and told it to unroot. I wasn't worried about trying to remove the tampered tag as i was just goin to root the device again. But SuperSU told me that the unroot failed.
So i continue to find a different method, more thorough. I came across a guide on HTC hacks on how to unroot the device, reflashes the original ROM on it and as well removes the tampered tag. I try it and use the correct (or so i think) RUU (the 1.13.651.1). The RUU told me it couldn't do it and gave me the 155 error, wrong ROM image as i have found out. In the actual RUU process it says to update from 1.13.651.1_R2 to 1.13.651.1 (I'm not sure if that is pertinent information)
So i recover boot the phone back up and it doesn't seem to have any problems. Except SuperSU is gone (tried reinstalling and got the no SuperSU binary error when i ran it)
So any help as to how to flash my phone back to normal so i can go about my business?
RonniEdwards said:
So recently I decided to delve into the world of Rooting. So i did a little research and finally decided it was time.
So I rooted my Evo 4G LTE using regawmod
Well it worked all fine and dandy. Until I decided to unroot and use an RUU so that i could root in a different method and flash a ROM on it then.
First i went into SuperSU and told it to unroot. I wasn't worried about trying to remove the tampered tag as i was just goin to root the device again. But SuperSU told me that the unroot failed.
So i continue to find a different method, more thorough. I came across a guide on HTC hacks on how to unroot the device, reflashes the original ROM on it and as well removes the tampered tag. I try it and use the correct (or so i think) RUU (the 1.13.651.1). The RUU told me it couldn't do it and gave me the 155 error, wrong ROM image as i have found out. In the actual RUU process it says to update from 1.13.651.1_R2 to 1.13.651.1 (I'm not sure if that is pertinent information)
So i recover boot the phone back up and it doesn't seem to have any problems. Except SuperSU is gone (tried reinstalling and got the no SuperSU binary error when i ran it)
So any help as to how to flash my phone back to normal so i can go about my business?
Click to expand...
Click to collapse
fastboot relock ur bootloader then run ruu
inst1029 said:
fastboot relock ur bootloader then run ruu
Click to expand...
Click to collapse
Quick instruction on how to do that by chance?
What Ronni said x2. Also used the regawMod to unroot. I want to relock my bootloader and run the ruu also. A tutorial on how to relock would be appreciated. Thanks!
Sent from my EVO using xda app-developers app
shleppyjoe said:
What Ronni said x2. Also used the regawMod to unroot. I want to relock my bootloader and run the ruu also. A tutorial on how to relock would be appreciated. Thanks!
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
You can try this http://www.youtube.com/watch?v=5yS7yy4XVA4
Related
Building on the Framework of my other apps, I present to you my easy, quick and efficient Rooting solution for ANY HTC Device.
Check out the link for more info and Download:
http://forum.xda-developers.com/showthread.php?t=1870652
Sent from my HTC Desire S using Tapatalk 2
this works for all htc phones?what about if my bootloader is unlocked but not rooted.
Sent from my HTCEVOV4G using xda premium
ddurb said:
this works for all htc phones?what about if my bootloader is unlocked but not rooted.
Sent from my HTCEVOV4G using xda premium
Click to expand...
Click to collapse
Try it and see!
Need some help!
I decided to give this a try since it sounds like it has some potential to help get users rooted from stock configurations, or after flashing an OTA or RUU, even though I have been S-OFF via JuopunutBear for a while now. I figured I would try the rooting with an insecure boot.img first since that works for S-OFF, but got an error saying I didn't have the right boot.img installed. I had just flashed the latest Sprint ICS RUU.exe from Windows and wanted to see how this tool would work in that scenario.
So since it wanted a boot.img that I didn't have, I tried the universal exploit option but that gave me an error at the Windows level. The phone rebooted into recovery and I had to pull the battery and reboot into the stock ROM, which was fine.
I have attached screenshots of the info I got when I first started the app, the error I got when I tried to root with the exploit (I'm on Windows 7 Ultimate, Service Pack 1) and a text file containing the contents of the message in the scrollable details text box.
I'm also curious what bootloader gets flashed if that option is selected.
Please advise.
Edit: Just noticed that the version went from 1.1.10 that I downloaded yesterday to 1.1.12 today so I will reload the RUU and try that version.
ramjet73
ramjet73 said:
I decided to give this a try since it sounds like it has some potential to help get users rooted from stock configurations, or after flashing an OTA or RUU, even though I have been S-OFF via JuopunutBear for a while now. I figured I would try the rooting with an insecure boot.img first since that works for S-OFF, but got an error saying I didn't have the right boot.img installed. I had just flashed the latest Sprint ICS RUU.exe from Windows and wanted to see how this tool would work in that scenario.
So since it wanted a boot.img that I didn't have, I tried the universal exploit option but that gave me an error at the Windows level. The phone rebooted into recovery and I had to pull the battery and reboot into the stock ROM, which was fine.
I have attached screenshots of the info I got when I first started the app, the error I got when I tried to root with the exploit (I'm on Windows 7 Ultimate, Service Pack 1) and a text file containing the contents of the message in the scrollable details text box.
I'm also curious what bootloader gets flashed if that option is selected.
Please advise.
ramjet73
Click to expand...
Click to collapse
You need htcdev unlock so you can get Su. Then it should work
Sent from my PG86100 using Tapatalk 2
VictoriousShooter said:
You need htcdev unlock so you can get Su. Then it should work
Click to expand...
Click to collapse
With S-OFF? That's strange, since the OP says that both options work with S-OFF. Also, I couldn't find any mention of htcdev unlock in either the OP or the application when it was running.
I'm not going to htcdev unlock since my bootloader is locked after JuopunutBear and I don't want to have to deal with the ***RELOCKED*** status. I guess I could try flashing a custom bootloader after running the RUU that will allow the fastboot commands, but that can only be done by S-OFF users and by the time that's done it's probably faster to go into fastboot and flash the custom recovery, then the superuser .zip or a rooted ROM from recovery.
I'm not sure where this tool fits exactly, but it sounds like it's mostly useful for people that have done the htcdev unlock but are still S-ON and want to root more easily. If that's the case, they can run this, then boot into Android and flash a custom recovery from an app like 4EXT or Flash Image GUI without having to use fastboot for either superuser or the recovery. Is that the gist of it?
BTW, my results with version 1.1.12 are attached. I got farther this time, but it failed on the temp root.
ramjet73
The errors seem to be causing confusion. If everything else says okay but the Universal Exploit says Failed then this means the exploit has been patched on the stock Rom you are trying to run it on.
Also only rooting via insecure boot.img requires s-off. Universal root will work with s-on if the exploit hasn't been patched.
Sent from my HTC Desire S using Tapatalk 2
lyriquidperfection said:
The errors seem to be causing confusion. If everything else says okay but the Universal Exploit says Failed then this means the exploit has been patched on the stock Rom you are trying to run it on.
Also only rooting via insecure boot.img requires s-off. Universal root will work with s-on if the exploit hasn't been patched.
Click to expand...
Click to collapse
So in other words, this tool won't work using the "universal exploit" (in quotes because I guess it's not really universal) on the official Sprint ICS build (2.89.651.2) for the Evo 3D, which is what I flashed via RUU.exe right before running it, regardless of the S-ON or S-OFF status? Would it work with an "insecure boot.img" if we are S-OFF and if so how would we set that up?
Assuming someone wanted to root the latest Sprint GB build (2.17.651.5) for the Evo 3D, what advantages does this tool provide over flashing a custom recovery and superuser .zip file from fastboot on a PC?
I'm not trying to be negative, just want to be clear on when someone on our device would benefit from using it.
ramjet73
ramjet73 said:
So in other words, this tool won't work using the "universal exploit" (in quotes because I guess it's not really universal) on the official Sprint ICS build (2.89.651.2) for the Evo 3D, which is what I flashed via RUU.exe right before running it, regardless of the S-ON or S-OFF status? Would it work with an "insecure boot.img" if we are S-OFF and if so how would we set that up?
Assuming someone wanted to root the latest Sprint GB build (2.17.651.5) for the Evo 3D, what advantages does this tool provide over flashing a custom recovery and superuser .zip file from fastboot on a PC?
I'm not trying to be negative, just want to be clear on when someone on our device would benefit from using it.
ramjet73
Click to expand...
Click to collapse
Ramjet, I have tried it too and end up where you are at. I have done the HTC unlock too.
Can someone show the step by step because I hate to presume I'm doing it right.
I have the phone set and on home screen. I run the program and fails.
I reboot the fone into the boot screen (pwr/vol dn) and select fastboot (pwr press once) then the program works and then fails at the temp thingy..
Alright I will try to recap what ive done today. I Was rooted with s-off via the thunderbolt tool and had the new ICS rom installed and running fine. But I decided to sell it so I used the thunderbolt tool to unroot and return to stock.
All was going well then in the boot-loader the update failed and i got stuck with boot-loader locked security warning, which would not let me do anything, was stuck in the boot-loader.
After some searching I found a link to unlock the boot-loader via htcdev to fix the security warning and allowed me to finally boot back into the rom but the phone kept shutting down after it booted up past the thunderbolt screen. So after searching I found this link http://www.thunderboltforums.com/forum/htc-thunderbolt-help/7853-how-fix-security-warning.html and used the 2nd method to fix it since I still have a custom recovery on the phone. Now my problem is I am once again trying to get s-off through the thunderbolt tool like it says in the guide but every time I use the tool it says Starting up... and does nothing. Bascially im now stuck with s-on and an unlocked boot-loader. oh I tried to relock the bootloader but it just gives me a security warning again and im stuck in the bootloader again.
Any Ideas?
Alright never-mind I just used the Revolutionary 0.4 program and gained "revolutionary" in the pink field and s-off again so im good there again.
The thunderbolt tool is still stuck at "starting up"..., is there another way to get the tbolt back to stock condition?
dlahmeyer said:
Alright never-mind I just used the Revolutionary 0.4 program and gained "revolutionary" in the pink field and s-off again so im good there again.
The thunderbolt tool is still stuck at "starting up"..., is there another way to get the tbolt back to stock condition?
Click to expand...
Click to collapse
If you have S-off then just grab a stock RUU (easiest probably gingerbread) and flash the RUU in hboot. This will completely return your phone to stock as well as unroot you. If you wish to keep root then flash a leaked RUU that someone put up.
Jeagle88 said:
If you have S-off then just grab a stock RUU (easiest probably gingerbread) and flash the RUU in hboot. This will completely return your phone to stock as well as unroot you. If you wish to keep root then flash a leaked RUU that someone put up.
Click to expand...
Click to collapse
So how the hell do you do that?
fillyo said:
So how the hell do you do that?
Click to expand...
Click to collapse
If you're already rooted go to the development section and download the new radio and put it on the root of your sd card, rename it to PG05IMG.zip, reboot into the bootloader. The bootloader will automatically scan for the update and ask it you want to update. Select yes. Once it is finished and the phone boots back up. Use a file manager to browse to the radio and rename it. Then download and flash the official ics build. Don't confuse it with the leak. The leak is a worthless piece of crap and doesn't come close to how much better the ota is.
Sent from my ADR6400L using Tapatalk 2
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
brownsfan said:
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
Click to expand...
Click to collapse
So I think I found out what I did. 2.28 is the Global version. I must of rooted that version and flashed roms. I wanted to unroot and get back to stock software version.
Where should I go from here? Is there an RUU for the ICS Global? I can not seem to find one.
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Thingula said:
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Yes I can unlock again and that does get me unstock from the boot screen but still cant get where I want. Hmm.
I wonder if you can fastboot-flash the older kernels, using a computer, then flash the old stock ROM, lock the bootloader, then run an RUU.. Can anyone confirm this? Sounds too simple to work on an HTC phone.
Edit: No, of course that doesn't work. Sorry, I can't really offer any more help.. I'll have to just hope that someone more knowledgeable can take over.
Sent from my ADR6425LVW using xda app-developers app
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Very much so! Thank you. If I could hit the thanks button 10x I would.
Im sure im not the only only to have the Hboot 2.28 issue.
hey man you still around ? i need some help with a situation like this
dust906 said:
hey man you still around ? i need some help with a situation like this
Click to expand...
Click to collapse
I replied to you in your thread.
S-On Locked stock !
mikeyk101 said:
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Click to expand...
Click to collapse
This guide was FREAKING AWESOME. It led me to finally after 2 years go S-Off (wire trick) to do RUU, etc. Have to return phone and have already got replacement. Crossed my fingers and everything looks stock stock stock !
So this is what happened .
i was stuck on 2.07 update with moonshine s-off and fully unlocked with root.
Every thing was going well but really wanted the kitkat update.
so i followed this guide http://forum.xda-developers.com/showthread.php?t=2612740 to RUU.
which got me to 3.06.
even got to keep my s-off status.
downloaded the 4.4.2 OTApks.zips and updated one at a time through stock recovery.
still maintained my s-off status in kitkat..
attempted root with weaksauce.
gained root.
SUCCESS!
flashed TWRP2.7.
still going well
. this is where it all went down hill.
attempted to unlock boot loader without a device wipe.
i used the unlock_boot loader.zip from this thread http://forum.xda-developers.com/showthread.php?t=2160677.
and it worked!!
FINALLY I GAINED S-OFF ROOT AND UNLOCKED.
so i reboot the device and Unfortunately Verizon Login has stopped.
over and over again.......
Had to factory reset the device.
now weaksasuce isnt working for me poo.
o well. if i could do it over again i would see if kingo htc unlock would work.
i hope this helps out others having issues with root....
Now im S-off and unlocked.
but i cant gain root.
any advice is suggested.
Flash supersu zip from Twrp recovery. Should give you root.
Sent from my HTC6435LVW using xda app-developers app
use this supersu!
Flash SuperSu
Epiel said:
use this supersu!
Flash SuperSu
Click to expand...
Click to collapse
I ended up fastboot flashing a custom recovery . And used the recovery flashable superus. . I was trying to avoid this method because of the Dr eloper logo that appears but I saw a thread some where where somebody already patched the hboot that removes that bs.
Okay, here's the biz. My wife's phone needs updated, and I'm not sure of the best way to do it. She's rooted and I want to keep it that way, as she needs her wifi-tether.
She's not s-off. I tried using moonshine and rumrunner to no avail, even though I had met all pre-requisites. rumrunner recommended I flashed a less-stable kernel and try it again. I'm not real interested in doing that.
I was trying to s-off so i could flash the OTAs that are on xda.
I have studied posts on here for about 4 hours now and have not come up with a solid answer.
The only things we need are root and the newest 3.17- firmware and possibly radios. Can anyone send me to the right place?
Can I just ruu the newest software?
Please. Thanks will be given.
Phone specs:
freshly ruu android 4.0.4
sense 4.1
software 2.13.651.1
s-on
bootloader unlocked
hboot 1.19.000
radio 1.12.11.0803
Check the top link in my sig. There is a link to all applicable RUU's at the bottom of the first post (I recommend reading the entire thread), including the 3.17 RUU and the newer 4.13 RUU. Running the RUU will update your software, firmware, HBOOT, etc. The RUU is probably the quickest way to get everything up to date, in my opinion. Just download whichever RUU you want to install to your computer, connect your phone to your computer while the phone is booted to the OS, double-click the RUU file and follow the on-screen instructions on your computer. You may also want to install HTC Sync to your computer, as well. After running the RUU you'll need to unlock your bootloader again, install a custom recovery and SuperSU for root access. If you want to S-off the phone once it's updated, again, check the top link in my sig for further info.
Sent from my HTC device
I tried using the ruu for the newest 4.XX and it wouldn't work. I guess I should just use 3.17.xxx?
NVM, I forgot to relock the bootloader before I tried the ruu.... now it's working. Thanks
btyking said:
NVM, I forgot to relock the bootloader before I tried the ruu.... now it's working. Thanks
Click to expand...
Click to collapse
Glad you got it going:thumbup:
Sent from my HTC device
Hey I'm trying to use windroid to unlock the bootloader again, but it's not recognizing the phone's status.. any help on unlocking that bloader?
Again, NVM I had to authorize the debugging on my phone.
Okay, I've ruu to the newest ota, which is 4.XX- and I have TWRP 2.7.0 but I can't figure out how to root it. I have tried flashing both of the super user files from the linked page in your sig, to no avail. I tried to flash them from twrp. Nothing. One app says it needs binaries, and the other one doesn't open. Not sure how to root at this point? I tried to push the superuser.zip files through adb shell and that didn't work either. stumped...
btyking said:
Okay, I've ruu to the newest ota, which is 4.XX- and I have TWRP 2.7.0 but I can't figure out how to root it. I have tried flashing both of the super user files from the linked page in your sig, to no avail. I tried to flash them from twrp. Nothing. One app says it needs binaries, and the other one doesn't open. Not sure how to root at this point? I tried to push the superuser.zip files through adb shell and that didn't work either. stumped...
Click to expand...
Click to collapse
You need to use the TWRP from Captain's thread.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Okay, thanks, got it. Do I need a different kernel to s-off with rumrunner?