Related
I'm struggling with all the terminology and methods with flashing. Basically I just wanted root, so I read several different guides and got a rooted status and managed to install the Amon Ra recovery. However my bootloader (also called HBOOT - is that correct?) shows tampered / unlocked now. Basically, I want to flash back to the most current build and try again.
Would the link on the Android Police forums to download RUU 4.03.605.2 be latest Verizon build as if it were fresh out of the box?
I checked on the wiki, but didn't see anything for the Rezound there.
Also, to use this utility, I relock my bootloader using HTCDev and then move this zipped file to my sd card and reboot to the bootloader either using adb or the power + volume down, correct? It will see the zip file and begin flashing or do I run an executable from my PC with the phone connected? I'm not S-Off because I figured that is way above my head at this point.
I appreciate any help anyone can offer.
The tampered just means you have a custom recovery like Amon Ra installed.
Sent from my ADR6425LVW using xda app-developers app
oatlord said:
I'm struggling with all the terminology and methods with flashing. Basically I just wanted root, so I read several different guides and got a rooted status and managed to install the Amon Ra recovery. However my bootloader (also called HBOOT - is that correct?) shows tampered / unlocked now. Basically, I want to flash back to the most current build and try again.
Would the link on the Android Police forums to download RUU 4.03.605.2 be latest Verizon build as if it were fresh out of the box?
I checked on the wiki, but didn't see anything for the Rezound there.
Also, to use this utility, I relock my bootloader using HTCDev and then move this zipped file to my sd card and reboot to the bootloader either using adb or the power + volume down, correct? It will see the zip file and begin flashing or do I run an executable from my PC with the phone connected? I'm not S-Off because I figured that is way above my head at this point.
I appreciate any help anyone can offer.
Click to expand...
Click to collapse
4.03.605..2 is the latest vzw build.
jbh00jh said:
4.03.605..2 is the latest vzw build.
Click to expand...
Click to collapse
If I want to load that RUU, do I have to relock my bootloader? Will I be able to load the file from the Android Police forum without being S-OFF since I've rooted and loaded a recovery?
oatlord said:
If I want to load that RUU, do I have to relock my bootloader? Will I be able to load the file from the Android Police forum without being S-OFF since I've rooted and loaded a recovery?
Click to expand...
Click to collapse
Having S-OFF negates the need to relock your bootloader.
You should be able to flash the "RUU" zip file with your phone in its current condition.
If you do some research in this section in the S-OFF threads, you'll get some good info about not re locking after s-off.
Re-locking is only necessary if you don't have s-off.
Sent from my ADR6425LVW using Tapatalk 2
to reinstall the RUU, first make sure you have fastboot on your PC and your phone is in the fastboot menu of the bootloader and connected to your PC. It should say "fastboot USB". (If you don't have the HTC drivers installed, download HTC Sync 3.0 and that should install it. I haven't gotten it to work on Windows 8 so if you use Windows 8 use these drivers)
Open a command prompt, change the directory to where your fastboot.exe is (example: cd c:\fastboot_directory). Type in 'fastboot oem lock'. Your phone will restart, then boot up. Turn it off, reboot to the bootloader and make sure it says *RELOCKED* on the top. Then, go back to fastboot and in your cmd window, type in 'fastboot oem rebootRUU'. Your phone will reboot and show a black screen with a grey HTC logo. Copy the RUU (doesn't matter if it's named PH98IMG.zip or something else) into the same folder as fastboot.exe and type in 'fastboot flash zip ruu_zip_name.zip' (obviously replacing ruu_zip_name.zip with the zip's actual name). The terminal will start sending the zip and details will be displayed on your computer screen. Your phone will also have a progress bar. Once the terminal on your computer says it's finished, you can reboot your phone.
I am currently S-On, unlocked, running Newts One XXX with the Global OTA (4.03.605) Sense 4 Kernel. I would now like to get the 4.03.605.2 firmware installed. Would the procedure described above work for my situation or is there another method I can use.
My next leap is to go S-off but for now I would just like to get the firmware updated before reflashing Newts.
Thanks in advance.
Yes, you can use the above method fine. However, going S-Off is very easy. It seems like a daunting task, but if you read the directions thoroughly it is very easy. I used the .5 version of Juopunutbear and it worked without a hitch. You are already unlocked and rooted, so if you S-Off, you won't have to do it all over again. From there you can flash the RUU, flash a FLASHABLE version of AR 3.15, then reflash any rom that you want. You will only get the benefit from global with roms that are built aroung the .2 base, but you will get updated radios. I haven't honestly noticed much of a difference with the new radios though.
layneja said:
I am currently S-On, unlocked, running Newts One XXX with the Global OTA (4.03.605) Sense 4 Kernel. I would now like to get the 4.03.605.2 firmware installed. Would the procedure described above work for my situation or is there another method I can use.
My next leap is to go S-off but for now I would just like to get the firmware updated before reflashing Newts.
Thanks in advance.
Click to expand...
Click to collapse
Flash stock recovery here's a link http://www.mediafire.com/?wb21d2gdurui2c6 then lock bootloader. (Fastboot OEM lock)
After locking bootloader(cuz your s-on) rename the ruu you downloaded from android police To PH98IMG put on your sd return sd phone boot into bootloader run update, if it stops and powers off mid update remove battery and start it again, It flashed the hboot first then you gotta go back In And finish the update.
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
---------- Post added at 11:41 AM ---------- Previous post was at 10:59 AM ----------
layneja said:
I am currently S-On, unlocked, running Newts One XXX with the Global OTA (4.03.605) Sense 4 Kernel. I would now like to get the 4.03.605.2 firmware installed. Would the procedure described above work for my situation or is there another method I can use.
My next leap is to go S-off but for now I would just like to get the firmware updated before reflashing Newts.
Thanks in advance.
Click to expand...
Click to collapse
Also to avoid any problems do a factory reset in hboot after update is installed. Being that we're s-on when we re-unlock it does it for us but I've heard some people are having problems after the ruu if they didn't FDR while on stock recovery.. just a heads up
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
famouscollin said:
Flash stock recovery here's a link (removed cause I'm too new) then lock bootloader. (Fastboot OEM lock)
After locking bootloader(cuz your s-on) rename the ruu you downloaded from android police To PH98IMG put on your sd return sd phone boot into bootloader run update, if it stops and powers off mid update remove battery and start it again, It flashed the hboot first then you gotta go back In And finish the update.
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
---------- Post added at 11:41 AM ---------- Previous post was at 10:59 AM ----------
Also to avoid any problems do a factory reset in hboot after update is installed. Being that we're s-on when we re-unlock it does it for us but I've heard some people are having problems after the ruu if they didn't FDR while on stock recovery.. just a heads up
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
Click to expand...
Click to collapse
Just to clarify: when you reboot using "adb reboot" or power + volume down, are you booting into the bootloader or hboot? I've read the guides but still a little confused there.
Also, what does the stock recovery do versus something like Amon Ra? Does the stock recovery allow for creating backups and what-not? Sorry to be a total noob here. I can bake cookies or something for you all for your help, hehe.
WookieFan said:
Having S-OFF negates the need to relock your bootloader.
You should be able to flash the "RUU" zip file with your phone in its current condition.
If you do some research in this section in the S-OFF threads, you'll get some good info about not re locking after s-off.
Re-locking is only necessary if you don't have s-off.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
if you're s-off you shouldn't have to unlock.
---------- Post added at 07:17 PM ---------- Previous post was at 07:11 PM ----------
oatlord said:
Just to clarify: when you reboot using "adb reboot" or power + volume down, are you booting into the bootloader or hboot? I've read the guides but still a little confused there.
Also, what does the stock recovery do versus something like Amon Ra? Does the stock recovery allow for creating backups and what-not? Sorry to be a total noob here. I can bake cookies or something for you all for your help, hehe.
Click to expand...
Click to collapse
The bootloader is the hboot. You power on holding vol down to get there.
The stock recovery does not allow you to create backups, or do much at all I'm pretty sure. That is why we have custom ones.
If i helped throw me a thanks
iamwalterwhite said:
Yes, you can use the above method fine. However, going S-Off is very easy. It seems like a daunting task, but if you read the directions thoroughly it is very easy. I used the .5 version of Juopunutbear and it worked without a hitch. You are already unlocked and rooted, so if you S-Off, you won't have to do it all over again. From there you can flash the RUU, flash a FLASHABLE version of AR 3.15, then reflash any rom that you want. You will only get the benefit from global with roms that are built aroung the .2 base, but you will get updated radios. I haven't honestly noticed much of a difference with the new radios though.
Click to expand...
Click to collapse
Do you mean flash the RUU in the bootloader and then the recovery also in bootloader? i only ask cause im at school and i forgot my microsd adapter so i cant rename the zips so that I can flash both of them from there, but if i can do it from recovery then im set
xxtsxx said:
Do you mean flash the RUU in the bootloader and then the recovery also in bootloader? i only ask cause im at school and i forgot my microsd adapter so i cant rename the zips so that I can flash both of them from there, but if i can do it from recovery then im set
Click to expand...
Click to collapse
Sorry that you never got an answer to this. Yes, you should flash both recovery (stock) and the RUU as PH98IMG zip files. Wait to start this process until you have a pc/sd card reader available. Trying this without those basic tools is going to make this a frustrating process for you.
Sent from my ADR6425LVW using Tapatalk 2
I bought Evo which was already upgraded to ICS (OTA I assume), and it was branded I think. I've unlocked it via HTCDev, flashed '4ext touch recovery' and then rooted. Then I flashed MIUI ICS ROM, and everything is OK for now.
I want to use BootManager to flash multiple ROMs. It requires s-off. I tried it already with s-on, because I've read that SmartFlash (from 4ext recovery) makes my phone like s-off, so ROM on SD card installed, but won't boot. I had many problems going back to my Phone ROM, I restored my backup, wiped many times, installed fresh ROM and still had a bootloop. Finally I got it working again by flashing boot.img via fastboot (glad I did nandroid backup before). I didn't try again with different ROM, because after 2 hours of trying to recover my base ROM I've had enough. So I'm pretty sure BootManager will work better if my phone will be s-off.
So my question is - what to do next? We have so many guides and different comments here, sometimes the same method works for one, and doesn't work for another one, and I'm really confused.
I assume I should follow the instructions here http://forum.xda-developers.com/showthread.php?t=1743466 but I don't understand few things:
friend.evil said:
flash an ICS ROM from recovery(Method B from 10 to 14)
open ICS ROM.zip and extract boot.img to a folder which contains adb, fastboot and AdbWinApi.dll
go to fastboot and type:
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Do I have to do this if I'm already have MIUI with root privileges? Do I still need that boot.img from MIUI, and put it together with fastboot.exe?
Or should I restore stock ICS? I'm pretty sure I did nandroid backup before flashing MIUI.
friend.evil said:
12_Notice when you s-off the phone the hboot is corrupted i advice after s-off to follow the methods In E_(from 1 to 4)
Click to expand...
Click to collapse
Do I need to fix hboot after s-off? What hboot version I have after doing steps 1 to 4 from section E? There's a big zip file (PG86IMG.zip), is it another ROM or what?
And most important question - if method D doesn't work, method F is recommended, but:
elias17 said:
Hboot s on will only flash roms that are based on ics 3.28xx and sense 4 roms using a special boot.img ! U can never flash GB roms until u go s off like i did its a tricky process but it works and now i can flash any rom in the gsm section
Click to expand...
Click to collapse
friend.evil said:
2_flash Leedroid GB ROM from recovery http://leedroid.ftp.rshost.eu/Shoote....zip(Don't forget to wipe data/factory reset and wipe cache + dalvik)
Click to expand...
Click to collapse
I don't get it - can I flash GB ROM or not if I have hboot 1.53.0007 s-on? Can I use method F if method D fail?
Sorry for my english, I'm from Poland.
Thanks in advance for any tip.
You're confusing yourself, What you need to do my friend is.
1. Download RUU, Run RUU
2. HTC Unlock bootloader again
3. Do the Juopunutbear Wiretrick to get s-off
4. Download the 1.04 ENG hboot (There is one of those for the GSM I think... not sure though)
5. Flash a badass Android 4.2.1 rom. They work.
There's much more detailed guides on what to do, BUT This is a summary of what you want.
Be sure to hit thanks [= I'm almost to 100
Which RUU should I search for? GB or ICS?
But isn't the 1+2 the same as restoring my ICS Stock ROM from backup?
I think hboot 1.49.0007 would be enough, I've read that BootManager works well with that version.
1. Yes you can just restore your stock ics backup BUT you will have to root it using the file provided in method B.
2. Yes the 1.49.0007 hboot is best for gsm
3. You can flash a GB rom with your hboot no problem. It just dont think it will boot. so technically you should be able to do the wire trick with a GB rom flashed(not booted into). You'll be in fastboot mode for the wiretrick. There are different files for GB and ICS when doing the wiretrick
Your best bet is to run an ICS RUU, unlock bootloader, root rom, do the wire trick, change hboot to 1.49.0007 and then flash any rom you want
Backup was made right after I made root, is it enough? I just don't want to go through the entire process from the beginning (unlocking, rooting etc).
mars28 said:
Backup was made right after I made root, is it enough? I just don't want to go through the entire process from the beginning (unlocking, rooting etc).
Click to expand...
Click to collapse
That should work But unlocking again is really easy
You should still have you unlock token in the same place,
You just plug up to the computer hop into fastboot usb and type
Fastboot flash unlocktoken Unlock_Code.bin
to unlock and then
fastboot flash recovery recovery.img
for a recovery,
Then move SU to your sd card and flash it in recovery.
Then your all ready for the wire trick, The more you do these things the more experience you get at them and the better you get with fastboot. I suggest you go through the process opposed to just restoring (First off it's much much safer) and you'll know the ropes if you (or anyone else) has this problem.
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
mars28 said:
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
Click to expand...
Click to collapse
The token and the unlock code are specific to the phone, And doesn't change until you get a new phone.
And that seems to be the right one, Do you live in Europe? lol Shooter u means GSM and ICS means it's the latest RUU.
mars28 said:
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
Click to expand...
Click to collapse
you can easily get a new token from htc dev web site
Sent from my HTC EVO 3D X515m using xda app-developers app
Can't_Live_Without_My_Evo said:
And that seems to be the right one, Do you live in Europe? lol Shooter u means GSM and ICS means it's the latest RUU.
Click to expand...
Click to collapse
I know I use shooter_u, I asked because I've found another RUU which have "Rogers_WWE" in name of the file, and the rest of the file name is identical, and I remember that I had to choose "rogers" when I was unlocking via htcdev. That's why I wasn't 100% sure if I had to choose "HTC_Europe" or "Rogers_WWE".
Another thing which confuses me:
http://forum.xda-developers.com/showthread.php?t=1495358
mpgrimm2 said:
Note 3: If you previously did the HTC Unlock, you'd have to "RELOCK" BEFORE running the RUU.
To do this from fastboot type: fastboot oem lock
Click to expand...
Click to collapse
Should I do this or start directly with RUU.exe? My phone is currently "UNLOCKED, hboot 1.53.0007, s-on".
And what about CID? I've read somewhere that I have to change to supercid or something, to be able to flash zips via fastboot. How to check my current CID?
Search for cid getter on play store to get your cid
You certainly need to relock you hboot before running RUU. For the correct ruu you should check the box that your phone came in. It should have the details (atleast i think so)
P.S. you probably don't need to change cid. Infact i'd recommend you not to do that just yet
Got the CID, it's HTC__032. I want to be prepared, who knows what might come up during the whole process.
friend.evil said:
12_Notice when you s-off the phone the hboot is corrupted i advice after s-off to follow the methods In E_(from 1 to 4)
Click to expand...
Click to collapse
What means "corrupted"? Phone won't boot or what?
Eeh, if I knew that hboot 1.53.x is so problematic, I would buy Evo with GB on-board.
mars28 said:
Got the CID, it's HTC__032. I want to be prepared, who knows what might come up during the whole process.
What means "corrupted"? Phone won't boot or what?
Eeh, if I knew that hboot 1.53.x is so problematic, I would buy Evo with GB on-board.
Click to expand...
Click to collapse
I think yours might be an european model. i had the exact same cid as yours.
when you get to that step of corrupted hboot just follow the steps on this thread and flash hboot 1.49.0007
http://forum.xda-developers.com/showthread.php?t=1906172
Cant kive without my evis comments about the wire trick are bang on. It will fix everything. Having s-off is just much easier so do the wire trick. It will work. My wife and I both have an evo. I had to do the wire trick twice on hers for it to work and four times on mine for it to work. Be patient if it fails the first few times. And if the screen gets stuck on the jounuo whatever screen you can fix that.
If you are stuck at Juopunutbear screen and if you can go to bootloader you need to connect the phone to pc, go to fastboot ( should say fastboot usb)*Go to controlbear folder (from where you ran controlbear to begin withon you pc then open command window in it (hold shift and right click, that willopen command window rigjt there and then*when you get into it you need to enter:
"ControlBear.exe -f" no quotes or "ControlBear f" notice the space after the exe !
Lots of peopke forget to put it in and say it didnt work.
I presume this will fix the problem
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
My phone is now s-off. I didn't flash RUU, just restored stock rooted ROM from backup, did the wire trick (just one time, surprisingly) and everything went nice and smooth. Then I flashed hboot 1.49.0007 with no problems at all. Thanks guys for the tips.
One more thing - my phone state is now "LOCKED" - should I bother?
So I got what I wanted - I've installed ROM in BootManager (the one which doesn't boot before, while phone was 's-on') and this time it booted from SD. Today I'll try more ROMs in BootManager.
Locked doesn't matter as long as you are s-off. It only creates problems if you ever plan on using fastboot commands. Trust me, you dont need to bother with it
But if you really want to know heres a quote from ramjet where he explains it a bit.
ramjet73 said:
Once the RUU.exe is run and the stock bootloader is installed, the phone will be bootloader S-ON regardless of the radio S-OFF status. To run fastboot commands like "flash" and "erase" the stock bootloader needs to be unlocked by the htcdev method or a custom bootloader modified to support those commands needs to be flashed, which requires radio S-OFF.
Click to expand...
Click to collapse
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
VZW is sending me a refurb to replace a dead Rezound.
I have PH98IMG_ICS_3.14.605.12-shipped-rom.zip
for the RUU, OTA-ICS-Plus-DTa2sd-v.1.2.zip for the
rom, recovery-ra-vigor-3.16-gnm.img for recovery and
ControlBear_Release_0.5_Vigor_ICS_2.14.605.5_Win
for the s-off script.
I've got a nandroid backup and complete backup of
the internal /sdcard and external microsd card
including a TiBu of everything in both flashable
and database formats with a flashable TiBu
apk. :angel:
I know I have to
unlock boot loader
flash a recovery
install root
then run the s-off script and do the wire trick when prompted,
did I miss any steps?
After that I reflash the recovery and restore
the amonra backup, recopy the backup of
internal /sdcard and hopefully be back
where I was when the nandroid &
/sdcard backup was done?
I'd like to end up with s-off, Amonra recovery and
the custom ICS ROM I was on at last nandroid.
Do I need to reflash a bootloader / radio / boot
combo or does the s-off script do that?
I'm unsure what will be the refurb sometimes
I get ones with the original gingerbread and
sometimes whatever is the latest OTA.
Do I need to flash an ICS RUU that is compatible
with the rom I'm going to use before / after s-off?
Would that replace the s-off hboot with the stock one?
I guess maybe I should do the RUU then S-off?
fuzzynco said:
VZW is sending me a refurb to replace a dead Rezound.
I have PH98IMG_ICS_3.14.605.12-shipped-rom.zip
for the RUU, OTA-ICS-Plus-DTa2sd-v.1.2.zip for the
rom, recovery-ra-vigor-3.16-gnm.img for recovery and
ControlBear_Release_0.5_Vigor_ICS_2.14.605.5_Win
for the s-off script.
I've got a nandroid backup and complete backup of
the internal /sdcard and external microsd card
including a TiBu of everything in both flashable
and database formats with a flashable TiBu
apk. :angel:
I know I have to
unlock boot loader
flash a recovery
install root
then run the s-off script and do the wire trick when prompted,
did I miss any steps?
After that I reflash the recovery and restore
the amonra backup, recopy the backup of
internal /sdcard and hopefully be back
where I was when the nandroid &
/sdcard backup was done?
I'd like to end up with s-off, Amonra recovery and
the custom ICS ROM I was on at last nandroid.
Do I need to reflash a bootloader / radio / boot
combo or does the s-off script do that?
I'm unsure what will be the refurb sometimes
I get ones with the original gingerbread and
sometimes whatever is the latest OTA.
Do I need to flash an ICS RUU that is compatible
with the rom I'm going to use before / after s-off?
Would that replace the s-off hboot with the stock one?
I guess maybe I should do the RUU then S-off?
Click to expand...
Click to collapse
uhhhh, there are alot of questions. so im just going to reply with my thoughts than reply if you need more answers
You should Flash the latest RUU. if it already comes with it than just keep that one
install Amon Ra Recovery
do S-OFF, S-OFF will not touch your radio or boot but it may flash an hboot of 2.25 but if you want you can re flash your RUU after and wont lose or effect S-OFF
also when restoring your nandroid you only nee to restore the data folder to get everything back. so flash the rom zip in recovery than restore the data folder only and reboot. and things like music and pictures should be copied back to your sdcards
and as for ics RUU and rom compatibility, any ics RUU will work with your ics ROM. but always use the latest
BTW weird choice of rom, there are alot of new roms out that are awesome
PLEASE be sure that when you do Juopunut's S-OFF method you DO NOT USE the same SDCard where your Nandroid is, or you will most assuredly lose everything on that card. Use a different microsd card, or at least copy everything on your card to PC for safekeeping, then you can copy it back.
I'm not sure the Nandroid from the old phone will take on the new one because of the new device ID, but others may be able to help you get around that.
I just did this (for the 3rd time) but first I waited for the OTA firmware/radio update. Then, as you state, the method is: (1) htc.dev unlock bootloader; (2) flash Amon Ra recovery; (3) Root the device in recovery; (4) Nandroid backup (just in case): (5) insert different microsd card and run Juopunot S-OFF; (6) replace temp sdcard with your regular sdcard in the handset; (7) restore Nandroid (or old nandroid, if you can).
hgoldner said:
...
I'm not sure the Nandroid from the old phone will take on the new one because of the new device ID, but others may be able to help you get around that.
...
Click to expand...
Click to collapse
Yeah, in regards to the phone ID and nandroid, what you need to do is make a new nandroid on the new phone and it will make a folder with that phone's ID. Then copy your old nandroid into that folder so it will then see it and you can restore that old one from there.
hboot's and ROMs and fastboot Oh My
hgoldner said:
PLEASE be sure that when you do Juopunut's S-OFF
method you DO NOT USE the same SDCard where your Nandroid is, or you will
most assuredly lose everything on that card. Use a different microsd card, or at
least copy everything on your card to PC for safekeeping, then you can copy it
back.
.
Click to expand...
Click to collapse
The latest one, 0.5 I think, does attempt to preserve the sdcard's content,
but I always an empty 4gb just for that.
You were saying the latest stock hboot will still allow fastboot commands,
with s-off already done? I thought I need the patched JB (s-off) one for
ICS to have that work?
May I should look into a current ROM with the updated radios then?
fuzzynco said:
The latest one, 0.5 I think, does attempt to preserve the sdcard's content,
but I always an empty 4gb just for that.
You were saying the latest stock hboot will still allow fastboot commands,
with s-off already done? I thought I need the patched JB (s-off) one for
ICS to have that work?
May I should look into a current ROM with the updated radios then?
Click to expand...
Click to collapse
Nope. I flashed my own splash screen via fastboot usb right after getting S-OFF via Juopunut's ControlBear.
Dumped down the innertubes from my Transformer TF300T.
Wouldn't you be on Juopunut's hboot at that point?
I was asking if I used a later RUU, (overwriting the special
hboot with the newer stock one), would the unlocked fastboot
commands still work, even though its locked / s-off?
fuzzynco said:
Wouldn't you be on Juopunut's hboot at that point?
I was asking if I used a later RUU, (overwriting the special
hboot with the newer stock one), would the unlocked fastboot
commands still work, even though its locked / s-off?
Click to expand...
Click to collapse
Should. I just checked again and post ControlBear S-OFF I still have hboot v. 2.28 which is the new OTA firmware version.
Remember, you can obviously do fastboot usb on stock hboot, because that's how you unlock the bootloader.
My name's Harold and I'm a flashaholic.....
So are you saying all the patched & ENG hboots do differently
is cosmetics? (saying locked / no tampered warning (with a
possible custom title line) vs tampered and unlocked)?
fuzzynco said:
So are you saying all the patched & ENG hboots do differently
is cosmetics? (saying locked / no tampered warning (with a
possible custom title line) vs tampered and unlocked)?
Click to expand...
Click to collapse
Not sure. I know that my old Rezound had Juopunut's last hboot and said "locked" even though it was S-OFF and my current Rezound says "TAMPERED UNLOCKED" on stock hboot. It doesn't really matter. Both support fastboot usb, and I don't use it that much anyway. Only issue may be a mainver mismatch now, but as I intend to stay mostly stock, that doesn't matter to me.
Dumped down the innertubes from my Asus Transformer TF300T
fuzzynco said:
So are you saying all the patched & ENG hboots do differently
is cosmetics? (saying locked / no tampered warning (with a
possible custom title line) vs tampered and unlocked)?
Click to expand...
Click to collapse
hgoldner said:
Not sure. I know that my old Rezound had Juopunut's last hboot and said "locked" even though it was S-OFF and my current Rezound says "TAMPERED UNLOCKED" on stock hboot. It doesn't really matter. Both support fastboot usb, and I don't use it that much anyway. Only issue may be a mainver mismatch now, but as I intend to stay mostly stock, that doesn't matter to me.
Dumped down the innertubes from my Asus Transformer TF300T
Click to expand...
Click to collapse
My understanding is this:
When you s-off your phone will say locked.
Juopunut's hboot - no fastboot function
Eng hboot - fastboot function, which is why people flash this
Stock hboot - fastboot function (of course)
Tampered just means you have a custom recovery on it, but when you s-off the process replaces it, I don't know what it says instead, maybe Juopunut.
Tampered and unlocked is usually a phone that is s-on with a custom recovery (like mine), although some people who s-offed also unlocked again for some reason so theirs say unlocked. However, you don't have to unlock after you s-off.
feralicious said:
My understanding is this:
When you s-off your phone will say locked.
Juopunut's hboot - no fastboot function
Eng hboot - fastboot function, which is why people flash this
Stock hboot - fastboot function (of course)
Tampered just means you have a custom recovery on it, but when you s-off the process replaces it, I don't know what it says instead, maybe Juopunut.
Tampered and unlocked is usually a phone that is s-on with a custom recovery (like mine), although some people who s-offed also unlocked again for some reason so theirs say unlocked. However, you don't have to unlock after you s-off.
Click to expand...
Click to collapse
I think the last version of Juopunut restores both whatever recovery you had before you get S-OFF and possibly also your hboot. I definitely did *not* have "tampered* on my first two Rezounds after getting S-OFF, but they were on earlier hboot/RUU versions. This is the first time I ran it on a post "official" global OTA (with the 2.28 hboot), and now it says TAMPERED. I could probably flash an earlier hboot, but since I still have fastboot usb access (and used it to flash my own splash screen) it isn't necessary.
Can I use Juopunut's hboot (25) with the current firmware and
a rom expecting the current firmware, and AmonRa recovery?
I also use a custom splash (actually Juopunut's).
I like to clean look of locked and untampered
It does support most of fastboot command set,
I don't need the ENG specific subset anyway.
So, I have a dilemma. I am currently S-ON running TACHYON 1.2 (Android 4.3)
HBOOT 2.28.0000
Radio 2.23.10.0123/4
I updated the hboot and radio while S-ON. Now, I've decided I'd like to go S-OFF. According to JuopunutBear I need to be on a stock RUU for their S-OFF to work. I tried running the newest ICS RUU a few weeks ago and found that it would just error out when it was checking the file because the radios and hboot on the phone were newer than the ones on the RUU. Can I step backwards in HBOOT versions whlie S-ON or have I kind of screwed myself? Or is there a better option I haven't thought about?
Thanks
Just install a stock Rom to run s-off program. You are on a stock hboot, so no problem there.
Sent from my DNA using my mind.
Uzephi said:
Just install a stock Rom to run s-off program. You are on a stock hboot, so no problem there.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
It's a stock hboot, yes. But the RUU won't run because it is an older version hboot.
You need s-off to downgrade. Just install a stock based Rom that is rooted and run s-off procedure. You will have no issues. After s-off if you want, you can ruu
Sent from my DNA using my mind.
Step 1 from Unlimited: Verify - You are on Stock RUU (not FreshROM, Stock Rooted, HarmonyROM - none of these will work!)
They say not to be rooted or anything. What difference does it make?
Also, what do you mean by "stock rom"? Is there a stock rom I can install that is not an RUU? (maybe that's a dumb question but I don't know lol)
jeff925 said:
Step 1 from Unlimited: Verify - You are on Stock RUU (not FreshROM, Stock Rooted, HarmonyROM - none of these will work!)
They say not to be rooted or anything. What difference does it make?
Also, what do you mean by "stock rom"? Is there a stock rom I can install that is not an RUU? (maybe that's a dumb question but I don't know lol)
Click to expand...
Click to collapse
A stock rooted RUU would work. I was in your predicament once. First, do a nandroid backup then use this guide it'll get you to s-off. If you want to downgrade, then use this guide to accomplish this.
Thanks guys for the help. Installed the rom listed in the guide and it worked great. S-OFF now!! (Took me long enough...I've had the phone for 2 years!)
It installed JuopunutBear's hboot but whatever. I'd probably rather stick with a stock hboot but I can do that later.
Restored my nandroid backup and I'm back up and running like I never left.
Just flash this ROM and boot image, and you should be able to S-OFF, I can't remember if stock recovery is needed but that can be flashed separately as well if needed, but I don't think it is.
http://forum.xda-developers.com/showthread.php?t=2260154
So, All was well until I decided to flash the stock hboot back to the phone. I put the file on the sd card and renamed it ph98img.zip and flashed it in fastboot. It said it was successful and that I was running hboot 2.28 and radio 2.23.10.0123/4. Then I rebooted and it hung up at the white screen with green htc logo. I pulled the battery and rebooted holding the power and volume buttons. It booted to fastboot so I tried a few things. I tried flashing a recovery but it said that remote was not allowed and failed. Then I tried opening the recovery I already had on the phone from fastboot and it gave me the software download icon. Nothing happened so I pulled the battery and tried to boot back to fastboot. This time it wouldn't even get to fastboot. The white screen with HTC logo comes up and then the screen goes blank. Then the software download icon comes up and then shortly there after a red triangle with an exclamation point takes its place.
That went downhill fast! Any suggestions?
EDIT: Pulling the SD card allows me to get back into fastboot! But I'm still not sure what to do. Is it because my bootloader is locked?
jeff925 said:
So, All was well until I decided to flash the stock hboot back to the phone. I put the file on the sd card and renamed it ph98img.zip and flashed it in fastboot. It said it was successful and that I was running hboot 2.28 and radio 2.23.10.0123/4. Then I rebooted and it hung up at the white screen with green htc logo. I pulled the battery and rebooted holding the power and volume buttons. It booted to fastboot so I tried a few things. I tried flashing a recovery but it said that remote was not allowed and failed. Then I tried opening the recovery I already had on the phone from fastboot and it gave me the software download icon. Nothing happened so I pulled the battery and tried to boot back to fastboot. This time it wouldn't even get to fastboot. The white screen with HTC logo comes up and then the screen goes blank. Then the software download icon comes up and then shortly there after a red triangle with an exclamation point takes its place.
That went downhill fast! Any suggestions?
EDIT: Pulling the SD card allows me to get back into fastboot! But I'm still not sure what to do. Is it because my bootloader is locked?
Click to expand...
Click to collapse
In fastboot does it say s-off? Try manually flashing the boot.img by extracting it. If you haven't setup enviroment variable for fastboot put the boot.img in the same directory as fastboot.exe and use command prompt by typing
Code:
cd C:\Android\platform-tools (or wherever it is for you)
Then type
Code:
fastboot flash boot boot.img
I was able to put an RUU on another sd card and flash that. So now I'm on ICS 4.03.605.2 and running. But I still haven't solved my recovery problems.
According to this thread: androidforums.com/rezound-all-things-root/550408-s-off-guide-info-return-stock.html
I can either use juopunutbear's hboot (which I just flashed over the top of) to flash a new recovery or I can compile a recovery in a ph98img file (which I don't know how to do or want to do).
My question is: What happens if I unlock my bootloader while S-OFF? (Yes, it says s-off on the bootloader screen.) Will that solve my problem or do I have to go back to juopunutbear's hboot?
jeff925 said:
I was able to put an RUU on another sd card and flash that. So now I'm on ICS 4.03.605.2 and running. But I still haven't solved my recovery problems.
According to this thread: androidforums.com/rezound-all-things-root/550408-s-off-guide-info-return-stock.html
I can either use juopunutbear's hboot (which I just flashed over the top of) to flash a new recovery or I can compile a recovery in a ph98img file (which I don't know how to do or want to do).
My question is: What happens if I unlock my bootloader while S-OFF? (Yes, it says s-off on the bootloader screen.) Will that solve my problem or do I have to go back to juopunutbear's hboot?
Click to expand...
Click to collapse
You can unlock when S-OFF, but there is no reason to, you can get a PH98img.zip of CWM here: http://forum.xda-developers.com/showthread.php?t=1914215 or TWRP here: http://forum.xda-developers.com/showthread.php?t=1902381 and just copy it to your sd card (remember to name it exactly PH98IMG.zip, beware the Windoze "double zip" issue) then pop it in the phone, boot into Hboot with the USB disconnected and it should recognize it and flash either CWM or TWRP. from there you can flash ANYTHING you want, being S-OFF with custom recovery allows you to flash anything, no fastboot commands required.
Also, since you are S-OFF, your Hboot is mostly irrelevant, but should be the matching version to your radios... an engineered hboot (like Juopunutbears) would allow fastboot commands well locked, but fastboot isn't generally needed once S-OFF has been obtained...
Try this. no wire even, works great.
http://forum.xda-developers.com/showthread.php?p=48911002#post48911002
i am on hboot 2.25 though. im thinking of updating my hboot still researching how exactly.
4218kris said:
Try this. no wire even, works great.
http://forum.xda-developers.com/showthread.php?p=48911002#post48911002
i am on hboot 2.25 though. im thinking of updating my hboot still researching how exactly.
Click to expand...
Click to collapse
i can help with that....its pretty easy if your already s-off
---------- Post added at 03:26 AM ---------- Previous post was at 03:22 AM ----------
jeff925 said:
I was able to put an RUU on another sd card and flash that. So now I'm on ICS 4.03.605.2 and running. But I still haven't solved my recovery problems.
According to this thread: androidforums.com/rezound-all-things-root/550408-s-off-guide-info-return-stock.html
I can either use juopunutbear's hboot (which I just flashed over the top of) to flash a new recovery or I can compile a recovery in a ph98img file (which I don't know how to do or want to do).
My question is: What happens if I unlock my bootloader while S-OFF? (Yes, it says s-off on the bootloader screen.) Will that solve my problem or do I have to go back to juopunutbear's hboot?
Click to expand...
Click to collapse
and what recovery problems are you having....flashing an hboot will not give you a recovery...and an ruu is an exe file not a ph98img file...those are OTA's.....if you need pure stock i can easily help you obtain it....i just need to know what exactly your trying to achieve
REV3NT3CH said:
i can help with that....its pretty easy if your already s-off
---------- Post added at 03:26 AM ---------- Previous post was at 03:22 AM ----------
Click to expand...
Click to collapse
i believe i can flash hboot with a ph98img yea? can you link me to the best/newest 2.28 i think.
4218kris said:
i believe i can flash hboot with a ph98img yea? can you link me to the best/newest 2.28 i think.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=40767819&postcount=33
4218kris said:
i believe i can flash hboot with a ph98img yea? can you link me to the best/newest 2.28 i think.
Click to expand...
Click to collapse
that one or the this 2nd ph98img in my downgrade/upgrade guide work as well...that one is just radios and hboot....doesnt come with stock <3e> recovery
REV3NT3CH said:
if you need pure stock i can easily help you obtain it....i just need to know what exactly your trying to achieve
Click to expand...
Click to collapse
Hey REV3NT3CH,
So, thanks to the help of so many in these parts, including you, I now think I'm S-Off and I'm very interested in bringing my phone up to the latest, completely stock OTA ROM. Can you help me with that?
Thanks!
cheers,
john
jrredho said:
Hey REV3NT3CH,
So, thanks to the help of so many in these parts, including you, I now think I'm S-Off and I'm very interested in bringing my phone up to the latest, completely stock OTA ROM. Can you help me with that?
Thanks!
cheers,
john
Click to expand...
Click to collapse
when you boot into your bootloader...does your hboot now say S-OFF....if so i can give you everything you need and what id suggest doing just prior to doing it
REV3NT3CH said:
when you boot into your bootloader...does your hboot now say S-OFF..
Click to expand...
Click to collapse
Yes it does.
REV3NT3CH said:
.if so i can give you everything you need and what id suggest doing just prior to doing it
Click to expand...
Click to collapse
That would be fantastic!
Thanks,
John