[Q] Can't boot into recovery HTC one - One (M7) Q&A, Help & Troubleshooting

Hi -
Thanks for any help in advance. I'm a bit of a rookie round here, I've rooted and flashed my past 3 HTC phones but taken the easy route every time.
But today, I've used ADB commands to flash the revone binary and unlock and get s-off on my HTC one m7. It took me several tries, but it eventually worked (or at least said successful). So my HBOOT 1.44 says UNLOCKED & S-OFF.
So onto the next step. fastboot flash recovery recoverytwrp.img
...
Another success!
So, I reboot into bootloader and prompt recovery boot like I'm about to get HAM on twrp and flash some superuser files. It shows me a developer screen full of red print saying that it's booting into recovery, and then after a while, it just rebooted back into system.
It does this every time. I reflashed the image, I flashed the stock image, I tried the hansoon tool. each time I can't actually get into the recovery.
So this is where I'm stuck. Why can't I get anywhere with this?
EDIT & ANSWER;
Sprint phone needed Sprint TWRP image

Have you tried
fastboot erase cache

BenPope said:
Have you tried
fastboot erase cache
Click to expand...
Click to collapse
This.
Just do evrything again until you finish installing custom recoveries. Before rebooting, erase the cache with "fastboot erase cache"

ryryzz said:
This.
Just do evrything again until you finish installing custom recoveries. Before rebooting, erase the cache with "fastboot erase cache"
Click to expand...
Click to collapse
Gave that all a shot all over again. Still can't boot into recovery

Is fast boot off?

Use the original cable your One came with, go into bootloader power/vol - then open a cmd window
Now connect the One with your computer, don't use a USB 3.0 connection, and a different one then before.
In bootloader choose fastboot, that should change to fastboot USB
In cmd window point to your fastboot directory where you also copied the recovery to, I would try CWM touch for now.
Type cd c:\fastboot (or what your toolfolder is called)
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
That installs the recovery, you can select it in bootloader abd boot into it.
Sent from my HTC One using xda premium
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
BenPope said:
Is fast boot off?
Click to expand...
Click to collapse
You mean the fastboot option under Power Settings is unticked when booted up normally?
Sent from my HTC One using xda premium

hardstuffmuc said:
Use the original cable your One came with, go into bootloader power/vol - then open a cmd window
Now connect the One with your computer, don't use a USB 3.0 connection, and a different one then before.
In bootloader choose fastboot, that should change to fastboot USB
In cmd window point to your fastboot directory where you also copied the recovery to, I would try CWM touch for now.
Type cd c:\fastboot (or what your toolfolder is called)
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
That installs the recovery, you can select it in bootloader abd boot into it.
Sent from my HTC One using xda premium
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
You mean the fastboot option under Power Settings is unticked when booted up normally?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Same deal. On it's way to booting into recovery it goes blank, resets and reboots into system

C:\adt\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.078s]
finished. total time: 0.078s
C:\adt\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7422 KB)...
OKAY [ 1.139s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.778s
C:\adt\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\adt\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
There's the last log - and then on it's way to recovery there's a red disclaimer and a pink text saying "Entering Recovery"...then after 20 seconds it resets

Did you try various recovery (versions) ? May be , you just have corrupted recovery image.

tash2013 said:
Did you try various recovery (versions) ? May be , you just have corrupted recovery image.
Click to expand...
Click to collapse
at this point I've tried stock, twrp and cwm. All with the same results

Jman12000 said:
at this point I've tried stock, twrp and cwm. All with the same results
Click to expand...
Click to collapse
Ok , I see mysterious problem ))
Try, remaining unlocked, go back to s-on (you can always take s-off again) and check your recovery (enter and flashing) under s-on.

tash2013 said:
Ok , I see mysterious problem ))
Try, remaining unlocked, go back to s-on (you can always take s-off again) and check your recovery (enter and flashing) under s-on.
Click to expand...
Click to collapse
Is that something I can do with the revone binary? To be honest, I have no idea how to turn security back on. I can relock it and that may be about it.
I stumbled upon another thread, shares a common theme as my issue, but with a different twist. Using a superboot.img as a rooting method instead of flashing it via recovery. It somewhere says that the boot.img needs to be flashed as well, however I can't find a decent boot.img to flash. The superboot tool seems like unproven territory right now.
Here's the other thread, I've leafed through it and found no determinable answer for my particular issue.
http://forum.xda-developers.com/showthread.php?p=39852757#post39852757

Do not apply revone to return s-on!
Use fastboot by "fastboot oem writesecureflag 3".
Be convinced that bootloader is unlocked before return to s-on.
Regarding your issue: I suspect that a certain code in HBOOT tries to install TAMPERED flag when sees custom recovery, but isn't able to do it correctly because s-off (bypassing security) and a certain mistake or exception conducts to reset phone.

