Database Users

[Q] Rooting Fail status read failed too many links

I have tried three different methods
Nexus 7 Toolkit 2.0
Nexus Root Toolkit 1.5.3
Downloading drivers manually and ran from CMD
all resulted with the same error
"downloading 'boot.img'...
Failed <status read failed <Too many links>>
finished. total time: 0.005s "
All failed to root my Nexus 7 4.1.1 JRO03D
I was able to unlock fine.
This is evidenced when I run fastboot or bootloader it clearly says unlocked in red letters and of course the unlocked icon shows when starting up
My system see the device properly and was able to unlock
I relocked and unlocked again
I restored an .ap backup using the 1.5.3 tool which worked well to get me back where I was albeit an unlocked system now.
If I may have permission I can post screen shots.

owcraftsman said:
I have tried three different methods
Nexus 7 Toolkit 2.0
Nexus Root Toolkit 1.5.3
Downloading drivers manually and ran from CMD
all resulted with the same error
"downloading 'boot.img'...
Failed <status read failed <Too many links>>
finished. total time: 0.005s "
All failed to root my Nexus 7 4.1.1 JRO03D
I was able to unlock fine.
This is evidenced when I run fastboot or bootloader it clearly says unlocked in red letters and of course the unlocked icon shows when starting up
My system see the device properly and was able to unlock
I relocked and unlocked again
I restored an .ap backup using the 1.5.3 tool which worked well to get me back where I was albeit an unlocked system now.
If I may have permission I can post screen shots.
Click to expand...
Click to collapse
I had this issue on my phone once. I had to reload everything. The boot loader seemed to get screwed up.
Try setting it all back to factory, and installing the boot loader again.

[Solved]
Thanks for the help.
After attempting several different things including a laptop w/Vista
I started fresh on a new machine which had nevber had the Nexus attached to it.
I downloaded Google Nexus 7 Toolkit 2.0 to the root of C:\
unblocked in properties and gave it run as administrator privileges while I was there.
Right clicked exe and clicked run as admin.
Once installed and opened I went in to #24 "toolkit settings" and entered my donator code and updated to 3.0
Reopened GN7T 3.0 used #1 the Install/Uninstall Google Nexus Drivers on my PC"
Attached my Nexus 7 w/supplied cable drivers installed without a hitch.
Since my N7 was basically bricked/ stuck in loop to on off bootloader only no OS after all I had tried
I went and used #9 "Download, Extract + Flash Factory Stock Rom" which I had before w/o success
This time it worked I went through initial setup wifi and google account and then enabled Developer Option & Debug mode.
Since things were going so well I decided to gamble again.
I used #8 "1-Click For All [unlock,root,rename,cwm,busybox all at once"
It all went well it unlocked rooted etc etc once the N7 rebooted I went in and opened Superuser to update all look good
Next I used #2 "Backup and Restore your device" to restore and backp (.ap) I made of all my apps before all this happened
again all went well and all my apps were back in place.
Now that I had everything backup and ruining I decided to do a complete Nandroid backup #7
leaving the files on my PC so if I ever need to go back to where I am right now.
I loaded drivers from donator ver 3.0 Google Nexus 7 Toolkit on a clean PC
I'm not sure exactly what did it but I suspect it was all driver related on the other PC
had I taken the time to clean out the current drivers and install them again who knows
maybe it was unblocking in the exe properties
or maybe running as administrator
I do know this changing cables and ports had no effect in my case but is always a good idea to try
In any case if you are reading this and in trouble like I was I hope this helps!

Moto X Pure Edition XT1575 - Always boots to Bootloader

