Hello, i have rom file for evo3d and know procedure to install rom on the phone. Just need to know how to root the phone, also can i temp root only if i only want to install rom on the phone? Also, flashing this ROM: RUU_Shooter_U_HTC_ARA_1.24.415.6_Radio_10.59.9020.00_10.15.9020.06_M_release_22091 7_signed.exe
Thank you.
Just need to know how to root the phone, also can i temp root only if i only want to install rom on the phone?
Click to expand...
Click to collapse
There are guides in the development section that show you how to do it. It all depends on if your phone is cdma or gsm, and what hboot you have.
Also, flashing this ROM: RUU_Shooter_U_HTC_ARA_1.24.415.6_Radio_10.59.9020. 00_10.15.9020.06_M_release_22091 7_signed.exe
Click to expand...
Click to collapse
If you flash that, that's an ruu and will unroot you. Also, you do not need root to flash an ruu.
sitlet said:
There are guides in the development section that show you how to do it. It all depends on if your phone is cdma or gsm, and what hboot you have.
If you flash that, that's an ruu and will unroot you. Also, you do not need root to flash an ruu.
Click to expand...
Click to collapse
I have read somewhere procedure to flash rom to phone:
Enter vol down + power and enter recovery
Mount storage and coipy rom to root of phone
Wipe data and then
Install zip file from sdcard
Is this procedure correct and enough and/or do i need some more steps?
YOur answer will really help me...thanks
Almost correct. You need to wipe data, cache, and dalvik. And also make a nandroid backup before wiping.
And FYI, you still need root to flash a rom.
sitlet said:
Almost correct. You need to wipe data, cache, and dalvik. And also make a nandroid backup before wiping.
And FYI, you still need root to flash a rom.
Click to expand...
Click to collapse
But u earlier told me i dont need root for flashing ruu...btw i read somewhere i just need fastboot.exe and i need to uninstall htc sync and the connect phone in fastboot mode and run the ruu file from pc
sitlet said:
Almost correct. You need to wipe data, cache, and dalvik. And also make a nandroid backup before wiping.
And FYI, you still need root to flash a rom.
Click to expand...
Click to collapse
You don't need root to flash a rom, you need a recovery to flash a rom. Flashing
A custom rom gives you root. Or you can root your stock rom.
#Root-Hack_Mod*Always\
Ok thanks guys, just need to know if i can run this ruu i mentioned earlier on HBOOT 1.4 or HBOOT 1.5?
Do you have a cdma or gsm phone? What hboot are you on now? Why are you wanting to flash an RUU?
sitlet said:
Do you have a cdma or gsm phone? What hboot are you on now? Why are you wanting to flash an RUU?
Click to expand...
Click to collapse
I have a gsm phone and want to install rom for arabic support...i will receive a couple of pieces tomorrow and dont know which hboot its on..can i flash this ruu on any hboot?
andrew21 said:
I have a gsm phone and want to install rom for arabic support...i will receive a couple of pieces tomorrow and dont know which hboot its on..can i flash this ruu on any hboot?
Click to expand...
Click to collapse
No you can't. Whats your hboot ver ?? To find out power off your phone. Then press and hold the volume down button. Keep the volume button pressed down and then tap the power button. Then you should boot into a white screen. At the top left corner it will be your hboot verison
#Root-Hack_Mod*Always\
laie1472 said:
No you can't. Whats your hboot ver ?? To find out power off your phone. Then press and hold the volume down button. Keep the volume button pressed down and then tap the power button. Then you should boot into a white screen. At the top left corner it will be your hboot verison
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
Can you tell me what hboot version can i installl this ROM on? If you wish to know the HBoot version my phone is on i will post after 12 hours....thanks
andrew21 said:
Can you tell me what hboot version can i installl this ROM on? If you wish to know the HBoot version my phone is on i will post after 12 hours....thanks
Click to expand...
Click to collapse
You should definitely read this entire thread before you flash that ruu.
http://forum.xda-developers.com/showthread.php?t=1282840
Hope this helps.
#Root-Hack_Mod*Always\
sitlet said:
Almost correct. You need to wipe data, cache, and dalvik. And also make a nandroid backup before wiping.
And FYI, you still need root to flash a rom.
Click to expand...
Click to collapse
You dont need root to flash any ROM, root is just having superuser.apk and binary in your ROM.
Your NAND protection needs to be unlocked via HTC method or revolutionary.io to install a ROM.
---------- Post added at 07:17 PM ---------- Previous post was at 07:14 PM ----------
andrew21 said:
I have a gsm phone and want to install rom for arabic support...i will receive a couple of pieces tomorrow and dont know which hboot its on..can i flash this ruu on any hboot?
Click to expand...
Click to collapse
For a ROM with Arabic support, search in the GSM developmet section of 3D.
It should be zip file instead of exe .
It does not matter whether you are rooted or not to install a ROM.
Just make sure your bootloader is unlocked via revolutionary.io , or HTCdev.com (if revolutionary is unsupported)
Also you should have a custom recovery.
So, you mean to say i need bootloader unlocked to flash ruu shipped roms right? BTW how do i know if my bootloader is unlocked or not?
BTW downloaded program from revolutioary.io, how do i use this program to unlock bootloader?
Thanks
andrew21 said:
So, you mean to say i need bootloader unlocked to flash ruu shipped roms right? BTW how do i know if my bootloader is unlocked or not?
BTW downloaded program from revolutioary.io, how do i use this program to unlock bootloader?
Thanks
Click to expand...
Click to collapse
Nah, for RUU.exe you need a locked bootloader and for flashing the ROMs made by XDA devs , you need unlocked bootloader.
If you are going to use RUU exe dont unlock bootloader and dont use revolutionary and dont install custom Recovery..
Use them only if you want to flash ROMs made by XDA devs.
But be sure that the RUU you are using is made for your phone, or you will end up with a bricked phone.
mnomaanw said:
Nah, for RUU.exe you need a locked bootloader and for flashing the ROMs made by XDA devs , you need unlocked bootloader.
If you are going to use RUU exe dont unlock bootloader and dont use revolutionary and dont install custom Recovery..
Use them only if you want to flash ROMs made by XDA devs.
But be sure that the RUU you are using is made for your phone, or you will end up with a bricked phone.
Click to expand...
Click to collapse
Thanks, saved my day
Just one more question...does it matter what version my HBOOT is to flash ruu?
andrew21 said:
Just one more question...does it matter what version my HBOOT is to flash ruu?
Click to expand...
Click to collapse
Yes , you cant just use any RUU of any region I guess, you should use only the RUU made for phones of your region.
The RUU should contain the hboot same as yours or a new version.
It should not contain hboot of lower version than your current one..
mnomaanw said:
Yes , you cant just use any RUU of any region I guess, you should use only the RUU made for phones of your region.
The RUU should contain the hboot same as yours or a new version.
It should not contain hboot of lower version than your current one..
Click to expand...
Click to collapse
I know how to check HBOOT version of my evo3d...if i want to flash this file:
RUU_Shooter_U_HTC_ARA_1.24.415.6_Radio_10.59.9020.00_10.15.9020.06_M_release_220917_signed
How do i know HBOOT version of this file?
Thanks
andrew21 said:
I know how to check HBOOT version of my evo3d...if i want to flash this file:
RUU_Shooter_U_HTC_ARA_1.24.415.6_Radio_10.59.9020.00_10.15.9020.06_M_release_220917_signed
How do i know HBOOT version of this file?
Thanks
Click to expand...
Click to collapse
Run the RUU exe without connecting your phone to PC.
When the 1st screen of RUU appears, minimise it > open my computer > then in your windows drive > search " rom.zip" .
There should be only one rom.zip > copy it to your desktop or anywhere > close the RUU program > open the rom.zip with winRAR or any software > you will see a list of " .img, .txt, .nb0 " files. One of the ".nb0" file says "hboot_*.*_signedbyaa.nb0"
In my case it is "hboot_1.50.0000_signedbyaa.nb0"
The number infront of the hboot is its version . In my case it is hboot 1.50.0000.
Related
Currently on HBOOT 0.57.0000 with S-ON and want to upgrade to 1.02.0000 so I can use Revolutionary to S-OFF. Is there anyway to upgrade the HBOOT to this version without losing my CWM/CM7 setup or using a stock RUU to flash? Can the HBOOT be extracted from the stock RUU? On a US AT&T Aria for the record.
Just nandroid first then run the ruu-revolutionary-then restore.after you s-off you can fastboot flash whatever version of cwm you want.
Sent from my HTC Aria using XDA App
I understand that method, but was attempting to avoid the RUU flashing. Just wanted to upgrade the HBOOT with the 1.02.000 nb0 file. Can this be done via fastboot?
TDQuiksilver said:
I understand that method, but was attempting to avoid the RUU flashing. Just wanted to upgrade the HBOOT with the 1.02.000 nb0 file. Can this be done via fastboot?
Click to expand...
Click to collapse
I don't think so.
Try this one.Usageut the LIBEDIAG.zip into you /sdcard and then turn off you device,hold on Vol-,and then power button to HBoot,wait few sec,then it will display info,do it as the info.
I have not test it,'cos I have no one s-on device,but these operation will not damage you phone.
jeleint said:
Try this one.Usageut the LIBEDIAG.zip into you /sdcard and then turn off you device,hold on Vol-,and then power button to HBoot,wait few sec,then it will display info,do it as the info.
I have not test it,'cos I have no one s-on device,but these operation will not damage you phone.
Click to expand...
Click to collapse
Did you manually make this zip file? If it isn't signed by HTC, it won't work.
drumist said:
Did you manually make this zip file? If it isn't signed by HTC, it won't work.
Click to expand...
Click to collapse
I'd like to know this as well.
If I did the wire trick to get s-off how will flashing the latest RUU affect me? Wanted to try the latest Ineffabilis rom, but they say you should flash the RUU first. Can someone give me a run down of how this should work? I am unlocked, s-off, ICS firmware, amon ra recovery.
jaxsin said:
If I did the wire trick to get s-off how will flashing the latest RUU affect me? Wanted to try the latest Ineffabilis rom, but they say you should flash the RUU first. Can someone give me a run down of how this should work? I am unlocked, s-off, ICS firmware, amon ra recovery.
Click to expand...
Click to collapse
S-off won't affect your flashing any RUU. Just download the RUU you want to run , put on the external SD card rename to PHIMG98.zip then reboot to bootloader. Press power to access fastboot menu , it will then find the RUU and read it then ask it you want to update. Select volume up to choose yes and let it do its thing. It should automatically run twice , because the first time it just installs the stock recovery, and 2 other parts. Second time it installs the rest including radio's and system image.
When finally done it should reboot and you will be on the stock RUU that you ran. After that , just reflash a custom recovery and either restore a backup rom or flash the rom of your choice.
jaxsin said:
If I did the wire trick to get s-off how will flashing the latest RUU affect me? Wanted to try the latest Ineffabilis rom, but they say you should flash the RUU first. Can someone give me a run down of how this should work? I am unlocked, s-off, ICS firmware, amon ra recovery.
Click to expand...
Click to collapse
mjh68 said:
S-off won't affect your flashing any RUU. Just download the RUU you want to run , put on the external SD card rename to PHIMG98.zip then reboot to bootloader. Press power to access fastboot menu , it will then find the RUU and read it then ask it you want to update. Select volume up to choose yes and let it do its thing. It should automatically run twice , because the first time it just installs the stock recovery, and 2 other parts. Second time it installs the rest including radio's and system image.
When finally done it should reboot and you will be on the stock RUU that you ran. After that , just reflash a custom recovery and either restore a backup rom or flash the rom of your choice.
Click to expand...
Click to collapse
great explanation of how the ruu process is done. One thing to add, back up internal sd before doing this because it will be wiped.
Just to double check, I don't need to lock the phone before flashing RUU?
jaxsin said:
Just to double check, I don't need to lock the phone before flashing RUU?
Click to expand...
Click to collapse
No, the modified jb will let you flash it.
Sent from my ADR6425LVW using Tapatalk 2
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 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