Related
I have an HTC EVO 3D That I purchased yesterday, and It's been flashed to Boost Mobile (A company owned and operated by Sprint) Boost is a CDMA service. I am interested in rooting my device, but when I tried this method: http://forum.xda-developers.com/showthread.php?t=1218193 I was stopped because my HBOOT isn't supported. Baffled, I went searching the forums and found this:http://forum.xda-developers.com/showthread.php?t=1547695 unfortunately, I'm not sure if it's safe to proceed with this procedure, because I wasn't there when my phone was flashed, and I don't know if HTC Dev was used. Furthermore, I don;t know if I have S-On of S-OFF, because I didn't flash my phone. Also, it has come to my understanding that linux is required for that method of HBOOT downgrade. Is there any way I can avoid that? It's kind of a lot of trouble.
You can check if you're s-on or s-off by looking at the top of the hboot screen. Pull the batt, put it back in, hold vol down + power.
If you don't have s-off, the downgrade is easy, linux is easy. After the downgrade you have to use revolutionary.io to achieve s-off and it'll likely screw up your boost flash. I'll edit with a thread link for prepping to downgrade with a carrier flashed phone.
Edit... http://forum.xda-developers.com/showthread.php?t=1646815
wikdNoob said:
You can check if you're s-on or s-off by looking at the top of the hboot screen. Pull the batt, put it back in, hold vol down + power.
If you don't have s-off, the downgrade is easy, linux is easy. After the downgrade you have to use revolutionary.io to achieve s-off and it'll likely screw up your boost flash. I'll edit with a thread link for prepping to downgrade with a carrier flashed phone.
Click to expand...
Click to collapse
Hboot says I have S-ON. By following the steps in that link you'll give, will I be able to restore my flash without losing MMS and 3G, etc.?
I'm really not sure, I've never flashed a phone. If you don't mind me asking, why do you want s-off? It's nice to have because it makes flashing roms easier but its not required to flash roms, and if your not sure you can flash your phone back, its probably not worth the risk.
wikdNoob said:
I'm really not sure, I've never flashed a phone. If you don't mind me asking, why do you want s-off? It's nice to have because it makes flashing roms easier but its not required to flash roms, and if your not sure you can flash your phone back, its probably not worth the risk.
Click to expand...
Click to collapse
Well the whole idea is that i need to downgrade HBOOT in order to root, and I was under the impression that to downgrade Hboot i needed to have S-OFF.
No, you just need to unlock at htcdev. Then you can root, give me a sec and ill give you another link. Once you think you can flash your phone to boost, I suggest getting s-off. Just less issues with s-off flashing.
Edit... A lot of guides out there, check the roll up sticky thread. This one will probably work. http://forum.xda-developers.com/showthread.php?t=1239821
wikdNoob said:
No, you just need to unlock at htcdev. Then you can root, give me a sec and ill give you another link. Once you think you can flash your phone to boost, I suggest getting s-off. Just less issues with s-off flashing.
Edit... A lot of guides out there, check the roll up sticky thread. This one will probably work. http://forum.xda-developers.com/showthread.php?t=1239821
Click to expand...
Click to collapse
THank man, i wish i could click thanks a thousand times. I'll try this method and see what i get.
Any time.. btw, you might be able to do the wire trick to get s-off without messing up the flash. It's in the dev section, called something like junoputabear s-off. Ask in that thread, maybe someone will know.
wikdNoob said:
Any time.. btw, you might be able to do the wire trick to get s-off without messing up the flash. It's in the dev section, called something like junoputabear s-off. Ask in that thread, maybe someone will know.
Click to expand...
Click to collapse
I got root, and recovery but for some reason the fastboot method wher you extrtact the boot.img and use fastboot to load recovery doesn't work for ICS roms, they bootloop. I found a working Gingerbread rom and I like it. Only issue is i wanted an ICS app. Btw, which gapps should I flash for 2.3.4?
_xNova said:
I got root, and recovery but for some reason the fastboot method wher you extrtact the boot.img and use fastboot to load recovery doesn't work for ICS roms, they bootloop. I found a working Gingerbread rom and I like it. Only issue is i wanted an ICS app.
Click to expand...
Click to collapse
From what I remember, if you boot a recovery from fastboot (fastboot boot recovery.img), you wouldn't need to extract any boot image. When you boot a recovery from fastboot, you'll be able to write to the boot partition, so all you need to do is flash the rom and it should work. With that said, I've read a lot of times that flashing ics roms with s-on will cause bootloops. I've never seen that personally, I was s-off before ics came along.
Btw, which gapps should I flash for 2.3.4?
Click to expand...
Click to collapse
You probably know this but ill say it just incase. You only flash gapps on aosp roms. I think all the ics gapps say ics in the name, and most of the time gapps for any rom are linked in the same thread as the rom.
Look at your pm in a little bit. I'm gonna send you some stuff that'll help you figure out how to correctly flash a phone so that you can s-off without worry. I can't really post it here.
Edit... Sent
Search has failed me, I have a rezound that i rooted after unlocking the bootloader and using hansons toolkit..
What is the best way to get to stock so I can accept the ICS update and re root?
I am familiar with how to relock my bootloader..
Thank you all
PS I called verizon today because my rezound is a bit fishy with the charger wanting to replace it to under warranty , they no longer have them available and are shipping the Razr Maxx as a substitute...UGGGH.
Don't accept that Motorola garbage.... Less processor speed and terrible screen also less dev support. Oh and you don't need to get back to stock to get ics just flash the ics ota in bootloader
Sent from my ADR6425LVW using xda app-developers app
please forgive my ignorance how do I flash the over the air update on to my phone from the bootloader mode
mayhem like me said:
Search has failed me, I have a rezound that i rooted after unlocking the bootloader and using hansons toolkit..
What is the best way to get to stock so I can accept the ICS update and re root?
I am familiar with how to relock my bootloader..
Thank you all
PS I called verizon today because my rezound is a bit fishy with the charger wanting to replace it to under warranty , they no longer have them available and are shipping the Razr Maxx as a substitute...UGGGH.
Click to expand...
Click to collapse
I've created a guide for rooted users to install the official ICS over-the-air: https://docs.google.com/document/d/1tmlh4OnplVfBNSjSyXfTYIVGfyb9lgI6ABpfg7gHY44/edit
I'm also working on a guide to restore root after installing ICS. It's not too bad at all, it's just finding a simple guide that's the trick... For restoring root after ICS, you can see my response here, where I reference discussions where I asked the same questions: http://forum.xda-developers.com/showthread.php?t=1829484
mayhem like me said:
please forgive my ignorance how do I flash the over the air update on to my phone from the bootloader mode
Click to expand...
Click to collapse
Correct me if I'm wrong, but you wouldn't do that for the over the air update.
You would need to flash stock recovery (assuming you've flashed a custom recovery), and then they can install the update through Android, like normal.
The guide i posted takes you through this process, as i did it.
---------- Post added 14th August 2012 at 12:08 AM ---------- Previous post was 13th August 2012 at 11:59 PM ----------
mayhem like me said:
PS I called verizon today because my rezound is a bit fishy with the charger wanting to replace it to under warranty , they no longer have them available and are shipping the Razr Maxx as a substitute...UGGGH.
Click to expand...
Click to collapse
Oh, and if you flashed Clockwork Mod, this is likely causing your charging problems. This is why i used AR Recovery 3.15 instead.
You can either take the OTA update or install an RUU.
Both ways, you have to relocked your bootloader or S-OFF.
For the OTA, you should be stock everything.
Stock recovery and rom.
For an RUU, just make sure you are on a rom that matches your firmware.
Gingerbread ROM on Gingerbread firmware.
Sent from my NeoMax Rezound
I have amon ra and I was responding to the first answer, I will try your method, do I have to go stock first or will the first step in your guide put me back to stock recovery, then relock bootloader .
mayhem like me said:
I have amon ra and I was responding to the first answer, I will try your method, do I have to go stock first or will the first step in your guide put me back to stock recovery, then relock bootloader .
Click to expand...
Click to collapse
For the OTA, you need to be stock everything or it won't install. This is why I included instructions on how to revert back to stock recovery before trying the OTA.
You do not need to re-lock your hboot if you have S-OFF. What happens is that the OTA update re-locks the bootloader and you have to unlock it again if you want to play with your device (like, re-install AR Recovery). Or, if you have S-Off, you can install a different hboot that's already unlocked, and then you can flash custom recoveries, etc. But since messing with the hboot is very risky, I chose to re-unlock my hboot the HTC way after installing the OTA.
*important edit*
The OTA may have worked for me with an unlocked hboot because I was S-Off prior to updating. If you're not S-Off, you may indeed need to re-lock before updating.
However, it may be just as easy to get S-Off. It's actually very easy. I will make a very easy guide for this as well. Let me know, and I can help you through it. I'm not an expert, but it doesn't take an expert. The hardest part for me was just finding a good, uncomplicated guide - doesn't seem to be one at the moment, though there is a ton of info out there.
Anyway, let me know if you want help getting S-Off.
bloodymurderlive said:
For the OTA, you need to be stock everything or it won't install. This is why I included instructions on how to revert back to stock recovery before trying the OTA.
You do not need to re-lock your hboot if you have S-OFF. What happens is that the OTA update re-locks the bootloader and you have to unlock it again if you want to play with your device (like, re-install AR Recovery). Or, if you have S-Off, you can install a different hboot that's already unlocked, and then you can flash custom recoveries, etc. But since messing with the hboot is very risky, I chose to re-unlock my hboot the HTC way after installing the OTA.
*important edit*
The OTA may have worked for me with an unlocked hboot because I was S-Off prior to updating. If you're not S-Off, you may indeed need to re-lock before updating.
However, it may be just as easy to get S-Off. It's actually very easy. I will make a very easy guide for this as well. Let me know, and I can help you through it. I'm not an expert, but it doesn't take an expert. The hardest part for me was just finding a good, uncomplicated guide - doesn't seem to be one at the moment, though there is a ton of info out there.
Anyway, let me know if you want help getting S-Off.
Click to expand...
Click to collapse
Think I may have to try S off , tried to get back to stock and bootloader relocked but stock recovery would not flash,, unlocked again and restored from a backup through Amon ra
mayhem like me said:
Think I may have to try S off , tried to get back to stock and bootloader relocked but stock recovery would not flash,, unlocked again and restored from a backup through Amon ra
Click to expand...
Click to collapse
you need to be unlocked if you want to flash recoveries. You should have flashed the stock recovery and then relocked. (if I'm understanding what you did)
mayhem like me said:
Think I may have to try S off , tried to get back to stock and bootloader relocked but stock recovery would not flash,, unlocked again and restored from a backup through Amon ra
Click to expand...
Click to collapse
Here is my new guide for S-OFF: https://docs.google.com/document/d/1_kRxD5LtazP7vEnr9cDb3iHwWB1ZfJD_yn6xXo7d1bo/edit
It's really very easy - at least it was for me. Using the metronome audio file that I linked to, I was able to successfully complete the wire trick on my first try. It was cake when actually doing it.
Let me know if this helps.
topgun1953 said:
you need to be unlocked if you want to flash recoveries. You should have flashed the stock recovery and then relocked. (if I'm understanding what you did)
Click to expand...
Click to collapse
hmm I dont remember...lol will flashing stock recovery take away SU and bring me stock? running another nand back up now...
mayhem like me said:
hmm I dont remember...lol will flashing stock recovery take away SU and bring me stock? running another nand back up now...
Click to expand...
Click to collapse
Flashing a different recovery doesn't modify the rom.
Sent from my NeoMax Rezound
mayhem like me said:
hmm I dont remember...lol will flashing stock recovery take away SU and bring me stock? running another nand back up now...
Click to expand...
Click to collapse
Flashing a recovery won't affect root. The OTA will break root, but it's simple to restore. That's the easy part.
What I think you should do first is achieve S-OFF (you do not need to re-lock if you achieve S-OFF. It's easy, and it makes switching ROMs easier).
Then flash stock recovery.
Then accept OTA update(s).
Then unlock again (rather than mess with your bootloader).
Then flash superSU to restore root.
All per my instructions. I think they will make it easy as possible for you. The hardest thing, I think, is trying to find a step-by-step guide on all of this.
Just my opinion. There's a lot of info out there, but it's hard to sort through which steps you should choose to do, and when you should do them.
So Sprint finally said there was a system update to ICS so I downloaded it and installed and it instantly popped up an error, didn't have any words it was just a picture of the guy with the warning sign. So I waited and it never did anything. I figured I would clear everything/factory reset and see if that fixed it. Nope. Even moreso, it wouldn't let me install any other ROM either. I did enough superwipes and stuff that I finally got the stock ROM to work so I'm back where I started.. One clue might be that I cannot seem to clear the sd-ext, it gives me an error there.
With it back in working order, if I don't clear anything and just try and install ICS from bootloader, what I show in the pic is what happens.
The last part about the E:error in sd card is what I was getting when all the other ROM's were screwing up.
Maybe bad sdcard
Sent from my PG86100 using Tapatalk 2
I don't see how when it works fine now. It's like something is messing with it but I have no clue what.
Re-lock your device and apply the update again.
Just do a fastboot command "fastboot oem lock".
Ugh, you cannot take an OTA if you are rooted with a custom recovery.
sitlet said:
Ugh, you cannot take an OTA if you are rooted with a custom recovery.
Click to expand...
Click to collapse
I had Revolutionary with CWM installed on mine w/ Gingerbread. Installed via EXE method and everything works.....
js593 said:
I had Revolutionary with CWM installed on mine w/ Gingerbread. Installed via EXE method and everything works.....
Click to expand...
Click to collapse
Right, that is not an OTA.
Sent from my PG86100 using xda app-developers app
wow! are you F***ing serious? OH I'M ROOTING AND I'M GOING TO TAKE AN OTA? SERIOUSLY!? lmao! Other than that, I'm not going to say anything more. lol. I WISH I WAS ROOTED AND HAD 1.4 INSTALLED WHEN I GOT MY PHONE! but no! it came with 1.5 and it took a year to figure out how to downgrade. lol. oh well. now they've figured everything out. can s-off with being on 1.5. love everyone on here. Anyway, DO NOT TAKE AN OTA!
I am not the greatest with these things. You are saying I need to unroot my phone for this to work? And I need to somehow get rid of the revolutionary recovery thing? I don't know what OTA means but I can see it's part of the file name. Is there a non-OTA version of it that I can use? For some reason a lot of ROM's don't work. I have hboot 1.5 with s-on and cynogenmod and a lot of ICS ROM's just hang on the HTC screen.
You are saying I need to unroot my phone for this to work? And I need to somehow get rid of the revolutionary recovery thing?
Click to expand...
Click to collapse
You don't need to unroot, but you need to lock your bootloader and get the stock recovery back to take the OTA. The easiest way to upgrade to ICS without doing all that is to flash the new firmware, then flash a stock rooted rom if you want to stay on the stock rom.
I don't know what OTA means but I can see it's part of the file name.
Click to expand...
Click to collapse
Over The Air, i.e. the update that Sprint sends out.
Is there a non-OTA version of it that I can use?
Click to expand...
Click to collapse
Upgrade firmware through bootloader, then flash a stock rooted rom or a custom rom based on ICS. If you want to use the new kernel, you will have to upgrade hboot as well, or you can keep your current hboot and use the VM leak kernel.
For some reason a lot of ROM's don't work.
Click to expand...
Click to collapse
Could be a number of reasons, you need the new firmware to run an ICS rom, and you need the new hboot if those roms use the new kernel.
I have hboot 1.5 with s-on and cynogenmod and a lot of ICS ROM's just hang on the HTC screen.
Click to expand...
Click to collapse
You can't flash kernels with s-on, so you will need to get s-off before you want to use an ICS rom.
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
Just my luck that Verizon puts this new OTA out the day before I was going to root this thing! It looks to me like we have no option now to root these updated devices. Anyone have any ideas?
therreid said:
Just my luck that Verizon puts this new OTA out the day before I was going to root this thing! It looks to me like we have no option now to root these updated devices. Anyone have any ideas?
Click to expand...
Click to collapse
You either need to wait, or try search how to revert the update.
dafuzzbudd said:
You either need to wait, or try search how to revert the update.
Click to expand...
Click to collapse
I tried to wipe/factory reset then install stock 2.17.605.2 RUU last night from .exe file. Wouldn't let it load due to updated bootloader. I also tried flashing unlock_code.bin from previous unlock experience with Hasoon2000's toolkit without luck as well as running through mdmower's unlock script with attempt to change CID. Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. I'm guessing I probably need root to modify bootloader to revert to old to unlock it... so probably just screwed until someone smarter figures out a way to unlock the new bootloader...
dkkunkel said:
Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. ..
Click to expand...
Click to collapse
Did you make sure your copy and paste to HTC was correct? That was my problem a couple of weeks ago. A single <space> was the culprit for me.
pmcall said:
Did you make sure your copy and paste to HTC was correct? That was my problem a couple of weeks ago. A single <space> was the culprit for me.
Click to expand...
Click to collapse
Yes, it was correct; just like other successful times... Did yours unlock after the latest OTA or was it prior to the update?
dkkunkel said:
I tried to wipe/factory reset then install stock 2.17.605.2 RUU last night from .exe file. Wouldn't let it load due to updated bootloader. I also tried flashing unlock_code.bin from previous unlock experience with Hasoon2000's toolkit without luck as well as running through mdmower's unlock script with attempt to change CID. Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. I'm guessing I probably need root to modify bootloader to revert to old to unlock it... so probably just screwed until someone smarter figures out a way to unlock the new bootloader...
Click to expand...
Click to collapse
Were you rooted with s-off, or s-on?
dkkunkel said:
I tried to wipe/factory reset then install stock 2.17.605.2 RUU last night from .exe file. Wouldn't let it load due to updated bootloader. I also tried flashing unlock_code.bin from previous unlock experience with Hasoon2000's toolkit without luck as well as running through mdmower's unlock script with attempt to change CID. Also HTCdev just gives me an error now when trying to get a new unlock token... ugh. I'm guessing I probably need root to modify bootloader to revert to old to unlock it... so probably just screwed until someone smarter figures out a way to unlock the new bootloader...
Click to expand...
Click to collapse
dkkunkel said:
Yes, it was correct; just like other successful times... Did yours unlock after the latest OTA or was it prior to the update?
Click to expand...
Click to collapse
Prior to update coming out, I have not installed the OTA.
junkmail9 said:
Were you rooted with s-off, or s-on?
Click to expand...
Click to collapse
Rooted, s-on. had avatar nightly installed//had issues with no data service and eventually re-loaded stock RUU with hopes to find a fix (after wiping, clean install, flash/re-flash firmware multiple times) and put avatar back on.... but then the OTA hit and here I am... unable to unlock bootloader.
dkkunkel said:
Rooted, s-on. had avatar nightly installed//had issues with no data service and eventually re-loaded stock RUU with hopes to find a fix (after wiping, clean install, flash/re-flash firmware multiple times) and put avatar back on.... but then the OTA hit and here I am... unable to unlock bootloader.
Click to expand...
Click to collapse
Hopefully you at least have data service now. Unless you can manage SuperCID, you might be out of luck for a while. I hope I'm wrong about that.
I am now curious if anyone who is s-off installed the OTA (either accidentally or intentionally) and retained s-off. In theory, if you're s-off you can recover from nearly anything. (I will admit that I have absolutely no desire to try it for myself)
junkmail9 said:
Hopefully you at least have data service now. Unless you can manage SuperCID, you might be out of luck for a while. I hope I'm wrong about that.
I am now curious if anyone who is s-off installed the OTA (either accidentally or intentionally) and retained s-off. In theory, if you're s-off you can recover from nearly anything. (I will admit that I have absolutely no desire to try it for myself)
Click to expand...
Click to collapse
How were you able to get the CID to change? I followed the CID change script manually using temp-root and DD commands through shell with a hex editor and it would NOT change the CID although I was given no errors. Crazy.
stevey500 said:
How were you able to get the CID to change? I followed the CID change script manually using temp-root and DD commands through shell with a hex editor and it would NOT change the CID although I was given no errors. Crazy.
Click to expand...
Click to collapse
I used DirtyRacun back on the 2nd OTA to obtain s-off, and DirtyRacun does not require the SuperCID method. I have not done anything with the latest OTA, as it isn't worth the risk to me... I somehow doubt that the DirtyRacun will work with the latest OTA, but I do not recall seeing anyone post that they have tried it, either.
junkmail9 said:
I used DirtyRacun back on the 2nd OTA to obtain s-off, and DirtyRacun does not require the SuperCID method. I have not done anything with the latest OTA, as it isn't worth the risk to me... I somehow doubt that the DirtyRacun will work with the latest OTA, but I do not recall seeing anyone post that they have tried it, either.
Click to expand...
Click to collapse
Ah... I'll go ahead and give it a try. This phone bone-stock is nearly unbearably slow. HTC bloating the hell out of these phone and then locking the bootloaders is a sad marketing scheme.
stevey500 said:
Ah... I'll go ahead and give it a try. This phone bone-stock is nearly unbearably slow. HTC bloating the hell out of these phone and then locking the bootloaders is a sad marketing scheme.
Click to expand...
Click to collapse
Anyone figure out if this works?? DirtyRacun after OTA I mean. thanks
join in for the unbelievable ... post2014-OTA [S-OFF] has been achieved
http://forum.xda-developers.com/showthread.php?t=2664460