Related
Im no pro at this stuff by any means, but I have modded the heck out of 5 personal phones and numerous other devices for friends and co workers.
I see a lot of talk of radio's and RUU, are these the same thing? The names are so confusing to me at the moment. Im used to 4 digit Radio names that tend to work on every rom. It seems as if some of the roms are coming with their own modified radios ( RUU's? ) Just wondering if anyone could clarify some basic information on this whole deal.
Secondly it seems as if these RUU/Radio 's are flashed via stock recovery. How does one boot their TB into stock recovery and what are the controls once in stock recovery ( stock recovery and bootloader are the same thing, correct? )
How do I boot into CWR from a dead phone? If I should happen to soft brick my phone or something in the future, how do I get into CWR without being able to boot?
And lastly, can someone give me a brief explanation of what S-on and S-off are? I assume anyone thats rooted is running s-off, correct?
So far I'm rooted running the battery sipper Kernel and I don't really know what direction to take, just trying to do my research. Might wait for CM7 support to start flashing, as this phone really isn't that bad..
Thanks in advance!
I'm still pretty new to all of this, but this is what I've learned so far.
RUU and the radio are different. RUU has everything, the apps the firmware and radio in it. Basically what you need when you wipe your phone and go back to completely stock. Where as radio just updates your radio or baseband.
It's kind of confusing the terms that are thrown around. Some people call it Hboot some call it bootloader. To get into it, turn off your phone, hold Vol down and then the power button. Let go and you should boot into bootloader.
Having S-Off just means your phone is unlock. You're able to access files and folders that are normally locked from you. Which lets you flash roms etc.. S-on, those files/folders are locked.
RUU is short for ROM Upgrade Utility - it's an historical name, based on a utility used to upgrade older HTC phones. For HTC Android phones, the HUU files contain images which get flashed to the phone.
Bootloader is a generic term on Android phones - the HTC one is call Hboot.
Recovery is a separate app/partition, it can be started from Hboot. If you root, you'll probably install Clockworkmod Recovery, which lets you backup/restore the partitions. It should also prevent an OTA update from being installed.
S-On/S-Off refer to a security feature which prevents unsigned images from being flashed. Rooting should set S-Off, which lets you make changes.
Every time I boot into hboot it wants me to confirm an update after it performs an operation it did during the root process. Should I remove that file from my sd?
Sent from my ADR6400L using XDA App
If you have an PG05IMG.zip on your sdcard, remove it. You don't want to leave it laying around after it's been flashed.
mike.s said:
RUU is short for ROM Upgrade Utility - it's an historical name, based on a utility used to upgrade older HTC phones. For HTC Android phones, the HUU files contain images which get flashed to the phone.
Bootloader is a generic term on Android phones - the HTC one is call Hboot.
Recovery is a separate app/partition, it can be started from Hboot. If you root, you'll probably install Clockworkmod Recovery, which lets you backup/restore the partitions. It should also prevent an OTA update from being installed.
S-On/S-Off refer to a security feature which prevents unsigned images from being flashed. Rooting should set S-Off, which lets you make changes.
Click to expand...
Click to collapse
I had a pretty good idea what these were, but great explanations. Thank You
mike.s said:
RUU is short for ROM Upgrade Utility - it's an historical name, based on a utility used to upgrade older HTC phones. For HTC Android phones, the HUU files contain images which get flashed to the phone.
Bootloader is a generic term on Android phones - the HTC one is call Hboot.
Recovery is a separate app/partition, it can be started from Hboot. If you root, you'll probably install Clockworkmod Recovery, which lets you backup/restore the partitions. It should also prevent an OTA update from being installed.
S-On/S-Off refer to a security feature which prevents unsigned images from being flashed. Rooting should set S-Off, which lets you make changes.
Click to expand...
Click to collapse
Nice, Simple explanations. Very clear and helpful. Thanks.
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
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!
This AM I was:
S-ON
HBOOT: 1.19
Running a version of Fresh
11PM I am:
S-OFF w/ DirtyRacun
HBOOT 1.15.2222
Radio 1.05.11.0606
I have access to Bootloader & I have TWRP 2.4.1.0
I have reformatted internal SDcrd, and I've reformatted internal memory
The phone is blank besides Bootloader and TWRP
Any ROM's I attempt to flash "FAILS"
My attempts at flashing a kernal has been dubious.. I don't know what I'm doing on the kernal front.
Is there a plain Jane Rom out there that will load every time? I'm just not sure where to go from here.
2/20/13 Comment - I forgot to mention, after achieving S-Off with Racun, the phone was basically stock, so I re-rooted with 1.22_RUU_PLUS_ROOT which seemed to flash with no problems and install TWRP. It was at this point I tried to flash (over confidently, I did not make a backup) fresh-evo-lte-5.3.1. The Flash never made it through the process, and restarted. There's where it sits. Now all Rom's very quickly start to flash then, "Fail."
Ffej4ord said:
This AM I was:
S-ON
HBOOT: 1.19
Running a version of Fresh
11PM I am:
S-OFF w/ DirtyRacun
HBOOT 1.15.2222
Radio 1.05.11.0606
I have access to Bootloader & I have TWRP 2.4.1.0
I have reformatted internal SDcrd, and I've reformatted internal memory
The phone is blank besides Bootloader and TWRP
Any ROM's I attempt to flash "FAILS"
My attempts at flashing a kernal has been dubious.. I don't know what I'm doing on the kernal front.
Is there a plain Jane Rom out there that will load every time? I'm just not sure where to go from here.
2/20/13 Comment - I forgot to mention, after achieving S-Off with Racun, the phone was basically stock, so I re-rooted with 1.22_RUU_PLUS_ROOT which seemed to flash with no problems and install TWRP. It was at this point I tried to flash (over confidently, I did not make a backup) fresh-evo-lte-5.3.1. The Flash never made it through the process, and restarted. There's where it sits. Now all Rom's very quickly start to flash then, "Fail."
Click to expand...
Click to collapse
try downgrading TWRP. Some ROMs aren't compatible with the latest release. The Dev has to bake something in the ROM. Version 2.3.1.0 seems to be the "sweet spot". Get it here. Since you're s-off just use the "Download - Bootloader Method:" make sure you rename it to PJ75IMG.zip and place it on the root of your EXTERNAL sdcard.
Similar Issues
I have a similar issue as the OP. I've looked around, and to avoid created a new thread, I'm going to pseudo-bump this into a new topic.
S-ON
HBOOT: 2.09
Running TWRP 2.6
Radio 1.13.11.0830
When stock, I was on 3.17 baseband. I saw that DirtyRacun was had the capability to unlock it, and they (If I read correctly) completely abandoned windows. MeanBean is on 3.16. I'm not adverse to Linux, but I have no idea how to use it past the GUI, and I don't want to install another OS to do something that should be accomplish able on the regular PC.
I have tried DirtyRacun, FacePalm, and Moonshine to get S-Off, no avail on any front unless I'm doing it wrong, which is completely possible.
I have access to Bootloader & I have TWRP 2.6.3.0
I have reformatted internal SDcrd, and I've reformatted internal memory
I am running Mean Bean due to its interesting method of installation, separating the Rom from kernel.
Any other ROM's I attempt to flash "FAILS"
I have flashed a kernel but no ROM I try will install regardless of my attempts. I have used Flash Image GUI from the Play store, but it doesn't seem to help any.
The only reason I am still trying to get a different ROM, MeanBean has no audio. Granted, it plays Pandora, but it has no ringtones, cannot install Amazon MP3, Cannot use Zedge (Crashes every time, not even FC), and cannot see my SD card to use manually loaded music. So I have no music or notification capabilities. No alarm, no text, nothing but the stock ringtone and I think a default e-mail that works about half the time. It also has no loaded sounds, so I cant even set any of the stock ones, which I could suffer until I get the Nexus 5. My Phone, like most people, is my alarm and my life line, so... I really wanna get it back in shape. I appreciate any and all help! I already got help getting out of Limbo once, now I just need one more little piece of info to get comfy again.
Part of your issue is that you're S-on, and you really need to be S-off (fairly simple using the newest Rumrunner method, which is Windows friendly).
As far as MeanBean, I'm not quite sure why you're having those issues with audio, as I and countless others have used that same ROM and have not encountered those issues. What other ROM's have you tried to flash?
Take a look at the top link in my sig. It has some useful info which hopefully you'll find helpful.
If you continue to have issues after exhausting all efforts, shoot me a PM.
Sent from my HTC EVO 4G LTE
Ok I unlocked my loader, then i think what happend was clockwerk installed its self to the boot partition so i was stuck in a loop. I used One_M8_All-In-One_Kit_v to flash a new recovery lower version at that and now i do have a bootable recovery. Problem is now i didn't backup like a dumb arse my working OS and flashed a bad one or maybe the radio or some crap needed to be done first since it was going from 4.4.2 to 5+. In short all i have is recovery and sideload and every rom i download fails to sideload on the phone side and says sucessful on the pc cmd window. Need help with this please
Darthdiddy said:
Ok I unlocked my loader, then i think what happend was clockwerk installed its self to the boot partition so i was stuck in a loop. I used One_M8_All-In-One_Kit_v to flash a new recovery lower version at that and now i do have a bootable recovery. Problem is now i didn't backup like a dumb arse my working OS and flashed a bad one or maybe the radio or some crap needed to be done first since it was going from 4.4.2 to 5+. In short all i have is recovery and sideload and every rom i download fails to sideload on the phone side and says sucessful on the pc cmd window. Need help with this please
Click to expand...
Click to collapse
Wipe data, cache, dalvik, put the appropriate ROM for your carrier/build on SD card or root of internal storage and flash. All else fails run an RUU, bring you back to 100% stock then you can properly reinstall the custom recovery of your choice.
CavyS said:
Wipe data, cache, dalvik, put the appropriate ROM for your carrier/build on SD card or root of internal storage and flash. All else fails run an RUU, bring you back to 100% stock then you can properly reinstall the custom recovery of your choice.
Click to expand...
Click to collapse
I do the proper wipe before flashing my new rom, i'm under the AT&T HTC One M8 section i believe my phone was only @ 4.4.2 before this and here is the bootloader info is :
***Tampered***
***Unlocked***
M8_UL_CA_ PVT SHIP S-On
HBOOT-3.16.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 18 2014,16:06:33.22985
Tried cm-12-20150131-NIGHTLY-m8 it fails to flash and its on the sd and internal. SkyDragon M8 Sense Rom installs but doesn't boot (tried 2 versions of this rom 700mb and a 1.6gb), believe i tried a couple other roms in my phones section there's only like 9 of them there. I have the stock RUU but fails to detect the phone and fails i think it's meant to sense a turned on functional phone i don't see any kind of recovery method with the stock ruu. All i want is a rom to work with Straight talk the stock os even being unlocked and rooted with su still shoved the default APN down my throat(I even paid 2.99$ for the SQLlite and deleted all other APNs still won't let me check off a APN profile i created as default) making my signal on ST flakey and couldn't get mms to work just picture txting wasn't working. So i went full on like my old HTC One X but dived head first too fast didn't backup my old OS and didn't know firewater was gone till i was at that step of the procedure and it was too late Oh and using TWRP 2.7.1.0 it's the highest i can use before it won't boot.
Darthdiddy said:
I do the proper wipe before flashing my new rom, i'm under the AT&T HTC One M8 section i believe my phone was only @ 4.4.2 before this and here is the bootloader info is :
***Tampered***
***Unlocked***
M8_UL_CA_ PVT SHIP S-On
HBOOT-3.16.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 18 2014,16:06:33.22985
Tried cm-12-20150131-NIGHTLY-m8 it fails to flash and its on the sd and internal. SkyDragon M8 Sense Rom installs but doesn't boot (tried 2 versions of this rom 700mb and a 1.6gb), believe i tried a couple other roms in my phones section there's only like 9 of them there. I have the stock RUU but fails to detect the phone and fails i think it's meant to sense a turned on functional phone i don't see any kind of recovery method with the stock ruu. All i want is a rom to work with Straight talk the stock os even being unlocked and rooted with su still shoved the default APN down my throat(I even paid 2.99$ for the SQLlite and deleted all other APNs still won't let me check off a APN profile i created as default) making my signal on ST flakey and couldn't get mms to work just picture txting wasn't working. So i went full on like my old HTC One X but dived head first too fast didn't backup my old OS and didn't know firewater was gone till i was at that step of the procedure and it was too late Oh and using TWRP 2.7.1.0 it's the highest i can use before it won't boot.
Click to expand...
Click to collapse
Boot into fastboot, check device manager (if youre on windows) for any unknown drivers and install them if you can. Then run the RUU I posted here http://forum.xda-developers.com/att-htc-one-m8/help/100-stock-4-4-4-ruu-t3017594 which would update you to 4.4.4.
CavyS said:
Boot into fastboot, check device manager (if youre on windows) for any unknown drivers and install them if you can. Then run the RUU I posted here http://forum.xda-developers.com/att-htc-one-m8/help/100-stock-4-4-4-ruu-t3017594 which would update you to 4.4.4.
Click to expand...
Click to collapse
Ok TY i'll try that soon as it downloads, i did finally get RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2
To see the phone and no progress bar shows up on the phone and the program errors out, i even did a full system wipe before i tried it again still to no avail.
CavyS said:
Boot into fastboot, check device manager (if youre on windows) for any unknown drivers and install them if you can. Then run the RUU I posted here http://forum.xda-developers.com/att-htc-one-m8/help/100-stock-4-4-4-ruu-t3017594 which would update you to 4.4.4.
Click to expand...
Click to collapse
Ok tried that stock ruu and it failed i did finally get the phone running on a badseed rom based on 4.4.2 all seems to be working now except i can't send pictures in texts but regular text, calls, and internet work seems to be a common problem with straight talk. So new problem probably a thread somewhere on here about it i'll take a look, thank you for the help
Darthdiddy said:
Ok tried that stock ruu and it failed i did finally get the phone running on a badseed rom based on 4.4.2 all seems to be working now except i can't send pictures in texts but regular text, calls, and internet work seems to be a common problem with straight talk. So new problem probably a thread somewhere on here about it i'll take a look, thank you for the help
Click to expand...
Click to collapse
You'll have to setup your APN and mms message size settings for straight talk, that should fix the text messaging problems.
CavyS said:
You'll have to setup your APN and mms message size settings for straight talk, that should fix the text messaging problems.
Click to expand...
Click to collapse
No matter what message app i try i can't send pictures or large txts my mms is borked and to make matters worse when i installed this rom i must of removed the stock HTC messaging app so i can't find any settings to set the mms size limits. I'd like to figure out how to put the stock messaging app back on the phone without redoing the whole OS
Using Handcent and hangouts and i see no size limit options within the apps or anywhere in the phone settings. Looked up my phone specifically and where the option/s is supposed to be the said section of options is not even there.
If you've got a stock rom downloaded to your computer or sd card you can unzip it and look in system app folder and find the htc messaging apks. Then just install them as system apps and fix permissions.
Sent from my HTC One_M8 using XDA Free mobile app
Before i try and fix my obvious other problems does anyone know how to fix a bad flash of TWRP? I'm used to just adb command line flashing it and never had a issue before on my HTC One X, but seems it a was bad idea and it landed on boot partition and is causing glitches. is there a stock boot i can flash or what do i need?
Darthdiddy said:
but seems it a was bad idea and it landed on boot partition and is causing glitches.?
Click to expand...
Click to collapse
Why do you think that partition, in particular? If you are talking about boot.img, that gets re-flashed any time your flash a ROM.
Try fastboot erase cache, and flash recovery by fastboot. If Clockwork doesn't work, try TWRP.
If you indeed have some corrupted partition(s), your best bet is to RUU. You are non-specific about what error codes, so its hard to help you troubleshoot why the RUU failed. Try a more updated RUU, such as 2.23.
redpoint73 said:
Why do you think that partition, in particular? If you are talking about boot.img, that gets re-flashed any time your flash a ROM.
Try fastboot erase cache, and flash recovery by fastboot. If Clockwork doesn't work, try TWRP.
If you indeed have some corrupted partition(s), your best bet is to RUU. You are non-specific about what error codes, so its hard to help you troubleshoot why the RUU failed. Try a more updated RUU, such as 2.23.
Click to expand...
Click to collapse
Error 155 Unknown Error it says, do i need to relock the bootloader? I could never find a way to S-Off the device so idk if its that or corrupted partition like you said but all my services on my phone crash constantly. But that's better then aokp_task650_m8_kitkat_5.13.2014 that one won't even make it through setup the services crash so often the badseed rom is the only other rom i found that is actually usable. Oh my RUU is 2.0.16 how can i find the newest one for my HTC One M8?
Darthdiddy said:
Error 155 Unknown Error it says, do i need to relock the bootloader?
Oh my RUU is 2.0.16 how can i find the newest one for my HTC One M8?
Click to expand...
Click to collapse
You always need to relock the bootloader to run RUU with s-on. No exceptions.
Hopefully this will clear up your RUU problem, although the RUU number you just supplied above doesn't make any sense (doesn't correspond to any RUU for this device) Where did you find it, and its not what you referenced in Post #5 above.
CavyS already supplied a link for the "latest" AT&T RUU in Post #4 above. Although be aware, that if you are successful in running the latest RUU, it will render sunshine unable to achieve s-off. I suggest RUU to 1.58 or 2.23 (if you want s-off), as those should still be supported by sunshine.
Darthdiddy said:
I could never find a way to S-Off the device
Click to expand...
Click to collapse
Did you try sunshine? Its the only way to s-off at this time.
redpoint73 said:
You always need to relock the bootloader to run RUU with s-on. No exceptions.
Hopefully this will clear up your RUU problem, although the RUU number you just supplied above doesn't make any sense (doesn't correspond to any RUU for this device) Where did you find it, and its not what you referenced in Post #5 above.
CavyS already supplied a link for the "latest" AT&T RUU in Post #4 above. Although be aware, that if you are successful in running the latest RUU, it will render sunshine unable to achieve s-off. I suggest RUU to 1.58 or 2.23 (if you want s-off), as those should still be supported by sunshine.
Did you try sunshine? Its the only way to s-off at this time.
Click to expand...
Click to collapse
Relocked and flashed the ruu utility version said 2.0.16.2014 and is KK 4.4, idk about sunshine as to reading about people with my phone and it not working so for a 25$ leap of faith not sure what to do about that. My phone is running perfect now in a locked down carrier branded and bloatware way lol. Thanks guys, anyway i can tell if sunshine will work on my phone?
Darthdiddy said:
Relocked and flashed the ruu utility version said 2.0.16.2014 and is KK 4.4
Click to expand...
Click to collapse
I think that is the version of the actual installer software (.exe) not the ROM version it will install on your phone. Kitkat for AT&T would be either 1.58 or 2.23. That number will be in the actual file name of the RUU, so just look there (actually a much longer string of numbers starting with 1.58 or 2.23, but I've abbreviated them for convenience).
Darthdiddy said:
idk about sunshine as to reading about people with my phone and it not working so for a 25$ leap of faith not sure what to do about that. My phone is running perfect now in a locked down carrier branded and bloatware way lol. Thanks guys, anyway i can tell if sunshine will work on my phone?
Click to expand...
Click to collapse
You install the sunshine APK, run it, and sunshine will tell you whether it can s-off the phone or not. You won't be charged unless it can successfully s-off the phone. I haven't heard of any folks here that got charged, and sunshine couldn't s-off the device.
redpoint73 said:
I think that is the version of the actual installer software (.exe) not the ROM version it will install on your phone. Kitkat for AT&T would be either 1.58 or 2.23. That number will be in the actual file name of the RUU, so just look there (actually a much longer string of numbers starting with 1.58 or 2.23, but I've abbreviated them for convenience).
You install the sunshine APK, run it, and sunshine will tell you whether it can s-off the phone or not. You won't be charged unless it can successfully s-off the phone. I haven't heard of any folks here that got charged, and sunshine couldn't s-off the device.
Click to expand...
Click to collapse
Wow thanks for the info! Before i try this can after S-OFF/rooting/SU can i install the unlocked/developer ruu from HTC and get HTC OTA and get away from this bloated carrier branded crap? So much in the forums and i can't find a answer to this question anywhere.