Database Develop

HELP! stuck in fastboot

Hello everyone,
I was trying to return my htc one, s-on, custom recovery and rom installed...back to complete stock. I have a mac. I tried using the following guide:
http://forum.xda-developers.com/showthread.php?t=2251800
I was able to re-lock the bootloader, but I was unable to flash the RUU as instructed in the post. Kept getting an error in terminal
htconeroot Josh$ ./fastboot-mac flash zip Rom.zip
sending 'zip' (1029700 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
Joshuas-MacBook-Pro:htconeroot Josh$ ./fastboot-mac flash zip Rom.zip
ERROR: could not clear input pipe; result -536870163< waiting for device >
./fastboot-mac flash zip Rom.zip
I am now stuck at the fastboot screen. It say tampered, relocked, security warning. I can't get into recovery or anything. It just returns me to this screen.
How can I fix this?
Thanks,
Blue

I was able to re-unlock the bootloader using htc dev...so I have access to my phone again. Still trying to figure out how to return it to stock using a mac, but at least its usable again.
Sorry for the post,
Blue

Help please
BlueGoldAce said:
I was able to re-unlock the bootloader using htc dev...so I have access to my phone again. Still trying to figure out how to return it to stock using a mac, but at least its usable again.
Sorry for the post,
Blue
Click to expand...
Click to collapse
How did you get your phone working again? This is what I've been getting:
./fastboot flash zip RUU2.zip
sending 'zip' (101972 KB)... OKAY
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
Do you know what to do about this?

cowkong said:
How did you get your phone working again? This is what I've been getting:
./fastboot flash zip RUU2.zip
sending 'zip' (101972 KB)... OKAY
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
Do you know what to do about this?
Click to expand...
Click to collapse
I'm guessing your trying to use the 1.29 RUU with 1.31....
Follow this http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app

cowkong said:
How did you get your phone working again? This is what I've been getting:
./fastboot flash zip RUU2.zip
sending 'zip' (101972 KB)... OKAY
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
Do you know what to do about this?
Click to expand...
Click to collapse
Are you running version 1.32? or whatever it is...
The ruu you are trying to push is for version 1.29. As indirect states in the post, you need to the do following:
"fastboot boot recovery and then do this:
adb shell
echo 1.29.00 | dd if=/dev/block/mmcblk0p19 bs=1 skip=160
and then just fastboot oem lock and run the RUU"
Again, I can't take credit for this, its indirect's work, but it works.
You just need to get into recovery, and type in the echo portion of the message while in abd shell. Then get into fastboot and you can push the ruu.
Does that help?
-Blue

BlueGoldAce said:
Are you running version 1.32? or whatever it is...
The ruu you are trying to push is for version 1.29. As indirect states in the post, you need to the do following:
"fastboot boot recovery and then do this:
adb shell
echo 1.29.00 | dd if=/dev/block/mmcblk0p19 bs=1 skip=160
and then just fastboot oem lock and run the RUU"
Again, I can't take credit for this, its indirect's work, but it works.
You just need to get into recovery, and type in the echo portion of the message while in abd shell. Then get into fastboot and you can push the ruu.
Does that help?
-Blue
Click to expand...
Click to collapse
Thanks for the in depth reply. I've tried the flashing the latest RUU.zip file even with the adb commands. I'm still getting this error:
./fastboot flash zip RUUnew.zip
sending 'zip' (1032712 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
I'm having trouble accessing the internal memory. In twrp and cwm recovery, they state that the internal memory is 0MB.

I would pm indirect. He will be of more help than I can.

BlueGoldAce said:
I would pm indirect. He will be of more help than I can.
Click to expand...
Click to collapse
So my question is ...u were able to run the RUU on a mac from indirects thread.. ??
Sent from my HTCONE using xda app-developers app

Actually I did all the adb and fast boot commands with my Mac, and then I ran an ruu using an old windows.
I believe you should be able to do it all via abd and fast boot with you Mac.

BlueGoldAce said:
Actually I did all the adb and fast boot commands with my Mac, and then I ran an ruu using an old windows.
I believe you should be able to do it all via abd and fast boot with you Mac.
Click to expand...
Click to collapse
Not sure I've read that RUU'S are for pc only...but I saw JUS the ONE video available...with a guy running a RUU on mac...??
Sent from my HTCONE using xda app-developers app

I would think pushing the ruu via fastboot, as directed in that thread, should work.,,, but maybe not.
Running an ruu on a Mac requires using wine... Or running windows through parallel desktops.

BlueGoldAce said:
I would think pushing the ruu via fastboot, as directed in that thread, should work.,,, but maybe not.
Running an ruu on a Mac requires using wine... Or running windows through parallel desktops.
Click to expand...
Click to collapse
Yup that's what I thought ... To run a RUU wine would be needed and spoke good timing...lol I'll wait to borrow a pc.:thumbup:
Sent from my HTCONE using xda app-developers app

[Q] Can't seem to get any rom to work. A beer to whomever can help me out!

I've tried a number of different combinations to get my HTC One running on a custom ROM, and none of them seem to work.
S-ON
HBOOT=1.56.0000
Click to expand...
Click to collapse
I've tried using both TWRP and CWM, and tried installing both the latest Viper and Bad Boyz roms. Regardless, installation completes successfully (apparently) and the phone reboots. It gets past the loading screen, then to a locked home screen. Upon unlock, all I see is a white screen with the HTC logo.
Sometimes, I'll get a dialog with the following error:
Process com.htc.htcdialer isn't responding
Click to expand...
Click to collapse
The phone then reboots itself, and the cycle begins again.
I will happily through a beer, coffee, or other beverage of choice (or equivalent) to whomever is able to help me out. Thank you!

You did do a full wipe in recovery correct? I've flashed both of those no problem.
Sent from my HTCONE using Tapatalk

Bairdog35 said:
You did do a full wipe in recovery correct? I've flashed both of those no problem.
Click to expand...
Click to collapse
I have, yes. Does not appear to make a difference, unfortunately. Performed full wipes, made sure to wipe both caches upon install, still stuck.

kadjar said:
I have, yes. Does not appear to make a difference, unfortunately. Performed full wipes, made sure to wipe both caches upon install, still stuck.
Click to expand...
Click to collapse
You are using a Sprint HTC one correct? May be a stupid question for me to ask, but you'd be surprised how easily people get lost here!
Sent from my HTCONE using Tapatalk

Bairdog35 said:
You are using a Sprint HTC one correct? May be a stupid question for me to ask, but you'd be surprised how easily people get lost here!
Click to expand...
Click to collapse
I am indeed I appreciate you making sure! I can't help but wonder if I did something similarly dumb to bungle this thing.

kadjar said:
I am indeed I appreciate you making sure! I can't help but wonder if I did something similarly dumb to bungle this thing.
Click to expand...
Click to collapse
You are in a pickle haha, this is what I would do. If your phone is not in a working state, RUU back to stock, then unlock the boot loader again, flash TWRP recovery, try flashing your Rom of choice. I bet after that process your Rom will boot and run just fine.
Sent from my HTCONE using Tapatalk

Bairdog35 said:
You are in a pickle haha, this is what I would do. If your phone is not in a working state, RUU back to stock, then unlock the boot loader again, flash TWRP recovery, try flashing your Rom of choice. I bet after that process your Rom will boot and run just fine.
Click to expand...
Click to collapse
Darn. Do you happen to know if there's any way to RUU on a mac? Everything I've seen so far seems to utilize a .exe

I would also re-download your ROM/S you wish to try, it's amazing how easily an error can come from the download itself and not show up until it's flashed
Process of Elimination.
Bashing away at my HTC Desire C

kadjar said:
I've tried a number of different combinations to get my HTC One running on a custom ROM, and none of them seem to work.
I've tried using both TWRP and CWM, and tried installing both the latest Viper and Bad Boyz roms. Regardless, installation completes successfully (apparently) and the phone reboots. It gets past the loading screen, then to a locked home screen. Upon unlock, all I see is a white screen with the HTC logo.
Sometimes, I'll get a dialog with the following error:
The phone then reboots itself, and the cycle begins again.
I will happily through a beer, coffee, or other beverage of choice (or equivalent) to whomever is able to help me out. Thank you!
Click to expand...
Click to collapse
try reflashing the latest radio with twrp recovery, you can find them in flashable zips here in the threads.

kadjar said:
Darn. Do you happen to know if there's any way to RUU on a mac? Everything I've seen so far seems to utilize a .exe
Click to expand...
Click to collapse
Man this is just not your day haha
Download this http://www.androidfilehost.com/?fid=23329332407573774
Unzip it, you will find Rom.zip inside the folder.
I'm assuming you have fastboot working on your Mac
Reboot your phone into boot loader, select fastboot, plug into Mac.
Make sure you relock your boot loader.
Move that Rom.zip into the folder that fastboot is found on mac.
Type the following commands
1. fastboot oem rebootRUU
2. fastboot flash zip rom.zip
3. fastboot flash zip rom.zip
4. fastboot reboot
Yes you need to do fastboot flash zip Rom.zip twice, it will fail the first time.
Let it do its thing then reboot. You should have your phone back to stock!
Sent from my HTCONE using Tapatalk

Followed your instructions, but it seems to be failing (more than once)
Any guesses as to what I'm doing wrong?
Code:
➜ platform-tools ./fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
ERROR: usb_read failed with status e00002c0
FAILED (status read failed (No such file or directory))
finished. total time: 1.131s
➜ platform-tools ./fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.035s]
finished. total time: 0.035s
➜ platform-tools ./fastboot flash zip /Users/garrett/Dev/android/stock.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 120085191 is not a multiple of the block size 4096
sending sparse 'zip' (1476856 KB)...
error: write_sparse_skip_chunk: don't care size 120085191 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 120085191 is not a multiple of the block size 4096
OKAY [ 86.741s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 237.804s
➜ platform-tools ./fastboot flash zip /Users/garrett/Dev/android/stock.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 124279495 is not a multiple of the block size 4096
sending sparse 'zip' (1478186 KB)...
error: write_sparse_skip_chunk: don't care size 124279495 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 124279495 is not a multiple of the block size 4096
OKAY [ 70.744s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 222.003s
➜ platform-tools ./fastboot flash zip /Users/garrett/Dev/android/stock.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 128047815 is not a multiple of the block size 4096
sending sparse 'zip' (1476924 KB)...
error: write_sparse_skip_chunk: don't care size 128047815 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 128047815 is not a multiple of the block size 4096
OKAY [ 69.791s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 220.860s

Your fastboot exe may be bad, try installing from this thread - http://forum.xda-developers.com/showthread.php?t=2588979

Bairdog35 said:
Man this is just not your day haha
Download this http://www.androidfilehost.com/?fid=23329332407573774
Unzip it, you will find Rom.zip inside the folder.
I'm assuming you have fastboot working on your Mac
Reboot your phone into boot loader, select fastboot, plug into Mac.
Make sure you relock your boot loader.
Move that Rom.zip into the folder that fastboot is found on mac.
Type the following commands
1. fastboot oem rebootRUU
2. fastboot flash zip rom.zip
3. fastboot flash zip rom.zip
4. fastboot reboot
Yes you need to do fastboot flash zip Rom.zip twice, it will fail the first time.
Let it do its thing then reboot. You should have your phone back to stock!
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
You, sir, I owe a beer. Back up and running on stock, managed to root stock as well. PM me your paypal?

kadjar said:
You, sir, I owe a beer. Back up and running on stock, managed to root stock as well. PM me your paypal?
Click to expand...
Click to collapse
Seems you found it, thank you greatly. If you need anything, don't be afraid to pm me
Sent from my HTCONE using Tapatalk

Htc one A9 firmware flashing problem
htc one a9 (model: 2PQ9100) see the error below i'm facing please help me i am very upset :crying:
C:\adb>fastboot oem rebootRUU
...
OKAY [ 0.047s]
finished. total time: 0.048s
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1166400000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 617001178 is not a multiple of the block size 4096
sending sparse 'zip' (1139061 KB)...
error: write_sparse_skip_chunk: don't care size 617001178 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 617001178 is not a multiple of the block size 4096
OKAY [ 53.554s]
writing 'zip'...
(bootloader) HOSD CL#853511
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_z
(bootloader) EOonp
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 91.572s

First thing I would do is get a fresh download of the RUU update and try that.

Help - Stuck in Bootloop

The point in which everything took a turn for the worst was while trying to update firmware via SD update method. At which point it just stayed on android boot screen.
Recovery was broken at this point
I successfully flashed an older CWM version, but that was useless for reflashing the latest Asus firmware.
I tried flashing stock recovery again and it appeared to succeed, but now when I try to boot to recovery, it just goes back to bootloop.
I'm trying to flash the US version now via fastboot I get bootloop again and I'm getting weird errors every time I try regarding filesize. (See below)
I tried flashing CROMbi as well and it went through the install process successfully, but that resulted in bootloop as well.
Tried flashing Asus US firmware again without success,
Kind of pissed that this all started when following the instructions on the Asus site to upgrade to their latest firmware via SD card.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system
asusus.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 425021387 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.457s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 425021387 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 425021387 is not a multiple of t
he block size 4096
OKAY [ 86.837s]
writing 'system'...
OKAY [ 17.080s]
sending sparse 'system' (415060 KB)...
OKAY [ 57.305s]
writing 'system'...
OKAY [ 11.353s]
finished. total time: 174.042s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.021s
C:\Program Files (x86)\Minimal ADB and Fastboot>

Last time something like this happened, I had to wipe everything and reflash. so I did the following.
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 erase cache
fastboot -i 0x0b05 erase userdata
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 erase staging
fastboot -i 0x0b05 erase system
and now I get a bootloader error on startup
I was able to successfully flash CWM 6037 again. I tried newer ones, but 6037 is the only one that will work.
Stock firmware from custom recovery fails every time. "Installing update... Installation aborted."
Crombi installer goes through without any problems. but just never boots once completed.
I tried installing the latest Cyanogen Nightly and got the following error "This package is for tF701T devices; this is a K00C."
But the K00C is a TF701T
After installing CROMbi again, I'm no longer getting the bootloader error in red letters, but I am still bootlooping.
When crombi installer completes I do get one error at the very end. "set_metadata_recursive:some changes failed".
I looked at the log and it says Cant partition non-vfat datamedia.
Does bootloop after apparently successful fstboot flash have anythignt o do with why in the FAW's ASUS recommends ignoring the software update for 4.3? Afterall this is what put me in this situation.

The SD update is designed to work with the stock recovery. What made you think it would work with CWM?
The only successful recovery from a similar situation I remember is the following (and I'm quoting from memory here - it's too late here for me to find the thread, but it is somewhere here in this forum - search for it.
Download the stock recovery to your fastboot folder from here: http://droidbasement.com/db-blog/?p=3210
Also download the 10.26.1.18 firmware, unzip it once, put it on a microSD and insert into tablet.
Enter fastboot mode
Issue:
Code:
fastboot [b]boot[/b] recovery.img
Note: You do not flash the recovery, you boot it!
The recovery should recognize the firmware on the microSD and start to flash it.
If that is successful, you would have stock recovery and firmware again.
Then download the latest firmware, unzip it, put into microSD or internal and the stock recovery should flash it.
Good luck!
Sent from my K00C using Tapatalk

berndblb said:
The SD update is designed to work with the stock recovery. What made you think it would work with CWM?
The only successful recovery from a similar situation I remember is the following (and I'm quoting from memory here - it's too late here for me to find the thread, but it is somewhere here in this forum - search for it.
Download the stock recovery to your fastboot folder from here: http://droidbasement.com/db-blog/?p=3210
Also download the 10.26.1.18 firmware, unzip it once, put it on a microSD and insert into tablet.
Enter fastboot mode
Issue:
Code:
fastboot [b]boot[/b] recovery.img
Note: You do not flash the recovery, you boot it!
The recovery should recognize the firmware on the microSD and start to flash it.
If that is successful, you would have stock recovery and firmware again.
Then download the latest firmware, unzip it, put into microSD or internal and the stock recovery should flash it.
Good luck!
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
The attempted SD update was done with custom recovery as I couldn't get stock recovery to work after the initial SD update with stock recovery.
Thanks for the info. I'll update.

gorilla p said:
Last time something like this happened, I had to wipe everything and reflash. so I did the following.
fastboot -i 0x0b05 erase boot
fastboot -i 0x0b05 erase cache
fastboot -i 0x0b05 erase userdata
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 erase staging
fastboot -i 0x0b05 erase system
and now I get a bootloader error on startup
I was able to successfully flash CWM 6037 again. I tried newer ones, but 6037 is the only one that will work.
Stock firmware from custom recovery fails every time. "Installing update... Installation aborted."
Crombi installer goes through without any problems. but just never boots once completed.
I tried installing the latest Cyanogen Nightly and got the following error "This package is for tF701T devices; this is a K00C."
But the K00C is a TF701T
After installing CROMbi again, I'm no longer getting the bootloader error in red letters, but I am still bootlooping.
When crombi installer completes I do get one error at the very end. "set_metadata_recursive:some changes failed".
I looked at the log and it says Cant partition non-vfat datamedia.
Does bootloop after apparently successful fstboot flash have anythignt o do with why in the FAW's ASUS recommends ignoring the software update for 4.3? Afterall this is what put me in this situation.
Click to expand...
Click to collapse
That error message means that your internal sdcard is no t available to format. Erasing all partitions is a dangerous thing to do.
The only way you will get back to normal is to try and flash the stock asus rom now as that will recreate everything. I recommend you start with the 4.2.2 one - need to flash it over fastboot - I can't see anything else working as you have erased it all.....
Also you used 0x0b05 which is the code for the last generation of transformers..... You don't need it for the TF701 but not sure if that has caused additional grief now. Probably not but you never know .....

Yeah IO'm getting the same issue that I was having before. I tried both the 4.3 and 4.2 boot.img and the recommended recovery.img file. Each time I ran
fasboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.121s]
booting...
OKAY [ 0.032s]
finished. total time: 1.157s
booting from downloaded boot.img (on tablet)
Then it goes to boot into the image and...bootloop.
C:\Program Files (x86)\Minimal ADB and Fastboot\asus>fastboot flash system asus4
22.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 346827884 is not a multiple of t
he block size 4096
erasing 'system'...
OKAY [ 1.515s]
sending sparse 'system' (628732 KB)...
error: write_sparse_skip_chunk: don't care size 346827884 is not a multiple of t
he block size 4096
error: write_sparse_skip_chunk: don't care size 346827884 is not a multiple of t
he block size 4096
OKAY [ 86.861s]
writing 'system'...
OKAY [ 17.098s]
sending sparse 'system' (338700 KB)...
OKAY [ 46.823s]
writing 'system'...
OKAY [ 9.280s]
finished. total time: 161.586s
Bootloop...
Could the inability to flash or boot from stock recovery have anything to do with the CWM recovery protection?

Well after those attempts it's totally shot.
Now I can't even get to fastboot. Every reboot results in "Unrecoverable bootloader error..."
Files RMA. Returned.
Moral of story. Don't do anything on a Tegra device without previous documentation that doesn't have NVFlash available.

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:

What to do with a fully cleansed phone?

My attempt to install a custom rom has failed horribly and I'm left with a wiped phone. Is there a way to reinstall EMUI? Or still somehow get a custom rom?
I flashed lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bvS.img on system, but although there was no error message it didn't seem to do anything.
It's a LLD-L31

hasl3r said:
Is there a way to reinstall EMUI?
Click to expand...
Click to collapse
Maybe, in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...

-Alf- said:
Maybe, in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...
Click to expand...
Click to collapse
I don't seem able to get into fastboot anymore, only TWRP 3.2.1-0 boots. The menu "Reboot - Fastboot" leads back to TWRP and running "adb reboot fastboot" from console as well.

hasl3r said:
I don't seem able to get into fastboot anymore, only TWRP 3.2.1-0 boots. The menu "Reboot - Fastboot" leads back to TWRP and running "adb reboot fastboot" from console as well.
Click to expand...
Click to collapse
- Try the following: turn off your phone, press and hold Volume Down and connect phone to PC.
- Can you boot into eRecovery? (turn off, connect to PC and press and hold Power & Vol Up). If so, try to update phone via Wifi and option "Download latest....".
hasl3r said:
The menu "Reboot - Fastboot" leads back to TWRP and running "adb reboot fastboot" from console as well.
Click to expand...
Click to collapse
Do you have TWRP installed instead of Recovery or eRecovery?
hasl3r said:
It's a LLD-L31
Click to expand...
Click to collapse
What is your regional variant? (Cxxx)

-Alf- said:
- Try the following: turn off your phone, press and hold Volume Down and connect phone to PC.
Click to expand...
Click to collapse
That worked, I'm not around a PC at the moment, I'll run the commands as soon as possible
-Alf- said:
- Can you boot into eRecovery? (turn off, connect to PC and press and hold Power & Vol Up). If so, try to update phone via Wifi and option "Download latest....".
Do you have TWRP installed instead of Recovery or eRecovery?
Click to expand...
Click to collapse
That booted into TWRP as well, so I guess?
-Alf- said:
What is your regional variant? (Cxxx)
Click to expand...
Click to collapse
How to I find that out? I tried google but didn't find information.
All else I got are the IMEI and:
Serial number: FPM4C18622002338
Product ID: 71171281
Many thanks already for your help btw

hasl3r said:
How to I find that out?
Click to expand...
Click to collapse
through the mentioned fastboot commands.

-Alf- said:
through the mentioned fastboot commands.
Click to expand...
Click to collapse
>> fastboot oem get-build-number
(bootloader) :LLD-L31 9.1.0.189(C432E10R1P4)
>> fastboot oem get-product-model
(bootloader) LLD-L31
>> fastboot getvar vendorcountry
vendorcountry: hw/eu
>> fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :LLD-L31-CUST 9.1.0.10(C432)
>> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :LLD-L31 9.1.0.117(C432E4R1P3)

hasl3r said:
>> fastboot oem get-build-number
(bootloader) :LLD-L31 9.1.0.189(C432E10R1P4)
>> fastboot oem get-product-model
(bootloader) LLD-L31
>> fastboot getvar vendorcountry
vendorcountry: hw/eu
>> fastboot oem oeminforead-CUSTOM_VERSION
(bootloader) :LLD-L31-CUST 9.1.0.10(C432)
>> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :LLD-L31 9.1.0.117(C432E4R1P3)
Click to expand...
Click to collapse
Okay, try the following:
1. Download Service ROM
Unpack it, there's a dload file in Software folder. Copy dload as it is to the SD Card (without unpacking it!)
2. Download TWRP 3.2.1 https://mega.nz/#!tkcTlATI!A8UJGPBGtxJbLcUOJoxCGJj5PFZXzCnjbb3OkwqKTP8
and copy it to SD Card
3. also copy to SD stock Recovery_ramdisk-9.1.img , download here:
https://mega.nz/#!M0FHlYhb!4yWz8Onr3D1NATel4mZSK4SNdd5B3p6dnPg6oXPGWl8
4. Boot into your TWRP, select storage - SD Card, select "Install image", find TWRP-9.1 file and mark eRecovery, swipe. Go back, find recovery_ramdisk-9.1 file , mark Recovery, swipe.
5.Turn off the phone, use option 'Power Off' in TWRP's menu.
6. Press and hold Power & both Volume buttons .

-Alf- said:
Okay, try the following:
Click to expand...
Click to collapse
Amazing, thank you so much!
-Alf- said:
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...
Click to expand...
Click to collapse
Having the phone running again gave me hope, so I'll try to flash LineageOS 17.1 tomorrow.

hasl3r said:
Amazing, thank you so much!
Having the phone running again gave me hope, so I'll try to flash LineageOS 17.1 tomorrow.
Click to expand...
Click to collapse
Glad to help

-Alf- said:
Glad to help
Click to expand...
Click to collapse
Sorry to bother you again, just wondering if you have any advice. I tried flashing LineageOS 17.1, but realised that the bootloader is locked again. My unlock code doesn't seem to work anymore (check password failed) and I figured it's because I have to downgrade EMUI 9.1 to 8.0. Took me a while, but turns out that was not the issue.
Do you happen to have any idea what to try? Do I have to buy another DC Unlocker license?
I don't know if it's related, but "adb reboot fastboot" just reboots the device and I have to use the volume down key to get there.

hasl3r said:
the bootloader is locked again.
Click to expand...
Click to collapse
it's normal after using dload method
hasl3r said:
My unlock code doesn't seem to work anymore
Click to expand...
Click to collapse
Unlock code is permanent. Is OEM unlocking turned on in Developer options? (FRP unlock on fastboot screen?)

-Alf- said:
Unlock code is permanent. Is OEM unlocking turned on in Developer options? (FRP unlock on fastboot screen?)
Click to expand...
Click to collapse
Turns out the problem was copy/pasting the unlock code instead of hand typing it..
So I could flash it, but then the reset failed. Just realised that EMUI 9.1 is a requirement though, so I'll flash that first and try again.

Edit: Nvm fixed it. Sorry if you got a notification anyway.

-Alf- said:
If you want to flash GSI custom ROM , look here or here .
(ANE and LLD are basically identical devices).
Btw, I'm running LOS 19.0 by Andy Yan on ANE-LX1, works like a charm...
Click to expand...
Click to collapse
Hmm I tried it with a clean stock 9.1 but flashing didn't work
If you have no ideas, I'll just stick with the stock installation.
Code:
>> fastboot flash system losq-v224-201017-arm64-bgN.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (460796 KB)...
OKAY [ 12.198s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 12.678s
Code:
>>fastboot flash system "caos-v315+220228-arm64-bgZ.img"
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/7 (460796 KB)...
OKAY [ 12.284s]
writing 'system' 1/7...
FAILED (remote: sparse flash write failure)
finished. total time: 12.730s

hasl3r said:
Hmm I tried it with a clean stock 9.1 but flashing didn't work
If you have no ideas, I'll just stick with the stock installation.
Code:
>> fastboot flash system losq-v224-201017-arm64-bgN.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (460796 KB)...
OKAY [ 12.198s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 12.678s
Code:
>>fastboot flash system "caos-v315+220228-arm64-bgZ.img"
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/7 (460796 KB)...
OKAY [ 12.284s]
writing 'system' 1/7...
FAILED (remote: sparse flash write failure)
finished. total time: 12.730s
Click to expand...
Click to collapse
1. be sure that your bootloader is unlocked, try to unlock it again
2. In fastboot mode run command
fastboot erase system
and try to flash GSI again
3. Install TWRP 3.2.1 gaguga edition, in TWRP select Mount - mark System, go back, select Wipe > Advanced > mark System > Repaire or etc. > Resize file system > confirm, reboot .
Then flash back stock recovery and try to install GSI.
4. Downgrade to the lower build number via dload method
5. idk...