[Q] can't access Htc One recovery - AT&T HTC One (M7)

I finished unlocking my bootloader with the Hasoon 2000 HTC one tool kit and I flash the cwm recovery. I started to flash the elementalX kernals ,my first kernel. I tried to got back into recovery but I couldn't access it. I believe it is because I forgot to perm root my HTC One. I was to flash the supersu with hasoon 2000 before I begin flashing kernals and roms but I didn't... How can I fix this problem so I can access recovery

CrazyPhoneHacker said:
I finished unlocking my bootloader with the Hasoon 2000 HTC one tool kit and I flash the cwm recovery. I started to flash the elementalX kernals ,my first kernel. I tried to got back into recovery but I couldn't access it. I believe it is because I forgot to perm root my HTC One. I was to flash the supersu with hasoon 2000 before I begin flashing kernals and roms but I didn't... How can I fix this problem so I can access recovery
Click to expand...
Click to collapse
What recovery did you flash initially? I did CWM touch and I had the same problem. Use the toolkit and reflash recovery, but flash stock CWM this time. After you flash try again. It should work.

garment69 said:
What recovery did you flash initially? I did CWM touch and I had the same problem. Use the toolkit and reflash recovery, but flash stock CWM this time. After you flash try again. It should work.
Click to expand...
Click to collapse
I flash all the optionsexcept custom recovery to see if any of them would fix it but none of them helped

cwm working
CrazyPhoneHacker said:
I flash all the optionsexcept custom recovery to see if any of them would fix it but none of them helped
Click to expand...
Click to collapse
i use the tool to reboot into boot loader because i am retarded and cant do it with the volume key. i used this site http
wccftech.com/install_clockworkmod-recovery-on-htc-one-at-t/
downloaded fastboot from them and extraced to c:
downloaded cwm touch from the same page moved it to the extraced fastboot folder in c:
booted to boot loader from the tool used same comand prompt window
did cd c:\fastboot and followed step by stem had cwm touch and nandroid done 10 minutes.

Related

[Q] Stuck on HTC logo after flashing

my HH has an unique issue when i flashing another custom rom....
before i flashed i already done this :
wipe data/cache/dalvik 3x each of them.....
and after it finished to flash and reboot its stuck on HTC logo.
this issue encountered when i flash another custom rom except the synergy 3dvo from nightly....
please help me solve this problem....
thx b4
didit.here said:
my HH has an unique issue when i flashing another custom rom....
before i flashed i already done this :
wipe data/cache/dalvik 3x each of them.....
and after it finished to flash and reboot its stuck on HTC logo.
this issue encountered when i flash another custom rom except the synergy 3dvo from nightly....
please help me solve this problem....
thx b4
Click to expand...
Click to collapse
Sounds like your kernel is not getting flashed. If you used HTC's method to unlock you'll need to use fastboot to flash the boot.img
xHausx said:
Sounds like your kernel is not getting flashed. If you used HTC's method to unlock you'll need to use fastboot to flash the boot.img
Click to expand...
Click to collapse
yeah, im using unlock method... does it mean i have to run it in fastboot usb mode if i wanna flash??
my htc is in newest OTA and in hboot 1.500
didit.here said:
yeah, im using unlock method... does it mean i have to run it in fastboot usb mode if i wanna flash??
my htc is in newest OTA and in hboot 1.500
Click to expand...
Click to collapse
I've answered this type of question a few times in other posts. I've edited my answer from a few minutes ago to help answer your question. Feel free to post back if anything isn't clear!
http://forum.xda-developers.com/showpost.php?p=18807723&postcount=3
When booted into the custom recovery through the traditional methods, reboot recovery, bootloader -> recovery, etc., HTC unlock method does not unlock *kernel* write access but does unlock *system* write access.
The main issue around kernel write access is due to the HTC unlock method only allowing kernel write access in two modes:
1) Booted in normal Android mode. My application, Flash Image GUI, will flash any kernel .zip file with the HTC unlock method because it runs in normal android mode. HTC unlocks write access to the boot partition, where the kernel is stored, in normal Android mode. Flash Image GUI also properly loads the respective WiFi modules essentially eliminating this WiFi mismatch error.
2) Fastboot booted into the custom recovery using the following command: fastboot boot c:\android\cwm-recovery.img. HTC unlock method allows kernel write access while using fastboot boot of a custom recovery.
Hope that helps!
Click to expand...
Click to collapse
joeykrim said:
I've answered this type of question a few times in other posts. I've edited my answer from a few minutes ago to help answer your question. Feel free to post back if anything isn't clear!
http://forum.xda-developers.com/showpost.php?p=18807723&postcount=3
Click to expand...
Click to collapse
whoaa it was really helping me, thx man for the suggestion.....
i think i have to try it
sorry, im to noob in flashing method

