Database Develop

Not able to boot up

The phone is unlocked and is working fine but out of the sudden it is hung at boot up screen.
Now i cannot even access the RA-nexus recovery gui. It will hang at the screen with the 'X' logo.
I tried to re-flash the recovery but got the below error when i try to do a fastboot.
"
D:\Downloads\Nexus One\android-sdk-windows\tools>fastboot devices
123456789012 fastboot
D:\Downloads\Nexus One\android-sdk-windows\tools>fastboot flash recovery recover
y-RA-nexus-v1.7.0.img
sending 'recovery' (3948 KB)... OKAY
writing 'recovery'... FAILED (remote: not allowed)
D:\Downloads\Nexus One\android-sdk-windows\tools>
"
Another weird output when i ran the 'fastboot-windows.exe devices -s'
"
C:\1>fastboot-windows.exe devices -s
123456789012 fastboot
"
Seems like i need a GoldCards for Nexus One but i don't know how to make it since my only Nexus One is not accessible now.
Any help on this??

Are to you doing this to enter recovery from bootloader mode (vol down, power)

try flashing the stock recovery image...

jerrycycle said:
Are to you doing this to enter recovery from bootloader mode (vol down, power)
Click to expand...
Click to collapse
Cannot enter the recovery from bootloader too. After selecting the 'recovery' option, it will stuck with the 'X' nexus icon.

craigacgomez said:
try flashing the stock recovery image...
Click to expand...
Click to collapse
Where can i find the stock recovery image?

If you used superboot to root try these instructions.
http://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/

When i try to run the command, i will hit the 'FAILED (remote: not allowed)' error.
'
>fastboot flash recovery recovery-RA-nexus-v1.7.0.img
sending 'recovery' (3948 KB)... OKAY
writing 'recovery'... FAILED (remote: not allowed)
'
jerrycycle said:
If you used superboot to root try these instructions.
http://theunlockr.com/2010/01/08/how-to-load-a-custom-rom-on-the-nexus-one/
Click to expand...
Click to collapse

Did you save the recovery image to the superboot folder?

jerrycycle said:
Did you save the recovery image to the superboot folder?
Click to expand...
Click to collapse
Yup.
D:\Downloads\Nexus One\ROM\1.0-EPE54B-nexusone-insecure>fastboot-windows.exe flash recovery recovery-RA-nexus-1.7.0.img
sending 'recovery' (3948 KB)... OKAY
writing 'recovery'... FAILED (remote: not allowed)

Just try this. I know with the mt3g it worked a few time. Try to erase the recovery partition (IE: fastboot erase recovery). This will erase the recovery image. THEN immediately after reflash the recovery (IE: fastboot flash recovery <PATH TO Amon_RA1.0.7>)....Report back your findings
I AM NOT RESPONSIBLE FOR FURTHER PROBLEMS!!!! YOU UN-LOCKED AND ARE PERFORMING THIS AT YOUR OWN RISK!!!

Hi,
Still hitting the 'FAILED (remote: not allowed)' error.
"
>fastboot erase recovery
erasing 'recovery'... FAILED (remote: not allowed)
"
martin0285 said:
Just try this. I know with the mt3g it worked a few time. Try to erase the recovery partition (IE: fastboot erase recovery). This will erase the recovery image. THEN immediately after reflash the recovery (IE: fastboot flash recovery <PATH TO Amon_RA1.0.7>)....Report back your findings
I AM NOT RESPONSIBLE FOR FURTHER PROBLEMS!!!! YOU UN-LOCKED AND ARE PERFORMING THIS AT YOUR OWN RISK!!!
Click to expand...
Click to collapse

no clue then man. I mean you said your un-locked and all, ARE YOU POSITIVE? In fastboot it says "Un-locked"?? Just first time i've seen this on here.....not sure what it could be....+ I have limited android skills (sadly).....

