So, one of my phones is fine, the other one bricked hard.
Plugging it in to mount to the pc yields a prompt to format it in order to use it.
It seemed to have loaded JB (and MeanBean) when it would not boot.
The bootloader now says Tampered and Relocked.
And the old ICS RUU of course does not work, since JB is partially (unsuccessfully loaded.
Any ideas?!?
Thanks.
Well if you can turn the device on and get into bootloader you are not bricked just in a bad situation
Sent from my EVO using Tapatalk 2
ronnienyc said:
So, one of my phones is fine, the other one bricked hard.
Plugging it in to mount to the pc yields a prompt to format it in order to use it.
It seemed to have loaded JB (and MeanBean) when it would not boot.
The bootloader now says Tampered and Relocked.
And the old ICS RUU of course does not work, since JB is partially (unsuccessfully loaded.
Any ideas?!?
Thanks.
Click to expand...
Click to collapse
OK I have been here.
Here is what you do:
1) Unlock your phone again using the HTC Devunlock method.
2) Reload TWRP
3) Load the stock ICS Kernel via fastboot (its the boot image file in the main zip).
4) Relock
5) Flash the stock RUU
Treat as stock phone and do what you need/want with it.
The thing that is causing problems is that likely the phone is relocked but the wrong boot.img is loaded. It will then fail checksums etc. causing all sorts of issues. In my case I wanted to load a rom for getting S-Off so I loaded the one mentioned in the old LazyPanda thread instead of the stock RUU. So I did the above and it worked just fine.
ronnienyc said:
So, one of my phones is fine, the other one bricked hard.
Plugging it in to mount to the pc yields a prompt to format it in order to use it.
It seemed to have loaded JB (and MeanBean) when it would not boot.
The bootloader now says Tampered and Relocked.
And the old ICS RUU of course does not work, since JB is partially (unsuccessfully loaded.
Any ideas?!?
Thanks.
Click to expand...
Click to collapse
Are you able to go to recovery from bootloader ?
Sent from my lair.
I have been off-line for a while, but looks like I figured it out.
Reunlocked, insatlled TWRP again, flashed MeanBean (I had already installed the JB kernel) and now it works.
I think the issue was not using the latest TWRP and/or mixing up the JB MeanBean with the ICS MeanRom.
It was not my finest, hour (took all day to sort this out), and thanks for the suggestions!
I am stuck in bootloader and not sure how much longer my battery will last like this.
I downloaded the drivers, the RUU, framework 4.1... all kinds of things. the last thing i tried, [ROOT] RegawMOD EVO 4G LTE Rooter | Updated 09.07.12, says that my phone is not a Sprint 4G EVO LTE.
can someone be more help other then just say run the HTC dev unlock. I rooted my phone day one and can't remember the exact way I did it. Can I reroot from bootloader? I have Android Sdk tools and could push files with adb and the proper help.
http://htcevohacks.com/htc-evo-4g-l...tc-evo-4g-lte-unlock-bootloadertwrp-recovery/
I'M BACK!!! took me forever but this site helped me. Looks like somehow I lost my Nand backups but at least I have a phone.
This is not even a soft brick, just restore your nandroid and you should be fine.
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!
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
I had much the same problem with my cdma, hboot 1.5, S-On shooter. When I was S-On none of the ICS roms would work. The all bootlooped on me. If you follow the rooting method found here on xda, it will get you back to a stock Rooted GB Rom.
go into hboot -> fastboot USB-> run command dos -> fastboot cwm-4.0.1.4-shooter.IMG -> flash the 2.17 firmware-> enjoy.
I had to S-off with Juopunutbear, then re-run that root/flash to get past the bootloops.
Sent from my Shooter using xda app-developers app
Unfortunately I have tried that and it still is not working.
My only suggestion would be to try it a few times, other then that, its above my head.
Sent from my shooter using xda app-developers app
rookiemistake said:
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
Click to expand...
Click to collapse
Have you tried one of the ruu exe files that you run from your computer? If you are trying to go stock, you should be able to relock the bootloader and run the ruu and that's it.
Sent from my ICS 3VO with Tapatalk 2
First of all I want to thank everyone that has been attempting to assist me with my problem. I have tried to relock since I am on htcdev unlock and then run an ruu force via my computer. I get an installation aborted error when trying to flash pg86img via recovery. I don't know what else to say.
You can't flash a bootloader zip from recovery. You have to flash it from hboot. Also make sure the zip is named correctly "PG86IMG.zip" without the quotes. Also make sure the zip is on the root of your sd as in not in any folders. Once you've named the zip correctly and placed it correctly then power off the phone. Hold down the volume down button and tap the power button. You should boot into the bootloader wait until the phone recognizes the zip and follow the on screen instructions. Hopefully this helps.
#Root-Hack_Mod*Always\=LTE
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
rookiemistake said:
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
Click to expand...
Click to collapse
To get the ota release (if it ever comes ) I do believe you will need to be locked and running the existing gingerbread rom. While I am not positive, I think the system uses the props file to determine if an update is applicable, and it will likely not recognize the teamgenesis rom version as being upgradeable.
Now I will likely get flames for saying this, but if you want to put the meanrom v2.4 of ICS on the phone, it can be done with s-on, you just need to follow the correct process. I ran that rom for a while, and it is very stock like, stable, and has a few enhancements that you will not find on a non-rooted stock rom. I never found anything wrong or not working with that rom.
To get it to load, first I downloaded flashimagegui from market, put the meanrom zip file on the sd card and made sure I had a recovery that I could get into. I am using TWRP v2.1.1, lots of folks talk about others like ext4, and I am only going to say use whichever you like, after all it is your phone.
Then with the phone unlocked via the htc method, I started the flashimage app, and browsed to the meanrom file. It extracted the kernel and flashed it. Once that was done, with clear cache buttons selected, rebooted to recovery, and used the install menu selection of TWRP to again flash the same rom file. Once it flashed the file, selected clear cache and dalvik just to be safe, selected reboot system, and it worked great.
Have a great weekend.
So, apparently I am still doing something wrong. I have put the pg86img on the root, relocked to the bootloader, and let it run it's course. However, it will get through with reading it and stops and does not finish anything with loading the system information. I have also tried to run the ruu via usb connection. I keep running into a c++ issue saying runtime error. I have wiped everything and thankfully I did make a backup of the rom and other information that I was runing so I can currently fall back on that.
I am on hboot 1.5, 2.17, and teamgenesis ICS rom for evo 3d.
Apparently there have been rumors that Sprint has finally released the ICS OTA, not that it really matters anymore, but I have run into a few interesting glitches, such as WIFI not staying connected while asleep or disconnecting.
If I have to I am willing to pay to do a netmeeing with someone in order to be able to fix this.
Sorry if it sounds like I am getting frustrated, but I have tried every walkthrough that I have found and have not had any luck with any of them.
Please help.
I forgot to say I am s-on
Ok this is odd. I tried to go fully stock from Newt Sense 5 1.0.4 ROM so I can completely install the rom from the ground up (I had black boxes show up when the 1.0.4 patch was installed on some menus and crashes in settings).
I relocked the bootloader and used RUU which wiped the CWM Recovery and the ROM from the device but then it gave me this error and now the phone will not boot past recovery and will not allow me to re-unlock my bootloader for whatever reason. Any ideas? Any help would be appreciated since my phone is pretty much a paper weight right now.
xraytid said:
Ok this is odd. I tried to go fully stock from Newt Sense 5 1.0.4 ROM so I can completely install the rom from the ground up (I had black boxes show up when the 1.0.4 patch was installed on some menus and crashes in settings).
I relocked the bootloader and used RUU which wiped the CWM Recovery and the ROM from the device but then it gave me this error and now the phone will not boot past recovery and will not allow me to re-unlock my bootloader for whatever reason. Any ideas? Any help would be appreciated since my phone is pretty much a paper weight right now.
Click to expand...
Click to collapse
There is always something wrong with his ROMs, including the ones he made for the Thunderbolt. . I tried flashing one of his a week ago. The phone would not connect to the network, wifi worked. I ran a different rom still no connection, ran the RUU, no luck. I had a new sim put in, and wound up getting the unit replaced.
Are you S-Off? Are the proper drivers for your computer installed?
http://forum.xda-developers.com/showthread.php?t=1928439
Also did you have the eng hboot and did you switch back to the pre ota hboot before relocking? Cause if you locked with eng then that will definitely brick your phone. If that didn't happen and you can still get into fastboot then it's just your on the new hboot and RUU won't run with the new hboot. Just flash the pre ota hboot then run the RUU that should make it run.
Sent from my 5 Senses of DNA
RLGL said:
There is always something wrong with his ROMs, including the ones he made for the Thunderbolt. . I tried flashing one of his a week ago. The phone would not connect to the network, wifi worked. I ran a different rom still no connection, ran the RUU, no luck. I had a new sim put in, and wound up getting the unit replaced.
Click to expand...
Click to collapse
Hmmm. I've used his ROMs on my last three devices without issue. At all. Including the DNA.
Sent from my Nexus 10
xraytid said:
Ok this is odd. I tried to go fully stock from Newt Sense 5 1.0.4 ROM so I can completely install the rom from the ground up (I had black boxes show up when the 1.0.4 patch was installed on some menus and crashes in settings).
I relocked the bootloader and used RUU which wiped the CWM Recovery and the ROM from the device but then it gave me this error and now the phone will not boot past recovery and will not allow me to re-unlock my bootloader for whatever reason. Any ideas? Any help would be appreciated since my phone is pretty much a paper weight right now.
Click to expand...
Click to collapse
Are you on the 2.04 firmware at all?
Sent from my HTC6435LVW using XDA Premium HD app
try this
xraytid said:
Ok this is odd. I tried to go fully stock from Newt Sense 5 1.0.4 ROM so I can completely install the rom from the ground up (I had black boxes show up when the 1.0.4 patch was installed on some menus and crashes in settings).
I relocked the bootloader and used RUU which wiped the CWM Recovery and the ROM from the device but then it gave me this error and now the phone will not boot past recovery and will not allow me to re-unlock my bootloader for whatever reason. Any ideas? Any help would be appreciated since my phone is pretty much a paper weight right now.
Click to expand...
Click to collapse
Youre not bricked. As long as you can get to the bootloader menu there is hope. You have to re unlock using the unlock token HTC emailed you through fast boot . fastboot Flash unlocktoken unlock_code.bin I believe is the command. Then after reflash your ROM through recovery
Flash twrp recovery if possible via fastboot if you don't already have it, adb sideload a stock rom
Sent from my HTC6435LVW using xda app-developers app
Hello. So I've tried multiple times flashing ROMs to my device, and have always had problems somewhere along the line. The furthest I got was successfully flashing this ROM, but it ended up in a boot loop. I believed it was due to my device being S-ON, even though I've successfully rooted and unlocked my bootloader via HTCdev and thus I've been attempting to get S-OFF. I tried JuopunutBear but got an error message related to checking my adb and fastboot drivers (Which I'm fairly sure are up to date and working) and I think the problem is I am on HBOOT 1.57. I've been attempting to downgrade using this guide (Which uses Revolutionary to get S-OFF in which case I wouldn't need JuopunutBear). I only got a bit of the way in, however, before I got stuck. After relocking my device it tells you to put the RUU zip on your device, but my computer isn't detecting my device and I'm stuck in the bootloader. I've tried shutting it off, trying all the options in the bootloader, taking out the battery, entering commands into adb, and probably some other things I've forgot, but I'm still stuck on the bootloader and my device isn't detected at all on my computer (Either in command prompt or in the explorer window).
Essentially what I'm asking here is:
How do I get my phone unstuck from bootloader?
Do I need S-OFF to be able to flash ROMs?
If I don't need S-OFF, what was I doing wrong? Should I try a different ROM?
And I suppose I may as well ask if that's a worthwhile ROM. I want something that optimizes my device and allows for custom themes, but otherwise I'm not too picky.
Specs:
Windows Vista (With ADB and fastboot, as well as HTC Sync and other phone drivers. Essentially I think I have all the software I'd need installed.)
HTC EVO 3D CDMA with Virgin Mobile as the carrier.
HTCdev unlocked bootloader
S-ON
HBOOT 1.57
Stock ROM
4ext recovery
Any and all help would be greatly appreciated!
(Also I apologize if I didn't give all the information needed or if I posted this in the incorrect spot. I figured this would be the most appropriate spot since although I have issues with specific processes it's also a fairly general request for help.)
UPDATE: I tried re-unlocking my phone using HTCdev so I'm no longer stuck in bootloader. I'm going to be trying the HBOOT Downgrade Toolkit guide again sometime today or tomorrow to see if I can get it working. I think one of the problems before was that I didn't put the RUU on the sdcard beforehand and then my device wasn't being recognized so i couldn't put it there then. If I put it on beforehand I should be able to update successfully and get past the step I was stuck on before.
If you're son u can only flash sence ROMs.
Sent from my PG86100 using xda app-developers app
cj_302 said:
If you're son u can only flash sence ROMs.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Er, I'm not quite sure what you're saying here.
UPDATE: I tried re-unlocking my phone using HTCdev so I'm no longer stuck in bootloader. I'm going to be trying the HBOOT Downgrade Toolkit guide again sometime today or tomorrow to see if I can get it working. I think one of the problems before was that I didn't put the RUU on the sdcard beforehand and then my device wasn't being recognized so i couldn't put it there then. If I put it on beforehand I should be able to update successfully and get past the step I was stuck on before.
It will be your hboot causing the problems.
Most recoveries allow you to mount usb storage so you can use that option to connect to your pc and move the ruu across without removing your sdcard etc.
Download G Cloud Backup for Android, up to 8 GB Free.Use this code: [KWLYRO] at signup and we'll both earn space: https://play.google.com/store/apps/details?id=com.genie9.gcloudbackup
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 !