My heart is about to break ;( , It's been a couple days without my rezound working properly.....
I tried to Flash BAMF's rom v1.1 and it kept on rebooting itself after a couple minutes.
After I found out that I had to install the new RUU i tried that.
And i guess i failed horribly.
I dl'd it and put it on my sd card.
I Locked my Rezound, and had it installing.
I ran it about 3 times and the blue bar went from blue to yellow and then it just went back to the android men skateboarding.
I tried to run my nandroid but I didnt get any signal what so ever (Wifi-3g-4g).
At this point I was going insane.
I'm not sure what I should do......
My phone is just a white screen having these text.
***UNLOCKED***
VIGOR PVT SHIP S-ON RL
HBOOT-2.11.0000
RADIO-0.95.00.1118r/0.95.00.1223r
OpenDSP-v10.6.0.7611.00.0919
eMMC-boot
Oct 6 2011, 15:43:22
PLEASE HELP ME
(Yes, i tried looking up very single thing....)
(I have both a PC and Mac, If possible can you post instructions for MacOS)
First, based off those version numbers, you never successfully installed the latest RUU. Scott has a nice write up on his site on how to do the RUU install, it's needed for any of the latest ICS based roms. - http://www.scottsroms.com/showthread.php/856-HOW-TO-Prepare-for-CleanROM-4-0-Update
If you're trying to restore a backed up rom, you also need flash the kernel back into place, nandroid restore can't do it because our phones are s-on. Try using this to do the restore - http://forum.xda-developers.com/showthread.php?t=1547496
Is it possible to do something else than recover the back up?
What are you trying to do before recovering the back up?
kevinlovesrice said:
My heart is about to break ;( , It's been a couple days without my rezound working properly.....
I tried to Flash BAMF's rom v1.1 and it kept on rebooting itself after a couple minutes.
After I found out that I had to install the new RUU i tried that.
And i guess i failed horribly.
I dl'd it and put it on my sd card.
I Locked my Rezound, and had it installing.
I ran it about 3 times and the blue bar went from blue to yellow and then it just went back to the android men skateboarding.
I tried to run my nandroid but I didnt get any signal what so ever (Wifi-3g-4g).
At this point I was going insane.
I'm not sure what I should do......
My phone is just a white screen having these text.
***UNLOCKED***
VIGOR PVT SHIP S-ON RL
HBOOT-2.11.0000
RADIO-0.95.00.1118r/0.95.00.1223r
OpenDSP-v10.6.0.7611.00.0919
eMMC-boot
Oct 6 2011, 15:43:22
PLEASE HELP ME
(Yes, i tried looking up very single thing....)
(I have both a PC and Mac, If possible can you post instructions for MacOS)
Click to expand...
Click to collapse
so when exactly did you almost brick?
I had a similiar problem. I relocked just fine, but when flashing the ruu it only partially worked even though it didn't give me any errors.
Turned out I had a bad download. Try to redownload ruu check file size and try to flash again. This worked for me.
tmar23 said:
I had a similiar problem. I relocked just fine, but when flashing the ruu it only partially worked even though it didn't give me any errors.
Turned out I had a bad download. Try to redownload ruu check file size and try to flash again. This worked for me.
Click to expand...
Click to collapse
That's weird. You have to run it twice, the first one updates hboot, and it will install in a random order. It will reboot, pull battery, get back to hboot, and install again. It will install in the correct order and be successful.
I was trying to recover a RezRom recovery but when I actually got into the back-up, it gave me no signal.
I'm going to try and re-download and hopefully revive me ReZound :,(
None of that = brick..
Sent from my ADR6425LVW using XDA Premium.
2 options at this point OP
1.) Reflash your custom recovery and a custom rom of your choice/nandroid and reflash kernel.
or
2.) Redownload/Check MD5 of the RUU, update, reflash AmonRA and reflash BAMF 1.1.
mjones73 said:
First, based off those version numbers, you never successfully installed the latest RUU. Scott has a nice write up on his site on how to do the RUU install, it's needed for any of the latest ICS based roms. - http://www.scottsroms.com/showthread.php/856-HOW-TO-Prepare-for-CleanROM-4-0-Update
If you're trying to restore a backed up rom, you also need flash the kernel back into place, nandroid restore can't do it because our phones are s-on. Try using this to do the restore - http://forum.xda-developers.com/showthread.php?t=1547496
Click to expand...
Click to collapse
Follow the scottsroms post on how to update. Whoever told you above that you have to battery pull to get to the second round of updating is wrong.
1. Lock it
2. Run the RUU PH98IMG.zip in the bootloader
3. It will go to the white HTC screen, for me, it stuck there for like 20min. Just make sure it's plugged in and be paitent.
4. It will reboot into fastboot, select bootloader and tell it to run the PH file again.
5. It will reboot into the stock ROM
if it does anything other than that, you've done it wrong.
6. Don't try to nandroid restore... just do a clean install and don't restore anything from Ti Backup. Why would you try to restore a broken install?
a-jive said:
Follow the scottsroms post on how to update. Whoever told you above that you have to battery pull to get to the second round of updating is wrong.
Click to expand...
Click to collapse
There were (not many) of some reports of hardlocking/freezing while updating hboot to where it comes up with an "OK" but doesnt give the prompt to press power to reboot.
Myself, I didn't have to.
this might help
Scott has a very detailed step by step guide in his CleanROM thread. Just a few pointers before you jump in. Following this and the steps in Scott's guide should help you to get your phone back. I truely suggest using the Amonra recovery, people have reported many times that this recovery just works right, no issues.
1) make sure you have a card reader for your computer that you can connect your removable micro-SD card to. Trust me, if you screw up somewhere in the process, having a reliable way to access the SD card is a life saver.
2) before flashing always wipe/factory reset 3 times, some think it is overkill, but if you end up with some odd glitch or bug when you just wiped once, you will most likely have to wipe and flash again to get rid of the bug...so of course you are actually saving time and hassle by just doing it 3 times in the first place.
3) make sure your battery is full or almost full before you start the process, you will avoid many problems by not having your phone battery die in the middle of a flash or update.
4) read, read and read again all the information and the instructions on what you are going to be doing, then make sure you understand and are comfortable Before you actually start. Reading through the forums and knowing beforehand what others have experienced, and the fixes, will make your life 100% better while you play with your phone.
THANKS
MY REZOUND IS ALIVE!!!!
I love scott.....
ohh my... im starting to think the definition for "bricking" a phone is changing
yojoe600 said:
ohh my... im starting to think the definition for "bricking" a phone is changing
Click to expand...
Click to collapse
+1
10 char
Yep. I was wondering when being in hboot=bricked.
Snuzzo said:
There were (not many) of some reports of hardlocking/freezing while updating hboot to where it comes up with an "OK" but doesnt give the prompt to press power to reboot.
Myself, I didn't have to.
Click to expand...
Click to collapse
My bad, didn't ever catch that issue in my research.
Related
Okay. So, I unlocked my bootloader, rooted my phone and then went to do the S-Off with the "wire trick." Well, during the Control Bear program it got to the 5th beer and rebooted my phone to the black screen with the phone and green arrows in a circle on it. It then couldn't find the device after 5 attempts of doing so. Yes, I had the drivers installed properly for the phone and ADB - so I don't believe that was the issue. Anyways, I closed Control Bear and unplugged my phone. Restarted my phone and Control Bear and it got stuck on the same screen, but now it can't find the device. I put the phone in fastboot, Control Bear detected it and then it booted up to the green arrow screen again.
At this point, I figure I just need to do a factory reset and everything should be fine. WRONG!
So far I have flashed 4EXT touch recovery so that I can attempt to flash a custom ROM. I tried flashing two different ROMs and after a successful installation it reboots and then gets to the same green arrow screen. I've also attempted to flash a stock RUU by putting it on the external SD card, renaming it PH85IMG.zip and it only gets through the blue status bar in the upper right corner and then goes back to the fast boot screen. Rebooting it afterward takes me to the same green arrow screen.
Suggestions on resurrecting my phone? I'd really like to not have to go through the unbricking BS in this thread: http://forum.xda-developers.com/showthread.php?t=1627882
Carrier
OS version
etc.
Info then problem solving after.
Most likely you can just restore a stock ruu, the one you used is probably older since you dug up a hard brick recovery thread though you have a softbrick, tells me you read a far way back than you needed to, so shoot some info, start solving from there.
TMOUS
Was running Stock ICS 4.0.3
HBOOT 1.93.0002
Dark Nightmare said:
Carrier
OS version
etc.
Info then problem solving after.
Most likely you can just restore a stock ruu, the one you used is probably older since you dug up a hard brick recovery thread though you have a softbrick, tells me you read a far way back than you needed to, so shoot some info, start solving from there.
Click to expand...
Click to collapse
Here: http://d-h.st/3VD
I don't know if that's the one you downloaded, but that's the latest image we have, you already know the process of renaming the file and placing it on your external sd card, also before you attempt to reload the stock RUU, don't forget to lock your bootloader, since you're s-on. It will say relocked, but that's fine, then put your sd card in and reboot into bootloader after relocking, watch the magic happen, hit volume up to update.
Ah! That's the step I was forgetting: relocking my bootloader! Thanks. I'm gonna get on that now. I'll let you know how it goes.
Dark Nightmare said:
Here: http://d-h.st/3VD
I don't know if that's the one you downloaded, but that's the latest image we have, you already know the process of renaming the file and placing it on your external sd card, also before you attempt to reload the stock RUU, don't forget to lock your bootloader, since you're s-on. It will say relocked, but that's fine, then put your sd card in and reboot into bootloader after relocking, watch the magic happen, hit volume up to update.
Click to expand...
Click to collapse
I figured, but I could've been wrong, yup let me know when you boot.
YEAH! That worked! Thanks so much! I think I'm gonna skip doing S-Off for now. LOL
DJ_Caibel said:
YEAH! That worked! Thanks so much! I think I'm gonna skip doing S-Off for now. LOL
Click to expand...
Click to collapse
:highfive:
Lol it's not exactly needed unless you wanna mess with things on an advanced level or go back to GB, which I doubt you do, so no worries.
I was looking to SuperCID, but I'm gonna leave that be and be happy with it as is. Thanks again for your help.
Dark Nightmare said:
:highfive:
Lol it's not exactly needed unless you wanna mess with things on an advanced level or go back to GB, which I doubt you do, so no worries.
Click to expand...
Click to collapse
so i went to switch out my battery and when i turned the phone back on it vibrated and displayed the white htc screen, then went black for a second and then stays on the white htc screen forever! Im a total noob when it comes to all the technical stuff about RUU's Kernels Roms and whatnot. I can get to bootloader, but i tried to do factory reset and it showed a green circle with a loading bar but then it changed into a red triangle with an exclamation. I tried flashing amon ra recovery but it doesnt work, although TWRP works. While in TWRP though, whenever i try to flash a zip file, it fails and says something like E:failed to mount /cache E:failed to mount /system E:failed to mount /data. Please help me i need this phone working to help me at my job. If someone can walk me through what i need to do i would REALLLYYYY appreciate it. Like i said though, i am a noob so i need realy stupified instructions lol. Thanks
just wanted to note that right now when i go to bootloader it says
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
Vigor PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
kverduin said:
just wanted to note that right now when i go to bootloader it says
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
Vigor PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Click to expand...
Click to collapse
First you should go to shipped-roms.com and download the vigor ics ruu.exe, the rezound downloads there are under vigor . Plug your phone into your computer and from hboot highlight fastboot press power and run the .exe file from your computer and follow the on screen instructions, this will return your phone to full stock ics. Make sure you download the vigor ics ruu.exe as the GB ruu will not work with s-on.
You can also download this: http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ it's the latest ruu it'll update your hboot, stock recovery, rom, and radios, to latest stock. Just download, rename the zip file to PH98IMG (don't include .zip it is a zip file it'll add it on its own in hboot) put it on your sd card, not in a folder just on. Put it back in your phone and boot to bootloader and runn the update, when it powers off. Run it again. (As it has to update the hboot to 2.27 first)Then you'll be on the stock latest. Then root and Rom from there. Of you need help pm me for my gtalk and I could walk you thru it..
sent from my s-off reZound rockin' viperRez Rom on global ICS firmware
Sounds like no boot.img
GrayTheWolf said:
Sounds like no boot.img
Click to expand...
Click to collapse
Its because of the security warning. The phone wont boot if it says that he has to run an RUU
Sent from my HTC Droid Incredible
Same exact problem. Installing zip now, god i hope this works!!
So my screen is the exact same, i tried to flash a kernal for not only wrong phone but wrong carrier too. Anyways no OS, when i try to flash either of the ways you have explained they both dont work. When i put it on the sd card as PH98IMG it looks like it loads it in the upper right then thats it. regular bootload screen after that nothing happens. try to load it by opening the application after im plugged in as fasboot usb and the program says Install script setup launcher has stopped working. I have been able to flash liquids rom and looks as if it is booting but waited 24 min and nothing happpend just stayed on boot screen. So im just trying to get back to RUU then work from there.
mrcorson said:
So my screen is the exact same, i tried to flash a kernal for not only wrong phone but wrong carrier too. Anyways no OS, when i try to flash either of the ways you have explained they both dont work. When i put it on the sd card as PH98IMG it looks like it loads it in the upper right then thats it. regular bootload screen after that nothing happens. try to load it by opening the application after im plugged in as fasboot usb and the program says Install script setup launcher has stopped working. I have been able to flash liquids rom and looks as if it is booting but waited 24 min and nothing happpend just stayed on boot screen. So im just trying to get back to RUU then work from there.
Click to expand...
Click to collapse
You need to extract the boot.IMG from liquid Rom and rename it ph98img and put that on your sd card or in the folder with adb and fastboot flash it using fastboot flash boot boot.img
Sent from my ADR6425LVW using xda app-developers app
Also wipe cache and dalvik cache in recovery immediately after doing this
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app
I ended up flashing liquidsmooth rom in recovery then had to wipe factory data reset, then i could wipe dalvick cache then when i rebooted it actually booted the rom and I LOVE IT. Still having some issues tho.
Still cant get my computer to talk to my phone when in fastboot usb i cant get any devices when i do "adb devices" cmd.
It says devices listed below but no devices.
Also im still stuck on TWRP 2.2 and I cant my 2.6 to flash in recovery. - Still troubleshooting this and might get it in a bit.
Thanks for the suggestions!!!
mrcorson said:
I ended up flashing liquidsmooth rom in recovery then had to wipe factory data reset, then i could wipe dalvick cache then when i rebooted it actually booted the rom and I LOVE IT. Still having some issues tho.
Still cant get my computer to talk to my phone when in fastboot usb i cant get any devices when i do "adb devices" cmd.
It says devices listed below but no devices.
Also im still stuck on TWRP 2.2 and I cant my 2.6 to flash in recovery. - Still troubleshooting this and might get it in a bit.
Thanks for the suggestions!!!
Click to expand...
Click to collapse
ooooh older stuff ick lol...do you have your htc sync drivers installed....what os are you on? are you s-on? what hboot you on? you need to be wiping before rom install and not after....are your issues pertaining to random reboots?
REV3NT3CH said:
ooooh older stuff ick lol...do you have your htc sync drivers installed....what os are you on? are you s-on? what hboot you on? you need to be wiping before rom install and not after....are your issues pertaining to random reboots?
Click to expand...
Click to collapse
Yes i did reinstall my HTC Sync drivers, I have been wipining factory reset, cache, system, dalvick cache before i flash a new rom. I am S-On. Havent really determined a reason to go s-off yet, i am messing up my phone good enough with this let alone a paperclip. no problem with random reboots. I finally decided to go to a custom rom bc i was sick of my phone rebooting for OTA updates then being late for work. So the 3 roms i have now tried are Liquid smooth which i liked but i couldnt get mms messages to show up on phone. Also it wouldnt change from silent to a beep for text message notifications. i could select it but it would stay as silent. So.... I flashed ViperRezROm which i just didnt like the look and theme. So i finally flashed Cyanogen ROM and come to find out its the same kernal as Liquid smooth so it looks the same and I like that but I still cant change the notification from silent to a beep for text messages. So i never know when i get a text.
Still working on trying to flash a newer version of TWRP.
Then this time flashing I tried to titanium backup and went to load my backup and it cant find it.... WTF
UGH... Learning so much with this stuff. just taking alot of patience.
Thanks again for yalls support, I love this forum.
Mike
BTW just to note...if your bootloader is locked fastboot flash methods will not work 90 percent of the time...if you flashed liquid 3.0 that's more than likely your problem with mms as that is a beta...but on more recent 4.3 builds mms is fixed...and no its not the same kernel...just similar source code...liquid 2.9 does not have this mms issue...any random reboots on 4.2 are caused by min frequency not set right at 384 mhz and using amon ra to flash or not doing a proper clean flash....I do recommend s-off as it will make life much easier for you for modding things or flashing custom zips and for future flashing back to full stock if needed as its not possible while s-on...you can always pm me for help as I've yet to run into an error I can't fix unless posted in op caused by source
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app
There is a few good reasons to S-Off.
1.No need to fastboot flash kernels
2.can RUU if needed
3.can flash recovery updates (cwm, twrp) as ph98img zips
4. Can keep bootloader ***locked***
5. No more ***tampered*** tag after you RUU
Scenario: you are out and about (or a computer isn't handy) somehow you are in an infinite bootloop. You nandroid restore. But it is something on boot partition. Only way to fix this while S-On is fastboot flashing a boot.img, but if you were S-Off, you would have restored the boot image from the nandroid.
Edit: added 5th reason
Sent from my ADR6425LVW using xda app-developers app
Uzephi said:
There is a few good reasons to S-Off.
1.No need to fastboot flash kernels
2.can RUU if needed
3.can flash recovery updates (cwm, twrp) as ph98img zips
4. Can keep bootloader ***locked***
5. No more ***tampered*** tag after you RUU
Click to expand...
Click to collapse
I finally went S-OFF to help another user get step by step to restore to fully locked and stock ruu. I decided to leave it S-OFF. It's so nice to be able to just load a rom and not have to do anything else (other than wiping). It makes changing/upgrading rom's a breeze.
I highly recommend it. It seems scary, but once you have done it once, you will not go back.
But be warned, never go back to S-ON on a non-HTC hboot... you will hard brick your device. That is the only real threat I've heard about... if you never go back to S-ON, then you have absolutely nothing to worry about. Just about any error can be fixed except for going s-on on a non-ruu hboot.
Thanks
molson8045 said:
You need to extract the boot.IMG from liquid Rom and rename it ph98img and put that on your sd card or in the folder with adb and fastboot flash it using fastboot flash boot boot.img
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
You saved me! That worked like a charm.
please help
Hi guys
Im have that problem in my htc rezound i seen the above comments but i couldnt able to understand so please tell the procedure one by one please pleasr..........
parthis said:
Hi guys
Im have that problem in my htc rezound i seen the above comments but i couldnt able to understand so please tell the procedure one by one please pleasr..........
Click to expand...
Click to collapse
If English is not your first language I apologise.
Otherwise, you need to be more specific and use full sentences.
GrayBoltWolf said:
Sounds like no boot.img
Click to expand...
Click to collapse
you were dead on accurate regarding my problem. Your post helped me revive an all but dead rezound!! Thanks man!!
Hello all, I need some help if there are any ideas what could be going on with this phone. I can usually fix my own phone problems, but this one has stumped me...
I bought a rezound dirt cheap that was stuck on the white HTC screen and would not boot into the stock rom. At the time I bought it, it was s-on and I could get in the HBOOT and run fastboot commands.
Since buying it, I have tried many things to get this thing working. I've tried to RUU (with PH98IMG and .exe) and apparently after it completes it is once again in a boot loop on the white HTC screen. I have been able to unlock and flash a custom recovery onto it (amon-ra) and install any cm/aokp rom onto it and boot into that. The only issue with that is when in the rom, my wifi and bluetooth will not connect at all. It wont even toggle on in settings and it is not greyed out. 4G and everything else seems to work ok.
At this time, I'm thinking there is some kind of hardware failure but I'm open to suggestions.
In summary...
I have been able to s-off
I have tried different firmware combos of HBOOTs/radios
I have flashed custom recoveries and roms and can boot into them without wifi or bluetooth
I have been unsuccessful to RUU to anything stock, it'll just boot loop the white HTC screen
Right now, I have installed Tron 2.1 onto it. I did notice post:http://forum.xda-developers.com/showthread.php?t=2272781&highlight=no+wifi
When I go into system/lib, there was no /modules folder. I went ahead and created it and put in bcmdhd.ko and rebooted, but still no go. I'm not sure why the /modules folder was missing, but this reaches the extent of my knowledge on what is supposed to be there.
I believe I have tried everything and done fairly thorough searches to get this phone working properly and am at a loss what to do next. If anybody has a thought of something to try, I'm all for it. Fortunately if this phone doesnt work out, its not a big deal to me.
I don't want this to sound like another "stuck on HTC screen" thread. I have been through all those and this doesn't seem like the same problem.
Your help is greatly appreciated!
tacoman said:
Hello all, I need some help if there are any ideas what could be going on with this phone. I can usually fix my own phone problems, but this one has stumped me...
I bought a rezound dirt cheap that was stuck on the white HTC screen and would not boot into the stock rom. At the time I bought it, it was s-on and I could get in the HBOOT and run fastboot commands.
Since buying it, I have tried many things to get this thing working. I've tried to RUU (with PH98IMG and .exe) and apparently after it completes it is once again in a boot loop on the white HTC screen. I have been able to unlock and flash a custom recovery onto it (amon-ra) and install any cm/aokp rom onto it and boot into that. The only issue with that is when in the rom, my wifi and bluetooth will not connect at all. It wont even toggle on in settings and it is not greyed out. 4G and everything else seems to work ok.
At this time, I'm thinking there is some kind of hardware failure but I'm open to suggestions.
In summary...
I have been able to s-off
I have tried different firmware combos of HBOOTs/radios
I have flashed custom recoveries and roms and can boot into them without wifi or bluetooth
I have been unsuccessful to RUU to anything stock, it'll just boot loop the white HTC screen
Right now, I have installed Tron 2.1 onto it. I did notice post:http://forum.xda-developers.com/showthread.php?t=2272781&highlight=no+wifi
When I go into system/lib, there was no /modules folder. I went ahead and created it and put in bcmdhd.ko and rebooted, but still no go. I'm not sure why the /modules folder was missing, but this reaches the extent of my knowledge on what is supposed to be there.
I believe I have tried everything and done fairly thorough searches to get this phone working properly and am at a loss what to do next. If anybody has a thought of something to try, I'm all for it. Fortunately if this phone doesnt work out, its not a big deal to me.
I don't want this to sound like another "stuck on HTC screen" thread. I have been through all those and this doesn't seem like the same problem.
Your help is greatly appreciated!
Click to expand...
Click to collapse
i would like you to do the following.
flash this http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
2 times. it will make sure we have a solid base to work on.
after that has ran 2 times. boot into the stock rom one time.
after that flash this https://dl.dropboxusercontent.com/u/12405441/new.global.firm.PH98IMG.zip
once this is done let it boot into the rom.
from here you should be good to flash any rom that is out there to date. (note please dont restore any system data, only app data)
ALSO MAKE SURE YOU HAVE 100% battery. doing an ruu can brick the phone if its interrupted.
report back when done
Thanks for replying. I have flashed that RUU several times in a row in the past, but I'm redownloading it now to make sure my copy isnt corrupt. Earlier experience when I double flashed this it still remained a white HTC screen loop.
Currently estimated at 6hrs to download, so I wont be able to reply for a bit with my findings...
tacoman said:
Thanks for replying. I have flashed that RUU several times in a row in the past, but I'm redownloading it now to make sure my copy isnt corrupt. Earlier experience when I double flashed this it still remained a white HTC screen loop.
Currently estimated at 6hrs to download, so I wont be able to reply for a bit with my findings...
Click to expand...
Click to collapse
When the Rezound first came out a bunch of people had boot loop problems because the phone was set to wcdma or some such thing instead of cdma. I'm just a noob hack but that's my memory of it. The cure was to boot without the back cover on which contains the antenna and then change the setting.
Ok, I have re downloaded the AndroidPolice RUU and flashed twice, but was not able to boot into it no matter how long I waited (20 min+). It would just loop the HTC white screen. I then went ahead and flashed your global update firmware and have the same result after waiting (20 min+), it just loops the HTC white screen.
I have tried this process several times last night, but still no progress.
As the phone sits now:
*** UNLOCKED ***
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
tacoman said:
Ok, I have re downloaded the AndroidPolice RUU and flashed twice, but was not able to boot into it no matter how long I waited (20 min+). It would just loop the HTC white screen. I then went ahead and flashed your global update firmware and have the same result after waiting (20 min+), it just loops the HTC white screen.
I have tried this process several times last night, but still no progress.
As the phone sits now:
*** UNLOCKED ***
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
You need stock recovery and a locked bootloader
- "Is it dark in there?"
drynyks said:
You need stock recovery and a locked bootloader
- "Is it dark in there?"
Click to expand...
Click to collapse
S/he ran the RUU so they are stock.
Sounds like the symptoms of a kernel issue. Try pulling the boot.img from this stock OTA ROM and flashing it.
http://forum.xda-developers.com/showthread.php?t=2260154
fastboot flash boot boot.img
I have the exact same you. Been this way for months. Maybe once a month BT/Wifi will turn on but only for a few hours maybe. Phone will reboot itself and come back up with the 2 broken again.
feralicious said:
S/he ran the RUU so they are stock.
Sounds like the symptoms of a kernel issue. Try pulling the boot.img from this stock OTA ROM and flashing it.
http://forum.xda-developers.com/showthread.php?t=2260154
fastboot flash boot boot.img
Click to expand...
Click to collapse
Well I finally booted into stock sense after flashing that boot.img which is a big step from before. For a brief moment, it saw wifi networks in my office but when I went to connect to one, wifi died and it no longer sees any wifi network. Bluetooth appears to still be an issue as well, i.e. will not turn on.
Flyhalf205 said:
I have the exact same you. Been this way for months. Maybe once a month BT/Wifi will turn on but only for a few hours maybe. Phone will reboot itself and come back up with the 2 broken again.
Click to expand...
Click to collapse
Unfortunatly that doesnt sound very good for me if you've been battling this wifi/BT problem for months.
synisterwolf said:
i would like you to do the following.
flash this http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
2 times. it will make sure we have a solid base to work on.
after that has ran 2 times. boot into the stock rom one time.
after that flash this https://dl.dropboxusercontent.com/u/12405441/new.global.firm.PH98IMG.zip
once this is done let it boot into the rom.
from here you should be good to flash any rom that is out there to date. (note please dont restore any system data, only app data)
ALSO MAKE SURE YOU HAVE 100% battery. doing an ruu can brick the phone if its interrupted.
report back when done
Click to expand...
Click to collapse
can you explain what you mean by flash the ruu twice once I have saved it to the root of my sd card? Does that just mean get to the bootloader, watch as it reads the the ph98img file and let it do that twice, or do I need to reboot in between, or do I need to put in a command?
fivedezs said:
can you explain what you mean by flash the ruu twice once I have saved it to the root of my sd card? Does that just mean get to the bootloader, watch as it reads the the ph98img file and let it do that twice, or do I need to reboot in between, or do I need to put in a command?
Click to expand...
Click to collapse
when you let hboot flash the zip, the first time is super short. it updates hboot, stock recovery, and splash i think. then it will reboot back to bootloader and ask to be flashed again. this time it will take some time to update because it does the whole system.
---------- Post added at 08:25 AM ---------- Previous post was at 08:24 AM ----------
tacoman said:
Well I finally booted into stock sense after flashing that boot.img which is a big step from before. For a brief moment, it saw wifi networks in my office but when I went to connect to one, wifi died and it no longer sees any wifi network. Bluetooth appears to still be an issue as well, i.e. will not turn on.
Click to expand...
Click to collapse
something doesnt seem right. the RUU would have flashed the boot.img for you. can you link me to the downloaded ruu that you have? also before you run the ruu did you do fastboot oem lock the bootloader?
Edit:
i remember an old trick from the inc days. after the RUU boot back into hboot and do a "factory reset" then boot into the phone. it use to fix the radio errors somewhere getting after a RUU. no clue why we did it. it just worked. try that when you are on stock recovery locked bootloader
Here is the RUU I have re downloaded. It was also the original I used in the past on my other Rezound
https://www.dropbox.com/s/1570h8l0ba1u7qp/rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
I have also tried the RUU 3.14.605.12.exe and a couple other different RUU versions, but have the same issue with that as well. Even on MicroMod777's OTA-Global-Stock-4.05.605.14 710RD-Rooted 5/1/13 flashed through amon-ra, I get the bootloop. I have done these as locked and unlocked bootloader with no difference. I have also tried the factory reset with locked bootloader.... no go with that either.
I was only able to finally boot in to stock by fastboot flashing the boot.img, and that is where this phone sits now. My major issue at this point is I dont have wifi or bluetooth and have dug through numerous posts and tried different things, and nothing is working on it. What was strange as I said in my previous post, the very first time I was able to boot into stock sense by flashing the boot.img, it briefly saw wifi networks but disappeared and disabled as soon as I tried to connect to one. I have not been able to replicate that since then.
On a sidenote and possibly related, since this phone has been sitting at my desk I decided to try and flash Newt's NOS JB v1.0.0 ROM and it bootloops also at the droid eye screen. I never was able to get it going on this phone. My other rezound boots this just fine.
I think I have reached the limits of my android knowledge of what to try on this thing. I am satisfied with it not having wifi/bluetooth since my wife wont be using those features. I would like to understand what the heck is going on though.
I have a rezound that is now semi-broken. I've got Arman's recovery, but I can't seem to flash anything. I'm really hoping someone can help me out!
I have an hboot that says tampered, unlocked hboot,
VIGOR PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12, 2012 16:47:46
This whole thing is acting weird, and I've been working on it for a few hours. I can't seem to get a rom actually working. Maybe I'm not waiting enough, but I left it there for five minutes on the boot screen and it did nothing. I've tried both OTA superstock and Ecliptic, neither to any avail.
Fastboot is being a *****. I've tried everything I can to get fastboot to work, and it will not. It just simply wont work. So I'm hoping someone has some ideas, because I would really like to make sure this isn't my first real brick. plz <3
What commands are you using? And what files are you trying to flash?
Sent from my HTC Rezound using Xparent Skyblue Tapatalk 2
I can help you with Ecliptic, which should have just been a simple reboot to hboot after rom flash and then normal reboot. What exactly is occurring? Are you getting "mainver is older" error?
I've tried flashing both hboot_7230ddr2_Runnymede_1.28.0006_20120424 and supermisc - and at this point, I believe the partition tables are borked. I currently have amonra for the recovery, and now when I try and install zip from sdcard it gets all lame and says it cannot mount it. I think what needs to happen first is through ADB I need to find a way to flash a full RUU or something. It used to have 4.03 on it, so I know I'm not far away from success.
oh and at no point has flashboot oem lock ever worked. No Flashboot command has ever responded with anything. I have uninstalled all HTC drivers, removed Sense, and installed just the revolutionary drivers, and they still don't work.
Win 7 x64 -
If the phone boots to hboot fine you should be able to get the ph98img ruu for 605.12 and put that on your SD card and have it reflash your phone. It will fix partition problems as well. Can you try that and report back?
Sent from my ADR6425LVW using Tapatalk 2
@cellularticulate
Going by your info in post #4 it sounds like your trying to flash stuff meant for the Sensation XL. You can't do that, also to add you are s-on and if you try to load an eng hboot you WILL brick.
Run through this PH98IMG RUU in bootloader mode.
http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Snuzzo said:
@cellularticulate
Going by your info in post #4 it sounds like your trying to flash stuff meant for the Sensation XL. You can't do that, also to add you are s-on and if you try to load an eng hboot you WILL brick.
Run through this PH98IMG RUU in bootloader mode.
http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Click to expand...
Click to collapse
And make sure you allow the RUU to complete, it will run through twice. It will go to a black screen for several seconds and then it will start over again. Make sure you don't interrupt it. Iirc, it will end up in bootloader when it's done, or maybe it reboots the phone.
It will only run through once, hboot and radio versions will match.
Sent from my ADR6425LVW using Xparent ICS Tapatalk 2
I need to fix the sd card permissions, I think. I will try flashing the RUU. I'm supposed to rename it and place it on my sdcard, and then just boot into hboot? It just...starts...automatically?
cellularticulate said:
I need to fix the sd card permissions, I think. I will try flashing the RUU. I'm supposed to rename it and place it on my sdcard, and then just boot into hboot? It just...starts...automatically?
Click to expand...
Click to collapse
If the ph98img is correct it (hboot) will detect it and prompt you to press up to start the update....
Sent from my Nexus 7 using Tapatalk HD
So I think I just realized why this has been a catastrophic failure this entire time. It's supposed to be on an EXTERNAL sd, right?
cellularticulate said:
So I think I just realized why this has been a catastrophic failure this entire time. It's supposed to be on an EXTERNAL sd, right?
Click to expand...
Click to collapse
Lol...yup...the small things get ya. Good luck finishing it up tonight. Finish ruu, unlock, flash custom recovery (I prefer the ph98img version of recoveries most of the time). Then load whatever ROM you want from recovery -or- continue rooting/setting up the stock ota ROM.
Sent from my Nexus 7 using Tapatalk HD
I still dont know why fastboot never worked :\ But yeah. That's literally all it was. The external SD card vs internal. I wish that was clarified somewhere. But I guess I know this going forward now!
I've got the RUU re-flashed, but I'm still stuck at the ecliptic boot screen. Ill try and do a fix permissions and see if that works.
cellularticulate said:
I've got the RUU re-flashed, but I'm still stuck at the ecliptic boot screen. Ill try and do a fix permissions and see if that works.
Click to expand...
Click to collapse
If you are stuck at the boot screen it's likely you don't have the correct kernel flashed for that rom. Did fastboot ever work for you? If not, do you have a ph98img version of the kernel for ecliptic? Snuzzo will probably chime in here shortly since i think that's his kernel...
I do not have a zip of his kernel, and fastboot still doesn't work. When I try and flash twrp and gives the mainver is old error, and I don't have time to fix this before work. Hopefully someone gives me golden advice and I can get this thing fixed. Three days now :\
Snuzzo, I know you don't do this specifically for money, but I will be donating to you. You've been a huge help.
you as well dottat.
One thing that's strange is I still think my partitions are messed up. I tried using the misctool to write an image to /sdcard2 and no matter what I tried, I couldn't find it. What's strange is when I'm in a shell, it shows this really, really weird login, and keeps kicking me OUT of the shell every couple of minutes. I'm going to try and switch back to TWRP since that what was on this phone when I got it. And yes, the phone was in working condition, things have just inherently gotten worse. http://puu.sh/2XtmZ.png
<3 y'all
OK what status are you at currently and why are you trying to flash that particular partition? Youre getting mainver is older? Hmmmm
You still got the latest twrp on here? If so, flash erez v9 then flash this
http://d-h.st/FZc
That's a dual purpose kernel zip. Do a fresh kernel flash with it. It should also set your mainver properly.
Sent from my Nexus 7 using Tapatalk HD
cellularticulate said:
I do not have a zip of his kernel, and fastboot still doesn't work. When I try and flash twrp and gives the mainver is old error, and I don't have time to fix this before work. Hopefully someone gives me golden advice and I can get this thing fixed. Three days now :\
Snuzzo, I know you don't do this specifically for money, but I will be donating to you. You've been a huge help.
you as well dottat.
One thing that's strange is I still think my partitions are messed up. I tried using the misctool to write an image to /sdcard2 and no matter what I tried, I couldn't find it. What's strange is when I'm in a shell, it shows this really, really weird login, and keeps kicking me OUT of the shell every couple of minutes. I'm going to try and switch back to TWRP since that what was on this phone when I got it. And yes, the phone was in working condition, things have just inherently gotten worse. http://puu.sh/2XtmZ.png
<3 y'all
Click to expand...
Click to collapse
If you let the RUU fun fully and you still have ecliptic boot screen showing you either didn't let the RUU fun fully or something really wonky is going on.. If you let the RUU run fully, you should have a stock rom booting by itself. Can we at least get to that point? We can probably get you around it. .but i would feel better starting from a fresh RUU.
Snuzzo said:
OK what status are you at currently and why are you trying to flash that particular partition? Youre getting mainver is older? Hmmmm
You still got the latest twrp on here? If so, flash erez v9 then flash this
http://d-h.st/FZc
That's a dual purpose kernel zip. Do a fresh kernel flash with it. It should also set your mainver properly.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
@Snuzzo - what's erez v9? tried googling. Didn't see it in the guides on here either.
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