Related
I successfully installed Fresh Evo LTE 5.3.1 on my phone.
One of the suggestions is to update the Radio but I'm having a tough time doing that.
Here are my specs:
HBOOT 1.15.0000
S-ON
FreshEVO 5.3.1 ROM
I went to the link from the FreshEVO LTE 5.3.1 page to update the radio and have tried the following to install the Radio:
Attempt 1
Downloaded the Full Firmware zip file
Rename it "PJ75IMG"
Place it in the root of my SD card
Reboot into Bootloader
The PJ75IMG.zip file is detect but I only get 'Parsing PJ75IMG.zip' and then the Fastboot, Recovery, etc. options are displayed.
Attempt 2
From the same page where I downloaded the Full Firmware zip file, I also tried:
Download the Boot.img Only (signed) file
Flash it through the command prompt while in Fastboot ("fastboot flash boot boot.img")
Go into Bootloader
The PJ75IMG.zip is detected but still get the "Parsing..." message and nothing else happens.
Attempt 3
I have also tried going into my TWRP recovery and installing the Full Firmware zip AND the Radio 1.12.11.0809 Only.zip file but the installation fails.
Any pointers or a link to a video or a post would be much appreciated.
Thanks and sorry if this is a duplicate post but I really couldn't find any post that showed step-by-step process.
revert to stock and accept the ota, you can then fastboot recovery again and reflash. hboot 1.15 can not directly flash any firmware
edit: you may have to relock your hboot but ive seen users state they didnt. if you decide to relock the phone you will have to unlock the bootloader again to enable fastboot
om4 said:
The easiest way to update your firmware is to revert to stock and accept the ota, you can then fastboot recovery again and reflash
Click to expand...
Click to collapse
I don't have my stock backup anymore.
I've heard stuff about using RUU or something like that. Any quick guide on how to revert back to stock?
DO NOT UNROOT TO ACCEPT THE OTA OR RUU
I'd highly suggest just staying with your current radios and waiting for S-OFF before trying to update the radios. You can still flash the new ROMS in the meantime
You cannot update radios or firmware with Hboot 1.15 or 1.19------->Thats why it is suggested and not required
Rxpert said:
DO NOT UNROOT TO ACCEPT THE OTA OR RUU
I'd highly suggest just staying with your current radios and waiting for S-OFF before trying to update the radios. You can still flash the new ROMS in the meantime
You cannot update radios or firmware with Hboot 1.15 or 1.19------->Thats why it is suggested and not required
Click to expand...
Click to collapse
Thanks for the warning.
Since I'm pretty new to all this, I'll play it safe and stick to what I have.
sorry guys internet crapped out and i got stuck trying to post lol. rxpert has a point but with so much negativity about s-off never coming I'm starting to consider taking the OTA.
also you should always have a back up, its your go to solution when nothing else seems to be working since its a back up of when everything was new and working be it stock or custom
The new radios aren't worth losing the possibility, no matter how small
Sent from my EVO using Tapatalk 2
True...
om4 said:
sorry guys internet crapped out and i got stuck trying to post lol. rxpert has a point but with so much negativity about s-off never coming I'm starting to consider taking the OTA.
also you should always have a back up, its your go to solution when nothing else seems to be working since its a back up of when everything was new and working be it stock or custom
Click to expand...
Click to collapse
Just so I am clear, I too am 1.5 so if have my orginal rom, (the one after I unlocked my bootloader) i can restore it and accept the OTA without having to relock my phone? (it wont brick):good: Or do i have some other steps to take, I read the don't panic instructions, but it only mentioned what the OTA does ( relocks with a new rom) but nothing about what happens if I don't relock before I accept the OTA, I know i seem a bit slow, 4g lte isn't as interesting as OG 4g without S-off.
RamesisX said:
Just so I am clear, I too am 1.5 so if have my orginal rom, (the one after I unlocked my bootloader) i can restore it and accept the OTA without having to relock my phone? (it wont brick):good: Or do i have some other steps to take, I read the don't panic instructions, but it only mentioned what the OTA does ( relocks with a new rom) but nothing about what happens if I don't relock before I accept the OTA, I know i seem a bit slow, 4g lte isn't as interesting as OG 4g without S-off.
Click to expand...
Click to collapse
I havent yet done it myself but users have said they didnt need to relock, how ever as captain said there is no real need to update right now. If you decide to go ahead it would be a good idea to relock ( fastboot oem lock ) just to make sure, you can unlock afterwards. I neglect to mention this in my guide because most phones now are on 1.19 anyway and those still on 1.15 are holding out for soff
You will want to have the stock recovery to take the ota. Most people do this by relocking and running the ruu
Once again, I'm providing the info but I don't recommend it
Sent from my EVO using Tapatalk 2
Rxpert said:
You will want to have the stock recovery to take the ota. Most people do this by relocking and running the ruu
Once again, I'm providing the info but I don't recommend it
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I am still researching how to relock without issues. I have my orginal rom but still leary about the entire relocking process. I was hoping i could restore to orginal sense rom, then take the OTA. otherwise I am looking for the simplest way to accompish the relocking task, but frankly nothing is easy when i comes to playing around with 4g lte, except it is rather difficult to brick. With my luck i might succeed in that LMAO
:good::laugh:
RamesisX said:
I am still researching how to relock without issues. I have my orginal rom but still leary about the entire relocking process. I was hoping i could restore to orginal sense rom, then take the OTA. otherwise I am looking for the simplest way to accompish the relocking task, but frankly nothing is easy when i comes to playing around with 4g lte, except it is rather difficult to brick. With my luck i might succeed in that LMAO
:good::laugh:
Click to expand...
Click to collapse
there is no simpler method for relocking hboot, simply fastboot oem lock
om4 said:
there is no simpler method for relocking hboot, simply fastboot oem lock
Click to expand...
Click to collapse
Used that and it worked great.
Evo 4G LTE
h-boot 1.19, s-on, HTCDev unlocked
Hello, I desperately would like to see how to put my HTC Amaze back to stock. A couple of months ago I tried putting it back to stock because the energy rom kept rebooting on me and draining my battery life randomly. Anyways I was not successful and so I just kept the rom and the rebooting problems stopped anyways. Now, its happening again and I would really love for some one to help me get it back to stock so I can see if it improves and maybe get the thing S-OFF later. I am with Wind mobile.
Any help is greatly appreciated,
A frustrated amaze user.
rspierz said:
Hello, I desperately would like to see how to put my HTC Amaze back to stock. A couple of months ago I tried putting it back to stock because the energy rom kept rebooting on me and draining my battery life randomly. Anyways I was not successful and so I just kept the rom and the rebooting problems stopped anyways. Now, its happening again and I would really love for some one to help me get it back to stock so I can see if it improves and maybe get the thing S-OFF later. I am with Wind mobile.
Any help is greatly appreciated,
A frustrated amaze user.
Click to expand...
Click to collapse
Well since you're s on lock your bootloader and flash a wind ruu from bootloader you can find the necessary thread in development section
Sent from my HTC_Amaze_4G using xda premium
ravike14 said:
Well since you're s on lock your bootloader and flash a wind ruu from bootloader you can find the necessary thread in development section
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Hey thanks for the response. So I locked the bootloader and then got the wind RUU renamed it as PH85img.zip or w/e its supposed to be. And now when in the boot screen it cannot find my file I then tried another RUU but this time is used the exe wind one but that one failed as well and came up as an error saying the hboot version is older then what im flashing or something?
So I am stuck at this point. Do you know how to get around this?
Make sure the ruu is on the root of the sd card
Sent from my SGH-T999 using Tapatalk 2
rspierz said:
Hey thanks for the response. So I locked the bootloader and then got the wind RUU renamed it as PH85img.zip or w/e its supposed to be. And now when in the boot screen it cannot find my file I then tried another RUU but this time is used the exe wind one but that one failed as well and came up as an error saying the hboot version is older then what im flashing or something?
So I am stuck at this point. Do you know how to get around this?
Click to expand...
Click to collapse
well you cant flash a exe you have to connect your phone to the pc and run the exe from pc and bout the hboot whats your current version? :/
ravike14 said:
well you cant flash a exe you have to connect your phone to the pc and run the exe from pc and bout the hboot whats your current version? :/
Click to expand...
Click to collapse
Yeah it was connected via usb. I got somewhere, now but im am hoping you can tell me what i need to do now. I followed the second post here : http://forum.xda-developers.com/showthread.php?t=2167596 and now I have GB rom on my phone running unlocked. What do I need to do from here so I can S-off and super CID? PS I tried doing an OTA update from the phone and it wont work.
Looking into the S-off guide it says i must be on a stock RUU. is the one i got install a stock RUU. Also my hboot version is 1.93.0002 (Mar 15 2012) which is ice cream sandwich according to the Unlimited.IO site, but the RUU im on is definitely gingerbread. What can I do about this?
rspierz said:
Looking into the S-off guide it says i must be on a stock RUU. is the one i got install a stock RUU. Also my hboot version is 1.93.0002 (Mar 15 2012) which is ice cream sandwich according to the Unlimited.IO site, but the RUU im on is definitely gingerbread. What can I do about this?
Click to expand...
Click to collapse
What is your android version in settings?? Cuz what your telling is kinda weird
Sent from my HTC_Amaze_4G using xda premium
Adroid Version: 2.3.4
HTC Sense version: 3.0
Software number 1.43.531.3
am I completely screwed now? Cause it seems i wont be able to get S-off or CID off while not on this unsigned rom (t-mobile), i am with Wind. The OTA does not work while on the phone (settings > software update). Would locking my bootloader and then loading the latest OTA zip from wind on the SD card work? I am very stuck!
rspierz said:
am I completely screwed now? Cause it seems i wont be able to get S-off or CID off while not on this unsigned rom (t-mobile), i am with Wind. The OTA does not work while on the phone (settings > software update). Would locking my bootloader and then loading the latest OTA zip from wind on the SD card work? I am very stuck!
Click to expand...
Click to collapse
well you have ginger bread so try the jbear GB s off tool in ubuntu
but what about the hboot version being ICS? Do you think it should still work?
rspierz said:
but what about the hboot version being ICS? Do you think it should still work?
Click to expand...
Click to collapse
what bout your CID?
I havent done anything to the CID, so I believe it is still locked to wind?
rspierz said:
I havent done anything to the CID, so I believe it is still locked to wind?
Click to expand...
Click to collapse
well choice is yours your android version says GB hboot says ICS :/ i say try the GB s-off tool but do at your own risk...
well S-Off worked so thats good haha. Now i am trying to super CID. However, when uploading the proper hboot for doing so it wont let me because of the CID.
Ignore that last post. I figured it out so all is good. Now here is another question, should i flash CM10.1 or your rom that viper one? How would I go about flashing a rom. I remembered before you would just go into recovery and then format all execpt sd card and then install from zip. I tried that with the CM10.1 rom and when I rebooted it did not work.
went ahead and tried installing the Viper rom and after i reboot (when it said all was good) it show a black screen with green arrows. And its stuck on that. I do not know what to do now. Because I should have everything open. Was I supposed to flash something after doing the S-OFF?
This is what I am getting stuck on. I tried another rom too, same thing. I can boot into 4ext. But cant get past this on boot up.
rspierz said:
This is what I am getting stuck on. I tried another rom too, same thing. I can boot into 4ext. But cant get past this on boot up.
Click to expand...
Click to collapse
Now your s off BUT you have gb firmware so you have to flash a ruu 1st then flash a recovery then supersu or just flash any rom you want if you decide to stay with the ruu stock rom to gain root permission flash supersu
Sent from my HTC_Amaze_4G using xda premium
For the last week or so, I've noticed my Wi-Fi has been dropping in and out. I had been trying some JB ROMS lately and restoring to another Sense ROM. I figured it needed a big refresh, so I ran the 403.605.2 RUU from the root of the SD card in the PH98IMG.zip form.
Still the same issues, and now my 4G is really flaky.
Now I'm wondering if my phone is just on its way out.
Is running the RUU from a PC better?
Can I do any other wipe/flash combos to reset it even further?
I am S-Off...
Run the ruu again and perform a factory reset in hboot BEFORE installing a custom recovery.
bwthor20 said:
For the last week or so, I've noticed my Wi-Fi has been dropping in and out. I had been trying some JB ROMS lately and restoring to another Sense ROM. I figured it needed a big refresh, so I ran the 403.605.2 RUU from the root of the SD card in the PH98IMG.zip form.
Still the same issues, and now my 4G is really flaky.
Now I'm wondering if my phone is just on its way out.
Is running the RUU from a PC better?
Can I do any other wipe/flash combos to reset it even further?
I am S-Off...
Click to expand...
Click to collapse
the most up to date ruu is firmware_4.05.605.14 with the 2.28 HBoot and 2.23.10.0123r, 2.23.10.0124r radios.....here is a link ( https://dl.dropboxusercontent.com/u/12405441/new.global.firm.PH98IMG.zip ) make sure you re install your recovery afterwards and that both radios read 2.23 and not 2.22...theres much more info on this here ( http://forum.xda-developers.com/showthread.php?t=2260154 ) but make sure its the new global ota latest update...this is what i did and hope this helps you
Edit: i too am s-off and ran this with all jb roms posted and it works perfectly fine....also always make backups and rename that file on the link and make sure it looks like PH98IMG.zip
REV3NT3CH said:
the most up to date ruu is firmware_4.05.605.14 with the 2.28 HBoot and 2.23.10.0123r, 2.23.10.0124r radios.....here is a link ( https://dl.dropboxusercontent.com/u/12405441/new.global.firm.PH98IMG.zip ) make sure you re install your recovery afterwards and that both radios read 2.23 and not 2.22...theres much more info on this here ( http://forum.xda-developers.com/showthread.php?t=2260154 ) but make sure its the new global ota latest update...this is what i did and hope this helps you
Edit: i too am s-off and ran this with all jb roms posted and it works perfectly fine....also always make backups and rename that file on the link and make sure it looks like PH98IMG.zip
Click to expand...
Click to collapse
Thanks for the info. I had run the 4.03.605.2 RUU a couple of times, and also the latest official RUU that updated to 4.05.605.14 with the correct radios you listed. I have no idea what was going on, but my phone seemed to get worse every step. It would reboot, Wi-Fi quit, the 4G quit. It would go into a bootloop on the white HTC screen and wouldn't boot until I ran the RUU again. It finally went to that mode where it wouldn't boot at all until I charged the battery for a few hours. I figured it was hosed, and started browsing eBay for something new.
I finally ran the latest official RUU again and let it update OTA to the latest. I then did a factory reset under settings, then from the bootloader. I ran it stock for a day, then finally last night installed Amon RA and installed EclipticRez v9 and (fingers crossed) things seem to be back to normal.
I really wish I knew what happened, and I'm wondering if it could be battery related. I was sure it was something hardware related. Nothing I did for the couple of days before I first posted helped...
Weird...my phone wasn't that loopy...I've seen similar errors on other posts but if followed proper steps should work fine...I always read twice and flash once just to be safe instead of getting flash happy lol..I updated radios because signal and battery life was poor and read that jelly bean required the latest ruu...so I did tons of research
Sent from my L1QU1D H311H0UND using xda app-developers app
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
i cannot for the LIFE of me get a straight answer.
Do HTC devices lose the flash to another carrier (PagePlus) if I install a new rom or anything?
ShawnSnyder1991 said:
i cannot for the LIFE of me get a straight answer.
Do HTC devices lose the flash to another carrier (PagePlus) if I install a new rom or anything?
Click to expand...
Click to collapse
Naw. I'm also a fellow Page Plus user and I didn't lose my flash, even after the update to the bootloader. I did do it through Captains update instead of the official RUU I dunno if that makes a difference. I do know that if you're S-ON and you decide to run Moonshine or Runrunner to get S-OFF then you will lose your flash.
Shredder87 said:
Naw. I'm also a fellow Page Plus user and I didn't lose my flash, even after the update to the bootloader. I did do it through Captains update instead of the official RUU I dunno if that makes a difference. I do know that if you're S-ON and you decide to run Moonshine or Runrunner to get S-OFF then you will lose your flash.
Click to expand...
Click to collapse
so lemme get this straight, if i purchase the htc rezound, flash, then s-off, ill lose flash?
also, will this method work and still have flash?
http://unlimited.io/juopunutbear.htm
I would assume it's correct since it happened with my evo, so I would suggest s-off first, then proceed with flashing the phone. That method is a more complicated way of getting s-off and I believe they mentioned they only fully support it though linux.
Agree with Shredder. I recently flashed my Evo 4g lte to page plus and had the same problem when i did the FacePalm S-OFF routine. Lost my pageplus flash. Had to do the flash procedure again.
Later i realized i had to update the radio to install most kitkat ROMs.
Had to follow Captain_throwback's steps here for that.
http://forum.xda-developers.com/showthread.php?t=2639180
I thought i might loose the pageplus flash after this, but did not happen. My pageplus flash was intact after upgrading the radio version using the above. After upgrading the radio, yday i installed the Slimkat rom and everything is working as of now.
I have to mention i do not have 3g yet. Only voice and sms,
no 3g after S-OFF
srinia said:
Agree with Shredder. I recently flashed my Evo 4g lte to page plus and had the same problem when i did the FacePalm S-OFF routine. Lost my pageplus flash. Had to do the flash procedure again.
Later i realized i had to update the radio to install most kitkat ROMs.
Had to follow Captain_throwback's steps here for that.
http://forum.xda-developers.com/showthread.php?t=2639180
I thought i might loose the pageplus flash after this, but did not happen. My pageplus flash was intact after upgrading the radio version using the above. After upgrading the radio, yday i installed the Slimkat rom and everything is working as of now.
I have to mention i do not have 3g yet. Only voice and sms,
Click to expand...
Click to collapse
Same thing happened to me when I S-OFF. I only have voice and sms. MMS seems to only work on 3g which I only can get 1x. Let me know how you get 3gwhen you get it, because I tried everything I did before that got me 3g but no success this time.