Hi guys,
Nothing I am trying works. Nothing I'm doing has any effect. fastboot shows my phone, adb does not. I have the official recovery from Motorola, but I can't flash any of the pieces in. Everything fails.
The phone is locked. I can't boot it, so I can't unlock it. I also can't enable bridge mode.
I've set ANDROID_PRODUCT_OUT and tried "fastboot -w flashall" but it only says "error: could not load android-info.txt: No error". I'd make one, but I don't know what it should contain. Googling it tells me nothing.
RSDLite doesn't see my phone.
I can get to recovery and I can get it into "adb sideload", but I don't have a zip. I could make one? What needs to go in it?
Does anyone have any ideas that could help? Anything and everything seems to require an unlocked bootloader and I can't do that.
Terrenius said:
Hi guys,
Nothing I am trying works. Nothing I'm doing has any effect. fastboot shows my phone, adb does not. I have the official recovery from Motorola, but I can't flash any of the pieces in. Everything fails.
The phone is locked. I can't boot it, so I can't unlock it. I also can't enable bridge mode.
I've set ANDROID_PRODUCT_OUT and tried "fastboot -w flashall" but it only says "error: could not load android-info.txt: No error". I'd make one, but I don't know what it should contain. Googling it tells me nothing.
RSDLite doesn't see my phone.
I can get to recovery and I can get it into "adb sideload", but I don't have a zip. I could make one? What needs to go in it?
Does anyone have any ideas that could help? Anything and everything seems to require an unlocked bootloader and I can't do that.
Click to expand...
Click to collapse
When you try to flash the recovery image what does the error say? Were you on 6.0, 5.1, or 4.4.4?
Enviado desde mi XT1095 mediante Tapatalk
AGISCI said:
When you try to flash the recovery image what does the error say? Were you on 6.0, 5.1, or 4.4.4?
Click to expand...
Click to collapse
When the phone died, I was on 5.1; hadn't gotten Marshmallow yet.
Code:
ro.build.fingerprint[0]: motorola/victara_tmo/victara:5.1/L
ro.build.fingerprint[1]: PE23.32-21.6/7:user/release-keys
ro.build.version.full[0]: Blur_Version.23.16.6.victara_tmo.
ro.build.version.full[1]: tmo.en.US
ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
ro.build.version.qcom[1]: .04.04.02.048.045
When I try to flash the recovery image, it says:
Code:
C:\MotoX\TMO_5.1_LPE23.32-21.3_5_23.16.3.victara_tmo.tmo.en.US>Windows\fastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.361s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.478s
fastboot on the phone says:
Code:
Fastboot Reason: Volume down key pressed
USB Connected
cmd: getvar:max-sparse-size
cmd: download:00a0a000
cmd: flash:recovery
Using the USB cable that came with the phone plugged into a monitor USB 2.0 port. I downloaded the Motorola drivers and manager. I think things are communicating properly (though I'd love to be wrong, because then it would be correctable.)
Terrenius said:
When the phone died, I was on 5.1; hadn't gotten Marshmallow yet.
Code:
ro.build.fingerprint[0]: motorola/victara_tmo/victara:5.1/L
ro.build.fingerprint[1]: PE23.32-21.6/7:user/release-keys
ro.build.version.full[0]: Blur_Version.23.16.6.victara_tmo.
ro.build.version.full[1]: tmo.en.US
ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
ro.build.version.qcom[1]: .04.04.02.048.045
When I try to flash the recovery image, it says:
Code:
C:\MotoX\TMO_5.1_LPE23.32-21.3_5_23.16.3.victara_tmo.tmo.en.US>Windows\fastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.361s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.478s
fastboot on the phone says:
Code:
Fastboot Reason: Volume down key pressed
USB Connected
cmd: getvar:max-sparse-size
cmd: download:00a0a000
cmd: flash:recovery
Using the USB cable that came with the phone plugged into a monitor USB 2.0 port. I downloaded the Motorola drivers and manager. I think things are communicating properly (though I'd love to be wrong, because then it would be correctable.)
Click to expand...
Click to collapse
I beleive the problem is that you are flashing the wrong firmware. What I read is that your phone has build 23.32-21.6 installed(stagefright patch) but you are trying to flash an older firmware 23.32-21.3(without stagefright patch). With a locked bootloader that will fail because it does not let you flash older firmware. Here is the correct firmware for your phone:
http://www.filefactory.com/file/5d66szhobgmx/VICTARA_TMO_XT1095_5.1_LPE23.32-21.6_cid9_CFC.xml.zip
Sent from my XT1095 using Tapatalk
AGISCI said:
I beleive the problem is that you are flashing the wrong firmware. What I read is that your phone has build 23.32-21.6 installed(stagefright patch) but you are trying to flash an older firmware 23.32-21.3(without stagefright patch). With a locked bootloader that will fail because it does not let you flash older firmware. Here is the correct firmware for your phone:
http://www.filefactory.com/file/5d66szhobgmx/VICTARA_TMO_XT1095_5.1_LPE23.32-21.6_cid9_CFC.xml.zip
Click to expand...
Click to collapse
Since your post I have tried lots of things and gotten nowhere.
Flashing the recovery.img in the ROM you linked yields the same error. I then tried flashing the partition because I thought maybe the whole filesystem was corrupted. That first gave the too many links error. When I tried again, it just failed. When I tried a third time with a new cable, Windows 8.1 says that fastboot is not compatible with my OS anymore. Rebooting didn't solve anything.
So, my next step is to live boot a Linux distro and try using that to flash the phone. I wonder if my memory is just completely fried.
Related
Hey guys, I did something really stupid.
I acquired an Atrix HD through a third party, network/sim unlocked it to work on T-Mobile, and tried to flash 4.1.2 Mexican Retail (MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX) through RSD Lite 6.1.5 after removing the getvar command and.. it failed half way. I forgot to unlock the bootloader before flashing.
Now I'm stuck and I've tried almost everything to fix it. I've searched Google and XDA, in the process I have downloaded Myth Tools, sirhoover_atrixhd_utility, motochopper, motopocalypse, and moto-fastboot, tried them all to the best of my knowledge and nothing is working. I've even edited the XML file to exclude the files it fails on.
Common errors I encounter:
Fastboot reason: Boot failure
Fastboot reason: Flash failure
Partition (boot) Security Version Downgraded
Preflash Validation Failed for boot
Partition (system) Security Version Downgraded
PIV black validation for system failed
Invalid PIV image: system
Worst part is, I can't unlock my bootloader because I need ADB to do so! Recovery will give me ADB but only to sideload (available on certain recoveries I've managed to flash). If you have any ideas or information that could assist me in getting my phone back to normal, whether that's unlocking the bootloader through fastboot or flashing a stock rom sucessfully, I would greatly appreciate it! :good:
You don't need a unlocked bootloader to flash firmware through rsd.. Try flashing the stock att back.
Sent from my PACMAN MATRIX HD MAXX
deeje00 said:
You don't need a unlocked bootloader to flash firmware through rsd.. Try flashing the stock att back.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
Thanks for your reply
I've tried flashing several stock firmwares already, I get preflash validation failed errors every time on boot.img and system.img
Here's the firmwares I have downloaded:
MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX
MB886_bell-user-4.1.2-9.8.2Q-8_MB886_FFW-11-4-release-keys-BellMobility-CA
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC
I wish I knew exactly the version I had before I started flashing, but unfortunately I do not..
DaveTheRave said:
Thanks for your reply
I've tried flashing several stock firmwares already, I get preflash validation failed errors every time on boot.img and system.img
Here's the firmwares I have downloaded:
MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX
MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC
7.7.1Q-115_MB886_FFW-14_SIGNED_CFC
I wish I knew exactly the version I had before I started flashing, but unfortunately I do not..
Click to expand...
Click to collapse
Once your phone's OS has been upgraded, I don't think you can flash to an older firmware unless you have an unlocked bootloader. I'm not sure but that maybe the reason you're getting validation errors.
Did you try re-downloading the firmware?
audit13 said:
Once your phone's OS has been upgraded, I don't think you can flash to an older firmware unless you have an unlocked bootloader. I'm not sure but that maybe the reason you're getting validation errors.
Did you try re-downloading the firmware?
Click to expand...
Click to collapse
Just tried re-downloading everything on a brand new Windows install on a different computer, still having problems.
No matter how hard I try, I cannot get boot.img or system.img to flash from any Stock firmware, whether it's AT&T, Mex, or Bell
Using snap-fastboot:
snap-fastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.788s]
writing 'boot'...
Preflash validation failed
FAILED (remote failure)
snap-fastboot flash system system.img
sending 'system' (30720 KB)...
OKAY [ 2.343s]
writing 'system'...
Preflash validation failed
FAILED (remote failure)
I'm going to try making a Motorola Factory cable in the meantime. Any other suggestions?
EDIT: Factory cable didn't help.. is there a way to generate a higher security version? No matter what, the bootloader always displays Partition (boot/system) Security Version Downgraded
I really don't want this to end up being a paperweight
Is this where you got the firmware: http://sbf.droid-developers.org/dinara/list.php ?
Did you reboot each time you loaded a different set of fastboot files? Did you remove the previous fastboot files before installing a new set of fastboot files? Are you able to try this on a different computer?
I just got a new Atrix HD replacement and its showing firmware of 9.8.0Q-97_MB886_FFW-20 . Its not the same as the firmware available here: http://sbf.droid-developers.org/ .... I get the same error even after modifying the XML file in the SBF. Wonder if the last update caused an issue. Running into some similar issue with the replacement. Its not wanting to bootloader unlock.
Did you mount the system before installing?
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Sorry I've been MIA, been busy with work.
TabascoTX said:
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Click to expand...
Click to collapse
Thanks for the reply! I wished this worked for me. After completing the steps successfully, I get:
Partition (boot) Security Version Downgraded
Fastboot Reason: Boot Failure
Code:
adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
fastboot oem fb_mode_set
...
OKAY [ 0.006s]
finished. total time: 0.006s
fastboot oem fb_mode_clear
...
OKAY [ 0.005s]
finished. total time: 0.005s
fastboot erase userdata
erasing 'userdata'...
OKAY [ 3.095s]
finished. total time: 3.095s
fastboot erase cache
erasing 'cache'...
OKAY [ 1.669s]
finished. total time: 1.669s
fastboot reboot
rebooting...
finished. total time: 0.005s
audit13 said:
Is this where you got the firmware: http://sbf.droid-developers.org/dinara/list.php ?
Did you reboot each time you loaded a different set of fastboot files? Did you remove the previous fastboot files before installing a new set of fastboot files? Are you able to try this on a different computer?
Click to expand...
Click to collapse
That's exactly where I got my firmwares from. And to answer your question, I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.
DaveTheRave said:
...I have tried this on different computers but I wasn't doing much rebooting when changing fastboot files.
Click to expand...
Click to collapse
Try logging off and back on to see what happens. For me, using fastboot/adb commands on an x86 Win7 machine works more consistently than using an x64 Win7 machine.
TabascoTX said:
Found a fix for the AP Fastboot loop
List of commands to type in. ( in order)
1. adb reboot bootloader
2.fastboot oem fb_mode_set
3.fastboot oem fb_mode_clear
3.fastboot erase userdata
4.fastboot erase cache
5.fastboot reboot
Source:http://www.droidrzr.com/index.php/topic/17320-sticky-bit-fastboot/
Click to expand...
Click to collapse
When I run fastboot oem fb_mode_set, it just says "< waiting for any device >"
Sorry for the late reply. make sure you have adb installed and the drivers for the Atrix. Also,if possible and not in a boot loop or stuck in fastboot, device debugging should be enabled.
Boot problem
Hello here I have a problem and I made everything from my knowledge but It's not fixed.
I have a Motorola Droid Maxx X8 verison XI1080, version 4.4.4, built number SU4.21,
If I install or do something and I switch off and I turn on my phone it disappears as if it is never done and if I try to reinitialize the phone I have a error Fastboot Reason: Boot Failure
If I get the fastboot and I take recovery its said Boot up failed.
I did everything I flashed with RSD and I update it with Motorola update but still nothing we see that the flashing and the update works but on reboot Its has no effect on the phone its stays as if you did nothing.
Please help me! I look forward to a solution, I thank you more.
have u solved the problem
Please explain how u have solved the problem ,my moto g4 plus in same problems
DL'ed 5.0.1 and went to flash as I have done dozens of times. Always perform a manual fastboot flash ... I've had issues in the past nothing big. This time I'm kind of stumped. I have ATT N6, rooted, TWRP and the only single mod was the tap2wake. When I got to system.img I got (bootloader) Data size exceeds download buffer
I didn't 1st flash my TWRP, but then I did after this issue.
Thoughts ? I did roll back to my nandroid, but I would like to know what happened and why. Thanks!!
Are you using the latest fastboot version from the SDK?
El Daddy said:
Are you using the latest fastboot version from the SDK?
Click to expand...
Click to collapse
Yes, I made sure to dl the latest.
Here is what I'm getting;
fastboot flash system system.img
sending 'system' (1640247 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
Don't use the flash-all script. Do it manually line by line.
Nucleonic said:
Don't use the flash-all script. Do it manually line by line.
Click to expand...
Click to collapse
Thats exactly what I'm doing.
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.05.img
sending 'bootloader' (3807 KB)...
OKAY [ 0.177s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.415s]
finished. total time: 0.592s
fastboot flash radio radio-shamu-d4.0-9625-02.55.04.img
sending 'radio' (67169 KB)...
OKAY [ 2.619s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.948s]
finished. total time: 3.568s
fastboot flash system system.img
sending 'system' (1640247 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.002s
j
I flashed it earlier today and it worked fine. I haven't updated my SDK in about 2 weeks and everything worked just fine. I manually sent over each package before flashing another ROM.
I've never had this issue before. I'm wondering if it has anything to do with this being an ATT phone? Besides that I have no idea. I've searched and searched and no good answer. I may drop the factory 5.0 in if I can't find an answer.
I had a problem like this when I thought I bricked my phone in an earlier thread. Try doing this first:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Then flash the individual line items one at a time again. It worked for me.
Thanks for all the advice, this is what ultimately worked;
Ahem, I used a freaking Win7 PC!
Are you kidding me? I live and breath by my MacAir. I've never had an issue like this before. I finally decided to pull out my work PC, made sure it had the newest fastboot, extracted the .imgs and it worked.
So, XDA masters, why? I don't understand it. I made sure I dl'ed the newest SDK, pulled out the adb folder that included fastboot. Yet it would not break up the system.img.
jackpollard said:
Thanks for all the advice, this is what ultimately worked;
Ahem, I used a freaking Win7 PC!
Are you kidding me? I live and breath by my MacAir. I've never had an issue like this before. I finally decided to pull out my work PC, made sure it had the newest fastboot, extracted the .imgs and it worked.
So, XDA masters, why? I don't understand it. I made sure I dl'ed the newest SDK, pulled out the adb folder that included fastboot. Yet it would not break up the system.img.
Click to expand...
Click to collapse
I was getting ready to recommend you run the fastboot reboot bootloader command a few times in between some of those flashes. Some of the guides recommend you do that. Because of buffer overflow maybe? idk.
crashercarlton said:
I was getting ready to recommend you run the fastboot reboot bootloader command a few times in between some of those flashes. Some of the guides recommend you do that. Because of buffer overflow maybe? idk.
Click to expand...
Click to collapse
Hummm, that is a good suggestion, I wonder if rebooting my Mac would of done anything. I had an older fastboot, when I updated it to the newest one I didn't close terminal, i wonder if maybe it didn't release it. Very odd, I would like to know why this happened. I'm going to check the logs to see if they say anything. I suppose if doing it from a Win machine worked, I would lean towards driver, fastboot/adb. Thanks for all the feedback!
Please note they recently released a new copy of fastboot and adb, about the same time as the N6. Updating it for me helped.
Sent from my Nexus 6 using XDA Free mobile app
jackpollard said:
DL'ed 5.0.1 and went to flash as I have done dozens of times. Always perform a manual fastboot flash ... I've had issues in the past nothing big. This time I'm kind of stumped. I have ATT N6, rooted, TWRP and the only single mod was the tap2wake. When I got to system.img I got (bootloader) Data size exceeds download buffer
I didn't 1st flash my TWRP, but then I did after this issue.
Thoughts ? I did roll back to my nandroid, but I would like to know what happened and why. Thanks!!
Click to expand...
Click to collapse
you need to install and use mFastboot for things like that and edit the flash all to mFastboot
bkjolly said:
you need to install and use mFastboot for things like that and edit the flash all to mFastboot
Click to expand...
Click to collapse
Interesting, I grabbed this from the mfastboot site; "Unfortunately, that standard fastboot is limited on how big of files it can properly flash. In recent android devices, Motorola has surpassed the limits of fastboot, as such they have an "upgraded" or "tweaked" fastboot" certainly sounds like my issue. Thanks all.
bkjolly said:
you need to install and use mFastboot for things like that and edit the flash all to mFastboot
Click to expand...
Click to collapse
I use the sdk on my MacAir all the time and never have issues, just keep it updated, works for me.
I'm getting the same error on my mac when trying to fastboot system.img
any thoughts? or guidance on how to update the fastbook or sdk?
AceKingNYC said:
I'm getting the same error on my mac when trying to fastboot system.img
any thoughts? or guidance on how to update the fastbook or sdk?
Click to expand...
Click to collapse
The only thing that worked for me was to use a PC. I hate to say that, but nothing I did on my Mac worked. I have both a Win7 and Win8 setup, I used the Win8 for the N6. It seems that for some reason the fastboot on the PC will parse out the system.mg and flash it. I tried the mfastboot from Motorola, but it was not for the Mac.
I did make sure I had the new sdks and all the new tools on my Mac, all other .img's flashed just fine.
Anyway, my only suggestion is to use a PC, sorry.
jackpollard said:
The only thing that worked for me was to use a PC. I hate to say that, but nothing I did on my Mac worked. I have both a Win7 and Win8 setup, I used the Win8 for the N6. It seems that for some reason the fastboot on the PC will parse out the system.mg and flash it. I tried the mfastboot from Motorola, but it was not for the Mac.
I did make sure I had the new sdks and all the new tools on my Mac, all other .img's flashed just fine.
Anyway, my only suggestion is to use a PC, sorry.
Click to expand...
Click to collapse
Thanks for the info! I think I updated my SDK stuff yesterday - was my first time doing so but I saw there were updates and installed them. Going to give it a go later today and see if it made a difference. if not, going to have to find a Win8 computer to try this on
Update: I updated my fastboot file, and was able to install 5.0.1 and flash CF Auto Root without losing any data whatsoever. When i updated the SDK files, I took the updated fastboot file and dropped it into the folder where all the 5.0.1 files were, and obviously, removed the outdated fastboot one so that there were no mixups.
Hope this helps anyone running into this error!
Thanks for that follow-up, I'm going to go thru the sdk update again, I was rushing and maybe I messed something up. If it worked for you, I'm going to hope it works for me.
Okay, so all day, I've been trying to fix this damn phone because of a root fail. I unlocked the bootloader, installed SuperSU and now the phone just reboots with a white screen and red words saying this build is for development purposdes only. I can get to download and bootloader mode fine though. Its S-On Bootloader Unlocked. I would honestly settle for it to be set to factory settings as I just need the phone fixed. Rooting has been so stressful. I don't care about losing data.
I'm thinking it failed because I used an SDHC 32GB Micro SD Card? Ive been trying to use a recovery img, Im using HTC Android Phone ROM Update Utility and thats not working. It asks to update the ROm version from 3.35.401.12 to image version (shows nothing). Then it says image error 158 (cannot update my android phone).
When flashing a recovery image, I get:
C:\Users\shaif\Downloads\Root M9>fastboot flash recovery recovery.img
target reported max download size of 800000000 bytes
sending 'recovery' (32848 KB)...
OKAY [ 2.503s]
writing 'recovery'...
(bootloader) HOSD CL#671758
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.792s]
finished. total time: 5.301s
Still not working.
Also tried fastboot oem rebootRUU but that took me to a screen that says Security Warning
Someone please help me, Im desperate
Shaifhemraj said:
Okay, so all day, I've been trying to fix this damn phone because of a root fail. I unlocked the bootloader, installed SuperSU and now the phone just reboots with a white screen and red words saying this build is for development purposdes only. I can get to download and bootloader mode fine though. Its S-On Bootloader Unlocked. I would honestly settle for it to be set to factory settings as I just need the phone fixed. Rooting has been so stressful. I don't care about losing data.
I'm thinking it failed because I used an SDHC 32GB Micro SD Card? Ive been trying to use a recovery img, Im using HTC Android Phone ROM Update Utility and thats not working. It asks to update the ROm version from 3.35.401.12 to image version (shows nothing). Then it says image error 158 (cannot update my android phone).
When flashing a recovery image, I get:
C:\Users\shaif\Downloads\Root M9>fastboot flash recovery recovery.img
target reported max download size of 800000000 bytes
sending 'recovery' (32848 KB)...
OKAY [ 2.503s]
writing 'recovery'...
(bootloader) HOSD CL#671758
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.792s]
finished. total time: 5.301s
Still not working.
Also tried fastboot oem rebootRUU but that took me to a screen that says Security Warning
Someone please help me, Im desperate
Click to expand...
Click to collapse
I'm not sure if I can get you back to stock or not, but I can help move on to a custom ROM like Resurrection Remix. Just pm me sometime if you wanna give it a try.
Shaifhemraj said:
Okay, so all day, I've been trying to fix this damn phone because of a root fail. I unlocked the bootloader, installed SuperSU and now the phone just reboots with a white screen and red words saying this build is for development purposdes only. I can get to download and bootloader mode fine though. Its S-On Bootloader Unlocked. I would honestly settle for it to be set to factory settings as I just need the phone fixed. Rooting has been so stressful. I don't care about losing data.
I'm thinking it failed because I used an SDHC 32GB Micro SD Card? Ive been trying to use a recovery img, Im using HTC Android Phone ROM Update Utility and thats not working. It asks to update the ROm version from 3.35.401.12 to image version (shows nothing). Then it says image error 158 (cannot update my android phone).
When flashing a recovery image, I get:
C:\Users\shaif\Downloads\Root M9>fastboot flash recovery recovery.img
target reported max download size of 800000000 bytes
sending 'recovery' (32848 KB)...
OKAY [ 2.503s]
writing 'recovery'...
(bootloader) HOSD CL#671758
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.792s]
finished. total time: 5.301s
Still not working.
Also tried fastboot oem rebootRUU but that took me to a screen that says Security Warning
Someone please help me, Im desperate
Click to expand...
Click to collapse
Here's a handful of sites that have step-by-step instructions on unlocking the bootloader on an HTC One M9 device.
This list of links begins with the Official HTC Developers link on unlocking the bootloader (i was surprised to find):
http://www.htcdev.com/bootloader/
https://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
http://www.droidviews.com/how-to-unlock-bootloader-on-htc-one-m9/
https://www.androidexplained.com/htc-one-m9-unlock-bootloader/
They weren't hard to find using Google.
I wish you the best of luck!
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
********************************************
**IF I WAS HELPFUL IN ANY WAY THEN**
**PLZ THANK ME WITH A THUMBS UP!**
********************************************
How to unlock the OEM when I could not activate the developer options, because the device does not turn on?
It is not possible to flash a ROM because it says: flashing_locked
In short, the device only goes to Fastboot.
------------------
I manage to do the following. I did a temporary boot via Fastboot.
fastboot boot "Original ROM file or Boot.img Patched with Root"
More information I have I will be putting it here.
An application to use adb and fastboot without a computer.
Bugjaeger or Bugjaeger Premium
ps: requires otg support on the device you are going to control.
I'm out of results at the moment, I couldn't recover my Moto G7 Plus.
I've already lost almost 100% of the hopes that I can manage.
I think I will have to send it to a Motorola Official Technician or buy another device, as it is not worth me to have it fixed. because the stores are far from my city.
I was able to start the device, but I still can't activate oem unlock.
it is already a progress.
I used a modified boot.img and started the device using:
fastboot boot boot.img
the problem I have to use this command to turn on the device without...
if i get more news i will talk here.
Anrito Kun said:
if i get more news i will talk here.
Click to expand...
Click to collapse
Did you manage to solve it, or did you have any progress?
Could you send the boot.img file you used?
wfsmnt said:
Did you manage to solve it, or did you have any progress?
Could you send the boot.img file you used?
Click to expand...
Click to collapse
------------------
I don't know how to send files here.
I have no new results, but I will try to send the boot.img that could connect the device.
wfsmnt said:
Did you manage to solve it, or did you have any progress?
Could you send the boot.img file you used?
Click to expand...
Click to collapse
Boot.img: https://mirrorbits.lineageos.org/recovery/lake/20201222/lineage-17.1-20201222-recovery-lake.img
I haven't been able to do anything new yet.
I think that only specialist technicians will know how to fix the device.
Anrito Kun said:
Boot.img: https://mirrorbits.lineageos.org/recovery/lake/20201222/lineage-17.1-20201222-recovery-lake.img
Click to expand...
Click to collapse
------------------
After downloading use the command: fastboot boot file.img
This managed to start the device, but I couldn't get into Recovery ... At least I couldn't.
Does anyone know how to patch a boot.img file? most have to sign almost the same kernel signature.
Anrito Kun said:
Does anyone know how to patch a boot.img file? most have to sign almost the same kernel signature.
Click to expand...
Click to collapse
------------------
I think it may be possible to join TWRP with the system's Boot.img. As if it were a magched patched, only instead of magisk it is TWRP.
delete
delete
poog said:
Thanks for replying to my post. I tried your patched boot.img but when I try to flash it I get " (bootloader) fllash permission denied "
renamed it to boot.img and then....tried 2 things that fail
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
(bootloader) Failed to load/authenticate boot image: Not Found
FAILED (remote failure)
finished. total time: 0.510s
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (21845 KB)...
OKAY [ 0.465s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.479s
Click to expand...
Click to collapse
------------------
You're using the Moto G7 plus, right?
the command has to be this to use the file:
fastboot boot "file name".img
poog said:
I can boot to fastboot, but I cannot flash anything. I cannot get a proper return with "fastboot devices"
I cannot get RSD LITE to recognize my device. (win 10). I have read to try win7
Device Manager (windows 10) can only show the device as "Motorola ADB Device". I have not figured out how to force it to show as Qualcom ..............if that will make a difference or not. qualcom drivers are installed.
Before I messed it up I was able to load the device as a qualcom device on the right port and blankflashed after I hardbricked with nothing on screen.
Ability to boot to fastboot but not flash anything seems it is effectively dead for now.
Click to expand...
Click to collapse
------------------
There is no point in trying Flash on the device when the device is Flashing Locked.
My phone is in the same situation after I tried to re-lock the bootloader. Please do follow up on your progress.
hey I have the same problem have you found a solution?
Unfortunately, no.
I managed to brick a moto G7 plus to the point of not being able to recover from it (locked bootloader, no twrp, boots to fastboot)
I wanted to go back to 100% stock but failed badly.
My device is odd one. RETLA stream with XT1965-T hardware. Lenovo Rescue apparently don't work on these devices.
1) I flashed stock RETLA latest rom from Lolinet using a flash.bat I made
2) worked and booted fine.....twrp was still intact
3) I did factory reset when booted in.
4) To relock I flashed boot.img and sent lock command a few times
5) Bootloader is now locked but only boots to fastboot and get (YOUR DEVICE HAS LOADED A DIFFERENT OPERATING SYSTEM.
6) I cannot unlock with code because adb says says I need developer option etc.
To repeat: this is BOOTLOADER LOCKED, JUST BOOTS TO FASTBOOT and gives "your device loaded a different operating system) which is not the issue and I expected that.
Bankflash didn't do anything. I mostly get oermission denied with mostly flashing anythiine else.
Any suggestions on how to just get this thing at least bootable again to use?
Thanks.
I have the same problem, but I found a way to at least start the device.
I gave "fastboot boot file.img" with a boot.img patched via Magisk.
But then it stopped working, so I changed the boot.img file to LineageOS.
Anrito Kun said:
I have the same problem, but I found a way to at least start the device.
I gave "fastboot boot file.img" with a boot.img patched via Magisk.
But then it stopped working, so I changed the boot.img file to LineageOS.
Click to expand...
Click to collapse
------------------
I was only able to do what is here: https://forum.xda-developers.com/t/...oem-at-developer-option-moto-g7-plus.4201169/
Anrito Kun said:
------------------
I was only able to do what is here: https://forum.xda-developers.com/t/...oem-at-developer-option-moto-g7-plus.4201169/
Click to expand...
Click to collapse
Thanks for replying to my post. I tried your patched boot.img but when I try to flash it I get " (bootloader) fllash permission denied "
renamed it to boot.img and then....
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (21845 KB)...
OKAY [ 0.465s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.479s
PROBLEM SOLVED. See my post.
https://forum.xda-developers.com/t/moto-g7-plus-no-service.4201229/post-84335207