Jman12000 said:
Hi -
Thanks for any help in advance. I'm a bit of a rookie round here, I've rooted and flashed my past 3 HTC phones but taken the easy route every time.
But today, I've used ADB commands to flash the revone binary and unlock and get s-off on my HTC one m7. It took me several tries, but it eventually worked (or at least said successful). So my HBOOT 1.44 says UNLOCKED & S-OFF.
So onto the next step. fastboot flash recovery recoverytwrp.img
...
Another success!
So, I reboot into bootloader and prompt recovery boot like I'm about to get HAM on twrp and flash some superuser files. It shows me a developer screen full of red print saying that it's booting into recovery, and then after a while, it just rebooted back into system.
It does this every time. I reflashed the image, I flashed the stock image, I tried the hansoon tool. each time I can't actually get into the recovery.
So this is where I'm stuck. Why can't I get anywhere with this?
Click to expand...
Click to collapse
try to install recovery again
you can download recovery from here
http://www.clockworkmod.com/rommanager

tash2013 said:
Do not apply revone to return s-on!
Use fastboot by "fastboot oem writesecureflag 3".
Be convinced that bootloader is unlocked before return to s-on.
Regarding your issue: I suspect that a certain code in HBOOT tries to install TAMPERED flag when sees custom recovery, but isn't able to do it correctly because s-off (bypassing security) and a certain mistake or exception conducts to reset phone.
Click to expand...
Click to collapse
Code:
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fa
stboot oem writesecureflag 3
...
(bootloader) writesecureflag: partitions siganture pass
OKAY [ 1.665s]
finished. total time: 1.666s
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fa
stboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.045s]
finished. total time: 0.046s
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
error: device not found
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
So here's where I'm at
Right now I've done all the above, I've got a *** TAMPERED *** and ***UNLOCKED*** and S-ON
I've been through 4 boots, 2 of them attempts to get to recovery. Now instead of recovery rebooting into system, it just shuts off now.
Where do you think I go from here?

I've just skimmed through the posts and didn't see this mentioned
If you are still able to boot into the system, download either GooManager (for TWRP) or RomManager (for CWM) and use either of those apps to install recovery. Once done, you can use the app to boot into recovery instead of the fancy ADB commands or button presses.

Jman12000 said:
So here's where I'm at
Right now I've done all the above, I've got a *** TAMPERED *** and ***UNLOCKED*** and S-ON
I've been through 4 boots, 2 of them attempts to get to recovery. Now instead of recovery rebooting into system, it just shuts off now.
Where do you think I go from here?
Click to expand...
Click to collapse
This topic seems like your problem :
http://forum.xda-developers.com/showthread.php?t=2328983&page=3
The man resolved this by flashing the same recovery many many times.
And more.. Please print here your recovery flashing process

tash2013 said:
This topic seems like your problem :
http://forum.xda-developers.com/showthread.php?t=2328983&page=3
The man resolved this by flashing the same recovery many many times.
And more.. Please print here your recovery flashing process
Click to expand...
Click to collapse
So both that method through ADB shell and GooManager require root. Every rooting method requires recovery, so I don't have perm root yet.

You quoted me, but answered not to me.
Read a post #26 from my link above

Possible Solution
Hello I have the same problem and the solution was:
1. Settings - Energy- Fastboot uncheked
2. Flash Recovery usin one all-in-one-kit
3. Erase Cache 3 times
4. Unplug to PC, and load into system normal
5. Turn off phone - via stock menu NOT FORCE TO OFF pressing the off button
6. Wait 2 minutes, and boot into HBOOT - Power + Volume(-) pressing
7. Choose recovery
Ready.. May these work for you! Let me know

Related

ICS upgrade - boot loop - can't fix - bricked?

