HTC ONE M8 International (Flash Issue) - Android Q&A, Help & Troubleshooting

hii.
i am new on this site and android too but about 3 days gone after i was tring to flash android but with noluck.
1.i have bootloader unlocked and s-on
2.i have 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip downloaded from this site
3.i also tried to flash androd i create new folder and fill this files:adb, AdbWinApi, AdbWinUsbApi, fastboot, rom(witch is 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip)
4.i launch htc one m8 bootloader mode and use this commands :
fastboot devices
fastboot oem rebootRUU
fastboot flash rom.zip
and here is error:
sending 'zip' (1687272 KB)... OKAY
writing 'zip'... INFOzip header checking...
FAILED (remote: 32 header error)
need to fix this issue please help me on this
HTC_E11 version

Related

[Q] can not flash radio.img

hi all,
I'm HBOOT 1.5 and htcdev method to unlocked(but s-on), but can not flash radio.img, fastboot flash radio radio.img said:
sending 'radio' (17505 KB)...
OKAY [ 3.859s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.469s
the radio.img is extracted from PG86IMG.zip of 2.08.561.2.
Also, I can not flash wimax.img.
But, I can flash boot.img,recovery.img successfully, and totally updated with RUU 2.08.561.2 successfully. But when I try to flash radio.img,wimax.img with fastboot, it show above message; I tried toput radio.img,wimax.img onto the sd card(pachaged by PG86IMG.zip), hboot can find PG86IMG.zip, but after parsing the package, bootloader just ignore it and give nothing hint.
Any other method to flash radio.img? Thanks in advance!

[Q] HELP! Can't get to bootloader (S-on)

Hello!
I installed Munjeni's special hboot partition (to increase usable space) and wanted to update the phone back to stock (to take back to att).
The RUU utility failed with code of 152.
The partition failed.
Now the phone is "stuck" at the black HTC screen with four warning triangles in each corner.
Any ideas?
I can fastboot and issue some commands...
I am s-on, hboot 1.02.
Thanks in advance!
DanGeorges said:
Hello!
I installed Munjeni's special hboot partition (to increase usable space) and wanted to update the phone back to stock (to take back to att).
The RUU utility failed with code of 152.
The partition failed.
Now the phone is "stuck" at the black HTC screen with four warning triangles in each corner.
Any ideas?
I can fastboot and issue some commands...
I am s-on, hboot 1.02.
Thanks in advance!
Click to expand...
Click to collapse
If the bootloader is accessible, you can try grabbing the rom.zip out of the RUU (run it & let it load, then search in Windows' temporary folder for "rom.zip". If not there's probably a download somewhere), and rename it to "LIBEIMG.zip" on the root of the SD card.
Then boot into the bootloader (vol down) and it should pick it up and start flashing (might be a confirmation before it does)
Edit: Well I looked at the title again... does this mean its not accessible?
It should be if fastboot is, but I've never had the bad triangles so not completely sure..
If not, alternate option that may work: extract the hboot image from rom.zip and flash it with fastboot (if its allowed)
This is the RUU zip: http://www.mediafire.com/?tay1j415ymvukh5
drumist said:
This is the RUU zip: http://www.mediafire.com/?tay1j415ymvukh5
Click to expand...
Click to collapse
Thank you for the link. I'm downloading it now.
I can fastboot, but I'm S-on (from one of my flashes).
What's the fastboot command for flashing the hboot? Will this even let me?
I'll give this a try. Thanks again!
When I try to fastboot flash a recovery, here's what I get:
C:\Mobile\Android\Fastboot and ADB Tool>fastboot flash recovery recovery.img
sending 'recovery' (3716 KB)... OKAY [ 0.875s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.578s
C:\Mobile\Android\Fastboot and ADB Tool>
For hboot - does anyone have an idea which hboot I can try flashing?
WinSuk said:
If the bootloader is accessible, you can try grabbing the rom.zip out of the RUU (run it & let it load, then search in Windows' temporary folder for "rom.zip". If not there's probably a download somewhere), and rename it to "LIBEIMG.zip" on the root of the SD card.
Then boot into the bootloader (vol down) and it should pick it up and start flashing (might be a confirmation before it does)
Edit: Well I looked at the title again... does this mean its not accessible?
It should be if fastboot is, but I've never had the bad triangles so not completely sure..
If not, alternate option that may work: extract the hboot image from rom.zip and flash it with fastboot (if its allowed)
Click to expand...
Click to collapse
I'll try the hboot image and see what happens.
What's the fastboot command?
I tried:
fastboot flash hboot
and
fastboot flash boot
Both gave me an invalid signature:
C:\>fastboot flash hboot hboot_liberty_7227_1.02.0000_101104.nb0
sending 'hboot' (512 KB)... OKAY [ 0.234s]
writing 'hboot'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.328s
C:\>fastboot flash boot hboot_liberty_7227_1.02.0000_101104.nb0
sending 'boot' (512 KB)... OKAY [ 0.234s]
writing 'boot'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.328s

HTC RIDER_X515E unable to unlock with unlock code.bin

Dear Experts,
I received HTC Rider X515E with locked bootloader + S-OFF+ 4EXT recovery + custom rom installed.
It have some wifi issue, i have download another custom rom but when i flashed its stuck on htc logo.
then i have flash official "RUU_RIDER_ICS_35_S_KT_KR_3.09.1010.8_Radio_11.24.3504.18_M_release_262166_signed" after that phone boot normaly but korean sms problem then i go to www.htcdev.com to unlock bootloader for REXT recovery installing.
i have follow all instrucion by htcdev.com and flash the unlock_code.bin but it doest not show unlock boot loader screen and my bootloader still locked.
please find below my unlocking logs
Code:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.144s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.152s
when i enter same command 2nd time so i got this
Code:
C:\adb>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 0.005s
Please let me know how i can unlock bootloader should i need to downgarde or anything else...
Try "fastboot flash unlocktoken unlock_code.bin"
Don't add the adb line in the beginning, that involves the adb application. You need to use the fastboot application.
Sent from my Evo 3D CDMA using Tapatalk 2
VictoriousShooter said:
Try "fastboot flash unlocktoken unlock_code.bin"
Don't add the adb line in the beginning, that involves the adb application. You need to use the fastboot application.
Sent from my Evo 3D CDMA using Tapatalk 2
Click to expand...
Click to collapse
He isn't. That's just the directory he is in
私のEVO 4G LTEから送信される。

[SOLVED] Flash recovery RELOCKED S-OFF LATEST OTA (FAILED (remote: not allowed)

Try this at your own risk. I do not take any responsibility, read on if you accept the risks.
I have discovered a working solution for people that have S-OFF RELOCKED and took the latest/last OTA update but cant flash a recovery via fastboot and cant re-unlock.
When i tried the following in fastboot
fastboot flash recovery recovery.img (place your favorite recovery into platform-tools folder)
< waiting for device >
sending 'recovery' (8758 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.049s
It errors out by using TWRP and CWM FAILED (remote: not allowed)
INSTRUCTIONS:
download the attached recovery.zip and place it into platform-tools (TWRP recovery)
fastboot oem rebootRUU
---wait for black HTC logo--
fastboot flash zip recovery.zip
--it will show a progress bar on your phone, and finished in the CMD window--
fastboot reboot bootloader
select recovery
profit
Can someone confirm that flashing recovery works with the method above. Also post what version software you are running. Someone with S-ON LOCKED please try this, possible new way to flash ROMS without S-OFF/unlock?
Awesome
I know it's been a while since you posted this, but THANK YOU. Worked a charm on my S-OFF Relocked 3.06. I even modified the zip file, removed the older version of TWRP, inserted a new version (renamed as recovery.img) and now have the most recent TWRP.
Droidel said:
Try this at your own risk. I do not take any responsibility, read on if you accept the risks.
I have discovered a working solution for people that have S-OFF RELOCKED and took the latest/last OTA update but cant flash a recovery via fastboot and cant re-unlock.
When i tried the following in fastboot
fastboot flash recovery recovery.img (place your favorite recovery into platform-tools folder)
< waiting for device >
sending 'recovery' (8758 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.049s
It errors out by using TWRP and CWM FAILED (remote: not allowed)
INSTRUCTIONS:
download the attached recovery.zip and place it into platform-tools (TWRP recovery)
fastboot oem rebootRUU
---wait for black HTC logo--
fastboot flash zip recovery.zip
--it will show a progress bar on your phone, and finished in the CMD window--
fastboot reboot bootloader
select recovery
profit
Can someone confirm that flashing recovery works with the method above. Also post what version software you are running. Someone with S-ON LOCKED please try this, possible new way to flash ROMS without S-OFF/unlock?
Click to expand...
Click to collapse
not working on my htc droid dna firmware version 4.09.605.5
Droidel said:
Try this at your own risk. I do not take any responsibility, read on if you accept the risks.
I have discovered a working solution for people that have S-OFF RELOCKED and took the latest/last OTA update but cant flash a recovery via fastboot and cant re-unlock.
When i tried the following in fastboot
fastboot flash recovery recovery.img (place your favorite recovery into platform-tools folder)
< waiting for device >
sending 'recovery' (8758 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.049s
It errors out by using TWRP and CWM FAILED (remote: not allowed)
INSTRUCTIONS:
download the attached recovery.zip and place it into platform-tools (TWRP recovery)
fastboot oem rebootRUU
---wait for black HTC logo--
fastboot flash zip recovery.zip
--it will show a progress bar on your phone, and finished in the CMD window--
fastboot reboot bootloader
select recovery
profit
Can someone confirm that flashing recovery works with the method above. Also post what version software you are running. Someone with S-ON LOCKED please try this, possible new way to flash ROMS without S-OFF/unlock?
Click to expand...
Click to collapse
Thank you thank you thank you so much.
luis181193 said:
Thank you thank you thank you so much.
Click to expand...
Click to collapse
aminebigboss said:
not working on my htc droid dna firmware version 4.09.605.5
Click to expand...
Click to collapse
Mine work!!
htc droid dna firmware version 4.09.605.5

Tried to flash Marshmallow factory image, but failing

So I tried the flash-all to update to new version, and it failed with the system.img error everyone talks about.
I saw that that was common, so I went ahead with flashing each image separately. However, when I try to flash the bootloader, I get the following error:
E:\adb\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk
\platform-tools>fastboot flash bootloader boot.img
target reported max download size of 518205818 bytes
sending 'bootloader' (8278 KB)...
OKAY [ 0.555s]
writing 'bootloader'...
(bootloader) Device State : Unlocked
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: header error)
finished. total time: 1.143s
Any idea how to fix this? Googling it didn't come up with anything. I just downloaded the newest version of fastboot by updating the android SDK today, so I don't think it's that.
I got the exact same error when I tried flashing my Nexus 5, before attempt my Nexus 9. I actually uninstalled the SDK and dowloaded and installed a whole fresh version and the Flash All script worked fine after that for both the N5 and N9. Both have been running great! The animations, volume slider for exampt, are so much smoother in M. Lots of little tweaks.
If it's working properly on the N9, fastboot will sparse the System image and send it to the device in multiple uploads and flashes.
Of course you would have failed. You have done it the wrong way. The bootloader command should be like:
fastboot flash bootloader bootloader.img
but you flashed bootloader with kernel boot.img

Categories

Resources