I've got a friend's HTC One M8 that's stuck in HBOOT. I can't flash a new recovery, I've tried both TWRP and CWM. Either time I get an error message "FAILED (remote: image update error)"
I'm at the end of my thread here with things I can try to fix it. I've searched almost all topics to no avail.
Here's the getvar dump:
C:\Users\Adrian>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
--
Device says *** UNLOCKED *** on screen, doesn't say TAMPERED (not sure what this is).
Anything fastboot commands usually result in a failed message but the device is recognized if I type "fastboot devices".
Here's a sample when trying to use Squabbi's toolkit:
target reported max download size of 1830727680 bytes
sending 'recovery' (24576 KB)...
OKAY [ 1.607s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.678s
I've tried using an ATT RUU, various recovery files, etc. The phone boots straight into HBOOT. Any other commands apart from fastboot on the device result in a quick flash of another screen and returns to the fastboot USB screen.
What can I do to get this device back up and running? For some reason I just can't get the recovery file to flash so I can move forward already. Am I missing something? I just got the device from a friend. He mentioned he was watching YT when all of a sudden the device went into this boot loop.
Thanks in advance!
adriankeith said:
I've got a friend's HTC One M8 that's stuck in HBOOT. I can't flash a new recovery, I've tried both TWRP and CWM. Either time I get an error message "FAILED (remote: image update error)"
Thanks in advance!
Click to expand...
Click to collapse
Hello
I'm no expert but it sounds like a radio issue
Have you tried a new RUU
Also what is your (bootloader) version-main:
Thanks
jcbjoe said:
Hello
I'm no expert but it sounds like a radio issue
Have you tried a new RUU
Also what is your (bootloader) version-main:
Thanks
Click to expand...
Click to collapse
Admittedly, I've got an iOS device myself so I'm going to have to defer to your expertise. I believe I've tried a new RUU (an ATT .exe file? It was a full blown installer, told me what version i was on, what version it would be updating to.. does this sound right?).
How can I get you the bootloader version?
adriankeith said:
Admittedly, I've got an iOS device myself so I'm going to have to defer to your expertise. I believe I've tried a new RUU (an ATT .exe file? It was a full blown installer, told me what version i was on, what version it would be updating to.. does this sound right?).
How can I get you the bootloader version?
Click to expand...
Click to collapse
C:\Users\Adrian>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: < --
jcbjoe said:
C:\Users\Adrian>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: < --
Click to expand...
Click to collapse
That was a straight copy paste from my command line. So.. I guess if there's nothing there.. ??
RUU
adriankeith said:
That was a straight copy paste from my command line. So.. I guess if there's nothing there.. ??
Click to expand...
Click to collapse
You can try this
1.58.502.1 full RUU
jcbjoe said:
You can try this
1.58.502.1 full RUU
Click to expand...
Click to collapse
Unfortunately, it seems with any of these RUU installers I get a USB connection error. I have to think it has something to do with me being unable to enable the USB Debugging mode of the phone.
Any other ideas?
adriankeith said:
Unfortunately, it seems with any of these RUU installers I get a USB connection error. I have to think it has something to do with me being unable to enable the USB Debugging mode of the phone.
Any other ideas?
Click to expand...
Click to collapse
Can you get into fastboot mode ?
IF you can get into fastboot mode we are fine .. we don't need adb
Think of fastboot as the bios and adb as the software
IF your usb is jacked you need to try another computer
EDIT: If fastboot works go to This Thread
The first download link is the firmware that you need
1. Download the firmware
2. Put your phone in fastboot mode
3. fastboot erase cache
4. fastboot oem rebootRUU
5. fastboot flash zip thefirmwareyoudownload.zip < -- if it fails you might have to do this 2x
6. fastboot reboot-bootloader
7. Tell us what you see after words
jcbjoe said:
Can you get into fastboot mode ?
IF you can get into fastboot mode we are fine .. we don't need adb
Think of fastboot as the bios and adb as the software
IF your usb is jacked you need to try another computer
Click to expand...
Click to collapse
I'm able to get into fastboot USB mode but any of the critical commands I've tried running (fastboot flash recovery image.img) all throw errors.
Like this --
sending 'recovery' (12846 KB)...
OKAY [ 1.272s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.341s
---
edit:
Here's the error I get when trying to erase the cache:
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.006s
Click to expand...
Click to collapse
adriankeith said:
I'm able to get into fastboot USB mode but any of the critical commands I've tried running (fastboot flash recovery image.img) all throw errors.
Like this --
sending 'recovery' (12846 KB)...
OKAY [ 1.272s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 1.341s
---
edit:
Here's the error I get when trying to erase the cache:
Click to expand...
Click to collapse
Did you flash the firmware file from the link i provided ?
Firmware < -- Flash this first .. don't flash anything individually .. you need to update the firmware don't unpack it
jcbjoe said:
Did you flash the firmware file from the link i provided ?
Firmware < -- Flash this first .. don't flash anything individually .. you need to update the firmware don't unpack it
Click to expand...
Click to collapse
How do I flash this file?
adriankeith said:
How do I flash this file?
Click to expand...
Click to collapse
Download it
.. once you download it you will see it says firmware.zip
Then you put it on your desktop or your Downloads folder
Then
1. fastboot erase cache
2. fastboot oem rebootRUU
3. fastboot flash zip firmware.zip < -- if it fails you might have to do this 2x (remember you flash it to where its at .. so if its in windows on your desktop it would be fastboot flash zip ~/Desktop/firmware.zip or in Downloads it would be fastboot flash zip ~/Downloads/firmware.zip
4. fastboot reboot-bootloader
5. Tell us what you see after words
jcbjoe said:
Download it
.. once you download it you will see it says firmware.zip
Then you put it on your desktop or your Downloads folder
Then
1. fastboot erase cache
2. fastboot oem rebootRUU
3. fastboot flash zip firmware.zip < -- if it fails you might have to do this 2x (remember you flash it to where its at .. so if its in windows on your desktop it would be fastboot flash zip ~/Desktop/firmware.zip or in Downloads it would be fastboot flash zip ~/Downloads/firmware.zip
4. fastboot reboot-bootloader
5. Tell us what you see after words
Click to expand...
Click to collapse
Here's the problem when I try to attempt the first command
C:\Users\Adrian>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.006s
adriankeith said:
Here's the problem when I try to attempt the first command
C:\Users\Adrian>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.006s
Click to expand...
Click to collapse
Can you rename the firmware.zip to 0p6bimg.zip
Once you do that put the file onto the root of your sdcard (meaning not in a folder)
Credits for the Below Method (an0ther Post# 1)
2. Simply move the "0p6bimg.zip" to the ROOT of your EXT micro sd card.
3. Boot to your boot loader. There are many ways to get to your boot loader. A lot of custom roms have it built into the restart menu. If you have usb debugging enabled its just "adb reboot bootloader" If you can't get there with one of these methods, simply make sure phone is on, hold vol up and power for 11 seconds until screen shuts off, let go and hold vol down and power until boot loader comes up. "about 4 seconds"
4. Click HBOOT in your boot loader. Your phone will automatically scan the file and ask if you want to update. Hit vol up for yes or vol down for no.
5. Phone will begin RUU restore. You can watch what it does on the screen as it will go through a list and bypasses are normal. It will reboot boot loader and you can watch progress bars in the top right corner. It goes through a TON of them so do NOT turn off phone for any reason and let it finish. The process takes about 15 minutes give or take. Once it is done, it will say complete, press power to reboot. Again do not power off phone or even touch it for that matter during this process.
jcbjoe said:
Can you rename the firmware.zip to 0p6bimg.zip
Once you do that put the file onto the root of your sdcard (meaning not in a folder)
Credits for the Below Method (an0ther Post# 1)
2. Simply move the "0p6bimg.zip" to the ROOT of your EXT micro sd card.
3. Boot to your boot loader. There are many ways to get to your boot loader. A lot of custom roms have it built into the restart menu. If you have usb debugging enabled its just "adb reboot bootloader" If you can't get there with one of these methods, simply make sure phone is on, hold vol up and power for 11 seconds until screen shuts off, let go and hold vol down and power until boot loader comes up. "about 4 seconds"
4. Click HBOOT in your boot loader. Your phone will automatically scan the file and ask if you want to update. Hit vol up for yes or vol down for no.
5. Phone will begin RUU restore. You can watch what it does on the screen as it will go through a list and bypasses are normal. It will reboot boot loader and you can watch progress bars in the top right corner. It goes through a TON of them so do NOT turn off phone for any reason and let it finish. The process takes about 15 minutes give or take. Once it is done, it will say complete, press power to reboot. Again do not power off phone or even touch it for that matter during this process.
Click to expand...
Click to collapse
Got a wrong zipped image while it was loading the zip file.
adriankeith said:
Got a wrong zipped image while it was loading the zip file.
Click to expand...
Click to collapse
Try any of the links in the Thread
You have to rename it to 0p6bimg.zip
jcbjoe said:
Try any of the links in the Thread
You have to rename it to 0p6bimg.zip
Click to expand...
Click to collapse
Yep, I renamed it to the 0P6BIMG.zip and when it began to load the file it agave me that error. I'll try that thread now.
--
Still getting the "Wrong Zipped Image!" error. I did this previously with a different firmware and it got through some of the process but bombed out after something and put me back in HBOOT. Couldn't launch recovery, couldn't launch anything. Fastboot USB shows up fine.
adriankeith said:
Yep, I renamed it to the 0P6BIMG.zip and when it began to load the file it agave me that error. I'll try that thread now.
--
Still getting the "Wrong Zipped Image!" error. I did this previously with a different firmware and it got through some of the process but bombed out after something and put me back in HBOOT. Couldn't launch recovery, couldn't launch anything. Fastboot USB shows up fine.
Click to expand...
Click to collapse
You Possibly have a bricked device
You can try chatting on freenode via irc
irc.freenode.net #sunshine-support or #htc-dev or #venomroms .. all these channels have htc devices m7 or m8
Thanks
jcbjoe said:
You Possibly have a bricked device
You can try chatting on freenode via irc
irc.freenode.net #sunshine-support or #htc-dev or #venomroms .. all these channels have htc devices m7 or m8
Thanks
Click to expand...
Click to collapse
I was coming to that conclusion quickly.
Thanks for your help though. I appreciate it.
adriankeith said:
Unfortunately, it seems with any of these RUU installers I get a USB connection error. I have to think it has something to do with me being unable to enable the USB Debugging mode of the phone.
Any other ideas?
Click to expand...
Click to collapse
Since you are s-in and bootloader unlocked, you need to relock the bootloader to run an RUU. This shouldn't give you a USB connection error, but its at least worth a try to relock.
Also, try to connect the phone to PC, go into Window Device Manager, and see if you can format the internal memory to FAT32. Some folks have had issues with internal memory corrupted, and cannot install recovery; and this fix worked for them.
---------- Post added at 10:17 AM ---------- Previous post was at 10:13 AM ----------
jcbjoe said:
You Possibly have a bricked device
Click to expand...
Click to collapse
I doubt it. So far, I've only seen on these forums one M8 where the screen still comes on, and extensive help from several folks couldn't get it back up and running. Being able to get into hboot means we can recover, 99.99% of the time.
Still a lot of things left to try.
Related
Okay, a little background here:
HTC Evo 4G LTE
Android Version: 2.3.3
Baseband Version: 2.15.00.11.19
Kernel Version 2.6.37.4-cyanogenmod
Mod Version: 7.0.3.1-supersonic
Okay so i acquired this phone in a trade (upgrading from a Evo 4G) and have attempted to activate it with my sprint number. Every time I get to the step where I have to press ##etc... the phone will not cooperate. From what I understand, this is due to the lack of sense.
I have clockwork recovery premium installed and am familiar with the procedure for flashing a rom. I just need someone to point me in the right direction of which rom I need to install/do other things to get this phone activated.
Any help would be greatly appreciated! If any additional info is needed, please let me know! Thanks!
Grab one of the roms from the development section like meanrom and flash it over, wipe the phone first, if you have any trouble booting to android fastboot the kernel
om4 said:
Grab one of the roms from the development section like meanrom and flash it over, wipe the phone first, if you have any trouble booting to android fastboot the kernel
Click to expand...
Click to collapse
Thank you for the fast response.
Well, I may have already messed up. I saw the check for updates button in clockwork recovery and downloaded the newest cyanogen mod that it recommended ( 7.2. something I think, I can't remember). I flashed it and it is now stuck on the boot logo.
Could I apply the fastboot thing you are talking about to this situation? If so, how do I do that on windows 7? Sorry for my ignorance.
Just grab a sense Rom like mean and flash it, it has a kernel installer built in. You really should be using teamwin recovery
http://db.tt/zyPbGmtO
Extract that and open cmd inside the folder, connect to fastboot and type fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img and once that's done flash meanrom
om4 said:
Just grab a sense Rom like mean and flash it, it has a kernel installer built in. You really should be using teamwin recovery
Extract that and open cmd inside the folder, connect to fastboot and type fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img and once that's done flash meanrom
Click to expand...
Click to collapse
okay i did the steps to the best of my understanding and i got this response in cmd.
recovery-twrp-2.2.2.0-jewel.i
sending 'recovery' (7356 KB).
OKAY [ 1.901s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.902s
Any suggestions?
Hmm so write failed, odd
Gotta think about this one, maybe someone else has a solution already
om4 said:
Hmm so write failed, odd
Gotta think about this one, maybe someone else has a solution already
Click to expand...
Click to collapse
I can still access my clockwork recovery. Could I just put the mean rom on an sd card and flash it through clockwork? Thanks for your help.
Cwm is not very reliable on our phones. Try it but if it doesn't boot you will need to extract boot.img and place it in the adb folder and flash it using fastboot flash boot boot.img
om4 said:
Cwm is not very reliable on our phones. Try it but if it doesn't boot you will need to extract boot.img and place it in the adb folder and flash it using fastboot flash boot boot.img
Click to expand...
Click to collapse
Okay, so I attempted to flash through clockwork recovery and got this message
"Error in /sdcard/MeanROM-ICS-V47-jewel-ltevo.zip
(Status 0)
Installation aborted."
I guess the installer is dependant on twrp, I'm not that familiar with cwm though
om4 said:
I guess the installer is dependant on twrp
Click to expand...
Click to collapse
Okay, well is there any way I can just completely wipe it and get it back to stock? Or anything? Sorry, I am just kind of freaking out a little right now...
Well there is the ruu, I'd try fastboot again though
When in bootloader type fastboot devices to make sure its connected, and try to flash twrp again
om4 said:
Well there is the ruu, I'd try fastboot again though
When in bootloader type fastboot devices to make sure its connected, and try to flash twrp again
Click to expand...
Click to collapse
Well it identifies it using the fastboot devices cmd. I tried to flash it again on another computer ending in the same error.
Is there any way that the recovery package you linked to could be faulty or something?
You can try downloading it again from the twrp website but if it had been bad I'm sure it would have failed the signature verification
Try fastboot getvar all and tell me what the output is
om4 said:
You can try downloading it again from the twrp website but if it had been bad I'm sure it would have failed the signature verification
Try fastboot getvar all and tell me what the output is
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.10.0001
(bootloader) version-baseband: 2.15.00.11.19
(bootloader) version-cpld: None
(bootloader) version-microp: 041f
(bootloader) version-main: 3.26.651.6
(bootloader) serialno: HT08THL01989
(bootloader) imei: 355195000000017
(bootloader) product: supersonic
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PC3610000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3655mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-3b95cc40
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
can you still get into cm10? You can try installing twrp from goo manager. Install that and I'm menu install open recovery script. Otherwise relock the bootloader and run ruu, I can't think of any reason that fastboot can't flash recovery unless its locked but output states phone is soff
om4 said:
can you still get into cm10? You can try installing twrp from goo manager. Install that and I'm menu install open recovery script. Otherwise relock the bootloader and run ruu, I can't think of any reason that fastboot can't flash recovery unless its locked but output states phone is soff
Click to expand...
Click to collapse
No, every time I try to reboot into cm10 it will hang on the boot logo except one time when it booted into recovery. Could you link me a good guide to relock the bootloader and run ruu?
Is there any where else I can post this to get some additional input?
Since you're soff you can try the update zip twrp offers, it goes on root of sd card and bootloader will install. Don't forget to rename it to PJ75IMG.zip. Otherwise, download ruu and in fastboot relock bootloader "fastboot oem lock" and then run ruu
om4 said:
Since you're soff you can try the update zip twrp offers, it goes on root of sd card and bootloader will install. Don't forget to rename it to PJ75IMG.zip. Otherwise, download ruu and in fastboot relock bootloader "fastboot oem lock" and then run ruu
Click to expand...
Click to collapse
Well I can't get the phone to do anything now...its just showing a black screen (no backlight or anything). I was going to try to do the zip.
Have I messed up? Now I am getting worried
You can't get into bootloader at all? Have you tried holding power to reboot phone?
Hi guys,
This is my first post on XDA. Recently, I rooted my HTC one ATT to 4.3 google edition, and everything was fine. However today morning (November 27, 2013) i got a message that said I was able to upgrade to Android 4.4, so I pressed download and install. However, when i went into CWM, it glitched up, and my OS booting screen became green, and wouldn't boot I then decided to download the newest version of Cyanogenmod, since i had it on my SD card. However, CWM then said it was unable to mount the sd card, and then I had no idea what to do. As of right now, whenever i boot into cyanogen mod, it goes into the booting image, and then the phone turns off temporarily, and goes back to the cyanogenmod booting image. And when i try going into recovery, my phone just says "Entering Recovery" and doesn't respond. I've already tried flashing TWRP over CWM via fastboot, but that hasn't worked. I have been phoneless the whole day, and don't know what to do. Please help.
tl;dr installed 4.4, f'd up phone, recovery and OS not working
I believe that you need to flash the stock recovery for the GPE Rom.
Sent from my HTC One using Tapatalk
prith98 said:
Hi guys,
This is my first post on XDA. Recently, I rooted my HTC one ATT to 4.3 google edition, and everything was fine. However today morning (November 27, 2013) i got a message that said I was able to upgrade to Android 4.4, so I pressed download and install. However, when i went into CWM, it glitched up, and my OS booting screen became green, and wouldn't boot I then decided to download the newest version of Cyanogenmod, since i had it on my SD card. However, CWM then said it was unable to mount the sd card, and then I had no idea what to do. As of right now, whenever i boot into cyanogen mod, it goes into the booting image, and then the phone turns off temporarily, and goes back to the cyanogenmod booting image. And when i try going into recovery, my phone just says "Entering Recovery" and doesn't respond. I've already tried flashing TWRP over CWM via fastboot, but that hasn't worked. I have been phoneless the whole day, and don't know what to do. Please help.
tl;dr installed 4.4, f'd up phone, recovery and OS not working
Click to expand...
Click to collapse
NEVER TAKE OTA UPDATE ON CUSTOM RECOVERY !!!
Boot to bootloader / fastboot usb
then run the command
fastboot erase cache
now flash your recovery
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
and again fastboot erase cache
next fastboot reboot-bootloader
now try this ->> http://forum.xda-developers.com/showthread.php?t=2358781
clsA said:
NEVER TAKE OTA UPDATE ON CUSTOM RECOVERY !!!
Boot to bootloader / fastboot usb
then run the command
fastboot erase cache
now flash your recovery
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
and again fastboot erase cache
next fastboot reboot-bootloader
now try this ->> http://forum.xda-developers.com/showthread.php?t=2358781
Click to expand...
Click to collapse
When I run "sudo ./fastboot flash recovery ~/Downloads/openrecovery-twrp-2.6.3.3-m7.img" I get
Code:
sending 'recovery' (9184 KB)...
OKAY [ 1.198s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.158s
Should I carry on going through the steps?
janne_oksanen said:
When I run "sudo ./fastboot flash recovery ~/Downloads/openrecovery-twrp-2.6.3.3-m7.img" I get
Code:
sending 'recovery' (9184 KB)...
OKAY [ 1.198s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.158s
Should I carry on going through the steps?
Click to expand...
Click to collapse
no you need to download the file again and do a md5 check that the file is not corrupt
and flash again. I would also move the file to the same directory as fastboot
clsA said:
no you need to download the file again and do a md5 check that the file is not corrupt
and flash again. I would also move the file to the same directory as fastboot
Click to expand...
Click to collapse
I checked the checksum, it matches. Moved the file to the same dir as fastboot, still getting the same error. Also the link to the rest of the instruction is no good, because I don't have s-off and I have HBOOT-1.54.000.
janne_oksanen said:
I checked the checksum, it matches. Moved the file to the same dir as fastboot, still getting the same error. Also the link to the rest of the instruction is no good, because I don't have s-off and I have HBOOT-1.54.000.
Click to expand...
Click to collapse
rumrunner works with hboot 1.54
give me the results from fastboot getvar all
and we can try and find you a RUU to flash
clsA said:
rumrunner works with hboot 1.54
give me the results from fastboot getvar all
and we can try and find you a RUU to flash
Click to expand...
Click to collapse
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [sorry, not giving out this ;]
(bootloader) imei: [sorry, not giving out this ;]
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
@janne_oksanen
delete sorry you have no recovery
Edit: If you do manage to get twrp flashed try this Guru Reset
http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
I'm sorry but everything i find requires you have s-off or at least custom recovery installed
maybe someone else can help you
I'm in the same unfortunate boat as OP. I haven't been able to boot or enter recovery or download mood, just a blue screen. Am I just borked?
c:\SDK\platform-tools>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.72.0000
(bootloader) version-baseband: 3.1204.171.33
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.18.401.2
(bootloader) serialno: FA2BRW105444
(bootloader) imei: 353567051447689
(bootloader) product: enrc2b_u
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM3511000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(bootloader) devpower: 91
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.520s
c:\SDK\platform-tools>fastboot oem rebootRUU
...
(bootloader) Save data from original MSC...
(bootloader) Save data from SIF...
(bootloader) Update partition data to SIF partition
(bootloader) Update partition data from original MSC...
(bootloader) [MSG] OKAY
OKAY [ 0.190s]
finished. total time: 0.190s
c:\SDK\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (734167 KB)...
OKAY [ 92.812s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 125.302s
---------------------------------------------------
my Device is HTC ONE X+
*** RELOCKED ***
*** Security Warning ***
ENRC2B_U PVT SHIP S--ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-3.1204.171.33
emmc-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
MODEM PATH : OFF
You don't need to update your devices firmware, latest HBOOT (1.72) is already installed. The steps you need to do now:
1. unlock your bootloader
2. install a custom recovery
3. reboot to system and copy rom.zip onto your phone
4. reboot into bootloader (fastboot mode) and flash boot.img
5. enter recovery and flash rom.
at least you need to wipe /data partition before/while flashing rom. i recommend wiping /system, /cache and /data (without /data/media).
Also don't forget to make a backup in recovery anywhere between step 2. and 4. !!!
i can't copy rom.zip in my phone
No operating system on phone now
And I can not get to the internal memory of the device
in fastboot msg failed to open usp master mode
i gave HTCDriver_4.2.0.001 put HTC MTP Device Driver not Install
in recovery mode not see mount sdcard
ezat121 said:
No operating system on phone now
And I can not get to the internal memory of the device
in fastboot msg failed to open usp master mode
i gave HTCDriver_4.2.0.001 put HTC MTP Device Driver not Install
in recovery mode not see mount sdcard
Click to expand...
Click to collapse
I don't know about HTC driver version, safest way would be downloading and isntalling HTC Sync to get the right drivers (you can uninstall sync later and keep the drivers.
MTP devices are not able to mount /sdcard in recovery, so you need to use adb sideload command. In case you don't have ADB/Fastboot on your computer, take a look here.
Copy the rom zip file into your ADB/fastbootfolder on your computer (maybe rename it to something shorter), connect your phone to your computer and start sideload mode in recovery. Type "adb devices" in command line to see if your phone is recognized, if it is not, you may need to wait a bit longer or there's an issue with drivers. As soon as your device is recognized as in sideload mode, you can type "adb sideload <name_of_the_rom>.zip" and it should start copying. Installation process should start automatically after copying, or if it does not, you should find a file called "sideload.zip" on your phones internal memory that you can flash manually.
Thank you
After loading the rum on the device
stops at HTC ONE logo
Why did not complete
Sorry for the inconvenience..
But I'm new in this area
Thank You
AW: [Q] any help plzz flash Android Revolution HD
ezat121 said:
After loading the rum on the device
stops at HTC ONE logo
Why did not complete
Sorry for the inconvenience..
But I'm new in this area
Thank You
Click to expand...
Click to collapse
When you say HTC One logo, I assume you flashed the boot.img.
Did you wipe /system, /data (without /data/media) and /cache in before installing rom?
You solved your issue?
Sent from my HTC One X+ using Tapatalk 2
i flashing boot img
reaper90 said:
When you say HTC One logo, I assume you flashed the boot.img.
Did you wipe /system, /data (without /data/media) and /cache in before installing rom?
Click to expand...
Click to collapse
i flashing boot from link of android revolution is that Flash_boot_8.x_0.1
and im wipe from recovery (dalvik cache-system-cache-data-internal storage ) befor install
no start stop in htc one logo dynamic
put no sound in logo
in installing rom zip Option zip file signature verification not
When i chose failed install and see msg no md5 file fond
ezat121 said:
i flashing boot from link of android revolution is that Flash_boot_8.x_0.1
and im wipe from recovery (dalvik cache-system-cache-data-internal storage ) befor install
no start stop in htc one logo dynamic
put no sound in logo
in installing rom zip Option zip file signature verification not
When i chose failed install and see msg no md5 file fond
Click to expand...
Click to collapse
make sure the download is not corrupted. also first boot may take 5-10 minutes, so give it some time.
zeroth said:
You solved your issue?
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Not yet, but I'm trying
reaper90 said:
make sure the download is not corrupted. also first boot may take 5-10 minutes, so give it some time.
Click to expand...
Click to collapse
We have prepared the steps are as follows:
1- wipeing /system /cache/data before flashing rom.
2- install a boot.img (Flash boot 8.x 0.1)
3- reboot into bootloader
4- enter recovery and flash rom
flashing Completed and reboot system
Device freezes at logo htc Third (htc one tm ) Supposed to give a voice put no sound
I waited for more than 20 minutes and do not change
What is the problem and where error ؟
I tried more than once and repeated problem
Thank you very much for your response
ezat121 said:
We have prepared the steps are as follows:
1- wipeing /system /cache/data before flashing rom.
2- install a boot.img (Flash boot 8.x 0.1)
3- reboot into bootloader
4- enter recovery and flash rom
flashing Completed and reboot system
Device freezes at logo htc Third (htc one tm ) Supposed to give a voice put no sound
I waited for more than 20 minutes and do not change
What is the problem and where error ؟
I tried more than once and repeated problem
Thank you very much for your response
Click to expand...
Click to collapse
Steps are correct so far, so it should work... Maybe your download of the rom wasn't complete, try redownloading. Also what recovery do you use?
reaper90 said:
Steps are correct so far, so it should work... Maybe your download of the rom wasn't complete, try redownloading. Also what recovery do you use?
Click to expand...
Click to collapse
i try redownloading newly
i restore the previous steps
Do not change the same problem
i use TWRP v 2.6.3.0
i try Back rom stock from this site
http://forum.xda-developers.com/showthread.php?t=2414238
But I did not know how
ezat121 said:
i try redownloading newly
i restore the previous steps
Do not change the same problem
i use TWRP v 2.6.3.0
i try Back rom stock from this site
http://forum.xda-developers.com/showthread.php?t=2414238
But I did not know how
Click to expand...
Click to collapse
The steps i usually do:
0. If possible (OS is still installed), copy rom onto your phones internal storage
1. reboot into bootloader (fastboot) and flash boot.img
2. reboot into recovery
3. wipe everything except internal storage
4. install rom (sideload if necessary)
5. reboot and wait some minutes for first boot to finish.
Since you have international version of the One X+ (enrc2b) and you use TWRP like i do, this should work. The only reason why it could not work, is that you either did not flash the boot.img (you would only see bootloop on first htc screen) or the rom.zip was corrupted, but then again, there would probably be a failure in aroma installer of ARHD.
Hello,
My HTC One m7 was bootloader unlocked and I used TWRP 2.8.4.0 recovery. I also installed CyanogenMod 10.2.1. Last night while playing music, the phone restarted on its own and got stuck on a boot loop (just boots to a white HTC screen and restarts to the same after 10-15 sec). Now the Phone is not recognized in adb (is blank under devices connected, another phone shows up fine) but I can send across commands (reboot to bootloader, relock bootloader...etc). I tried flashing the recovery again, but it says it went across fine, but gets to the boot loop again. I tried flashing the HTC factory ruu, it goes for about 22%, says it is complete but get to the bootloop again. Please help :crying:
Hboot - 1.55
Simpleusername said:
Hello,
My HTC One m7 was bootloader unlocked and I used TWRP 2.8.4.0 recovery. I also installed CyanogenMod 10.2.1. Last night while playing music, the phone restarted on its own and got stuck on a boot loop (just boots to a white HTC screen and restarts to the same after 10-15 sec). Now the Phone is not recognized in adb (is blank under devices connected, another phone shows up fine) but I can send across commands (reboot to bootloader, relock bootloader...etc). I tried flashing the recovery again, but it says it went across fine, but gets to the boot loop again. I tried flashing the HTC factory ruu, it goes for about 22%, says it is complete but get to the bootloop again. Please help :crying:
Hboot - 1.55
Click to expand...
Click to collapse
are you still stuck ?
Boot Loop
clsA said:
are you still stuck ?
Click to expand...
Click to collapse
Yup...still stuck. Had been travelling, so didn't try much in the last two days. Adb does not recognize the decive, but fastboot commands work. CANNOT push recovery as it says it is a success, but Can't boot to recovery.
Simpleusername said:
Yup...still stuck. Had been travelling, so didn't try much in the last two days. Adb does not recognize the decive, but fastboot commands work. CANNOT push recovery as it says it is a success, but Can't boot to recovery.
Click to expand...
Click to collapse
Did you relock the bootloader to flash the RUU ? and did you unlock it to flash TWRP again ?
Boot Loop
clsA said:
Did you relock the bootloader to flash the RUU ? and did you unlock it to flash TWRP again ?
Click to expand...
Click to collapse
Yes. I did.
Simpleusername said:
Yes. I did.
Click to expand...
Click to collapse
The next step i would take is format data in TWRP, but be aware this will totally wipe the phone, sdcard and all
you would then need to flash a rom back to the phone
After that your option is to relock and reflash the same firmware your on now
Boot Loop
clsA said:
The next step i would take is format data in TWRP, but be aware this will totally wipe the phone, sdcard and all
you would then need to flash a rom back to the phone
After that your option is to relock and reflash the same firmware your on now
Click to expand...
Click to collapse
As long as I can get the Phone working, I don't care about the data. But I can't get to recovery. can you post the steps.
Simpleusername said:
As long as I can get the Phone working, I don't care about the data. But I can't get to recovery. can you post the steps.
Click to expand...
Click to collapse
Try this
If you just simply want it working, just follow this, note that unlocking the bootloader will erase the entire contents of your phone.
you can unlock your bootloader with your phone in bootloader mode, follow the instructions here, http://www.htcdev.com/bootloader
your bootloader now says TAMPERED and UNLOCKED at the top, your warranty is now void.
the instructions will provide you with some files, adb and fastboot, keep hold of those, you will need them.
once your bootloader is unlocked, flash 2.6.3.3 recovery from here, (2.6.3.3 is the most compatible to date, all the others give some sort of problem) http://techerrata.com/browse/twrp2/m7
download the recovery file, place it in the same folder as fastboot and adb on your computer, and with your phone in bootloader/fastbootUSB mode type
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
download this: http://www.androidfilehost.com/?fid=23501681358545274
again put it in the same folder as adb and fastboot, for ease rename the file to rom.zip
enter recovery (main screen only, no sub menu's) and type:
adb push rom.zip /sdcard/
it will appear unresponsive, takes about 5 mins to push, once done, the cmd window will let you know.
unplug your phone and then in recovery select install, and select rom.zip from the list, swipe to begin the install, follow the on screen instructions.
Click to expand...
Click to collapse
Boot Loop
clsA said:
Try this
Click to expand...
Click to collapse
I don't have the phone with me, I'll try it tomorrow. Thanks.
Boot Loop
clsA said:
Try this
Click to expand...
Click to collapse
I tried the steps, but still no-go. The recovery goes through fine (acc. to cmd prompt)...I erase cache, reboot to bootloader and try to go to recovery, It says booting to recovery and then resumes the bootloop. I tried different recoveries, does not work. Could one reason be that USB debugging might have been disabled...? I don't know if that matters at this point, since I can't boot to anywhere and the memory is wiped clean, but I'm out of ideas and clutching at straws.
BTW...I found this thread that could explain something about this. If true...well so much for a graduation present.
http://forums.androidcentral.com/ht...ootloader-can-t-get-into-recovery-help-3.html
Simpleusername said:
I tried the steps, but still no-go. The recovery goes through fine (acc. to cmd prompt)...I erase cache, reboot to bootloader and try to go to recovery, It says booting to recovery and then resumes the bootloop. I tried different recoveries, does not work. at this point, I'm out of ideas.
Click to expand...
Click to collapse
Flash a ROM
Sent from my SM-A500FU using XDA Free mobile app
Boot Loop
mygalaxya said:
Flash a ROM
Sent from my SM-A500FU using XDA Free mobile app
Click to expand...
Click to collapse
Cannot flash a ROM as adb does not recognise device.
Simpleusername said:
I tried the steps, but still no-go. The recovery goes through fine (acc. to cmd prompt)...I erase cache, reboot to bootloader and try to go to recovery, It says booting to recovery and then resumes the bootloop. I tried different recoveries, does not work. Could one reason be that USB debugging might have been disabled...? I don't know if that matters at this point, since I can't boot to anywhere and the memory is wiped clean, but I'm out of ideas and clutching at straws.
BTW...I found this thread that could explain something about this. If true...well so much for a graduation present.
http://forums.androidcentral.com/ht...ootloader-can-t-get-into-recovery-help-3.html
Click to expand...
Click to collapse
usb debugging is only for when the phone is booted up to android os
post your fastboot getvar all and we can try stock recovery or firmware flash
Also please list all the files you have tried / RUU / Recovery / anything else
Boot Loop
clsA said:
usb debugging is only for when the phone is booted up to android os
post your fastboot getvar all and we can try stock recovery or firmware flash
Also please list all the files you have tried / RUU / Recovery / anything else
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4091mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
File Versions tried -
TWRP - 2.8.4.0
TWRP - 2.6.3.3
ROMS - CM 10.2.1
Factory RUU - RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
Simpleusername said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4091mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
File Versions tried -
TWRP - 2.8.4.0
TWRP - 2.6.3.3
ROMS - CM 10.2.1
Factory RUU - RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2
Click to expand...
Click to collapse
Everything looks ok
lock the bootloader - fastboot oem lock
Flash this firmware > https://www.dropbox.com/s/o1o487pmdfi9dyo/firmware_3.17.502.3.zip?dl=0
fastboot oem rebootRUU
fastboot flash zip firmware_3.17.502.3.zip
fastboot flash zip firmware_3.17.502.3.zip
fastboot reboot-bootloader
it will replace your recovery with the stock recovery
from bootloader choose recovery, wait a few seconds and hold volume up and tap power
this will bring up the menu in stock recovery
choose Factory Reset, when it finishes try and boot up your phone. if it won't boot try the RUU again
Be sure you RUU is not corrupt check it's md5 it should be >
Filename: RUU_M7_UL_JB43_SENSE50_MR_Cingular_US_3.17.502.3_Radio_4A.19.3263.13_10.38j.1157.04_release_334235_signed_2.exe
MD5: 20f152644d2187b158ca9cdc887db40a
Click to expand...
Click to collapse
Boot Loop
clsA said:
Everything looks ok
lock the bootloader - fastboot oem lock
Flash this firmware > https://www.dropbox.com/s/o1o487pmdfi9dyo/firmware_3.17.502.3.zip?dl=0
fastboot oem rebootRUU
fastboot flash zip firmware_3.17.502.3.zip
fastboot flash zip firmware_3.17.502.3.zip
fastboot reboot-bootloader
it will replace your recovery with the stock recovery
from bootloader choose recovery, wait a few seconds and hold volume up and tap power
this will bring up the menu in stock recovery
choose Factory Reset, when it finishes try and boot up your phone. if it won't boot try the RUU again
Be sure you RUU is not corrupt check it's md5 it should be >
Click to expand...
Click to collapse
I did that and I get
C:\HTC\adb_fastboot_drivers>fastboot flash zip firmware_3.17.502.3.zip
sending 'zip' (40022 KB)...
OKAY [ 3.535s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 9.296s.
Now, when I try to boot to recovery, it reboots to fastboot. Even factory reset in bootloader does the same and reboots to fastboot.
I then tried the factory RUU. MD5 checked, Antivirus, Firewall disabled. Run it as admin. samething. Update window on PC goes upto 22% and stays there, bar on phone goes through to completion and then I get a "Your ROM update has been completed. Your phone is ready to use" and back to the bootloop AGAIN...
Simpleusername said:
I did that and I get
C:\HTC\adb_fastboot_drivers>fastboot flash zip firmware_3.17.502.3.zip
sending 'zip' (40022 KB)...
OKAY [ 3.535s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 9.296s.
Now, when I try to boot to recovery, it reboots to fastboot. Even factory reset in bootloader does the same and reboots to fastboot.
I then tried the factory RUU. MD5 checked, Antivirus, Firewall disabled. Run it as admin. samething. Update window on PC goes upto 22% and stays there, bar on phone goes through to completion and then I get a "Your ROM update has been completed. Your phone is ready to use" and back to the bootloop AGAIN...
Click to expand...
Click to collapse
you can extract the rom.zip from your windows temp folder when the RUU is running
copy it to your fastboot folder and try and flash it manually
fastboot oem rebootRUU
fastboot flash zip Rom.zip
fastboot flash zip Rom.zip
fastboot reboot-bootloader
Boot Loop
clsA said:
you can extract the rom.zip from your windows temp folder when the RUU is running
copy it to your fastboot folder and try and flash it manually
fastboot oem rebootRUU
fastboot flash zip Rom.zip
fastboot flash zip Rom.zip
fastboot reboot-bootloader
Click to expand...
Click to collapse
I used this method to get it...
http://forum.xda-developers.com/showthread.php?t=2534428
Didn't work. Just as before, the flash is successful, but reboots to the bootloop. Also, while going through the cmd process logs, I found a failure
start image[sbl1-1] unzipping & flushing...
[RUU]UZ,sbl1-1,0
[RUU]UZ,sbl1-1,100
signature checking...
verified fail
I don't know what that means, but maybe someone can make sense of it.
Simpleusername said:
I used this method to get it...
http://forum.xda-developers.com/showthread.php?t=2534428
Didn't work. Just as before, the flash is successful, but reboots to the bootloop. Also, while going through the cmd process logs, I found a failure
start image[sbl1-1] unzipping & flushing...
[RUU]UZ,sbl1-1,0
[RUU]UZ,sbl1-1,100
signature checking...
verified fail
I don't know what that means, but maybe someone can make sense of it.
Click to expand...
Click to collapse
that fail is meaningless the RUU contains files for more than one phone and the files that are not for your phone just say fail
If you look the same files will say success further down (or up)
If your phone is still in a bootloop after RUU and factory reset from stock recovery I have no more ideas
Boot Loop
clsA said:
that fail is meaningless the RUU contains files for more than one phone and the files that are not for your phone just say fail
If you look the same files will say success further down (or up)
If your phone is still in a bootloop after RUU and factory reset from stock recovery I have no more ideas
Click to expand...
Click to collapse
Yeah, I guessed that's pretty much it. I'll prob sell it for parts on ebay. Thanks for your help nonetheless.
Hey everyone,
I lately tried to root my HTC One M8, but due to some mistakes I got stuck and just have access to the bootloader,but I'm not able to get in my phone. I've have unlocked the bootloader and have S-On. I would be pleased, if someone could tell me how I reset my phone to factory state. I'm pretty new to such things, so let me know if you need further informations. I really hope that you guys can help me, all of this made so frustrated.
Thanks in advance
Matthew F.
You have access to Bootloader. Can you Boot into recovery? There you will find a selection for factory reset.
http://www.androidcentral.com/sites...arge/public/postimages/108579/m7-recovery.jpg
I can't confirm that's the best course to take, but its there if recovery is.......
If that does not work, then you will need to relock the bootloader and run the RUU for your variant of the M8, and it must be the same version or newer. You can not downgrade while S-On.
Cremnomaniac said:
You have access to Bootloader. Can you Boot into recovery? There you will find a selection for factory reset.
I can't confirm that's the best course to take, but its there if recovery is.......
Click to expand...
Click to collapse
I can't get in recovery, it just goes back to the bootloader
es0tericcha0s said:
If that does not work, then you will need to relock the bootloader and run the RUU for your variant of the M8, and it must be the same version or newer. You can not downgrade while S-On.
Click to expand...
Click to collapse
I tried to install the ruu, but everytime I get this message 'Error 120: low main battery' and the install Setup stops
It has to be above 30% before it will run, if I remember right.
es0tericcha0s said:
It has to be above 30% before it will run, if I remember right.
Click to expand...
Click to collapse
Yeah that's right, but my battery is about 70%
It might not be due to the software being messed up and the bright white screen of the bootloader. You can try extracting the rom.zip from the RUU exe and flashing via fastboot manually. http://forum.xda-developers.com/showthread.php?t=2497614 - this is for the M7 but the same basic principles apply. I don't believe that it requires the 30% this method, but it's been a bit since I have flashed manually.
es0tericcha0s said:
It might not be due to the software being messed up and the bright white screen of the bootloader. You can try extracting the rom.zip from the RUU exe and flashing via fastboot manually. http://forum.xda-developers.com/showthread.php?t=2497614 - this is for the M7 but the same basic principles apply. I don't believe that it requires the 30% this method, but it's been a bit since I have flashed manually.
Click to expand...
Click to collapse
so, I've followed this guide, but now I'm stuck again. Everytime I type in this command 'fastboot flash zip C:/mini-sdk/rom.zip' I get a error-message 'target reported max download size of 1826418688 Bytes error: cannot load 'C:/mini-sdk/Rom.zip'.
Any ideas for that?
Is the rom zip IN the folder titled C:/mini-sdk?
Yes, it is.
es0tericcha0s said:
Is the rom zip IN the folder titled C:/mini-sdk?
Click to expand...
Click to collapse
Yes, it is.
If your command prompt is already pointed to the adb/fastboot folder then you should be able to just use the command:
fastboot flash zip rom.zip
instead of fastboot flash zip C:/blahblahblah
es0tericcha0s said:
If your command prompt is already pointed to the adb/fastboot folder then you should be able to just use the command:
fastboot flash zip rom.zip
instead of fastboot flash zip C:/blahblahblah
Click to expand...
Click to collapse
The command prompt is already pointed in the adb/fastboot Folder, but i still get the same error ('target reported max download size of...'). Do my phone has to be unlocked or locked, S-on or S-off at that Moment?
Locked if S-On. S-Off, either way.
es0tericcha0s said:
Locked if S-On. S-Off, either way.
Click to expand...
Click to collapse
hmm... it already was relocked and s-on. What do I have to do?
and the Software Status says 'Modified', if that's necessary
Matthew F. said:
so, I've followed this guide, but now I'm stuck again. Every time I type in this command 'fastboot flash zip C:/mini-sdk/rom.zip' I get a error-message 'target reported max download size of 1826418688 Bytes error: cannot load 'C:/mini-sdk/Rom.zip'.
Any ideas for that?
Click to expand...
Click to collapse
I'm not sure this is the problem, but it sounds familiar. It may be the version of adb/fastboot you're using. Try using this one posted by Dottat.
Its the Fastboot link at the bottom of the OP
http://forum.xda-developers.com/ver...pment/stock-m-firmware-nand-recovery-t3330972
Read about the options for installing RUUs. There's a few.
PS - Its customary when asking for help to provide some basic info about your phone. I don't see that you have even mentioned which ROM your currently running. There are RUUs for s-on and s-off.
Cremnomaniac said:
I'm not sure this is the problem, but it sounds familiar. It may be the version of adb/fastboot you're using. Try using this one posted by Dottat.
Its the Fastboot link at the bottom of the OP
http://forum.xda-developers.com/ver...pment/stock-m-firmware-nand-recovery-t3330972
Read about the options for installing RUUs. There's a few.
PS - Its customary when asking for help to provide some basic info about your phone. I don't see that you have even mentioned which ROM your currently running. There are RUUs for s-on and s-off.
Click to expand...
Click to collapse
Sorry sir, I'm using this ROM https://www.androidfilehost.com/?fid=95916177934546378 (should be the right one) and here are some Infos about my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH485WM02248
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Execution time is 21(ms)
I also downloaded Dottat's fastboot/adb Version and typed in following commands:
-fastboot oem rebootRUU (no Problem with this command)
-fastboot Flash zip 0P6B10000.zip (renamed it after my mid)
But then I get this error-message:
C:\Users\Frank\Desktop\HTC_fastboot_adb>fastboot flash zip 0P6B10000.zip
sending 'zip'... (46606 KB) OKAY
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
FAIL32 header error
FAILED (remote: 32 header error)
Execution time is 8(s)
Any ideas for this Problem?
PS - I wouldn't have come this far without your help, so thank you
Matthew F. said:
Sorry sir, I'm using this ROM https://www.androidfilehost.com/?fid=95916177934546378 (should be the right one)
I also downloaded Dottat's fastboot/adb Version and typed in following commands:
-fastboot oem rebootRUU (no Problem with this command)
-fastboot Flash zip 0P6B10000.zip (renamed it after my mid)
But then I get this error-message:
C:\Users\Frank\Desktop\HTC_fastboot_adb>fastboot flash zip 0P6B10000.zip
sending 'zip'... (46606 KB) OKAY
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
FAIL32 header error
FAILED (remote: 32 header error)
Execution time is 8(s)
Any ideas for this Problem?
PS - I wouldn't have come this far without your help, so thank you
Click to expand...
Click to collapse
May I suggest that you do some more research BEFORE you use that file.
The file you link to is an RUU! Executable. I know, I just downloaded it and opened it to be sure.
If your renaming it, and trying to use fastboot, you are using the wrong file. The file your trying to flash is NOT flash-able via fastboot. Again, its an RUU.exe file. If you don't know what that is, you shouldn't be using it.
Do some research on RUU's......