I have searched the forums, and I can not find the answer to my specific situation. Please forgive me if it is there somewhere. The story…….
- last working ROM was VIVO ICS official, RUU installed. (RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed.exe). HBOOT was changed to 2.02 S-ON, bootloader locked. I unlocked via HTCdev. Before this I had IceColdSandwich 8.1.1, ENG Hboot S-OFF. I had originally used the GB downgrade ROM to S-OFF, and restored IceCold backup after this.
- I wanted to be S-OFF again, and so tried installing this zip using CWM Recovery, following the advice of tpbklake:
vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip Version 1.1
(from http://forum.xda-developers.com/showthread.php?t=1756500&page=1)​
- now boot loop. I tried reinstalling other ROMs which I have successfully installed in the past (GB downgrade, stock ICS), and also restore various backups, but all result in boot loop (stuck on white HTC screen). Each time I would use CWM Recovery to clear dalvik, cache etc.
- I have now followed 'fix' instructions in that same thread, ie. :
1. Download the file lib.zip from here: http://bit.ly/PwK4BH
2. Unzip the lib.img and place it on your PC where you have fastboot.exe installed.
3. Boot into FASTBOOT USB mode and then enter the following command:
fastboot flash lib lib.img
4. Download the file format_lib_update.zip from here: http://bit.ly/RIpEUL
5. Copy it to your SD card.
6. Boot into recovery and then install format_lib_update.zip
7. While in recovery format the SYSTEM partition.
8. Then reinstall vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip​
But at step 3 I get the following:
C:\adb>fastboot flash lib lib.img
sending 'lib' (155648 KB)...
OKAY [ 27.553s]
writing 'lib'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 52.417s
C:\adb>​
Please help! I’m close to considering myself properly bricked, and using that as an excuse to go and buy a OneX.
jcr67 said:
I have searched the forums, and I can not find the answer to my specific situation. Please forgive me if it is there somewhere. The story…….
- last working ROM was VIVO ICS official, RUU installed. (RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed.exe). HBOOT was changed to 2.02 S-ON, bootloader locked. I unlocked via HTCdev. Before this I had IceColdSandwich 8.1.1, ENG Hboot S-OFF. I had originally used the GB downgrade ROM to S-OFF, and restored IceCold backup after this.
- I wanted to be S-OFF again, and so tried installing this zip using CWM Recovery, following the advice of tpbklake:
vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip Version 1.1
(from http://forum.xda-developers.com/showthread.php?t=1756500&page=1)​
- now boot loop. I tried reinstalling other ROMs which I have successfully installed in the past (GB downgrade, stock ICS), and also restore various backups, but all result in boot loop (stuck on white HTC screen). Each time I would use CWM Recovery to clear dalvik, cache etc.
- I have now followed 'fix' instructions in that same thread, ie. :
1. Download the file lib.zip from here: http://bit.ly/PwK4BH
2. Unzip the lib.img and place it on your PC where you have fastboot.exe installed.
3. Boot into FASTBOOT USB mode and then enter the following command:
fastboot flash lib lib.img
4. Download the file format_lib_update.zip from here: http://bit.ly/RIpEUL
5. Copy it to your SD card.
6. Boot into recovery and then install format_lib_update.zip
7. While in recovery format the SYSTEM partition.
8. Then reinstall vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip​
But at step 3 I get the following:
C:\adb>fastboot flash lib lib.img
sending 'lib' (155648 KB)...
OKAY [ 27.553s]
writing 'lib'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 52.417s
C:\adb>​
Please help! I’m close to considering myself properly bricked, and using that as an excuse to go and buy a OneX.
Click to expand...
Click to collapse
OK, so what is the state of your HBOOT? Are you still HBOOT 2.02.0002 UNLOCKED?
When you are using the an unlocked HTC HBOOT and you flash a custom ROM in CWM, you then manually have to extract the boot.img file from that ROM's zip file and flash it manually in FASTBOOT USB mode. If you don't do that, you will get a boot loop.
What you need to do if you can still get into CWM and the bootloader is still UNLOCKED is reflash that ROM again and then flash the boot.img file in FASTBOOT mode and you should be ok.
tpbklake said:
OK, so what is the state of your HBOOT? Are you still HBOOT 2.02.0002 UNLOCKED? .
Click to expand...
Click to collapse
yep
tpbklake said:
When you are using the an unlocked HTC HBOOT and you flash a custom ROM in CWM, you then manually have to extract the boot.img file from that ROM's zip file and flash it manually in FASTBOOT USB mode. If you don't do that, you will get a boot loop.
What you need to do if you can still get into CWM and the bootloader is still UNLOCKED is reflash that ROM again and then flash the boot.img file in FASTBOOT mode and you should be ok.
Click to expand...
Click to collapse
I should have mentioned, I already tried that. However, I will try it one more time. I tried so many things - if I try it again in isolation, I will be 100% sure I am telling you the truth.
Thanks for the reply.
jcr67 said:
I should have mentioned, I already tried that. However, I will try it one more time. I tried so many things - if I try it again in isolation, I will be 100% sure I am telling you the truth.
Thanks for the reply.
Click to expand...
Click to collapse
OK, I tried it again.
- In CWM Recovery, install from zip, chose 'vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip'
- It completed successfuly (rather quickly)
- extracted boot.img from that zip, places in adb/fastboot folder on PC
- Rebooted phone into bootloader USB
- On PC, executed 'fastboot boot boot.img'
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.328s]
booting...
OKAY [ 0.000s]
finished. total time: 1.328s​
- it rebooted automatically, and now stuck on white HTC screen for last 10 minutes
jcr67 said:
OK, I tried it again.
- In CWM Recovery, install from zip, chose 'vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip'
- It completed successfuly (rather quickly)
- extracted boot.img from that zip, places in adb/fastboot folder on PC
- Rebooted phone into bootloader USB
- On PC, executed 'fastboot boot boot.img'
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 1.328s]
booting...
OKAY [ 0.000s]
finished. total time: 1.328s​
- it rebooted automatically, and now stuck on white HTC screen for last 10 minutes
Click to expand...
Click to collapse
Instead of "fastboot boot boot.img"
it should be
"fastboot flash boot boot.img"
Try that and see how it goes
Cheers
Drugzy said:
Instead of "fastboot boot boot.img"
it should be
"fastboot flash boot boot.img"
Try that and see how it goes
Cheers
Click to expand...
Click to collapse
Aaaarghh....silly me
However, same result. Still white screen after 10min
C:\adb>fastboot flash boot boot.img
sending 'boot' (3824 KB)...
OKAY [ 1.187s]
writing 'boot'...
OKAY [ 1.234s]
finished. total time: 2.422s​
jcr67 said:
Aaaarghh....silly me
However, same result. Still white screen after 10min
C:\adb>fastboot flash boot boot.img
sending 'boot' (3824 KB)...
OKAY [ 1.187s]
writing 'boot'...
OKAY [ 1.234s]
finished. total time: 2.422s​
Click to expand...
Click to collapse
Well then you can always relock the bootloader and then run the 4.10.405.1 RUU like you did originally. Then you can unlock the bootloader since you already have the unlock_code.bin file.
tpbklake said:
Well then you can always relock the bootloader and then run the 4.10.405.1 RUU like you did originally. Then you can unlock the bootloader since you already have the unlock_code.bin file.
Click to expand...
Click to collapse
Then I will end up where I was in the first place? Oh well, at least I could use the phone.
Anyhow......
C:\adb>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.312s​
HBOOT now says:
*** RELOCKED ***
*** Security Warning ***
jcr67 said:
Then I will end up where I was in the first place? Oh well, at least I could use the phone.
Anyhow......
C:\adb>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.312s​
Click to expand...
Click to collapse
Once you get back to that point, unlock the bootloader, install ClockworkMod and then flash su-3.0.7-efghi.zip to root the official ROM. Then you should be able to rerun the downgrade process to get back to S-OFF.
Reinstall the HTC ruu
Sent from my HTC Raider X710e using xda app-developers app
tpbklake said:
Once you get back to that point, unlock the bootloader, install ClockworkMod and then flash su-3.0.7-efghi.zip to root the official ROM. Then you should be able to rerun the downgrade process to get back to S-OFF.
Click to expand...
Click to collapse
But my relock resulted in a security warning, as shown above. Are you telling me that's fine, and I can go ahead with RUU? Thanks
jcr67 said:
But my relock resulted in a security warning, as shown above. Are you telling me that's fine, and I can go ahead with RUU? Thanks
Click to expand...
Click to collapse
Yes you should be ok.
tpbklake said:
Yes you should be ok.
Click to expand...
Click to collapse
yep he will be , during my downgrade i had to relock with security warning and ruu fixed it all
tpbklake said:
Yes you should be ok.
Click to expand...
Click to collapse
Thanks very much. The stock ICS RUU has now installed successfully. I guess when I originally tried to reinstall it, I had left out the 'RELOCK' step, which is why it failed.
So now I am back to the start (stock ICS + HBOOT 2.02 S-ON), and want to get S-OFF and install your ROM zip. ,What I originally intended to do to get S-OFF was:
1) Unlock the bootloader, flash CWM Recovery, flash SU
2) Run downgrade GB RUU
3) S-off with Revolutionary
4) Install Blackrose HBOOT
5) Install your vivo_signed_WWE_4.10.405.1_ICS_SENSE36_5.zip
But step 2) failed with an unknown error. (I then tried to install your zip, and the rest is the sad history.....).
So what caused step 2 to fail? Did I need to relock the bootloader first?
Many thanks for your help, tpbklake
Did you use this script to downgrade and then flash gb ruu?
http://forum.xda-developers.com/showthread.php?t=1373697
If so run it and post up the results. It may not.be downgrading your mainver correctly.
Sent from my HTC Incredible S using xda app-developers app
Drugzy said:
Did you use this script to downgrade and then flash gb ruu?
http://forum.xda-developers.com/showthread.php?t=1373697
If so run it and post up the results. It may not.be downgrading your mainver correctly. p
Click to expand...
Click to collapse
That's it. HBOOT is remaining at 2.02.0002 after runme.cmd
Is the device rooted?
y OR n:y
Waiting for device to connect
Device found
Pushing misc_version
2455 KB/s (367096 bytes in 0.146s)
Correcting permissions
Downgrading main version
--set_version set. VERSION will be changed to: 2.00.000.0
Patching and backing up misc partition...
Error opening input file.
Cleaning temp files​
Any ideas anyone?
What is the status of your bootloader? Is it locked, unlocked or relocked? If it is locked you may have to answer n to is the phone rooted to give temp root. If not on page 76 of this post there is the same issue.
http://forum.xda-developers.com/showthread.php?t=1373697
And fyi it will not change the h boot version, only the main ver which is reported at the end of the script.
Cheers
Sent from my HTC Incredible S using xda app-developers app
Drugzy said:
What is the status of your bootloader? Is it locked, unlocked or relocked? If it is locked you may have to answer n to is the phone rooted to give temp root. If not on page 76 of this post there is the same issue.
http://forum.xda-developers.com/showthread.php?t=1373697
And fyi it will not change the h boot version, only the main ver which is reported at the end of the script.
Cheers
Click to expand...
Click to collapse
No, I'm unlocked and rooted
Does the stock ruu have superuser installed? If it does I'm outta ideas.
Sent from my HTC Incredible S using xda app-developers app
---------- Post added at 07:58 PM ---------- Previous post was at 07:40 PM ----------
One more thing, I would try flashing another ROM, i came from Niks Sense 4a rom, and the script worked with no issues.
Remember you will need to manually flash the boot.img of the rom as you are S-ON.
jcr67 said:
No, I'm unlocked and rooted
Click to expand...
Click to collapse
Open a command window and then type in the command:
adb shell
If you get a # prompt then your ROM is rooted correctly and the script should run. If it doesn't then the ROM isn't properly rooted and the script will fail.

