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!
Related
So I have Scott's CleanROM GBE 1.7.5 on my phone. I was wandering through my phone's settings, and accidentally hit something in the update area. I do not know what I was thinking, but I know I expected it to ask me if I was sure I wanted to update. So far it has only done the first part where it prepares the phone for the update. I do not know when the other part is coming but I assume it is automatic. I was planning on updating to a rooted ICS once I felt comfortable with it (just seemed a little harder than my original flash of rooted GB). So if it would be easier to just update to ICS some way now, I would be very willing to do that. I am s-on, I believe I installed Amon Ra, but I am not sure how to check and not sure if I have an actual recovery rom or not.
I checked around and found similar problems, but nothing really like mine since my update has not gone all the way thru yet. If anyone could help, it would be greatly appreciated. THank you.
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ok just to make sure I know and don't mess anything else up. I relock (should be easy to.find a guide) . Then run the update on my phone? Then unlock thru HTC again, and flash the actual amon or CWM to my phone? And from there I will be able to flash any ICS Rom with more ease?
And thank you for the quick reply.
Edit: I searched the internet more for less-similar situations. I think all I have to do is re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Also,nothing I have to do as far as unrooting?
malignancyy said:
Also,nothing I have to do as far as unrooting?
Click to expand...
Click to collapse
Nope just relock the bootloader
AshtonTS said:
Nope just relock the bootloader
Click to expand...
Click to collapse
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
malignancyy said:
Okay, thanks a lot. And I edited this into a prior post, but I just wanted to make sure:
I have to re-lock. Download the newest RUU from Android police and put it in the root of the SD card as PH98IMG.zip (I'm assuming it should be the internal memory, but please correct me if I am wrong.) Hold volume down & power to boot into bootloader, then the phone takes it from there?
Click to expand...
Click to collapse
Then you just have to press continue when it tells you to.
PS: Another way to get to the bootloader is to use adb (make sure USB debugging is enabled on your phone)
Command:
adb reboot bootloader
I find it easier than holding down buttons for a long time, but that's just my personal preference.
(Also, most custom ROMs can reboot to bootloader from within the ROM. I forget if CleanROM GBE includes the advanced power menu.)
pwned3 said:
Easiest way is to relock your bootloader, run the newest ruu, unlock and flash recovery again. That way you will be set up to run any ics Rom without having to worry about flashing a patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Good advise, and if he RUUs to ICS, then he should not even get asked to install the update because it will already be installed on his phone.
Also RUU twice. Just reboot into bootloader right away and install the RUU a second time. Then boot up normally and remove the zip file from the sdcard.
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
malignancyy said:
Thanks, you all helped a lot. I was able to get the stock rom, rooted, and running smoothly. But, once I tried to install custom roms I had problems. I decided to S-off to make it easier from here on out. After a few tries, it said I had successfully done the S-off. I tried to install Juopunutbear custom hboot, directly afterwards and it said it installed but I was stuck on the Juopunutbear screen. After this, I have not been able to get past hboot.I do not think the custom hboot actually installed. It is saying from the top:
***TAMPERED***
***LOCKED***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.27.0000
RADIO-2.22.10.0801r/2.22.10.0803r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Aug 6 2012, 19:24:37
My external sd card needed formatting, so I just did that. And my plan is to RUU again (i guess twice), flash recovery (when clicked on currently, nothing happens), I guess root although I am not sure about this part, then try to install a custom rom.
Didn't want to make another thread just to check on this, but does this sound about right?
And as far as installing rom since I am now s-off, just go to recovery and flash it, nothing else at all to worry about?
Click to expand...
Click to collapse
The jbear hboot might have failed because you are on the newest global update with 2.27 hboot, and I believe the controlbear tool still has the 2.25 hboot. (someone correct me if I'm wrong)
I think there is an unguarded 2.27 hboot somewhere, so you should flash that manually.
Sent from my NeoMax Rezound
Right now, like I said the hboot says at the top 2.27.0000
When I reboot from there, or boot it regularly it goes to a JuopunutBear, black and green writing screen.
I have tried to install this forum.xda-developers.com/showthread.php?t=1843030 ([HBOOT] HBoot 2.27 (from 4.03.605 OTA) Unlocked) from both, but cannot figure out how to do so.
edit: within JuopunutBear, wiping says "can't open" and applying update gives "failed to open loopdevice" and "failed to mount /sdcard" when I try to update.
Within the regular hboot, I get "no image" as it searches for files.
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
A little more info on this. Windows tries installing QHUSB_DLOAD driver for it when plugged in, but unsuccessfully. The charging indicator does not come on either. Have tried to turn it on plugged in with battery out, and battery in both ways.
malignancyy said:
Well, I put the same file on a new sd card, and it worked on the first try, kinda.
Now it appears my phone is bricked. It will not boot at all. She barely lasted a few hours s-off before I messed it up. Any tips anyone out there can give to this sad fellow, or am I off to get a replacement?
Click to expand...
Click to collapse
Depending on what caused the brick, it may be recoverable.
Check out the unbricking thread in the dev section.
Sent from my NeoMax Rezound
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
malignancyy said:
Wanted to post this in the NeoMax thread, but I am currently not allowed to. I gave up on my last Rezound, and am getting a replacement here soon. I did a bunch of reading before and after I got my Rezound, and a bunch more the past few days as I wanted to get an ICS rom. Unfortunately, the one time I deferred from guides I followed (installing the JBear hboot), I killed my Rezound. I now want to stay S-on, at least until I gain some more familiarity and skill with this whole process.
What I plan on doing is once I get the Rezound, installing the OTA update, possibly having to wait for it to do so. I assume this would be the newest, .2, global update. I plan to unlock, flash recovery, then root. The rom I really want however is NeoMax. There are limited instructions on how I go about this. But from what I understand I change the filename to PH98IMG and flash it from hboot? The file name is originally, GlobalRuuPH98IMG.zip, but the thread title claims ICS De-Sensed 3.14.605.12, which I believe is two versions prior. So here I am lost. If it is in fact older, I have to flash the rom through recovery, then flash the kernel, correct? If so, do I just use the 3.14.605 that was in the NeoMax thread?
Sorry to bother you all with what i'm sure others have done many times. Like I said, I have read a lot on this, its just that I either did not understand in the least what the guides were saying, or it seemed like this situation was much different. And on a side note, if there is any other rom out there that someone would recommend that would make this easier (such as being on the latest kernel), I wouldn't be opposed to trying it. I just want one that is desensed, as it is one of my main reasons for wanting a custom rom.
Click to expand...
Click to collapse
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
wlmeng11 said:
Don't worry, you're not bothering anyone.
The people who claim to have bricked their phones when they have a boot loop and say nothing about their rom and firmware are bothering people.
Keep doing what you are currently doing and people will always be willing to help you.
Ok, so back to helping...
Of you're starting on GB, make sure you update to 3.14.605.12 before updating to the most recent one.
If you update via OTA then you don't need to worry.
Keep in mind that NeoMax is based off of the 3.14.605.12 build, so you'll have to mix n match the right way to get it to work on the latest firmware.
I believe it was you have to use the new kernel if you use the new radios and hboot.
So after installing NeoMax, flash the PH98IMG that contains the newer kernel, not the 3.14.605.12 version.
Or use fastboot to flash the kernel. (my preferred method while s-on)
Sent from my NeoMax Rezound
PS: A good way to get the required 10 posts to post in the dev section is post random stuff in the off topic thread.
Click to expand...
Click to collapse
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
malignancyy said:
As far as which kernel, this is what was said in the NeoMAX Q&A:
Q: "I flashed your rom and my phone gets really hot after a while. In fact, Ive noticed it on all the newer roms lately. What could be causing it and how can I attempt to fix it?"
A: "Make sure you have updated your radio to the latest available and then flash the 2nd to latest kernel. This combination has been known to have the best rom performance for all my roms and decreased heat"
SO this means I should use the 4.03.605.1? And the newest radio will automatically still be on there from the OTA update, or will I have to flash those as well? I have no experience in flashing radios so this is new ground to me.
Click to expand...
Click to collapse
That QA is outdated.
It was referring to using the 3.14.605.07 kernel as opposed to the then-most-recent 3.14.605.10
Back then those two builds were similar enough that they could mix n match without issues.
Between 3.14.605.12 and 4.03.605.1 is a lot of changes. (whole number change to represent it) Specifically, new hboot and radios. Therefore, it is incompatible with the older kernels.
When you're S-ON you can't touch the radios except through an official RUU.
Even with s-off I doubt you can flash radios from recovery (not sure on this one), and NeoMax doesn't have any radio files anyway. (nor does any rom I know for this phone)
If you haven't yet updated to 4.03.605.1 then I recommend that you stay on 3.14.605.12 until Neo updates the ROM.
If you already updated, it is still possible to run NeoMax. You just have to manually flash the new 4.03.605.1 kernel after installing the ROM.
Sent from my NeoMax Rezound
I've been (at least trying to) patiently wait for Deck to post full install instructions for CM10 but the CM10 op is still bare as bones. Has anyone else posted an install guide or instructions yet?
I'm currently rooted with RegawMod and running MeanRom 2.1 and it's really terribly laggy and frustrating, I can't wait any longer for CM10. Do I need S-off to install CM10 or do I just wipe, flash, and go?
Thanks for any help or links!
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Its been my daily for 3 weeks.
Sent from my EVO using Tapatalk 2
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Sent from my EVO using xda app-developers app
corcgaigh said:
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Click to expand...
Click to collapse
Dont use flash image gui unless you know how to do it manually through fastboot. You are just asking for issues
Instructions:
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Rxpert said:
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Click to expand...
Click to collapse
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Yes hboot 1.12 allows for access to the boot partition
Also luuuuucckkyyyyyy...
EdhyMonker said:
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Click to expand...
Click to collapse
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Bit off topic, anyone check to see if you can push a new splash, right now I'm too lazy to start my PC just to fastboot one measly splash
Rxpert said:
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Click to expand...
Click to collapse
The S-OFF guide was way over my head so I just let it be. If there's not a real good reason for doing it, and I can still run CM10, then I'd rather not.
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
om4 said:
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
Click to expand...
Click to collapse
No, S-ON people with 1.12 H-boot can flash radios and firmware from recovery. They can do whatever they please in recovery just like S-OFF. S-OFF users can flash things from bootloader and even change the appearance of their h-boot to read S-ON and **locked** even though they are S-OFF
To the OP, this is the best rooting guide I've seen. It really explains everything step by step. http://androidforums.com/evo-4g-lte...panda-s-htc-dev-ltevo-root-dummies-guide.html Its recommended to have Linux at least bootable, because in the small chance the phone gets bricked... the unbricker program requires linux.
I ran it in windows before the unbricker was available, no issues here
You basically just hook the phone up to it and run the program like you do for most other root programs. All 1-click
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
om4 said:
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
Click to expand...
Click to collapse
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
You don't have to flash any firmware updates. There are a few users with issues although they may be related to the ROM update and not necessarily the firmware included. I haven't really checked since I'm s on. If you want to update the radios there's an update zip here somewhere, be sure to read through everything carefully. Radios are more risky then every day flashing
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
EdhyMonker said:
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
Click to expand...
Click to collapse
ive only ever seen this issue with cyanogenmod and the old htc vogues, still great phones for what they were
EdhyMonker said:
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
Click to expand...
Click to collapse
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Rxpert said:
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Click to expand...
Click to collapse
Thanks, but I tried this and it says "no image or wrong image" when trying to flash the PJ75IMG.zip file.
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
joebarkho said:
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
Click to expand...
Click to collapse
I thought that might've been the issue so I tried it both ways, didn't work either way. I'll take another shot at it tomorrow.
Hey folks..so I want to start flashing kernels and yes I know I probably should have gone s-off way sooner but I want to do it now. I've been rooting and romming my phones for a while but this whole s-off procedure continued to scare the crap out of me. But..I don't want to limit my choices when it comes to roms and kernels so I guess I'll do it anyway.
However, I am currently running RUU 4.03.605.2 with Vigor360 1.1 s modified kernel.
Can I still go s-off even though I am now running the global leak (or is it now impossible) and if so, can someone point me in the right direction?
Thank you kind gents n ladies!
I've heard of several people being successful on 4.03.605.2 with the 3.14.605.5 ControlBear version.
Only other advice I can offer is don't give up, try different wires if you're having trouble, and pay attention to the troubleshooting page if you decide you want back out and try again later. I've S-OFF'ed three Rezounds. The first took 3 days, the second 2 minutes, and the third 30 minutes.
dplane said:
Hey folks..so I want to start flashing kernels and yes I know I probably should have gone s-off way sooner but I want to do it now. I've been rooting and romming my phones for a while but this whole s-off procedure continued to scare the crap out of me. But..I don't want to limit my choices when it comes to roms and kernels so I guess I'll do it anyway.
However, I am currently running RUU 4.03.605.2 with Vigor360 1.1 s modified kernel.
Can I still go s-off even though I am now running the global leak (or is it now impossible) and if so, can someone point me in the right direction?
Thank you kind gents n ladies!
Click to expand...
Click to collapse
i did s-off with viper's rom and the .5. i was on global too, don't let it scare you or you will not get it. i couldn't get the timing for the life of me. first two hours was a hassle, then i had to get my other battery(thought i bricked my phone) then i relized that they had a metrnome with the correct timing and it worked the first time. but use a different memory card. all of these things can be found under the s-off instructions.:good:
its really easy man you can do it. i reccemend using speaker wire as its more pliable than a paperclip.. if you need help i can walk you thru it on gtalk. just pm me for me gtalk. otherwise. goodluck and yes the 3.14.605.5 ControlBear version is the correct one just lock your bootloader, run the full ruu agan( 4.03.605.2), flash amonRA, then flash this in recovery (https://docs.google.com/file/d/0B0ZJtM40GdJ0MEpGeG1ZWi0yNDA/edit) to gain root on stock global, download root checker from the app store to be sure you got root before you begin. then boot phone and check usb debugging, connect your phone to the comp(within the stock rom), start control bear.. make sure to back up EVERYTHING as it could all get wiped. (internal sd, external sd, and your nandroid if you so choose) i reccemend using a spare sd card if you have one.. ive only done my phone but it took me all of 2 trys.. i got weird errors a couple times (other than "error: still sober" got that once) if you do just run control bear again
Thanks for the responses and moral support folks!
Collin, I may have to hit you up for that assistance soon, I'd rather be safe then sorry so I might feel better if I have someone to "hold my hand"
May not get around to it til Sat afternoon or Sunday though.
famouscollin said:
its really easy man you can do it. i reccemend using speaker wire as its more pliable than a paperclip.. if you need help i can walk you thru it on gtalk. just pm me for me gtalk. otherwise. goodluck and yes the 3.14.605.5 ControlBear version is the correct one just lock your bootloader, run the full ruu agan( 4.03.605.2), flash amonRA, then flash this in recovery (https://docs.google.com/file/d/0B0ZJtM40GdJ0MEpGeG1ZWi0yNDA/edit) to gain root on stock global, download root checker from the app store to be sure you got root before you begin. then boot phone and check usb debugging, connect your phone to the comp(within the stock rom), start control bear.. make sure to back up EVERYTHING as it could all get wiped. (internal sd, external sd, and your nandroid if you so choose) i reccemend using a spare sd card if you have one.. ive only done my phone but it took me all of 2 trys.. i got weird errors a couple times (other than "error: still sober" got that once) if you do just run control bear again
Click to expand...
Click to collapse
I'm working with the same situation as the OP. You posted a link to a second recovery to flash after Amon Ra, I've tried that link and it forces me to request access. Which recovery is it and is there another link or are you able to give me access to that one?
Hey guys.
I am a complete newb with most this stuff.
I am not sure how I look at RUU I have. I will say that my phone was pretty much stock through the official ICS release.
Currently I have CM9 flashed as my rom.
Is there anyway I can S-OFF my phone?
Sax1031 said:
Hey guys.
I am a complete newb with most this stuff.
I am not sure how I look at RUU I have. I will say that my phone was pretty much stock through the official ICS release.
Currently I have CM9 flashed as my rom.
Is there anyway I can S-OFF my phone?
Click to expand...
Click to collapse
If you haven't already, I would say start by checking out unlimited.io They have all the basic details about how to achieve S-OFF. Without knowing more specifics about your setup it would be hard someone to give a more specific answer.
neowisdom1031 said:
If you haven't already, I would say start by checking out unlimited.io They have all the basic details about how to achieve S-OFF. Without knowing more specifics about your setup it would be hard someone to give a more specific answer.
Click to expand...
Click to collapse
Yea I have went there.
I have the program downloaded. I am on Gray's CM9 rom.
Followed all the instructions. When the program runs it goes like this:
Starting up....
Connecting to device....
Searching device.....
Found device......
Backing up.....
Permission denied.....
Transferring backups....
Secondary backup FAILED!!
Press ENTER to exit.
like I said my phone was stock till the official ICS update released. After that I unlocked the boot loader and just recently flashed my first rom, through Amon Ra.
If I could kindly ask you what info you need, and possibly how to access the info, to help me out. Do I need to flash a stock rom back?
---------- Post added at 08:27 PM ---------- Previous post was at 07:29 PM ----------
I hope to god my hboot was stock. As I am running a previous RUU.
Hopefully once I do this, I will be able to S-OFF.
Sax1031 said:
Yea I have went there.
I have the program downloaded. I am on Gray's CM9 rom.
Followed all the instructions. When the program runs it goes like this:
Starting up....
Connecting to device....
Searching device.....
Found device......
Backing up.....
Permission denied.....
Transferring backups....
Secondary backup FAILED!!
Press ENTER to exit.
like I said my phone was stock till the official ICS update released. After that I unlocked the boot loader and just recently flashed my first rom, through Amon Ra.
If I could kindly ask you what info you need, and possibly how to access the info, to help me out. Do I need to flash a stock rom back?
---------- Post added at 08:27 PM ---------- Previous post was at 07:29 PM ----------
I hope to god my hboot was stock. As I am running a previous RUU.
Hopefully once I do this, I will be able to S-OFF.
Click to expand...
Click to collapse
If you're able to flash back to stock that would be the best place to start for S-OFF
neowisdom1031 said:
If you're able to flash back to stock that would be the best place to start for S-OFF
Click to expand...
Click to collapse
I flashed back to the first ICS RUU.
I think I know why it said permission denied. Because I didn't have actual root access.
At the point of trying the wire trick.
Edit: Achieved S-OFF. Thanks so much guys. Going from 3 days ago of flashing my first rom. To having to relock the device, run the first ICS Ruu, then doing the wire trick. Hell of a learning curve on these things. Thanks everyone for all the help.
Just a quick update. I was able to achieve S-Off while using this specific RUU. It took a few time flashing the RUU and a rooted rom to finally get it but it is possible with this RUU.
neowisdom1031 said:
Just a quick update. I was able to achieve S-Off while using this specific RUU. It took a few time flashing the RUU and a rooted rom to finally get it but it is possible with this RUU.
Click to expand...
Click to collapse
Fwiw I also was able to go s-off using this ruu and flashing supersu from a temporary amon ra. Not as tough as it thought.
Sent from my ADR6425LVW using xda app-developers app
.
Did you put the Juopunutbear executable and files into the same folder
that Android fastboot, adb, and other files are located?
michaelbsheldon said:
Did you put the Juopunutbear executable and files into the same folder
that Android fastboot, adb, and other files are located?
Click to expand...
Click to collapse
It shouldn't matter. ControlBear has its own versions of everything it needs.
Sent from my HTC Rezound using Tapatalk 2
So this is what i've done and its failing with the error: "Secondary backup FAILED!!"
-I reset everything by using the RUU 4.03.605.2.
-I then set the debugging mode, unlocked the bootloader
-Put AmonRa3.15 as my recovery
-Flashed the CWM SuperSU.
-Confirmed root access by using TitaniumBackup.
-Started the ControlBearRelease_vigor_ICS_3.14.605.5 for the ICS leak process.
-Then I get the fun error Secondary backup FAILED!!.
I'm using the latest version of JuopunutBear 0.4. Help?
-------------update---------------
So I re-flashed the full RUU and went through all the steps and still same outcome. "Secondary backup Failed!". I read that only version .1 may work if this error occurs?
=-\
Izeltokatl said:
So this is what i've done and its failing with the error: "Secondary backup FAILED!!"
-I reset everything by using the RUU 4.03.605.2.
-I then set the debugging mode, unlocked the bootloader
-Put AmonRa3.15 as my recovery
-Flashed the CWM SuperSU.
-Confirmed root access by using TitaniumBackup.
-Started the ControlBearRelease_vigor_ICS_3.14.605.5 for the ICS leak process.
-Then I get the fun error Secondary backup FAILED!!.
I'm using the latest version of JuopunutBear 0.4. Help?
-------------update---------------
So I re-flashed the full RUU and went through all the steps and still same outcome. "Secondary backup Failed!". I read that only version .1 may work if this error occurs?
=-\
Click to expand...
Click to collapse
i s-offed with the global ruu and and this version of control bear https://docs.google.com/file/d/0B0ZJtM40GdJ0SmVBbm40anJpRTg/edit ia got a few wierd errors but just started it up again and all went well..also make sure you have htc sync uninstalled from your computer
famouscollin said:
i s-offed with the global ruu and and this version of control bear https://docs.google.com/file/d/0B0ZJtM40GdJ0SmVBbm40anJpRTg/edit ia got a few wierd errors but just started it up again and all went well..also make sure you have htc sync uninstalled from your computer
Click to expand...
Click to collapse
Ya that's the exact same version I have, not really sure what to do? I re-did everything back to RUU again to no avail.
Izeltokatl said:
Ya that's the exact same version I have, not really sure what to do? I re-did everything back to RUU again to no avail.
Click to expand...
Click to collapse
you can try backing up your sd cards and partition them before you start the control bear process, and your sure you have root access correct? via rootchecker, tatanium backup or somethin gand usb degugging checked? if your still having issues look for apophis' thread named "so you need assistance, WE ARE HERE TO HELP" post in that thread im sure he can help you walk thru it..
When I bought my rezound used it had a constant boot loop issue. That's why I got it fairly cheap. I immediayly ran the global ruu hoping it would boot. It still boot looped. I was able to unlock, flash recovery and install newts xxx. I have tried to boot other romsand they give me issues too. Is there any way I can s off in my current configuration because I am pretty confident another ruu from my sd card just won't boot. Has anyone had success being on a custom Rom w global firmware hboot 2.27?
[SOLVED - See Post #9]
Hey everyone,
So, I have some experience with rooting/ROMs, bootloaders and recoveries, all specifically on my HTC Droid Incredible (Yep, the original). But that's long in the tooth these days, and getting rather difficult to stand the slower speeds and all.
I decided to pick up a used phone, in this case an HTC Rezound, to repair and serve as my default. Cracked digitizer, but that's an easy fix, and it works for the moment which is all that matters. Turns out there was one more problem with it - it doesn't boot Android. It gets stuck in a bootloop if you allow it to boot, but it does go to hboot if you boot it up and hold the VOL down key, as expected. I cannot boot into recovery.
I tried flashing the 4.03.605.2 RUU from AndroidPolice - same problem. So, I'm not sure where the issue lies. I'd like to start by just getting the phone back to stock, and booting into Android if anyone can help me. I should be able to do everything properly from there.
I'm not entirely certain if HBOOT is stock - it shows the Android on the skateboard at the bottom - I'm not sure if that's a custom HBOOT or not, and I can't seem to find any specific reference to it. It is LOCKED with S-ON, so, I've been assuming that it hasn't been tampered with too deeply, someone just hosed an upgrade and I'm not sure how to go about getting it fixed.
Any help is deeply appreciated.
- Katie
lolatvincent said:
You have to fastboot oem rebootRUU first
then fastboot flash zip PH98IMG.zip
you may have to flash the zip twice.
Code:
androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
(I can't link yet)
Click to expand...
Click to collapse
This might be able to help you too. You have adb and fastboot on your computer right?
lolatvincent said:
This might be able to help you too. You have adb and fastboot on your computer right?
Click to expand...
Click to collapse
Yes, I do. Thank you, I'll check that out!
Like I was saying, I knew it wasn't bricked, I just didn't know how to go about doing it. I think I get where I need to go with that.
ncc74656m said:
Yes, I do. Thank you, I'll check that out!
Like I was saying, I knew it wasn't bricked, I just didn't know how to go about doing it. I think I get where I need to go with that.
Click to expand...
Click to collapse
Flash a recovery in a zip right after you finish the ruu using the same method (no need for reboot).
To get root again you might want this: downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip
lolatvincent said:
Flash a recovery in a zip right after you finish the ruu using the same method (no need for reboot).
To get root again you might want this: downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip
Click to expand...
Click to collapse
Ok, no such luck. I did the RUU flash and then tried rebooting, no go, tried reflashing from my SD after that, nothing. I'm not sure what to do now. :/
Update
Small update - I did the HTC bootloader unlock and successfully got Amon Ra flashed onto it. Now working on getting Android to boot. *sigh* This thing is a serious pain in the... :angel:
If I get it to work, I'll be sacrificing a ram, or at least some RAM. :fingers-crossed:
Still, I'm open to any suggestions or help anyone can offer. Thank you!
I would make a nandroid now and keep it as is for a bit just to make sure it functions okay.
Then if all is good flash a ROM!
I'm running ViperRez and it's very good. Doesn't seem to stream bluetooth media but all else is good. Very nice daily driver. There might be an update coming which will hopefully fix the bt steaming.
feralicious said:
I would make a nandroid now and keep it as is for a bit just to make sure it functions okay.
Then if all is good flash a ROM!
I'm running ViperRez and it's very good. Doesn't seem to stream bluetooth media but all else is good. Very nice daily driver. There might be an update coming which will hopefully fix the bt steaming.
Click to expand...
Click to collapse
Heh, that would be doing things the SMART way. I'm going to do the unofficial CM9 which has BT streaming media, but not phone - sadly, something I'm much more interested in. I am wondering if I can't get the stock ICS or JB on there and just stick with that, since I do like using my BT headset. But since I've had no luck so far getting that to go on there, I think I'll take my chances with CM9 first, and go from there.
If I get that, I'll back it up thoroughly and then try my hand at putting the stock 4.03 on instead.
Solved!
Ok, so, I got CM9 booted!
The short of what I did was the following steps:
1) HTC Dev Bootloader Unlock
2) Installed Amon Ra
3) Installed CM9 using the S-ON instructions found at the site below - I can't link yet, so forgive me.
Code:
http://forum.xda-developers.com/showthread.php?t=1885553
4) Letting the bootloader flash the Kernel failed, so I had to do it manually by following the instructions for S-ON below in case of a parsing failure:
Code:
http://www.androidauthority.com/rezound-android-4-0-4-ics-cyanogenmod-9-cm9-rom-unofficial-120696/
5) Boot and done!
ncc74656m said:
Ok, so, I got CM9 booted!
The short of what I did was the following steps:
1) HTC Dev Bootloader Unlock
2) Installed Amon Ra
3) Installed CM9 using the S-ON instructions found at the site below - I can't link yet, so forgive me.
Code:
http://forum.xda-developers.com/showthread.php?t=1885553
4) Letting the bootloader flash the Kernel failed, so I had to do it manually by following the instructions for S-ON below in case of a parsing failure:
Code:
http://www.androidauthority.com/rezound-android-4-0-4-ics-cyanogenmod-9-cm9-rom-unofficial-120696/
5) Boot and done!
Click to expand...
Click to collapse
Oh! I misread your last post above mine and thought you had gotten it back to stock.
Your issue was exactly what you figured out, that when you are s-on you need to flash the kernel separately after flashing a ROM or else you'll get stuck. If you s-off that will be automated but s-off makes it easier to brick your phone. I don't flash often so I'm staying s-on.
Sorry I misread your post, I could've let you know about that.
feralicious said:
Oh! I misread your last post above mine and thought you had gotten it back to stock.
Your issue was exactly what you figured out, that when you are s-on you need to flash the kernel separately after flashing a ROM or else you'll get stuck. If you s-off that will be automated but s-off makes it easier to brick your phone. I don't flash often so I'm staying s-on.
Sorry I misread your post, I could've let you know about that.
Click to expand...
Click to collapse
No worries, it happens, thank you!!!!
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
BrahManty said:
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
Click to expand...
Click to collapse
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
acejavelin said:
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
Click to expand...
Click to collapse
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
BrahManty said:
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
Click to expand...
Click to collapse
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
acejavelin said:
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
Click to expand...
Click to collapse
Oh, thank god. Hahah. I didn't remember ever flashing any leaked firmware before, so I was kind of confused there. I figured I may have done it somewhere in the unlocking/rooting process and just couldnt remember. Okay, thanks again for the help. RUU's have always confused me with the way they work. I should be stable in no time hopefully.
And now I'm having more issues... I can't use the Rom Updater because somethings wrong with my usb connection. I can plug it in and transfer files and such, but trying to use any ADB commands results in "Device not found" and the Rom Updater says it can't connect to my device either. My HTC Drivers are up to date, so I'm not sure why this is happening. Is there any way I can just get the PH98IMG.zip for 3.14.605.12 instead of having to use the RUU?
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
acejavelin said:
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
Click to expand...
Click to collapse
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
BrahManty said:
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
Click to expand...
Click to collapse
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
acejavelin said:
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
Click to expand...
Click to collapse
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
BrahManty said:
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
Click to expand...
Click to collapse
Cool, glad you got it working.
That firmware is actually pretty decent and rock solid stable, you shouldn't have any more software related issues... Plus you can root/ROM like normal from that version, the radios may be slightler lower than most recommended versions, but they should work fine. If you do decide to go the ROM route again, I would suggest going S-OFF before starting, it will just make it easier in the long run.
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
*** TAMPERED ***
*** LOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
Click to expand...
Click to collapse
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
JoeKamel said:
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
Click to expand...
Click to collapse
You should be able to just boot into twrp and flash a rom
Sent from my ADR6425LVW using xda premium
izzaeroth said:
You should be able to just boot into twrp and flash a rom
Click to expand...
Click to collapse
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
JoeKamel said:
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
Click to expand...
Click to collapse
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Sent from my ADR6425LVW using xda premium
izzaeroth said:
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Click to expand...
Click to collapse
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
JoeKamel said:
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
Click to expand...
Click to collapse
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Click to expand...
Click to collapse
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
JoeKamel said:
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
Click to expand...
Click to collapse
Recovery = twrp
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
S-off is S-off... installing a RUU wont change that, it may set you back to 'Locked", but you are S-off so it doesn't matter, you can stay locked&s-off and its no different than unlocked/S-off.
If you are going back to stock and are S-off I would use the Global Mode Leak (4.3.605.2) available on AndroidPolice and flash in Hboot... rename file to PH98IMG.zip and place in root of SD card (how it gets there is a irrelevant) then reboot into Hboot, confirm and wait.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app