I did the HTC Dev Bootloader Unlock;I installed custom recovery; and I installed a rom via fastboot that had everything....... including the hacked 1.05 hboot now i keep getting boot loop and forsome reason even though the bootloader says ***UNLOCKED***" at the top; it still says S-on.... any help?
Sorry I don't know the answer but maybe you'd get a quicker and better response in the Rooting thread in the Dev section.
Did you downgrade the software if it was @ the most current OTA version?
http://forum.xda-developers.com/showthread.php?t=1401959
Sent from my HTC ThunderBolt using XDA Premium App
yeah from .9 to .5 then unlocked bootloader
smtom said:
Did you downgrade the software if it was @ the most current OTA version?
http://forum.xda-developers.com/showthread.php?t=1401959
Sent from my HTC ThunderBolt using XDA Premium App
Click to expand...
Click to collapse
You install (flash) the super user app?
Sent from my HTC ThunderBolt using XDA Premium App
You downgraded and then you unlocked the bootloader? Had never heard of doing any phone in that order
FWIK and from my personal experience with HTCDEV unlock is that you will never have S-Off, not without an Eng-HBoot. Hacked HBoot's and other exploits can help gain it but "S-On" is in reference to a security feature in relation to the kernel and recovery partition, it was a safety measure to (in theory) keep you from bricking your phone by flashing an unstable kernel on it through recovery mode and possibly being unable to restore your previous nand by effing your recovery up. That is a simplified explanation and not all the reasons but you get the idea. I hope you can get it fixed. Best way to try to fix it is to go back and start from the beginning with just getting an Eng-HBoot or a hacked one that will allow writing to the secure kernel partition through recovery (one that will allow you to copy the NAND part of your device and it's kernel, htcdev unlock only allows nand no matter what the recovery's log says), if you can't do that then try using fastboot in a cmd window to boot a saved recovery image from the fastboot directory on your computer, that may allow you to fix your issues, good luck, hope it helps
if i get the eng hboot how am i going to flash it if its not letting me run pc'img's?
loveableterrorepic4g said:
You downgraded and then you unlocked the bootloader? Had never heard of doing any phone in that order
FWIK and from my personal experience with HTCDEV unlock is that you will never have S-Off, not without an Eng-HBoot. Hacked HBoot's and other exploits can help gain it but "S-On" is in reference to a security feature in relation to the kernel and recovery partition, it was a safety measure to (in theory) keep you from bricking your phone by flashing an unstable kernel on it through recovery mode and possibly being unable to restore your previous nand by effing your recovery up. That is a simplified explanation and not all the reasons but you get the idea. I hope you can get it fixed. Best way to try to fix it is to go back and start from the beginning with just getting an Eng-HBoot or a hacked one that will allow writing to the secure kernel partition through recovery (one that will allow you to copy the NAND part of your device and it's kernel, htcdev unlock only allows nand no matter what the recovery's log says), if you can't do that then try using fastboot in a cmd window to boot a saved recovery image from the fastboot directory on your computer, that may allow you to fix your issues, good luck, hope it helps
Click to expand...
Click to collapse
Have you tried using fastboot as a way to reboot the bootloader? I mean, my big thing is if you can get the pg img for the eng-hboot then you should be able to put it on your SD and then reboot the bootloader to let it try to boot the Pg, I know that I had a panic moment on the original EVO before they figured out a downgrade fix that I nearly bricked it, it wouldn't run the PG img check on first boot of the bootloader until I used fastboot to actually reflash the partitions on the phone (i may hate heimdall when I am working with samsungs but fastboot damn near broke me ha) the best thing to do it get a more intimate knowledge of the process and of fastboot and adb, they are great things to know how to use. Like I said I don't have a Thunderbolt but in dealing with HTC and HTCDEVs unlock tool I am pretty knowledgeable after working with it multiple times, I do know I had to downgrade my EVO (original) by manual partition flashing after I used the HTCDEV unlock tool, it unlocked the bootloader to allow me to boot what I flashed, but the kernel partition was still secure (S-On) this is what the tool, it seems that it was an attempt to cover their ass to ensure that those who don't know what their doing couldn't fully eff things up without more knowledge of the system and could reverse anything that may be unstable.
Related
Ok, I'm sure - the answer to this is in here somewhere, but an hour searching is enough...
What exactly does the s-on mean in the hboot? I started from leak 1, upgraded to leak 3, then root. My hboot shows s-on... How does this affect my phone?
Sent from my Froyo Eris using XDA App
Macrodroid said:
Ok, I'm sure - the answer to this is in here somewhere, but an hour searching is enough...
What exactly does the s-on mean in the hboot? I started from leak 1, upgraded to leak 3, then root. My hboot shows s-on... How does this affect my phone?
Sent from my Froyo Eris using XDA App
Click to expand...
Click to collapse
The first "root" which was gained on the Eris was via a leaked HTC "Engineering" ROM which had the 1.49.2000 S-OFF bootloader. An "S-OFF" bootloader has normal security checks suppressed, so that you can use the "fastboot" utility with the phone's bootloader in "FASTBOOT USB" mode to write to various partitions, including the recovery partition. In addition, that same Engineering ROM allowed you to obtain a root shell via the "adb" (Android Device Bridge) tool in the SDK, so you could also write to partitions (including the recovery partition) with the OS of the phone booted.
The way that rooting occurred in most of the early cases was similar to what we do now: as a first step, the recovery boot partition is replaced with a custom recovery (Amon_RA v1.6.2), and then after that a replacement OS is flashed via the (Amon_RA) recovery boot. In a way, the S-OFF bootloader was sort of "free" - you had to apply the Root-ROM (PB00IMG.ZIP) file to the phone using the bootloader HBOOT mode, and this would flash all partitions on the phone.
In any event, if you look at earlier posts, they are dominated by discussions of "what bootloader version do you have" - because if you had a 1.46.0000 S-ON, or 1.47.0000 S-ON bootloader, it was possible to apply the Root-ROM flash using HBOOT; whereas if you had jumped the gun and applied any of the other HTC 2.1 Test release ROMs (which became known as "Leak-V1", "Leak-V2", or "Leak-V3", and had a 1.49.0000 S-ON bootloader installed as a result of that), then it was impossible to apply the "Root ROM" to the phone using HBOOT.
The newly-discovered methods exploit a different hole in the booting of the main OS, so the bootloader is not touched - a permission bug is exploited so that the recovery partition can be overwritten by any user on the phone (root isn't even needed!). Therefore, the recovery partition can be replaced without flashing the entire phone (just as it was in "the wayback").
So, if you look through those old threads where someone asked "I think I rooted, but I am not sure", other folks in the know would ask "does your bootloader say S-ON or S-OFF?"
But now we can gain privilege on the phone by directly overwriting the recovery partition with a custom recovery , and then booting that (which always has root privilege). You can now get a "rooted" recovery, and then a "rooted" ROM installed afterward onto the phone without ever touching the bootloader.
In practice, nobody has been able to detect any noticeable dependencies of the OS on version of the bootloader; if you can get a new OS installed onto the phone by hook or by crook, neither the bootloader nor the OS seem to care what the version of the other is.
That's the long explanation for "you don't need to worry too much about it any longer".
Having an S-OFF bootloader provides just a little bit more flexibility for emergency recovery of the phone; on the other hand, flashing the bootloader is the absolute most dangerous flashing operation that happens on the phone. Everything on the phone springs to life via the bootloader - it has to be intact for anything else on the phone to work.
So, I'd say - "don't worry, be happy". And leave your bootloader as it is.
bftb0
That definately answers my question! Thanks!
Sent from my Buuf Froyo using XDA App
Ok, did have my phone rooted but one of the ROM's on here managed to cause problems so installed one of the factory HTC ROM's to unroot it and put it back should I need to send it to HTC to fix.
So after putting the stock HTC ROM on when I enter recovery mode it is now teling me that the handset is locked (bootloader is presume) also the it is still showing S-OFF.
It is showing the following so if someone can explain to a noob how to re-root it that would be fantastic.
SHOOTER_U PUT SHIP S-OFF RL
HBOOT - 1.49.0018
RADIO-10.14.9020.06_M
eMMC-boot
Oct 3 2011,15:03:01
Any help is really appreciated as there is some really cool looking ROM's that I would like to try.
So, over 80 views and no-one has an answer for this?!
ratedr75 said:
Ok, did have my phone rooted but one of the ROM's on here managed to cause problems so installed one of the factory HTC ROM's to unroot it and put it back should I need to send it to HTC to fix.
So after putting the stock HTC ROM on when I enter recovery mode it is now teling me that the handset is locked (bootloader is presume) also the it is still showing S-OFF.
It is showing the following so if someone can explain to a noob how to re-root it that would be fantastic.
SHOOTER_U PUT SHIP S-OFF RL
HBOOT - 1.49.0018
RADIO-10.14.9020.06_M
eMMC-boot
Oct 3 2011,15:03:01
Any help is really appreciated as there is some really cool looking ROM's that I would like to try.
Click to expand...
Click to collapse
ratedr75 said:
So, over 80 views and no-one has an answer for this?!
Click to expand...
Click to collapse
Wow .. so originally you had an older hboot and used revolutionary to set s-off. Then you loaded a newer RUU which contained an hboot that was patched against revolutionary's s-off method.
Now you're on a newer hboot patched against revolutionary's s-off method, but you're still set s-off from previously using their method.
Don't see this situation very often. According to the theory, of how unrevoked set s-off and how I assume revolutionary is similar, you should still be s-off, as your bootloader shows, meaning your internal memory is NOT write protected.
In order to root your device, you should be able to fastboot flash a custom recovery. Boot into the custom recovery and load the normal superuser .zip or manually over adb push an su binary (I prefer aosp for developers) and chmod 4755 /system/bin/su . Both of those methods should give you root!
Hope that helps!
So if I install another ROM and try to goto recovery mode (which at the moment I am getting the triangle when I enter) I should be able to re-root this?
joeykrim said:
Wow .. so originally you had an older hboot and used revolutionary to set s-off. Then you loaded a newer RUU which contained an hboot that was patched against revolutionary's s-off method.
Now you're on a newer hboot patched against revolutionary's s-off method, but you're still set s-off from previously using their method.
Don't see this situation very often. According to the theory, of how unrevoked set s-off and how I assume revolutionary is similar, you should still be s-off, as your bootloader shows, meaning your internal memory is NOT write protected.
In order to root your device, you should be able to fastboot flash a custom recovery. Boot into the custom recovery and load the normal superuser .zip or manually over adb push an su binary (I prefer aosp for developers) and chmod 4755 /system/bin/su . Both of those methods should give you root!
Hope that helps!
Click to expand...
Click to collapse
ratedr75 said:
So if I install another ROM and try to goto recovery mode (which at the moment I am getting the triangle when I enter) I should be able to re-root this?
Click to expand...
Click to collapse
I've quoted my previous post to highlight the steps outlined. I never mentioned anything about another ROM.
If the theory holds, as it was true for unrevoked's method of s-off and some members of unrevoked are now part of AlphaRevX releasing the revolutionary tool, you only need to flash a custom recovery through fastboot or bootloader.
If you have adb setup, it would literally take you 10 seconds to issue the fastboot command and another 10 seconds to reboot into recovery to see if t worked.
Currently, when you boot into recovery and you see the triangle, that is the stock recovery. Sometimes on the stock recovery screen, if you want to activate the menu, pressing vol up + pwr *should* work in stock recovery but sometimes manf like HTC change this function in the version of recovery they distribute.
Once you use the command: fastboot flash recovery c:\android\cwm-recovery.img , you should be able to boot into recovery and see the custom recovery load.
If that method doesnt work, the other method to attempt is loading a PG86IMG.zip file on the root of the sdcard with the custom recovery inside the PG86IMG.zip. Upon booting into the bootloader, it should scan this file and ask to update. If you select yes to update, the bootloader should flash and you should have a custom recovery.
If neither of those two methods work, you'll likely have to use the HTC unlock method. But I think those methods should work as your device still shows S-OFF.
Good luck!
Have tried all your methods and various other ones.
None of them work at all, a lot of the people on here seem to think that eveyrone has their abilities.
I could get an ADB shell up, the CMD prompt didn't work either.
The phone is going in its box and i'd rather spend some money on a phone that is easier to work with a windows 7 laptop.
ratedr75 said:
Have tried all your methods and various other ones.
None of them work at all, a lot of the people on here seem to think that eveyrone has their abilities.
I could get an ADB shell up, the CMD prompt didn't work either.
The phone is going in its box and i'd rather spend some money on a phone that is easier to work with a windows 7 laptop.
Click to expand...
Click to collapse
The issues you're experiencing are due to HTC's complex locking method to deter root access. There are many Android devices which come stock with no locking protection or must less sophisticated locking protection.
If you're not able to properly setup adb, then the PG86IMG.zip method should be more convenient for you. All you need to do is put a PG86IMG.zip file onto the root (main dir) of your sdcard and holding vol down + pwr (boot into the bootloader). From here, it will scan the PG86IMG.zip and prompt if you want to load. Choose yes and this will flash the custom recovery.
Once the custom recovery is loaded, you should be able to flash a rooted ROM from, flash superuser .zip file or adb push su binary to restore root.
HTC intentionally makes this process difficult and it is relatively more difficult than other Android devices. All the resources are here at your disposal but HTC requires a bit more work/effort/learning to accomplish what is easier on some other Android devices. Although, even the Google Nexus S requires using fastboot to unlock t he device.
Nobody wants to see anybody give up and abandon. Hope that helps!
for whatever reason on the evo 3D, fastboot commands for things like flashing a recovery don't seem to work even with s-off. You need to put the custom recovery in a zip and name it PG86IMG then flash it from the bootloader and it will work.
fyi you should always be able to run a stock RUU (even new ones) because Revolutionary for the evo 3D gave you actual radio s-off and not just fake s-off with a patched hboot which is how Revolutionary worked on most phones. radio s-off pretty much means your phone will never go back to s-on even with a stock RUU. that is why you were able to upgrade the hboot and still keep s-off.
Thanks for the help guys. I'm going to give this one last try before I got and invest in an xperia arc s.
Does anyone have a decent download for the PG86IMG.zip file?
Ill try this at lunch, if not its away it goes.
patrick92260 said:
for whatever reason on the evo 3D, fastboot commands for things like flashing a recovery don't seem to work even with s-off.
Click to expand...
Click to collapse
fastboot commands don't work on the EVO 3D? even for recovery?
I haven't seen this complaint on the Q&A board. Majority of users seem to have plenty of success using fastboot to flash kernels and custom recoveries. Although, majority of people posting on the Q&A board recently have the latest hboot and can only use HTC's unlock method. Perhaps this is only an issue on revolutionary s-off devices?
ratedr75 said:
Thanks for the help guys. I'm going to give this one last try before I got and invest in an xperia arc s.
Does anyone have a decent download for the PG86IMG.zip file?
Ill try this at lunch, if not its away it goes.
Click to expand...
Click to collapse
I went to google.com and typed in the phrase, "twrp PG86IMG.zip" and the second link looks to be the quickest to obtaining the file:
http://teamw.in/project/twrp/67
I have heard pretty decent reports of Sony being fairly support of developers and allowing their devices to be unlocked and rooted.
Good Luck!
Thanks guys. Again. Now would anyone be interested in purchasing the EVO 3D GSM sim free from myself?
hi I am in the same position as the OP, just got my phone 2nd hand..want to flash LeeDroids Rom, my phone is GSM version, please advise how to get custom recovery..thanks
Been a lurker for a while, now I need some input if possible. I have a Thunderbolt whose touchscreen is not fully working, there is a strip about 1/4" wide top to bottom that does not respond to input. I rooted it using trter's Thunderbolt Tool and have been running Santod's ICS. When I decided to return to stock I did not read anything and merely ran trtr's tool and used the unroot option. This has me stuck now with a weird state.
Boot screen:
*** UNLOCKED ***
MECHA XD SHIP S-ON
HBOOT-1.05.0000
MICROP-/
RADIO-1.48.00.0930w_3
eMMC-boot
Jul 19 2011, 14:51:08
4ext recovery is still installed for some reason.
Here are things I have tried:
1. Unroot using trtr's tool - leaves me in a non-booting state with a Security warning and Main Version failure.
2. Used HTCDev unlock and pushed PG05IMG.zip of 2.11.605. This allows me to boot to a seemingly stock ROM.
3. OTA's get pushed, device reboots but OTA's fail to install.
4. Tried recovering Nandroid backups with 4ext, no matter which one I try to restore I get stuck in a boot loop (BAMF SoaB, ICS Santod, Liquid ICS, Multi-source ICS, ICS stock deodex).
5. Tried using 4ext to install the above ROMS directly, along with full wipes and partition formats before each attempt. They seem to install but get stuck in a boot loop on each.
6. Other various combinations of HTCdev, Thunderbolt Tool, FastBoot boot.img pushes, etc. Trtr's tool connecting in booted and fastboot modes fails to unroot or root or change S-ON state.
7. Did step 2 again to get me a working phone (except touch screen problem) until I can figure out WTH is going on.
Current state - the above Boot Screen details, 2.11.605.19 deodexed-signed image, and lucky I have not totally bricked it yet.
Help please? I've googled for the last 3 days and read countless posts and am not sure what to do from here. All I need is to get it back to stock so I can send it back to HTC and get a replacement. I have a working ADB set up and am willing to follow steps exactly or read whatever page you believe I have missed, or call me a dumb n00b, berate me for not reading something, anything... at this point I have no interest in retaining data on the phone or SD card or my dignity, just a stock phone that I can send back.
Thanks all!
Me too
google thunderboltforums How to Fix Security Warning - this is what trtr10 himself recommended to me . It didn't let me post, when I tried direct link.
Your #2 & #6 is similar, but maybe not exactly the same. It didn't work for me, though. And I had to add an adb manual lock step, because you need to be locked before trying trtr10s tool to unroot (or at least locked before it runs the final flash update, which fails for me with Main Version is older. Update Fail!
Also, technically the adb fastboot oem lock yields error #1:
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.459s
That's major coincidence I have exact same problem, down to dead touch screen strip. I've been trying to get unrooted for a week and was supposed to mail the thing back last Friday . .
Here's hoping a solution gets posted. I don't want to pay cuz the insurance refurb was fail, when my warranty service is supposed to be free replacement and it is stupid hardware failure.
All I can say is trter supposedly updated his tool to work with the latest ota, but its been about a week and he hasn't released it yet.
He did say something about having a problem with his host though.
washuai said:
google thunderboltforums How to Fix Security Warning - this is what trtr10 himself recommended to me . It didn't let me post, when I tried direct link.
Click to expand...
Click to collapse
This is how I fixed the security warning when I first got it, using HTCDev unlock. I also used adb fastboot relock to lock back before trying the tool.
washuai said:
Your #2 & #6 is similar, but maybe not exactly the same. It didn't work for me, though. And I had to add an adb manual lock step, because you need to be locked before trying trtr10s tool to unroot (or at least locked before it runs the final flash update, which fails for me with Main Version is older. Update Fail!
Also, technically the adb fastboot oem lock yields error #1:
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.459s
Click to expand...
Click to collapse
Yep - got that too...
Weird. Guess I'll wait for the new tool and see what it does...
As far as the identical touchscreen issue, this phone is also a refurb, my second with a touchscreen problem. The really weird part is that it works sometimes, particularly after all this work flashing and re-flashing, but I don't think it has anything to do with the ROMS or software, rather the fact that during all this work I am constantly doing battery pulls and SD card swaps and maybe it's because of a flaky ribbon connection or something - if it was not under warranty I would open it up and just try reseating anything I could find inside.
Have you tried to RUU back? It is a way manufacturers refurb or make the software new again without having to figure out what state it is in.
As long as you can get in fastboot it will work... Also could you possibly fastboot an ENG HBOOT? It doesn't show if it's unlocked nor does
it have any of those pink banners up at top.... Those I believe allow you to flash anything you couldn't normally do before... Try that.. Also I
ALWAYS manually push and flash my stuff through ADB and fastboot. It is faster (if you know what you are doing) AND it has better control
over what I am doing. I made a tut on how to flash boot screens (the very first image that comes up when you turn it on) and it is just about
same commands to flash normally stuff.
I run a Linux Box and always use root terminal so I am not certain at what point you would need superuser if any but as follows
#fastboot devices
#fastboot flash zip "name of zip" (no it doesn't have to be called anything specific, it could be called file1.zip)
#fastboot erase [option] /cache /data /system
to force it into the special RUU mode to use HTC's RUU, this is the command
#fastboot oem rebootRUU
Linux too Yes, I can flash via fastboot, I'm concerned about which one to flash though, I don't want to brick...
jnorth said:
Linux too Yes, I can flash via fastboot, I'm concerned about which one to flash though, I don't want to brick...
Click to expand...
Click to collapse
If you can give me today and I'll send you either the link to download the RUU or the exe itself.
You have the new radios installed and need to downgrade them by going s-off again. Need to do this to avoid main version errors.
The ota's don't install because of the custom recovery.
Backups don't work because your s-on and the kernel can be installed.
You may be able to install santod's ota rom in recovery and install the boot.IMG from the rom (kernel) in fasboot = ./fastboot flash boot boot.img
Relock the boot loader and send it in looking like stock.
There is also a way to spoof your main version and downgrade from ICS to GB Ruu stock. That is posted on another site.
Sent from my ConD3m3dPaC-man ADR6425LVW using xda app-developers app
tburns said:
You have the new radios installed and need to downgrade them by going s-off again. Need to do this to avoid main version errors.
Click to expand...
Click to collapse
Working on this now, as soon as I figure out how to get s-off again. Thanks!
http://androidfiles.org/ruu/?developer=Mecha
The RUU's to take you back to stock
Thanks to hints from you both, I am back to stock... probably more steps than were needed but it worked for me LOL.
1. Used part of the Revolutionary tool to get S-Off again and let it install CWM over 4ext
2. Re-rooted
3. Installed 2.11.605.9 radio and GB OTA rom
4. Used fastboot to put stock hboot back
Appears to be normal stock now and OTA in progress.
Thank you both again!
jnorth said:
Thanks to hints from you both, I am back to stock... probably more steps than were needed but it worked for me LOL.
1. Used part of the Revolutionary tool to get S-Off again and let it install CWM over 4ext
2. Re-rooted
3. Installed 2.11.605.9 radio and GB OTA rom
4. Used fastboot to put stock hboot back
Appears to be normal stock now and OTA in progress.
Thank you both again!
Click to expand...
Click to collapse
that is what the community is all about , right?
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
jnorth said:
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
Click to expand...
Click to collapse
you could ALWAYS use an ENG and nobody would be non-the-wiser if you rooted or not! It would look like a developer phone instead..
when it says ***RELOCKED*** it tells anybody and everybody you have been rooted at one point or another (no bueno for warranty)
jnorth said:
Exactly!
One last question - bootloader says ***RELOCKED*** instead of ***LOCKED*** - presumably because I used the HTCdev unlocker at one point... is that fixable or permanent?
Click to expand...
Click to collapse
this -SHOULD- take care of the pink banner up at top BE CAREFUL WITH THIS!!!
there again... I run constant root terminal so I do not know if it requires root or not soooo.....
#fastboot oem mw 8d08ac54 1 31302E30
#fastboot flash hboot whateverhbootfile.nb0
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
Hello,
This is an odd request, but I'm in need of some help with this HTC Rezound. A bit of background first. It's not mine. I'm a G2 user (rooted and I know my way around Android hacking). This phone belongs to a friend and despite having it rooted he knows nothing about how he got there or how to fix a problem. Currently it's stuck in a bootloop. He mailed the phone to me (we live 750 miles apart) and he's hoping I might be able to assist. I can get into recovery (I'm assuming it's a custom recovery - looks like ClockworkMod) and my hope was to flash a new ROM but he stupidly neglected to send the phone to me with an SD Card. I'm wondering if there's a way to get a ROM/gapps onto the phone (internal storage) and flash from there. I see there's an option for USB-MS toggle and I've tried playing around in the internal_sd area, and I can get a G: drive to appear when choosing this and connected via USB to my computer, but when I put the ROM/gapps on there I cannot seem to access it for flashing purposes.
Sorry for the long-winded description. But is this a simple solution? Do I just need to get a hold of an SD card and put the files needed on there for flashing? Or is there a way to flash the ROM directly from internal storage?
Thanks in advance for any help you might provide.
Could you post a "fastboot getvar all" ? Without the commas.
Also one thing I would do. Flash twrp 2.6.3.0 Then mount the phone. Push the ROM using a adb push. But first could you post a fastboot getvar all ?
Sent from my Rezound running Sense 5. S-OFF
pball52998 said:
Could you post a "fastboot getvar all" ? Without the commas.
Also one thing I would do. Flash twrp 2.6.3.0 Then mount the phone. Push the ROM using a adb push. But first could you post a fastboot getvar all ?
Sent from my Rezound running Sense 5. S-OFF
Click to expand...
Click to collapse
Sorry for my noobness, but I have no idea how to do that with this phone. I know nothing about HTC devices - never owned one before.
No problem at all man, we all start somewhere for every phone company.
Okay, pull the battery out. Put it back in, volume down, power button. It should show up a white screen. With I think like 5 options, I know the first two are: fastboot and recovery. When highlighted over fastboot, press power. Then will bring you to fastboot. It'll say in red letters "FASTBOOT USB" at the top. Plug it into the computer open a cmd prompt where you fastboot/adb also known as platform-tools is. Type fastboot getvar all
Sent from my Rezound running Sense 5. S-OFF
pball52998 said:
No problem at all man, we all start somewhere for every phone company.
Okay, pull the battery out. Put it back in, volume down, power button. It should show up a white screen. With I think like 5 options, I know the first two are: fastboot and recovery. When highlighted over fastboot, press power. Then will bring you to fastboot. It'll say in red letters "FASTBOOT USB" at the top. Plug it into the computer open a cmd prompt where you fastboot/adb also known as platform-tools is. Type fastboot getvar all
Sent from my Rezound running Sense 5. S-OFF
Click to expand...
Click to collapse
Thanks for the reply. My time messing with the phone is done for the night, but I'll give that a try tomorrow.
Okay sounds good
Sent from my crappy Jailbroken apple iPad.....
Freedoms just another word for nothing left to do... Nothin' ain't worth nothing but it's free.....
It should say something in the bootloader at the top like below:
***unlocked***
Pvt ship s-off (or s-on)
Hboot version # stuff here
Radio version # stuff here
Is it s-off or s-on?
If it's secure flag is still on, you would need to extract the boot.IMG from your ROM zip and do the following command after pushing and flashing the ROM in recovery. After you do flash the ROM, boot back into bootloader and into fastboot and type the following command in PC terminal
Fastboot flash boot boot.img
Sent from my Rezound
Uzephi said:
It should say something in the bootloader at the top like below:
***unlocked***
Pvt ship s-off (or s-on)
Hboot version # stuff here
Radio version # stuff here
Is it s-off or s-on?
If it's secure flag is still on, you would need to extract the boot.IMG from your ROM zip and do the following command after pushing and flashing the ROM in recovery. After you do flash the ROM, boot back into bootloader and into fastboot and type the following command in PC terminal
Fastboot flash boot boot.img
Sent from my Rezound
Click to expand...
Click to collapse
Yep, pretty much, what I was trying to get him through first was actually pushing a ROM to the phone, also the fastboot getvar all gives almost all info. But true with that, that's probably the MOST important part of rooting and ROMing HTC lol. Although he never stated what rom he has. Trying to get him through some basics of HTC too.
Sent from my Rezound running Sense 5. S-OFF
Yeah, just wanted to put that out there in case he found it how to flash a ROM without us, he will see that post to fix his boot loop (if s-on)
Sent from my Rezound
Thanks again for the replies everyone. Very helpful. As stated before, this is an odd situation because I know nothing about rooting/ROMs for HTC and this isn't my phone.
Anyway, a bit of where I'm at and some better info regarding the phone's situation. The phone, upon attempting to boot, would just bootloop. I don't remember exactly which ROM was on there as I've since done a factory reset, but needless to say it wasn't working. Also, I happened to track down an SD card from an old phone of mine and I used the USB-MS feature in recovery to put a ROM on there for flashing. Wiped everything as I would any other phone, flashed the ROM (which stated was successful) and upon a reboot the phone just hangs on the white HTC screen. Did a bit of digging and decided to try returning to stock (he doesn't care if this phone is still rooted, just wants it working). Found this link http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ and followed the instructions exactly. Update seemed to take just fine, but again a reboot just got me stuck on the white HTC screen.
I've yet to hook this up to try the fastboot getvar thing as the computer I'm using didn't have ADB installed and I didn't have the time to do so. In the meantime any additional suggestions?
I'm attaching a pic of the phone in hboot so you can see some info that might be helpful.
The reason the phone froze at the HTC screen is because that phone is s-on...
In HTC world, there is the bootloader lock (the purple thing at the top saying unlocked) and the secure flag.
With the bootloader unlocked, you can flash on virtually any partition (only signed firmware and other technical stuff that is irrelevant in your situation) but when booted in recovery, you cannot flash to the boot partition. (Can only do that when s-off)
To flash the boot partition when unlocked s-on (secure flag on) you need to extract the boot.IMG from the ROM and flash it while in fastboot mode from the hboot.
To RUU (return to complete stock) you also need to flash upwards or same version firmware officially signed by HTC when s-on. If you are s-off then you can downgrade. Also, bootloader needs to be locked again.
TL/DR: flash the boot image following my post above and that ROM you flashed will work.
Sent from my Rezound
Uzephi said:
The reason the phone froze at the HTC screen is because that phone is s-on...
In HTC world, there is the bootloader lock (the purple thing at the top saying unlocked) and the secure flag.
With the bootloader unlocked, you can flash on virtually any partition (only signed firmware and other technical stuff that is irrelevant in your situation) but when booted in recovery, you cannot flash to the boot partition. (Can only do that when s-off)
To flash the boot partition when unlocked s-on (secure flag on) you need to extract the boot.IMG from the ROM and flash it while in fastboot mode from the hboot.
To RUU (return to complete stock) you also need to flash upwards or same version firmware officially signed by HTC when s-on. If you are s-off then you can downgrade. Also, bootloader needs to be locked again.
TL/DR: flash the boot image following my post above and that ROM you flashed will work.
Sent from my Rezound
Click to expand...
Click to collapse
Thanks for this. I think I get what you're saying, but just for the sake of clarification, one more question regarding this process.
I extract the boot.IMG from my ROM of choice, flash the ROM/gapps as I would on any other device, then go back to fastboot and run the adb commands posted earlier? Correct?
Rodeojones said:
Thanks for this. I think I get what you're saying, but just for the sake of clarification, one more question regarding this process.
I extract the boot.IMG from my ROM of choice, flash the ROM/gapps as I would on any other device, then go back to fastboot and run the adb commands posted earlier? Correct?
Click to expand...
Click to collapse
Exactly. Be sure to do exactly that command not
Fastboot boot boot.img
If you forget to say flash boot, it will just temporarily boot that kernel/boot image and not flash it to the device. Then upon reboot you will be back at step one.
Sent from my Rezound
Uzephi said:
Exactly. Be sure to do exactly that command not
Fastboot boot boot.img
If you forget to say flash boot, it will just temporarily boot that kernel/boot image and not flash it to the device. Then upon reboot you will be back at step one.
Sent from my Rezound
Click to expand...
Click to collapse
Again, thank you. Going to give this a go after my son's t-ball game. I feel like more of a noob than when I rooted my OG Droid years ago.
@Uzephi, @pball52998, thank you to for your assistance. I felt like a total noob working on a phone that wasn't mine. But I've got it up and running again. My friend Jake will be very happy (I've also told him that this is the last ROM he will ever put on here unless he learns how to do everything I just did - he didn't even know what ADB was when I told him).
Rodeojones said:
@Uzephi, @pball52998, thank you to for your assistance. I felt like a total noob working on a phone that wasn't mine. But I've got it up and running again. My friend Jake will be very happy (I've also told him that this is the last ROM he will ever put on here unless he learns how to do everything I just did - he didn't even know what ADB was when I told him).
Click to expand...
Click to collapse
Wait! He has old HBOOT and Radios, the newest radio is 1.28 he has 1.21 I think I saw.... I would suggest s-off then RUU and doing a RUU.... Or if anyone has em, the HBOOT and Radios you can flash in recovery.
pball52998 said:
Wait! He has old HBOOT and Radios, the newest radio is 1.28 he has 1.21 I think I saw.... I would suggest s-off then RUU and doing a RUU.... Or if anyone has em, the HBOOT and Radios you can flash in recovery.
Click to expand...
Click to collapse
Flashing them in recovery would be great, if there's a link to download the files. But just to be clear, despite this phone finally booking up there's more I need to do to make it 100% usable?
It is 100% usable, but you will experience less overheats and better battery life with the new firmware. I know the hboot ph98img zip is somewhere in this forum for the updated hboot and radio (for that zip you would just put in root of external SD card and in hboot it will automatically flash)
Sent from my Rezound
Uzephi said:
The reason the phone froze at the HTC screen is because that phone is s-on...
In HTC world, there is the bootloader lock (the purple thing at the top saying unlocked) and the secure flag.
With the bootloader unlocked, you can flash on virtually any partition (only signed firmware and other technical stuff that is irrelevant in your situation) but when booted in recovery, you cannot flash to the boot partition. (Can only do that when s-off)
To flash the boot partition when unlocked s-on (secure flag on) you need to extract the boot.IMG from the ROM and flash it while in fastboot mode from the hboot.
To RUU (return to complete stock) you also need to flash upwards or same version firmware officially signed by HTC when s-on. If you are s-off then you can downgrade. Also, bootloader needs to be locked again.
TL/DR: flash the boot image following my post above and that ROM you flashed will work.
Sent from my Rezound
Click to expand...
Click to collapse
Hello, I have been preparing to RUU back to 4.03.605.2 and want to be sure of process. I read REV3NT3CH's post on downgrading, so I downloaded the latest 2 PH89IMGs via his instructions and here's where I stand:
S Off
Hboot 2.28
Radio 2.23.10.0123r/1.23.10.0124r
also running CleanRom 4.5
Can I just place PH89IMG on sdcard to RUU or am I missing a step? Thank you in advance
Just place it in the root of SD card and reboot to your boot loader
Sent from my Rezound