I have the Moto X PE XT1575.
I had unlocked the boot loader and rooted it a while back.
I noticed that I had not recieved the May security update, so I checked and found that I had not gotten the Feburary update either.
So I tried got back to stock by downloading the image from Motorola, and installing that. But that also didn't make any differnce. But I did noticed that the bootloader would complain sometimes I would get the following error when trying to flash one of the files.
Code:
(bootloader) Preflash validation failed
I wasn't getting anywhere so I also went back to the 5.1.1 images from this thread. That seemed to get me some progress, as I could see that there was an update so I downloaded it but I could never get it to install.
Somewhere along the line, now though I've gottem my device stuck and it always boots to the bootloader and I have to manually tell it it to start booting system or recovery. I can't figure out how to get it out of that state.
I've tried the stock images, etc, but nothing seems to help.
If anyone has any ideas, I'd much appreciate the advice.

userwaldo said:
I have the Moto X PE XT1575.
I had unlocked the boot loader and rooted it a while back.
I noticed that I had not recieved the May security update, so I checked and found that I had not gotten the Feburary update either.
So I tried got back to stock by downloading the image from Motorola, and installing that. But that also didn't make any differnce. But I did noticed that the bootloader would complain sometimes I would get the following error when trying to flash one of the files.
I wasn't getting anywhere so I also went back to the 5.1.1 images from this thread. That seemed to get me some progress, as I could see that there was an update so I downloaded it but I could never get it to install.
Somewhere along the line, now though I've gottem my device stuck and it always boots to the bootloader and I have to manually tell it it to start booting system or recovery. I can't figure out how to get it out of that state.
I've tried the stock images, etc, but nothing seems to help.
If anyone has any ideas, I'd much appreciate the advice.
Click to expand...
Click to collapse
Sounds like your stuck in OEM Fastboot mode, try entering this in fastboot :
fastboot oem fb_mode_clear
Sent from my Motorola XT1575 using XDA Labs

acejavelin said:
Sounds like your stuck in OEM Fastboot mode, try entering this in fastboot :
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Thanks! That is exactly what I was trying to find. I figured there was some kind of flag, somewhere, but I wasn't having any luck finding it.

stuck in bootloader, no recovery.

hi, i have a problem with my N6P. it was unlocked, twrp flashed and running newest version of this ROM http://forum.xda-developers.com/nexus-6p/development/rom-debloated-prerooted-deoxeded-t3372600.
then, out of the blue, phone refused to work. when i'm trying to restart it, only option is boot to bootloader. i was trying to flash newest radio, bootloader, vendor and recovery - all failed with message "(remote: flash write failure)"
when i'm in bootloader mode, Andy Android is lying on his back, with no red exclamation point.
also there is written below Andy:
BL: K
Baseband: (empty)
Product/Variant: Angler-VN2
Serialn Number: (is present, but i think there is no need to write it)
CPU: MSM8994 0x20001
eMMC: 32GB Samsung
DRAM: 3072MB HYNIX LPDDR4
Console: NULL
Battery OK
Device is LOCKED
Qfuse Status: ENABLED
Off-Mode-charge: ENABLED
Download Mode: DISABLED
Connect USB Data Cable
strange thing is, that there is written "Device is LOCKED", because when wrote command "fastboot flashing unlock", there was a message:
...
(bootloader) Device already unlocked!
FAILED (remote failure)
I was able to fastboot boot boot.img, but it hanged on "Google" screen.
device is not visible after writing "adb devices", but is visible after writing "fastboot devices".
any ideas?

Might be a dumb question, but have you tried going back to stock Android N using Googles Factory Image in fastboot just to determine if your phone will still boot into os?

i'm downloading GFI, but 3 more hours left to finish download (unless there is a mirror server to download them). i'll probably try to do it, but i would like to avoid it because my backup is 2 months old :/

Fe Mike said:
Might be a dumb question, but have you tried going back to stock Android N using Googles Factory Image in fastboot just to determine if your phone will still boot into os?
Click to expand...
Click to collapse
tried this, no luck - still "remote flash write failure" message.
strange thing is, that i'm able to relock the bootloader (at least command "fastboot flashing lock" gave me possibility to do this {(YES/NO) message}, i didn't relocked it.
i've read, that this is probably fried emmc, but would it be possible to relock bootloader though?

