Related
Now before I screw up my phone, I would like to know if it is possible to switch to ICS from a custom ROM. I just want to try it out, I'm currently on Bananacakes Holiraider. I have the US version of HTC Vivid if that helps. And if it is possible, how to do it.
Short answer yes you can. Many have done it successfully, including myself. You have to relock your bootloader to be able to install the RUU. Don't do it if you're on any other carrier but ATT.
Ah ok thanks, so just to be sure, and I'm aware I may sound like a pain the assholes, I have AT&T Vivid so I'm good, all I need to do is just relock my bootloader. Then download the RUU from a thread I saw earlier. Is it still possible to root on ICS?
Yes, I'm rooted with ICS. Since the rooted rom's have been removed from here you may have to get on Wildchilds site to get a rooted ICS rom. He has step by step instructions on how to flash it without issues. Essentially after the RUU install, you'll need to unlock the bootloader, flash recovery, flash boot.img, and flash the rom. You may be able to find PG's rom elsewhere on the internet but I don't know if everything he's done is offline. Hope this helps.
strose09 said:
Yes, I'm rooted with ICS. Since the rooted rom's have been removed from here you may have to get on Wildchilds site to get a rooted ICS rom. He has step by step instructions on how to flash it without issues. Essentially after the RUU install, you'll need to unlock the bootloader, flash recovery, flash boot.img, and flash the rom.
Click to expand...
Click to collapse
You can skip downloading the RUU if you want. If you're going with WC's ROM, he has a PH39IMG.zip packaged in it that contains the new HBoot. So basically you'll relock the bootloader, flash PH39IMG.zip in bootloader TWICE, unlock bootloader, fastboot flash boot.img and wcxrecovery.img, boot to recovery, flash ROM and you'll end up with WC's rooted ICS (more detailed instructions in his .zip)
Exactly what he said!
Thanks so much. Just a couple of questions (phobia of bricked phone). Flash the PH.zip file in fastboot? As in just boot to bootloader and it should automatically update? Then reboot to fastboot again? And for the boot image, use flash GUI? Same for recovery? Then flash Rom?
Sent from my HTC Raider X710e using XDA
bangorang said:
Thanks so much. Just a couple of questions (phobia of bricked phone). Flash the PH.zip file in fastboot? As in just boot to bootloader and it should automatically update? Then reboot to fastboot again? And for the boot image, use flash GUI? Same for recovery? Then flash Rom?
Sent from my HTC Raider X710e using XDA
Click to expand...
Click to collapse
Not quite. Ph flashes automatically in bootloader..TWICE. then you have to get it off of your sd, boot to hboot again, but this time choose fastboot. Plug in USB. Unlock. Fastboot flash boot boot.IMG. fastboot flash recovery wcxrecovery.IMG. back to bootloader. Choose recovery. Flash Rom from recovery
Sent from my HTC PH39100 using xda premium
Do you guys have a link to WildChild's ROM site?
I've got my Vivid Bootloader unlocked and with CWM 5.5.0.4 but can't get past the white HTC screen with Holicakes or anything else.
willgill said:
Do you guys have a link to WildChild's ROM site?
I've got my Vivid Bootloader unlocked and with CWM 5.5.0.4 but can't get past the white HTC screen with Holicakes or anything else.
Click to expand...
Click to collapse
Find one of his posts...its in his Sig. Are you flashing the boot.IMG before trying to flash the rom?
Sent from my HTC PH39100 using xda premium
Ok I got you on everything except the fastboot flashing boot.IMGs. I'm so sorry for the inconvenience but I just don't want to rage over a bricked phone. I was able to install custom roms and stuff, but I don't recall flashing from fastboot... Thank you again so much.
Sent from my HTC Raider X710e using XDA
Since we don't have S-Off, there a certain partitions that recovery can't write to (like the boot partition and recovery partition). Since this is the case, we have to flash custom recoveries and boot.img (which include the kernel) with fastboot. There is a GUI floating around that should flash boot.img as well, but it's not difficult to do with fastboot (I've never used the GUI so I can't speak first hand about it's effectiveness). In the ROM's .zip, you'll find boot.img. You need to extract this to the same location you have fastboot installed (in the sdk, it's in /platform-tools/). Once you have the boot.img in this directory, you need to navigate here in a command prompt. The easiest way to do this is to Shift+Click in this directory, and choose "Open command window here" Now you need to boot your phone to bootloader (power down, hold PWR+Vol- until hboot starts). Select Fastboot. Now plug your phone in and it will change to Fastboot USB. Enter the following command in the command prompt window:
fastboot flash boot boot.img
(Note: you can also flash a custom recovery here by issuing the following command, with the recovery.img in the fastboot directory
fastboot flash recovery nameofrecovery.img)
Press Enter. You will see it send, then write, then finish. Now on your phone select bootloader, then recovery. Now wipe data, cache, and Dalvik cache, then flash ROM
Recently, I had saved on my HDD before PirateGhost pulled it, his ICS rom, So I followed the diretions to flash the boot.img before flashing thr rom, so it installed and such, and when it went back to the recovery menu it said installed failed, but the actual program that launched o install the stuff said it was ok..Ok lets fast forward I reboot the device and it starts booting up, and shows the boot animation, then it will freeze and of course bootloop, but me being smart I did a backup before I installed anything and it still bootloops, it doesn't even get to the bootanimation... So this is where I start worrying. So I looked and try to revert back to stock just to see if it will work, I can't even lock my bootloader because it says something about error too many links.>.< I need help and any help is most appreciative!
Did you let the PH39IMG.zip install 2 times? Or did you try to update to the newest H-Boot before you re-locked your bootloader? I saw the same error about too many links when I tried to update H-Boot before I locked the bootloader. When you go into the bootloader what version of H-boot does it show?
I have Hboot 1.83.0014, and after i installed the PH39IMG, I installed a new kernel and a new rom too see if it would work and it booted up and everything it was working, so I tried to restart the phone to restore a backup I had and now my recovery won't even boot up, I can still access bootloader and such
Riomaru said:
I have Hboot 1.83.0014, and after i installed the PH39IMG, I installed a new kernel and a new rom too see if it would work and it booted up and everything it was working, so I tried to restart the phone to restore a backup I had and now my recovery won't even boot up, I can still access bootloader and such
Click to expand...
Click to collapse
Read the instructions again. You have the wrong hboot
Sent from my HTC PH39100 using xda premium
Riomaru said:
I have Hboot 1.83.0014, and after i installed the PH39IMG, I installed a new kernel and a new rom too see if it would work and it booted up and everything it was working, so I tried to restart the phone to restore a backup I had and now my recovery won't even boot up, I can still access bootloader and such
Click to expand...
Click to collapse
That's the old H-Boot. That's why the ICS ROM doesn't flash correctly. You need to lock your bootloader and use the PH39IMG.zip to install the new H-Boot. Ignore the error you get on the command line when relocking. You should get into the bootloader and it should say relocked and have a security warning of some kind. Just let it run the PH39IMG.zip and update. It will run once and turn your phone off. Boot back into the bootloader and let it update again. When it's done you will have to flash recovery again, then the boot.img, and then boot to recovery and flash the ROM.
pside15 said:
Just let it run the PH39IMG.zip and update. It will run once and turn your phone off. Boot back into the bootloader and let it update again. When it's done you will have to flash recovery again, then the boot.img, and then boot to recovery and flash the ROM.
Click to expand...
Click to collapse
The step I bolded isn't necessary. If you wait long enough (30-45 seconds?), the phone powers back on and boots into bootloader on it's own and completes the install without any action required on your part.
anthromatt said:
The step I bolded isn't necessary. If you wait long enough (30-45 seconds?), the phone powers back on and boots into bootloader on it's own and completes the install without any action required on your part.
Click to expand...
Click to collapse
Thanks for the info. I wasn't aware of that. I just booted back to the bootloader manually and everything worked well.
pside15 said:
Thanks for the info. I wasn't aware of that. I just booted back to the bootloader manually and everything worked well.
Click to expand...
Click to collapse
Yeah, I discovered that by accident after about 4 failed attempts to successfully flash. The last time I "forgot" to pull the battery after the phone powered off because I had gone into the kitchen to get coffee. When I returned, it had rebooted itself and was finishing the update.
I couldn't flash the recovery while it was locked so I had to unlock it, but currently I am flashing the rom and I will see what happens
I had success by flashing the RUU first then flashing the new recovery, then finally the Rum Float zip file.
Riomaru said:
I couldn't flash the recovery while it was locked so I had to unlock it, but currently I am flashing the rom and I will see what happens
Click to expand...
Click to collapse
Yes, that is true but you didn't complete the H-Boot update. ICS ROMs won't flash properly on the old H-boot. You need to lock the bootloader to use the PH39IMG.zip to update H-Boot then unlock and flash recovery and then ROM.
pside15 said:
That's the old H-Boot. That's why the ICS ROM doesn't flash correctly. You need to lock your bootloader and use the PH39IMG.zip to install the new H-Boot. Ignore the error you get on the command line when relocking. You should get into the bootloader and it should say relocked and have a security warning of some kind. Just let it run the PH39IMG.zip and update. It will run once and turn your phone off. Boot back into the bootloader and let it update again. When it's done you will have to flash recovery again, then the boot.img, and then boot to recovery and flash the ROM.
Click to expand...
Click to collapse
Ok that did it !!!! Thank so much
Riomaru said:
Ok that did it !!!! Thank so much
Click to expand...
Click to collapse
No problem. Glad you got everything worked out.
I have a soft-bricked Raider and looks like I am having the same problem, I have hboot 1.83.0014 and unlocked. a getver all shows the version-main to be 1.65.666.3 so I google that up and found this ICS image...
OTA_HOLIDAY_ICS_35_S_BM_3.38.666.2-1.65.666.3_release_255932wpop8vtj8tts3ou3.zip
http://forum.xda-developers.com/showthread.php?t=1498003
So it appear I need to lock my bootloader and update the hboot.
When I run oem lock this is what I get.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Unknown error))
finished. total time: 0.022s
I let it sit for 15 minutes but no change.
what do I need to do to get my bootloader relocked?
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Hi,
I got a big problem after i have unlock boot-loader.
after unlock boot loader i try to install OTA update 1.29.401.12 and i got an error, then the device freeze in this screen
sorry i can't insert the image, but its black screen and HTC logo in the middle and there are 4 triangle on the corners
Now i have to flash the stock RUU ROM right? if its yes i need the link of the ROM!!
thanx
Can you boot the device like normally? If so, just relock your device, install OTA and then unlock again. OTAs can't be flashed with unlocked bootloader or custom roms.
thom109 said:
Can you boot the device like normally? If so, just relock your device, install OTA and then unlock again. OTAs can't be flashed with unlocked bootloader or custom roms.
Click to expand...
Click to collapse
thank you?
my phone back to life
I need help with figuring how to solve my problem. Whenever I try to reboot it boots straight to hboot/fastboot. I can't update my system because of it. Can't unlock because it freezes at the screen where I choose to unlock or not. What should I do??
What have you done to your phone so far?
Have you unlocked your bootloader?
Have you installed TWRP Recovery?
Have you rooted your phone?
Have you flashed any new roms or kernels?
Can you still access your recovery? (TWRP or stock - stock is just black screen with a red triangle in the middle)
Please give a detailed description of the things you have done, the results of each of these things if any, and when your phone started rebooting straight to HBoot.
Also, is your phone the 32 bit US model, or the 64 bit Europian/Australian model?
There's still a chance your device's firmware is recoverable, but you probably shouldn't try anything until you get some advice from someone who has a lot of knowledge and a detailed description of how you ended up where you're at.
Good luck!
What have you done to your phone so far? I have unlocked it before, but end up re-locking it after failing to root it.
Have you unlocked your bootloader? I did and relocked it.
Have you installed TWRP Recovery? Couldn't and Can't
Have you rooted your phone? No
Have you flashed any new roms or kernels? No
Can you still access your recovery? (TWRP or stock - stock is just black screen with a red triangle in the middle) I can't enter recovery.
I have no .img files when entering hboot. I can't unlock because it freezes after choosing the unlock option. It shows entering recovery at the stop and a discalimer message at the botto and goes no where
How to fix the issue
The first thing is to do is to relock the boot loader by typing 'fastboot oem lock' and the appropriate RUU for your device and carrier and open the RUU and reflash the device and it will be good as new
bcbradley12 said:
The first thing is to do is to relock the boot loader by typing 'fastboot oem lock' and the appropriate RUU for your device and carrier and open the RUU and reflash the device and it will be good as new
Click to expand...
Click to collapse
You should not just lock the boot loader without first reinstalling the stock recovery! When you go to use the RUU if it doesn't see the stock recovery it's going to fail... First reinstall the stock recovery and then OEM lock then you can use the RUU!
P.S. I have no idea why you're replying to some post from 2014... This post was almost a year ago lmao...
You don't have to have stock recover I did it with TWRP Recovery and it put stock recovery for you
bcbradley12 said:
You don't have to have stock recover I did it with TWRP Recovery and it put stock recovery for you
Click to expand...
Click to collapse
OK but why are you replying to and worried about a post from a year ago?!?
my htc m7 got bricked and stuck in a bootloop after two days of being OTA updated to lollipop, knowing that it's S-on and bootloader locked, now when i try to unlock it through HTCDEv everything goes well but when the phone reboots it would still be locked and won't enter recovery! and when trying to flash a stock firmware instead of rebooting to bootloader (fastboot oem rebootRUU) the phone would reboot to system and stuck in boot loop, any solution to flash the phone back to normal?
If you are using Clockwork Mod, then there should be a way to get back into the rom flash option. Go into your "Power/Volume Down" page, and look for the option to flash from zip. Find the zip you used when ORIGINALLY flashing to your custom rom. Do not try to go to stock at first, work your way backwards. If you can get back to the working custom rom, from there you can use on screen functions to repair the phone back to stock.
yakie47 said:
my htc m7 got bricked and stuck in a bootloop after two days of being OTA updated to lollipop, knowing that it's S-on and bootloader locked, now when i try to unlock it through HTCDEv everything goes well but when the phone reboots it would still be locked and won't enter recovery! and when trying to flash a stock firmware instead of rebooting to bootloader (fastboot oem rebootRUU) the phone would reboot to system and stuck in boot loop, any solution to flash the phone back to normal?
Click to expand...
Click to collapse
Looks like you are having firmware or hardware issue. We often see this problem (not being able to unlock the bootloader) when the phone was relocked with a custom recovery still installed. But it doesn't seem to be your case since your phone is s-on and locked unless you tell me that you did re-locked the bootloader with a custom recovery installed...
Unfortunately the only walk around for this issue is to flash the same version stock firmware.zip in ruu mode which is not accessible in your case.
Why you can't access the ruu mode, I really don't know, it might confirm an firmware issue, maybe with the bootloader. Your not the first one stuck in that situation (not unlockable + ruu mode broken), its not common but you are not the first.
Btw is your phone a GPE or Sense variant? GPE variant have a well known bug which will prevent the bootloader to be unlocked. Does not apply to Sense variants.
I'm afraid there is nothing to do if you can't unlock or access ruu mode. Maybe a jtag repair could work or you'll have to send it for repair.
Sorry
ethanvallivue said:
If you are using Clockwork Mod, then there should be a way to get back into the rom flash option.
Click to expand...
Click to collapse
OP said he was bootloader locked so he can't use a custom recovery.
Go into your "Power/Volume Down" page, and look for the option to flash from zip.
Click to expand...
Click to collapse
There is no such option for HTC devices. To flash stock zip on the M7 you must access RUU mode, OP said RUU mode is broken...
Find the zip you used when ORIGINALLY flashing to your custom rom. Do not try to go to stock at first, work your way backwards. If you can get back to the working custom rom, from there you can use on screen functions to repair the phone back to stock.
Click to expand...
Click to collapse
Don't understand why you are talking about custom roms, did you read the OP?
I appreciate your responds guys and i believe the only option left is the jtag i guess..