Related
i have tried everything possible with this phone to root it and nothing. Was wondering if someone would help me out??
I feel your pain and I've try the HTC dev. unlock with no luck I'm coming from the OG evo which was really easy to root ..
Sent from my PG86100 using XDA Premium App
go to htcevohacks.com i hace hboot 1.5 and it worked perfectly if u have the newest upgrade tho i dont think they have a root method out yet
Htcevohacks is easiest . And with the newest ota its still hboot 1.5
Sent from my PG86100 using XDA App
brandonaspencer said:
i have tried everything possible with this phone to root it and nothing. Was wondering if someone would help me out??
Click to expand...
Click to collapse
It would help us if you told us exactly what problems you are having.
Cool!! thanks!!
Sent from my PG86100 using XDA Premium App
Look at the roll up stickies. The directions are pretty clear. HTC method is going to be your only option
Sent from my Galaxy Nexus using XDA App
Rooting phone
brandonaspencer said:
i have tried everything possible with this phone to root it and nothing. Was wondering if someone would help me out??
Click to expand...
Click to collapse
have kinda problems have you had with rooting your phone.
HTC evohacks is very easy thanks !! For the help : )
Sent from my PG86100 using XDA Premium App
yami951 said:
Look at the roll up stickies. The directions are pretty clear. HTC method is going to be your only option
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I agree
Sent from my PG86100 using xda premium
Trying to root using HTC 1.5 with no success.
Hi to all I have tried to root using the HTC boot unlocker with no success. I was using the step by step instructions from HTC evo hacks. I got to the step at the command prompt where I put in the unlock code and I got this : C:\rootevo3dnew>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.152s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.161s
The phone screen asking me to unlock the bootloader never came up. Any help would be appreciated. BTW I have rooted at least 7 EVO 3D's. with no problems.
I'm stumped.
lilal100 said:
The phone screen asking me to unlock the bootloader never came up. Any help would be appreciated. BTW I have rooted at least 7 EVO 3D's. with no problems.
Click to expand...
Click to collapse
See the Guide/flashing Notes in my signature. You need to rerun the currently installed "FULL" Ruu or the the Latest RUU, then the unlock will work.
I did the HTCDev and unlocked it went to thread on downgrade from 1.5 hboot to 1.4 tried that and it did not work. I went to try the wire trick and this is what I get when I try to use the controlbear. the phone connects and goes through process but says the following...
======== ControlBear 0.6 beta for JuopunutBear S-OFF ==========
Starting up......
Connecting to device...
Searching device.....
Found device.....but device has no root!!
Press ENTER to exit.....
Any help would be helpful I have tried superuser but wont install, tried rootevo3dnew, temproot sensation Ect. everything says I need to be rooted.
I am running stock rom that shipped with phone and yes I did updates. I am Sprint CDMA 2.17 rom shipped, 1.5 Hboot. I have flashed roms and modded before but dont consider myself to be advanced. I have done flashing and installing roms with my old HTC Touch pro2 but alot easier on touch pro2 LOL... Please point me in the correct place I have beeen all over from this thread to that one and back and forth and yes I have search threads and I have tried them but still come back to the one with wire trick.. I am 1.5 with S-ON
inkjammer said:
I did the HTCDev and unlocked it went to thread on downgrade from 1.5 hboot to 1.4 tried that and it did not work. I went to try the wire trick and this is what I get when I try to use the controlbear. the phone connects and goes through process but says the following...
======== ControlBear 0.6 beta for JuopunutBear S-OFF ==========
Starting up......
Connecting to device...
Searching device.....
Found device.....but device has no root!!
Press ENTER to exit.....
Any help would be helpful I have tried superuser but wont install, tried rootevo3dnew, temproot sensation Ect. everything says I need to be rooted.
I am running stock rom that shipped with phone and yes I did updates. I am Sprint CDMA 2.17 rom shipped, 1.5 Hboot. I have flashed roms and modded before but dont consider myself to be advanced. I have done flashing and installing roms with my old HTC Touch pro2 but alot easier on touch pro2 LOL... Please point me in the correct place I have beeen all over from this thread to that one and back and forth and yes I have search threads and I have tried them but still come back to the one with wire trick.. I am 1.5 with S-ON
Click to expand...
Click to collapse
Ok, let's make sure we know where you are at to start with. When you use the vol and power button to boot to fastboot, does the phone show "unlocked". If not, I think you need to do the htc method again. I have not kept up recently, but I am not sure there is any method other than the HTC method that works every time for 1.5. I have used the HTC method on two phones without a problem, so that is the method I use.
Once you get that far, I used adb to push or flash the twrp image into the recovery section of the phone. Then you should be able to flash superuser via the install menu of twrp. There are threads that have detailed explanations on how this is done.
Yea, I had a bit of a learning curve from my TP2 also, but love this phone!
sonza said:
Ok, let's make sure we know where you are at to start with. When you use the vol and power button to boot to fastboot, does the phone show "unlocked". If not, I think you need to do the htc method again. I have not kept up recently, but I am not sure there is any method other than the HTC method that works every time for 1.5. I have used the HTC method on two phones without a problem, so that is the method I use.
Once you get that far, I used adb to push or flash the twrp image into the recovery section of the phone. Then you should be able to flash superuser via the install menu of twrp. There are threads that have detailed explanations on how this is done.
Yea, I had a bit of a learning curve from my TP2 also, but love this phone!
Click to expand...
Click to collapse
I am unlocked I did the HTC Dev and unlocked it. I have a stock rom (the one shipped on phone) all I have done is unlock it... I did try the controlbear and got what I posted on last post. I am Hboot 1.5 S-ON and stock rom is 2.17.651.5 HTC Sense 3.0 ANDROID Ver. 2.3.4... Like I said all I have done is Unlock and installed TWRP 2.2 and created a restore point and created a recovery and backed up my phone. All through Goo Manager. That is all I have done.
inkjammer said:
I am unlocked I did the HTC Dev and unlocked it. I have a stock rom (the one shipped on phone) all I have done is unlock it... I did try the controlbear and got what I posted on last post. I am Hboot 1.5 S-ON and stock rom is 2.17.651.5 HTC Sense 3.0 ANDROID Ver. 2.3.4... Like I said all I have done is Unlock and installed TWRP 2.2 and created a restore point and created a recovery and backed up my phone. All through Goo Manager. That is all I have done.
Click to expand...
Click to collapse
In my post Ive included a flashable SuperSU zip. What youll need to do is boot to recovery and install this zip. Then reboot. You should have superuser access then.
Still learning this forum so excuse any errors I make. I've spent the last 10 hours trying to fix the mess I created on my wife's Evo 3d. I was able to root my phone and it was relatively easy so I tackled hers as well and have gotten a bootloop I cannot figure out, 10 hours later. I'm on hboot 1.5. I unlocked the phone (using a pretty reliable video), loaded 4EXT Recovery then tried to load roms. Everything worked fine until the rom-loading portion. Since then, the phone loops, but once or twice it made it all the way to the main screen and before I could slide the ring, a read error message appeared next to the bars of service then the phone just completely reboots. Right now, the only thing I can get into is the bootloader and the clockworkmod v4.0.1.4, somehow I lost my 4EXT Recovery. I'm stuck and in dire straights as my wife is going out of town and will KILL me if I don't fix her phone. Please help! BTW, somehow I managed to NOT back anything up (stupidity on my part). Will I be able to get this thing back to stock at least or is it now a paperweight?
user22410 said:
Still learning this forum so excuse any errors I make. I've spent the last 10 hours trying to fix the mess I created on my wife's Evo 3d. I was able to root my phone and it was relatively easy so I tackled hers as well and have gotten a bootloop I cannot figure out, 10 hours later. I'm on hboot 1.5. I unlocked the phone (using a pretty reliable video), loaded 4EXT Recovery then tried to load roms. Everything worked fine until the rom-loading portion. Since then, the phone loops, but once or twice it made it all the way to the main screen and before I could slide the ring, a read error message appeared next to the bars of service then the phone just completely reboots. Right now, the only thing I can get into is the bootloader and the clockworkmod v4.0.1.4, somehow I lost my 4EXT Recovery. I'm stuck and in dire straights as my wife is going out of town and will KILL me if I don't fix her phone. Please help! BTW, somehow I managed to NOT back anything up (stupidity on my part). Will I be able to get this thing back to stock at least or is it now a paperweight?
Click to expand...
Click to collapse
Your not bricked by any means. And Im going to guess you tried to boot an ICS rom.. dont. They dont work with hboot 1.5. If you really want to go back to stock run the 2.17 RUU and youll be back to where you started. Another option is to download a GB rom and flash that. Not ICS. If your able to get to the bootloader than you can still load up 4ext recovery so you can flash the GB rom.
Edit: some hboot 1.5 users are lucky and can flash them if they used the correct VM firmware but majority of users have problems.
NineInchNails said:
Your not bricked by any means. And Im going to guess you tried to boot an ICS rom.. dont. They dont work with hboot 1.5. If you really want to go back to stock run the 2.17 RUU and youll be back to where you started. Another option is to download a GB rom and flash that. Not ICS. If your able to get to the bootloader than you can still load up 4ext recovery so you can flash the GB rom.
Edit: some hboot 1.5 users are lucky and can flash them if they used the correct VM firmware but majority of users have problems.
Click to expand...
Click to collapse
Thanks, I just tried flashing a rom that has taken it back to stock but I'm still in the bootloop. Should I stop flashing and simply locate the RUU?
22410,
It sounds like the kernel did not flash correctly with 4ext Recovery (next time, make sure u indicat S-on in its settings). I'm not sure if you were just stock 2.17 rooted or not, but use 7zip on your pc to open & extract/copy out the "boot.img" file from the rom, zip, etc you were using and copy it to your fastboot pc folder. Still have the Cwm 4.0.1.4 recovery.IMG file there too right (or the 4ext recovery.img file)? Ok...
- put phone in fastboot usb mode
From PC's fastboot command prompt type:
- " fastboot flash boot boot.img "
(this will reflash the kernel/boot image extracted from a rom)
If your recovery is screwed up:
- " fastboot flash recovery YourRecoveryFilename.img "
(ie: cwm_4.0.1.4_recovery.img or recovery.img, etc as listed in fastboot folder, to reflash a recovery to your phone).
With S-on, to properly enter a recovery for flashing ANYTHING you must:
- " fastboot boot YourRecoveryFilename.img "
(doesn't apply if using 4ext's Smartflash or TWRP's Dumlock settings. But you must have a bootable android OS/kernel first, once the flash is screwed it won't work).
If u have a Sprint CDMA EVO3D/HTC Unlocked & S-on (not Jbear s-Off), then the guide in my signature has more info.
Edit: as NIN said you will likely have problems flashing ICS roms with S-on (hboot version doesn't matter). If u are still unlocked & have a working recovery u can flash any gb Rom successfully after wiping system, data, & cache (or run superwipe zip). Meanrom GB v4.5 recommended.
Sent from my "Up all night, Sleep all day" EVO3D!
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
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?
Hey gang -
Working with my EVO 3D (Virgin Mobile) - and I'm stuck in a world of S-ON. The pre-requisites state that for the S-OFF Wire trick to work you must be on Windows 7 or less and be using specific version of HTC drivers. I'm running Windows 8, the specific version of HTC drivers recommended (HTC Driver 3.0.0.007) will not work in Windows 8. Needless to say I've not been able to get the wire trick to work and I'm "still sober". I've had very little success trying roms that will work and be happy with an S-ON phone. Until I decide to downgrade a machine back to Windows 7... what roms should I look for that I'll actually be able to use without bootlooping? So far the Midnight rom worked but is incredibly battery hungry (10 minutes of facebooking drops the battery 20-25%) - and today I installed MeanRom which seems to be doing better in the battery department.
Just looking for friendly advice... I've kinda given up on the wire trick for now.
Midnight1970 said:
Hey gang -
Working with my EVO 3D (Virgin Mobile) - and I'm stuck in a world of S-ON. The pre-requisites state that for the S-OFF Wire trick to work you must be on Windows 7 or less and be using specific version of HTC drivers. I'm running Windows 8, the specific version of HTC drivers recommended (HTC Driver 3.0.0.007) will not work in Windows 8. Needless to say I've not been able to get the wire trick to work and I'm "still sober". I've had very little success trying roms that will work and be happy with an S-ON phone. Until I decide to downgrade a machine back to Windows 7... what roms should I look for that I'll actually be able to use without bootlooping? So far the Midnight rom worked but is incredibly battery hungry (10 minutes of facebooking drops the battery 20-25%) - and today I installed MeanRom which seems to be doing better in the battery department.
Just looking for friendly advice... I've kinda given up on the wire trick for now.
Click to expand...
Click to collapse
CyanogenMod 10.1 - WILD FOR THE NIGHT Works like a dream! http://forum.xda-developers.com/showthread.php?t=2098121&nocache=1 Also compatible with Virgin (It says you need S-Off but I have S-On on my Evo 3D, just need to use Flash Image GUI)
jsls said:
CyanogenMod 10.1 - WILD FOR THE NIGHT Works like a dream! http://forum.xda-developers.com/showthread.php?t=2098121&nocache=1 Also compatible with Virgin (It says you need S-Off but I have S-On on my Evo 3D, just need to use Flash Image GUI)
Click to expand...
Click to collapse
Are you on the Sprint 1.5 hboot?
WFTN is not going to boot with the stock 1.57 VM hboot.
ramjet73
Yes, sadly I'm on 1.57 hboot. This has been quite the thorn in my side.
Only one i know is Harmonia from andriodforums evo v 4g sections.
Not sure if you can run Wild for the night, but its my rom of choice but im s-off.
Looking at Harmonia now - thanks for the suggestion - I'm running MeanRom since last night.
MeanRom's battery performance is better than the last one I was using, MidnightRom.
Being stuck in the world of S-ON sucks... I want so much to try the AOKP/AOSP roms.... ugh!
Midnight1970 said:
Looking at Harmonia now - thanks for the suggestion - I'm running MeanRom since last night.
MeanRom's battery performance is better than the last one I was using, MidnightRom.
Being stuck in the world of S-ON sucks... I want so much to try the AOKP/AOSP roms.... ugh!
Click to expand...
Click to collapse
The requirements for the JuopuntBear wire trick have been changed to Ubuntu Linux and they no longer support Windows at all. There's a live CD linked from the unlimited.io website that can be booted without having to actually install Linux so you might want to give that a try.
I have a guide here for root/S-OFF that might work with Windows 8 if you use this guide to install the drivers.
ramjet73
Thanks ramjet - I'm looking at that info now. It sure is a lot to consume.
Most guides all say "click this post" for reference, that has a link within to click another post, which links to another post... lol, gets to where I've got 10 tabs open in no time... not complaining at all, just a bit time consuming to ensure all the info has been digested...
I'm having fits!
I followed the guide... got the RUU installed and configured.... unlocked the bootloader (again)... flashed the SU.... now when I try to run ControlBear it won't complete, saying it can't transfer the backups - looking at the JuopunutBear website it says that error is due to a custom rom or htc sync installed.... I don't have htc sync and the rom is the RUU.... I'm really confused now...
Midnight1970 said:
I'm having fits!
I followed the guide... got the RUU installed and configured.... unlocked the bootloader (again)... flashed the SU.... now when I try to run ControlBear it won't complete, saying it can't transfer the backups - looking at the JuopunutBear website it says that error is due to a custom rom or htc sync installed.... I don't have htc sync and the rom is the RUU.... I'm really confused now...
Click to expand...
Click to collapse
If you are using my guide, restart controlbear.exe and check the screen for superuser access prompts that need to approved. That's usually why the secondary backup fails.
ramjet73
Well I'll be........
Guess it would help if I actually looked at the screen, huh?
Well... I'm happy to report that after following your guide, ramjet, that I'm officially S-OFF!!! (after only the 2nd try) - I'm a happy man tonight!! Thank you sir...
I'm also refreshed that I was able to ask my questions and receive the answers and help I needed without a "xda smackdown" that tends to follow such newbie questions. For this I'm grateful.
Installed my first AOKP rom, TeamDIRT_DirtyUnicorns_V1.2, and its bootlooping after the install... never made it to the setup screen.
Ugh....
Have you installed another hboot? 1.50 and below to boot aosp based ROMs. Either do the PG86IMG.zip method, or my new favorite, search XDA for fastboot commander. I had to use it for my gfs evo v 4g because I couldn't get the pg86img to work because of the cid. I recommend 1.50.5050 jbear or 1.04 eng.
Sent from my PG86100 using xda premium
Its on JuopunutBear hboot but its still 1.57 ... guess I need to figure out how to get to 1.50.5050.... argh.
Ready to start screaming, lol ... really thought I had it with the wire trick... double argh...
Found the thread for the PG86IMG_JBear_1.50.5050_hboot_GB -
Rename this to just PG86IMG.zip and let the bootloader flash it?
Midnight1970 said:
Found the thread for the PG86IMG_JBear_1.50.5050_hboot_GB -
Rename this to just PG86IMG.zip and let the bootloader flash it?
Click to expand...
Click to collapse
That's it.
Congratulations on getting S-OFF.
ramjet73
I think I screwed up.... after going back to the RUU - I forgot to install the OTA update while on the stock RUU... now I'm having troubles sending and receiving texts.... do I have to start over from scratch?
I was getting the Radio Interface Resource Shortage error msg - I rebooted the phone and all seems well now... hmm.
Midnight1970 said:
I think I screwed up.... after going back to the RUU - I forgot to install the OTA update while on the stock RUU... now I'm having troubles sending and receiving texts.... do I have to start over from scratch?
Click to expand...
Click to collapse
No problem.
Since you are S-OFF now you can just flash the firmware only updates from both the VM OTA's (November and March). The November update is in this post and the March update is in this post. Just flash them in sequence from the bootloader.
ramjet73
If I use fastboot commands to push those updates, can I rename them or do they have to remain named PG86IMG.zip?
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