miguelm75 said:
tried this, no luck - still "remote flash write failure" message.
strange thing is, that i'm able to relock the bootloader (at least command "fastboot flashing lock" gave me possibility to do this {(YES/NO) message}, i didn't relocked it.
i've read, that this is probably fried emmc, but would it be possible to relock bootloader though?
Click to expand...
Click to collapse
You might be right about fried emmc, have you tried placing a twrp.img in fastboot folder and run command fastboot boot twrp-x-x-x.img (not flash)? If it is fried can you rma?
Edit: I found this thread, second post has a link that may help. It is kinda advanced. The process can at least tell you if in fact emmc is bad and if it's not bad there may be a way of fixing it.

Fe Mike said:
You might be right about fried emmc, have you tried placing a twrp.img in fastboot folder and run command fastboot boot twrp-x-x-x.img (not flash)? If it is fried can you rma?
Edit: I found this thread, second post has a link that may help. It is kinda advanced. The process can at least tell you if in fact emmc is bad and if it's not bad there may be a way of fixing it.
Click to expand...
Click to collapse
1. i tried to flash recovery - no luck.
2. there will be problem with RMA, because i won this phone in a giveaway at AndroidAuthority.com and it has US warranty, so it would be rather expensive to send it to USA from Poland. but i will try to contact Huawei support in my country.
3. did you forgot to insert link to this thread?

miguelm75 said:
1. i tried to flash recovery - no luck.
2. there will be problem with RMA, because i won this phone in a giveaway at AndroidAuthority.com and it has US warranty, so it would be rather expensive to send it to USA from Poland. but i will try to contact Huawei support in my country.
3. did you forgot to insert link to this thread?
Click to expand...
Click to collapse
Yes I did, my bad.
https://www.google.com/amp/s/amp.re...here_a_way_to_check/?client=ms-android-google

Fe Mike said:
Yes I did, my bad.
https://www.google.com/amp/s/amp.re...here_a_way_to_check/?client=ms-android-google
Click to expand...
Click to collapse
thank you. unfortunatelly this is for LG devices. i can't find anything similiar for Huawei devices. i did tried Nexzus Root Toolki by Wug Fresh and i got the same error - "remote flash write failure"
so i think i will try to contact Huawei and local phone service to see, if they are able to fix it. thank you for your help.

Did you try to format data partition then flash the google image?

Iceburn1 said:
Did you try to format data partition then flash the google image?
Click to expand...
Click to collapse
i just did and received (remote: failed to erase partition) error.