Blackrose installed but impossible to install recovery + TexasIce

Hi guys,
I need your help, I have a Nexus One, with Cyanogenmod 7 and Clockwork recovery and decided to give ICS a try so I have been trying to install TexasIce and can't install the recovery.
First I installed Blackrose using the manual method, because the blackrose.exe will stop at "waiting for device".
fastboot oem unlock
fastboot boot go35.lol (checked and it is the right .lol for my previous HBOOT 0.35.0017)
then, at the big frozen X:
fastboot flash hboot hboot_brcrust_210-8-218-ICS.nb0
fastboot reboot-bootloader
and the phone reboots to hboot and I can see the
* BlackRose......
TexasICS-210/8/218
NEXUSONE PVT ENG S-OFF
HBOOT-7.35.5017 (PV9910000)
MICROP-0b15
TOUCH.....
RADIO-5.12-00-00
Then choose Fastboot and confirm with the trackball, plug the USB cable and it shows FASTBOOT USB, and "fastboot devices" finds the phone.
The problem comes then when I try
fastboot flash recovery recovery-clockwork-5.0.2.0-passion.img
It shows:
sending 'recovery' (3058 KB).
FAILED (data transfer failure (Unknown error))
finished. total time: 0.017s
And the phone is frozen, I have to remove the cable and battery.
fastboot boot recovery-clockwork-5.0.2.0-passion.img also fails, and trying with RA recovery fails too.
¿What can I do?
If it helps, I have only been able to flash the new blackrose for jellybean found here.
http://forum.xda-developers.com/showthread.php?t=1762790
BTW I am trying without sim or microSD card inserted
princado said:
If it helps, I have only been able to flash the new blackrose for jellybean found here.
http://forum.xda-developers.com/showthread.php?t=1762790
BTW I am trying without sim or microSD card inserted
Click to expand...
Click to collapse
princado said:
Hi guys,
I need your help, I have a Nexus One, with Cyanogenmod 7 and Clockwork recovery and decided to give ICS a try so I have been trying to install TexasIce and can't install the recovery.
First I installed Blackrose using the manual method, because the blackrose.exe will stop at "waiting for device".
fastboot oem unlock
fastboot boot go35.lol (checked and it is the right .lol for my previous HBOOT 0.35.0017)
then, at the big frozen X:
fastboot flash hboot hboot_brcrust_210-8-218-ICS.nb0
fastboot reboot-bootloader
and the phone reboots to hboot and I can see the
* BlackRose......
TexasICS-210/8/218
NEXUSONE PVT ENG S-OFF
HBOOT-7.35.5017 (PV9910000)
MICROP-0b15
TOUCH.....
RADIO-5.12-00-00
Then choose Fastboot and confirm with the trackball, plug the USB cable and it shows FASTBOOT USB, and "fastboot devices" finds the phone.
The problem comes then when I try
fastboot flash recovery recovery-clockwork-5.0.2.0-passion.img
It shows:
sending 'recovery' (3058 KB).
FAILED (data transfer failure (Unknown error))
finished. total time: 0.017s
And the phone is frozen, I have to remove the cable and battery.
fastboot boot recovery-clockwork-5.0.2.0-passion.img also fails, and trying with RA recovery fails too.
¿What can I do?
Click to expand...
Click to collapse
When you try to change partition layout between HBOOTs, you need to format (a.k.a erase) all partitions except SD card before flashing a new recovery or custom ROM. Try this:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase cache
fastboot erase recovery
Then flash new recovery then flash the custom ROM. And, BTW, don't use CWM because it could corrupt your SD card. Use either Amon_RA or 4EXT recovery.
Oh sorry I forgot to reply again!!
I finally managed to fix it. Somehow, the recovery and system got corrupted and won't boot. I could only boot to hboot or fastboot, and trying to flash anything would result on locking the phone. I could fix it by getting standard google image and putting it as PASSIMG.zip on the root of the SD so hboot restored the phone except blackrose hboot. Then the phone booted again and I could flash a recovery normally from fastboot

