First I must say that I have already fixed the problem. I flashed and RUU using step 8 and up on the DirtyRacun method and my phone us back to normal.
I'm S-off
HBOOT 1.15.2222
Originally had Venom 2.0.1 installed (error: i have 3.0.1)
Flashed Using TWRP 2.4.1.0
I did a full wipe before flashing. While I was flashing MeanBean 2.02 I think it just restarted without warning. When I tried going into TWRP again it wouldn't load, it would show the boot screen for a split second then reboot into bootloops. I tried fastboot flashing other version of TWRP but that didn't do anything.
From here I relocked and flashed my RUU accordingly with the DirtyRacun process. After unlocking my bootloader and flashing TWRP 2.3.1.0 I restored my old backup of Venom and I'm back to normal.
I checked the MD5 sums of the MeanBean ROM and they matched.
What the heck happen during the install?
Flash new radios now my phone is bricked and get teh DLOAD drivers on windows.
I'm gonna take a guess and say you flashed the latest firmware 3.16 without flashing the previous firmware update 3.15.
There is no radio only zip available from the latest OTA update for this very reason.
If this is the case your phone is unrecoverable . back to sprint
Sent from my EVO using xda premium
Shad Stang said:
First I must say that I have already fixed the problem. I flashed and RUU using step 8 and up on the DirtyRacun method and my phone us back to normal.
I'm S-off
HBOOT 1.15.2222
Originally had Venom 2.0.1 installed
Flashed Using TWRP 2.4.1.0
I did a full wipe before flashing. While I was flashing MeanBean 2.02 I think it just restarted without warning. When I tried going into TWRP again it wouldn't load, it would show the boot screen for a split second then reboot into bootloops. I tried fastboot flashing other version of TWRP but that didn't do anything.
From here I relocked and flashed my RUU accordingly with the DirtyRacun process. After unlocking my bootloader and flashing TWRP 2.3.1.0 I restored my old backup of Venom and I'm back to normal.
I checked the MD5 sums of the MeanBean ROM and they matched.
What the heck happen during the install?
Click to expand...
Click to collapse
u must have did something u wasnt suupposed to do cause meanbean would not hurt your phone in anyway bro
I second this, I am having issues as well.
Let this be a warning for others that may follow in your footsteps. You need to make sure you know what you are doing before you start flashing firmware. Firmware is meant to be upgraded one step at a time, not jumping from an old firmware to the latest, this will brick you phone in most cases. Please make sure you have verified your current firmware that you are on and upgrade to the next highest in sequence until you finally reach the newest. Also, the radio is just a part of the firmware, so if you did not upgrade the full firmware in the past then you need to go back and install the full firmware that you were on and then upgrade to each subsequent one. If you are s-on the only way to do this is to relock and take the OTA. For those that are s-off visit Captain Throwbacks thread in the development section and start reading and learning. You may find a solution in it.
Cruise was right, i thought i had the radio that came with 3.15 but i really had the radio that came with 1.22 XD.
Need to Update...not sure how!
cruise350 said:
Let this be a warning for others that may follow in your footsteps. You need to make sure you know what you are doing before you start flashing firmware. Firmware is meant to be upgraded one step at a time, not jumping from an old firmware to the latest, this will brick you phone in most cases. Please make sure you have verified your current firmware that you are on and upgrade to the next highest in sequence until you finally reach the newest. Also, the radio is just a part of the firmware, so if you did not upgrade the full firmware in the past then you need to go back and install the full firmware that you were on and then upgrade to each subsequent one. If you are s-on the only way to do this is to relock and take the OTA. For those that are s-off visit Captain Throwbacks thread in the development section and start reading and learning. You may find a solution in it.
Click to expand...
Click to collapse
(1) How do I know if I'm s-off or on?
(2) I keep getting an OTA update notification. Do I take this update? If so, once it downloads then what?
-Running MeanBean_1.7 (I know sooo...far behind. That's why I want to update)
-Android 4.1.1
-PRL 25012
-Kernel: [email protected] #1 SMP PREEMPT
BaseB - 1.12.11.1119
Build - 3.15.651.16 CL124461 release-keys
I just need a step by step process on how to update this thing. Video, tutorial. etc.
Thanks in advance!
KEMODREAMS said:
(1) How do I know if I'm s-off or on?
(2) I keep getting an OTA update notification. Do I take this update? If so, once it downloads then what?
-Running MeanBean_1.7 (I know sooo...far behind. That's why I want to update)
-Android 4.1.1
-PRL 25012
-Kernel: [email protected] #1 SMP PREEMPT
BaseB - 1.12.11.1119
Build - 3.15.651.16 CL124461 release-keys
I just need a step by step process on how to update this thing. Video, tutorial. etc.
Thanks in advance!
Click to expand...
Click to collapse
Unless you bought your phone used, you should know whether you are s-on or s-off since it is an involved process to get your phone s-off. What ota notices are you getting? Are they from the ota updater built in to MeanBean, or is it the HTC update?
If its the MeanBean update you can let it update and it should work just fine. Your firmware will not be up to date, but MeanBean will still work. If its HTC then don't take the update.
If you are s-off you can update you firmware with the file provided in the first post of the MeanBean thread.
If you are s-on, the only way to update your firmware is returning to stock, locking your bootloader, and taking the HTC ota update.
Sent from my icrap 2 using Tapatalk HD
cruise350 said:
Unless you bought your phone used, you should know whether you are s-on or s-off since it is an involved process to get your phone s-off. What ota notices are you getting? Are they from the ota updater built in to MeanBean, or is it the HTC update?
If its the MeanBean update you can let it update and it should work just fine. Your firmware will not be up to date, but MeanBean will still work. If its HTC then don't take the update.
If you are s-off you can update you firmware with the file provided in the first post of the MeanBean thread.
If you are s-on, the only way to update your firmware is returning to stock, locking your bootloader, and taking the HTC ota update.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
+1 if you boot into boot loader you will see whether you are s-off or not.
Sent from my Nexus 7 using xda app-developers app
Need to Update...not sure how!
ronniemayo said:
+1 if you boot into boot loader you will see whether you are s-off or not.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Ok so I did that and it says I'm s-on. Now what? Do I take the OTA update that says "This will update your ROM (MeanBean) to version MeanBean_3.06"? If so, once it's downloaded what do I do? Restart into bootloader? Also my Titanium backup is saying that it "could not acquire root privileges" What does that mean? Thanks for your help.
If you want to update meanbean then backup and flash the latest meanbean. If yours breaks like mine did, flash an ruu and dont be an idiot like me. im guessing it s a rare occurrence that mine broke the recovery
If your goal is to flash new radios then you have two options:
Two methods:
Get your adventure face on and follow the DirtyRacun S-Off process step by step (It worked for me on windows 7 x64 but its easy to use a ubuntu livecd)
Once you are s-off you can flash radios. DO NOT JUMP VERSIONS... EVER use the baseband version as reference in about phone and flash each version up until you are at the latest
OR
staying s-on and leaving yourself less prone to brick hell
recovery nandroid backup: system, data, boot
flash ruu
ota update
reroot
restore backup.
i dont know how to root from the latest version so idk if this is a good procedure. make sure you can root with the latest version
But really if you have a choice, ditch the evo and get the s3. you can firmware jump all you want, but the downside is that the s3 has sh*t roms. I miss venom and stock with goodies :crying:
Shad Stang said:
If you want to update meanbean then backup and flash the latest meanbean. If yours breaks like mine did, flash an ruu and dont be an idiot like me. im guessing it s a rare occurrence that mine broke the recovery
If your goal is to flash new radios then you have two options:
Two methods:
Get your adventure face on and follow the DirtyRacun S-Off process step by step (It worked for me on windows 7 x64 but its easy to use a ubuntu livecd)
Once you are s-off you can flash radios. DO NOT JUMP VERSIONS... EVER use the baseband version as reference in about phone and flash each version up until you are at the latest
OR
staying s-on and leaving yourself less prone to brick hell
recovery nandroid backup: system, data, boot
flash ruu
ota update
reroot
restore backup.
i dont know how to root from the latest version so idk if this is a good procedure. make sure you can root with the latest version
But really if you have a choice, ditch the evo and get the s3. you can firmware jump all you want, but the downside is that the s3 has sh*t roms. I miss venom and stock with goodies :crying:
Click to expand...
Click to collapse
You should read Captain _Throwback's firmware thread
You can root the latest OTA just click the link in my sig
Sent from my PoS MoPho
Related
The main question is the title - Should you S-off before or after the OTA?
I have seen people around the forums (via a few searches) say that it is likely a good idea to perform S-off before OTA because we didn't know for sure if the OTA would close the S-off exploit. Now that the OTA is a known quantity, is that still the best route?
My device is:
Stock rom and firmware (2.01.605.11)
Unlocked
AmonRA 3.15 recovery
Rooted
I'm a little nervous about doing S-off, but I figure it will be really handy to have it once its done, and I understand it really is no big deal. My end goal is to run the Venom rom and then move to AOKP/CM9 once they have most of the bugs worked out. Would my best course of action be to S-Off, run the firmware updater, reinstall recovery (probably TWRP, seems like that is the most popular one at the moment), then flash my rom of choice? Will I need to re-root if I switch to a different recovery?
UPDATE:
S-off is done and was no big deal, I got it on my third try. I selected to not install the jb_hboot during the process, since I'm doing RUU next.
The 3.14.605.12 RUU (from android police) was as simple as could be, I renamed the file to PH98IMG.zip and dumped it into my sd card, once I rebooted into the bootloader it was automatic from there
I got stuck on the "flash juopunut Bear hboot" part, I am using Hasoon2000's HTC Rezound ALL-In-One Kit and S-Off Toolkit. I thought I could just flash the hboot from this and be done... I learned that unless you have the jb_hboot (the latest vigor hboot from unlimited.io) installed you can't use ADB commands (which the toolkits use). The solution was very simple. I just renamed the jb_hboot to PH98IMG.zip, rebooted into the bootloader and it was installed.
TWRP v. 2.20 flashed, for some reason my phone doesn't charge while plugged in and booted into this recovery. I guess I need to make sure I have a nice charge if I want to do anything major.
Installed ViperRez rom 1.03, now I'm toying around with it
Originally Posted by AshtonTS
Originally Posted by YTHero
My device is:
Stock rom and firmware (2.01.605.11)
Unlocked
AmonRA 3.15 recovery
Rooted
I want to run a custom (like ViperRez or CM9) ICS rom with the OTA (3.14.605.12) updated firmware.
So my process will be:
S-Off -> flash Hboot/radio/firmware files from 3.14.605.12 -> flash juopunut Bear hboot -> flash TWRP -> Flash ICS rom
Is my plan correct in that I should flash juopunutBear hboot after I flash the Hboot/radio/firmware files from 3.14.605.12? If so why?
Is there anything else that I should do in between these steps that I haven't identified? Am I taking any unnecessary risks by doing it this way?
Click to expand...
Click to collapse
Yeah, flash the RUU, then the JBear hboot, then TWRP/Amon Ra, then a Rom
Click to expand...
Click to collapse
I would do it beforehand. Once you are s-off, you can flash the latest firmware without installing the whole RUU also.
But it limits from getting the actual ota which I love to see
Sent from my ADR6425LVW using xda app-developers app
I would do it before and then after you S-Off run through this PH98IMG RUU. From talks, this is the OTA.
http://forum.xda-developers.com/showthread.php?t=1810931
Then flash the patched 2.25.2525 JB hboot from http://unlimited.io/hboot-downloads/
EDIT:
Alternatively you could S-Off, flash latest radios and patched hboot, then flash a rom of your choosing based on 605.10 or 605.12.
I'm still going to wait to see if we can get s-off on ics before updating today as I don't have the wire to currently do the exploit.
Sent from my ADR6425LVW using xda app-developers app
All I am saying is this. Why wait for the OTA when their are already roms based off 605.10, barely anything changed from it to 605.12. Also, S-Off will stick as long as you make it stick.
why wait for the ota when the ota was leaked?
YTHero said:
The main question is the title - Should you S-off before or after the OTA?
I have seen people around the forums (via a few searches) say that it is likely a good idea to perform S-off before OTA because we didn't know for sure if the OTA would close the S-off exploit. Now that the OTA is a known quantity, is that still the best route?
My device is:
Stock rom and firmware (2.01.605.11)
Unlocked
AmonRA 3.15 recovery
Rooted
I'm a little nervous about doing S-off, but I figure it will be really handy to have it once its done, and I understand it really is no big deal. My end goal is to run the Venom rom and then move to AOKP/CM9 once they have most of the bugs worked out. Would my best course of action be to S-Off, run the firmware updater, reinstall recovery (probably TWRP, seems like that is the most popular one at the moment), then flash my rom of choice? Will I need to re-root if I switch to a different recovery?
Click to expand...
Click to collapse
You are on Gingerbread firmware, that's the first thing to recognize. There's lots of development tools that were designed AFTER the Gingerbread firmware (2.xx is GB; 3.xx is ICS). In fact Amon Ra 3.15 was the version done after the ICS leak (because mount points were changed).
So you can (and probably should) do the S-OFF using the GB version over at Juopunut's site and then either wait for the ICS OTA to come to your phone or flash it in bootloader as a PH98IMG.ZIP (the RUU is available via Android Police, 3.14.605.12 is the "official" ICS, and I'm pretty sure its here on XDA but I don't remember the thread.)
If you don't want to wait for the OTA, it doesn't matter whether you are S-ON or S-OFF, you'll still have to flash the RUU in hboot. Both will completely wipe your phone, and the S-OFF process will wipe your CARD so use a different card before you do it!
Finally, to reiterate what's all over by now: the "official" update, 3.14.605.12 is only marginally different than the unofficial leak that's been out since May, 3.14.605.10, and the radios, kernel and hboot are all the same.
hgoldner said:
So you can (and probably should) do the S-OFF using the GB version over at Juopunut's site and then either wait for the ICS OTA to come to your phone or flash it in bootloader as a PH98IMG.ZIP (the RUU is available via Android Police, 3.14.605.12 is the "official" ICS, and I'm pretty sure its here on XDA but I don't remember the thread.)
If you don't want to wait for the OTA, it doesn't matter whether you are S-ON or S-OFF, you'll still have to flash the RUU in hboot. Both will completely wipe your phone, and the S-OFF process will wipe your CARD so use a different card before you do it!
Click to expand...
Click to collapse
I recieved the OTA today from Verizon, but deferred to take until I figured out what I want to do. If I understand what you are saying:
S-Off -> OTA -> install TWRP -> then Flash ViperRez or whatever rom
Taking the OTA seems like the easiest and most straight forward way of upgrading to ICS radios/hboot. Will I need to do anything else before or following the OTA? I feel like somewhere I read that I will need to patch the hboot because I will be S-off.
YTHero said:
I recieved the OTA today from Verizon, but deferred to take until I figured out what I want to do. If I understand what you are saying:
S-Off -> OTA -> install TWRP -> then Flash ViperRez or whatever rom
Taking the OTA seems like the easiest and most straight forward way of upgrading to ICS radios/hboot. Will I need to do anything else before or following the OTA? I feel like somewhere I read that I will need to patch the hboot because I will be S-off.
Click to expand...
Click to collapse
After you s off, flash juopunutBears hboot it should be on his website
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
After you s off, flash juopunutBears hboot it should be on his website
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I'm trying to understand this post
http://forum.xda-developers.com/showpost.php?p=29715514&postcount=51
and this thread
http://forum.xda-developers.com/showthread.php?t=1614366
superchilpil said:
New firmware patch huh?
This is simply for those upgrading to ICS firmware on a GB rom Or and ICS rom that had the gingerbread patch flashed over it
Whats the difference between the stock Hboots and the JB/ENG Hboots?
Simply, These Hboots have fastboot commands enabled WITHOUT unlocking the bootloader
I suggest if you use fastboot alot to use these hboots
Click to expand...
Click to collapse
I'm just trying to figure out if I will have to reflash the juopunutBears hboot after I flash the Hboot/radio/firmware files from 3.14.605.12
So will it be:
S-Off -> Hboot/radio/firmware files from 3.14.605.12 -> juopunut Bear hboot ->install TWRP -> then Flash ViperRez or whatever ICS rom
YTHero said:
So will it be:
S-Off -> Hboot/radio/firmware files from 3.14.605.12 -> juopunut Bear hboot ->install TWRP -> then Flash ViperRez or whatever ICS rom
Click to expand...
Click to collapse
You got it right on.
Sent from my ADR6425LVW using xda app-developers app
This is going to be a short and simple guide for S-OFF users that want to update to the current RUU level or refresh their phone because they are having issues like being unable to boot certain ROM's. You will not lose S-OFF by flashing the RUU.
1. Do a nandroid backup of your current ROM if you want to restore it later.
2. Download the current version of the RUU for your phone in exe or zip format from this page.
3. Run the exe version of the RUU in Windows or the zip version as a PG86IMG.zip file through the bootloader. If using the bootloader method make sure the file is named exactly "PG86IMG.zip" and placed in the root of your SD card before starting the bootloader.
There is no need to unlock the bootloader before running it if you are S-OFF and there is troubleshooting information in this post if you have problems. It may be necessary to run the RUU twice if you have a custom bootloader installed when it is run the first time. If the utility hangs after flashing the bootloader from Windows just cancel it and restart.
I recommend downloading and installing the OTA(s) immediately after flashing the RUU to get the most current firmware while still 100% stock, but the OTA firmware update(s) can be downloaded as a separate PG86IMG.zip file if you forget or can't do that for some reason.
4. Flash a custom hboot using the instructions in this post. My recommendation for a good general purpose hboot is the JBear GB 1.50.5050 version unless you are running an ICS Sense ROM like stock or Cool ICS that requires an ICS bootloader (1.57.xxxx or 1.58.xxxx).
5. Connect your phone to a PC and start the bootloader in "fastboot USB " mode, then issue the following command to flash your favorite recovery:
fastboot flash recovery recovery.img (where "recovery.img" is the name of the recovery file in your ADB/fastboot directory)
6. Boot into recovery and restore a nandroid or flash another custom ROM. You may have to wipe cache+dalvik and restart recovery if you get any error messages from the recovery program.
That's it. You're now updated or re-synced with the current firmware, the hboot that meets your requirements and your favorite recovery.
Here are some additional links that might be helpful:
4EXT Recovery OP for the Evo 3D CDMA thread with a direct link to recovery.img in the download section (not the most current version)
Current TeamWin (TWRP2) touch recovery for the CDMA Evo 3d.
Virgin Mobile OTA firmware only in PG86IMG.zip format.
Sprint OTA firmware only in PG86IMG.zip format.
ramjet73
Thanks for this.
Question,the RUU links...
Am I looking for the link with the radio he has currently on his phone?
0.97.10.0530?
3volution said:
Thanks for this.
Question,the RUU links...
Am I looking for the link with the radio he has currently on his phone?
0.97.10.0530?
Click to expand...
Click to collapse
No. That's an older GB level and the most current RUU for the Evo 3D is the 2.89.651.2 ICS version. That's the one I recommend.
Since he is S-OFF already it's easy to revert to a GB RUU if neccessary.
ramjet73
I better not mess with it,lol
This isn't anything like flashing new ROM's on my phone.
Thanks though.
3volution said:
I better not mess with it,lol
This isn't anything like flashing new ROM's on my phone.
Thanks though.
Click to expand...
Click to collapse
You're welcome.
It's not really that difficult if you are familiar with rooting and flashing HTC devices but I can understand how it might be for users coming from other brands. Samsung in particular is definitely less complicated.
ramjet73
Thanks!
Thanks for this great post ramjet. Really a great concise How-to.
Nevermind, fixed.
ramjet73 said:
No. That's an older GB level and the most current RUU for the Evo 3D is the 2.89.651.2 ICS version. That's the one I recommend.
Since he is S-OFF already it's easy to revert to a GB RUU if neccessary.
ramjet73
Click to expand...
Click to collapse
I flashed the above RUU .exe and I'll get to 10%, then my phone reboots (RUU program says "attaining bootloader" or something) and go into a bootloop. Is there a specific hboot necessary to run this. I am on 1.04.200 and s-off, 1.09.00.706
I also tried updating via the bootloader method as well..... runs well....updates like four of the ten check offs and then bootloops as well.
Edit: turns out I was flashing the wrong version, oops
Hedied4me said:
I flashed the above RUU .exe and I'll get to 10%, then my phone reboots (RUU program says "attaining bootloader" or something) and go into a bootloop. Is there a specific hboot necessary to run this. I am on 1.04.200 and s-off, 1.09.00.706
Click to expand...
Click to collapse
From experience I've discovered that the RUU.exe utility will sometimes stop after flashing the stock bootloader if it is run with a custom hboot installed, which is why I put this comment in the OP:
If the utility hangs after flashing the bootloader from Windows just cancel it and restart.
Click to expand...
Click to collapse
I've had no problem completing the RUU.exe flash if I just cancel the utility in the Windows task manager and restart it.
Others have reported that re-flashing the RUU.zip file through the bootloader also works if the original flash is incomplete.
Also, make sure that you downgrade your hboot after flashing the RUU since the stock hboot won't boot GB or AOSP based ROM's.
ramjet73
Ok one more stupid question, after successfully flashing the correct RUU my phone boots into the stock virgin mobile. How do I get into bootloader (to flash OTA update and hboot) from here since holding power and volume down button from off no longer work.
Sent from my HTCEVOV4G using Tapatalk 2
Hedied4me said:
Ok one more stupid question, after successfully flashing the correct RUU my phone boots into the stock virgin mobile. How do I get into bootloader (to flash OTA update and hboot) from here since holding power and volume down button from off no longer work.
Click to expand...
Click to collapse
Try removing/replacing the battery and then use the Power+VolumeDown buttons together to enter the bootloader.
The stock ROM has the "fast boot" option turned on in the power settings by default and that will interfere if you try to enter the bootloader after powering down from the stock ROM.
ramjet73
Thank you very much for your patience and help Ramjet. Everything went well.
Sent from my Evo V 4G using Tapatalk 2
Please excuse me this might have been asked before.
I'm currently S-Off H-boot 1.40 but still on gingerbread firmware(2.17 radio 0.97.10.0530). also flashed to Boost Mobile. My question is if I run RUU to newest build will I lose boost mobile flash?
El Queson said:
Please excuse me this might have been asked before.
I'm currently S-Off H-boot 1.40 but still on gingerbread firmware(2.17 radio 0.97.10.0530). also flashed to Boost Mobile. My question is if I run RUU to newest build will I lose boost mobile flash?
Click to expand...
Click to collapse
I honestly don't know.
There is a post by a cricket user in my rooting and S-OFF guide that says the customization is not lost for that carrier but I've never used Boost and can't speak to that.
Perhaps another Boost user on these forums has experience with flashing the RUU.
ramjet73
++sorry++
Using the bootloader procedure is, by far, the easiest way of doing the RUU process that I've encountered. From custom ROM, to stock, back to a custom ROM in less than 45 minutes.
ramjet, thank you for your contributions to our platform.
so my wife is hboot 1.40, radio version 0.97.... running a GB ROM. I need to update her EVERYTHING(you pointed me here) and get her on NegaLite BluROM. I believe I will need to update her hboot as well. At what point in this process should that be done? Do I need to be worried that her current ROM is incompatible with either the new RUU or the new bootloader? And if it is, then I just work through it all in recovery?
Very useful thread, and thank you very much, by the way.
GAPO said:
so my wife is hboot 1.40, radio version 0.97.... running a GB ROM. I need to update her EVERYTHING(you pointed me here) and get her on NegaLite BluROM. I believe I will need to update her hboot as well. At what point in this process should that be done? Do I need to be worried that her current ROM is incompatible with either the new RUU or the new bootloader? And if it is, then I just work through it all in recovery?
Very useful thread, and thank you very much, by the way.
Click to expand...
Click to collapse
Is her phone S-OFF? If so, there is a link in the OP to a post that covers updating the hboot. If not, the only way to update the hboot is to flash a more current RUU.
ramjet73
ramjet73 said:
Is her phone S-OFF? If so, there is a link in the OP to a post that covers updating the hboot. If not, the only way to update the hboot is to flash a more current RUU.
ramjet73
Click to expand...
Click to collapse
Yes she is S-off. She also already has 4ext recovery installed.
Does this negate my need to flash recovery in the downloader?
Since she is S-off, this should be pretty easy.
I will still need to access the bootloader via Windows cmd, yes? Or can I accomplish all of this using only the handset?
Sent from my PG86100 using xda premium
---------- Post added at 07:07 PM ---------- Previous post was at 06:52 PM ----------
Her hboot is:
SHOOTER XC SHIP S-OFF RL
HBOOT-1.40.0000
RADIO-0.97.10.0530
eMMC-boot
Jun 8 2011, 17:20:22
Is this a custom hboot, or stock? I ask because of the caution on the OP regarding custom bootloaders. And I am not sure because I changed her bootloader a week or so ago and had to change it back.
Sent from my PG86100 using xda premium
GAPO said:
Is this a custom hboot, or stock? I ask because of the caution on the OP regarding custom bootloaders. And I am not sure because I changed her bootloader a week or so ago and had to change it back.
Click to expand...
Click to collapse
That's a stock hboot so you should be fine. You can still update using the RUU if a custom hboot is installed, but it might take a restart to complete after the stock hboot is installed.
ramjet73
I'd like to update to the new Stock ROM with Goodies- Questions....
1. Hotspot work on this ROM?
2. What firmware/Radio do I need for this or does any of that get updated automatically?
3. Is there a walk through instruction/video for this update...from such an old ROM?
I have:
Hboot 1.12.0000
S-on
Radio 1.02.12.0427
TWRP 2.1.8
Well to start you need to decide if you want to s- off or not. If you don't i believe you can update firmware with the 1.12 hboot.
I'd update the firmware in consecutive order from where you are now. You want the firmware zips without the hboot img
Then you can flash the new rom you want.
I would follow the directions for s- off personally. It makes things alot easier
Sent from my EVO using xda premium
NaterTots said:
Well to start you need to decide if you want to s- off or not. If you don't i believe you can update firmware with the 1.12 hboot.
I'd update the firmware in consecutive order from where you are now. You want the firmware zips without the hboot img
Then you can flash the new rom you want.
I would follow the directions for s- off personally. It makes things alot easier
Sent from my EVO using xda premium
Click to expand...
Click to collapse
If I turn the device into s-off, then I can use TWRP to update from zip files right?
I read that I don't want to jump firmware to the latest or I could brick the device. So I thought the process might look like this.
PLEASE CORRECT ME IF I'M WRONG:
1. LazyPanda ( http://forum.xda-developers.com/showthread.php?t=1737123 )
to "s-off" the device
2. Run zip for 2.13.651.1 OTA (which one though?)
....Reboot THEN
run zip for 3.16.651.3 OTA
So I don't brick it
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
3. Install Stock ROM with Goodies...
Am I missing something?
What about the radio (comes with the firmware?)? What's the deal with the boot.img or not (I don't see the firmware WITHOUT boot.img included)?
Lazy panda is not technically supported anymore, so not sure how much luck you'll have there, but I would say run the 3.15 RUU, then s-off with dirty racun .
Stock with goodies is using the 3.16 base, so once you're s-off you can update to that firmware/radio version via the bootloader...assuming you're coming from 3.15. Just make sure to flash the 3.16 zip without the tp img, or your touch screen won't work with any other base.
http://forum.xda-developers.com/showthread.php?t=1704612
Sent from my EVO LTE
premo15 said:
Lazy panda is not technically supported anymore, so not sure how much luck you'll have there, but I would say run the 3.15 RUU, then s-off with dirty racun .
Stock with goodies is using the 3.16 base, so once you're s-off you can update to that firmware/radio version via the bootloader...assuming you're coming from 3.15. Just make sure to flash the 3.16 zip without the tp img, or your touch screen won't work with any other base.
http://forum.xda-developers.com/showthread.php?t=1704612
Sent from my EVO LTE
Click to expand...
Click to collapse
OK. let me revise then
1. S-off through RUU 3.15, then use Dirty Racun
2. Then update through TWRP (do I need a specific version or do I HAVE to use the Hboot?) to 3.15, then reboot and change to 3.16 (without tp.img in it)
3. install new ROM stock with goodies 3.16
Do I have it now?
(sigh...my Sprint Epic 4G first gen, and my wife's Galaxy Note 2 are SOOO much less complicated than HTC stuff)
ZenInsight said:
OK. let me revise then
1. S-off through RUU 3.15, then use Dirty Racun
2. Then update through TWRP (do I need a specific version or do I HAVE to use the Hboot?) to 3.15, then reboot and change to 3.16 (without tp.img in it)
3. install new ROM stock with goodies 3.16
Do I have it now?
(sigh...my Sprint Epic 4G first gen, and my wife's Galaxy Note 2 are SOOO much less complicated than HTC stuff)
Click to expand...
Click to collapse
That's what I was saying in another thread. With samsung phones you just flash and reboot. With these HTC phones you have to update this downgrade that just to flash a rom. I came from a one X and you had to flash the boot.img every time you wanted to flash a rom/kernel/modem.
Sent from my SAMSUNG-SGH-I717
No. Dont s-off then run dirty racun. S-off is what dirty racun does. He's saying Use RUU to get to 3.15, THEN use dirty racun (as per their instructions).
Then STAY at 3.15. Uncles you wanna use a 3.16 sense ROM (which is no different than a 3.15 ROM). If you S-off and update to 3.16 firmware AND flash the 3.16 touch panel image (tp.IMG), you will not be able to use any ROMs that aren't sense 3.16. I would suggest leaving your firmware where it is, and try the ROM you want. Generally, you DO NOT need current firmware to run a current ROM. The two are mutually exclusive (firmware and ROM). I always rock old radios. Newer isn't always better.
From my Evo LTE, yup.
1. S-OFF with DirtyRacun (doesn't really matter which RUU you choose)
2. Install custom recovery through fastboot (latest TWRP should be fine, depending on the ROM you choose - you might need 2.4.0.0 or older if flashing a ROM with an outdated update binary)
3. Flash ROM of your choice.
4. Update to latest firmware using most recent zip from firmware thread (this is done through the bootloader, not recovery)
5. Profit.
I feel pretty stupid with how confusing this is.
So
1. Use dirty Racun to go to s-off
2. I already have TWRP 2.1.8 for installing zip updates (Can I leave that version or do I need to change it?),,,
3. Install 3,15 firmware (or install 3.16 but without the tp img or my touchscreen in recovery will be busted.
Also, once I go to 3.16 I can only use 3.16 ROMS in the future.
4. Install any ROM which automatically changes me to the latest radio (is that true?).
I want this one:
http://forum.xda-developers.com/showthread.php?t=1701117
but does that mean I HAVE to have 3.16 firmware to use a 3.16 ROM? Or can I just leave it at 3.15?
ZenInsight said:
I feel pretty stupid with how confusing this is.
So
1. Use dirty Racun to go to s-off
2. I already have TWRP 2.1.8 for installing zip updates (Can I leave that version or do I need to change it?),,,
3. Install 3,15 firmware (or install 3.16 but without the tp img or my touchscreen in recovery will be busted.
Also, once I go to 3.16 I can only use 3.16 ROMS in the future.
4. Install any ROM which automatically changes me to the latest radio (is that true?).
I want this one:
http://forum.xda-developers.com/showthread.php?t=1701117
but does that mean I HAVE to have 3.16 firmware to use a 3.16 ROM? Or can I just leave it at 3.15?
Click to expand...
Click to collapse
2. The S-OFF process involved flashing an RUU, which will replace TWRP with the stock recovery. So like I said, you will need to flash TWRP. Since I don't know if flex has updated the update binary in that ROM, I would flash TWRP 2.4.0.0.
3. Just flash the 3.16 firmware. I've taken out anything that would be of concern, so you can flash whatever ROMs you want.
4. Radio is part of the firmware.
Captain_Throwback said:
2. The S-OFF process involved flashing an RUU, which will replace TWRP with the stock recovery. So like I said, you will need to flash TWRP. Since I don't know if flex has updated the update binary in that ROM, I would flash TWRP 2.4.0.0.
3. Just flash the 3.16 firmware. I've taken out anything that would be of concern, so you can flash whatever ROMs you want.
4. Radio is part of the firmware.
Click to expand...
Click to collapse
Ok. I get it. I lose TWRP once I "s-off", so I have to put it back on.
Just flash 3.16...it doesn't matter anymore about the touchscreen, that's been fixed.
Radio is included in the 3.16 firmware, not the ROM.
Flash the Stock with goodies...and I'll be fine.
Phew.... I hope this is right.
Do not flash 3.16 firmware if you haven't already flashed 3.15 first. Will brick.
From my Evo LTE, yup.
scottspa74 said:
Do not flash 3.16 firmware if you haven't already flashed 3.15 first. Will brick.
From my Evo LTE, yup.
Click to expand...
Click to collapse
No, it won't. Otherwise I would've said so. You obviously haven't been reading the firmware thread .
scottspa74 said:
Do not flash 3.16 firmware if you haven't already flashed 3.15 first. Will brick.
From my Evo LTE, yup.
Click to expand...
Click to collapse
Funny you say that since 3.15 firmware was causing soft bricks with older hboots. The only problem with the latest update is that aosp roms are stuck with out touch screen support for now.
Captain_Throwback said:
No, it won't. Otherwise I would've said so. You obviously haven't been reading the firmware thread .
Click to expand...
Click to collapse
Alright. Guess I missed something. Last time I was in there , if you didn't do 3.15 prior to 3.16 you were hosed.
But I did see the firmware haus dropped that it was said would be OK regardless of 3.15 or not. Just hadn't seen anyone try it.
Definitely listen to Cap'n. He's the man when it comes to firmwares and radios.
From my Evo LTE, yup.
Okay, I wish I had read this before I did what I just did. My device seems to be bricked
Was running 1.22.651.3 and MeanROM-ICS-v65 and went to update things to JB. Updated using PJ75IMG_3.16.651.3_firmware in HBOOT and now the screen won't turn on and none of the LEDs light up when plugged in. The device manager shows QHSUSB_DLOAD when it's plugged into the PC.
Any way to unbrick this?
(insert obligatory "I feel like an idiot for not doing more reading on here ahead of time" statement)
Trioculus said:
Okay, I wish I had read this before I did what I just did. My device seems to be bricked
Was running 1.22.651.3 and MeanROM-ICS-v65 and went to update things to JB. Updated using PJ75IMG_3.16.651.3_firmware in HBOOT and now the screen won't turn on and none of the LEDs light up when plugged in. The device manager shows QHSUSB_DLOAD when it's plugged into the PC.
Any way to unbrick this?
(insert obligatory "I feel like an idiot for not doing more reading on here ahead of time" statement)
Click to expand...
Click to collapse
Did you not download the most recent firmware from my thread? Because there's no way it should've bricked you. I personally updated from 1.22 firmware up to 3.16 with no issues, and someone else updated from 1.13 firmware up to 3.16. What exact file did you use?
EDIT: I just looked, and I don't even have a file available with that name in my thread (anymore). The only one I have is this, which is the extended firmware which eliminates the bricking issue. Sounds like you had an old download.
Captain_Throwback said:
What exact file did you use?
Click to expand...
Click to collapse
I used the one linked to from the wiki page: http://d-h.st/9L9 PJ75IMG_3.16.651.3_firmware.zip
Any way to fix this? Thanks for your help
Trioculus said:
I used the one linked to from the wiki page: http://d-h.st/9L9 PJ75IMG_3.16.651.3_firmware.zip
Any way to fix this? Thanks for your help
Click to expand...
Click to collapse
Ouch. I'll have to update the Wiki. I'll be sure to mention it to Haus.
And no, your device is bricked. Time to get a replacement.
EDIT: Wiki updated with proper link.
Captain_Throwback said:
Ouch. I'll have to update the Wiki. I'll be sure to mention it to Haus.
And no, your device is bricked. Time to get a replacement.
EDIT: Wiki updated with proper link.
Click to expand...
Click to collapse
ouch..That sucks, man.
Hi I just updated my htc evo 4g 3d from Sprint to 2.95 via ota and after that i cannot use wifi at all it just says error. please Help!!!!
b0235g10d said:
Hi I just updated my htc evo 4g 3d from Sprint to 2.95 via ota and after that i cannot use wifi at all it just says error. please Help!!!!
Click to expand...
Click to collapse
You probably took the update and tried to install it with a custom recovery installed. If so, it appears that will result in a partially installed update with the ROM updated and the kernel not being flashed, which causes WiFi errors.
If that's your situation the best thing to do is flash a stock rooted ROM if that is what you were using prior to taking the OTA.
ramjet73
ramjet73 said:
You probably took the update and tried to install it with a custom recovery installed. If so, it appears that will result in a partially installed update with the ROM updated and the kernel not being flashed, which causes WiFi errors.
If that's your situation the best thing to do is flash a stock rooted ROM if that is what you were using prior to taking the OTA.
ramjet73
Click to expand...
Click to collapse
Can you please give me the official ics 2.89 rom or find it please?
b0235g10d said:
Can you please give me the official ics 2.89 rom or find it please?
Click to expand...
Click to collapse
You can find a rooted version in this post.
ramjet73
ramjet73 said:
You can find a rooted version in this post.
ramjet73
Click to expand...
Click to collapse
I found this thread because I'm in a similar situation. I tried downloading from the quoted link and using 4eXT recovery to load the zip file from sd card and it says "installation aborted".
Any ideas on what to try next? My eventual goal is to get back to 100% showroom stock non-rooted, locked booloader, so that the phone will accept OTA updates fully. Modding/ROMing is a drug I experimented with, and am now ready to go back to the straight and narrow. I'd prefer the phone not have any scars whatsoever from my old habits.
Additional background:
Started with ICS OTA. Used HTC unlock to unlock bootloader. Coworker installed rom toolbox, superSU and 4eXT recovery (not sure what order) to get SOS rom up and running. Never did go for S-OFF.
Decided I wanted to return to 100% Sprint factory stock. Coworker promptly moved across country, leaving me to figure this out. Tried using several ROMs from XDA and elsewhere, and eventually ended up with a rooted almost stock ROM, but had to flash my own radios via 4eXT, as wifi and 4G weren't working from the rom. Flashing my own radios via 4eXT, got to 2.89 with then current radios.
While sitting in my hotel travelling abroad with no international data plan and super slow hotel wifi, I foolishly downloaded OTA this morning, promptly killing my phone's wifi. Phone is still rooted with 4eXT, superSU, installed on it if that helps.
ramjet73 said:
You can find a rooted version in this post.
ramjet73
Click to expand...
Click to collapse
I just did this yesterday (Thanks to ramjet for pointing it out). Backup first. It dose a factory reset. You also need to install the blue tooth fix from this post after flashing the ROM http://forum.xda-developers.com/showpost.php?p=29707708&postcount=303
fixed thanks
Hi to all
I just fixed my phone thanks to Mr ramjet and I used the last one because I completely formatted my phone and only had 4ext it takes while to load the first time but be patient and it will work
How about S-Off phones?
Hello... so my fiance' has a Virgin Mobile Evo 3D. I downloaded the update from them and tried to install it through the custom recovery. It did what Ramjet said by updating the ROM and not the Kernel. I now have no wifi,it says wifi error when trying to turn it on. Since then, I have made sure the stock ROM was rooted, and have also HTCDev unlocked the device as well as S-Off with the Junobear wire trick and Linux. Now that I'm S-Off, is it ok to use an RUU to downgrade everything? Just wondering before I go any further and brick the device or screw up something I shouldn't. I figure it's better to ask questions first before doing it lol! Any help is greatly appreciated from anybody! I have my specs listed here for you all:
HTC Evo 3D 4G Virgin Mobile
Mods: Rooted,HTCDev Unlocked, S-Off
JuopunutBear
Shooter XC SHIP S-OFF RL
HBOOT: 1.57.5757
Radio: 1.09.00.0706
Android Version 4.0.3
Sense Version 3.6
Software number 2.95.652.5 710RD
Kernel Version: 3.0.16-g4211684
[email protected] #1
SMP PREEMPT
Baseband Version:1.09.00.0706
Build Number: 2.95.652.5 CL560640 release-keys
EDIT: Problem has been fixed and I will post a new thread on how to fix the problem soon.
PS4AndroidHacker said:
EDIT: Problem has been fixed and I will post a new thread on how to fix the problem soon.
Click to expand...
Click to collapse
Was this new thread ever made because I am a Virgin Mobile user too just like the above user and ever since last update my wireless has stated error.
If ur phone's bootloader is unlocked, relock your phone by using the fastboot command "fastboot oem lock". Then just download the 2.89 RUU.exe. (i know ur on 2.95 but i have not seen the 2.95 ruu floating around hgere yet) Run it on a windows PC and follow the prompts and it should flash correctly on your phone (caution, it will erase everything on your phone). Once its flashed, the phone will reboot (sometimes more than once) just let it do its thing
Once the phone has flashed correctly, do a software update and it will update to 2.95
Worked for me when i had to go back to stock in order to return it for warranty when the digitizer went out
EDIT:
Here is the link to the 2.95 OTA http://d-h.st/vUe
Download to your PC, then unzip it, and run it after you have relocked your phone
Should you need them, here is the list of HBOOTS (thanks to ramjet73) http://forum.xda-developers.com/showthread.php?p=29844945#post29844945
sixty9fordkiller said:
If ur phone's bootloader is unlocked, relock your phone by using the fastboot command "fastboot oem lock". Then just download the 2.89 RUU.exe. (i know ur on 2.95 but i have not seen the 2.95 ruu floating around hgere yet) Run it on a windows PC and follow the prompts and it should flash correctly on your phone (caution, it will erase everything on your phone). Once its flashed, the phone will reboot (sometimes more than once) just let it do its thing
Once the phone has flashed correctly, do a software update and it will update to 2.95
Worked for me when i had to go back to stock in order to return it for warranty when the digitizer went out
EDIT:
Here is the link to the 2.95 OTA http://d-h.st/vUe
Download to your PC, then unzip it, and run it after you have relocked your phone
Should you need them, here is the list of HBOOTS (thanks to ramjet73) http://forum.xda-developers.com/showthread.php?p=29844945#post29844945
Click to expand...
Click to collapse
This sounds hopeful, I did try to install this before with no luck, it gave me a 131 custom id error. I did it relocked and I am currently 2.95.652.5, and S-ON.
any suggestions?
Thanks
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