Database Develop

[Q] Not able to flash recovery.img after S-OFF and firmware upgrade

Hi,
I S-OFF'ed my HTC One, and upgraded the firmware!! Now i have a problem flashing the recovery.
When I'm trying to flash the recovery I'm only getting:
c:\Android>fastboot flash recovery recovery.img
sending 'recovery' (7422 KB)...
OKAY [ 1.188s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.223s
Any idea of why its giving me remote: not allowed?

Have you tried to change the cable or the usb port?
However, all the other command will work?

Hehe never mind, it was a total brainfreeze, when i used revone, i also locked the bootloader again so unlocking it again kinda helped hehe
Thanks for the reply anyways

Flash recovery FAILED (remote: no transfered data)

Hello,
1. I think I may have bricked my phone, here's what I did. I was S-OFF, Super CID. Installed new M4 RUU, the only one I could find and then decided to install Stock_SixthSense-M4_5.11Base.
2. I had an error at the end of it 'unable to mount /system'.
3. Tried to start adb sideload to try a different ROM, couldn't start either.
4. Rebooted phone to booloader, tried to start recovery TWRP, screen flashing not starting.
5. Tried to reinstall recovery and this:
C:\adb>fastboot flash recovery twrp.img
< waiting for device >
sending 'recovery' (9432 KB)...
OKAY [ 1.188s]
writing 'recovery'...
FAILED (remote: no transfered data)
finished. total time: 1.219s
What is happening? Please help!

calbertuk said:
Hello,
1. I think I may have bricked my phone, here's what I did. I was S-OFF, Super CID. Installed new M4 RUU, the only one I could find and then decided to install Stock_SixthSense-M4_5.11Base.
2. I had an error at the end of it 'unable to mount /system'.
3. Tried to start adb sideload to try a different ROM, couldn't start either.
4. Rebooted phone to booloader, tried to start recovery TWRP, screen flashing not starting.
5. Tried to reinstall recovery and this:
C:\adb>fastboot flash recovery twrp.img
< waiting for device >
sending 'recovery' (9432 KB)...
OKAY [ 1.188s]
writing 'recovery'...
FAILED (remote: no transfered data)
finished. total time: 1.219s
What is happening? Please help!
Click to expand...
Click to collapse
Try to run the RUU again. If it is successful, then you are back to stock. There is a HTC One Mini forum which will have more expertise than this forum.

majmoz said:
Try to run the RUU again. If it is successful, then you are back to stock. There is a HTC One Mini forum which will have more expertise than this forum.
Click to expand...
Click to collapse
The RUU did install properly. It's an AT&T RUU though and there aren't any others which is a bit of an issue.
Still can't get a custom ROM to install with TRWP

calbertuk said:
The RUU did install properly. It's an AT&T RUU though and there aren't any others which is a bit of an issue.
Still can't get a custom ROM to install with TRWP
Click to expand...
Click to collapse
I don't know what you are trying to accomplish but here is a possibility: How to : Flash HTC One Mini with out S-OFF and no need RUU Stock ROM and [ROM][M4 - 4.09.401.3] Official Stock Sense 6 Rom v2 & Firmware

Custom ROM

Hi,
i try to install Lollipop on my Z1. A Long Time ago i had cm mod installed, after that stock rom.
i use actually C6903_14.4.A.0.157_Central Europe 1. i want to install cm 12, device downgrade on .108, root and upgrade to .157. unlocking the bootloader via Fastboot and flashtool failed:
04/041/2015 18:41:52 - INFO - FAILED (remote: Command did not succeed)
04/041/2015 18:41:52 - INFO - finished. total time: 0.019s
second time:
04/041/2015 18:41:57 - INFO - FAILED (remote: Device is already rooted)
04/041/2015 18:41:57 - INFO - finished. total time: 0.004s
at servicemenu: Bootloader unlocked allowed: Yes. i think the bootloader is locked, but i can unlock. otherwise i try to install boot.img via fastboot from cm 12.
sending 'boot' (13252 KB)...
OKAY [ 0.461s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.470s
than i tried with Z1-lockeddualrecovery2.8.1 to install crdroid 5.0.2, installation from dualrecovery without problems. after flashing crdroid and direct after Z1-lockeddualrecovery2.8.1-RELEASE.flashable i had a black screen after reboot. when i press the on button there is one time vibration, than nothing. the z1 will not boot or start recovery. i installed via flashtool -> flash mode C6903_14.4.A.0.157_Central Europe 1 stock rom. someone any idea ?
thx

thc2oo2 said:
Hi,
i try to install Lollipop on my Z1. A Long Time ago i had cm mod installed, after that stock rom.
i use actually C6903_14.4.A.0.157_Central Europe 1. i want to install cm 12, device downgrade on .108, root and upgrade to .157. unlocking the bootloader via Fastboot and flashtool failed:
04/041/2015 18:41:52 - INFO - FAILED (remote: Command did not succeed)
04/041/2015 18:41:52 - INFO - finished. total time: 0.019s
second time:
04/041/2015 18:41:57 - INFO - FAILED (remote: Device is already rooted)
04/041/2015 18:41:57 - INFO - finished. total time: 0.004s
at servicemenu: Bootloader unlocked allowed: Yes. i think the bootloader is locked, but i can unlock. otherwise i try to install boot.img via fastboot from cm 12.
sending 'boot' (13252 KB)...
OKAY [ 0.461s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.470s
than i tried with Z1-lockeddualrecovery2.8.1 to install crdroid 5.0.2, installation from dualrecovery without problems. after flashing crdroid and direct after Z1-lockeddualrecovery2.8.1-RELEASE.flashable i had a black screen after reboot. when i press the on button there is one time vibration, than nothing. the z1 will not boot or start recovery. i installed via flashtool -> flash mode C6903_14.4.A.0.157_Central Europe 1 stock rom. someone any idea ?
thx
Click to expand...
Click to collapse
try to boot your device in flashmode
install stock rom

If you failed to install a custom kernel is because you did not have unlocked your bootloader. You need a unlocked bootloader to flash boot.img, otherwise it will fail.
You got a black screen because you have not followed the right steps to install the ROM, some ROM needs to wipe everything (except sdcard) to work properly.

Restore Stock Recovery - Amazon Fire 7 5th Gen (Ford)

IF YOU PLAN ON INSTALLING ANY CUSTOM ROM CHECK THAT YOUR RECOVERY IS ACCESSABLE!!!
If you have lost access to your stock recovery on your Amazon Fire 7 5th Gen (Ford) for whatever reason I would highly recommend restoring your recovery before doing any further customization to your device. Without recovery you have absolutely nothing to fall back on if your device becomes inoperable. If you have tried flashing any type of custom recovery directly to your device its more then likely you have lost access to your stock recovery. Hopefully youv made it to this thread before it was too late and luckily its a pretty simple process to restore your access.
Before we begin you must have a working OS for this process to work. If your device will not successfully boot then you can not complete the steps necessary to restore access to your recovery.
First lets
• Download Fire 7 Stock Recovery Image https://app.box.com/s/tjju5dptvsmsfjienf37siip8j6ch7wo
• Download and install the Flashfire App http://download.chainfire.eu/950/FlashFire/FlashFire-v0.30-20160331135212.apk
Next we'll
• Open the Flashfire App and allow it root access
• Press the red "+" button and select "Flash Firmware Package"
• Browse to the folder containing the Fire 7 Stock Recovery Image you previously downloaded and select it then press the "√" in the upper right corner
• Change Reboot option from "Normal" to "Recovery"
• Press the "FLASH" then "OK"
• Flashfire will reboot into recovery when its complete (Usually only takes a couple mins but its possible it may run for more)
It is also possible to restore access to recovery using Flashify
• Download and install Flashify
http://www.apkmirror.com/apk/christian-gollner/flashify/
• Press "Select Recovery Image" then choose file
• Browse to the Fire 7 Stock Recovery Image you downloaded earlier, select it and choose "Yup"
• Once complete reboot to recovery to confirm
That's it now you're back in action!!!

Has any one try flashing in fastboot mode?
Sent from my XT1080 using XDA Labs

sd_shadow said:
Has any one try flashing in fastboot mode?
Sent from my XT1080 using XDA Labs
Click to expand...
Click to collapse
Thought about that this morning as well. If no one else confirms before I get off work here shortly I will try then. (Especially like to see someone with a hard brick attempt it) In theory it seems it should work since the image seems to carry the signature from Amazon. Well at least that's what I picked up from researching for a fix to restore access to recovery on two of my fires.

Doesn't appear to work. My recovery randomly stopped working while I was trying to get SlimLP to install (unsuccessfully). Details Here
If I try to flash it:
sending 'recovery' (16384 KB)...
OKAY [ 0.474s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.480s
Click to expand...
Click to collapse
If I try to boot to it, same error as if you try to boot to TWRP:
D:\Downloads\android-sdk-windows\platform-tools>fastboot boot fire7-stock-recovery.img
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.535s
Click to expand...
Click to collapse

knicknut said:
Doesn't appear to work. My recovery randomly stopped working while I was trying to get SlimLP to install (unsuccessfully). Details Here
If I try to flash it:
sending 'recovery' (16384 KB)...
OKAY [ 0.474s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.480s
If I try to boot to it, same error as if you try to boot to TWRP:
D:\Downloads\android-sdk-windows\platform-tools>fastboot boot fire7-stock-recovery.img
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.535s
Click to expand...
Click to collapse
used ?
Code:
fastboot -i 0x1949 flash fire7-stock-recovery.img
Sent from my XT1080 using XDA Labs

sd_shadow said:
used ?
Code:
fastboot -i 0x1949 flash fire7-stock-recovery.img
Sent from my XT1080 using XDA Labs
Click to expand...
Click to collapse
Took me a minute to realize I had to put "recovery" after flash, but even after I did, I sadly got the same result:
sending 'recovery' (16384 KB)...
OKAY [ 0.534s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.541s
Click to expand...
Click to collapse

knicknut said:
used ?
Took me a minute to realize I had to put "recovery" after flash, but even after I did, I sadly got the same result:
sending 'recovery' (16384 KB)...
OKAY [ 0.534s]
writing 'recovery'...
FAILED (remote: Flashing not allowed)
finished. total time: 0.541s
Click to expand...
Click to collapse
yes, my bad
Sent from my XT1080 using XDA Labs

Now that flashfire allows us to restore backups from fastboot could we restore a back up of stock recovery or system to get flashfire bricked tablets working again?

vuvious said:
Now that flashfire allows us to restore backups from fastboot could we restore a back up of stock recovery or system to get flashfire bricked tablets working again?
Click to expand...
Click to collapse
Unfortunately I don't believe so. We need a key to unlock the actual ability to flash via Fastboot. As far as I know at least

vuvious said:
Now that flashfire allows us to restore backups from fastboot could we restore a back up of stock recovery or system to get flashfire bricked tablets working again?
Click to expand...
Click to collapse
I suspect that capability is coming (foundation is in v0.32) but probably not for this device due to fastboot restrictions I posed by Amazon.

Sorry cross posted removed

Robin Son said:
stuck with 5.1 will not boot to stock recovery
was going to try using fastboot with 5.3.1 stock img.file but can't find one
TGT123 super tool will reboot my A-fire but will not install stock recovery
O yeah and i lost root and no playstore
Anyone had this problem and fixed???
Click to expand...
Click to collapse
Please don't cross post. Answered here: http://forum.xda-developers.com/ama...stom-rom-fireos-5-3-1-0-t3418541/post70006008

relocked phone, how do I unlock it again?

I have an HTC Desire C
It was not able to boot, got stuck at the boot screen.
So I used fastboot, unlocked the bootloader, installed cwm recovery, and then accidentally relocked the phone. Now I can't unlock it again.
I get this when I try to unlock it again:
fastboot oem flash Unlock_code.bin
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.009s]
finished. total time: 0.010s
I get this error when I try to boot into RUU mode and try to flash a zip:
sending 'zip' (250722 KB)...
OKAY [ 20.054s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 52.095s
I cant flash the stock recovery back cuz my bootloader isn't unlocked. What should I do now? Any help would be appreciated