Related
So I held out for months to unlock my phone and decided to do so last night via HTC unlock method. All went well, unlocked, rooted and ended up flashing Myn's twopointthree. After all that trouble decided I don't care to do the whole rom thing and invest time into hacking my phones anymore.
I have tried everything to my knowledge to at least get back to stock (regardless if it is still unlocked) and no luck. I have tried running the RUU which fails (probably has to do with custom recovery), PG86IMG zips through recovery and bootloader which fails and also tried flashing stock recovery and running RUU and still no luck.
In my EVO days I had no troubles doing whatever I wanted with rooting and unrooting and everything in between because if I decided to return to stock I would run the PG36IMG zip and thats all it took.
Does anyone have any input on getting back to stock rom or do I have to use a Rooted Stock from xHausX or something equivelent?
Anything and everything is appreciated!
pnewgaard said:
So I held out for months to unlock my phone and decided to do so last night via HTC unlock method. All went well, unlocked, rooted and ended up flashing Myn's twopointthree. After all that trouble decided I don't care to do the whole rom thing and invest time into hacking my phones anymore.
I have tried everything to my knowledge to at least get back to stock (regardless if it is still unlocked) and no luck. I have tried running the RUU which fails (probably has to do with custom recovery), PG86IMG zips through recovery and bootloader which fails and also tried flashing stock recovery and running RUU and still no luck.
In my EVO days I had no troubles doing whatever I wanted with rooting and unrooting and everything in between because if I decided to return to stock I would run the PG36IMG zip and thats all it took.
Does anyone have any input on getting back to stock rom or do I have to use a Rooted Stock from xHausX or something equivelent?
Anything and everything is appreciated!
Click to expand...
Click to collapse
Take a look at this post - http://forum.xda-developers.com/showthread.php?t=1193540 .
pnewgaard said:
So I held out for months to unlock my phone and decided to do so last night via HTC unlock method. All went well, unlocked, rooted and ended up flashing Myn's twopointthree. After all that trouble decided I don't care to do the whole rom thing and invest time into hacking my phones anymore.
I have tried everything to my knowledge to at least get back to stock (regardless if it is still unlocked) and no luck. I have tried running the RUU which fails (probably has to do with custom recovery), PG86IMG zips through recovery and bootloader which fails and also tried flashing stock recovery and running RUU and still no luck.
In my EVO days I had no troubles doing whatever I wanted with rooting and unrooting and everything in between because if I decided to return to stock I would run the PG36IMG zip and thats all it took.
Does anyone have any input on getting back to stock rom or do I have to use a Rooted Stock from xHausX or something equivelent?
Anything and everything is appreciated!
Click to expand...
Click to collapse
No details are mentioned with why RUU fails or why PG86IMG.zip fails. Both of these processes should provide some type of error.
Regardless, running an RUU through the .exe or flashing the signed PG86IMG.zip file should return all the partitions on the device to a stock state, minus perhaps the unlocked bootloader.
Best and most reliable souce for EVO 3D RUU files: http://www.goo-inside.me/shooter/ruu .
Good luck!
Forgive me for starting a new thread; I've utilized the search here and some Google-fu, but still have questions for the community.
I recently upgraded to an HTC Rezound from a Thunderbolt, and have accepted the stock OTA ICS update last weekend.
This has not stopped me from Rooting the device, however. Using an All-In-One Toolkit downloaded here, I was able to Unlock the Bootloader, Install custom Recovery (ClockWorkMod Touch), and have SU flashed. All signs point to root, but I would like to know a few things.
- Is there currently any method of acquiring S-OFF, other than the juopunutBear "Wire Trick"? It sounds incredibly risky, and I feel a bit hesitant to try it connecting pins on the back of my phone with insulated wire... I would like to have S-OFF, in case I want to roll back using a PH98IMG.zip
After rooting, I noticed that the text ****TAMPERED**** appears above the UNLOCKED line when I power on into HBOOT. Is this normal? Or have I messed things up? The best answer I have gleaned so far is from another device's forum, and that this simply indicates that I have root.
Would love to hear some feedback. This is my 5th Smartphone starting with the G1, and I have rooted every single one within days. Only the Rezound seems to be the trickiest for me.
Let me know your thoughts, thanks.
The hboot says tampered after you install a custom recovery so that's normal. I was the same way about s-off it seemed to risky and complicated but in all honesty it is very simple. It's our only way to get s-off and the main thing is getting the timing right for the wire trick. I got it on my second try. I would say just read up on it and gain as much info until you feel comfortable to do it.
Sent From My HTC Rezound
big_mike_2k6 said:
The hboot says tampered after you install a custom recovery so that's normal. I was the same way about s-off it seemed to risky and complicated but in all honesty it is very simple. It's our only way to get s-off and the main thing is getting the timing right for the wire trick. I got it on my second try. I would say just read up on it and gain as much info until you feel comfortable to do it.
Sent From My HTC Rezound
Click to expand...
Click to collapse
Thanks, that confirms a number of suspicions. & As I understand it, I need to be S-OFF in order to flash a custom ROM, correct?
And this is due to the fact that I not only have to flash the ROM in recovery, but also flash a Kernel through HBOOT?
I want to start flashing custom ROMs, but in the meantime, I'm fairly happy with rooted ICS. Got Google Now working, removed 'App Associations' menu, and removed the VZW crapware, so root is working out rather well
deadsoulboy said:
Thanks, that confirms a number of suspicions. & As I understand it, I need to be S-OFF in order to flash a custom ROM, correct?
And this is due to the fact that I not only have to flash the ROM in recovery, but also flash a Kernel through HBOOT?
I want to start flashing custom ROMs, but in the meantime, I'm fairly happy with rooted ICS. Got Google Now working, removed 'App Associations' menu, and removed the VZW crapware, so root is working out rather well
Click to expand...
Click to collapse
You don't need to be s-off to flash a Rom but you do need to flash the kernel separate in hboot when you're s-on. When you're s-off you don't have to. I myself usually stay fairly close to stock with a few tweaks here and there and of course Verizons crap long gone.
Sent From My HTC Rezound
One more thing... Given my software version, etc, if I S-OFF now, would I bork my device?
Also, it looks like at the unlimited.io site, there is only a Windows version of juopunutbear for Gingerbread, and early ICS versions. My phone's software is on version is 3.14.605.12; does this mean I should abandon attempting to S-OFF ?
deadsoulboy said:
One more thing... Given my software version, etc, if I S-OFF now, would I bork my device?
Also, it looks like at the unlimited.io site, there is only a Windows version of juopunutbear for Gingerbread, and early ICS versions. My phone's software is on version is 3.14.605.12; does this mean I should abandon attempting to S-OFF ?
Click to expand...
Click to collapse
No you'll be fine doing it on your current version. You can use the file from the unlimited.io site for the 3.14.605.05 ics leak it works with the official ics update.
Sent From My HTC Rezound
i know clockwork will bork your device im not sure if the touch version does the same thing.
I recommend installing Amon Ra recovery or TWRP.
If i helped thanks me
Hi all! This is my first post and hope it's not too silly of a question. I am currently using a Thunderbolt but very likely will be upgrading to a Rezound (I have both phones now). I know the ICS OTA is out for Rezound. I want to get root and S-off on Rezound running the stock ICS OTA, but I am not sure about the order of events.
1. Should I get S-off and root on the stock Gingerbread rom per the instructions in this thread (http://forum.xda-developers.com/showthread.php?t=1823362), and then upgrade to the ICS OTA? Or should I upgrade the stock Gingerbread to ICS OTA and then attempt to get S-off and root?
2. Is a confirmed s-off/root procedure out for the stock ICS OTA? sorry if I missed it - I promise I did my best searching through the forum before posting
I thought I'd start with the stock ICS OTA rom so I'll get a baseline for when I try out other roms down the road. And from what I've read here, the stock rom is probably a little bit more robust for day to day (correct me if I am wrong!). I hate the verizon bloatware and I think I'd be happy for a while if I can have S-off and root on the stock ICS.
thanks in advance for any help!
from scratch
Hiya, You're getting ready to become addicted to roms, by the way.
All your choices are kind of 'what do you want' things, but assuming you
receive it with stock Gingerbread, easiest thing would be to:
1 unlock by way of HTC Development instructions - lots of info here on xda
2 flash Cleanrom 175 a gingerbread stockish rooted rom
3 do the S-0ff thing with Juopunutbear, being careful not to amend or skip
any instructions in the S-0ff recipe (critical).
4 now your phone is s-0ff and locked. leave it just that way: no unlocks ever needed again and no pink warnings
5 flash Android police newest ICS RUU
6 flash amon ra as a PBIMG in recovery
7 use amon ra to wipe and install ANYTHING you want
haha Yeah roms are pretty addictive! So my background in rooting is limited to the Thunderbolt, which is my first smartphone. I used the Revolutionary IO method, which got me S-Off and root. But after reading through the Juopunutbear (Unlimited IO), I am slightly confused. I definitely did not do the wiring procedures involving the antennae contacts to get S-Off with the thunderbolt. I did more research and it sounds like the S-Off in thunderbolt is a "fake" S-off from a patched hboot?
That also leads to my next questions... up until now, I thought the following:
1. hboot = bootloader, which is the "BIOS" of the phone
2. In order to be rooted, S-off must happen first (this I guess is not true from your steps)
3. Recovery = part of hboot (from what I've read so far, this is incorrect too)
Also, would you elaborate on step #4? I thought unlocked is what I want, but instead I really want to have S-off and locked bootloader?
Thanks!
michaelbsheldon said:
Hiya, You're getting ready to become addicted to roms, by the way.
All your choices are kind of 'what do you want' things, but assuming you
receive it with stock Gingerbread, easiest thing would be to:
1 unlock by way of HTC Development instructions - lots of info here on xda
2 flash Cleanrom 175 a gingerbread stockish rooted rom
3 do the S-0ff thing with Juopunutbear, being careful not to amend or skip
any instructions in the S-0ff recipe (critical).
4 now your phone is s-0ff and locked. leave it just that way: no unlocks ever needed again and no pink warnings
5 flash Android police newest ICS RUU
6 flash amon ra as a PBIMG in recovery
7 use amon ra to wipe and install ANYTHING you want
Click to expand...
Click to collapse
yep
yo!
hboot is bootloader alright: some folks like a modified hboot which lets you do more than stock hboot.
personally I keep the stock ICS hboot 2.25.
nope, you dont have to be s-0ff to be rooted, only unlocked.
You can do most all modifications with unlock EXCEPT go back to previous hboot & rom.
Recovery is separate from hboot. Recovery is a menu choice in hboot.
A new recovery can only be installed if unlocked or s-0ff.
There's ClockworkMod and AmonRa. You'll wanna check them out both, I like Amon Ra.
re: step #4.
I know it's counterintuitive, but if you unlock it again after s-0ff, even though it's s-0ff, you will
have a nasty PINK Tampered flag every time you boot to hboot/custom recovery. And that crappy reminder stays
even after you you relock. The Juopunutbear process relocks the phone, making it S-0ff, Locked. Perfect.
Now with S-0ff, locked or unlocked doesn't matter regarding any roms or radios you may install and No warning flags.
Dont be intimidated by the wire procedure for s-0ff, just read it so many times beforehand that you effen KNOW it.
Enjoy: my Zound is so fast cool and perfect now that ive customized it to my useage pattern - hoping for
same experience for you!.
dashbored said:
Hi all! This is my first post and hope it's not too silly of a question. I am currently using a Thunderbolt but very likely will be upgrading to a Rezound (I have both phones now). I know the ICS OTA is out for Rezound. I want to get root and S-off on Rezound running the stock ICS OTA, but I am not sure about the order of events.
1. Should I get S-off and root on the stock Gingerbread rom per the instructions in this thread (http://forum.xda-developers.com/showthread.php?t=1823362), and then upgrade to the ICS OTA? Or should I upgrade the stock Gingerbread to ICS OTA and then attempt to get S-off and root?
2. Is a confirmed s-off/root procedure out for the stock ICS OTA? sorry if I missed it - I promise I did my best searching through the forum before posting
I thought I'd start with the stock ICS OTA rom so I'll get a baseline for when I try out other roms down the road. And from what I've read here, the stock rom is probably a little bit more robust for day to day (correct me if I am wrong!). I hate the verizon bloatware and I think I'd be happy for a while if I can have S-off and root on the stock ICS.
thanks in advance for any help!
Click to expand...
Click to collapse
I basically had the exact same questions. Here's what I figured out:
S-Off, then Stock Recovery, then ICS OTA:
http://forum.xda-developers.com/showthread.php?t=1821303
After post #6, go to the next link...
... Then flash AR Recovery 3.15:
http://forum.xda-developers.com/showthread.php?t=1827263
I had to unlock my hboot again, which means I wiped my data... However, I've read that adding a custom hboot is very risky, since your phone can't run anything if this gets screwed up. I'm no expert, but this is what I've read. So re-unlocking felt safer to me, even if it was probably a little more hassle. Better than bricking, imo.
A word of caution about custom recovery: Clockwork Mod (CWM) has a serious bug that does not allow the Rezound to charge properly! When my battery died, I had to use my wife's Thunderbolt to charge the battery before I could turn my Rezound back on... A royal pain. I installed AR Recovery, and it's perfect.
... Then continue at the first link at post #7 for how to use AR Recovery to flash superSU to restore root.
I'm thinking about writing up a simple guide, since that was the hardest thing for me to find through this process.
Rezound
AR Recovery 3.15
Stock hboot
ICS OTA
Rooted
I sold the Thunderbolt today and so now I've officially transitioned over to the Rezound! The phone is the stock gingerbread. I am dying to root it if only just so I can use titanium back up to transfer my crap over.
Thanks guys for the helpful replies! I've decided that right now, what I want is to be on the ICS OTA but with S-off & root so I can remove the bloat and optimize it. I'll stay with that for a bit to get a baseline before trying out different ROMs
What kind of wires did you guys use for the S-off procedure? Do I need to go out and buy something specific, or is there something around the typical household setting that I can grab? Obviously, not frying the phone is top priority. I've read through too much posts in the past 48 hours and I've come across a few that mentioned fried USB ports and even dead phones that had to be returned, which's made me a bit tentative. But I want S-off, so any pointers/comments you may have that would help about this would be much appreciated!
michaelbsheldon - question about your steps #1 & #2. Aren't these extraneous steps, as in you could just do the S-off wire with the stock Gingerbread? I am kinda confused as to the purpose of unlocking it first via HTC Dev and flashing a stockish ROM before the wire trick.
bloodymurderlive said:
I basically had the exact same questions. Here's what I figured out:
S-Off, then Stock Recovery, then ICS OTA:
http://forum.xda-developers.com/showthread.php?t=1821303
After post #6, go to the next link...
... Then flash AR Recovery 3.15:
http://forum.xda-developers.com/showthread.php?t=1827263
I had to unlock my hboot again, which means I wiped my data... However, I've read that adding a custom hboot is very risky, since your phone can't run anything if this gets screwed up. I'm no expert, but this is what I've read. So re-unlocking felt safer to me, even if it was probably a little more hassle. Better than bricking, imo.
A word of caution about custom recovery: Clockwork Mod (CWM) has a serious bug that does not allow the Rezound to charge properly! When my battery died, I had to use my wife's Thunderbolt to charge the battery before I could turn my Rezound back on... A royal pain. I installed AR Recovery, and it's perfect.
... Then continue at the first link at post #7 for how to use AR Recovery to flash superSU to restore root.
I'm thinking about writing up a simple guide, since that was the hardest thing for me to find through this process.
Rezound
AR Recovery 3.15
Stock hboot
ICS OTA
Rooted
Click to expand...
Click to collapse
Thanks for the tip about the CWM recovery! As I no longer have a thunderbolt, I would've been totally screwed. Question though - it sounds like you did what michaelbsheldon said not to do, re-unlock after you're S-off. Do you have the pink flag that he mentioned?
So here's my plan to get my Rezound into a S-off, rooted ICS OTA - please let me know if it's valid:
1a (waiting for michaelbsheldon reply if truly necessary, or if can proceed on stock GB) - HTC Dev unlock and flash Cleanrom 175
1. S-off wire procedure
2. Apply ICS OTA update
3. Apply global roaming update (if available? read about this in the past few days)
4. Since no need to unlock, flash appropriate Superuser for ICS OTA (will google, or if anyone would like to help make sure I find the right one, please feel free to link )
5. flash Amonra recovery. Keep stock hboot.
6. Install root explorer to delete VZ bloatware and titanium backup to restore apps and data from Thunderbolt
dashbored said:
Thanks for the tip about the CWM recovery! As I no longer have a thunderbolt, I would've been totally screwed. Question though - it sounds like you did what michaelbsheldon said not to do, re-unlock after you're S-off. Do you have the pink flag that he mentioned?
So here's my plan to get my Rezound into a S-off, rooted ICS OTA - please let me know if it's valid:
1a (waiting for michaelbsheldon reply if truly necessary, or if can proceed on stock GB) - HTC Dev unlock and flash Cleanrom 175
1. S-off wire procedure
2. Apply ICS OTA update
3. Apply global roaming update (if available? read about this in the past few days)
4. Since no need to unlock, flash appropriate Superuser for ICS OTA (will google, or if anyone would like to help make sure I find the right one, please feel free to link )
5. flash Amonra recovery. Keep stock hboot.
6. Install root explorer to delete VZ bloatware and titanium backup to restore apps and data from Thunderbolt
Click to expand...
Click to collapse
I'm going to give you a response this afternooon... I recommend that you don't do anything until I can clarify some things. brt...
dashbored said:
Thanks for the tip about the CWM recovery! As I no longer have a thunderbolt, I would've been totally screwed. Question though - it sounds like you did what michaelbsheldon said not to do, re-unlock after you're S-off. Do you have the pink flag that he mentioned?
So here's my plan to get my Rezound into a S-off, rooted ICS OTA - please let me know if it's valid:
1a (waiting for michaelbsheldon reply if truly necessary, or if can proceed on stock GB) - HTC Dev unlock and flash Cleanrom 175
1. S-off wire procedure
2. Apply ICS OTA update
3. Apply global roaming update (if available? read about this in the past few days)
4. Since no need to unlock, flash appropriate Superuser for ICS OTA (will google, or if anyone would like to help make sure I find the right one, please feel free to link )
5. flash Amonra recovery. Keep stock hboot.
6. Install root explorer to delete VZ bloatware and titanium backup to restore apps and data from Thunderbolt
Click to expand...
Click to collapse
It doesn't matter much if you do the OTA update before or after s-off. If it were me, I would do the OTA update first, especially if you are still locked....then unlock and do s-off using the proper ICS (for .5) jounuputbear. You can keep the stock hboot. NO NEED to unlock after s-off! AFter s-off, flash your Amonra recovery and then flash your SU...or just flash a rooted ROM. I haven't looked a lot, but I bet there is a stock, rooted, debloated ROM based on this OTA...just flash that and you'll be all set! ....
dashbored said:
Thanks for the tip about the CWM recovery! As I no longer have a thunderbolt, I would've been totally screwed. Question though - it sounds like you did what michaelbsheldon said not to do, re-unlock after you're S-off. Do you have the pink flag that he mentioned?
So here's my plan to get my Rezound into a S-off, rooted ICS OTA - please let me know if it's valid:
1a (waiting for michaelbsheldon reply if truly necessary, or if can proceed on stock GB) - HTC Dev unlock and flash Cleanrom 175
1. S-off wire procedure
2. Apply ICS OTA update
3. Apply global roaming update (if available? read about this in the past few days)
4. Since no need to unlock, flash appropriate Superuser for ICS OTA (will google, or if anyone would like to help make sure I find the right one, please feel free to link )
5. flash Amonra recovery. Keep stock hboot.
6. Install root explorer to delete VZ bloatware and titanium backup to restore apps and data from Thunderbolt
Click to expand...
Click to collapse
dashbored... The thing you need to understand is that everyone has their own way of doing things. You need to either (a) study everything everyone says until you understand everything well enough to create your own process, or (b) follow somebody else's process. I will provide you with one below.
In regards to the latest comments...
Flash CleanROM?
I see very little point in flashing a ROM, if you're trying to get the official ICS, root, and S-OFF. I believe the purpose of flashing the ROM is that the ROM is already rooted for you. However, you will need to re-root after you install the OTA, so why not do the same process twice (flash superSU) rather than two different processes (flash ROM, flash superSU)? Seems to me that flashing CleanROM introduces more variables than necessary.
MOST IMPORTANTLY: Maybe I don't know what I'm talking about, but I wouldn't try to install the OTA unless you are running stock Gingerbread. Alternatively, you could try to find a ROM based on the official ICS OTA, but the OTA is still very new... I would just do it the "proper" way (install through Gingerbread) and let those ROMs cook a little more before playing with them.
S-OFF before or after OTA?
I recommend achieving S-OFF before installing the OTA. The S-OFF procedure may very well work with the OTA, but it is guaranteed to work with stock Gingerbread. There is an ICS option in hansoon2000's all-in-one toolkit, but this is based on a leak... Which again is probably very similar (if not identical) to the OTA. But the official OTA is very new, so... In my opinion, the surest thing is to achieve S-OFF before installing the OTA.
Unlock after S-OFF?
My bootloader was locked after I installed the OTA update. What I discovered was that I was unable to flash any custom recoveries (AR Recovery 3.15). Even though I was S-OFF, I still needed to unlock before it would let me flash a recovery.
What I think some people do after achieving S-OFF is install a custom bootloader, and this is why they're able to install custom recoveries without having to unlock again. This is risky. As I understand it, nothing can run on your Rezound if your bootloader has a problem. So if you happen to install a corrupt bootloader, you could brick your Rezound.
It is kind of a pain to go through the HTC unlock process twice, but hey... It's up to you how much risk you're willing to take with your brand new Rezound. I took the safe route. It took maybe a little more time, and I had to do some steps twice (achieving root for GB, then for ICS... unlocking before and after ICS...), but since you only have to go through this whole process once, I recommend playing it safe.
PINK Tampered flag?
I unlocked again after achieving S-OFF. I just double-checked, and I do not see any pink "Tampered" flag anywhere in my bootloader. If you follow my instructions below, this shouldn't happen.
My start-to-finish recommendation:
If the end result you're looking for is ICS OTA, rooted, S-OFF, then I recommend you follow these guides, in the following order:
1: Scotty's noob-friendly guide to root Rezound:
http://androidforums.com/rezound-al...ys-noob-friendly-root-guide-start-finish.html
One thing to note: Scotty gives instructions both for temporary and permanent flashing of custom recovery. In your case, I would recommend doing the temporary flash. This will allow you to flash superSU (achieve root) - which you need to do in order to achieve S-OFF - but it will also save you the hassle of later having to flash the stock recovery back - which you need to have in order to install the OTA.
2: My guide to achieve S-OFF:
https://docs.google.com/document/d/1_kRxD5LtazP7vEnr9cDb3iHwWB1ZfJD_yn6xXo7d1bo/edit
3: My guide to install the OTA after rooting and S-OFF:
https://docs.google.com/document/d/1tmlh4OnplVfBNSjSyXfTYIVGfyb9lgI6ABpfg7gHY44/edit
If you flashed a temporary recovery, then you can skip to step 7 in this guide to verify that you have stock recovery on your device. If you do, then you should be able to initiate the OTA from within Gingerbread, and successfully install. In other words: If you flashed a temporary recovery, you can follow steps 7 to the end in this guide.
These three guides together, in the order that I listed them, are the exact steps I followed to achieve the same thing that you say you're shooting for: official ICS, rooted, S-OFF. I think these steps are the least risky steps you can take to achieve these things.
Keep us posted on how it goes!
bloodymurderlive said:
dashbored
Unlock after S-OFF?
My bootloader was locked after I installed the OTA update. What I discovered was that I was unable to flash any custom recoveries (AR Recovery 3.15). Even though I was S-OFF, I still needed to unlock before it would let me flash a recovery.
What I think some people do after achieving S-OFF is install a custom bootloader, and this is why they're able to install custom recoveries without having to unlock again. This is risky. As I understand it, nothing can run on your Rezound if your bootloader has a problem. So if you happen to install a corrupt bootloader, you could brick your Rezound.
Keep us posted on how it goes!
Click to expand...
Click to collapse
FYI: AFter you s-off you can not use fastboot flash commands unless you install the JB Hboot at the end of the S-off process (it should offer you the option) That is the custom hboot you refer to. All flashers are encouraged to check MD5 sum of the files they download before flashing (primarily RUU, hboot/radios..not so much roms). This will guard against corrupted files, making the process less risky.
If you have the ph98img.zip file version of amonra, it will flash just fine in the stock hboot. Hboot picks it up when it scans for ph98img.zip files and you select yes to install.
Personally, I've kept the stock hboot because there are ph98img.zip files of anything I've needed to flash so I don't have a need to be using a lot of fastboot commands.
topgun1953 said:
Personally, I've kept the stock hboot because there are ph98img.zip files of anything I've needed to flash so I don't have a need to be using a lot of fastboot commands.
Click to expand...
Click to collapse
Exactly... I prefer that my Rezound is self-sufficient, without needing a PC to mess with it.
Good note on fast boot!
stock or rooted
Dashboard:
Juopunutbear instructions require a rooted rom.
So if you wanna go S-0ff, you CAN use a stock rom, but it must
be rooted (SU and Busybox) for the S-0ff process to work.
michaelbsheldon said:
Hiya, You're getting ready to become addicted to roms, by the way.
All your choices are kind of 'what do you want' things, but assuming you
receive it with stock Gingerbread, easiest thing would be to:
1 unlock by way of HTC Development instructions - lots of info here on xda
2 flash Cleanrom 175 a gingerbread stockish rooted rom
3 do the S-0ff thing with Juopunutbear, being careful not to amend or skip
any instructions in the S-0ff recipe (critical).
4 now your phone is s-0ff and locked. leave it just that way: no unlocks ever needed again and no pink warnings
5 flash Android police newest ICS RUU
6 flash amon ra as a PBIMG in recovery
7 use amon ra to wipe and install ANYTHING you want
Click to expand...
Click to collapse
I am new to this and need help when performing a wipe with amon ra there are a lot of options in recovery for the wipe, and I am not sure which option to do. Can you help.
Thanks
flspanky said:
I am new to this and need help when performing a wipe with amon ra there are a lot of options in recovery for the wipe, and I am not sure which option to do. Can you help.
Thanks
Click to expand...
Click to collapse
What are you trying to accomplish? Root? In that case, I believe you need to use amon ra to Wipe cache, then Wipe dalvik cache. Then.com use it to flash superSU.
bloodymurderlive said:
dashbored... The thing you need to understand is that everyone has their own way of doing things. You need to either (a) study everything everyone says until you understand everything well enough to create your own process, or (b) follow somebody else's process. I will provide you with one below.
In regards to the latest comments...
Keep us posted on how it goes!
Click to expand...
Click to collapse
Wow thank you for that informative reply! That really cleared up all of my questions. I now have two new, minor questions.
1. The audio clip for the S-off wire trick has two distinct tones. From watching the video, it looks like the different tones don't matter. Basically just hit tap and release as the metronome hits the first beat, and then again on the second beat. Correct?
2. This is probably a silly question, but what are the advantages of Amon Ra recovery over the stock?
I am too tired tonight, but I think I am going to give this a go this weekend...
michaelbsheldon said:
Dashboard:
Juopunutbear instructions require a rooted rom.
So if you wanna go S-0ff, you CAN use a stock rom, but it must
be rooted (SU and Busybox) for the S-0ff process to work.
Click to expand...
Click to collapse
Gotcha. Thanks for clearing that up for me!
bloodymurderlive said:
What are you trying to accomplish? Root? In that case, I believe you need to use amon ra to Wipe cache, then Wipe dalvik cache. Then.com use it to flash superSU.
Click to expand...
Click to collapse
Thanks. I was installing the ICS Global root and ROM and the instructions said to wipe all, and I was not sure how many areas under the wiping options I should perform.
Quick update - I've rooted my Rezound. Have not done the S-off wire trick yet. Still on stock GB.
Question - none of the wifi tether app seems to be working! Open garden was working perfectly for me with my old rooted Thunderbolt. A quick search seems to show that Rezound has issues with wifi tethering?! This was one of the main motivations behind rooting, so I am a feeling a bit underwhelmed right now with my new Rezound...
Newest wifi tether works fine...even has Rezound settings. Since you are still on GB search for sirgatez mod. Worked great for me when I was still on GB.
Sent from my HTC Rezound / ADR6425LVW using Tapatalk v2.2.7
So I have Scott's CleanROM GBE 1.7.5 on my phone. I was wandering through my phone's settings, and accidentally hit something in the update area. I do not know what I was thinking, but I know I expected it to ask me if I was sure I wanted to update. So far it has only done the first part where it prepares the phone for the update. I do not know when the other part is coming but I assume it is automatic. I was planning on updating to a rooted ICS once I felt comfortable with it (just seemed a little harder than my original flash of rooted GB). So if it would be easier to just update to ICS some way now, I would be very willing to do that. I am s-on, I believe I installed Amon Ra, but I am not sure how to check and not sure if I have an actual recovery rom or not.
I checked around and found similar problems, but nothing really like mine since my update has not gone all the way thru yet. If anyone could help, it would be greatly appreciated. THank you.
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ok just to make sure I know and don't mess anything else up. I relock (should be easy to.find a guide) . Then run the update on my phone? Then unlock thru HTC again, and flash the actual amon or CWM to my phone? And from there I will be able to flash any ICS Rom with more ease?
And thank you for the quick reply.
Edit: I searched the internet more for less-similar situations. I think all I have to do is re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Also,nothing I have to do as far as unrooting?
malignancyy said:
Also,nothing I have to do as far as unrooting?
Click to expand...
Click to collapse
Nope just relock the bootloader
AshtonTS said:
Nope just relock the bootloader
Click to expand...
Click to collapse
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
malignancyy said:
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Click to expand...
Click to collapse
Then you just have to press continue when it tells you to.
PS: Another way to get to the bootloader is to use adb (make sure USB debugging is enabled on your phone)
Command:
adb reboot bootloader
I find it easier than holding down buttons for a long time, but that's just my personal preference.
(Also, most custom ROMs can reboot to bootloader from within the ROM. I forget if CleanROM GBE includes the advanced power menu.)
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Good advise, and if he RUUs to ICS, then he should not even get asked to install the update because it will already be installed on his phone.
Also RUU twice. Just reboot into bootloader right away and install the RUU a second time. Then boot up normally and remove the zip file from the sdcard.
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
malignancyy said:
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
Click to expand...
Click to collapse
The jbear hboot might have failed because you are on the newest global update with 2.27 hboot, and I believe the controlbear tool still has the 2.25 hboot. (someone correct me if I'm wrong)
I think there is an unguarded 2.27 hboot somewhere, so you should flash that manually.
Sent from my NeoMax Rezound
Right now, like I said the hboot says at the top 2.27.0000
When I reboot from there, or boot it regularly it goes to a JuopunutBear, black and green writing screen.
I have tried to install this forum.xda-developers.com/showthread.php?t=1843030 ([HBOOT] HBoot 2.27 (from 4.03.605 OTA) Unlocked) from both, but cannot figure out how to do so.
edit: within JuopunutBear, wiping says "can't open" and applying update gives "failed to open loopdevice" and "failed to mount /sdcard" when I try to update.
Within the regular hboot, I get "no image" as it searches for files.
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
A little more info on this. Windows tries installing QHUSB_DLOAD driver for it when plugged in, but unsuccessfully. The charging indicator does not come on either. Have tried to turn it on plugged in with battery out, and battery in both ways.
malignancyy said:
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
Click to expand...
Click to collapse
Depending on what caused the brick, it may be recoverable.
Check out the unbricking thread in the dev section.
Sent from my NeoMax Rezound
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
malignancyy said:
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
Click to expand...
Click to collapse
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
wlmeng11 said:
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
Click to expand...
Click to collapse
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
malignancyy said:
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
Click to expand...
Click to collapse
That QA is outdated.
It was referring to using the 3.14.605.07 kernel as opposed to the then-most-recent 3.14.605.10
Back then those two builds were similar enough that they could mix n match without issues.
Between 3.14.605.12 and 4.03.605.1 is a lot of changes. (whole number change to represent it) Specifically, new hboot and radios. Therefore, it is incompatible with the older kernels.
When you're S-ON you can't touch the radios except through an official RUU.
Even with s-off I doubt you can flash radios from recovery (not sure on this one), and NeoMax doesn't have any radio files anyway. (nor does any rom I know for this phone)
If you haven't yet updated to 4.03.605.1 then I recommend that you stay on 3.14.605.12 until Neo updates the ROM.
If you already updated, it is still possible to run NeoMax. You just have to manually flash the new 4.03.605.1 kernel after installing the ROM.
Sent from my NeoMax Rezound
I have the 1.57 hboot and TWRP, stock ROM and kernel. Is there a way to get S-Off without flashing a different ROM? I like my phone the way it is except for the bloatware. I can uninstall it with Titanium Backup but every time I reboot, it just reinstalls it all. I have made a filter with all the bloat in TT that I run to quickly remove it but it would be nice to be able to reboot without uninstalling all the bloat each time. Is there a way to gain write permissions to the system partition without getting S-Off? I'm not very savvy when it comes to the more complicated processes involving using ADB and command lines, by the way, so if it involves a lot of that I may just have to keep doing what I'm doing. Any help or points in the right direction would be appreciated. Thanks!
If Firewater won't S-OFF your phone with the stock ROM, then your next step would be to create a nandroid of your current stock ROM, flash a custom ROM and try Firewater again. If it's successful in gaining S-OFF, you can then restore the nandroid of stock. If Firewater comes back with the message saying it can't gain S-OFF no matter what you try, then you're stuck S-ON for now. Restore your nandroid and you're back to where you started.
If you just want to remove the bloatware and not have it return, and don't care about getting S-OFF, I believe you can flash an insecure kernel, such as ElementalX. After you install the insecure kernel, run your script to delete the bloatware and it should be gone for good.
I'm not 100% positive about this though, maybe more like 98%, b/c I've been S-OFF from the beginning and not entirely sure on the limitation of being S-On w/ unlocked bootloader. But I'm running the stock ROM, with ElementalX kernel and I've removed bloatware and it doesn't come back for me.
Thank you!
sharksfan7 said:
If Firewater won't S-OFF your phone with the stock ROM, then your next step would be to create a nandroid of your current stock ROM, flash a custom ROM and try Firewater again. If it's successful in gaining S-OFF, you can then restore the nandroid of stock. If Firewater comes back with the message saying it can't gain S-OFF no matter what you try, then you're stuck S-ON for now. Restore your nandroid and you're back to where you started.
If you just want to remove the bloatware and not have it return, and don't care about getting S-OFF, I believe you can flash an insecure kernel, such as ElementalX. After you install the insecure kernel, run your script to delete the bloatware and it should be gone for good.
I'm not 100% positive about this though, maybe more like 98%, b/c I've been S-OFF from the beginning and not entirely sure on the limitation of being S-On w/ unlocked bootloader. But I'm running the stock ROM, with ElementalX kernel and I've removed bloatware and it doesn't come back for me.
Click to expand...
Click to collapse
Thanks! This is just the information I was looking for. I won't be able to try it for a week or so, but when I do I'll post back here with the results.