Database Develop

HELP - BRICKED One!

I was flashing a new rom onto my HTC One today and my daughter got hold of it (Age 3) whilst my back was turned and has wiped the ROM completely!
I have TWRP v2.7.1.1 touch bootloader but I cant get a ROM installed - fastboot won't recognise that there is a device attached even though I get the 'connected sound' when I connect to my windows 8 laptop. I have searched for all the fastboot and adb solutions but have come to a dead end!
I think its dead! :crying:
Fastboot usb shows on the phone screen when connected though
the OS - on the fastboot screen shows blank too!
*** TAMPERED ***
*** RELOCKED ***
M7_ PVT SHIP S_ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Oct 21 2013,22:50:54.0
Can anyone help?

lol if you have a working recovery then your device is not bricked. Even if your recovery is broken if you can access the bootloader your device is still fine.
It sounds to me like you are having some trouble with the windows drivers.. if you have a pc with linux I would try it there as it is easier. or if you only have win8 then you have to install these drivers http://forum.xda-developers.com/showthread.php?t=2544146
btw what problem do you have when installing the rom via recovery?

cuyo11 said:
lol if you have a working recovery then your device is not bricked. Even if your recovery is broken if you can access the bootloader your device is still fine.
It sounds to me like you are having some trouble with the windows drivers.. if you have a pc with linux I would try it there as it is easier. or if you only have win8 then you have to install these drivers http://forum.xda-developers.com/showthread.php?t=2544146
btw what problem do you have when installing the rom via recovery?
Click to expand...
Click to collapse
"C:\android-tools>fastboot devices
HT34PW913345 fastboot"​
CID = HTC__001
I can attempt to flash a .zip rom (same recovery number = stock 5.11.401.10) but it fails!
C:\android-tools>fastboot flash zip One_5.11.401.10_odexed.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1154791 KB)...
OKAY [ 43.432s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 179.412s​
I cant flash a different recovery anymore I presume as my bootloader is "RELOCKED" and I can't work out how to unlock it. HTCDev can't unlock it.
C:\android-tools>fastboot flash recovery recovery.img
target reported max download size of 1526722560 bytes
sending 'recovery' (9434 KB)...
OKAY [ 1.187s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.141s​
What is "bootloader signature checking"? How do I resolve that problem of FAILED?
I can access the RUU screen successfully
[INDENTC:\android-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.187s]
finished. total time: 0.234s][/INDENT]
but when I try to flash a .zip it doesn't work still
C:\android-tools>fastboot flash zip One_5.11.401.10_odexed.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1154791 KB)...
OKAY [ 44.000s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 159.127s​
Anyone have any ideas of how to get the signature checking to work?

I have managed to unlock again using my Unlock_code.bin file but it still fails to load the .zip ROM
C:\android-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.016s]
finished. total time: 0.172s
C:\android-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.047s]
finished. total time: 0.172s
C:\android-tools>fastboot flash zip One_5.11.401.10_odexed.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1154791 KB)...
OKAY [ 43.874s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 61.203s​

I have now managed to load ClockworkMod Recovery v6.0.4.6
I have found I can't mount the /sdcard
I guess that's where my problem lies? If my phone has forgotten how to find /sdcard then how can it flash to it?

targett said:
I have now managed to load ClockworkMod Recovery v6.0.4.6
I have found I can't mount the /sdcard
I guess that's where my problem lies? If my phone has forgotten how to find /sdcard then how can it flash to it?
Click to expand...
Click to collapse
Check this http://forum.xda-developers.com/showthread.php?t=2228274&page=3
then let me know if you have any questions.

nkk71 said:
Check this http://forum.xda-developers.com/showthread.php?t=2228274&page=3
then let me know if you have any questions.
Click to expand...
Click to collapse
I have wiped the system and cache just in case and am attempting the sideload but when i do the "adb devices" it doesn't sow my device number, where it does if in fastboot.
G:\adb>adb devices
List of devices attached
​
And when I attempt at adb sideload I get this
G:\adb>adb sideload One_5.11.401.10_odexed.zip
error: device not found​Stuck again :crying:
Oh - How important is the USB OTG in the adb sideload

targett said:
I have wiped the system and cache just in case and am attempting the sideload but when i do the "adb devices" it doesn't sow my device number, where it does if in fastboot.
Stuck again:crying:
Click to expand...
Click to collapse
it is mentioned in the post, but here again: FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

nkk71 said:
it is mentioned in the post, but here again: FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
Sorry for being so stupid! I feel like a noob on this device (not flashed or rooted in about 3 years!)
Reading it all again I see I need S-Off. My Security is ON. and I can't turn it off as I can't install SuperSU or Superuser or anything at all.
Any thoughts?

targett said:
Sorry for being so stupid! I feel like a noob on this device (not flashed or rooted in about 3 years!)
Reading it all again I see I need S-Off. My Security is ON. and I can't turn it off as I can't install SuperSU or Superuser or anything at all.
Any thoughts?
Click to expand...
Click to collapse
sorry, i don't follow. it has nothing to do with s-on or s-off.
you say your device isn't being seen while in custom recovery, but it has to show somewhere in device manager, no? if yes, then you may need to manually select the correct drivers, that's it

nkk71 said:
sorry, i don't follow. it has nothing to do with s-on or s-off.
you say your device isn't being seen while in custom recovery, but it has to show somewhere in device manager, no? if yes, then you may need to manually select the correct drivers, that's it
Click to expand...
Click to collapse
Sorry!
I have sorted the Win8 driver issue - Hadn't spotted that one.
I have now managed to adb push the .zip file and adb sideload it too.
I'm now installing the 'sideload.zip' Wish me luck!
Wordked! It F#*king WORKED!!!!!
Thank you, thank you, thank you!

targett said:
Sorry!
I have sorted the Win8 driver issue - Hadn't spotted that one.
I have now managed to adb push the .zip file and adb sideload it too.
I'm now installing the 'sideload.zip' Wish me luck!
Wordked! It F#*king WORKED!!!!!
Thank you, thank you, thank you!
Click to expand...
Click to collapse
Good Luck :good: :good:

Cyanogenmod Stole My Recovery

Hi
I had TWRP installed and installed Cm12.1-20150427 unoffical-yuga and Cyanogenmod wrote its own recovery.
If I try to install any zips such as
extract_elf_ramdisk-hack.zip
twrp-2.8-20150424-yuga.zip
I get the error:
E:footer is wrong
E:signature verification failed
If I try ADB
fastboot flash recovery recovery.img
I get
sending 'recovery' (10388 KB)...
OKAY [ 0.446s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.458s
I'm stuck any ideas?
Thanks

What i did and it worked really fine is to use the Rashr utility (free from Google Store) and just fhlash the twrp image.
Try it!
cramhead said:
Hi
I had TWRP installed and installed Cm12.1-20150427 unoffical-yuga and Cyanogenmod wrote its own recovery.
If I try to install any zips such as
extract_elf_ramdisk-hack.zip
twrp-2.8-20150424-yuga.zip
I get the error:
E:footer is wrong
E:signature verification failed
If I try ADB
fastboot flash recovery recovery.img
I get
sending 'recovery' (10388 KB)...
OKAY [ 0.446s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.458s
I'm stuck any ideas?
Thanks
Click to expand...
Click to collapse

ROM Flashing - Image is too large - Partition

Motorola G XT1072 -
Recovery: Clockworkmod v6.0.4.7 -
Bootloader: Unlocked
Problem: Failed in flashing rom to device.
What I did:
1. Install "Minimal ADB and Fastboot".
2. Download "mfastboot-v2" and extract it to the same directory I installed "Minimal ADB and Fastboot".
3. Deleted "fastboot.exe" to avoid possible confusion with windows.
4. Extracted the stock rom for the phone to the same directory as "Minimal ADB and Fastboot".
5. Enter the phone in Fastboot Flash Mode
6. Open "Command Prompt" in the "Minimal ADB and Fastbook" folder when the "mfastboot" and extracted ROM files are.
7. In "Command Prompt" I typed "mfastboot flash partition gpt.bin"
I get this error in "Command Prompt"
-------------------------------------------------------------------------------------------------------------------
C:\Users\MAWiggKTA\Desktop\Moto G Files\Minimal ADB and Fastboot>mfastboot flash
partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.043s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.358s
C:\Users\MAWiggKTA\Desktop\Moto G Files\Minimal ADB and Fastboot>
On my phone screen I get pink writing saying: VERSION DOWNGRADED FOR PRIMARY_GPT
-------------------------------------------------------------------------------------------------------------------
8. I typed "mfastboot flash motoboot motoboot.img" and get this error:
C:\Users\MAWiggKTA\Desktop\Moto G Files\Minimal ADB and Fastboot>mfastboot flash
motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.105s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.388s
On my phone screen I get writing saying: VERSION DOWNGRADED FOR TZ
-------------------------------------------------------------------------------------------------------------------
9. I typed "mfastboot flash logo logo.bin" and it came back as OKAY.
10. I typed "mfastboot flash boot boot.img" and it again came back as OKAY.
11. I typed "mfastboot flash recovery recovery.img" and it again came back as OKAY.
12. I typed "mfastboot flash system system.img_sparsechunk.0" and got this error:
-----------------------------------------------------------------------------------------------------------------
C:\Users\MAWiggKTA\Desktop\Moto G Files\Minimal ADB and Fastboot>mfastboot flash
system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (261762 KB)...
OKAY [ 8.375s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.406s
On my phone screen it says: IMAGE IS TOO LARGE
-------------------------------------------------------------------------------------------------------------------
I think the partition maybe corrupted or something, possible suggestion please people.
Thanks in advanced

Please double check if you have downloaded the correct firmware zip corresponding to your phone model and region. Every region has a different firmware zip, so please verify it before downloading.

I'm positive its the right rom for my phone. I have also downloaded an EU one but get exactly the same errors. Thank you

Maybe try another custom recovery, twrp 2.8.5.0 worked perfectly for me.

thanks mate but ive tried that and still no good. Either recovery I get the same errors. Anyway to totally wipe the phone and redo the partitions?

I don´t know where but I read about the problem with too large images a few times in this forum lately....seems to be a new problem.

How to fix FAILED (remote: 'Command not allowed') when i want to flash android 10.0

D:\platform-tools>fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
Erasing 'userdata' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
D:\platform-tools>fastboot flash boot boot.img
Sending 'boot' (12392 KB) OKAY [ 0.297s]
Writing 'boot' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
D:\platform-tools>fastboot flash cache vendor.img
Sending 'cache' (36012 KB) OKAY [ 0.819s]
Writing 'cache' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
D:\platform-tools>fastboot flash system system.img
Sending sparse 'system' 1/5 (257072 KB) OKAY [ 5.833s]
Writing 'system' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed

Pixel 5 after OTA update can't start, stuck fastboot mode

My phone is no flash,no root, no USB debugging. Can't boot after OTA update today, stuck at Fastboot Mode, can't start. the error message is "failed to load/verify boot images"
I download Redfin from Factory Images for Nexus and Pixel Devices, run flash-all.bat, error message:
Code:
Sending 'bootloader_a' (8762 KB) OKAY [ 0.328s]
Writing 'bootloader_a' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.048s]
Finished. Total time: 0.051s
Sending 'radio_a' (149796 KB) OKAY [ 3.886s]
Writing 'radio_a' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
--------------------------------------------
Bootloader Version...: r3-0.4-8351081
Baseband Version.....: g7250-00202-220422-B-8489468
Serial Number........: 09
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.169s]
Checking 'version-bootloader' OKAY [ 0.178s]
Checking 'version-baseband' OKAY [ 0.139s]
Setting current slot to 'a' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Press any key to exit...
I run:
[ICODE]# fastboot flashing unlock
FAILED (remote: 'Error getting device locked state Not Ready')
fastboot: error: Command failed[/ICODE]
fastboot boot boot.img
Sending 'boot.img' (98304 KB) OKAY [ 2.400s]
Booting FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
fastboot devices
09aaaaaaaaaa fastboot
please help me

Have you tried simply re-flashing?

Sewdohe said:
Have you tried simply re-flashing?
Click to expand...
Click to collapse
yes, but it can't open, He still remains in "Fastboot Mode" and cannot be started

Barbet is Pixel 5a.
Redfin is Pixel 5

andybones said:
Barbet is Pixel 5a.
Redfin is Pixel 5
Click to expand...
Click to collapse
sorry, I look my download folder, it is "redfin-sq3a.220705.003.a1-factory-b193f96f"

Evolv X said:
sorry, I look my download folder, it is "redfin-sq3a.220705.003.a1-factory-b193f96f"
Click to expand...
Click to collapse
Did using the correct file fix your problem?

NO, and I use Google Online, Bug can't
V0latyle said:
Did using the correct file fix your problem?
Click to expand...
Click to collapse

Evolv X said:
NO, and I use Google Online, Bug can't
Click to expand...
Click to collapse
Could you be a bit more detailed? I don't understand.

Same, I don't understand. It appears you're trying to flash for the wrong phone...

If your bootloader is locked, you cannot flash anything in fastboot/bootloader.
Try sideloading the OTA again.

Getting this issue...are you able to fix it?