So I just recently used sunshine in order to gain S-Off on my HTC One. I used adb and fastboot in order to flash twrp recovery onto it but it unfortunately won't load into recovery from the fastboot menu. It says at the top that it is entering recovery in pink like it should but then just sends me back to the Hboot menu. Any help would be greatly appreciated! I tried using the lastest twrp and twrp 2.7
Okay so i got TWRP installed but I can't flash a rom, they all just say that the zip file is corrupt???
Updating to the latest Twrp and doing the Error 7 fix worked perfectly! Sorry for the wasted time!
Related
Early today, I was working on a G2 trying to get it rooted with a custom ROM installed. I managed to root the phone and disable the bootloader security. From here, I attempted to install clockwork recovery via rom manager... here's where the disaster starts.
Everything seemed to be going well (no errors), so I tried to load a custom ROM. The Rom installation started but failed partway through. This is when I noticed that the clockwork recovery wasn't working properly. It was flickering and none of the options worked (screen just flashed or turned black if you selected anything). So at this point, the phone would not boot since the ROM installation didn't complete, and I had a buggy recovery image installed.
Unfortunately, the fun doesn't stop here. I figured that I should load the PC10IMG.zip and start from scratch... bad idea. This flashed the bootloader (relocking it) then failed-- leaving me with a bad ROM, bad recovery image, and a locked bootloader. Luckily for me, I was able to use adb via the buggy recovery to unlock the bootloader again.
At this point, I got a bit antsy and jumped the gun. I decided to use fastboot to erase and load a new recovery image. Unfortunately, I realized that I didn't have a recovery.img file to flash... just after I used the fastboot erase recovery command.
I'm hoping that someone here has a recovery.img file compatible with the T-Mobile G2 so I can flash the recovery partition with fastboot. If anyone has any better ideas I'm open to suggestions.
Thanks in advance for any help.
Install amon recovery. It's much better then clockword. Do it using adb
Sent from my HTC Hero using XDA App
Just an update. I couldn't get into adb but I was able to flash clockwork via fastboot. For whatever reason, the amon recovery would go through. Nevertheless, I installed cyanogen using clockwork and everything is gravy!
I had done the htc unlock method and all was fine, tried couple roms etc
the reading a few things I decided to try rom manager and of course let it load the newest clockwork recovery and now i cant get into recovery at all........
anyone help on this one??? if i try to load the latest pc186.img for twrp recovery it just tells me version is older and only option is to reboot device
metalmenance said:
I had done the htc unlock method and all was fine, tried couple roms etc
the reading a few things I decided to try rom manager and of course let it load the newest clockwork recovery and now i cant get into recovery at all........
anyone help on this one??? if i try to load the latest pc186.img for twrp recovery it just tells me version is older and only option is to reboot device
Click to expand...
Click to collapse
Go to twrp site and download the latest image which is 1.1.1.img and flash it using fastboot all should be well.
If you HTC unlocked, you have to flash everything other than ROMs through fastboot.
That means kernels, recoveries, splash screens, etc. have to flashed through fastboot.
In your case you would download the twrp 1.1 image and enter 'fastboot flash recovery twrp.img'
Is there a newer CWM (currently using 4) for those of us stuck with HBOOT 1.5?
And if so, where can I find it? I've searched but every recovery I try won't work with this crappy HTC Method.
lcars123 said:
Is there a newer CWM (currently using 4) for those of us stuck with HBOOT 1.5?
And if so, where can I find it? I've searched but every recovery I try won't work with this crappy HTC Method.
Click to expand...
Click to collapse
Have you tried TWRP? I'm htc unlocked 1.5 and it works fine for me. Try that or have a look at this.
lcars123 said:
I've searched but every recovery I try won't work with this crappy HTC Method.
Click to expand...
Click to collapse
In theory, the only issue should be HTC not unlocking the boot partition while booted in the standard recovery mode.
I'm s-off with revolutionary, but curious, what about the custom recovery's don't work for you? What error messages do the custom recovery's provide?
joeykrim said:
In theory, the only issue should be HTC not unlocking the boot partition while booted in the standard recovery mode.
I'm s-off with revolutionary, but curious, what about the custom recovery's don't work for you? What error messages do the custom recovery's provide?
Click to expand...
Click to collapse
I can't install the latest CWM Recovery. That is the main issue. I'm stuck with an outdated version. If I try to load it via Rom Manager, after trying to boot into recovery, i get the splash screen, a black screen, then the phone reboots. I've tried to pull it from the CWM website and flash it via fastboot and the same thing happens. Is there something that has to be modified for recovery to work when unlocked via the HTC method?
Is there a version of the latest CWM 5.0.2.0 that will work with the HTC unlock method on hboot 1.5? Anyone? Anyone?
I am on hboot 1.5 and have been able to flash different recoveries fine. So far I have used TWRP 1 & 2. You should be able to flash via bootloader which includes adb commands sent from cmd on your PC.
You need:
Android SDK (Install from Android site)
HTC ADB Drivers (should install automatic..if not google and find and install)
Put your desired .img (recovery) into the folder where ADB.EXE exists (android-sdk sub-directory)
Reboot into bootloader---->fastboot
RUN THIS COMMAND FROM YOUR PC WITH THE PHONE ATTACHED VIA USB CABLE cd c:/******* fastboot flash recovery recovery.img
where ******* is the path to ADB.EXE (same folder as .img file and ADB.EXE)
for example cd c:/android fastboot flash recovery recovery.img
hii i have a problem that i was in the recovery twrp. today i decided to put stock recovery. after i finished i tried to to boot to recovery and it didn't let me he only restarting. can somebody help me to to fix it.thanks in advanced.
this is for the sprint one max, not sure what you have but this has the stock recovery that you can re-flash from fastboot, http://forum.xda-developers.com/showthread.php?t=2705215
or you can just flash TWRP recovery back to it.
http://forum.xda-developers.com/showthread.php?t=2498746
mrkrowely said:
this is for the sprint one max, not sure what you have but this has the stock recovery that you can re-flash from fastboot, http://forum.xda-developers.com/showthread.php?t=2705215
or you can just flash TWRP recovery back to it.
http://forum.xda-developers.com/showthread.php?t=2498746
Click to expand...
Click to collapse
thanks man i did already tried to install stock recovery in fastboot it didn't work. and i have international version
i want the stock recovery back because i want to get update from htc
ah, i didn't use twrp to flash mine, i went into fastboot oem rebootRUU and flashed it there, my problem with the stock recovery is i can't find one for hboot 2.49, the one for 2.09 flashed, and loaded, but that was it, it would error out, maybe a google search for your t6ul___ version that is stated on your bootloader screen will find you an international one.
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
geek-x said:
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
Click to expand...
Click to collapse
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
geek-x said:
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
Click to expand...
Click to collapse
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
es0tericcha0s said:
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
Click to expand...
Click to collapse
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
geek-x said:
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
Click to expand...
Click to collapse
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
es0tericcha0s said:
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
Click to expand...
Click to collapse
I tried flashing the firmware.zip file from the thread but I got a FAILED: (remote: not allowed) error in command prompt at the end of the process, what did I do wrong?
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
UPDATE:
Thank you so much es0tericcha0s, I really appreciate the support, I got the /data mount issue fixed finally. I just had to flash an older twrp recovery image and then reflashed the new one in fastboot and I could then flash CM successfully.
I can't believe I finally unbricked this phone, its been bricked since Sunday. Once again, es0tericcha0s, Thank you!
geek-x said:
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
Click to expand...
Click to collapse
You might need to RUU back then. If you have issues with the RUU exe, then you can extract the rom.zip and install it like you did the firmware. There are quite a few tutorials on how to extract it, or there might already be a version floating around for your phone.