miguelm75 said:
thank you. unfortunatelly this is for LG devices. i can't find anything similiar for Huawei devices. i did tried Nexzus Root Toolki by Wug Fresh and i got the same error - "remote flash write failure"
so i think i will try to contact Huawei and local phone service to see, if they are able to fix it. thank you for your help.
Click to expand...
Click to collapse
The op has an LG device but in second post there is a link (the one I'm posting now) for Qualcomm chipsets.
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301

miguelm75 said:
tried this, no luck - still "remote flash write failure" message.
strange thing is, that i'm able to relock the bootloader (at least command "fastboot flashing lock" gave me possibility to do this {(YES/NO) message}, i didn't relocked it.
i've read, that this is probably fried emmc, but would it be possible to relock bootloader though?
Click to expand...
Click to collapse
Same thing just happened to me except I was just using my phone then it crashed and never came back tried for days to recover was able to re-lock bootloader but no other commands took. Had to RMA it back to Huawei took 3 weeks but it was covered by 12 month warranty so that's a plus

did you switch on find my phone in administer options before unlocking and flashing errors ?

rowihel2012 said:
did you switch on find my phone in administer options before unlocking and flashing errors ?
Click to expand...
Click to collapse
no, i didn't touch it.

Happened to me too while using it. I am still trying to save my data, but no luck for now.

(ROOTED) MOTO X Pure (Style) XT1575 Cannot recieve calls

Make: Motorola
Model: Moto X Pure Edition (Style) XT1575
OS: 6.0 Marshmallow
Rooted: yes
Bootloader: you'd better believe it
Hello,
I am having a little trouble with the calling function on my moto x pure edition XT1575.
Problem:
The first time i loaded the os, my phone couldnt boot. it was stuck on the bootloader screen for days until i found a file that i ran in my recovery called SR3 SuperSU v2.78 it helped my phone get out of the bootloader page and i was finally able to use my phone and everything was great! until somebody called.
The phone is connected to my cell network and the phone will ring and i can call out. But, when i hit the phone but it does not display the call window. sometimes i dont realize i am calling somebody until i hear a small "Hello?". while i am on the call with the other person I am on the home screen and can not hang up the call. When others call me my phone rings but it only displays the home screen and it will not allow me to answer the call. All i can do is wait for the phone to stop ringing and hit the call button to call them back. I cannot call my voicemail as there is no keypad. only the home screen and yes i tend to pull up apps with my face.
The only solution i have to this problem is to connect a bluetooth device to it. I have been wearing my Gear S2 3G around so i could make and answer calls minus the use of the voice functionality. Voice commands do not work on my smartwatch anymore for some reason. I have to manually turn the dial to select the contact i would like to call. I can still add phone numbers on the phone (this function didnt work before until i installed another os then reinstalled it). but quite frankly, there is a time i would like to be able to pick up my phone and just answer an incoming call rather then fiddling around with this watch all the time. trying to keep it charged.
What I have tried:
I have tried a number of things. installing a new boot img, new recovery, downloading a new kernel. loading all new img folders into the command prompt. Then my laptop was acting up and i had to reinstall windows to fix it. A friend of mine suggested I should work on getting back my original os and reload some working folders . Ok, so i followed the steps and noticed my command prompt now will not read my phone to load the new img's and i noticed the drivers are not installed. ok, im working with a new computer basically and it doesnt quite recognize my phone. so i installed motorola device manager. adb, usb and the other driver has installed correctly, cool. I tried the casual test on the command prompt "adb devices" it didnt recognize it...ok? so i tried to type in the recovery img like before. nothing. tried to boot up the bootloader. nothing. what is going on here? i have all the drivers and the files waiting to go into the phone. I even restarted the computer to finalize the changes i made to the computer. nothing i have tried works.
what am i going to try next?
clockworkmod... if this doesnt work then i dont know what will.
If there are any suggestions out there any anyone that can help me with the problems that i am having with my phone please reply to this post. Thank you for any help that is posted up here. I will try to comment on what method has worked for me so that whoever has this problem will be able to fix this very simple functionality for a phone. I mean what is the point of carrying around a phone that cannot make or receive phone calls? sure its rooted and thats all cool and fancy. but its laughable that my phone cannot handle what a phone is supposed to do. At this point i might be carrying around 2 phones with me. its ridiculous lol. A phone that cannot call people. I have a small tablet. its not even a phone anymore lol. its a fancy tablet. please comment below, thank you guys!

(update)
I just followed the instructions on this link (http://forum.xda-developers.com/moto-x-style/general/xt1572-mm-twrp-root-xposed-t3276792) from another member of this site. I restored my phone to the way it was when i bought it. but i dont have any connection through my data nor can i connect to wifi. will update again when i find a fix.

Tacoman64 said:
Make: Motorola
Model: Moto X Pure Edition (Style) XT1575
OS: 6.0 Marshmallow
Rooted: yes
Bootloader: you'd better believe it
Hello,
I am having a little trouble with the calling function on my moto x pure edition XT1575.
Problem:
The first time i loaded the os, my phone couldnt boot. it was stuck on the bootloader screen for days until i found a file that i ran in my recovery called SR3 SuperSU v2.78 it helped my phone get out of the bootloader page and i was finally able to use my phone and everything was great! until somebody called.
The phone is connected to my cell network and the phone will ring and i can call out. But, when i hit the phone but it does not display the call window. sometimes i dont realize i am calling somebody until i hear a small "Hello?". while i am on the call with the other person I am on the home screen and can not hang up the call. When others call me my phone rings but it only displays the home screen and it will not allow me to answer the call. All i can do is wait for the phone to stop ringing and hit the call button to call them back. I cannot call my voicemail as there is no keypad. only the home screen and yes i tend to pull up apps with my face.
The only solution i have to this problem is to connect a bluetooth device to it. I have been wearing my Gear S2 3G around so i could make and answer calls minus the use of the voice functionality. Voice commands do not work on my smartwatch anymore for some reason. I have to manually turn the dial to select the contact i would like to call. I can still add phone numbers on the phone (this function didnt work before until i installed another os then reinstalled it). but quite frankly, there is a time i would like to be able to pick up my phone and just answer an incoming call rather then fiddling around with this watch all the time. trying to keep it charged.
What I have tried:
I have tried a number of things. installing a new boot img, new recovery, downloading a new kernel. loading all new img folders into the command prompt. Then my laptop was acting up and i had to reinstall windows to fix it. A friend of mine suggested I should work on getting back my original os and reload some working folders . Ok, so i followed the steps and noticed my command prompt now will not read my phone to load the new img's and i noticed the drivers are not installed. ok, im working with a new computer basically and it doesnt quite recognize my phone. so i installed motorola device manager. adb, usb and the other driver has installed correctly, cool. I tried the casual test on the command prompt "adb devices" it didnt recognize it...ok? so i tried to type in the recovery img like before. nothing. tried to boot up the bootloader. nothing. what is going on here? i have all the drivers and the files waiting to go into the phone. I even restarted the computer to finalize the changes i made to the computer. nothing i have tried works.
what am i going to try next?
clockworkmod... if this doesnt work then i dont know what will.
If there are any suggestions out there any anyone that can help me with the problems that i am having with my phone please reply to this post. Thank you for any help that is posted up here. I will try to comment on what method has worked for me so that whoever has this problem will be able to fix this very simple functionality for a phone. I mean what is the point of carrying around a phone that cannot make or receive phone calls? sure its rooted and thats all cool and fancy. but its laughable that my phone cannot handle what a phone is supposed to do. At this point i might be carrying around 2 phones with me. its ridiculous lol. A phone that cannot call people. I have a small tablet. its not even a phone anymore lol. its a fancy tablet. please comment below, thank you guys!
Click to expand...
Click to collapse
The problem here is we don't know your phones state and what files you have used and what you have done...
To be honest, at this point I would do a full reflash back to pure stock. The instruction link is in my signature (you don't have to lock, that is optional). Once you are in a known good state, then maybe you can root the right way.

Found the problem (no solution yet)
it seems all of my files are running fine when i enter them into the command prompt but the only one that is not working is the gpt.bin.
(fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.369s)
I didnt just copy and paste the name. i manually typed it but it just doesnt work for some reason. hope this information helps.

Tacoman64 said:
it seems all of my files are running fine when i enter them into the command prompt but the only one that is not working is the gpt.bin.
(fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.369s)
I didnt just copy and paste the name. i manually typed it but it just doesnt work for some reason. hope this information helps.
Click to expand...
Click to collapse
Yup... As I suspected... "Preflash validation failed" means you are attempting to flash an older Android version than you have already installed. You need to use a newer/newest firmware version.

(update)
I have successfully unrooted my device. I have typed all the file commands in the command prompt and the only error i got was a preflash validation failed error. I read a few forums to make sure that this was not going to brick my device and found out. Because i am not upgrading my os. the gpt.bin file really isnt necessary. I suppose it would be good to try to code it in anyways but if it fails then it should be fine.
THE PROBLEM:
Was another file wasnt installing correctly. I think the first time i typed in Flash modem NON-HLOS.bin It must have failed before but i didnt see it. It failed again on me but i sent the command again and it successfully installed (huh... weird).
In Conclusion:
So it goes to show you.
Rule 1: OPEN command prompt in the same folder you have your files extracted on by holding shift+right click. It should have an option to open command prompt. (if you've tried it multiple times then put the files in a new folder)
Rule 2: CHECK YOUR COMMANDS! see if they have installed correctly. gpt.bin file doesnt mean anything if you're not upgrading your original os.
Rule 3reverts to rule 2) CHECK your NON-HLOS.bin file in your commands list to see if it downloads correctly to you command prompt.
Rule 4:NO FAILURES. NONE of these other files should say failed and if they do. RE-TYPE them in. If that doesnt work. then download another file. you might just either have a broken file, it didnt download correctly or it might just be the wrong one. find the right file for your model number of phone!
This is to all those who dont know much about computers.
Rule 5: MISSING FILES. If there are any missing files then check your files. the failures could be due to not extracting your files, not downloading the proper files, and simply typing them incorrectly. ex. fastboot flash logo "logo.bin". if your logo name is not "logo.bin" and you just copy pasted it. the file will fail. your file could say something different like "XT1575-logo-new-9-14-15.bin". So instead, type in "fastboot flash logo XT1575-logo-new-9-14-15.bin" it should successfully download. If it doesnt. revert back to the previous rules.
NOW: On to Re-Rooting my device.

Tacoman64 said:
I have successfully unrooted my device. I have typed all the file commands in the command prompt and the only error i got was a preflash validation failed error. I read a few forums to make sure that this was not going to brick my device and found out. Because i am not upgrading my os. the gpt.bin file really isnt necessary. I suppose it would be good to try to code it in anyways but if it fails then it should be fine.
THE PROBLEM:
Was another file wasnt installing correctly. I think the first time i typed in Flash modem NON-HLOS.bin It must have failed before but i didnt see it. It failed again on me but i sent the command again and it successfully installed (huh... weird).
In Conclusion:
So it goes to show you.
Rule 1: OPEN command prompt in the same folder you have your files extracted on by holding shift+right click. It should have an option to open command prompt. (if you've tried it multiple times then put the files in a new folder)
Rule 2: CHECK YOUR COMMANDS! see if they have installed correctly. gpt.bin file doesnt mean anything if you're not upgrading your original os.
Rule 3reverts to rule 2) CHECK your NON-HLOS.bin file in your commands list to see if it downloads correctly to you command prompt.
Rule 4:NO FAILURES. NONE of these other files should say failed and if they do. RE-TYPE them in. If that doesnt work. then download another file. you might just either have a broken file, it didnt download correctly or it might just be the wrong one. find the right file for your model number of phone!
This is to all those who dont know much about computers.
Rule 5: MISSING FILES. If there are any missing files then check your files. the failures could be due to not extracting your files, not downloading the proper files, and simply typing them incorrectly. ex. fastboot flash logo "logo.bin". if your logo name is not "logo.bin" and you just copy pasted it. the file will fail. your file could say something different like "XT1575-logo-new-9-14-15.bin". So instead, type in "fastboot flash logo XT1575-logo-new-9-14-15.bin" it should successfully download. If it doesnt. revert back to the previous rules.
NOW: On to Re-Rooting my device.
Click to expand...
Click to collapse
Actually, your experience is not weird... it is not uncommon for NON-HLOS to fail the first time, subsequent attempts usually work... no idea why, some people say to use the erase modemst# commends first, others don't...
You are still in a mixed environment, the fact your are getting a preflash validation error means your partition table is newer than the one you are attempting to flash, this your device is out of sync (all your partitions don't match version wise). Although this condition itself will not result in bricking, taking an OTA later could cause that (we don't know, it could potentially). Something is definitely amiss, otherwise the gpt.bin would flash and go fine, but the phone KNOWS the partition table you are attempting to flash is older than the one on the device, that should tell you something. If you are going to flash a custom ROM, oh well, but if you are going to stay stock you should flash the latest 18-4 firmware image completely.

my intentions are to root my phone. I was just repairing my call functionality so i could receive phone calls. my phone works now. i can call people and i think receive calls because the call page pulls up when i call out. i dont know if i could receive calls because my phone is currently not activated. (not a phone issue, just didnt pay the bill) when my phone was activated with the root. the phone would ring but no call came up and when i called out the phone page would not be there. so i couldnt hang up a call or access the number pad while in a call for automated systems. now i can so i think that part of it is fixed. I am currently following one of your how to pages but it doesnt explain how to install twrp on the phone. it only says to go to advanced mode of what i believe to be the advanced mode on the recovery menu and put in that command before installing supersu. im still looking for command prompts on how to reinstall my recovery and trying to better understand what advanced setting you are trying to point out.

ITS ALIVE!!!
My phone is now FIXED and ROOTED! thanks to all of you wonderful people out there who helped me! posting up the wonderful posts that include all of the files, data and commands i needed to make this possible. Thank you all again! You guys are the best. now all there is to do is to put some mods on here and have fun with my new toy

acejavelin said:
Actually, your experience is not weird... it is not uncommon for NON-HLOS to fail the first time, subsequent attempts usually work... no idea why, some people say to use the erase modemst# commends first, others don't...
You are still in a mixed environment, the fact your are getting a preflash validation error means your partition table is newer than the one you are attempting to flash, this your device is out of sync (all your partitions don't match version wise). Although this condition itself will not result in bricking, taking an OTA later could cause that (we don't know, it could potentially). Something is definitely amiss, otherwise the gpt.bin would flash and go fine, but the phone KNOWS the partition table you are attempting to flash is older than the one on the device, that should tell you something. If you are going to flash a custom ROM, oh well, but if you are going to stay stock you should flash the latest 18-4 firmware image completely.
Click to expand...
Click to collapse
I made a how to explaining step by step. how to properly root the moto x pure and or all 6.0 motorola's If you would like to check out, make corrections to my post feel free, and or if you have any suggestions on how to make it better please let me know. http://forum.xda-developers.com/moto-x-style/general/how-to-unlock-root-moto-x-pure-style-t3504263

Tacoman64 said:
I made a how to explaining step by step. how to properly root the moto x pure and or all 6.0 motorola's If you would like to check out, make corrections to my post feel free, and or if you have any suggestions on how to make it better please let me know. http://forum.xda-developers.com/moto-x-style/general/how-to-unlock-root-moto-x-pure-style-t3504263
Click to expand...
Click to collapse
It's funny because my guide went live the other day, just haven't added it to my sig yet... http://forum.xda-developers.com/moto-x-style/general/guide-how-to-root-pure-style-t3503958

acejavelin said:
It's funny because my guide went live the other day, just haven't added it to my sig yet... http://forum.xda-developers.com/moto-x-style/general/guide-how-to-root-pure-style-t3503958
Click to expand...
Click to collapse
I seen that that's where I got the code I was missing the first time around. I am about to create another post and attach that link to it on here too. So if someone were to mess up their phone by skipping or not checking the command prompt then they have a plan B. I'll be the simple 1 stop post for every issue on Motorola like Walmart lol. I think it will get cluttered though.

Is this Moto G5 Plus "gone" or is there hope for recovery?

Hello,
My wife's moto g5 plus today just showed up with "startup failed" and it's booting in Fastboot Flash Mode (Secure).
This phone was stock international version, nothing was touched.
My thought is that probably the storage device is dead (or close to), because any operation I tried ends with FAILED (remote failure), even flashing a new partition.
If I try to use "factory" (within fastboot flash mode), it fails booting, same goes for any other option beside "bootloader logs" and BarCodes.
Interesting, I discovered that the IMEI and SKU for this phone are all zeros, even though nothing was ever flashed on this phone beside standard OTA updates, so maybe the storage device has been failing for a while. I remember at some point asking my wife why her phone was always running on 3G. (This was a new phone, not a used one).
Unfortunately OEM is locked, but when I try to unlock it with fastboot oem get_unlock_data, I get:
Code:
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.037s]
finished. total time: 0.038s
At this point I'm considering purchasing a new phone, but I'd be happy to perform some other test (at this point I don't care of anything that's on the phone, it's going in the garbage anyway) that someone might suggest.
Finally, a way to cleanup the storage device would be ideal, I want to clear the phone before throwing it in the garbage (well, recycling really)
Thanks for any help!

Yup. No hope. Probably the storage is done. Get a new device.

Fire-Dragon-DoL said:
Hello,
My wife's moto g5 plus today just showed up with "startup failed" and it's booting in Fastboot Flash Mode (Secure).
This phone was stock international version, nothing was touched.
My thought is that probably the storage device is dead (or close to), because any operation I tried ends with FAILED (remote failure), even flashing a new partition.
If I try to use "factory" (within fastboot flash mode), it fails booting, same goes for any other option beside "bootloader logs" and BarCodes.
Interesting, I discovered that the IMEI and SKU for this phone are all zeros, even though nothing was ever flashed on this phone beside standard OTA updates, so maybe the storage device has been failing for a while. I remember at some point asking my wife why her phone was always running on 3G. (This was a new phone, not a used one).
Unfortunately OEM is locked, but when I try to unlock it with fastboot oem get_unlock_data, I get:
At this point I'm considering purchasing a new phone, but I'd be happy to perform some other test (at this point I don't care of anything that's on the phone, it's going in the garbage anyway) that someone might suggest.
Finally, a way to cleanup the storage device would be ideal, I want to clear the phone before throwing it in the garbage (well, recycling really)
Thanks for any help!
Click to expand...
Click to collapse
Sounds like the eMMC is broken.
Just to have made the attempt you could try to flash the latest signed Motorola firmware:
https://mirrors.lolinet.com/firmware/moto/potter/official/
Choose the 8.1.0_OPS28.85-17-6-2 build for your region and flash it by fastboot.
You should have Motorola drivers and ADB/Fastboot installed, everything downloadable here:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
But as said above, there's not much hope.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
Sounds like the eMMC is broken.
Just to have made the attempt you could try to flash the latest signed Motorola firmware:
https://mirrors.lolinet.com/firmware/moto/potter/official/
Choose the 8.1.0_OPS28.85-17-6-2 build for your region and flash it by fastboot.
You should have Motorola drivers and ADB/Fastboot installed, everything downloadable here:
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
But as said above, there's not much hope.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Thanks, tested all that.
If fails at the first command, but I tried running the others just to see if it would "do anything". It fails on every command with a "remote" error.
I guess it IS dead. Time to look for a new cheap phone :silly:

Perhaps one last ditch try, use Lenovo Smart Assistant -
https://support.lenovo.com/us/en/downloads/ds101291

goodjuju said:
Perhaps one last ditch try, use Lenovo Smart Assistant -
https://support.lenovo.com/us/en/downloads/ds101291
Click to expand...
Click to collapse
Tested that too, it's a brick
Thanks for the suggestion though, I appreciated the good will!

fwiw....Due to the recent launch of the G8, brand new 64GB/4GB Moto G7s, not the janky Power or Play models, are going for $150-$160 'Buy it Now' on ebay and new 64gb/3gb G6's for $99! I luv it when a new G launches...prices come a tumblin down.
Also...the nearly new 'Open Box' & A+ grade G7s will start going waay down as folks start trading in their G7s for a G8, or other, to upgrade. I've had fantastic luck with open boxers...like the G5+ I have now.