[Q] Problem Installing a Custom Recovery

I'm trying to install TWRP recovery via CMD but I'm having problems. As of now, I've done the following:
Downloaded TWRP 2.5.0.0
Placed the file in the same folder used to unlock the phone that also contains fastboot
With the phone connected, i run the following command
Code:
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.img
In the prompt window, I received the following results "< waiting for device >" but i don't see anything progress thereafter on the phone or prompt window
I tried to reboot into recovery and now receive a red exclamation point within a triangle that's over a phone. See attached photo.
Thereafter, I have to force restart
Does anyone have any advice?
UPDATE
I was finally able to write the recovery on the phone. However, now when I try to boot into recovery, it fails to load recovery and boots as a normal restart.
UPDATE
I tried to reflash TWRP again. Following the reflash, I also deleted the cache using the following command
Code:
fastboot erase cache
I then reboot the bootloader using
Code:
fastboot reboot-bootloader
This time around, after making an attempt to boot into recovery, I would get the message "Entering Recovery...". However, after a few seconds, the phone would turn off.
Thereafter, I tried to flash the OEM recovery using the steps above and I'm still have the same problem. Is my recovery partition corrupt?
I read that it helps to erase the recovery partition prior to flashing over an existing recovery. I tired the command
Code:
fastboot erase recovery
But I receive the following results
Code:
c:\Android>fastboot erase recovery
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.001s
If erasing the recovery partition is good practice, how do I go about doing it?
I'm having the same problem.
I can successfully flash the TWRP 2.5.0.0 recovery ROM, but when I try to load into the recovery to flash a custom ROM, I see a flash of purple text on white background, then the screen goes black and boots normally.
Any help would be appreciated.
Ok... I had some issues when installing recovery so this is what I did...
Be advised that next steps are highly risky and that it might have worked for me but I take no responsibility if you break your device
After following almost all the instructions, I read that someone flashed the recovery to the boot partition. So I did that.
fastboot flash boot recovery.img
Now, after this, the device went to a constant bootloop and suddenly the recovery appeared.
Also, I erased the cache from fastboot with next command:
fastboot erase cache
I'm planning to post the procedure I've followed but I don't have much time lately.
Will try to do it as soon as possible.
Best regards.
---------- Post added at 12:22 AM ---------- Previous post was at 12:21 AM ----------
brianhill1980 said:
I'm having the same problem.
I can successfully flash the TWRP 2.5.0.0 recovery ROM, but when I try to load into the recovery to flash a custom ROM, I see a flash of purple text on white background, then the screen goes black and boots normally.
Any help would be appreciated.
Click to expand...
Click to collapse
For you mate, go into fastboot run:
fastboot erase cache
Then try again.
:No-Frost: said:
For you mate, go into fastboot run:
fastboot erase cache
Then try again.
Click to expand...
Click to collapse
You sir are my hero. Thank you!
I rebooted and went into Fastboot. Ran "fastboot erase cache". Then re-flashed the recovery image. Then ran the command "fastboot erase cache" again. Then restarted the bootloader, then went into the recovery and it worked.
brianhill1980 said:
You sir are my hero. Thank you!
I rebooted and went into Fastboot. Ran "fastboot erase cache". Then re-flashed the recovery image. Then ran the command "fastboot erase cache" again. Then restarted the bootloader, then went into the recovery and it worked.
Click to expand...
Click to collapse
Glad to help mate and glad to know you can go into recovery now
pwr2wh8 said:
UPDATE
I tried to reflash TWRP again. Following the reflash, I also deleted the cache using the following command
Code:
fastboot erase cache
I then reboot the bootloader using
Code:
fastboot reboot-bootloader
This time around, after making an attempt to boot into recovery, I would get the message "Entering Recovery...". However, after a few seconds, the phone would turn off.
Thereafter, I tried to flash the OEM recovery using the steps above and I'm still have the same problem. Is my recovery partition corrupt?
Click to expand...
Click to collapse
Do you have the Sprint version? I have Sprint and I was running into the same issue. After searching everywhere for this issue, I came across this post: http://forum.xda-developers.com/showpost.php?p=40828046&postcount=240
Here's the link to the file you need: http://techerrata.com/browse/twrp2/m7wls
I flashed this recovery img and it finally worked after all the other ones failed in the same way you described.
Hope it works for you!

