i've been using RR ROM for a week, but had some issues, so i decided to go back to stock firmware and lock bootloader again.
i've been trying to flash some firmwares found here and on the web for Moto Z but i get everytime some error about downgrade etc.
now i'm on lineageos official nightly, because i didnt find any flashable stock firmware.
i assume that i must use the latest 7.1.1 European firmware. But i can't findt it anywhere.
Search for retbr firmware, flash it, then get the first update from a tool in this forum. After that first manual update you can update normally.
knjigo said:
i've been using RR ROM for a week, but had some issues, so i decided to go back to stock firmware and lock bootloader again.
i've been trying to flash some firmwares found here and on the web for Moto Z but i get everytime some error about downgrade etc.
now i'm on lineageos official nightly, because i didnt find any flashable stock firmware.
i assume that i must use the latest 7.1.1 European firmware. But i can't findt it anywhere.
Click to expand...
Click to collapse
Download latest retus firmware, e.g. from here:
https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
In your phone settings it will show up as reteu and you can do ota updates without restrictions.
i got this with latest us firmware (XT1650-03_GRIFFIN_RETUS_7.1.1_NPL26.118-20_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip)
[[email protected] rom]# fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (142 KB)...
OKAY [ 0.001s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.148s
[[email protected] rom]#
Click to expand...
Click to collapse
Loader009 said:
Search for retbr firmware, flash it, then get the first update from a tool in this forum. After that first manual update you can update normally.
Click to expand...
Click to collapse
What do you mean with "get the first update from a tool in this forum"? (Was meinst du damit )
knjigo said:
What do you mean with "get the first update from a tool in this forum"? (Was meinst du damit )
Click to expand...
Click to collapse
First you flash a stock ROM (skip gpt and bootloader updates).
Then use this tool to get the first update (if no update is found with stock ROM):
https://forum.xda-developers.com/moto-z/development/tool-motorola-ota-link-generator-tool-t3537039
After you downloaded the first update, reboot to recovery (e.g. adb reboot recovery), tap on power button while holding vol_up and the menu appears. Select update over adb (or something like this) connect the phone and do adb sideload updatefile.zip
edit: You might need to flash stock ROM twice.
Loader009 said:
First you flash a stock ROM (skip gpt and bootloader updates).
Then use this tool to get the first update (if no update is found with stock ROM):
https://forum.xda-developers.com/moto-z/development/tool-motorola-ota-link-generator-tool-t3537039
After you downloaded the first update, reboot to recovery (e.g. adb reboot recovery), tap on power button while holding vol_up and the menu appears. Select update over adb (or something like this) connect the phone and do adb sideload updatefile.zip
edit: You might need to flash stock ROM twice.
Click to expand...
Click to collapse
All right, thanks. I assume that i can't lock bootloader with this sort of flashing
knjigo said:
All right, thanks. I assume that i can't lock bootloader with this sort of flashing
Click to expand...
Click to collapse
Try this:
https://forum.xda-developers.com/moto-z/help/how-to-lock-bootlader-t3685682/page5
Didn't test it though.
Related
Hi guys
So the problem I faced, I accidentally formatted my personal data off my phone, which included a rom I had just put onto my phone to install.
Obviously the rom had been deleted too, so I decided to ADB sideload a rom. As I did this I ran into an error reading 'Error: closed'. I couldn't find a way around it so I decided to use hasoon2000's tool to flash RUU zip. It mentioned that I'd need to relock the Bootloader in order to do so, so I simply relocked it using the tool. However, when trying to flash RUU from zip I get error:
sending 'zip' (711168 KB)...
OKAY [ 88.290s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) time: 4283
(bootloader) rom parsing finish ...
(bootloader) Your memory size = 59640MB, choose rawpt_64g.img
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 124.368s
Click to expand...
Click to collapse
I also get Customer ID error when trying to use RUU exe
I made an attempt to unlock the bootloader again, after failed 4 times, I decided to do one last try and it suceeded.
How would I go about using the RUU now? Should I risk relocking my bootloader? Should I leave bootloader unlocked and use RUU?
Or how would I get a rom onto SD card via fastboot?
Many thanks!
I have read. But I don't know much about your phone version. I don't know much about your OS. If you want help fill in your profile or at least gave the basics infos.
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?
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.
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......
i've lost my lost my imei during restoring a back up through twrp, then i encounter "Your device is corrupt. It cannot be trusted and will not boot". then i've flash a kdz H85010i_00_OPEN_EU_OP_0923.kdz, then when i try to reunlock my bootloader this is the result.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.035s]
writing 'unlock'...
(bootloader) ----------------------------------
(bootloader) Device-ID
(bootloader) 1C7832DD225B0CB8263BC96BB2F36819
(bootloader) B648B077E9D51C1E7B6290DB93F87B4D
(bootloader) ----------------------------------
(bootloader) IMEI
(bootloader) 000000000000000
(bootloader) ----------------------------------
(bootloader) Error!!
(bootloader) Wrong Bootloader Unlock key
FAILED (remote failure)
finished. total time: 0.159s
Me too
Im having the same problem... haven't found a solution yet but Im continuing to look!
Does anyone else have any ideas? I got into this position after the following:
Bricked my phone after wiping the misc partition - got certificate errors
Used LGUP and Uppercut to install v20d
Now, when I try to re-unlock I get the error above.
*#06# shows my IMEI correctly, it's just in the bootloader where it doesn't (which seems pretty odd). Im currently planning to try a different \ older kdz to see if that helps
FIXED IT!
Good news, I found a fix!
All I had to do was a factory reset (via LG Stock recovery steps) (I didn't use the older KDZ in the end). After that, I rebooted to bootloader and successfully flashed my existing unlock.bin
Not sure why this helped. After running LGUP, I noticed that I had all of my older apps still installed, but nothing was properly working (e.g. couldn't even copy files in File Manager). I suspect the factory reset removed whatever was upsetting the bootloader.
Hope this helps! Good luck