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.
Related
Before I begin, I've read through a lot of threads on different forums and have yet to find a solution (that's working for me.)
I could never get my device to S-OFF so simply dropped the task. Not in too big of a rush right now. That being said, I'd like to go back to GB for a bit just to try a few things out.
I never flashed the ICS firmware, therefor I've had to use the old firmware patches. So, I tried running the RUU for GB and it only encountered error after error and my phone stayed at the black HTC screen. Any ideas?
Phone works just fine, just rebooted while I was typing this post and went straight into my ROM.
Only way I found is S-off'd, I had to go back to GB after ICS since it came on the phone I bought and needed to return it. Everyone told me I had to S-Off then RUU
If s on make sure you relock bootloader, then you should be able to run the gb ruu for whichever version you were on.
Sent from my Rezound
Downgrading radios when s-on could very well hard brick your phone. I strongly recommend that you s-off first.
Sent from my ADR6425LVW using Tapatalk 2
Abu-7abash said:
Downgrading radios when s-on could very well hard brick your phone. I strongly recommend that you s-off first.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
You can't downgrade with s on....
Sent from my Rezound
ericsignals said:
If s on make sure you relock bootloader, then you should be able to run the gb ruu for whichever version you were on.
Sent from my Rezound
Click to expand...
Click to collapse
ericsignals said:
You can't downgrade with s on....
Sent from my Rezound
Click to expand...
Click to collapse
Are you even the same guy?
Sent from my ADR6425LVW using Tapatalk 2
Pick a Gingerbread based rom and flash. Try out Chingy's Ineffabilis gingerbread.
Chyrux said:
I never flashed the ICS firmware, therefor I've had to use the old firmware patches.
Click to expand...
Click to collapse
Wish you guys would read.
Abu-7abash said:
Are you even the same guy?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
If you never ran an ics ruu you still were on gb firmware....so you can run a gb ruu. When you run the same ruu that's not downgrading....sheesh :rolleyes . And its probably the easiest way to get back to a working phone if you are lost and don't really know what you are doing.
Sent from my Rezound
ericsignals said:
If s on make sure you relock bootloader, then you should be able to run the gb ruu for whichever version you were on.
Sent from my Rezound
Click to expand...
Click to collapse
Tried that. RUU said "Could not update your phone at this time."
I came from stock GB originally in...April. Is there a specific RUU for that?
I've never used RUU's before so I'm lost.
aaand now, I'm pretty sure my phone is a brick. It's re-locked now, can't go into recovery, won't boot into ROM.
Chyrux said:
aaand now, I'm pretty sure my phone is a brick. It's re-locked now, can't go into recovery, won't boot into ROM.
Click to expand...
Click to collapse
Still only a soft brick. Would suggest trying the other of the two GB RUU .exe version packages if you only tried one of them, just a suggestion until someone else can help you and diagnose.
http://forum.xda-developers.com/showthread.php?p=19756694
Chyrux said:
aaand now, I'm pretty sure my phone is a brick. It's re-locked now, can't go into recovery, won't boot into ROM.
Click to expand...
Click to collapse
If you can get to hboot It's not bricked. Which ruu were you trying
pwned3 said:
If you can get to hboot It's not bricked. Which ruu were you trying
Click to expand...
Click to collapse
RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00.1123r_3161E_9K_QMR_release_233635_signed
Try running that one again. It should work. You have to run it twice anyway
pwned3 said:
Try running that one again. It should work. You have to run it twice anyway
Click to expand...
Click to collapse
Tried. It's stuck on the "Verifying the information on your PDA Phone...Please wait..." screen.
EDIT: Nevermind, went into Fastboot, working now. Let you know how it goes. Thanks for the help so far.
I'm getting a bootloader version error. An ICS RUU should fix this, right? Granted, I know that means I can't go back until I S-Off, but I'd rather that than have a soft bricked phone
I am in the same boat - S-ON. I flashed Scott's ICS Rooted Stock Rom, along with the GB Patch. I downloaded the PH98IMG.zip and HBOOT doesn't recognize it. Trying the exe may resolve this?
Issue resolved thanks to dsb in the IRC channel. For some reason, I thought I had to throw the unlock.bin on my SD card to unlock.
And to the guy above me, try pushing it through adb. Extract the ROM, find the boot.img, throw it into your ADB directory.
adb reboot bootloader
(make sure you're in fastboot USB)
fastboot flash boot boot.img
Chyrux said:
Issue resolved thanks to dsb in the IRC channel. For some reason, I thought I had to throw the unlock.bin on my SD card to unlock.
And to the guy above me, try pushing it through adb. Extract the ROM, find the boot.img, throw it into your ADB directory.
adb reboot bootloader
(make sure you're in fastboot USB)
fastboot flash boot boot.img
Click to expand...
Click to collapse
Hate to ask you this, but would you mind giving me a step by step on what you did to get back to GB?
Thanks -Kim
print.logic said:
Hate to ask you this, but would you mind giving me a step by step on what you did to get back to GB?
Thanks -Kim
Click to expand...
Click to collapse
With the new leak out, I haven't. However, I can still help.
Make sure there is no P98IMG file on your SD card.
1. Download the mainver fix from this post http://forum.xda-developers.com/showpost.php?p=23169557&postcount=4
2. Drop GB ROM of your choice onto SD card.
3. Flash the fix in recovery and reboot into bootloader.
4. Relock your phone by going into adb and typing in fastboot oem lock
5. Run GB RUU of your choice.
6. Use the HTCDev unlock on your bootloader
7. Download a recovery and push it to your phone by typing in fastboot flash recovery recovery.img
8. Boot into recovery, flash ROM, enjoy.
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!!
My Evo has been completely trashed and I have no clue what to do.
I have hboot 1.19 s-on and I did the HTCdev unlock, and I rooted it and have the latest version TWRP (i think 2.3.something) with SuperSU installed. I tried to flash a ROM that was supposed to be compatible with with I had but i guess not. Everything was going great but I was stuck on the CM boot screen. After about 30 min of it sitting in that screen I figured something was wrong so i reset it and went back into TWRP. Someone told me to download MeanRom and flash that because its kernel and rom would fix everything. Here's where things get weird. I download MeanRom to my computer and mount my phone in TWRP to move the file over to the phone and when i went to factory reset before flashing it it kept saying unable to mount SD card and Internal Storage. I tried to do a restore my phone to an old back up and that wouldnt even work. So I wipe both caches and try to flash MeanRom anyway. i got a failed error and my phone shut off. Now my phone will only go into the Fastboot thing on the white screen and when i try to go into recovery, it just stays on the TWRP loading screen, not even letting me into the recovery program.
Is there anyway to fix this? My best buy insurance has expired because i missed 3 payments since I'm away at school and not working a whole bunch. So my whole smash it to pieces and get a new one solution is no longer an option.
I'm on a mac by the way so is there something I can enter into terminal to fix this? I don't care about losing any files or anything I'll do whatever I have to, to fix this.
Thanks in advance
- Josh
Read om4's guide don't panic...hboot 119 s-on you have to flash kernels separately.
Sent from my EVO using xda premium
I ran into the same problem. Word for word, really. I use a Mac, too. I went through HTCdev unlock, tried to flash a CM10 nightly and ran into a boot loop. No matter what I did, it was stuck. I couldn't restore to a nandroid backup because internal storage wouldn't mount. Couldn't do anything. All I had access to was bootloader and TWRP recovery.
I don't know the specifics of how this fixed it (I'm nothing close to a developer), but this is what I did to get out of it. You will need access to a Windows machine onto which you can download things.
1) If you still have access to fastboot, unroot your phone to stock. Completely stock.
2) Use DirtyRacun S-OFF (you'll need a Windows computer for this). Go through the whole process.
3) Re-root.
Nothing I tried fixed it until I started fresh. I couldn't tell you how it worked, but if you're desperate you really have nothing to lose but a little bit of time by doing the same thing I did.
Hope you get this figured out.
falconoble said:
I ran into the same problem. Word for word, really. I use a Mac, too. I went through HTCdev unlock, tried to flash a CM10 nightly and ran into a boot loop. No matter what I did, it was stuck. I couldn't restore to a nandroid backup because internal storage wouldn't mount. Couldn't do anything. All I had access to was bootloader and TWRP recovery.
I don't know the specifics of how this fixed it (I'm nothing close to a developer), but this is what I did to get out of it. You will need access to a Windows machine onto which you can download things.
1) If you still have access to fastboot, unroot your phone to stock. Completely stock.
2) Use DirtyRacun S-OFF (you'll need a Windows computer for this). Go through the whole process.
3) Re-root.
Nothing I tried fixed it until I started fresh. I couldn't tell you how it worked, but if you're desperate you really have nothing to lose but a little bit of time by doing the same thing I did.
Hope you get this figured out.
Click to expand...
Click to collapse
How would i unroot if I cant get into SuperSU since i cant boot up my phone? Do I need to do that first or can i just run the RUU without Going into SuperSU and hitting Unroot?
Also what do I need windows for? Getting S-OFF? Or unrooting?
Also thank you! I really hope this work!
Relock your phone from fastboot then run the RUU. Now you're completely stock.
Sent from my rooted LTEVO running CM10.
Shahal said:
Relock your phone from fastboot then run the RUU. Now you're completely stock.
Sent from my rooted LTEVO running CM10.
Click to expand...
Click to collapse
I'm sorry if this is a stupid question. But how do i re-lock it from fastboot?
U have to use the cmd window on your windows computer. I did it with mine before I ran dirty racun. It is a simple command but u have to be in the right directory ind the cmd line. Go through and look at the dirty racun guide and it tells u how to re-lock word for word I believe.
Sent from my EVO using xda app-developers app
Shahal said:
Relock your phone from fastboot then run the RUU. Now you're completely stock.
Sent from my rooted LTEVO running CM10.
Click to expand...
Click to collapse
Okay so I found a video on how to re-lock my phone in fastboot but when i type the command "fastboot oem lock"
it just says ' <waiting for device >
any suggestions on what to do? It's been stuck like this for about 5 min now.. in the video it took less than a second.
jklatt747 said:
Okay so I found a video on how to re-lock my phone in fastboot but when i type the command "fastboot oem lock"
it just says ' <waiting for device >
any suggestions on what to do? It's been stuck like this for about 5 min now.. in the video it took less than a second.
Click to expand...
Click to collapse
Turn on USB debug in devopleper options
Sent from a lens flare powered EVO LTE
What's funny is that all you had to do with s-on is flash the boot.IMG from the ROM via fastboot, just like the first reply said to.
You're doing more work right now than you needed to.
I realize this is a little late, but if you're still having trouble and you're still s-on, go read om4's guide, or get s-off.
If you want to stick with s-on, you will have to fastboot flash the boot.IMG files from the ROM manually.
jkrlvgn said:
What's funny is that all you had to do with s-on is flash the boot.IMG from the ROM via fastboot, just like the first reply said to.
You're doing more work right now than you needed to.
I realize this is a little late, but if you're still having trouble and you're still s-on, go read om4's guide, or get s-off.
If you want to stick with s-on, you will have to fastboot flash the boot.IMG files from the ROM manually.
Click to expand...
Click to collapse
Yeah i couldn't figure out how to do that. I would ask a question on how to do that and i just kept on getting the response of "google it" "look it up on youtube" or look in the forums. and I wasn't ever sure really where to find it because all my searches for it came up useless.
I just did the RUU on my phone and its finally back up and running! What a relief!!!
Now I'm going to try to get DirtyRacun s-off. How do I put a Custom Rom on my phone with S-off?
With s-off you just flash it in twrp..no extra steps
Sent from my EVO using xda premium
jkrlvgn said:
What's funny is that all you had to do with s-on is flash the boot.IMG from the ROM via fastboot, just like the first reply said to.
You're doing more work right now than you needed to.
I realize this is a little late, but if you're still having trouble and you're still s-on, go read om4's guide, or get s-off.
If you want to stick with s-on, you will have to fastboot flash the boot.IMG files from the ROM manually.
Click to expand...
Click to collapse
I only have windows 7 64bit. So this means i cannot go the dirtyracun route. Is there any other way to get S-OFF?
if not.. How do i fastboot flash the boot.IMG from the ROM manually?
jkrlvgn said:
What's funny is that all you had to do with s-on is flash the boot.IMG from the ROM via fastboot, just like the first reply said to.
You're doing more work right now than you needed to.
I realize this is a little late, but if you're still having trouble and you're still s-on, go read om4's guide, or get s-off.
If you want to stick with s-on, you will have to fastboot flash the boot.IMG files from the ROM manually.
Click to expand...
Click to collapse
I wish I'd ran into you when I had the same problem. I wasn't trying to make things more complicated for him, just telling him that when it happened to me, I went back to stock, went with S-OFF, and everything worked fine. At the very least I figured he probably would have just wanted his phone back.
falconoble said:
I wish I'd ran into you when I had the same problem. I wasn't trying to make things more complicated for him, just telling him that when it happened to me, I went back to stock, went with S-OFF, and everything worked fine. At the very least I figured he probably would have just wanted his phone back.
Click to expand...
Click to collapse
No. You helped me soooooo much! I was literally about to sell my phone for parts or something because everything went wrong that could go wrong and on top of that I couldn't find anything at all on how to fix it. I just did what you said and my phone is fixed! I want to go s-off now but dirtyracun doesn't support windows 7 with 64 bit, it only supports windows 7 with 32bit which I don't have access to. So i'm trying to find another way that is reliable to go S-OFF. It seems like S-OFF is the way to go and it makes everything easier.
If I cant find out how to go S-OFF with the windows 7 64 bit computer, then I guess i'll go S-on HTCdev unlock again and hopefully figure out how to manually flash the ROM or whatever it is that you do with S-ON.
jklatt747 said:
No. You helped me soooooo much! I was literally about to sell my phone for parts or something because everything went wrong that could go wrong and on top of that I couldn't find anything at all on how to fix it. I just did what you said and my phone is fixed! I want to go s-off now but dirtyracun doesn't support windows 7 with 64 bit, it only supports windows 7 with 32bit which I don't have access to. So i'm trying to find another way that is reliable to go S-OFF. It seems like S-OFF is the way to go and it makes everything easier.
If I cant find out how to go S-OFF with the windows 7 64 bit computer, then I guess i'll go S-on HTCdev unlock again and hopefully figure out how to manually flash the ROM or whatever it is that you do with S-ON.
Click to expand...
Click to collapse
Most sense roms come with a kernel installer for people that are S-ON and there have been reports of success using Win7 64bit and running DirtyRacun but.... if you run into problems they will not help you
bigdaddy619 said:
Most sense roms come with a kernel installer for people that are S-ON and there have been reports of success using Win7 64bit and running DirtyRacun but.... if you run into problems they will not help you
Click to expand...
Click to collapse
okay does anybody know on a mac what would I have to do to flash MeanRom to my phone with S-ON and HTCdev unlock?
I'm not sure how to use the kernel installer you're talking about or where to look for it.
jklatt747 said:
okay does anybody know on a mac what would I have to do to flash MeanRom to my phone with S-ON and HTCdev unlock?
I'm not sure how to use the kernel installer you're talking about or where to look for it.
Click to expand...
Click to collapse
It's included in the script just flash it like any other rom it takes a little longer to boot because it's writing the kenel so don't freak out
jklatt747 said:
okay does anybody know on a mac what would I have to do to flash MeanRom to my phone with S-ON and HTCdev unlock?
I'm not sure how to use the kernel installer you're talking about or where to look for it.
Click to expand...
Click to collapse
There is an app in the market called Flash Image GUI to use it all you have to do is click on browse in the app search where ever you downloaded your Rom or kernel select it and it will extract and flash the boot.IMG for you. So if you are s on and wanna flash a aosp Rom you can first flash the kernel using the app then it gives you the option to boot directly in to recovery then install as usual wipe system ,data, both caches and flash your Rom that you extracted the kernel from. You can also just flash just a kernel if you want to OC.
Sent from my EVO using xda premium
bigdaddy619 said:
It's included in the script just flash it like any other rom it takes a little longer to boot because it's writing the kenel so don't freak out
Click to expand...
Click to collapse
dandan2980 said:
There is an app in the market called Flash Image GUI to use it all you have to do is click on browse in the app search where ever you downloaded your Rom or kernel select it and it will extract and flash the boot.IMG for you. So if you are s on and wanna flash a aosp Rom you can first flash the kernel using the app then it gives you the option to boot directly in to recovery then install as usual wipe system ,data, both caches and flash your Rom that you extracted the kernel from. You can also just flash just a kernel if you want to OC.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Okay so here's whats happens for me.
When i go bigdaddy's way: I put the MeanRom zip on my phone from my computer (MeanRom v64 or what ever the latest one is) I factory reset, wipe cache, wipe dalvic chache, and then go to install find the app and swipe to flash.. everything seems fine until i get an error and fail. It also says there is no MD5 file when i do this.
When I go dandan's way: I have the MeanRom zip on my phone (i've tried this with v64 *or whatever the latest one is* and v34) then i go into flash image GUI and go through finding it and everything. Then i get an error right above the Flash Image button saying "zip file must contain only one of the following: recovery.img, zimage, or a type of boot.img!" On my computer I unzipped the file and looked inside and all I see the boot.img and some folders but no recover or zimage so i dont know what it is talking about.
I really dont want to go through the processes of unrooting and relocking my phone again so i want to do this right. Any help from here on out would be greatly appreciated!
If someone could give me a step by step to follow or something for putting the Latest version of MeanRom on my phone that would be great!! I think i read somewhere that you have to put on the old version of MeanRom first. If that is so, could you also include how i would go about updating from the old version to the new one?
(If you're going to help me please make sure your method supports the HTC EVO 4G LTE on hBoot 1.19 Software v. 2.13.651.1 71ORD HTCdev Unlocked and Rooted with SuperSU and TWRP. (GooManager, and Flash Image GUI are installed to)
I dont know if this matters but it also says under Kernel Version:
3.0.8-01680-gb6402b4
[email protected] #1
SMP PREEMPT
Other info:
Baseband v: 1.12.11.0809
Android Version: 4.04
HTC Sense: 4.1
HTC SDK API level: 4.24
I know this post is really long and I probably put waaayyy more information then I actually needed to but I just want to be safe. It seems like everything I try for putting any Roms on my phone goes wrong with an error or failed message and I really want to do this.
Hey everyone,
So I have successfully HTC Unlocked my Rezound bootloader, installed Amon Ra, and then installed and booted the CM9 unofficial. Problem was that CM9 wasn't quite as cooperative as I'd hoped - it is unofficial, after all, and so I decided to abandon that in favor of Nils' Business ROM. Here's where I ran into issues.
I have tried everything in every order I can find online and think of, including Nils' writeup. So, for the life of me, I cannot get the leaked ICS RUU to boot (4.03.605.2 as listed in his instructions on XDA). Install runs fine every time I do it from the relocked (I checked) stock HBOOT, all steps included. Every time it reboots (and I've tried forcing it back into hboot to do the install a second time) it just goes to the white HTC screen and starts boot looping. Tried it a million ways, no go. Also worth noting - the stock recovery doesn't install properly, either. Some'fin is hinky, here.
So I've tried just "assuming" it went fine anyhow and then proceeding with the install for Nils' ROM and same deal, no go, although with one difference. With Nils' ROM, it does display the boot splash screen "Nils Business ROM" or what have you about 1 out of every 4 "boots" in the loop cycle, and then reboots again.
I think I am going to perform S-OFF tomorrow if I have the time, and then try it again using the S-OFF instructions, but I would sincerely appreciate any help from you all. Honestly, I'm at near wit's end with this device, and I don't want to be, I enjoy this chase too much, but I *really* want the reward at the end of it, lol.
Any help is deeply appreciated.
- Katie
Re: [Q]
I'm guessing because of the corrupted recovery, you have a bad download of the RUU. Try re downloading and check the md5 hash for a match. The ruu should reboot itself after the first pass and end up in bootloader again for the second pass.... If not then after the first pass just hold down power + vol down to get back to bootloader.
Hope this helps
Sent from my ADR6425LVW using xda app-developers app
Make sure that you have a booting ROM before you s-off. You will cause yourself all kinds of heartache if you don't.
Using an sd card reader on a pc, check md5 of your RUU zip file. If it checks out good, put the sd back in your rez and do an hboot power on and accept the update again. Report back with your findings. Also you will need to re-unlock your hboot after and install your recovery again.
Snuzzo said:
Using an sd card reader on a pc, check md5 of your RUU zip file. If it checks out good, put the sd back in your rez and do an hboot power on and accept the update again. Report back with your findings. Also you will need to re-unlock your hboot after and install your recovery again.
Click to expand...
Click to collapse
Hey, thanks. Yeah, the RUU does check out just fine against an MD5SUM.
nm.... just read your original post again and you say you did relock the phone. I was hoping it was something simple like that that was overlooked.
Carry on...
feralicious said:
Nothing to see here, folks, move along.
Click to expand...
Click to collapse
Right now, I cannot S-OFF because it requires a working stock image, and I'll be lucky to get anything more than CM9 unofficial working here.
You're too fast, now my bad post lives on...
So, when theh RUU failed, you unlocked again, flashed a custom recovery and tried to flash Nils' ROM?
Do you have a nandroid you can try to restore? Even if its the cm9 ROM at least to see if you can get it back to a working phone?
feralicious said:
You're too fast, now my bad post lives on...
So, when theh RUU failed, you unlocked again, flashed a custom recovery and tried to flash Nils' ROM?
Do you have a nandroid you can try to restore? Even if its the cm9 ROM at least to see if you can get it back to a working phone?
Click to expand...
Click to collapse
Well that's the trick. CM9 didn't work well enough to even be worth backing up. I'm trying to reinstall it again now just to see if I get there - and it looks like I will. Once I'm back up with that, I'm not sure where to go from there. The phone barely worked under CM9. Really hoping to get Nils' ROM on there, since it gives all the nice features of a stock device without the bloatware. Even if I never get S-OFF, I'll be perfectly happy with just Nils' software.
How about this... did you wipe everything before running the RUU? There's CleanWipe in the Development forum you can flash it from recovery and it will wipe everything 5 times!
This shouldn't make any difference, but there's also a different RUU, the OTA that's not global. You might try that one instead. I'm convinced that sometimes things are just voodoo even when they should be completely logical. That's definitely the case at work on the Avid systems I use.
Here's the link to it:
http://androidfiles.org/ruu/?dir=Vigor
feralicious said:
How about this... did you wipe everything before running the RUU? There's CleanWipe in the Development forum you can flash it from recovery and it will wipe everything 5 times!
This shouldn't make any difference, but there's also a different RUU, the OTA that's not global. You might try that one instead. I'm convinced that sometimes things are just voodoo even when they should be completely logical. That's definitely the case at work on the Avid systems I use.
Here's the link to it:
http://androidfiles.org/ruu/?dir=Vigor
Click to expand...
Click to collapse
I did try wiping everything first. No luck. I will try the CleanWipe tomorrow, because right now, whatever my issues are, I'm being prevented from solving them since I can't S-OFF and I can't even seem to get a working ROM to make the phone worth having! Ugh.
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Flyhalf205 said:
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Click to expand...
Click to collapse
Oh yeah! Try that. Someone else was having trouble and did it that way and it worked. Here's instructions, just make sure you use PH98IMG and not whatever is used in the instructions since it was written up for a different phone.
http://androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
Also, once you get your phone back to stock make a nandroid as soon as you flash the recovery again so you'll have that to go back to if you have any more issues.
Flyhalf205 said:
And you can try installing it under fastboot oem ruu instead of the ph.zip file
Sent from my HTC Rezound...
Click to expand...
Click to collapse
Thank you, your magnanimity! Seriously, lol, you're gracing my thread just by being here. :victory:
feralicious said:
Oh yeah! Try that. Someone else was having trouble and did it that way and it worked. Here's instructions, just make sure you use PH98IMG and not whatever is used in the instructions since it was written up for a different phone.
http://androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
Also, once you get your phone back to stock make a nandroid as soon as you flash the recovery again so you'll have that to go back to if you have any more issues.
Click to expand...
Click to collapse
Thanks for the clicky, Feralicious. Same results, unfortunately. I'm going to try doing the RUU flash of Nils' ROM instead. Do you guys know where I can get the ICS firmware by itself? I cannot be sure that it's actually flashed right, unfortunately.
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Flyhalf205 said:
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Click to expand...
Click to collapse
I'll do that stuff and let you know. Thank you!
Yes, I am on 2.27 HBOOT.
Point of interest, though possibly unsurprising. When I send the lock command, it locks and reboots, but says "Failed" in my command window screen. Sure this is probably normal since the phone might just reboot before responding to the computer, but possibly an issue.
I believe that is the image I tried before, but I'll do it again both ways to be certain and report back soon! :good:
ncc74656m said:
Yes, I am on 2.27 HBOOT.
Point of interest, though possibly unsurprising. When I send the lock command, it locks and reboots, but says "Failed" in my command window screen. Sure this is probably normal since the phone might just reboot before responding to the computer, but possibly an issue.
I believe that is the image I tried before, but I'll do it again both ways to be certain and report back soon! :good:
Click to expand...
Click to collapse
My DNA said something about failing when I locked it. But it locked just fine.
Since it is failing.
fastboot oem rebootRUU
fastboot oem lock ----if unlocked
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
Should work Maybe
Flyhalf205 said:
Your HBOOT is 2.27 and it should say relocked????
It should since you flashed the 4.03.605.2 RUU. The only RUU you will be able to flash since your S-ON is the one found here http://www.androidfilehost.com/?fid=9390034591667978440
The other RUU will fail because you can't downgrade. So the link above(The Global RUU) will that fail or completely install 100%??
If it does install 100% and boot loops still. Take out the sdcard. Boot into the HBOOT and perform a factory reset inside of HBOOT/Fastboot(NOT IN RECOVERY)
Report your status
Click to expand...
Click to collapse
Ok, so, this part including a factory reset got me to "HTC Quietly Brilliant" screen, but then it bootloops again. Tried factory resetting again to no avail. Trying the second part.
Flyhalf205 said:
EDIT
The link listed above for the RUU. Other way of installing it which is a great way to look at the status of everything.
Boot into Fastboot
fastboot oem rebootRUU
fastboot oem lock
fastboot flash zip rezound_AndroidPolice_4.03.605.2_PH98IMG.zip
fastboot reboot
Click to expand...
Click to collapse
Same thing as before unfortunately. :/ Performed a factory reset afterwards to be safe - no go. Everything shows OK though in both this and the above install. *shrug*
Flyhalf205 said:
EDIT2:
If you can't get it installed or it did. Just go ahead and unlock again. Flash custom recovery. Install a rom. Flash the boot.img in fastboot. Factory reset. and then see if it boots. If still not working. hit me up on google chat [email protected]
Click to expand...
Click to collapse
Proceeding with another attempt at installing CM9, I guess. Maybe the first one got hosed. If I get it booting in any form, I'll Nandroid it before trying anything else.
ncc74656m said:
Proceeding with another attempt at installing CM9, I guess. Maybe the first one got hosed. If I get it booting in any form, I'll Nandroid it before trying anything else.
Click to expand...
Click to collapse
I really wouldn't see why you would need a Sense rom to get s-off. I would imagine it would just need su and busybox installed. But nandroid then try a sense rom again. Make sure you flash the boot.img through fastboot
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