[Q] Help getting HTC One Stock

Hello xda community, I'd like to start with saying all the work done on this forum for open-source, freeware, and general android tweaks is awesome! Thank you.
So awesome in fact that I got a little bit ahead of myself with my new "Sprint HTC One". I followed this guide http://forum.xda-developers.com/showthread.php?t=2244060 to Unlock the bootloader, and root my phone. I then went a step further and wanted to flash a custom Rom. I followed this video, but strayed a little bit (whoops!). I went into twrp recovery, and flashed the "Beanstalk" super custom 4.3 (9/24/2013), along with smw6180_superwipe, and 4.3 gapps.
This actually was working for about 4 days, but now it won't connect to the mobile network even when toggling on and off airplane mode (A temp fix for the ROM). I went ahead and looked for solutions, namely to just get back to stock to see if the problem is bigger than just custom ROM. I relocked my bootloader, following http://www.youtube.com/watch?v=0WWNZpaQBh8&list=PLE395F615E026133D&index=11 Thus running into my current issue of Error 140 when trying to flash the RUU.
I'm asking anyone that could help, to offer suggestions on getting my phone back to stock. I would also like a couple suggestions for more stable ROM's (again, i knew what i getting into; ie disclaimers) that offer cool customization!
did you put the stock recovery back on before you locked the bootloader? Also are you super cid?
olorolo said:
did you put the stock recovery back on before you locked the bootloader? Also are you super cid?
Click to expand...
Click to collapse
No i don't believe so, Well now its not even going into twrp recovery. It displays tampered relocked security warning, s-on, hboot 1.44.0000 and This is the only screen i have for fastboot and the bootloader
I've seen this issue before let me take a quick look I think your ok
Sent from my HTCONE using Tapatalk 4
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
You caught me in the middle of flashing the s-off firmware myself
Sent from my HTCONE using Tapatalk 4
Good to hear! Thank you for your time sir
get the newest twrp and rename it to recovery.zip put it in your cmd folder in bootloader type reboot bootloader fastboot flash flash recovery fastboot reboot
---------- Post added at 07:28 PM ---------- Previous post was at 07:18 PM ----------
once you have twrp back flash the s-off firmware http://forum.xda-developers.com/showthread.php?t=2467607 then the 4.3 rom of your choice
olorolo said:
get the newest twrp and rename it to recovery.zip put it in your cmd folder in bootloader type reboot bootloader fastboot flash flash recovery fastboot reboot
Click to expand...
Click to collapse
Either i don't understand fully or its failing. I have fastboot usb selected on my phone connected to usb on pc. I open my folder with cmd in it, and i typed what you said but error is "reboot" is not recognizable.
edit: I also have the trwp 2.6.3 image in the folder along with cmd.
Pug4567 said:
Either i don't understand fully or its failing. I have fastboot usb selected on my phone connected to usb on pc. I open my folder with cmd in it, and i typed what you said but error is "reboot" is not recognizable.
edit: I also have the trwp 2.6.3 image in the folder along with cmd.
Click to expand...
Click to collapse
twrp has to be renamed to recovery.zip try fastboot flash then type flash recovery then the name of the zip which is recovery.zip then fastboot reboot
I did that am getting error:cannot load recovery.
Also tried fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
that resulted in this
sending 'recovery' (8608 KB)...
OKAY [ 1.120s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.880s
Or should i try http://forum.xda-developers.com/showthread.php?t=2314582
Pug4567 said:
I did that am getting error:cannot load recovery.
Also tried fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
that resulted in this
sending 'recovery' (8608 KB)...
OKAY [ 1.120s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.880s
Or should i try http://forum.xda-developers.com/showthread.php?t=2314582
Click to expand...
Click to collapse
try hassoons all in one toolbox
I got twrp back by unlocking my phone again. Should i proceed with the 3.04.651.2 firmwre? beanstalk is now hanging on splash screen.
The phone isn't being recognized on my computer it seems, it shows as m7wls under device manager, when in twrp 2.6.3. When in bootloader it shows as One device, but neither is accessible.
Also tried flashing the s-off firmware, but got 'error cannot load firmware.zip'
Any more help would be appreciated, almost thinking of taking it back to sprint, i have a protection plan. But i would like to avoid that, im currently going to buy an otg-usb cable as well.

Bootloop - Recovery not working

Hi Everyone,
Don't know what I did wrong but at the moment i stucked with a bootloop. I was trying to flash a 4.4 Rom on a Cyanogenmod 4.2.2
Now I can enter in bootloader but not into the recovery. When I try to boot into recovery it simply tries to boot the phone.
Bootloader i unlocked (it says tampered) but S-ON.
Tried to fastboot the recovery of clockworkmod but still can't enter in it.
How I can restore the phone to its original factory image?
Thnaks
It's seems you are not the only one.
Enter bootloader and choose fastboot.
Then run a command prompt in your PC, cd to the fastboot folder and write fastboot flash recovery filename.img
I suggest you download and flash twrp 2.6.3.0
Then check if the recovery has been installed successfully.If yes, go into recovery and type in the command prompt in your PC the following:
Adb push filename.Rom /data/media/0
Filename.zip stands for the Rom you wanna flash. After its done you can flash that file with twrp
Sent from my HTC One using Tapatalk
I think the cache just needs wiping with the command:
fastboot erase cache
Worked for me once or twice
Sent from my HTC One using XDA Premium 4 mobile app
thanks guys,
as i said i already tried to flash the recovery with the fastboot flash command.
I tried CMW and TWRP... but still can't enter into the recovery.
I have to try the erase cache command....
will let you know!
Did you find a solution? I am in the same boat and it is actually quite annoying.
gerazzo said:
thanks guys,
as i said i already tried to flash the recovery with the fastboot flash command.
I tried CMW and TWRP... but still can't enter into the recovery.
I have to try the erase cache command....
will let you know!
Click to expand...
Click to collapse
The_Doctor_Who said:
Did you find a solution? I am in the same boat and it is actually quite annoying.
Click to expand...
Click to collapse
Yes solved for me with the erase cache command and fastboot recovery the latest TRWP
Than i flashed the AR ROM...
bye
gerazzo said:
Yes solved for me with the erase cache command and fastboot recovery the latest TRWP
Than i flashed the AR ROM...
bye
Click to expand...
Click to collapse
Thanks. Unfortunately I cannot boot in to the custom recovery. It skips the recovery and jumps directly to the google screen.
The_Doctor_Who said:
Thanks. Unfortunately I cannot boot in to the custom recovery. It skips the recovery and jumps directly to the google screen.
Click to expand...
Click to collapse
^^^^ fastboot erase cache will solve that
nkk71 said:
^^^^ fastboot erase cache will solve that
Click to expand...
Click to collapse
Unfortunately I've typed fastboot erase cache until I'm blue in the face and it still will not boot into the custom recovery. Trust me, I wish I could get it to work for me.
The_Doctor_Who said:
Unfortunately I've typed fastboot erase cache until I'm blue in the face and it still will not boot into the custom recovery. Trust me, I wish I could get it to work for me.
Click to expand...
Click to collapse
okay, i trust you, can i have a little info on your state:
hboot version
which recovery are you using (name and version please )
and you are unlocked right?
nkk71 said:
okay, i trust you, can i have a little info on your state:
hboot version
which recovery are you using (name and version please )
and you are unlocked right?
Click to expand...
Click to collapse
Sure! H-boot 1.54, s -On, I have tried both locked and unlocked (via fasboot oem lock and unlock). I originally tried CWM touch, then gave TWRP a try. No luck booting to either. I get success on the cmd with loading, but cannot get it into recovery. I select recovery from the fastboot menu and the phone vibrates, then a second later "Google" appears.
Version of recovery:
CWM 6.0.3.1 and and 6.0.4.3
TWRP: 2.6.6.3 m7
The_Doctor_Who said:
Sure! H-boot 1.54, s -On, I have tried both locked and unlocked (via fasboot oem lock and unlock). I originally tried CWM touch, then gave TWRP a try. No luck booting to either. I get success on the cmd with loading, but cannot get it into recovery. I select recovery from the fastboot menu and the phone vibrates, then a second later "Google" appears.
Click to expand...
Click to collapse
make sure bootloader is unlocked, reboot to booloader/FASTBOOT USB (again make sure the top line or 2nd says UNLOCKED), then get latest CWM (just for this exercise) from here: http://forum.xda-developers.com/showthread.php?t=2173863
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
copy/paste command prompt output (all of it pls)
---> and try to enter recovery.
let me know what happens.
nkk71 said:
make sure bootloader is unlocked, reboot to booloader/FASTBOOT USB (again make sure the top line or 2nd says UNLOCKED), then get latest CWM (just for this exercise) from here: http://forum.xda-developers.com/showthread.php?t=2173863
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
copy/paste command prompt output (all of it pls)
---> and try to enter recovery.
let me know what happens.
Click to expand...
Click to collapse
Sure. Thank you!
Here is my output:
c:\And>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.055s]
finished. total time: 0.056s
c:\And>fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
target reported max download size of 1526722560 bytes
sending 'recovery' (8746 KB)...
OKAY [ 1.175s]
writing 'recovery'...
OKAY [ 0.675s]
finished. total time: 1.852s
c:\And>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.051s]
finished. total time: 0.051s
c:\And>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
Tried entering recovery. Black screen for a moment, vibration and then "Google"
The_Doctor_Who said:
Sure. Thank you!
Here is my output:
c:\And>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.055s]
finished. total time: 0.056s
c:\And>fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
target reported max download size of 1526722560 bytes
sending 'recovery' (8746 KB)...
OKAY [ 1.175s]
writing 'recovery'...
OKAY [ 0.675s]
finished. total time: 1.852s
c:\And>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.051s]
finished. total time: 0.051s
c:\And>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.042s]
finished. total time: 0.042s
Tried entering recovery. Black screen for a moment, vibration and then "Google"
Click to expand...
Click to collapse
what is "******** Did you mean to fastboot format this partition?" how come I never get that
is your adb sdk newer or older than mine? I'm still using:
Code:
C:\ADB2>adb
Android Debug Bridge version 1.0.29
Question, are you on GPE hboot (the black one) or normal (the white one)?
nkk71 said:
what is "******** Did you mean to fastboot format this partition?" how come I never get that
is your adb sdk newer or older than mine? I'm still using:
Code:
C:\ADB2>adb
Android Debug Bridge version 1.0.29
Question, are you on GPE hboot (the black one) or normal (the white one)?
Click to expand...
Click to collapse
That's interesting. Here is mine:
c:\adb>adb
Android Debug Bridge version 1.0.26
I'm on the GPE black screen.
The_Doctor_Who said:
That's interesting. Here is mine:
c:\adb>adb
Android Debug Bridge version 1.0.26
I'm on the GPE black screen.
Click to expand...
Click to collapse
1- recommend updating adb sdk, mine isnt even the latest, i think latest is something like 1.0.3xx
2- don't know if this will work in GPE hboot, but try "fastboot boot <recovery>.img", it used to work on 1.44, but stopped on 1.54+, maybe on GPE it still works.
nkk71 said:
1- recommend updating adb sdk, mine isnt even the latest, i think latest is something like 1.0.3xx
2- don't know if this will work in GPE hboot, but try "fastboot boot <recovery>.img", it used to work on 1.44, but stopped on 1.54+, maybe on GPE it still works.[/QUOT
I'm updating now. I tried fastboot boot recovery yesterday and it froze the phone.
Click to expand...
Click to collapse
The_Doctor_Who said:
I'm updating now. I tried fastboot boot recovery yesterday and it froze the phone.
Click to expand...
Click to collapse
yeah, it was crapped in 1.54
i'm gonna have to sign off soon, but will check back tomorrow....
BTW: i wouldn't mind if you hit the thanks button on my posts (the useful ones!)
Cheers.
nkk71 said:
yeah, it was crapped in 1.54
i'm gonna have to sign off soon, but will check back tomorrow....
BTW: i wouldn't mind if you hit the thanks button on my posts (the useful ones!)
Cheers.
Click to expand...
Click to collapse
Of course! I appreciate your time today!
nkk71 said:
1- recommend updating adb sdk, mine isnt even the latest, i think latest is something like 1.0.3xx
2- don't know if this will work in GPE hboot, but try "fastboot boot <recovery>.img", it used to work on 1.44, but stopped on 1.54+, maybe on GPE it still works.
Click to expand...
Click to collapse
I think his recovery partition might be corrupt.. @mike1986. wrote an article about corrupt data partitions(http://android-revolution-hd.blogspot.ch/2013/10/fix-data-htc-one.html) I think it was you who sent me that link.. well.. do you know if it is possible to use some of this commands? But we'd have to get into a state where we can use adb..

Categories

Resources