I am the cause of this problem, and hope someone can help to extricate me.
I bought my Rezound in April, excited that ICS was coming. I soon found the leaked ICS 4.0.3/Sense 3.6 and installed the leak, and have been (largely) happily enjoying it. There have been some small issues, and when I read that Verizon was finally sending ICS out to the Rezound, I checked and found that I couldn't get it unless my phone was put back to GB. That's when the problem started.
I've tried numerous ROMs, but really don't know what I'm doing, and after almost 20 hours of reading the various posts and searches, am no farther to a resolution than where I started yesterday.
The phone, no matter what I try to load, boots fine until it hits the 4G LTE screen and then freezes. Here's the HBOOT/FASTBOOT screen:
*** LOCKED ***
VIGOR PVT SHIP S-ON 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
I would love to get it whole enough to receive OTAs, but would be happy to get back where I started. Can someone help me please?
gandroid2 said:
I am the cause of this problem, and hope someone can help to extricate me.
I bought my Rezound in April, excited that ICS was coming. I soon found the leaked ICS 4.0.3/Sense 3.6 and installed the leak, and have been (largely) happily enjoying it. There have been some small issues, and when I read that Verizon was finally sending ICS out to the Rezound, I checked and found that I couldn't get it unless my phone was put back to GB. That's when the problem started.
I've tried numerous ROMs, but really don't know what I'm doing, and after almost 20 hours of reading the various posts and searches, am no farther to a resolution than where I started yesterday.
The phone, no matter what I try to load, boots fine until it hits the 4G LTE screen and then freezes. Here's the HBOOT/FASTBOOT screen:
*** LOCKED ***
VIGOR PVT SHIP S-ON 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
I would love to get it whole enough to receive OTAs, but would be happy to get back where I started. Can someone help me please?
Click to expand...
Click to collapse
Someone more knowledgeable may correct me, but HBOOT 2.27 & 2.22 radios are the newest version. So you're already upgraded to the newest stuff. Try installing an AOSP or ICS ROM and see if that works.
I made progress?
d.kozzer said:
Someone more knowledgeable may correct me, but HBOOT 2.27 & 2.22 radios are the newest version. So you're already upgraded to the newest stuff. Try installing an AOSP or ICS ROM and see if that works.
Click to expand...
Click to collapse
Thank you, that's actually more good news than I expected!
I have lost total confidence in any knowledge I thought I had. If someone could give me 1st grader level guidance toward installing an AOSP or ICS ROM, I would be most appreciative.
gandroid2 said:
Thank you, that's actually more good news than I expected!
I have lost total confidence in any knowledge I thought I had. If someone could give me 1st grader level guidance toward installing an AOSP or ICS ROM, I would be most appreciative.
Click to expand...
Click to collapse
It's easy.... if you like AOSP/CM9, I'd recommend the "le n00b" ROM in the dev section. If you like Sense 3.6, try Vigor360. If you like Sense 4, I really liked ViperRom. Just go to the OP of any thread for those, download the newest version to a PC or onto your SD card.
Then, go check out Scotty's noob friendly guide to rooting on AndroidForums (there might be an equivelent thread here, but I used this guide). I recommend using Amon Ra as your recovery, which is linked toward the top of the first post.
gandroid2 said:
Thank you, that's actually more good news than I expected!
I have lost total confidence in any knowledge I thought I had. If someone could give me 1st grader level guidance toward installing an AOSP or ICS ROM, I would be most appreciative.
Click to expand...
Click to collapse
if you want to go aosp you will need to s-off the phone to get there.
but you are on the latest update. you can only run roms built off the global ruu such as:
http://forum.xda-developers.com/showthread.php?t=1852119
http://forum.xda-developers.com/showthread.php?t=1860632
http://forum.xda-developers.com/showthread.php?t=1855605
to flash said roms you will need to htc dev unlock and then flash a recovery and then you can do any of the three roms above. if you want to be on a rom that is build off an older release you will need to s-off the phone.
d.kozzer said:
It's easy.... if you like AOSP/CM9, I'd recommend the "le n00b" ROM in the dev section. If you like Sense 3.6, try Vigor360. If you like Sense 4, I really liked ViperRom. Just go to the OP of any thread for those, download the newest version to a PC or onto your SD card.
Then, go check out...QUOTE]
Thanks a bunch. I've opened Scotty's guide to read next, and have downloaded Amon Ra (recovery-ra-vigor-3.15-gnm.img.zip). I've looked up some comparisons between Sense 3 & 4, which should help me make an informed decision. Thanks again for the guidance and suggestions.
Click to expand...
Click to collapse
synisterwolf said:
if you want to go aosp you will need to s-off the phone to get there.
but you are on the latest update. you can only run roms built off the global ruu such as:
to flash said roms you will need to htc dev unlock and then flash a recovery and then you can do any of the three roms above. if you want to be on a rom that is build off an older release you will need to s-off the phone.
Click to expand...
Click to collapse
Thanks synisterwolf.
I'll look at the roms you recommended and appreciate the information and wisdom you shared.
I'll also check out the organizations listed in your signature.
Thanks again.
I would use hasoons toolkit to unlock and install amon ra. The 4.03.605.2 RUU runs smooth and quick.
gandroid2 said:
d.kozzer said:
It's easy.... if you like AOSP/CM9, I'd recommend the "le n00b" ROM in the dev section. If you like Sense 3.6, try Vigor360. If you like Sense 4, I really liked ViperRom. Just go to the OP of any thread for those, download the newest version to a PC or onto your SD card.
Then, go check out...QUOTE]
Thanks a bunch. I've opened Scotty's guide to read next, and have downloaded Amon Ra (recovery-ra-vigor-3.15-gnm.img.zip). I've looked up some comparisons between Sense 3 & 4, which should help me make an informed decision. Thanks again for the guidance and suggestions.
Click to expand...
Click to collapse
Unfortunately, Scotty's guide won't work for me, as its unlock with htcdev section requires the Rezound to connect to my PC via usb, but the phone's somewhat bricked, locking up at the 4G LTE screen and won't connect.
I would surely appreciate other suggestions. Plemelin recommended hasoons toolkit, and I will look at it now.
Thanks again.
Click to expand...
Click to collapse
plemelin said:
I would use hasoons toolkit to unlock and install amon ra. The 4.03.605.2 RUU runs smooth and quick.
Click to expand...
Click to collapse
Thank you. I'm looking at it next.
plemelin said:
I would use hasoons toolkit to unlock and install amon ra. The 4.03.605.2 RUU runs smooth and quick.
Click to expand...
Click to collapse
Yeah, this is a good tool too.
gandroid2 said:
Thank you. I'm looking at it next.
Click to expand...
Click to collapse
For Scotty's guide, you're clearly on the HTC Unlock stage,maybe you should find the latest RUU and flash that? It'll have all parts of the phone's system (ROM, bootloader, recovery, radios, etc), so you'll have a clean phone (meaning all data will be wiped), and all the different pieces will work together and you should be able to boot into the stock ROM, then follow the guide from there starting with the HTC unlock. I think where you were at in post #1, you had all the ICS/global firmware but were trying to boot a gingerbread ROM which will fail every time. If you use an RUU, everything will be in sync.
d.kozzer said:
Yeah, this is a good tool too.
For Scotty's guide, you're clearly on the HTC Unlock stage,maybe you should find the latest RUU and flash that? It'll have all parts of the phone's system (ROM, bootloader, recovery, radios, etc), so you'll have a clean phone (meaning all data will be wiped), and all the different pieces will work together and you should be able to boot into the stock ROM, then follow the guide from there starting with the HTC unlock. I think where you were at in post #1, you had all the ICS/global firmware but were trying to boot a gingerbread ROM which will fail every time. If you use an RUU, everything will be in sync.
Click to expand...
Click to collapse
Nice,that's the original version which started this journey. I had downloaded it prior to starting all this, and messed up my Rezound by not doing it correctly. Now it's the one which (finally) worked. I don't know how it worked, unfortunately, as it didn't work exactly like Scotty told me it would, and the first few times I tried to install it were unsuccessful also.
Thanks again.
It's alive!
Thank you all for your help. Your replies encouraged me and directed me toward the solution.
Scotty's guide worked, although not exactly like it said it would. I now have the version I originally wanted, and it all works, except for the SU.
I installed CWM-SuperSU-v0.96.zip per Scotty, but I have don't have the SU ability. Undoubtedly did something wrong.
Thanks again.
gandroid2 said:
Thank you all for your help. Your replies encouraged me and directed me toward the solution.
Scotty's guide worked, although not exactly like it said it would. I now have the version I originally wanted, and it all works, except for the SU.
I installed CWM-SuperSU-v0.96.zip per Scotty, but I have don't have the SU ability. Undoubtedly did something wrong.
Thanks again.
Click to expand...
Click to collapse
Glad to help!
If you're using SU, then open up the app by going into the app drawer and see if there's a way for you to "update the binary". The binary is the meat and bones of the superuser app, and for some reason it's not working well out of the box on some roms, and you need to update it to get it working.
d.kozzer said:
Glad to help!
If you're using SU, then open up the app by going into the app drawer and see if there's a way for you to "update the binary". The binary is the meat and bones of the superuser app, and for some reason it's not working well out of the box on some roms, and you need to update it to get it working.
Click to expand...
Click to collapse
Apparently I'm not using SU after all.I tried to update with superuser and it "Failed to find currently installed su binary". I also opened Titanium Backup and it couldn't acquire root privileges. I missed something...
Related
I am beyond feeling like a ReeeTard right now. As someone who beta tests for a lot of ROM builders and knows a great deal about Android, software development etc... please don't reply to this with a smart a** remark. It helps no one and makes you look like just a jerk.
We all have our days where we simply cannot think straight, I am dealing with a great deal of stress, in my life, so forgive me for somehow not finding the answer to this question.
I updated my phone, using an RUU...My phone WAS hboot 1.40, now however it's hboot 1.50, and it's UNLOCKED (the bootloader) as well as S-Off, Am I forgetting to do something to have ROOT access?
So I am hboot 1.50 UNLOCKED and S-off
With all of those things I thought, because I cant seem to think clearly right now, that I was rooted. I however ran root checker and I am not.
Please throw me a bone and fill me in on what I am missing here. It's been a rough couple weeks for me.
Much appreciated.
quickfixguru said:
I am beyond feeling like a ReeeTard right now. As someone who beta tests for a lot of ROM builders and knows a great deal about Android, software development etc... please don't reply to this with a smart a** remark. It helps no one and makes you look like just a jerk.
We all have our days where we simply cannot think straight, I am dealing with a great deal of stress, in my life, so forgive me for somehow not finding the answer to this question.
I updated my phone, using an RUU...My phone WAS hboot 1.40, now however it's hboot 1.50, and it's UNLOCKED (the bootloader) as well as S-Off, Am I forgetting to do something to have ROOT access?
So I am hboot 1.50 UNLOCKED and S-off
With all of those things I thought, because I cant seem to think clearly right now, that I was rooted. I however ran root checker and I am not.
Please throw me a bone and fill me in on what I am missing here. It's been a rough couple weeks for me.
Much appreciated.
Click to expand...
Click to collapse
Hey! No worries man. You're almost there. All you need to do is flash a recovery now. Choose a recovery, and flash it, either a pg86img.zip or a recovery.img, and flash it. Once you have recovery flashed, either just flash a rooted ROM, or flash a su.zip. Then you should be good to go.
Sent from my PG86100 using Tapatalk
Thanks a lot man, I appreciate it. I knew I needed to flash superuser I just wanted to be sure it was just flash a recovery then su.zip
quickfixguru said:
Thanks a lot man, I appreciate it. I knew I needed to flash superuser I just wanted to be sure it was just flash a recovery then su.zip
Click to expand...
Click to collapse
You're welcome. Glad to help. Let me know if you have further questions. if you just decide to flash a su.zip, as opposed to an entire custom rom, you'd probably have the best luck looking in the old original TWRP thread for one. I know that had a su.zip posted in it. I'll see if i can find it for you real quick.
EDIT: Here's a super user zip http://techerrata.com/toastcfh/Shooter/su-2.3.6.3-efgh-fixed-unsigned.zip that I found in the 3rd post of this old thread http://forum.xda-developers.com/showthread.php?t=1192077&highlight=twrp+recovery. That's not the newest super user app, but it should work just fine, and you should be able to update it from there once you get it installed.
buckley nailed it!
i was actually unaware that updating your bootloader would still leave you s-off if you were on 1.4. that is interesting... although i would still never update.
did you know that it would still leave you with your NAND unlocked when you updated?
cobraboy85 said:
buckley nailed it!
i was actually unaware that updating your bootloader would still leave you s-off if you were on 1.4. that is interesting... although i would still never update.
did you know that it would still leave you with your NAND unlocked when you updated?
Click to expand...
Click to collapse
Yea, updating will still leave you S-off. You won't have a custom recovery anymore, and you'll be on hboot 1.5, but you still have S-off. There is pretty much no way that I know of to turn it back to S-on without going into fastboot and doing that 'fastboot setsecureflag3' command or whatever it is. The revolutionary team gave us some pretty damn permanent S-off, lol. I've seen lots of people take OTA updates, and still have S-off. You can even downgrade the hboot back to 1.4 if you wanted to, even though there really isn't a reason to. Having hboot 1.5 with S-off is just the same as having 1.4 with s-off, you don't need to do any extra stuff to flash.
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
Hello,
I installed the AOKP "adrenalized" ROM yesterday (http://forum.xda-developers.com/showthread.php?t=1884085), and while I initially had a great experience with it, it seems several things have started to go wrong for me.
The most pressing issue is that I can no longer make any phone calls... within the first 12 hours or so of having the ROM, this was not an issue (I received a phone call), but all of a sudden, I no longer have any mobile signal (either 4g or 3g) whatsoever, and if I try to make a call, it says "Mobile network not available." I tried searching online for help with this, but I could not find anything.
The other two issues (these are not as pressing as my inability to make/receive calls) are a persistent error that I have a "Damaged SD card" and I can't access my internal storage when I hook up my phone to my PC. I did find someone else on another phone having an issue with AOKP/damaged sd card, but the fix suggested (editing a file called vold.fstab) did not work (the line to edit in the file was not present in my file).
Sorry for the long post - I am fairly inexperienced when it comes to this stuff, but any help is greatly appreciated.
rocketman13 said:
Hello,
I installed the AOKP "adrenalized" ROM yesterday (http://forum.xda-developers.com/showthread.php?t=1884085), and while I initially had a great experience with it, it seems several things have started to go wrong for me.
The most pressing issue is that I can no longer make any phone calls... within the first 12 hours or so of having the ROM, this was not an issue (I received a phone call), but all of a sudden, I no longer have any mobile signal (either 4g or 3g) whatsoever, and if I try to make a call, it says "Mobile network not available." I tried searching online for help with this, but I could not find anything.
The other two issues (these are not as pressing as my inability to make/receive calls) are a persistent error that I have a "Damaged SD card" and I can't access my internal storage when I hook up my phone to my PC. I did find someone else on another phone having an issue with AOKP/damaged sd card, but the fix suggested (editing a file called vold.fstab) did not work (the line to edit in the file was not present in my file).
Sorry for the long post - I am fairly inexperienced when it comes to this stuff, but any help is greatly appreciated.
Click to expand...
Click to collapse
Need a little bit more info for me to be helpful. S-on or off? Did you verify MD5 before installing? What rom did you come from? Latest firmware? Anything you can provide about your setup would be useful. TBH, it sounds like you had a bad download, so I'd try to re-download and verify MD5 before you install.
iamwalterwhite said:
Need a little bit more info for me to be helpful. S-on or off? Did you verify MD5 before installing? What rom did you come from? Latest firmware? Anything you can provide about your setup would be useful. TBH, it sounds like you had a bad download, so I'd try to re-download and verify MD5 before you install.
Click to expand...
Click to collapse
Thanks for your reply, iamwalterwhite. Here is the relevant information:
S-On
Previous ROM before AOKP: Scott's CleanROM Pro 4.5
Firmware: Android Version 4.0.4
Baseband version: 0.95.00.1118r, 0.95.00.1223r
Unfortunately, I did not check the MD5 before I installed because I thought the risk of not doing it would be low. Apparently, I was wrong! Given that information, do you think it is still worth verifying MD5 and re-installing AOKP? Thanks.
You are still on gb firmware. Flashing the old firmware patch may help.
Sent from my Kindle Fire using Tapatalk 2
pwned3 said:
You are still on gb firmware. Flashing the old firmware patch may help.
Sent from my Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Wow, really? How can you tell? I thought Android version 4.0.4 was Ice Cream Sandwich, and I vaguely remember flashing a GB firmware patch when I first installed Scott's CleanROM 4.5, but my memory could be a bit fuzzy... should I just reboot to AmonRa recovery and flash it? Thanks for your help!
We can tell based off of your baseband version. Honestly, I think you should re-lock then flash the newest RUU. It will probably clear up your problem. If you'd still like, I can tell you how to check an MD5, but I think it's best if you flash that RUU. It's worth it, our radios have gone through multiple updates since the version that you have.
iamwalterwhite said:
We can tell based off of your baseband version. Honestly, I think you should re-lock then flash the newest RUU. It will probably clear up your problem. If you'd still like, I can tell you how to check an MD5, but I think it's best if you flash that RUU. It's worth it, our radios have gone through multiple updates since the version that you have.
Click to expand...
Click to collapse
Thanks, iamwalterwhite. I did some searching and found the latest RUU for the Rezound as 4.03.605.1 (I found it on Android Police, but I can't post the link since I'm a new user). However, it seems I am supposed to check the MD5 for that file as well.
Assuming that is the latest RUU though, then the steps I'd follow are: download the RUU/verify MD5, name it as PH98IMG.zip in my SDcard root, re-lock my bootloader, and finally reboot to AmonRa recovery to flash this RUU.
Are there any steps I am missing? Thanks again for your help... it is much appreciated.
You need to install in hboot not recovery. Running this will also write over your recovery. I suggest having the newest amon ra downloaded so you can unlock and flash it after the ruu
Sent from my Rezound using Xparent SkyBlue Tapatalk 2
rocketman13 said:
Thanks, iamwalterwhite. I did some searching and found the latest RUU for the Rezound as 4.03.605.1 (I found it on Android Police, but I can't post the link since I'm a new user). However, it seems I am supposed to check the MD5 for that file as well.
Assuming that is the latest RUU though, then the steps I'd follow are: download the RUU/verify MD5, name it as PH98IMG.zip in my SDcard root, re-lock my bootloader, and finally reboot to AmonRa recovery to flash this RUU.
Are there any steps I am missing? Thanks again for your help... it is much appreciated.
Click to expand...
Click to collapse
Have you set up an ADB folder? If so, place the RUU in your adb folder then execute this command in a command prompt:
cd c:\(your adb folder name)
You should then get a screen that looks like this:
c:\(your adb folder name)>
Then type: md5sums (ruu name).zip
Should look like this:
c:\(adb folder name)> md5sums (ruu name).zip
Your steps are mostly correct, however, you must flash the PH98IMG.zip via hboot. In fact, you won't be able to get to your recovery if you boot into your bootloader with the .zip on your sd card.
By the way, don't use the .1 RUU. Follow this link: http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ This is the .2 (seems like a hopelessly miniscule difference), but it's the most current.
Edit: Since you are s-on, you will need to unlock via HTCDEV after the RUU. Then you can go about installing AR 3.15 the same way as you did before. If you plan on going s-off, you might want to consider doing that before running the RUU. I know it's a lot of information, and a lot to sift through (not to mention the many different ways to do do things) but going s-off makes it much more simple.
iamwalterwhite said:
Have you set up an ADB folder? If so, place the RUU in your adb folder then execute this command in a command prompt:
cd c:\(your adb folder name)
You should then get a screen that looks like this:
c:\(your adb folder name)>
Then type: md5sums (ruu name).zip
Should look like this:
c:\(adb folder name)> md5sums (ruu name).zip
Your steps are mostly correct, however, you must flash the PH98IMG.zip via hboot. In fact, you won't be able to get to your recovery if you boot into your bootloader with the .zip on your sd card.
By the way, don't use the .1 RUU. Follow this link: This is the .2 (seems like a hopelessly miniscule difference), but it's the most current.
Edit: Since you are s-on, you will need to unlock via HTCDEV after the RUU. Then you can go about installing AR 3.15 the same way as you did before. If you plan on going s-off, you might want to consider doing that before running the RUU. I know it's a lot of information, and a lot to sift through (not to mention the many different ways to do do things) but going s-off makes it much more simple.
Click to expand...
Click to collapse
A HUGE thank you to both of you!! I restored my phone to the .2 RUU, and I now have a working phone and proper access to my internal storage. Unfortunately iamwalterwhite, I didn't see your message until after I finished installing the RUU, so I am still on S-On, but I am rooted. Do you know if I could still get to S-Off from this point (i.e. after installing RUU on my phone)?
Also, do you think it is ok to try re-installing the AOKP ROM that previously gave me problems (I verified the MD5), or should I hold off/try another ROM?
Again, thanks to you both, iamwalterwhite and pwned3. I was pretty lost otherwise.
rocketman13 said:
A HUGE thank you to both of you!! I restored my phone to the .2 RUU, and I now have a working phone and proper access to my internal storage. Unfortunately iamwalterwhite, I didn't see your message until after I finished installing the RUU, so I am still on S-On, but I am rooted. Do you know if I could still get to S-Off from this point (i.e. after installing RUU on my phone)?
Also, do you think it is ok to try re-installing the AOKP ROM that previously gave me problems (I verified the MD5), or should I hold off/try another ROM?
Again, thanks to you both, iamwalterwhite and pwned3. I was pretty lost otherwise.
Click to expand...
Click to collapse
Sorry to post again, but I just had an issue arise that has been pestering me for a while. Anytime my GPS is on, my phone shuts off and reboots within a minute or so... I know Rezound folks had this problem a while back due to the Google Maps update, but I've been having this for a while, even when I was on Scott's CleanROM and with fixed Maps. Now that I am on RUU (rooted), I hoped this problem would go away because I use Navigation a lot... but unfortunately, it is still here. I currently have Maps 6.12.0.
Does anyone have any thoughts/suggestions? Thanks.
rocketman13 said:
A HUGE thank you to both of you!! I restored my phone to the .2 RUU, and I now have a working phone and proper access to my internal storage. Unfortunately iamwalterwhite, I didn't see your message until after I finished installing the RUU, so I am still on S-On, but I am rooted. Do you know if I could still get to S-Off from this point (i.e. after installing RUU on my phone)?
Also, do you think it is ok to try re-installing the AOKP ROM that previously gave me problems (I verified the MD5), or should I hold off/try another ROM?
Again, thanks to you both, iamwalterwhite and pwned3. I was pretty lost otherwise.
Click to expand...
Click to collapse
You're welcome, that's why they call this here a community. If I was you, I wouldn't try to s-off right now. The reason I say that is because the juopunutbear method to s-off uses a different hboot (I believe the jbear hboot is .25 while the RUU is .27). That hboot was compatible with the ICS ota pre-global. You may have to wait until they get an update do to it. At this point, you will only have to worry about extracting the boot.img for roms that aren't global based (aokp being an example), but that should be a small annoyance. Much smaller, than say, bricking your phone!
iamwalterwhite said:
You're welcome, that's why they call this here a community. If I was you, I wouldn't try to s-off right now. The reason I say that is because the juopunutbear method to s-off uses a different hboot (I believe the jbear hboot is .25 while the RUU is .27). That hboot was compatible with the ICS ota pre-global. You may have to wait until they get an update do to it. At this point, you will only have to worry about extracting the boot.img for roms that aren't global based (aokp being an example), but that should be a small annoyance. Much smaller, than say, bricking your phone!
Click to expand...
Click to collapse
A number of people have been successful with S-OFF on hboot 2.27 using the .5 ControlBear. There seem to be no issues with it at all.
shrike1978 said:
A number of people have been successful with S-OFF on hboot 2.27 using the .5 ControlBear. There seem to be no issues with it at all.
Click to expand...
Click to collapse
Just found this thread: http://forum.xda-developers.com/showthread.php?t=1883924&page=2 It looks like there have been a few successes wit s-off even after the .2 RUU. Thanks Shrike!
iamwalterwhite said:
Just found this thread: It looks like there have been a few successes wit s-off even after the .2 RUU. Thanks Shrike!
Click to expand...
Click to collapse
Oh man, I'm not sure I'm brave enough to do the infamous "wire trick" just yet... but I will keep that link as a reference once I feel more confident.
Also, sorry to bother you again, but did any of you happen to see my previous post about my GPS:
rocketman13 said:
Sorry to post again, but I just had an issue arise that has been pestering me for a while. Anytime my GPS is on, my phone shuts off and reboots within a minute or so... I know Rezound folks had this problem a while back due to the Google Maps update, but I've been having this for a while, even when I was on Scott's CleanROM and with fixed Maps. Now that I am on RUU (rooted), I hoped this problem would go away because I use Navigation a lot... but unfortunately, it is still here. I currently have Maps 6.12.0.
Does anyone have any thoughts/suggestions? Thanks.
Click to expand...
Click to collapse
As always, thank you very much!!
rocketman13 said:
Oh man, I'm not sure I'm brave enough to do the infamous "wire trick" just yet... but I will keep that link as a reference once I feel more confident.
Also, sorry to bother you again, but did any of you happen to see my previous post about my GPS:
As always, thank you very much!!
Click to expand...
Click to collapse
I saw that post abou GPS, but I'm not familiar with that at all. The only thing that I recall was the problem with the upgrade in google maps. Apophis has a thread over in General where he lists his g-talk (along with some other users). He might be able to help.
iamwalterwhite said:
I saw that post abou GPS, but I'm not familiar with that at all. The only thing that I recall was the problem with the upgrade in google maps. Apophis has a thread over in General where he lists his g-talk (along with some other users). He might be able to help.
Click to expand...
Click to collapse
Ok, great! I'll see if I can ask about the GPS. Thanks for your help!
Hello! I used to be very engrossed in the modding community for the Rezound a few months ago. But because of a forced phone switch I haven't been in the loop for a while.
Well now I'm back on a Rezound and I was wanting to know a few things.
Fair warning. When I left we had just achieved S-off and were delving into the new things we could do from then on, so if my questions seem dated; I'm sorry.
Also, my phone atm is on stock ICS, I wanted to get a feel for everything again before I went and rooted it.
*Which are the most prominent ROMs right now? (Preferrably sense with beats)
*Do any of those ROMs have a working DSP Manager with Virtual room or ability to get it working on it?
*What is this whole GSM thing I'm seeing on some ROMs lists? Are we able to use the rezound easily overseas or on different networks now or something?
I have looked through some of the forums but haven't been able to find any concrete information, so I figured I would just post my own thread.
Thank you for your time and any replies!
The most prominent roms are any of the ones on the first two pages of the development sections. I know that neo includes a Beats mod in his AOSP roms which works as well as any stock beats you'll find in a sense rom. The DSP manager included with cyanogenmod is 100% functional as far as I can tell. And yes, we can use the rezound on AT&T (siul does MIUI and uses his rezound on AT&T) but I'm not sure as to what frequencies we have access to and if its HSPA or not.
Since you've been gone we received a global ruu that gives the rezound service over seas. The most prominent roms sense based are viperrez, newts one xxx, ecliptic rez and so on.. Those are just the ones I've tried. I'm running newts hybrid rom now and it's doing well though it's not as optimized as his one xxx rom
Sent from my ADR6425LVW using xda app-developers app
Alright, thanks for the info! And what are the best recoveries to use, now?
Volkaru said:
Alright, thanks for the info! And what are the best recoveries to use, now?
Click to expand...
Click to collapse
all the recoverys are about the same now. its up to you on what you want it to do. TWRP and CWMT are both great touch based recoveries. if you want more of the menu scroll classic way. go with AmonRA 3.15
Volkaru said:
Alright, thanks for the info! And what are the best recoveries to use, now?
Click to expand...
Click to collapse
TWRP, unbeatable! Not sure if it's available for your phone though..
Vangelis13 said:
TWRP, unbeatable! Not sure if it's available for your phone though..
Click to expand...
Click to collapse
It is. Installed it.
I think I'm all set now except for one thing. Is it normal now after you unlock and install a recovery for it to say TAMPERED? Last I saw that was when people were installing the leaked ICS RUUs.
The order of which I rooted my phone in case I did anything wrong was. Unlock bootloader with HTCDev, Phone restarted, let it load up then went into the menu and enabled Debugging again, shut it off. Reloaded fastboot. Then installed TWRP 2.3.3.0 using the All-in-one tool. After that my bootloader said TAMPERED.
Thanks again for all the help.
Volkaru said:
It is. Installed it.
I think I'm all set now except for one thing. Is it normal now after you unlock and install a recovery for it to say TAMPERED? Last I saw that was when people were installing the leaked ICS RUUs.
The order of which I rooted my phone in case I did anything wrong was. Unlock bootloader with HTCDev, Phone restarted, let it load up then went into the menu and enabled Debugging again, shut it off. Reloaded fastboot. Then installed TWRP 2.3.3.0 using the All-in-one tool. After that my bootloader said TAMPERED.
Thanks again for all the help.
Click to expand...
Click to collapse
Tampered is ok. It just means there's a custom recovery installed. Every now and then TWRP has some issues flashing certain files just so you know, most likely you'll never see it, but just in case it keeps you from chasing your tail I mentioned it.
We're s off now, that's the big change for when you want to do some wild modification. But thanks to snuzzo there's no harm done in being s on it's easier now than it used to be.
Anything else, send me a PM if you'd like and we can catch up on gtalk.
So is your hboot 2.25 and your radio basebands end in .421r and .424r?
CharliesTheMan said:
Tampered is ok. It just means there's a custom recovery installed. Every now and then TWRP has some issues flashing certain files just so you know, most likely you'll never see it, but just in case it keeps you from chasing your tail I mentioned it.
We're s off now, that's the big change for when you want to do some wild modification. But thanks to snuzzo there's no harm done in being s on it's easier now than it used to be.
Anything else, send me a PM if you'd like and we can catch up on gtalk.
So is your hboot 2.25 and your radio basebands end in .421r and .424r?
Click to expand...
Click to collapse
Alright, thanks for all the info. Will PM you later.
Everything was fully updated as far as stock goes.
Just updated to the 4.4.3 OTA then rooted flashed TWRP and install Venom One ROM. Now I get that annoying message on boot. My OCD is drving me nuts! found a few tutorials about flashing fastboot, but they all seem pretty old. Not sure if theres an update or an easy to fallow tutorial using adb or an AIO software. Thanks.
Need to wait for hboot to be modded to have that removed
Wonders_Never_Cease said:
Need to wait for hboot to be modded to have that removed
Click to expand...
Click to collapse
Ah okay thanks. Wasnt sure if Hboot was universal or if it was by build.
2.23.503.2 ota? If not s-off cannot flash firmware...if s-off the hboot has been modified already. Link is located in my thread in the at&t m8 section
Wonders_Never_Cease said:
2.23.503.2 ota? If not s-off cannot flash firmware...if s-off the hboot has been modified already. Link is located in my thread in the at&t m8 section
Click to expand...
Click to collapse
I'm on build 2.22.401.5 running VenomOne rom, S-Off, rooted all the good stuff. Will your hboot mod work for mine?
if on an att device its been discussed many times to use the appropriate firmware for us devices...2.22.1540.3/.4 is latest developer edition device firmware, 2.23.502.3 is latest for att devices...imo use one of those packages @firmware instead of euro.
Wonders_Never_Cease said:
if on an att device its been discussed many times to use the appropriate firmware for us devices...2.22.1540.3/.4 is latest developer edition device firmware, 2.23.502.3 is latest for att devices...imo use one of those packages @firmware instead of euro.
Click to expand...
Click to collapse
OK and I can just install either one of those hboots over my existing one and it wont brick my phone or is this more to this?
look in the htc one m8 forum since your using a euro firmware for the modified 2.22.401.5 hboot im sure its been done...
Wonders_Never_Cease said:
look in the htc one m8 forum since your using a euro firmware for the modified 2.22.401.5 hboot im sure its been done...
Click to expand...
Click to collapse
Found it, thanks man. Gonna mess with it a little later.
CavyS said:
Just updated to the 4.4.3 OTA then rooted flashed TWRP and install Venom One ROM. Now I get that annoying message on boot. My OCD is drving me nuts! found a few tutorials about flashing fastboot, but they all seem pretty old. Not sure if theres an update or an easy to fallow tutorial using adb or an AIO software. Thanks.
Click to expand...
Click to collapse
Hey Cavy..I got a couple of questions for you, if you don't mind. Were you completely stock after taking the 4.4.3 update? I just received my update a couple of days ago and I'm thinking about taking the plunge and rooting. How did you go about rooting and flashing Venom One? Thanks for your help!
thinkhope said:
Hey Cavy..I got a couple of questions for you, if you don't mind. Were you completely stock after taking the 4.4.3 update? I just received my update a couple of days ago and I'm thinking about taking the plunge and rooting. How did you go about rooting and flashing Venom One? Thanks for your help!
Click to expand...
Click to collapse
Yeah I was completely stock after updating. To root I used the AIO toolkit found here (http://forum.xda-developers.com/showthread.php?t=2699065) Once youre rooted reboot into recovery and make a backup. Then download the ViperOne rom here (http://venomroms.com/htc-one-m8/) copy the zip folder onto your SD or internal storage and reboot into recovery again and flash the ViperOne zip folder.
CavyS said:
Yeah I was completely stock after updating. To root I used the AIO toolkit found here (http://forum.xda-developers.com/showthread.php?t=2699065) Once youre rooted reboot into recovery and make a backup. Then download the ViperOne rom here (http://venomroms.com/htc-one-m8/) copy the zip folder onto your SD or internal storage and reboot into recovery again and flash the ViperOne zip folder.
Click to expand...
Click to collapse
You don't need to root if you are going to flash a custom ROM right away. Unlock bootloader, install custom recovery, then put the custom ROM on the phone and flash it.
So the toolkit still works?? Thought I read somewhere the 4.4.3 patched something. Are you also S-OFF??
Sent from my HTC One_M8 using XDA Free mobile app
redpoint73 said:
You don't need to root if you are going to flash a custom ROM right away. Unlock bootloader, install custom recovery, then put the custom ROM on the phone and flash it.
Click to expand...
Click to collapse
It was just easier for me to fallow a set of instructions going step by step than jumping around just to avoid 1 easy step.
thinkhope said:
So the toolkit still works?? Thought I read somewhere the 4.4.3 patched something. Are you also S-OFF??
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah still works, you might of read that Firewater for some people doesnt work on 4.4.3. For me Firewater worked and I'm S-Off for some people it doesnt and you have to use Sunshine in that case.
thinkhope said:
So the toolkit still works??
Click to expand...
Click to collapse
I highly recommend doing it manually and steering clear of toolkits. Using a toolkit robs you of an important learning opportunity, and leaves you with little understanding of the processes. Skills and knowledge that are important when things don't go quite right (which will inevitably happen).
redpoint73 said:
I highly recommend doing it manually and steering clear of toolkits. Using a toolkit robs you of an important learning opportunity, and leaves you with little understanding of the processes. Skills and knowledge that are important when things don't go quite right (which will inevitably happen).
Click to expand...
Click to collapse
I agree and that's the route I'm trying to take, however just need a bit more of a solid guide to lean on. I haven't messed around with adb or pushed anything via fastboot since my One X. Don't want to end up with a fancy paper weight.
Sent from my HTC One_M8 using XDA Free mobile app
thinkhope said:
I agree and that's the route I'm trying to take, however just need a bit more of a solid guide to lean on. I haven't messed around with adb or pushed anything via fastboot since my One X. Don't want to end up with a fancy paper weight.
Click to expand...
Click to collapse
If you did it on your One X, its really not any different on the M8. Actually, probably a good deal easier if you had the AT&T One X (EVITA), since that phone required temp root and SuperCID to unlock the bootloader, for the most part.
In short:
-Go to HTCDev.com to unlock the bootloader. The website walks you though step-by-step, so there is really nothing to that part.
- Use adb to flash your recovery of choice (TWRP or CWM)
- Flash SU/SuperSU or flash a custom ROM
-S-off, if you want
- That's it!
redpoint73 said:
If you did it on your One X, its really not any different on the M8. Actually, probably a good deal easier if you had the AT&T One X (EVITA), since that phone required temp root and SuperCID to unlock the bootloader, for the most part.
In short:
-Go to HTCDev.com to unlock the bootloader. The website walks you though step-by-step, so there is really nothing to that part.
- Use adb to flash your recovery of choice (TWRP or CWM)
- Flash SU/SuperSU or flash a custom ROM
-S-off, if you want
- That's it!
Click to expand...
Click to collapse
I definitely did have the evita. Had to alter the cid to make htc dev believe it was a different phone or something like that, if I remember correctly.
S-ON really is only if I want to mess with different radios, right? All I want is xposed and and maybe some cm 11 or gpe once Android L is out.
Well, sounds easy enough. I will be attempting later tonight after work. Thanks for all of your help. If it's OK, mind if I PM you if something goes wrong?
Sent from my HTC One_M8 using XDA Free mobile app
thinkhope said:
S-ON really is only if I want to mess with different radios, right? All I want is xposed and and maybe some cm 11 or gpe once Android L is out.
Click to expand...
Click to collapse
S-off is needed to flash radio, hboot, SIM unlock, and some other things. But not for root or to flash ROMs. Pretty much similar to how things were on the EVITA; with the exception that boot.img will flash automatically along with the ROM (not possible on most hboots on the EVITA, and had to be flashed manually with fastboot).
It sounds like you are already on the "official" 2.23 software (Android 4.4.3) by OTA? If so, you don't need to update firmware (radio, hboot, etc.) as the OTA already updated it. Otherwise, s-off is needed to flash the firmware manually; which is pretty much required for any 2.xx Sense based custom ROMs (otherwise there will be serious bugs like very long boot times, broken WiFi, Bluetooth). While s-off is not strictly needed to flash the ROM (it will flash correctly) things just won't run right if firmware is outdated. This is the only reason you would "need" to have s-off for flashing ROMs. AOSP and GPE ROMs won't suffer this issue.
But if you are already on the new OTA, this isn't an issue for flashing any ROM. You can verify by looking at the hboot version and baseband. If you are on hboot 3.18 and baseband 1.19; your firmware is up to date, and won't be an issue for running any ROMs.
thinkhope said:
mind if I PM you if something goes wrong?
Click to expand...
Click to collapse
I actually prefer you just posting to the forums. Either to an existing relevant thread, or start a new one if a relevant one does not already exist.
Couple reasons for this:
- Info given to you can help others reading the forums, and benefit the community as a whole instead of being hidden away in PM
- You can get help from more than just one user. I don't claim to even remotely know everything, and often its helpful to have more than one set of eyes on a problem (especially the tougher ones). And I might not even be online to help.
In particular for the 2nd point: my wife and I are going to be having a baby, with scheduled induction tomorrow (Sept. 5) unless it happens by itself sooner. So I won't be available to help you when that happens, anyway!
In any case, good luck!