Related
i have tried everything possible with this phone to root it and nothing. Was wondering if someone would help me out??
I feel your pain and I've try the HTC dev. unlock with no luck I'm coming from the OG evo which was really easy to root ..
Sent from my PG86100 using XDA Premium App
go to htcevohacks.com i hace hboot 1.5 and it worked perfectly if u have the newest upgrade tho i dont think they have a root method out yet
Htcevohacks is easiest . And with the newest ota its still hboot 1.5
Sent from my PG86100 using XDA App
brandonaspencer said:
i have tried everything possible with this phone to root it and nothing. Was wondering if someone would help me out??
Click to expand...
Click to collapse
It would help us if you told us exactly what problems you are having.
Cool!! thanks!!
Sent from my PG86100 using XDA Premium App
Look at the roll up stickies. The directions are pretty clear. HTC method is going to be your only option
Sent from my Galaxy Nexus using XDA App
Rooting phone
brandonaspencer said:
i have tried everything possible with this phone to root it and nothing. Was wondering if someone would help me out??
Click to expand...
Click to collapse
have kinda problems have you had with rooting your phone.
HTC evohacks is very easy thanks !! For the help : )
Sent from my PG86100 using XDA Premium App
yami951 said:
Look at the roll up stickies. The directions are pretty clear. HTC method is going to be your only option
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I agree
Sent from my PG86100 using xda premium
Trying to root using HTC 1.5 with no success.
Hi to all I have tried to root using the HTC boot unlocker with no success. I was using the step by step instructions from HTC evo hacks. I got to the step at the command prompt where I put in the unlock code and I got this : C:\rootevo3dnew>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.152s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.161s
The phone screen asking me to unlock the bootloader never came up. Any help would be appreciated. BTW I have rooted at least 7 EVO 3D's. with no problems.
I'm stumped.
lilal100 said:
The phone screen asking me to unlock the bootloader never came up. Any help would be appreciated. BTW I have rooted at least 7 EVO 3D's. with no problems.
Click to expand...
Click to collapse
See the Guide/flashing Notes in my signature. You need to rerun the currently installed "FULL" Ruu or the the Latest RUU, then the unlock will work.
I did the HTCDev and unlocked it went to thread on downgrade from 1.5 hboot to 1.4 tried that and it did not work. I went to try the wire trick and this is what I get when I try to use the controlbear. the phone connects and goes through process but says the following...
======== ControlBear 0.6 beta for JuopunutBear S-OFF ==========
Starting up......
Connecting to device...
Searching device.....
Found device.....but device has no root!!
Press ENTER to exit.....
Any help would be helpful I have tried superuser but wont install, tried rootevo3dnew, temproot sensation Ect. everything says I need to be rooted.
I am running stock rom that shipped with phone and yes I did updates. I am Sprint CDMA 2.17 rom shipped, 1.5 Hboot. I have flashed roms and modded before but dont consider myself to be advanced. I have done flashing and installing roms with my old HTC Touch pro2 but alot easier on touch pro2 LOL... Please point me in the correct place I have beeen all over from this thread to that one and back and forth and yes I have search threads and I have tried them but still come back to the one with wire trick.. I am 1.5 with S-ON
inkjammer said:
I did the HTCDev and unlocked it went to thread on downgrade from 1.5 hboot to 1.4 tried that and it did not work. I went to try the wire trick and this is what I get when I try to use the controlbear. the phone connects and goes through process but says the following...
======== ControlBear 0.6 beta for JuopunutBear S-OFF ==========
Starting up......
Connecting to device...
Searching device.....
Found device.....but device has no root!!
Press ENTER to exit.....
Any help would be helpful I have tried superuser but wont install, tried rootevo3dnew, temproot sensation Ect. everything says I need to be rooted.
I am running stock rom that shipped with phone and yes I did updates. I am Sprint CDMA 2.17 rom shipped, 1.5 Hboot. I have flashed roms and modded before but dont consider myself to be advanced. I have done flashing and installing roms with my old HTC Touch pro2 but alot easier on touch pro2 LOL... Please point me in the correct place I have beeen all over from this thread to that one and back and forth and yes I have search threads and I have tried them but still come back to the one with wire trick.. I am 1.5 with S-ON
Click to expand...
Click to collapse
Ok, let's make sure we know where you are at to start with. When you use the vol and power button to boot to fastboot, does the phone show "unlocked". If not, I think you need to do the htc method again. I have not kept up recently, but I am not sure there is any method other than the HTC method that works every time for 1.5. I have used the HTC method on two phones without a problem, so that is the method I use.
Once you get that far, I used adb to push or flash the twrp image into the recovery section of the phone. Then you should be able to flash superuser via the install menu of twrp. There are threads that have detailed explanations on how this is done.
Yea, I had a bit of a learning curve from my TP2 also, but love this phone!
sonza said:
Ok, let's make sure we know where you are at to start with. When you use the vol and power button to boot to fastboot, does the phone show "unlocked". If not, I think you need to do the htc method again. I have not kept up recently, but I am not sure there is any method other than the HTC method that works every time for 1.5. I have used the HTC method on two phones without a problem, so that is the method I use.
Once you get that far, I used adb to push or flash the twrp image into the recovery section of the phone. Then you should be able to flash superuser via the install menu of twrp. There are threads that have detailed explanations on how this is done.
Yea, I had a bit of a learning curve from my TP2 also, but love this phone!
Click to expand...
Click to collapse
I am unlocked I did the HTC Dev and unlocked it. I have a stock rom (the one shipped on phone) all I have done is unlock it... I did try the controlbear and got what I posted on last post. I am Hboot 1.5 S-ON and stock rom is 2.17.651.5 HTC Sense 3.0 ANDROID Ver. 2.3.4... Like I said all I have done is Unlock and installed TWRP 2.2 and created a restore point and created a recovery and backed up my phone. All through Goo Manager. That is all I have done.
inkjammer said:
I am unlocked I did the HTC Dev and unlocked it. I have a stock rom (the one shipped on phone) all I have done is unlock it... I did try the controlbear and got what I posted on last post. I am Hboot 1.5 S-ON and stock rom is 2.17.651.5 HTC Sense 3.0 ANDROID Ver. 2.3.4... Like I said all I have done is Unlock and installed TWRP 2.2 and created a restore point and created a recovery and backed up my phone. All through Goo Manager. That is all I have done.
Click to expand...
Click to collapse
In my post Ive included a flashable SuperSU zip. What youll need to do is boot to recovery and install this zip. Then reboot. You should have superuser access then.
Still learning this forum so excuse any errors I make. I've spent the last 10 hours trying to fix the mess I created on my wife's Evo 3d. I was able to root my phone and it was relatively easy so I tackled hers as well and have gotten a bootloop I cannot figure out, 10 hours later. I'm on hboot 1.5. I unlocked the phone (using a pretty reliable video), loaded 4EXT Recovery then tried to load roms. Everything worked fine until the rom-loading portion. Since then, the phone loops, but once or twice it made it all the way to the main screen and before I could slide the ring, a read error message appeared next to the bars of service then the phone just completely reboots. Right now, the only thing I can get into is the bootloader and the clockworkmod v4.0.1.4, somehow I lost my 4EXT Recovery. I'm stuck and in dire straights as my wife is going out of town and will KILL me if I don't fix her phone. Please help! BTW, somehow I managed to NOT back anything up (stupidity on my part). Will I be able to get this thing back to stock at least or is it now a paperweight?
user22410 said:
Still learning this forum so excuse any errors I make. I've spent the last 10 hours trying to fix the mess I created on my wife's Evo 3d. I was able to root my phone and it was relatively easy so I tackled hers as well and have gotten a bootloop I cannot figure out, 10 hours later. I'm on hboot 1.5. I unlocked the phone (using a pretty reliable video), loaded 4EXT Recovery then tried to load roms. Everything worked fine until the rom-loading portion. Since then, the phone loops, but once or twice it made it all the way to the main screen and before I could slide the ring, a read error message appeared next to the bars of service then the phone just completely reboots. Right now, the only thing I can get into is the bootloader and the clockworkmod v4.0.1.4, somehow I lost my 4EXT Recovery. I'm stuck and in dire straights as my wife is going out of town and will KILL me if I don't fix her phone. Please help! BTW, somehow I managed to NOT back anything up (stupidity on my part). Will I be able to get this thing back to stock at least or is it now a paperweight?
Click to expand...
Click to collapse
Your not bricked by any means. And Im going to guess you tried to boot an ICS rom.. dont. They dont work with hboot 1.5. If you really want to go back to stock run the 2.17 RUU and youll be back to where you started. Another option is to download a GB rom and flash that. Not ICS. If your able to get to the bootloader than you can still load up 4ext recovery so you can flash the GB rom.
Edit: some hboot 1.5 users are lucky and can flash them if they used the correct VM firmware but majority of users have problems.
NineInchNails said:
Your not bricked by any means. And Im going to guess you tried to boot an ICS rom.. dont. They dont work with hboot 1.5. If you really want to go back to stock run the 2.17 RUU and youll be back to where you started. Another option is to download a GB rom and flash that. Not ICS. If your able to get to the bootloader than you can still load up 4ext recovery so you can flash the GB rom.
Edit: some hboot 1.5 users are lucky and can flash them if they used the correct VM firmware but majority of users have problems.
Click to expand...
Click to collapse
Thanks, I just tried flashing a rom that has taken it back to stock but I'm still in the bootloop. Should I stop flashing and simply locate the RUU?
22410,
It sounds like the kernel did not flash correctly with 4ext Recovery (next time, make sure u indicat S-on in its settings). I'm not sure if you were just stock 2.17 rooted or not, but use 7zip on your pc to open & extract/copy out the "boot.img" file from the rom, zip, etc you were using and copy it to your fastboot pc folder. Still have the Cwm 4.0.1.4 recovery.IMG file there too right (or the 4ext recovery.img file)? Ok...
- put phone in fastboot usb mode
From PC's fastboot command prompt type:
- " fastboot flash boot boot.img "
(this will reflash the kernel/boot image extracted from a rom)
If your recovery is screwed up:
- " fastboot flash recovery YourRecoveryFilename.img "
(ie: cwm_4.0.1.4_recovery.img or recovery.img, etc as listed in fastboot folder, to reflash a recovery to your phone).
With S-on, to properly enter a recovery for flashing ANYTHING you must:
- " fastboot boot YourRecoveryFilename.img "
(doesn't apply if using 4ext's Smartflash or TWRP's Dumlock settings. But you must have a bootable android OS/kernel first, once the flash is screwed it won't work).
If u have a Sprint CDMA EVO3D/HTC Unlocked & S-on (not Jbear s-Off), then the guide in my signature has more info.
Edit: as NIN said you will likely have problems flashing ICS roms with S-on (hboot version doesn't matter). If u are still unlocked & have a working recovery u can flash any gb Rom successfully after wiping system, data, & cache (or run superwipe zip). Meanrom GB v4.5 recommended.
Sent from my "Up all night, Sleep all day" EVO3D!
Hello everybody
The new ICS update for the ROGERS EVO 3D just came out yesterday, so I restored my phone to the original firmware (via restoring the backup I did in the recovery) and then proceeded to download the OTA update. After it finished, the phone rebooted into the recovery (i have 4-ext touch recovery) and started installing. After it finished, the phone rebooted and then got stuck on the white HTC screen. I managed to enter the recovery again and restore the original firmware again. What is that I'm doing wrong here? Here is some helpful info:
Rogers EVO 3D, GSM version
Unlocked bootloader (HTCDEV method), S-ON
carrier unlocked
HBOOT 1.49.0008
OS is rooted
I'm in the same boat but I'm not able to do a recovery. I went through the update process and when the phone rebooted it got stuck on the white htc screen. I can get it into the bootloader menu but when i choose recovery it starts but then i get an error with a pic of the device and the red yield sign. If i choose factory reset it just gets stuck at the white htc. I read some other posts and I saw that having an unlocked bootloader may cause issues with updates so that may be your issue as for me, I'm not sure what I can do. I may just need the actual update file to redo the update but I'm not sure where to find it.
Same here, but I don't get half way through the ota update before I see the red triangle and exclamation mark. Phone will boot into stock recovery (which I would assume you need instead of modded recovery) and the update starts, but doesn't complete. I pull the battery and the phone boots up normally. Just can't seem to get through the update. Could be something to do with being s-off I would guess.
EJ
madmajd said:
Hello everybody
The new ICS update for the ROGERS EVO 3D just came out yesterday, so I restored my phone to the original firmware (via restoring the backup I did in the recovery) and then proceeded to download the OTA update. After it finished, the phone rebooted into the recovery (i have 4-ext touch recovery) and started installing. After it finished, the phone rebooted and then got stuck on the white HTC screen. I managed to enter the recovery again and restore the original firmware again. What is that I'm doing wrong here? Here is some helpful info:
Rogers EVO 3D, GSM version
Unlocked bootloader (HTCDEV method), S-ON
carrier unlocked
HBOOT 1.49.0008
OS is rooted
Click to expand...
Click to collapse
Same problem but whit s-off
I have been predicting that this would happen... ICS failures with non-standard HBOOTs. Good luck.
Probably will have to wait for an RUU or custom.
I'd recommend using the GB ruu to get you back to full stock. Always found Rogers ota updates (possibly all carriers?) won't install if you're rooted or using a custom recovery.
I had to install the ruu via renaming the rom.zip to PG86IMG.zip and copying it to the sd card so that the bootloader would auto flash it. Running the ruu exe tossed up all kinds of errors.
It will put everything back to Rogers stock. After that just setup wifi and do the 2 Rogers OTA updates.
Once in ICS, it's easy peasy to get recovery and root back.
Also, for what it's worth, Go Backup is awesome for going rom to rom and not needing a full backup. Use it on rooted rom, then use it to restore after rooting new rom. Will do all your apk's and everything.
1st post here after years of lurking. Yay.
wikkid said:
I'd recommend using the GB ruu to get you back to full stock. Always found Rogers ota updates (possibly all carriers?) won't install if you're rooted or using a custom recovery.
I had to install the ruu via renaming the rom.zip to PG86IMG.zip and copying it to the sd card so that the bootloader would auto flash it. Running the ruu exe tossed up all kinds of errors.
It will put everything back to Rogers stock. After that just setup wifi and do the 2 Rogers OTA updates.
Once in ICS, it's easy peasy to get recovery and root back.
Also, for what it's worth, Go Backup is awesome for going rom to rom and not needing a full backup. Use it on rooted rom, then use it to restore after rooting new rom. Will do all your apk's and everything.
1st post here after years of lurking. Yay.
Click to expand...
Click to collapse
Alright thanks a lot
Just an update on what I did. I was able to reload the stock gb rom for rogers using the exe file, then I went through the 2 updates that came up when checking and ics is now up and running on my phone. However in my attempts of trying to fix the original problem, I managed to re-lock my bootloader before flashing to stock rom and I had s-on the whole time. hope this help.
i switched to stock like.. a week back?
jus got ota on 4th
i WAS rooted and using juopunutbear's hboot *u can jus get the hboot from their website*
so i jus flashed back stock recovery.. and updated.. and success.. lost root though.. and i was back to stock bootloader..
used the PG86IMG with juopunutbear's bootloader and 4ext recovery.. and flashed cwm supersu.. v0.91 i think.. i dunno.. latest one.. and bam.. im on stock.. rooted.. and works perfectly..
Possible sollution
Maybe try flashing one of the customized ROMs that are based on the latest OTA update. I'm sure Anryl's newest rom is blazing-fast and stable. You can find it in the gsm android development forum and flash it via recovery. Make sure you have the latest 4ext recovery installed, though.
where can a i find that stock rogers rom i modified mine and that might be the reason i get a security failure in hboot. s is on. when i run the ruu file in windows to downgrade i get error 155. when i run the the update from about phone. it locks up with blue android guy and yellow exclamation mark. i remove the battery and she boots fine with no changes.
I am trying to do same. Get stuck on HTC screen. I have S-ON. Was on cobra 2.4 prior.
If anyone can give details on how to fix it, it would be great! Please no saying "install exe". I need to know which exe etc.
just wanted to tell everyone that in order for the ota update to work properly, you need to be running stock unrooted firmware with a locked bootloader. Just relock your bootloader, reinstall the stock firmware, upgrade to ics via ota, then re-unlock and re-root.
Hi
I have a HTC EVO 3D from Rogers that was got messed up during changing networks... rooted the phone for no apparent reason... to now get a update for it for ics from the provider and it bricked the phone.
It's stuck at HTC boot screen, can get fastboot USB from bootloader. recovery gets a ! in a triangle and factory reset doesn't work, freezes at splash screen after restarting the phone. Was stupid not making a backup or searching for programs to back it up before I went ahead and clicked update
It has HTC boot-loader 1.49 s-on but is rooted.
I am looking for clear(fix my evo for dummies) step by step instructions with correct installation for my model of phone, HTC EVO 3D Rogers GSM, or anything that could replace the os to get my phone to be useful again I'm currently using my backup phone a HTC G1 HTC ftw
Try kingcobra's rom, ota from rogers will not boot due to the fact that your phone is rooted, kingcobra's rom is based on rogers ota, flash it and leave it.
Sent from my HTC EVO 3D X515m using xda premium
Davideichler7 said:
Hi
I have a HTC EVO 3D from Rogers that was got messed up during changing networks... rooted the phone for no apparent reason... to now get a update for it for ics from the provider and it bricked the phone.
It's stuck at HTC boot screen, can get fastboot USB from bootloader. recovery gets a ! in a triangle and factory reset doesn't work, freezes at splash screen after restarting the phone. Was stupid not making a backup or searching for programs to back it up before I went ahead and clicked update
It has HTC boot-loader 1.49 s-on but is rooted.
I am looking for clear(fix my evo for dummies) step by step instructions with correct installation for my model of phone, HTC EVO 3D Rogers GSM, or anything that could replace the os to get my phone to be useful again I'm currently using my backup phone a HTC G1 HTC ftw
Click to expand...
Click to collapse
Go to the gsm development forum and download the RUU for the phone, and restore it to stock unrooted OS. Before you do that though, make sure that your phone's BOOTLOADER IS LOCKED. Look up how to re-lock your bootloader. After you relock your bootloader, you can proceed with restoring the phone.
Soooo.... basically, what I'm getting from this is, if you like having a locked bootloader, CWM and root, don't bother trying to install this OTA update because it's a headache. Agree?
The phone's not mine, it's my wife's, and she doesn't want anything special or like the idea of me messing around in her phone.
I was about to install this late last night, just about to hit that button, then I thought, "what about the bootloader? what about root? what about the fact that it's now unlocked and being used on a carrier other than Rogers?"
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
Hello!
My current phone setup is:
2.13.651.1 710RD stock ROM
1.12.11.0809 baseband
Hboot 1.19
S-ON
htcdev unlocked
TWRP 2.1.8
rooted (SuperSU)
The phone is bugging me to take the 3.16 upgrade. Stock ROMs are fine...I won't be playing around with custom ROMs (don't have time right now), and I don't need S-OFF.
After reading and researching, I'm still not sure how to go about upgrading, or if it is a good idea. There seem to be issues with the 3.16 stock ROM and TWRP, a number of users having trouble gettings ROMs flashed in, etc.
From where I'm at now, is the 3.16 upgrade worth it?
What would the procedure be?
1) Back up with Titanium
2) Relock
3) Take the OTA upgrade
4) htcdev unlock
5) Install recovery and root (install what version of TWRP?)
6) Restore Titanium backup
Seems like something is missing between (2) and (3).
Thanks for any suggestions and advice!
Not 100% sure but I believe you need to flash a stock recovery for the ota to work. So step 2.5 would be flash stock recovery.
{ParanoiA} said:
Not 100% sure but I believe you need to flash a stock recovery for the ota to work. So step 2.5 would be flash stock recovery.
Click to expand...
Click to collapse
Gotta do that BEFORE relocking.
Ahhh yes...flashing the stock recovery before relocking. Thanks for the tip!
I'm still a bit confused about the touch sceen problem, and exactly when that problem occurs. According to some posts, it seems to affect some versions of TWRP. If I flash TWRP after taking the 3.16 OTA upgrade, will the touch screen work in TWRP?
Thanks again!
jbhtexas said:
Ahhh yes...flashing the stock recovery before unlocking. Thanks for the tip!
I'm still a bit confused about the touch sceen problem, and exactly when that problem occurs. According to some posts, it seems to affect some versions of TWRP. If I flash TWRP after taking the 3.16 OTA upgrade, will the touch screen work in TWRP?
Thanks again!
Click to expand...
Click to collapse
As long as you flash TWRP 2.4.1.0, your touch screen will work fine.
Captain_Throwback said:
As long as you flash TWRP 2.4.1.0, your touch screen will work fine.
Click to expand...
Click to collapse
Captain. I am new to being S-OFF. Can I take the OTA and it not affect my S-OFF state. This is the first time an OTA has come out and
my phone being S-OFF.
Unlocked
S-OFF
Recovery: TWRP 2.3.3
Device: HTC Jewel/PJ75100 (EVO 4G LTE) | Hardware Version: 0003
Baseband: 1.12.11.1119 | PRI: 2.87_003 | PRL: 25012
HBOOT: 2.09.2222
michaeldm said:
Captain. I am new to being S-OFF. Can I take the OTA and it not affect my S-OFF state. This is the first time an OTA has come out and
my phone being S-OFF.
Unlocked
S-OFF
Recovery: TWRP 2.3.3
Device: HTC Jewel/PJ75100 (EVO 4G LTE) | Hardware Version: 0003
Baseband: 1.12.11.1119 | PRI: 2.87_003 | PRL: 25012
HBOOT: 2.09.2222
Click to expand...
Click to collapse
If you're S-OFF, taking an OTA won't change that.
Captain_Throwback said:
If you're S-OFF, taking an OTA won't change that.
Click to expand...
Click to collapse
Thanks fort the help captain. been looking for that answer for the longest.
I ahve 2 more question.
1) When taking the OTA will it replace the recovery with a a stock recovery. I am running TWRP 2.4.1. Will I have to reflash it.
2) Will the OTA relock my bootloader. Do I have to unlock that as well? Is it necessary to be unlock if I am S-OFF?
Thanks for the help.
michaeldm said:
Thanks fort the help captain. been looking for that answer for the longest.
I ahve 2 more question.
1) When taking the OTA will it replace the recovery with a a stock recovery. I am running TWRP 2.4.1. Will I have to reflash it.
2) Will the OTA relock my bootloader. Do I have to unlock that as well? Is it necessary to be unlock if I am S-OFF?
Thanks for the help.
Click to expand...
Click to collapse
1) Yes, taking the OTA will replace your custom recovery with a stock one. You will need to reflash TWRP.
2) When you're S-OFF your bootloader is unlocked. You will just need to flash the latest DirtyRacun HBOOT so that fastboot commands will function, since it will be replaced by a stock HBOOT with the OTA.
You'll have to first flash the DR HBOOT via PJ75IMG.zip, then you'll be able to fastboot flash TWRP.
Captain_Throwback said:
1) Yes, taking the OTA will replace your custom recovery with a stock one. You will need to reflash TWRP.
2) When you're S-OFF your bootloader is unlocked. You will just need to flash the latest DirtyRacun HBOOT so that fastboot commands will function, since it will be replaced by a stock HBOOT with the OTA.
You'll have to first flash the DR HBOOT via PJ75IMG.zip, then you'll be able to fastboot flash TWRP.
Click to expand...
Click to collapse
Thanks you. don't want to seem dense. I am newbie. I understand what you are saying. Is there an order in which these things are done., Is there a link with the steps for dong the previous stated instructions. In which order do I need to do this.
Should I take the OTA first and then try to flash. or do all of the flashing first then take the OTA? I kinda of confused by the order. I already have the latest
HBOOT and RUU (RUU 3.15.651.16 - HBOOT 2.09) from DR. That's How I go S-OFF. If there a set of sequential instructions you can point me to I would be greatly appreciative.
Just an update on how the upgrade went...
The upgrading to 3.16 part went fine, and TWRP 2.4.0.1 is working fine. The restore from Titanium part didn't work great.
First, Titanium says that you can make an adb backup and restore from it after unlocking/rooting. So after the upgrade and before rooting, I made an adb backup since it appeared that all (or most anyway) my settings were retained over the upgrade. That didn't work, as Titanium said the adb backup was corrupted or unrecognized.
Next, when trying to restore my Titanium backup, there was some glitch where I could change to the folder where my Titanium backup was located on the backup folder selection screen (and a backup was recognized there), but this change wasn't internally accepted, and thus when going back to the main status screen, the default folder location was shown, and no backups were found to restore. After rebooting the phone a couple of times, this problem sovled itself, and I was able to restore. For the most part, everything was restored, other than a couple of widgets and settings. I sent a request to Titanium about the adb backup issue, but never got a response so I proceeded to restore the Titanium backup.
However, now I have another problem, but since it's a different topic, I'll start a new thread for that.
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 !