acidash said:
Where can i find the stock recovery image?
Click to expand...
Click to collapse
When my recovery went bonkers, I used a stock recovery image to fix the issue.
http://autisticpig.com/android/roms and flashes/PASSIMG_Passion_/recovery.img
Give that a try and see if things aren't more normal.

I guess it somehow lost its root access and now my nexus one is useless until i can get hold of a goldcards.
;(
martin0285 said:
no clue then man. I mean you said your un-locked and all, ARE YOU POSITIVE? In fastboot it says "Un-locked"?? Just first time i've seen this on here.....not sure what it could be....+ I have limited android skills (sadly).....
Click to expand...
Click to collapse

Thanks. It hit the 'FAILED (remote: not allowed)' error again.
deprecate said:
When my recovery went bonkers, I used a stock recovery image to fix the issue.
http://autisticpig.com/android/roms and flashes/PASSIMG_Passion_/recovery.img
Give that a try and see if things aren't more normal.
Click to expand...
Click to collapse

acidash said:
Where can i find the stock recovery image?
Click to expand...
Click to collapse
You can pull out the recovery from the stock passion image... http://forum.xda-developers.com/showthread.php?t=642811
If you can't flash the stock recovery as well, try a complete restore to stock... rename the zstock passion image zip to PASSIMG.zip, copy to the SD card,, boot into bootloader and when it asks, apply the update...
One more thing, you could try Koush's Clockwork recovery image from http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html (direct link http://koush.romraid.com/recoveries/recovery-clockwork-passion.img)

craigacgomez said:
You can pull out the recovery from the stock passion image... http://forum.xda-developers.com/showthread.php?t=642811
If you can't flash the stock recovery as well, try a complete restore to stock... rename the zstock passion image zip to PASSIMG.zip, copy to the SD card,, boot into bootloader and when it asks, apply the update...
One more thing, you could try Koush's Clockwork recovery image from http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html (direct link http://koush.romraid.com/recoveries/recovery-clockwork-passion.img)
Click to expand...
Click to collapse
+1 for this

Tried the 'PASSIMG.zip' method, and it says Update Partition Fails.
Now i cannot even power it up.
craigacgomez said:
You can pull out the recovery from the stock passion image... http://forum.xda-developers.com/showthread.php?t=642811
If you can't flash the stock recovery as well, try a complete restore to stock... rename the zstock passion image zip to PASSIMG.zip, copy to the SD card,, boot into bootloader and when it asks, apply the update...
One more thing, you could try Koush's Clockwork recovery image from http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html (direct link http://koush.romraid.com/recoveries/recovery-clockwork-passion.img)
Click to expand...
Click to collapse

Try getting a warranty/RMA for your device. There is something larger going on here than the fact the phone is unlocked...you should be able to flash recovery even if that partition is hosed.
actually, does anyone know a means to format just the partition recovery resides?
Oh wait..you said it won't power on...
Give HTC a ring; it may be your only recourse unless you can get your phone back on.

yup. Since i cannot even power it on, HTC is my only option.
Thanks all for all the guides.
deprecate said:
Try getting a warranty/RMA for your device. There is something larger going on here than the fact the phone is unlocked...you should be able to flash recovery even if that partition is hosed.
actually, does anyone know a means to format just the partition recovery resides?
Oh wait..you said it won't power on...
Give HTC a ring; it may be your only recourse unless you can get your phone back on.
Click to expand...
Click to collapse

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.

[Q] Stock Recovery Partition Missing?

Just curious, does anyone have a dump of the recovery partition for the Dev Edition? It looks like from a bit of reading is that the recovery partition doesn't seem to be present.
I am unable to use recovery mode properly since it saids invalid operation when I do apply from SD, storage or cache, followed by the phone automatically restarting.
Has anyone else noticed this? I wonder if the unlocked 32 GB versions is unaffected.

try to reflash the recovery, the partitions should be the same as the original One

I tried to do that by using the RUU and using the zip, but it did not bring it back.
Is there a way to get the recovery image itself? I tried to extract the zip but it looked like it's encrypted as I cannot do so.
Looks like one mike1986 mentioned it's missing as well.
mike1986. said:
1. Well, I decided not to mention some things to avoid confusion. At the moment unlocking bootloader removes content of /data/preload partition, so indeed, installing OTA will fail. But I truly hope that HTC will fix it at some point and unlocking bootloader won't cause some stock apps to be missing.
2. Which procedure?
Click to expand...
Click to collapse

Sango2 said:
I tried to do that by using the RUU and using the zip, but it did not bring it back.
Is there a way to get the recovery image itself? I tried to extract the zip but it looked like it's encrypted as I cannot do so.
Looks like one mike1986 mentioned it's missing as well.
Click to expand...
Click to collapse
if you can point me where the RUU for your dev edition is i can extract the recovery.img for you

matt95 said:
if you can point me where the RUU for your dev edition is i can extract the recovery.img for you
Click to expand...
Click to collapse
Great, thanks a lot.
Two places you can get it from
http://forum.xda-developers.com/showthread.php?p=39588860 (BrightstarUS_WWE which is Developer)
or directly from HTCdev
http://www.htcdev.com/devcenter/downloads

Sango2 said:
Great, thanks a lot.
Two places you can get it from
http://forum.xda-developers.com/showthread.php?p=39588860 (BrightstarUS_WWE which is Developer)
or directly from HTCdev
http://www.htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
ok, i'm downloading!
very very slow D:

matt95 said:
ok, i'm downloading!
very very slow D:
Click to expand...
Click to collapse
No worries, I'll be back on tonight since got some meetings to attend in the office. Lets see what you can discover.
Thanks!

ok, iside of it i found this recovery file! try to flash it using
Code:
fastboot flash recovery recovery_signed.img
Download

matt95 said:
ok, iside of it i found this recovery file! try to flash it using
Code:
fastboot flash recovery recovery_signed.img
Download
Click to expand...
Click to collapse
Tried it but for some reason I get this.
Code:
recovery recovery_signed.img
sending 'recovery' (9590 KB)...
OKAY [ 1.233s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.376s

Sango2 said:
Tried it but for some reason I get this.
Code:
recovery recovery_signed.img
sending 'recovery' (9590 KB)...
OKAY [ 1.233s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.376s
Click to expand...
Click to collapse
as i though, mmmhh, unzipping the file breaks the signature.... well then you need to download a stock nandroid backup and inside of it you will fina a recovery.zip... just flash it and you're ready to go

matt95 said:
as i though, mmmhh, unzipping the file breaks the signature.... well then you need to download a stock nandroid backup and inside of it you will fina a recovery.zip... just flash it and you're ready to go
Click to expand...
Click to collapse
Hmm, I'm beginning to wonder if the stock recovery is suppose to work like that, where if I try to apply storage, sd card, or cache it saids invalid operation and reboot. The reason is, a new HTC One S my relative got she her phone is being replaced for free under warranty... I go to the recovery and do those certain the apply stuff, it also saids invalid operation out and restarts!
I find this a bit interesting on my HTC One when I go to the recovery and wondering the failed mount SD card messages is normal.

Try this -> http://vps.rana.sg/HTC_ONE/individual_files/recovery.emmc.win
fastboot erase cache
fastboot flash recovery recovery.emmc.win

v-b-n said:
Try this -> http://vps.rana.sg/HTC_ONE/individual_files/recovery.emmc.win
fastboot erase cache
fastboot flash recovery recovery.emmc.win
Click to expand...
Click to collapse
I get this error.
Forbidden
You don't have permission to access /HTC_ONE/individual_files/recovery.emmc.win on this server.
Click to expand...
Click to collapse

Sango2 said:
I get this error.
Click to expand...
Click to collapse
Oops ... try now

v-b-n said:
Oops ... try now
Click to expand...
Click to collapse
I don't mean to hijack this thread but I tried flashing it on my HTC One and I received a signature verify fail...
Code:
sending 'recovery' (16383 KB)...
OKAY [ 1.921s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.876s

I don't get it why signature check is happening... Is the bootloader in unlock status and which custom recovery aren't of trying to overwrite?
Sent from my HTC One using xda premium

v-b-n said:
I don't get it why signature check is happening... Is the bootloader in unlock status and which custom recovery aren't of trying to overwrite?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
i'm wondering that too, but is that a recovery taken from the RUU.zip?

matt95 said:
i'm wondering that too, but is that a recovery taken from the RUU.zip?
Click to expand...
Click to collapse
It's A twrp backup which is flashable using fastboot... I have done it so many times, hope people are flashing the fastboot way?
Sent from my HTC One using xda premium

The only time bootloader is going to Sig check a recovery partition is if he is relocked. He said he used the ruu a couple times so he is still relocked.

v-b-n said:
It's A twrp backup which is flashable using fastboot... I have done it so many times, hope people are flashing the fastboot way?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
... you mean taken from the TWRP backup?

Can't Flash Recovery

I'm on the T-Mobile variant and have followed the steps on the motorola website to unlock the bootloader. When I boot into fastboot, it says the device is unlocked with at status code 3. When I run 'fastboot flash recovery recovery.img' everything seems to run fine:
fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.827s]
writing 'recovery'...
OKAY [ 1.102s]
finished. total time: 1.930s​When I try to reboot into recovery mode it just shows me the warning that my bootloader is unlocked, then boots as normal. I don't know what to do. I've tried both the twrp and cwm recovery images. Any help?

what recovery did you flash?

waiflih said:
what recovery did you flash?
Click to expand...
Click to collapse
I've tried both the twrp and cwm recoveries that are available in the android development section.

You are replacing recovery.img with the actual file name right?
Sent from my Moto X.

mentose457 said:
You are replacing recovery.img with the actual file name right?
Sent from my Moto X.
Click to expand...
Click to collapse
Yup. From reading around it seems like there's a script in /system that flashes the stock recovery upon booting up. I tried to get the PwnMyMoto apk onto my device to get root and remove the recovery script file but now I'm getting an unexpected exception when trying to install the apk through adb. I have both USB debugging and Unknown Sources allowed. Any ideas?
Edit:
By the way I am T-Mobile, post OTA. If that changes anything.

elijahah said:
Yup. From reading around it seems like there's a script in /system that flashes the stock recovery upon booting up. I tried to get the PwnMyMoto apk onto my device to get root and remove the recovery script file but now I'm getting an unexpected exception when trying to install the apk through adb. I have both USB debugging and Unknown Sources allowed. Any ideas?
Edit:
By the way I am T-Mobile, post OTA. If that changes anything.
Click to expand...
Click to collapse
This might be a long way to do it but can't you downgrade back to 4.2.2 then get root with that then follow the instructions found in the general section for maintaining root through taking the ota? This should fix your problem. Also the instructions there might give you a different idea of how to work around this issue. You might just be able to flash the boot image and install the hidden su yourself.
Sent from my XT1060 using xda app-developers app

jayboyyyy said:
This might be a long way to do it but can't you downgrade back to 4.2.2 then get root with that then follow the instructions found in the general section for maintaining root through taking the ota? This should fix your problem. Also the instructions there might give you a different idea of how to work around this issue. You might just be able to flash the boot image and install the hidden su yourself.
Sent from my XT1060 using xda app-developers app
Click to expand...
Click to collapse
I'm already on 4.2.2. I'm guessing you mean to undo the recent OTA? How would I do that without a custom recovery or root?

Twrp has a built on file explorer, can you boot directly into recovery from the fastboot screen and delete the file that way?
Sent on my Moto X

flashallthetime said:
Twrp has a built on file explorer, can you boot directly into recovery from the fastboot screen and delete the file that way?
Sent on my Moto X
Click to expand...
Click to collapse
Unfortunately I can't I flash the recovery via fastboot then try to boot into recovery and it just shows me the warning that my bootloader is unlocked and boots normally.

elijahah said:
Unfortunately I can't I flash the recovery via fastboot then try to boot into recovery and it just shows me the warning that my bootloader is unlocked and boots normally.
Click to expand...
Click to collapse
One more clarification: After you flash recovery, you are using the volume down key to highlight recovery and then you are using the up arrow to select it correct? You do not press the power button to make the selection as on nexus devices.

elijahah said:
Unfortunately I can't I flash the recovery via fastboot then try to boot into recovery and it just shows me the warning that my bootloader is unlocked and boots normally.
Click to expand...
Click to collapse
Don't flash it, boot it. Fastboot boot recovery recovery.IMG. if that works maybe you can delete that file.
Sent from my Nexus 7

mentose457 said:
One more clarification: After you flash recovery, you are using the volume down key to highlight recovery and then you are using the up arrow to select it correct? You do not press the power button to make the selection as on nexus devices.
Click to expand...
Click to collapse
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
phositadc said:
Don't flash it, boot it. Fastboot boot recovery recovery.IMG. if that works maybe you can delete that file.
Sent from my Nexus 7
Click to expand...
Click to collapse
Ah man I thought this would work but this is the response I got:
fastboot boot twrp263.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.881s
Thanks for all your help though guys.

elijahah said:
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
Ah man I thought this would work but this is the response I got:
fastboot boot twrp263.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.881s
Thanks for all your help though guys.
Click to expand...
Click to collapse
Did you leave a word out? I think it's fastboot boot recovery recovery. IMG.
Sent from my Nexus 7

elijahah said:
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
Thanks for all your help though guys.
Click to expand...
Click to collapse
Erase the recovery partition. Then try flashing twrp.
fastboot erase recovery
fastboot flash recovery twrp26XX.img
Sent from my Moto X.

mentose457 said:
Erase the recovery partition. Then try flashing twrp.
fastboot erase recovery
fastboot flash recovery twrp26XX.img
Sent from my Moto X.
Click to expand...
Click to collapse
I get this:
fastboot erase recovery
(bootloader) Variable not supported!
erasing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.071s​

Actually it works now. I just tired fastboot flash recovery twrp263.img then pressed vol down to get to recovery and pressed vol up to select it and it worked! Thanks for sticking with me guys.

elijahah said:
Actually it works now. I just tired fastboot flash recovery twrp263.img then pressed vol down to get to recovery and pressed vol up to select it and it worked! Thanks for sticking with me guys.
Click to expand...
Click to collapse
Excellent. Glad you got it working.

elijahah said:
Actually it works now. I just tired fastboot flash recovery twrp263.img then pressed vol down to get to recovery and pressed vol up to select it and it worked! Thanks for sticking with me guys.
Click to expand...
Click to collapse
PS you had recovery the first time you hit the up volume and it sent you to a screen that said "no command" from that screen if you press the up volume and power button together it sends you to the recovery screen. It may be down volume and power together to get passed that "no command" screen but its one of the two. I saw people having that same problem in the forum about maintaining root through the OTA.

phositadc said:
Did you leave a word out? I think it's fastboot boot recovery recovery. IMG.
Sent from my Nexus 7
Click to expand...
Click to collapse
elijahah said:
Oops I didn't know that! Still no avail. I get a screen with the green android that says 'no command'
Ah man I thought this would work but this is the response I got:
fastboot boot twrp263.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.881s
Thanks for all your help though guys.
Click to expand...
Click to collapse
Probably your battery isnt charged enough to proceed with operation.
Check your battery and make sure it is charged at least 50% and try again.

leonardoafa said:
Probably your battery isnt charged enough to proceed with operation.
Check your battery and make sure it is charged at least 50% and try again.
Click to expand...
Click to collapse
Will charge up a bit over 50% and see. I still get permission denied. Plus when I try to get into recovery, I can't. The Motorola log shows up for a while, then restarts and boots normally into Android.

Unable to root Htc one (sprint)

I am unable to root my htc one with sprint. I write the recoveries, to the deivce, and fastboot says it was ok.
When I try and boot to recovery, it hangs for approx 30 sec, then reboots to the OS.
I am currently running Android 4.3
S=Off
cid = spcs_001
hboot = 1.55.0000
radio = 1.00.20.0913_3
opendsp = v31.120.274.0617
os = 3.04.651.2
eMMC = boot 2048MB
tried to use fastboot erase cache a few times also
Any assistance would be greatly appreciated!
Thanks

abs7125 said:
I am unable to root my htc one with sprint. I write the recoveries, to the deivce, and fastboot says it was ok.
When I try and boot to recovery, it hangs for approx 30 sec, then reboots to the OS.
I am currently running Android 4.3
S=Off
cid = spcs_001
hboot = 1.55.0000
radio = 1.00.20.0913_3
opendsp = v31.120.274.0617
os = 3.04.651.2
eMMC = boot 2048MB
tried to use fastboot erase cache a few times also
Any assistance would be greatly appreciated!
Thanks
Click to expand...
Click to collapse
I forgot to mention, I have tried to use fastboot boot (image), and it freezes, no matter which recovery image I try. I have tried twrp, and clockwork so far.

Fastboot flash recovery twrp.img
Make sure you are getting the newest img file from twrp site. Make sure it's the Sprint ver.

an0ther said:
Fastboot flash recovery twrp.img
Make sure you are getting the newest img file from twrp site. Make sure it's the Sprint ver.
Click to expand...
Click to collapse
Double checked, it is the latest file, and I also verified it is for Sprint. Thought the same thing.

I assume it used to work? I see you are s-off? I don't see what could be going on. You can always do a full ruu reboot and start over but it will wipe your phone.
I just saw you did a Fastboot boot img. Not sure what that could have done. Boot.img is your kernel. When your phone boots , does it work?

an0ther said:
I assume it used to work? I see you are s-off? I don't see what could be going on. You can always do a full ruu reboot and start over but it will wipe your phone.
I just saw you did a Fastboot boot img. Not sure what that could have done. Boot.img is your kernel. When your phone boots , does it work?
Click to expand...
Click to collapse
The phone it self, does work. Boots fine. My problem, is I cant get root anymore. It worked until I went back to factory on everything, so I could get the updates. Even recovery worked when I got that back to stock. I took the Ota updates, no I cant get into recovery, so I can re root it.
Tried to go back to stock like i did before, same issue on 4.22 now. followed same procedures for re lock, un lock bootloader, both times, and this time it wont load anything into recovery.

Go to settings, power when phone is booted. Make sure fastboot is not selected.
Sent from my One using XDA Premium 4 mobile app

CoryTallman said:
Go to settings, power when phone is booted. Make sure fastboot is not selected.
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Shouldnt try this when tired lol. That was checked. Unchecked it, and got the following error this time :
sending 'recovery' (391888 KB)...
OKAY [ 13.413s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 13.456s

abs7125 said:
Shouldnt try this when tired lol. That was checked. Unchecked it, and got the following error this time :
sending 'recovery' (391888 KB)...
OKAY [ 13.413s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 13.456s
Click to expand...
Click to collapse
also, I tried to use rom manager, to download and install clockworkmod. It says an error occurred while flashing your recovery.

abs7125 said:
also, I tried to use rom manager, to download and install clockworkmod. It says an error occurred while flashing your recovery.
Click to expand...
Click to collapse
So after 2 days, it looks like I got this working.
Not sure why this fix made a difference, however it worked, for me.
I ended up having to flash an older recovery twrp image of 2.5.0.0 first. That atleast allowed me to boot into recovery, finally. Problem was, nothing on the touchscreen would work.
I rebooted the device back into the bootloader, then installed twrp 2.6.3.0
That worked great!