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
ooooook...this'll either get me killed or contented.
here goes.
the first part of this i basically stole from sullivan's post over at mik's.
there was no answer to his question...
there are too many guides, tutorials and suggested methods that I can't chose the right one to narrow it down...
i'm asking the same manner of question...
<<<<<
EVO 3d
sprint
-Revolutionary-
SHOOTER XC SHIP S-OFF RL
HBOOT 1.40.1100
RADIO-1.06.00.1216
eMMC-boot
Jun 8 2011,17:20:22
hardware 002
running smooth criminal (chose a random sense rom to update pri.prl)
kernel version is 3.0.50-ck1 butteredtoast ics rls 12.2+
Build # is 2.89.651.2 CL409645 release-keys
PRI Version 1.42_003
PRL Version 21090
i used htc unlock and closeone's toolkit.
was using mikvirgin for a while. vm leak without problems. couldn't update pri.prl
changed a few things here and there...then, i started having heat and drain issues. notably from browsing and swype beta.
figured it was time for a clean slate and new rom.
From what I've gathered I need an ics hboot, ie, 1.58 in order to run ics kernels the right way??
What should i do to be current??
start by updating my radio. (where's the latest file?)
should i upgrade hboot? 1.58?
Do I need to relock, ruu, then unlock again? (what method is most recent and where)
i thought i read that i can just change my hboot on its own and then also bootload the latest radio?
ideally, i'd love to be able to run a few aosp jb roms...cm 10...as well as any ics roms without issue.
also, is the deal with ext3 versus ext4 still the same? ext4 can't run sense roms...or, was that only for the evo4g?
>>>>>>>>>>>>>
advice would be considered a thankable and appreciated offense!
many, many thanks, everyone.
i need to head to bed.
clear my brain a bit.
between ramjet's and mpgrimm2's threads...i'm going into overload.
but, thanks. seriously. you guys rock.
--------------------------------------------------------------
what? you think just cause a guy reads comics he can't kick some a$$?
I would relock the bootloader and run the Sprint ICS ruu.exe. This will update you to the latest firmware, radio, hboot, etc, but you'll still be s-off. Then downgrade your hboot to 1.4 or 1.04 and install a custom recovery like 4ext. You should then be ready to install a custom Rom.
coal686 said:
I would relock the bootloader and run the Sprint ICS ruu.exe. This will update you to the latest firmware, radio, hboot, etc, but you'll still be s-off. Then downgrade your hboot to 1.4 or 1.04 and install a custom recovery like 4ext. You should then be ready to install a custom Rom.
Click to expand...
Click to collapse
i'm thinking running the ruu might be the way to go, too.
(if anyone would like to point me in the direction of the latest ruu "how-to" thread...much appreciated)
however, i'm not quite sold on the idea of downgrading hboot back to what i have (or, another 1.4 variation).
as per ramjet's thread on the subject...even the most flexible hboot "eng hboot" has issues with compatibility running 2.89 based kernels.
the ones that run ics and above are the 1.58 hboots and it's variables.
so, anyone have ideas as to what my specs should be to successfully run a cm 10 based rom and kernel successfully?
not to mention that i'd like to continue to swap into a sense based rom every now and again.
that leads me back to the ext3 vs ext4 question.
is ext4 still not a viable ext for sense based roms or was that only for the evo 4g?
thanks again, coal!
cipher77 said:
i'm thinking running the ruu might be the way to go, too.
(if anyone would like to point me in the direction of the latest ruu "how-to" thread...much appreciated)
however, i'm not quite sold on the idea of downgrading hboot back to what i have (or, another 1.4 variation).
as per ramjet's thread on the subject...even the most flexible hboot "eng hboot" has issues with compatibility running 2.89 based kernels.
the ones that run ics and above are the 1.58 hboots and it's variables.
so, anyone have ideas as to what my specs should be to successfully run a cm 10 based rom and kernel successfully?
not to mention that i'd like to continue to swap into a sense based rom every now and again.
that leads me back to the ext3 vs ext4 question.
is ext4 still not a viable ext for sense based roms or was that only for the evo 4g?
thanks again, coal!
Click to expand...
Click to collapse
This post was for a user in a situation similar to yours. It's basically what coal suggested and you can use my guide through Step2, but there is no need to relock the bootloader since you are S-OFF.
If your case, you might want to flash the ENG or JBear 1.50.5050 bootloader after running the RUU.exe since both of those will flash and run GB, ICS and JB ROM's except for a few Sense ROM's that require the stock 1.58 or JBear 1.58.5858 bootloader.
As far as EXT3 versus EXT4 goes, most current Sense and AOSP ROM's support both, but I usually just "format all partitions except SD card" in 4EXT recovery before flashing a ROM and let it default to that (EXT4) or whatever format the dev configured for the ROM. I just checked the nandroids on my SD card and they are all in the EXT4 format.
ramjet73
IMO, you should just update your radio (if you can find the latest PG86IMG.zip) or get the one from virus's thread which contains the latest hboot too. Then to install CM10 ROM downgrade back to eng hboot or 1.4 you should be able to run CM10 ROMs just fine. And if you want sense 3.6 ROM, you can try smoothcriminal ROM after updating your radio. It works with all hboots.
RUU vs OTA vs firmware zip file
mnomaanw said:
IMO, you should just update your radio (if you can find the latest PG86IMG.zip) or get the one from virus's thread which contains the latest hboot too. Then to install CM10 ROM downgrade back to eng hboot or 1.4 you should be able to run CM10 ROMs just fine. And if you want sense 3.6 ROM, you can try smoothcriminal ROM after updating your radio. It works with all hboots.
Click to expand...
Click to collapse
There's some good information about flashing an RUU versus taking an OTA in this thread on the HTC Desire forum, and flashing the firmware zip updates even less than taking the OTA. I've attached screen shots of the contents of virus's firmware zip file versus the RUU rom.zip file from the same build (Sprint ICS 2.89.651.2). As you can see, even discounting the boot, system, and data partitions, there's more that gets updated with the RUU than what's contained in the firmware .zip, which is why I recommend starting with an RUU flash (.exe or .zip) when upgrading to a new build.
ramjet73
ramjet73 said:
There's some good information about flashing an RUU versus taking an OTA in this thread on the HTC Desire forum, and flashing the firmware zip updates even less than taking the OTA. I've attached screen shots of the contents of virus's firmware zip file versus the RUU rom.zip file from the same build (Sprint ICS 2.89.651.2). As you can see, even discounting the boot, system, and data partitions, there's more that gets updated with the RUU than what's contained in the firmware .zip, which is why I recommend starting with an RUU flash (.exe or .zip) when upgrading to a new build.
ramjet73
Click to expand...
Click to collapse
Although mnomaanw makes a great point, I agree with ramjet on this one. My phone recently decided not to let me install ANY CM, GB, or JB based ROMs. The only ones that would successfully boot were Sense 3.6 and 4.0 based ICS ROMs. The rest would show my splash screen and then the phone would bootloop before even the boot ani showed. I tried to flash different radios, hboots, firmware, etc to no avail. Finally, I ran the ruu.exe, downgraded my hboot to 1.4 Revolutionary to try the MIUI ROM everyone is raving about and installed 4ext custom recovery. Everything is running great now.
I can confirm that it does more than just the firmware zip updates as it wiped my custom splash screen I had installed. Going through the hassle of running the ruu is worth it if you want to be sure that everything is completely updated properly.
ramjet73 said:
This post was for a user in a situation similar to yours. It's basically what coal suggested and you can use my guide through Step2, but there is no need to relock the bootloader since you are S-OFF.
If your case, you might want to flash the ENG or JBear 1.50.5050 bootloader after running the RUU.exe since both of those will flash and run GB, ICS and JB ROM's except for a few Sense ROM's that require the stock 1.58 or JBear 1.58.5858 bootloader.
As far as EXT3 versus EXT4 goes, most current Sense and AOSP ROM's support both, but I usually just "format all partitions except SD card" in 4EXT recovery before flashing a ROM and let it default to that (EXT4) or whatever format the dev configured for the ROM. I just checked the nandroids on my SD card and they are all in the EXT4 format.
ramjet73
Click to expand...
Click to collapse
first off...
huge, huge thanks for the responses, guys.
so, yeah...i've actually been using 4ext as my recovery for a while now. i have to say...it's quite good.
however, i always have wondered what the deal was with ext3 vs ext4. clearing that up more definitively than what i've been able to find on my own, as well as my own experiences, is great.
sounds like i'll be running the ruu executable.
just to confirm...already being s-off means that i don't have to relock my bootloader, yeah?
excellent. one less step.
as for the hboot...this seems to be where it gets tricky.
ramjet...you suggested downgrading hboot after the ruu flash to ENG or 1.50.5050.
i'm definitely dumb to NOT take your advice...so, i will. more than likely the 1.50.5050 hboot. seems to be more likely to play well with 2.89 kernels. otherwise, i'd do the ENG hboot.
from your thread, you mention that the only ones that DO run 2.89 based kernels are stock (1.58) and jbear's (1.58.5858).
do you think ENG hboot will be pliable enough at any point to be compatible with them? THAT would be pretty great.
thanks again, gang.
--------------------------------------------------------------
what? you think just cause a guy reads comics he can't kick some a$$?
cipher77 said:
ramjet...you suggested downgrading hboot after the ruu flash to ENG or 1.50.5050.
i'm definitely dumb to NOT take your advice...so, i will. more than likely the 1.50.5050 hboot. seems to be more likely to play well with 2.89 kernels. otherwise, i'd do the ENG hboot.
from your thread, you mention that the only ones that DO run 2.89 based kernels are stock (1.58) and jbear's (1.58.5858).
do you think ENG hboot will be pliable enough at any point to be compatible with them? THAT would be pretty great.
Click to expand...
Click to collapse
Unfortunately, there is no hboot that will run all Evo 3D CDMA ROM's but there are only three ROM's that I know require 1.58 or JBear 1.58.5858 at this time and that's the Sprint ICS stock ROM, Cool ICS and Viper3D. Some ROM developers have incorporated the "VM leak" kernel in place of the stock Sprint ICS 2.89(.651.2) kernel just to avoid that requirement. The reason I'm recommending JBear GB (1.50.5050) or the engineering (ENG-1.04) bootloader at this point is that there are far more ROM's that can be flashed and run with those than the 1.58.x versions, and they both support the fastboot commands that would normally require an unlocked bootloader.
ramjet73
ramjet73 said:
Unfortunately, there is no hboot that will run all Evo 3D CDMA ROM's but there are only three ROM's that I know require 1.58 or JBear 1.58.5858 at this time and that's the Sprint ICS stock ROM, Cool ICS and Viper3D. Some ROM developers have incorporated the "VM leak" kernel in place of the stock Sprint ICS 2.89(.651.2) kernel just to avoid that requirement. The reason I'm recommending JBear GB (1.50.5050) or the engineering (ENG-1.04) bootloader at this point is that there are far more ROM's that can be flashed and run with those than the 1.58.x versions, and they both support the fastboot commands that would normally require an unlocked bootloader.
ramjet73
Click to expand...
Click to collapse
gotcha.
makes sense that devs would swap out the vm leak just to avoid the hassle.
thanks for the info, btw.
about to flash the ruu from your qaderso zip.
not having to relock before doing the flash is nice.
thanks again for all of your help.
i'll report back with success...or, hang ups.
update...
just wanted to check in.
i went ahead and ran the ruu.exe without any issues.
since i was already s-off and unlocked via htc...i didn't bother relocking.
once the ruu did its thing it changed the hboot to stock and the previous REVOLUTIONARY in the bootloader header disappeared and it just read UNLOCKED.
not sure if this was right...but, i didn't have to unlock again.
i stayed s-off AND unlocked after the ruu.
i re-ran the ruu later in the day since staying s-off and unlocked didn't sit well with me after the intial run. but, the result was the same.
so, i'm all good, i suppose.
any takers?
installed SU, reinstalled 4ext (had been using it successfully for a while now. great recovery.) and busybox.
then, something strange happened.
rather, something i didn't expect.
after changing the hboot to 1.50.5050 via bootloader...
as instructed...i powered down.
extracted the zip from the root so i wouldn't be in a bootloop.
but, it still wouldn't load the stock rom.
is that weird? or, expected?
i actually had to reinstall via recovery another sense rom.
otherwise, i think everything's going well.
waiting to get some time to flash a cm10 rom at this point.
unless someone thinks otherwise!
thanks again...
cipher77 said:
then, something strange happened.
rather, something i didn't expect.
after changing the hboot to 1.50.5050 via bootloader...
as instructed...i powered down.
extracted the zip from the root so i wouldn't be in a bootloop.
but, it still wouldn't load the stock rom.
is that weird? or, expected?
i actually had to reinstall via recovery another sense rom.
otherwise, i think everything's going well.
waiting to get some time to flash a cm10 rom at this point.
unless someone thinks otherwise!
thanks again...
Click to expand...
Click to collapse
That's normal. As a reminder, I'll quote from a post I made earlier in this thread:
ramjet73 said:
Unfortunately, there is no hboot that will run all Evo 3D CDMA ROM's but there are only three ROM's that I know require 1.58 or JBear 1.58.5858 at this time and that's the Sprint ICS stock ROM, Cool ICS and Viper3D.
Click to expand...
Click to collapse
The stock 2.89.651.2 ROM is in fact one of the few that currently require the 1.58 bootloader. That's why my guide recommends installing the JBear 1.58.5858 bootloader by default since the RUU installs the stock ICS ROM.
Also, the reason your bootloader shows unlocked is probably because you htcdev unlocked it before doing the hboot 1.4 downgrade for S-OFF. I've never done that method myself, but in discussing it with mpgrimm2, apparently the downgrade method doesn't reset the bootloader status to locked like the JupunutBear (wire trick) method does.
ramjet73
ramjet73 said:
That's normal. As a reminder, I'll quote from a post I made earlier in this thread:
The stock 2.89.651.2 ROM is in fact one of the few that currently require the 1.58 bootloader. That's why my guide recommends installing the JBear 1.58.5858 bootloader by default since the RUU installs the stock ICS ROM.
Also, the reason your bootloader shows unlocked is probably because you htcdev unlocked it before doing the hboot 1.4 downgrade for S-OFF. I've never done that method myself, but in discussing it with mpgrimm2, apparently the downgrade method doesn't reset the bootloader status to locked like the JupunutBear (wire trick) method does.
ramjet73
Click to expand...
Click to collapse
RE: hboot bootloop...doy! consider me FACEPALMED.
maybe, RAM-PALMED!
hell, i probably read over that line twenty times and never really READ it.
so, thanks again.
either way, since not many will stay on stock soft or stock hboot...i suppose it's not really an issue.
change hboot and change rom.
but, it did give me a scare for a minute.
as for the lock versus unlock...your guess is as good as, if not infinitely better, than mine.
everything definitely works, tho.
appreciate you seeing this through and checking in on me, btw.
Ok, I am banging my head against the wall trying to figure this damn issue out. I have s-off via the Wiretrick method. I have tried 1.04 ENG, Juopunutbear's 1.50, 1.57, and 1.58, and Revolutionary hboot 1.40 Hboots. They were all flashed via the boot loader. I am running the latest 4ext recovery, and before that I was running TWRP 1.1.1. I seem to be able to boot into ICS roms just fine, (Harmonia and DigitalHigh MIUI) How ever though, I can not get booted into any Jellybean rom I try. I've tried Slimbean, AOKP, and DigitalHigh Miui JB. Wtf am I doing wrong, and how do I go about fixing it?
Thanks,
Deja
deja_geek said:
Wtf am I doing wrong, and how do I go about fixing it?
Thanks,
Deja
Click to expand...
Click to collapse
Did you do the "fix everything" thread?
Here's what I would recommend:
1. Flash the VM RUU.
2. Boot into the stock ROM and download and flash the OTA.
3. Flash a custom bootloader (JBear 1.50.5050 works well with both 4EXT and TWRP)
4. Use fastboot to flash 4EXT or recovery
5. Format "all partitions except SD card" in 4EXT
6. Flash and boot whatever AOSP based ROM you want
If you can't get the OTA via "System updates" in settings after flashing the RUU, follow the instructions for S-OFF users in this post to download and install it.
I think that will fix your booting problems. If all that works and you prefer TWRP you should be able to flash 2.3.3.0 after performing the above steps and still flash and boot most ROM's successfully.
ramjet73
ramjet73 said:
Did you do the "fix everything" thread?
Here's what I would recommend:
1. Flash the VM RUU.
2. Boot into the stock ROM and download and flash the OTA.
3. Flash a custom bootloader (JBear 1.50.5050 works well with both 4EXT and TWRP)
4. Use fastboot to flash 4EXT or recovery
5. Format "all partitions except SD card" in 4EXT
6. Flash and boot whatever AOSP based ROM you want
If you can't get the OTA via "System updates" in settings after flashing the RUU, follow the instructions for S-OFF users in this post to download and install it.
I think that will fix your booting problems. If all that works and you prefer TWRP you should be able to flash 2.3.3.0 after performing the above steps and still flash and boot most ROM's successfully.
ramjet73
Click to expand...
Click to collapse
Will this take me backt to a locked bootloader that I have to do the wiretrick on again to get S-OFF? What am I downloading with the OTA? Also, it's a Virgin Mobile Evo V.. some of these links take me to donwloads labeled sprint. Is that going to be an issue?
deja_geek said:
Will this take me backt to a locked bootloader that I have to do the wiretrick on again to get S-OFF? What am I downloading with the OTA? Also, it's a Virgin Mobile Evo V.. some of these links take me to donwloads labeled sprint. Is that going to be an issue?
Click to expand...
Click to collapse
1. No.
2. OTA Updates the base VM stock firmware and ROM.
3. VM USA is part of Sprint. Everything I recommended is compatible with the Evo V 4G.
4. No.
5. If you want to try to fix it another way that's fine with me.
ramjet73
ramjet73 said:
1. No.
2. OTA Updates the base VM stock firmware and ROM.
3. VM USA is part of Sprint. Everything I recommended is compatible with the Evo V 4G.
4. No.
5. If you want to try to fix it another way that's fine with me.
ramjet73
Click to expand...
Click to collapse
Did not mean to offend. I just noticed I didn't say Evo V on my orginal post and wanted to make sure I wasn't going to brick the phone. Thanks for the help, I will give this method a test. Just one more quick question (if you're willing to induldge me). I don't have a windows machine persay... my laptop(s) run linux with Windows Virtual Machines (Virtualbox) can I use those Virtual Machines?
Thanks a ton!
Deja
deja_geek said:
Did not mean to offend. I just noticed I didn't say Evo V on my orginal post and wanted to make sure I wasn't going to brick the phone. Thanks for the help, I will give this method a test. Just one more quick question (if you're willing to induldge me). I don't have a windows machine persay... my laptop(s) run linux with Windows Virtual Machines (Virtualbox) can I use those Virtual Machines?
Thanks a ton!
Deja
Click to expand...
Click to collapse
That might work if you install the HTC drivers but this is probably a better way:
1. Download the VM RUU.exe to a Windows virtual machine.
2. Use the method in this post to extract the rom.zip file and rename it to PG86IMG.zip.
3. Flash the RUU from your current bootloader.
The rest of the steps should be doable on Linux as long as you have the ADB/fastboot directory setup.
BTW, as soon as you mentioned Harmonia I knew you have an Evo V 4G since nobody uses that on the Evo 3D.
ramjet73
ramjet73 said:
That might work if you install the HTC drivers but this is probably a better way:
1. Download the VM RUU.exe to a Windows virtual machine.
2. Use the method in this post to extract the rom.zip file and rename it to PG86IMG.zip.
3. Flash the RUU from your current bootloader.
The rest of the steps should be doable on Linux as long as you have the ADB/fastboot directory setup.
BTW, as soon as you mentioned Harmonia I knew you have an Evo V 4G since nobody uses that on the Evo 3D.
ramjet73
Click to expand...
Click to collapse
I OWE YOU A BEER! Works great and now can install all the Jellybean goodness I can get my grubby little hands on! Thanks a million!
~Deja
I'm having the same issue. I will lose root and my custom recovery after flashing stock ruu right?
Sent from my PG86100 using xda app-developers app
DroidManIc said:
I'm having the same issue. I will lose root and my custom recovery after flashing stock ruu right?
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Yes, but if you are s-off, you'll remain that way. Then you can just flash a custom hboot and recovery and then ROM and you're set. If your s-on, you'll have to reroot after unlocking through HTCdev.
Alright, so I flashed stock ruu updated to ics and updated everything else. I remained S-off and unlocked bootloader.if I read this correctly now I flash recovery> flash SU (for root)>and finally reflash JB room?
Sent from my PG86100 using xda app-developers app
---------- Post added at 08:04 PM ---------- Previous post was at 08:03 PM ----------
coal686 said:
Yes, but if you are s-off, you'll remain that way. Then you can just flash a custom hboot and recovery and then ROM and you're set. If your s-on, you'll have to reroot after unlocking through HTCdev.
Click to expand...
Click to collapse
Alright, so I flashed stock ruu updated to ics and updated everything else. I remained S-off and unlocked bootloader.if I read this correctly now I flash recovery> flash SU (for root)>and finally reflash JB room?
Sent from my PG86100 using xda app-developers app
DroidManIc said:
Alright, so I flashed stock ruu updated to ics and updated everything else. I remained S-off and unlocked bootloader.if I read this correctly now I flash recovery> flash SU (for root)>and finally reflash JB room?
Click to expand...
Click to collapse
There is no need to root the stock ROM unless you want to nandroid it that way.
Since you are S-OFF and have unlocked the bootloader (or if you flashed a custom bootloader) you can use the "fastboot boot recovery recovery.img" command to flash your custom recovery, then wipe and flash a custom ROM. Make sure to flash an hboot lower than the stock 1.58 version before flashing a JB ROM.
ramjet73
ramjet73 said:
There is no need to root the stock ROM unless you want to nandroid it that way.
Since you are S-OFF and have unlocked the bootloader (or if you flashed a custom bootloader) you can use the "fastboot boot recovery recovery.img" command to flash your custom recovery, then wipe and flash a custom ROM. Make sure to flash an hboot lower than the stock 1.58 version before flashing a JB ROM.
ramjet73
Click to expand...
Click to collapse
And to add to that, I'd use one of the custom bootloaders. I use 1.4 revolutionary myself.
Ok ill give it a shot. The thing is that I had originally installed Jbear custom hboot and had the same issue. I downgraded to 1.4 same issue. But ill retry. Thanks
Sent from my PG86100 using xda app-developers app
ramjet73 said:
There is no need to root the stock ROM unless you want to nandroid it that way.
Since you are S-OFF and have unlocked the bootloader (or if you flashed a custom bootloader) you can use the "fastboot boot recovery recovery.img" command to flash your custom recovery, then wipe and flash a custom ROM. Make sure to flash an hboot lower than the stock 1.58 version before flashing a JB ROM.
ramjet73
Click to expand...
Click to collapse
If I flash hboot 1.40 via bootloader will stock ROM boot ok so I can rename file to get back into recovery via bootloader?
Sent from my PG86100 using xda app-developers app
DroidManIc said:
If I flash hboot 1.40 via bootloader will stock ROM boot ok so I can rename file to get back into recovery via bootloader?
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
No. The stock ICS ROM will not. Do you have the micro sd to sd card adapter to use in your computer?
Duh of course don't know how I forgot that. Well I redid the whole process and now I'm on MIUI JB. Thanks again guys!
Sent from my Evo 3D CDMA using xda app-developers app
ramjet73 said:
Did you do the "fix everything" thread?
Here's what I would recommend:
1. Flash the VM RUU.
2. Boot into the stock ROM and download and flash the OTA.
3. Flash a custom bootloader (JBear 1.50.5050 works well with both 4EXT and TWRP)
4. Use fastboot to flash 4EXT or recovery
5. Format "all partitions except SD card" in 4EXT
6. Flash and boot whatever AOSP based ROM you want
If you can't get the OTA via "System updates" in settings after flashing the RUU, follow the instructions for S-OFF users in this post to download and install it.
I think that will fix your booting problems. If all that works and you prefer TWRP you should be able to flash 2.3.3.0 after performing the above steps and still flash and boot most ROM's successfully.
ramjet73
Click to expand...
Click to collapse
Can i use the same vm ruu you linked? im on boost mobile
Thanks
Also, what exactly is the problem that causes these bootloops in the first place?
louforgiveno said:
Can i use the same vm ruu you linked? im on boost mobile
Thanks
Also, what exactly is the problem that causes these bootloops in the first place?
Click to expand...
Click to collapse
No, but here's a guide you can use instead.
As to what causes it, nobody has identified the specific reason, but in general terms it seems to be caused by mixing and matching various firmware and ROM updates.
It's like the GB and AOSP ROM's not booting with the stock (1.57/1.58) hboots. Nobody has identified why they don't work so we just downgrade them to work around the problem.
ramjet73
thanks in advance ramjet.
is there a way to do this without ruu? if i ruu my phone will be set for sprint again and not boost which will cost me about 100 bucks in money and time to get back to boost.
thanks again
birddseedd said:
thanks in advance ramjet.
is there a way to do this without ruu? if i ruu my phone will be set for sprint again and not boost which will cost me about 100 bucks in money and time to get back to boost.
thanks again
Click to expand...
Click to collapse
I've been a Sprint user for a long time so I don't know what's involved in flashing the Evo 3D to Boost, but here's a post from a Cricket user that might help.
Anything you do to modify your phone is at your own risk so you will need to decide if it is safe or not. I suggest using Google to get more feedback about using the RUU when when flashed to another carrier.
ramjet73
I need to get back to the latest stock update for the rezound. I'm on the infection ROM right now and just need to get back to the latest rezound ota. Are there any ota ROMs w root out? I dont want to have to re root again but I wanna be back on the latest ota w/ just root. Also, will I need to lock my phone again to do this?
One last thing, how can I update to the latest firmware/ hboot/kernel/radio etc. Pretty much want to return to the latest ota leak for the rezound even if its not official and then I'd like to update my hboot,radio, kernel, etc to the latest out.
Sorry for any typos I'm extremely busy at work trying to sneak this in. Thx for the help guys.
Sent from my Infectious Rezound using Tapatalk 2
Follow the instructions in this post:
http://forum.xda-developers.com/showpost.php?p=37448962&postcount=2
That will get you updated to the latest and back to stock.
Then you can unlock again, flash a recovery and reroot and remain on stock ROM with a custom recovery and rooted.
xXezmacXx said:
I need to get back to the latest stock update for the rezound. I'm on the infection ROM right now and just need to get back to the latest rezound ota. Are there any ota ROMs w root out? I dont want to have to re root again but I wanna be back on the latest ota w/ just root. Also, will I need to lock my phone again to do this?
One last thing, how can I update to the latest firmware/ hboot/kernel/radio etc. Pretty much want to return to the latest ota leak for the rezound even if its not official and then I'd like to update my hboot,radio, kernel, etc to the latest out.
Sorry for any typos I'm extremely busy at work trying to sneak this in. Thx for the help guys.
Sent from my Infectious Rezound using Tapatalk 2
Click to expand...
Click to collapse
What hboot/radio level are you at now?
For a good Sense 3.6 rom, I'd suggest Ineffabilis Deus v1.2, gives you that stock feel with tweaks available.
You can run the global RUU from here: http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ You will need to re-lock if you are s-on.
You can run NilsP Business Sense 3.6 if you want a mostly stock ROM without bloat. I'd suggest restoring a nandroid from the OTA if you have it (I don't keep many nandroids, but that ICS OTA is the one I kept).
Here is the stock ICS OTA: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/ You will also have to be s-off or re-locked to flash this.
Sorry if I've repeated information posted by anybody previously. That was never my intent. I just hope this helps.
mjones73 said:
What hboot/radio level are you at now?
For a good Sense 3.6 rom, I'd suggest Ineffabilis Deus v1.2, gives you that stock feel with tweaks available.
Click to expand...
Click to collapse
my hboot is 2.25.0000 and radio is 1.22.10.0421r/1.22.10.0424r. i know this isnt up to date. id like to be up to date i just dont know which to files i need and how to update everything.
Read post #2 in this thread.
mjones73 said:
What hboot/radio level are you at now?
For a good Sense 3.6 rom, I'd suggest Ineffabilis Deus v1.2, gives you that stock feel with tweaks available.
Click to expand...
Click to collapse
iamwalterwhite said:
You can run the global RUU from here: http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/ You will need to re-lock if you are s-on.
You can run NilsP Business Sense 3.6 if you want a mostly stock ROM without bloat. I'd suggest restoring a nandroid from the OTA if you have it (I don't keep many nandroids, but that ICS OTA is the one I kept).
Here is the stock ICS OTA: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/ You will also have to be s-off or re-locked to flash this.
Sorry if I've repeated information posted by anybody previously. That was never my intent. I just hope this helps.
Click to expand...
Click to collapse
so before i do anything i just want to understand a few things. im currently on a jellybean rom, infection. to get back to the latest ota i just flash the latest ruu which is 4.03.605.2? will i have any issues being s-off or being on a jb rom? and the once i get back onto 4.03 will i need to unlock using the htc website and then root again? and then my last question is, once im back to the lastest stock rom how do i update my firmware/radio/hboot, etc.? I'm just confused on what steps to take and in what order?
feralicious said:
Read post #2 in this thread.
Click to expand...
Click to collapse
i did. could you please read my previous post above? im s-off. do still need to lock my phone again? i remeber using that htcdev to unlock my phone awhile ago. then used the wire trick to get s-off.
xXezmacXx said:
so before i do anything i just want to understand a few things. im currently on a jellybean rom, infection. to get back to the latest ota i just flash the latest ruu which is 4.03.605.2? will i have any issues being s-off or being on a jb rom? and the once i get back onto 4.03 will i need to unlock using the htc website and then root again? and then my last question is, once im back to the lastest stock rom how do i update my firmware/radio/hboot, etc.? I'm just confused on what steps to take and in what order?
Click to expand...
Click to collapse
xXezmacXx said:
i did. could you please read my previous post above? im s-off. do still need to lock my phone again? i remeber using that htcdev to unlock my phone awhile ago. then used the wire trick to get s-off.
Click to expand...
Click to collapse
If you are s-off your phone should say "locked" and you can just run the RUU. Running that updates all the firmware, radios etc... and so you'll be on the latest stock and locked at that point. Run it twice and let it do its thing until it reboots so it gets all the system files.
Since you are s-off I don't think you will need to unlock again, check what the phone says in hboot as far as *tampered* *unlocked* *s-off* etc... you should confirm that with someone who is s-off.
(if you still have the unlock token you can use it again if you ever need to. Keep it handy so you'll always have it when you need it. I keep mine in the folder I use on my pc for fastboot.)
After you unlock you flash a custm recovery and root from within the recovery if you want to flash another ROM. Or use one of the tools, I've never used any of them.
I think you're good with this RUU for jb. It's the latest and I don't think anyone has anything later than that. I don't use a jb ROM so you may want to confirm that with someone who does.
feralicious said:
If you are s-off your phone should say "locked" and you can just run the RUU. Running that updates all the firmware, radios etc... and so you'll be on the latest stock and locked at that point. Run it twice and let it do its thing until it reboots so it gets all the system files.
Since you are s-off I don't think you will need to unlock again, check what the phone says in hboot as far as *tampered* *unlocked* *s-off* etc... you should confirm that with someone who is s-off.
(if you still have the unlock token you can use it again if you ever need to. Keep it handy so you'll always have it when you need it. I keep mine in the folder I use on my pc for fastboot.)
After you unlock you flash a custm recovery and root from within the recovery if you want to flash another ROM. Or use one of the tools, I've never used any of them.
I think you're good with this RUU for jb. It's the latest and I don't think anyone has anything later than that. I don't use a jb ROM so you may want to confirm that with someone who does.
Click to expand...
Click to collapse
My phone says:
***tampered***
***locked ***
vigor pvt ship s-off rl
hboot 2.25.0000
radio 1.22.10.0421r/1.22.10.0424r
I used htcdev to unlock my phone don't know why it says locked. Should I just go ahead and flash the ruu? Could you just give a quick step by step guide? ? But if I'm understanding you correctly I just flash the ruu, then i need to unlock my phone again with HTCdev then flash recovery n while in amonra i instill su to roor and I'm now on the latest ota with root? I don't want a ROM at this time. I just want the latest stock rezound with root and latest hboot and radio.
Sent from my Infectious Rezound using Tapatalk 2
If anyone else can help please jump in. I'm still on infection not good flash this ruu until I know exactly what to do.
Sent from my Infectious Rezound using Tapatalk 2
xXezmacXx said:
My phone says:
***tampered***
***locked ***
vigor pvt ship s-off rl
hboot 2.25.0000
radio 1.22.10.0421r/1.22.10.0424r
I used htcdev to unlock my phone don't know why it says locked. Should I just go ahead and flash the ruu? Could you just give a quick step by step guide? ? But if I'm understanding you correctly I just flash the ruu, then i need to unlock my phone again with HTCdev then flash recovery n while in amonra i instill su to roor and I'm now on the latest ota with root? I don't want a ROM at this time. I just want the latest stock rezound with root and latest hboot and radio.
Sent from my Infectious Rezound using Tapatalk 2
Click to expand...
Click to collapse
You're s-off. Going s-off relocks the phone because s-off is better than unlocked. You can just flash the RUU.
I recommend against unlocking once you're s-off, because if you try to relock it yourself outside of the s-off process, it will say "relocked" instead of "locked. You can either flash a recovery through a PH98IMG.zip, or you can flash a hex edited hboot to allow extended fastboot commands.
shrike1978 said:
You're s-off. Going s-off relocks the phone because s-off is better than unlocked. You can just flash the RUU.
I recommend against unlocking once you're s-off, because if you try to relock it yourself outside of the s-off process, it will say "relocked" instead of "locked. You can either flash a recovery through a PH98IMG.zip, or you can flash a hex edited hboot to allow extended fastboot commands.
Click to expand...
Click to collapse
OK so I just ruu and it will bring me back to stock. I then flash amonra 3.16 using the IMG.zip to get recovery on my phone.
(how do I flash the zip since recovery will not be on my phone yet? Do I just use the rezounds recovery to flash it?)
Then once amonra is installed I now root by installing su and superuser from the options in recovery.
Is that it, now I'm on the latest rezound stock w root? Am i still soff too, I don't need to do the wire trick to get soff again?
Oh and flashing that ruu will update me to the latest hboot and radio, correct?
Sent from my Infectious Rezound using Tapatalk 2
xXezmacXx said:
OK so I just ruu and it will bring me back to stock. I then flash amonra 3.16 using the IMG.zip to get recovery on my phone.
(how do I flash the zip since recovery will not be on my phone yet? Do I just use the rezounds recovery to flash it?)
Then once amonra is installed I now root by installing su and superuser from the options in recovery.
Is that it, now I'm on the latest rezound stock w root? Am i still soff too, I don't need to do the wire trick to get soff again?
Oh and flashing that ruu will update me to the latest hboot and radio, correct?
Sent from my Infectious Rezound using Tapatalk 2
Click to expand...
Click to collapse
Yes.
If you just want to stay stock and rooted then just run the RUU, flash recovery and root. You should still be s-off and ready to flash a custom ROM if you end up choosing to.
xXezmacXx said:
OK so I just ruu and it will bring me back to stock. I then flash amonra 3.16 using the IMG.zip to get recovery on my phone.
(how do I flash the zip since recovery will not be on my phone yet? Do I just use the rezounds recovery to flash it?)
Then once amonra is installed I now root by installing su and superuser from the options in recovery.
Is that it, now I'm on the latest rezound stock w root? Am i still soff too, I don't need to do the wire trick to get soff again?
Oh and flashing that ruu will update me to the latest hboot and radio, correct?
Sent from my Infectious Rezound using Tapatalk 2
Click to expand...
Click to collapse
As long as you have a flashable zip of AR 3.15 you're good. All you have to do is rename it PH98IMG.zip (make sure you don't name it .zip.zip) and flash in your bootloader. Here is a link for an already packaged recovery zip: http://www.teambamf.net/topic/3737-bootloader-update-recovery-files-amon-ra-315-and-cwm-touch/ No need to do the wire trick again. Yes, you will be on the newest hboot and radios.
iamwalterwhite said:
As long as you have a flashable zip of AR 3.15 you're good. All you have to do is rename it PH98IMG.zip (make sure you don't name it .zip.zip) and flash in your bootloader. Here is a link for an already packaged recovery zip: http://www.teambamf.net/topic/3737-bootloader-update-recovery-files-amon-ra-315-and-cwm-touch/ No need to do the wire trick again. Yes, you will be on the newest hboot and radios.
Click to expand...
Click to collapse
links dont work. i have AR 3.16 flashable zip, will that work
xXezmacXx said:
My phone says:
***tampered***
***locked ***
vigor pvt ship s-off rl
hboot 2.25.0000
radio 1.22.10.0421r/1.22.10.0424r
I used htcdev to unlock my phone don't know why it says locked. Should I just go ahead and flash the ruu? Could you just give a quick step by step guide? ? But if I'm understanding you correctly I just flash the ruu, then i need to unlock my phone again with HTCdev then flash recovery n while in amonra i instill su to roor and I'm now on the latest ota with root? I don't want a ROM at this time. I just want the latest stock rezound with root and latest hboot and radio.
Sent from my Infectious Rezound using Tapatalk 2
Click to expand...
Click to collapse
I was on the Inflection Rom too and S-off. I used the Hansoon rezound all in one toolkit. I reflashed the latest RUU and I ulocked again using my unlock code that I had generated on HTC. I flashed recovery and install supersu and now I am rooted on the latest RUU unlocked and S-off.
xXezmacXx said:
links dont work. i have AR 3.16 flashable zip, will that work
Click to expand...
Click to collapse
Yes, that's the latest version.
feralicious said:
Yes, that's the latest version.
Click to expand...
Click to collapse
ok everything went ok. im on 4.03.605.1.
my phone now says:
***locked***
vigor pvt ship s-off rl
hboot-2.27.0000
radio-2.22.10.0001r/2.22.10.0003r
few questions.
1. it use to say ***tampered*** right above locked. what happened?
2. how do i root now? do i just go into recovery>developer menu and select "install su & superuser"?
3. once the jellybean roms are fixed and all the bugs are gone im gonna jump back over. if i want to flash a jellybean rom, do i just go ahead and flash the rom? and will my hboot remain the same whatever rom i flash?
4. im just curious on how im s-off but my phone says locked?
netookska05 said:
I was on the Inflection Rom too and S-off. I used the Hansoon rezound all in one toolkit. I reflashed the latest RUU and I ulocked again using my unlock code that I had generated on HTC. I flashed recovery and install supersu and now I am rooted on the latest RUU unlocked and S-off.
Click to expand...
Click to collapse
i didnt unlock again? my phone still says soff? and it still says locked too.
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