[Q] CWM > v4 for HTC Unlock method

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

[Q] Installed wrong kernel through flash Image GUI

I have a EVO 3D with hboot 1.5 and I was trying to install a new ROM and instead of extracting kernel from that zip I think I browsed a wrong kernel and installed it through flash image GUI tool. Now, I am stock on recovery screen and none of the kernel or none of the roms that I try to install seem to work, none go past HTC screen. I have teamwin recovery installed. Please help.
peacefulcard said:
I have a EVO 3D with hboot 1.5 and I was trying to install a new ROM and instead of extracting kernel from that zip I think I browsed a wrong kernel and installed it through flash image GUI tool. Now, I am stock on recovery screen and none of the kernel or none of the roms that I try to install seem to work, none go past HTC screen. I have teamwin recovery installed. Please help.
Click to expand...
Click to collapse
You are going to need to use fastboot to reboot recovery and flash your rom. Instructions are here: http://forum.xda-developers.com/showpost.php?p=17083811&postcount=2
peacefulcard said:
I have a EVO 3D with hboot 1.5 and I was trying to install a new ROM and instead of extracting kernel from that zip I think I browsed a wrong kernel and installed it through flash image GUI tool. Now, I am stock on recovery screen and none of the kernel or none of the roms that I try to install seem to work, none go past HTC screen. I have teamwin recovery installed. Please help.
Click to expand...
Click to collapse
you'll have to use fastboot.
htc unlock method only unlocks kernel write access while in fastboot or android mode.
since you've loaded an incompatible/bad kernel, you aren't able to access android mode and the only option HTC has left you is fastboot mode.
in order to enter the recovery through fastboot mode, use the following command:
fastboot boot c:\downloads\recovery.img (either cwm or twrp will work).
good luck!
Thank you Sir!!!
Thank you both of you!!!

[Q] I can't flash kernel.

