Yesterday I flashed to the Charmeleon rom using TWRP. Stupidly I didn't make a backup of the stock rom and part of the process is wiping the current rom completely, which I did. Now it seems like I'm stuck with no way to get back to my stock rom. If there is ANY WAY to get back to the complete, full stock rom my EVO LTE came with, PLEASE explain to me how to do it! Thanks in advance for anyone who offers their help.
Well 1 you're in general so you're in the wrong section. 2 Yes! you can go back to stock WITH OUT your stuff using a RUU
http://forum.xda-developers.com/showthread.php?t=1655733
Or flash the stock rooted rom.
"We're coming from a pure power source"
Ok quick question, I found RUU files here - http://stockroms.net/file/HTCEvo4GLTE/RUU, and the link you gave me has 3 new ones... can anyone tell me which one is current?
cg121792 said:
Ok quick question, I found RUU files here - http://stockroms.net/file/HTCEvo4GLTE/RUU, and the link you gave me has 3 new ones... can anyone tell me which one is current?
Click to expand...
Click to collapse
your supposed to flash the same one that on your phone now... go into menu in about.. software info.. more.. build number.. mines is 1.13651.1 so thats the ruu that i would run... check to see what build u got and run that ruu and u golden!
Well that's my problem, none of those are on my phone, the Charmeleon rom is. I completely wiped the stock rom away which is what I'm trying to get back. Am I not able to do so?
An ruu is run from your pc, a rom is flashed through your recovery. Not to be a ****, but I think you should have read
a lot more about all of this before you started. So download the stock rooted rom from the dev section, boot into recovery, wipe everything but your sd card, and flash the rom just like you did before.
"We're coming from a pure power source"
Yeah sorry man, I'm just getting ahead of myself a bit because I've been searching this for the last (literally) 8 hours freaked out that I've done permanent damage to my phone. There's so many variations and believe it or not, there isn't a lot on this for this particular phone. Thanks to all you guys though, you all helped me a lot. Appreciate it.
The most recent build is 1.13, so you want to flash the stock rom of that build. It's always good to have the current ruu on your computer as a precaution, it can bring your phone back from the dead most of the time. Other than than its pretty easy, i'm on my phone so I can't post a link, but all you need should be in the stickies in the development section.
"We're coming from a pure power source"
Okay guys ran into antother quick problem. My bootloader was unlocked and in order to install the RUU it has to be locked. So I re-locked it and my phone will only start into the bootloader, with a 'security warning' on the screen. I now found out that if you have a custom rom installed when you re-lock the bootloader, you can only start into the bootloader until you run the RUU. So now I'm basically trying to find out how to run the RUU without actually being into my phone.
cg121792 said:
Yeah sorry man, I'm just getting ahead of myself a bit because I've been searching this for the last (literally) 8 hours freaked out that I've done permanent damage to my phone. There's so many variations and believe it or not, there isn't a lot on this for this particular phone. Thanks to all you guys though, you all helped me a lot. Appreciate it.
Click to expand...
Click to collapse
Like thwese guys said, if u want to take your phone into Sprint for any reason, just flash the Stock Rooted ROM. The RUU will take your phone back to it Original state, but u need to relock your Bootloader before u run that. But dont run the RUU and all that, just to have a Bacjup of a stock ROM. That would just be silly. flash the Stock Rooted ROM, and make a backup of that. It will be no different from having the Original Stock ROM. Only differnce is, is that it has SU and Busybox installed with it. SO your fine. No worries
cg121792 said:
Okay guys ran into antother quick problem. My bootloader was unlocked and in order to install the RUU it has to be locked. So I re-locked it and my phone will only start into the bootloader, with a 'security warning' on the screen. I now found out that if you have a custom rom installed when you re-lock the bootloader, you can only start into the bootloader until you run the RUU. So now I'm basically trying to find out how to run the RUU without actually being into my phone.
Click to expand...
Click to collapse
You should b able to run the RUU while the phone is in fastboot.
Everything worked. So now I'm completely back to the stock rom as if I had just taken the phone out of the box?
cg121792 said:
Everything worked. So now I'm completely back to the stock rom as if I had just taken the phone out of the box?
Click to expand...
Click to collapse
I did the same thing you did but with CM10 rom. Where can I find the most current stock ROM that is rooted? I want to stay rooted but also have the stock ROM available to flash? Your input is extremely appreciated.
Related
Ok, I screwed up....
Flashed the New ICS leak after relocking bootloader via PH
I was on a custom ROM and the flash failed miserably.
My phone will only boot into the bootloader and it shows Tampered and Relocked
I tried reflashing the last RUU in PH format and get an error saying Hboot version is older.
Anyone know how to get this phone to boot? Not how I wanted to start my Sat. morning at all.......
Wondering if someone can repack the latest RUU into a zip with a modified main version? I can only flash through fastboot and cannot Unlock the bootloader.
Scott has a tutorial for getting through this in the OP of ICS 4.0 Clean ROM
I'd think you would first want to unlock again. Then bootloader to recovery and restore the backup you made before trying to flash.
Got it unlocked again. I had to generate another Unlock code, my screw up somehow killed the original.
Issue resolved
Irieone said:
Got it unlocked again.
Click to expand...
Click to collapse
you need to chose factory reset , the first time after flashing a custom recovery then you can reboot into recovery after that. At least that was the experience of a few of us.
I'm back in business, but permanently branded. ( I think)
My bootloader still reads ***TAMPERED*** at the top. If anyone knows how to clear this, please let me know...
Irieone said:
I'm back in business, but permanently branded. ( I think)
My bootloader still reads ***TAMPERED*** at the top. If anyone knows how to clear this, please let me know...
Click to expand...
Click to collapse
from my reading last night it seems that this will go away once having the stock recovery back on the device, it only shows with a custom (amon ra, CWM) recovery.
andybones said:
from my reading last night it seems that this will go away once having the stock recovery back on the device, it only shows with a custom (amon ra, CWM) recovery.
Click to expand...
Click to collapse
Hmmm, it never said that until I botched flashing the new ICS leak. I spend a lot of time in the bootloader and never once saw it say tampered.
Irieone said:
Hmmm, it never said that until I botched flashing the new ICS leak. I spend a lot of time in the bootloader and never once saw it say tampered.
Click to expand...
Click to collapse
well that is because I am assuming you never installed a leaked firmware before...
you tampered with your bootloader, lol, so I guess it's letting you know.
I'm sure when I upgrade to the leak I'll have it too. not worried about it personally.
so installing the leak makes your bootloader say tampered? im sorta glad i held off on installing for right now.
Ok, I thought things were cool and they are not. I have my phone up and running. I was able to restore a backup I had...
Here is the catch tho, my phone will not read/access internal or external storage at all. My recovery will read storage
What to do now?
Irieone said:
Ok, I thought things were cool and they are not. I have my phone up and running. I was able to restore a backup I had...
Here is the catch tho, my phone will not read/access internal or external storage at all. My recovery will read storage
What to do now?
Click to expand...
Click to collapse
You can't restore backups on the new firmware.. I spent 6 hours last night into this morning figuring that out the hard way...Did you make a backup of the stock rom after you ran the RUU ? If so then just flash your backup and realize you have to wait for the roms to get updated. If you didn't the only way I can think of is to relock and rerun the RUU and don't restore backups.
Ouch, I don't have a backup of the stock rom.
Do you have a link to the last RUU? The link is dead in football's thread.
Wonder if I can flash Scott's new 4.0 ROM? I think I will try that...
[[/URL]
Irieone said:
Ouch, I don't have a backup of the stock rom.
Do you have a link to the last RUU? The link is dead in football's thread.
Click to expand...
Click to collapse
here is the one I downloadedhttp://lts.cr/Be5_ for the latest RUU. Unfortunately, once you flashed the new RUU you can't go back with the last RUU. The new one upgraded the hboot and I don't think you can downgrade.
you just need to rerun the same RUU you just did that is all and just wait for the rom you like to be updated.. most devs already have one in the works or out already
---------- Post added at 11:16 AM ---------- Previous post was at 11:02 AM ----------
Irieone said:
Ouch, I don't have a backup of the stock rom.
Do you have a link to the last RUU? The link is dead in football's thread.
Wonder if I can flash Scott's new 4.0 ROM? I think I will try that...
Click to expand...
Click to collapse
Good idea Scott's should work just fine .. just mount usb in recovery in order to get the Rom on the SD card .
Did you flash the RUU twice? That worked for me.
From here. http://forum.xda-developers.com/showthread.php?t=1550358 on your root sdcard rename the zip and flash it twice.
Scott's ROM keeps crashing and the phone reboots..
I will try flashing the RUU zip file again I guess..
You relocked the phone and change the file to PH98IMG correct?
My bootloader looked normal after the second flash. but then said tampered once i flashed a recovery.
Flyhalf205 said:
My bootloader looked normal after the second flash. but then said tampered once i flashed a recovery.
Click to expand...
Click to collapse
Were you on a custom ROM when your flashed?
Irieone said:
Were you on a custom ROM when your flashed?
Click to expand...
Click to collapse
At the time yes. Probably why I flashed it twice. But the RUU is used in HBOOT so it shouldn't have mattered if there is a custom recovery at the time.
Ok, I am doing this now
Irieone said:
Ok, I thought things were cool and they are not. I have my phone up and running. I was able to restore a backup I had...
Here is the catch tho, my phone will not read/access internal or external storage at all. My recovery will read storage
What to do now?
Click to expand...
Click to collapse
There is a zip floating around from Scott that you need to flash for your SD card. Check the development area
So like most users, I was very excited to hear about the ICS leak by Football since I've been waiting MONTHS for some sort of development on that.
Getting impatient on waiting for CM9 and Evervolv builds for the Amaze, I really wanted to try this new leak for T-Mobile. So I figured that in order to do that, I must get S-Off.
It seemed like a tedious process so I've been holding it off for a while. Now that I've got a copper wire and everything, I wanted to do the deed once and for all.
So I accidentally flashed a stock rom (which I thought was a good thing since the instructions said I needed a stock rom), but I seem to have lost root access. Superuser runs, but battery calibration says I need to have root first and Titanium Backup doesn't work. However, my phone still says unlocked and I can still run ClockworkMod Recovery. The S-Off program tells me that there's an error. Is there anyone that can help?
bri.kwong94 said:
So like most users, I was very excited to hear about the ICS leak by Football since I've been waiting MONTHS for some sort of development on that.
Getting impatient on waiting for CM9 and Evervolv builds for the Amaze, I really wanted to try this new leak for T-Mobile. So I figured that in order to do that, I must get S-Off.
It seemed like a tedious process so I've been holding it off for a while. Now that I've got a copper wire and everything, I wanted to do the deed once and for all.
So I accidentally flashed a stock rom (which I thought was a good thing since the instructions said I needed a stock rom), but I seem to have lost root access. Superuser runs, but battery calibration says I need to have root first and Titanium Backup doesn't work. However, my phone still says unlocked and I can still run ClockworkMod Recovery. The S-Off program tells me that there's an error. Is there anyone that can help?
Click to expand...
Click to collapse
Well you are on T-mobile so you have two choices here. you can S-off if you want to have total freedom or you can revert your phone to stock and relock your bootloader and flash it and then re-unlock again. but remember flashign this without s-off may prevent you from getting s-off later on.
Ray196 said:
Well you are on T-mobile so you have to choices here. you can S-off if you want to have total freedom or you can revert your phone to stock and relock your bootloader and flash it and then reunlock again.
Click to expand...
Click to collapse
Well, I can't flash the PH85IMG without S-Off, right? Because on the HBoot screen, it would load the file but i wouldn't be asked if I wanted to install it. So I had no idea what to do. I thought I had to have S-Off to install it. Does this really mean I've lost root even though my phone says unlocked and I can run Clockworkmod?
bri.kwong94 said:
Well, I can't flash the PH85IMG without S-Off, right? Because on the HBoot screen, it would load the file but i wouldn't be asked if I wanted to install it. So I had no idea what to do. I thought I had to have S-Off to install it. Does this really mean I've lost root even though my phone says unlocked and I can run Clockworkmod?
Click to expand...
Click to collapse
you can if you lock your boot loader and revert the phone to stock.
Ray196 said:
you can if you lock your boot loader and revert the phone to stock.
Click to expand...
Click to collapse
Well, how do i revert it to stock and reroot it exactly?
bri.kwong94 said:
Well, how do i revert it to stock and reroot it exactly?
Click to expand...
Click to collapse
i think you can use this. http://forum.xda-developers.com/showthread.php?t=1493905
bri.kwong94 said:
Well, how do i revert it to stock and reroot it exactly?
Click to expand...
Click to collapse
Pretty sure you just use fastboot to lock, open a command prompt with your phone attached in debugging mode, type in fastboot oem lock, then install the stock rom listed in the development section. (If I am wrong on this, someone please feel free to correct me.)
Wind Mobile released ICS today so I want to go back to stock from the custom ROM I'm using.
First I downloaded the RUU.exe in a thread I found here for Wind Mobile. I tried running it on my PC with my phone plugged in and it failed. So I thought perhaps I need to relock the boot loader (my phone is S-ON btw). So I downloaded the All in One Tool Kit, booted into the bootloader and chose relock option. First thing said success, second thing said failed too many failed attempts. After that my phone rebooted and went into the bootloader. It says **RELOCKED** and then *** Security Warning***. I'm assuming that meant it worked?
After this I could not reboot my ROM and I could not get into clock work mod recovery. So I attempted to install another recovery EXT4 included in the toolkit, it said success and rebooted. But when I choose recovery it just goes reboots into bootloader from the beginning again.
Did I fubar my phone?
mapleleafs89 said:
Wind Mobile released ICS today so I want to go back to stock from the custom ROM I'm using.
First I downloaded the RUU.exe in a thread I found here for Wind Mobile. I tried running it on my PC with my phone plugged in and it failed. So I thought perhaps I need to relock the boot loader (my phone is S-ON btw). So I downloaded the All in One Tool Kit, booted into the bootloader and chose relock option. First thing said success, second thing said failed too many failed attempts. After that my phone rebooted and went into the bootloader. It says **RELOCKED** and then *** Security Warning***. I'm assuming that meant it worked?
After this I could not reboot my ROM and I could not get into clock work mod recovery. So I attempted to install another recovery EXT4 included in the toolkit, it said success and rebooted. But when I choose recovery it just goes reboots into bootloader from the beginning again.
Did I fubar my phone?
Click to expand...
Click to collapse
Boot your phone into bootloader, choose fastboot, then run the RUU.exe file, follow the instructions to get it back to complete stock.
Mind telling me what ROM you were running? If it was ICS or something based on GB.
Edit: Wrong forum by the way
Thanks, it worked like that. I was on GB energy rom btw.
Back to stock, looks like Wind didn't even push the update out fully yet because no ones been able to update OTA yet.
Thanks again.
mapleleafs89 said:
Thanks, it worked like that. I was on GB energy rom btw.
Back to stock, looks like Wind didn't even push the update out fully yet because no ones been able to update OTA yet.
Thanks again.
Click to expand...
Click to collapse
Welcome, I was just checking the software version to make sure it would work correctly. Try checking for the update in settings, usually comes through faster that way.
ruu.exe being something like ruu_ruby_globalive_wwe_1.45.1500.2_r_radio_1.09.550L.11V2DC........etc etc etc.. ?
is that the right version to revert back to?
seems to be the only one i can find on the forums here.. via a really slow download link.
Ashcunak said:
ruu.exe being something like ruu_ruby_globalive_wwe_1.45.1500.2_r_radio_1.09.550L.11V2DC........etc etc etc.. ?
is that the right version to revert back to?
seems to be the only one i can find on the forums here.. via a really slow download link.
Click to expand...
Click to collapse
Well that's the only link we have here, you can always google for it, hopefully you can find a link on HTC's site, since that's probably the only link I'd trust.
forgot about this guy, everyone seems to trust him so ill go with the crowd...
http://forum.xda-developers.com/showthread.php?t=1335368
Ashcunak said:
forgot about this guy, everyone seems to trust him so ill go with the crowd...
http://forum.xda-developers.com/showthread.php?t=1335368
Click to expand...
Click to collapse
Fair enough, peace.
Hey, So i have a problem, I tried rooting my phone, and i guess i messed up somewhere, I lost my OS, and didn't create a backup because i'm stupid and didn't realize this could happen. I found a thread, relating to a similar problem, but a different phone so i relocked the phone with Hasoon's tool. Now i cannot find a proper RUU For my phone. I have an HTC One X+, Radio is 2.14.55.11, And the stock image is 1.20.661.1 or something. All i want now, is to return to stock. I've tried the RUU's from androidfiles . org/ruu/?developer=EvitaRE But no luck. It has some sort of error nearing the end. At the moment i can't find the error, as my phone is under %30, So after it reaches about 70, i'll try again and post the error. I'm getting pretty scared, as i'm new to this, and i don't want to lose my phone. Any help would be appreciated.
I don't really know what else to post, besides the radio, stock image file thing, and that it's the north american phone i guess, EvitaRE. The HBOOT is 1.40.0000 and it's stuck at the loading screen, 'HTC Quietly Brilliant'
Factory Reset's do not work, and push me back into the loading screen. It's in infinite boot, i guess, where i power the phone down and it just boots up again without me doing anything.
I dont know where i went wrong during the rooting process, as when Hasoon did it in his video tutorial, It worked out perfectly. but for me not so well, After flashing and unlocking bootloader etc, i clicked perm root, and i couldn't find the SuperUS or something, so i went to power the phone down into bootloader and it said i had no OS. I don't know what i did, and all i hope is that my phone can be somewhat revived so i can use it.
Thank you for reading, and any helpful information would be just appreciated.
~Cp
EDIT: Extremely sorry, but i have found other posts about this, but i can't seem to understand the fix, so if possible, please dumb it down for me! I'm extremely sorry for even attempting the rooting in the first place :S
Cpmasterme said:
Hey, So i have a problem, I tried rooting my phone, and i guess i messed up somewhere, I lost my OS, and didn't create a backup because i'm stupid and didn't realize this could happen. I found a thread, relating to a similar problem, but a different phone so i relocked the phone with Hasoon's tool. Now i cannot find a proper RUU For my phone. I have an HTC One X+, Radio is 2.14.55.11, And the stock image is 1.20.661.1 or something. All i want now, is to return to stock. I've tried the RUU's from androidfiles . org/ruu/?developer=EvitaRE But no luck. It has some sort of error nearing the end. At the moment...
Click to expand...
Click to collapse
Unlock the bootloader.
Install TWRP
Sideload a custom ROM
Flash that ROM's kernel.
Addicted2xda said:
Unlock the bootloader.
Install TWRP
Sideload a custom ROM
Flash that ROM's kernel.
Click to expand...
Click to collapse
Thank you, will try when I get home. Is there any roms you might recommend?
EDIT: Thank you, extremely. I honestly thought my phone was done for, after someone told me if ruu's didn't work i was screwed, guess i was talking to the wrong people. Thank you very, very much! After Sideloading, my phone booted up with venomXl rom, and works perfectly!
You are welcome.
BTW Sense 5 is here thanks to baadneez's insertcoin
Sent from my HTC One X+ using xda premium
Addicted2xda said:
Unlock the bootloader.
Install TWRP
Sideload a custom ROM
Flash that ROM's kernel.
Click to expand...
Click to collapse
i am stuck in the same place ..
bootloader unlocked
hboot 1.32
s 0ff
cid 1111111
i almost tried all roms .. nothing boots .. some rom just go to deep sleep .. any suggestions will be thank full
sathara said:
i am stuck in the same place ..
bootloader unlocked
hboot 1.32
s 0ff
cid 1111111
i almost tried all roms .. nothing boots .. some rom just go to deep sleep .. any suggestions will be thank full
Click to expand...
Click to collapse
I think you are not flashing the kernel.
Also - after flashing kernel, wipe cache and dalvik...
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