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?
Related
Figured I'd ask the XDA community before I give up. I was working on an HTC Rezound that a kid had water damage on. Finally got it running but with the weirdest issues I've seen. I've tried alot, can't remember everything off the top of my head but I wanted to double check with you guys before I give up tomorrow.
First off Its HTCDev unlocked, S-ON with HBOOT 2.28. There is no ROM or OS on it, nor will it boot to any Recovery I successfully flash over. I can send and receive commands on fastboot, and sometimes can send them when I select REBOOT RECOVERY. That leads me to a black screen but adb devices shows it under recovery.
Tried flashing TWRP, using the All In One tool, flashing a Custom ROM, the RUU zip and exe, and Amon-Ra recovery. All leads to the same thing basically, loads into HBOOT fine but never boots into any recovery. I get signature verify failed sometimes when flashing but honestly it sends and successfully writes a recovery.img but wont load into it. Is it brain dead somewhere or what?
Thanks guys! I'll post the getvar
C:\Users\AZ's Gaming>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.28.0000
(bootloader) version-baseband: 2.23.10.0123r/2.23.10.0124r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) serialno: HT19VS219499
(bootloader) imei: 990000336135878
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3746mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: cecc19f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
DO THIS ADVICE ONLY IF NOBODY ELSE HAS BETTER IDEA..
Flash the latest ruu thru bootloader boot into recovery image while on stock to see if it works if it does then unlock hboot then flash recovery if it doesn't well we will have to dig a lil deeper
Sent from my Infected Rezound using xda app-developers app
Put the recovery.img file from the latest TWRP into your adb directory, then issue:
fastboot boot recovery.img (Note the BOOT command, not flash!)
and see if that gets you to TWRP, if not, you are probably in trouble... if it does, wipe everything except boot and flash in a known stable ROM image like Global OTA Stock/Rooted, Infection, Beanstalk, or something like that.
Your fastboot getvar looks fine, except battery voltage is really low (should be around 3.9-4.2) and the version-main is messed up, meaning it doesn't see a ROM installed.
acejavelin said:
Put the recovery.img file from the latest TWRP into your adb directory, then issue:
fastboot boot recovery.img (Note the BOOT command, not flash!)
and see if that gets you to TWRP, if not, you are probably in trouble... if it does, wipe everything except boot and flash in a known stable ROM image like Global OTA Stock/Rooted, Infection, Beanstalk, or something like that.
Your fastboot getvar looks fine, except battery voltage is really low (should be around 3.9-4.2) and the version-main is messed up, meaning it doesn't see a ROM installed.
Click to expand...
Click to collapse
I tried this first because it was the only thing I haven't done, and I got nothing. It boots into a recovery I think because it shows up under adb devices but still get a black screen. I think the phone is toast.
NINJA EDIT: The menu and home buttons vibrate when I hit them, so it must be booted into recovery, just for some reason nothing is displayed.
Hi everyone,
I have my AT&T HTC One that's stuck in a bootloop due to me flashing a ROM (ARHD). I did not notice I still had S-On (S-Off is needed to flash the ROM) and now stuck in a loop. I can access recovery (TWRP 2.6.3.3) but sideload just stays at the message that's says its starting.
Bootloader is also accessible, I have all my adb files and fastboot files. I just want to get back to stock 4.3 or 4.4.2, or even a custom rom if it'll work.
Here are my vars:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.502.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.069s
Any help is appreciated.
EDIT: Managed to get sideload working, just opened cmd and had the TWRP running sideload, but it was stuck at the words starting so I checked for devices and found it. sideloaded stock AT&t rooted ROM by dark 2099 (http://forum.xda-developers.com/showthread.php?t=2676986) and still bootlooping after wiping caches and factory reset.
EDIT2: Sideloaded the ROM again now not bootlooping but stuck at HTC logo, still can use recovery and bootloader.
52me52 said:
Hi everyone,
I have my AT&T HTC One that's stuck in a bootloop due to me flashing a ROM (ARHD). I did not notice I still had S-On (S-Off is needed to flash the ROM) and now stuck in a loop. I can access recovery (TWRP 2.6.3.3) but sideload just stays at the message that's says its starting.
Bootloader is also accessible, I have all my adb files and fastboot files. I just want to get back to stock 4.3 or 4.4.2, or even a custom rom if it'll work.
Here are my vars:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.502.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3*********
(bootloader) imei: 354***********
(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: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.069s
Any help is appreciated.
EDIT: Managed to get sideload working, just opened cmd and had the TWRP running sideload, but it was stuck at the words starting so I checked for devices and found it. sideloaded stock AT&t rooted ROM by dark 2099 (http://forum.xda-developers.com/showthread.php?t=2676986) and still bootlooping after wiping caches and factory reset.
EDIT2: Sideloaded the ROM again now not bootlooping but stuck at HTC logo, still can use recovery and bootloader.
Click to expand...
Click to collapse
Edit your post to remove the serial no and IMEI
Try fastboot erase cache from fastboot USB (bootloader)
And how did you get to version-main: 4.20.502.1 ?
clsA said:
Edit your post to remove the serial no and IMEI
Try fastboot erase cache from fastboot USB (bootloader)
And how did you get to version-main: 4.20.502.1 ?
Click to expand...
Click to collapse
Hoping to hear from you, saw you in other Q&A posts!
I tried that fastboot erase cache still same thing. Any help is appreciated, hopefully I can get this done today it's my dad's.
EDIT: thinking about using an RUU but method would I take? .exe or .zip? I tried using an RUU and it failed and gave me that somehow. .exe RUU btw.
EDIT: the RUU is called elevate-RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2
52me52 said:
Hoping to hear from you, saw you in other Q&A posts!
I tried that fastboot erase cache still same thing. Any help is appreciated, hopefully I can get this done today it's my dad's.
Click to expand...
Click to collapse
Flash twrp again and erase cache after
what rom are you sideloading ? nvm I see
you cant RUU your software is too new and you need s-off
where did you find this
EDIT: the RUU is called elevate-RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R1 0_Radio_4T.24.3218.09_10.26.1718.01L_release_35656 5_signed_2
Click to expand...
Click to collapse
clsA said:
Flash twrp again and erase cache after
what rom are you sideloading ? nvm I see
you cant RUU your software is too new and you need s-off
Click to expand...
Click to collapse
Same situation still at HTC logo, ok I just saw that now too about the RUU.
Link:http://www.androidruu.com/index.php?developer=M7 first one.
52me52 said:
Same situation still at HTC logo, ok I just saw that now too about the RUU.
Click to expand...
Click to collapse
slow down and answer these questions
how did you get to version-main: 4.20.502.1 ?
and where is the RUU you listed.
also are you doing MD5 check of all the files your flashing ?
clsA said:
slow down and answer these questions
how did you get to version-main: 4.20.502.1 ?
and where is the RUU you listed.
also are you doing MD5 check of all the files your flashing ?
Click to expand...
Click to collapse
1) from the RUU I used.
2)just posted/edited
3)No I don't really do that
52me52 said:
1) from the RUU I used. ??? link
2)just posted/edited ??? link
3)No I don't really do that - how do you know your files are not corrupt ?
Click to expand...
Click to collapse
If everything is a big secret I can't help you
clsA said:
If everything is a big secret I can't help you
Click to expand...
Click to collapse
It's my link from the post above your last one: http://www.androidruu.com/index.php?developer=M7
I never check the MD5 because I never had a problem until now.
What would you recommend at this point?
52me52 said:
It's my link from the post above your last one: http://www.androidruu.com/index.php?developer=M7
I never check the MD5 because I never had a problem until now.
Click to expand...
Click to collapse
Who posted this RUU .. how did you find it ?
and why is it not the same main version as in you getvar
I'm downloading it now I'll see whats up
clsA said:
Who posted this RUU .. how did you find it ?
and why is it not the same main version as in you getvar
I'm downloading it now I'll see whats up
Click to expand...
Click to collapse
I came across this link: http://forum.xda-developers.com/showthread.php?t=2265618
I scrolled down to return to stock and pressed the first link for RUUs here: http://forum.xda-developers.com/showthread.php?t=2194707
pressed m7 and got the page of the RUUs.
The main version I don't really know, I ran it and it failed and when I redid the 'fastboot getvar all' I saw it. Thanks for all your help.
52me52 said:
I came across this link: http://forum.xda-developers.com/showthread.php?t=2265618
I scrolled down to return to stock and pressed the first link for RUUs here: http://forum.xda-developers.com/showthread.php?t=2194707
pressed m7 and got the page of the RUUs.
The main version I don't really know, I ran it and it failed and when I redid the 'fastboot getvar all' I saw it. Thanks for all your help.
Click to expand...
Click to collapse
Ok well it appears to be a Real RUU
but the MD5 failed - means it's corrupt
can you md5 check your file and compare it to mine ?
this is the md5 on the download page
fdbaccdda9519a321059b02e2dec49b2
clsA said:
Ok well it appears to be a Real RUU
but the MD5 failed - means it's corrupt
can you md5 check your file and compare it to mine ?
this is the md5 on the download page
fdbaccdda9519a321059b02e2dec49b2
Click to expand...
Click to collapse
Mine also failed same thing. Except my code in orange is different than yours.
52me52 said:
Mine also failed same thing. Except my code in orange is different than yours.
Click to expand...
Click to collapse
ok well lets try and get your phone working
flash this stock recovery
https://www.dropbox.com/s/rns2nj5hn7lwjln/recovery.img
then do a factory reset from the bootloader
I'll post more here while your do that...
Next step is redownload TWRP from here
http://techerrata.com/browse/twrp2/m7
and md5 check it
then flash it
and redownload My Rom here >> http://www.androidfilehost.com/?fid=23329332407576941
again md5 check it and sideload it
clsA said:
ok well lets try and get your phone working
flash this stock recovery
https://www.dropbox.com/s/rns2nj5hn7lwjln/recovery.img
then do a factory reset from the bootloader
I'll post more here while your do that
Click to expand...
Click to collapse
Good bless you and thanks, but should I do a backup of some sort?
52me52 said:
Good bless you and thanks, but should I do a backup of some sort?
Click to expand...
Click to collapse
no theirs nothing to backup
I downloaded the RUU again and got the exact same number as the first time
MD5: 5F121D72B8FA3F6F1704588467752605
clsA said:
no theirs nothing to backup
Click to expand...
Click to collapse
15-17 minutes till download finishes, sorry for keeping you up and thanks for the help.
52me52 said:
15-17 minutes till download finishes, sorry for keeping you up and thanks for the help.
Click to expand...
Click to collapse
did you flash the stock recovery and do the factory reset ?
did the phone try and boot up ?
first boot will sometimes take 5 - 7 min on the HTC logo
clsA said:
did you flash the stock recovery and do the factory reset ?
did the phone try and boot up ?
first boot will sometimes take 5 - 7 min on the HTC logo
Click to expand...
Click to collapse
Did that and stays on the logo, going to flash your rom now.
I got a bad md5, do I pick a mirror to download?
52me52 said:
Did that and stays on the logo, going to flash your rom now.
Click to expand...
Click to collapse
just don't forget everytime you flash a recovery to erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
and in TWRP when you do factory reset
clear delvic and cache also
not sdcard
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.
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......