I have an EVO 3D GSM of Telstra with hboot 12. I unlocked an rooted. I can flash all cook rom. Howerver, I can' flash any custom kernel. It always notice a error status 7. I tried many different kernel, but it was not working. I also tried using the Image UI and I got error.
Someone help me please. I want to flash some kernel.
Thanks for helping.
Someone help me. I want to flash some karnel...
S-On dosen't allow flashing kernals, but to get past that u have to access Recovery from Fastboot. To know how to do this follow these steps.
Download this: http://www.mediafire.com/?g6ex57jvbobel07
Then Follow this:
1. Boot into Fastboot and connect your phone to the computer
2. In the Folder you downloaded Click Open cmd
3. Type fastboot boot recovery.img
4. When recovery boots, just flash the Kernal normaly
5. Enjoy!!!!
You can also use this method to install S-OFF roms,
Happy Flashing!!! XD
Cousie G said:
S-On dosen't allow flashing kernals, but to get past that u have to access Recovery from Fastboot. To know how to do this follow these steps.
Download this: http://www.mediafire.com/?g6ex57jvbobel07
Then Follow this:
1. Boot into Fastboot and connect your phone to the computer
2. In the Folder you downloaded Click Open cmd
3. Type fastboot boot recovery.img
4. When recovery boots, just flash the Kernal normaly
5. Enjoy!!!!
You can also use this method to install S-OFF roms,
Happy Flashing!!! XD
Click to expand...
Click to collapse
I knew this method before, and I did it but result is error status 7. SO SAD (
Is the kernel you're flashing compatible with that rom? I don't think you can flash just any 'ol kernel.
G.Newton said:
Is the kernel you're flashing compatible with that rom? I don't think you can flash just any 'ol kernel.
Click to expand...
Click to collapse
Can you show me how can I identify it?

Please help. Ran ota with custom recovery.

Problem solved. Thanks to everyone that responded. I really do appreciate it!!!!
What exactly did you flash? The Mainver error only relates to the kernel IIRC.
The only thing I tried to flash was the custom recovery after I accidentally ran the ota update with the custom recovery still on my phone. When I should've flashed back to the stock recovery before accepting the update. And now I can't get into custom recovery. When I try to reflash armon ra it won't take. I've lost root access even though I have superuser still on my phone.
shane8262000 said:
The only thing I tried to flash was the custom recovery after I accidentally ran the ota update with the custom recovery still on my phone. When I should've flashed back to the stock recovery before accepting the update. And now I can't get into custom recovery. When I try to reflash armon ra it won't take. I've lost root access even though I have superuser still on my phone.
Click to expand...
Click to collapse
how are you trying to reflash Amon Ra ? , what recovery do you boot into ? As long as your still unlocked you should be able to flash Amon Ra through Hboot it has nothing to do with root access at that point. Even odder that the OTA flashed through the custom recovery, thought it would error out and not take if it wasn't the stock recovery. Unless you ran Con's Stock rooted, but then you wouldn't have an issue with superuser or root access.
Should be able to flash stock recovery through fastboot relock and RUU then if you really are stuck. Otherwise , no reason you shouldn't be able to reflash Amon Ra and reroot through recovery.
Download THIS
I take it the phone can't boot up at all? Have your tried fastboot flashing the stock kernel?
mjh68 said:
how are you trying to reflash Amon Ra ? , what recovery do you boot into ? As long as your still unlocked you should be able to flash Amon Ra through Hboot it has nothing to do with root access at that point. Even odder that the OTA flashed through the custom recovery, thought it would error out and not take if it wasn't the stock recovery. Unless you ran Con's Stock rooted, but then you wouldn't have an issue with superuser or root access.
Should be able to flash stock recovery through fastboot relock and RUU then if you really are stuck. Otherwise , no reason you shouldn't be able to reflash Amon Ra and reroot through recovery.
Click to expand...
Click to collapse
I'm trying to flash it in hboot as ph98img. And when I go to recovery it seems to go to the stock recovery with the little phone and a green circle but shortly after it turns into the red triangle and phone symbol.
Try flashing the recovery in fastboot. Download the latest version of AmonRa here and extract the recovery-ra-vigor-3.13-gnm.img. Take that file and place it in the same file directory you place the tools to unlock your bootloader (needs to be in the same directory as fastboot.exe).
Put your phone into bootloader and connect to PC and flash the recovery-ra-vigor-3.13-gnm.img in fastboot using the command:
fastboot flash recovery recovery-ra-vigor-3.13-gnm.img
Marcismo55 said:
Download THIS
I take it the phone can't boot up at all? Have your tried fastboot flashing the stock kernel?
Click to expand...
Click to collapse
It will boot and everything runs fine, I just can't get into custom recovery or install custom recovery. And my apps that need superuser permissions won't be allowed even though I still have superuser installed on the phone.
shane8262000 said:
It will boot and everything runs fine, I just can't get into custom recovery or install custom recovery. And my apps that need superuser permissions won't be allowed even though I still have superuser installed on the phone.
Click to expand...
Click to collapse
So you cannot flash the recovery through fastboot?
Marcismo55 said:
So you cannot flash the recovery through fastboot?
Click to expand...
Click to collapse
Nope. It just won't take. I can try it again and tell you exactly what it says as an error if that will help.
Marcismo55 said:
Try flashing the recovery in fastboot. Download the latest version of AmonRa here and extract the recovery-ra-vigor-3.13-gnm.img. Take that file and place it in the same file directory you place the tools to unlock your bootloader (needs to be in the same directory as fastboot.exe).
Put your phone into bootloader and connect to PC and flash the recovery-ra-vigor-3.13-gnm.img in fastboot using the command:
fastboot flash recovery recovery-ra-vigor-3.13-gnm.img
Click to expand...
Click to collapse
I'll try that and get back with you.
shane8262000 said:
I'll try that and get back with you.
Click to expand...
Click to collapse
Marcismo55 said:
Try flashing the recovery in fastboot. Download the latest version of AmonRa here and extract the recovery-ra-vigor-3.13-gnm.img. Take that file and place it in the same file directory you place the tools to unlock your bootloader (needs to be in the same directory as fastboot.exe).
Put your phone into bootloader and connect to PC and flash the recovery-ra-vigor-3.13-gnm.img in fastboot using the command:
fastboot flash recovery recovery-ra-vigor-3.13-gnm.img
Click to expand...
Click to collapse
Hey, when I download that file from your link, it is in .txt format. Am I missing something here?
Marcismo55 said:
Try flashing the recovery in fastboot. Download the latest version of AmonRa here and extract the recovery-ra-vigor-3.13-gnm.img. Take that file and place it in the same file directory you place the tools to unlock your bootloader (needs to be in the same directory as fastboot.exe).
Put your phone into bootloader and connect to PC and flash the recovery-ra-vigor-3.13-gnm.img in fastboot using the command:
fastboot flash recovery recovery-ra-vigor-3.13-gnm.img
Click to expand...
Click to collapse
Problem solved. Thank you very much!!!!
mjh68 said:
how are you trying to reflash Amon Ra ? , what recovery do you boot into ? As long as your still unlocked you should be able to flash Amon Ra through Hboot it has nothing to do with root access at that point. Even odder that the OTA flashed through the custom recovery, thought it would error out and not take if it wasn't the stock recovery. Unless you ran Con's Stock rooted, but then you wouldn't have an issue with superuser or root access.
Should be able to flash stock recovery through fastboot relock and RUU then if you really are stuck. Otherwise , no reason you shouldn't be able to reflash Amon Ra and reroot through recovery.
Click to expand...
Click to collapse
Thank you for the help!
Nice! Glad to help

Categories

Resources