HELP Droid 3 Recovery Failed Flash - Motorola Droid 3

Hi, I am a professional phone repair guy and I am very familiar with adb, rooting, android OS ect. So I will probably only need to be pointed in the right direction... I have searched 3 days for a solution and I know that I haven't tried EVERY possible recovery solution... But the links on the SBF Droid 3 flash files are "DEAD" and I can't find them...
So I used psouza4's one click and got this...
AP Fastboot Flash Mode (S) (Boot Failure)
0A.53
Battery OK
OK to Program
ConectUSB
Data Cable
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG HAB (CG: system, status: 0X0035 )
Invalid CG OTV (CG: system)
I know I most likely just need an SBF file for whichever STOCK firmware I was on, not sure which so if someone can link me the file or at least point me in the right direction to restore this phone. (Had it 2 days and soft bricked)
Thanks in Advance

If it's an XT862, it seems you have 2 choices (verizon stock roms) here:
http://forum.xda-developers.com/showthread.php?t=1295839

I prefer the method below. Download the 450MB-ish file and then just follow the instructions in the OP. It takes about 5 minutes to get back to box stock. Just used it today actually.
http://forum.xda-developers.com/showthread.php?t=1339816

redsox985 said:
I prefer the method below. Download the 450MB-ish file and then just follow the instructions in the OP. It takes about 5 minutes to get back to box stock. Just used it today actually.
http://forum.xda-developers.com/showthread.php?t=1339816
Click to expand...
Click to collapse
Hey. Im Having the same problem as the last guy ..Unfortunately the links are now bad since the Feds busted megaupload..Any chance you can post a different link to this file? Any help is greatly appreciated!

I may have a copy of the files needed to do the fast/easy unbrick method shown elsewhere in the general forum. Don't know if it will help, but I'll check when I get home tonight and maybe put it on dropbox.
Sent while mobile using Tapatalk.

fxwrangler said:
Hey. Im Having the same problem as the last guy ..Unfortunately the links are now bad since the Feds busted megaupload..Any chance you can post a different link to this file? Any help is greatly appreciated!
Click to expand...
Click to collapse
That link goes to multiupload, it can be downloaded from there use fileserve or another link on multiupload.

I have established all that info actually I have the file Flash Verizon DROID 3 OTA 5.6.890 to phone_psouza4.rar But that is what brought me to that state. I pretty well know that I bricked by not properly removing the old bootstrap before flashing the SAFE one for CM9 ICS the feds are taking out multiupload, but all the secondary links are dead. I can Drop box any files I have, they might help some people with different soft bricks but I'm worried about my phone cause I use psouza's many times and always the same result. I also tried flashing his firmware with RSD 5.5 and .5.4 didn't work still it constantly gets failed boot. I ALSO tried this file all those ways, VRZ_XT862_5.5.1_84_D3G-55_1FF_01 which did not work. I haven't attempted any Fast boot methods or linux, (because my linux machine is currently crashed)... I think that last file was the Verizon 5.5.959, and I read somewhere you couldn't go backwards if you were already at, Verizon 5.6.890 So does ANYONE please have that file, or maybe know if I'm doing something wrong?
edit : whenever i use rsd it never completes always failed at random point in the process... But I read somewhere that a guy edited hxml file or something to jump back and try to flash only certain sections of the phone. Can anyone give me any pointers on that? keeps giving size rturned by phone error

Let me just get this straight; you didn't try the fast/easy unbrick method wherein you use fastboot and Windows cmd line tool to flash to stock? If you did, never mind me lol. If you haven't, it's great and I used Windows to get mine back to stock.
I am ready to share those files via PM (dropbox link) if any one needs em.
Sent while mobile using Tapatalk.

protechcertifiedrepair said:
I have established all that info actually I have the file Flash Verizon DROID 3 OTA 5.6.890 to phone_psouza4.rar But that is what brought me to that state. I pretty well know that I bricked by not properly removing the old bootstrap before flashing the SAFE one for CM9 ICS the feds are taking out multiupload, but all the secondary links are dead. I can Drop box any files I have, they might help some people with different soft bricks but I'm worried about my phone cause I use psouza's many times and always the same result. I also tried flashing his firmware with RSD 5.5 and .5.4 didn't work still it constantly gets failed boot. I ALSO tried this file all those ways, VRZ_XT862_5.5.1_84_D3G-55_1FF_01 which did not work. I haven't attempted any Fast boot methods or linux, (because my linux machine is currently crashed)... I think that last file was the Verizon 5.5.959, and I read somewhere you couldn't go backwards if you were already at, Verizon 5.6.890 So does ANYONE please have that file, or maybe know if I'm doing something wrong?
edit : whenever i use rsd it never completes always failed at random point in the process... But I read somewhere that a guy edited hxml file or something to jump back and try to flash only certain sections of the phone. Can anyone give me any pointers on that? keeps giving size rturned by phone error
Click to expand...
Click to collapse
There is a moto-fasboot for windows, I would suggest trying it, looking in the xml files will tell you what order to fastboot flash in. Also note, if I'm not mistaken, that the verizon OTAs are named after the system version they are meant to be applied to, as opposed to the system version they upgrade you to.
Sent from my XT860 using xda premium

mmsomekid said:
My buddy made a torrent mirror of the sbf for anyone still looking for it. You can get it here
Click to expand...
Click to collapse
got this off the recovery thread.

I have used quick unbrick over a dozen times for various brick causes. It's never failed me and I'm a huge fan. Especially because it's faster than RSD. Make sure you have the latest drivers installed and stock USB cable as well. This changes a lot.

BenSWoodruff said:
Let me just get this straight; you didn't try the fast/easy unbrick method wherein you use fastboot and Windows cmd line tool to flash to stock? If you did, never mind me lol. If you haven't, it's great and I used Windows to get mine back to stock.
I am ready to share those files via PM (dropbox link) if any one needs em.
Sent while mobile using Tapatalk.
Click to expand...
Click to collapse
NO, I DID use the quick unbrick and the RSD lite methods. But no I did not yet try the Fast boot CMD style I will try tonight or tomorow, and that is only half my problem the other was getting those files for the stock, I only have pouzas version extracted and ran through rsd. So I will download files in the TOrrent mentioned post and try that. Thanks guys for the help I got mad donations for anyone who gives me th right poimter I need to fix my phone.

protechcertifiedrepair said:
NO, I DID use the quick unbrick and the RSD lite methods. But no I did not yet try the Fast boot CMD style I will try tonight or tomorow, and that is only half my problem the other was getting those files for the stock, I only have pouzas version extracted and ran through rsd. So I will download files in the TOrrent mentioned post and try that. Thanks guys for the help I got mad donations for anyone who gives me th right poimter I need to fix my phone.
Click to expand...
Click to collapse
The quick unbrick method (which I believe is mirrored in that torrent) is the CMD style unbricking method. I'm using it for the second time today, actually!
Here's a video I made recently showing how it works and whatnot.
http://www.youtube.com/watch?v=pcne9tFtBxY

protechcertifiedrepair said:
NO, I DID use the quick unbrick and the RSD lite methods. But no I did not yet try the Fast boot CMD style I will try tonight or tomorow, and that is only half my problem the other was getting those files for the stock, I only have pouzas version extracted and ran through rsd. So I will download files in the TOrrent mentioned post and try that. Thanks guys for the help I got mad donations for anyone who gives me th right poimter I need to fix my phone.
Click to expand...
Click to collapse
I believe it's a script you double click on after unzipping the file to your PC. If you have any trouble downloading, I have a copy of the .zip I can share. You connect via usb, power up while holding m button on D3 keyboard and select AP Fastboot mode, then run the script.
Just read the OP carefully and you should be fine ;-)
Good luck.

Just my input on this "One Click " ...it does work..I tried for three days and when I got to the "sending", it wouldnt go any further..So I finally tried it on another computer & Shazaam..It Worked!!..Thanks fot all the help from this forum!!
Sent from my DROID3 using Tapatalk

As far as I know, if the fast/easy unbrick method isn't working, it could very well be a usb/driver issue. The phone, once connected to the PC, should show up in device manager (windows). If it isn't connecting properly, it should say 'waiting for device.' If it is connected but doesn't go all the way through the process, trying a different/newer PC, stock usb cable, or updating drivers may be necessary.
Maybe you can describe what is the exact point that you run into a road block and we can see better the cause of the issue. I'll keep reading around to see if I can understand it better.
Sent while mobile using Tapatalk.

BenSWoodruff said:
As far as I know, if the fast/easy unbrick method isn't working, it could very well be a usb/driver issue. The phone, once connected to the PC, should show up in device manager (windows). If it isn't connecting properly, it should say 'waiting for device.' If it is connected but doesn't go all the way through the process, trying a different/newer PC, stock usb cable, or updating drivers may be necessary.
Maybe you can describe what is the exact point that you run into a road block and we can see better the cause of the issue. I'll keep reading around to see if I can understand it better.
Sent while mobile using Tapatalk.
Click to expand...
Click to collapse
OP, have you checked your drivers to see if they're the most recent? I, too, have been mentioning them for days with no acknowledgement of it. I feel like this is the only thing left other than a very strange device.

I have read over and over again for hours and I cant find a solution. I tried to used RDS Lite with Droid_3_SBF_5.6.890 for my XT860 and got the multiboot issue. I never could pass from 1/18
At that time I was still able to boot to application pressing m and selecting Normal. Then I read this forums and tried the fast/easy unbrick method.
I didnt have any problem to connect but some files were OK and someothers failed then I received a new error:
Invalid CG OTV: Invalid SP Data
Invalid CG HAB: CG: System Status: 0x0035
and cannot longer enter into the application using the m button.
The "easy" methods shows:
**
** Now flashing the Verizon DROID 3 OTA 5.6.890 updated system to your phone...
**
erasing 'userdata'... OKAY [ 0.014s]
erasing 'cache'... OKAY [ 0.039s]
sending 'recovery' (9216 KB)... OKAY [ 1.042s]
writing 'recovery'... INFOPreflash validation failure
FAILED (remote: )
sending 'boot' (8192 KB)... OKAY [ 1.183s]
writing 'boot'... INFOPreflash validation failure
FAILED (remote: )
sending 'devtree' (512 KB)... OKAY [ 0.334s]
writing 'devtree'... INFOPreflash validation failure
FAILED (remote: )
sending 'logo.bin' (854 KB)... OKAY [ 0.363s]
writing 'logo.bin'... OKAY [ 0.391s]
sending 'preinstall' (262144 KB)... OKAY [ 25.000s]
writing 'preinstall'... OKAY [ 22.900s]
sending 'preinstall' (229376 KB)... OKAY [ 21.985s]
writing 'preinstall'... OKAY [ 20.234s]
sending 'cdrom' (12032 KB)... OKAY [ 1.319s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
sending 'radio' (14368 KB)... OKAY [ 1.689s]
writing 'radio'... OKAY [ 1.447s]
sending 'system' (262144 KB)... OKAY [ 26.719s]
writing 'system'... OKAY [ 23.026s]
sending 'system' (175872 KB)... OKAY [ 17.813s]
writing 'system'... OKAY [ 15.383s]
rebooting...
**
** Done!
**
Press any key to continue . . .
I am getting out of ideas. PLEASE HELP ME!!!!
SOLVED!!! I was using the wrong SBF. Now it is working using RDS Lite 5.5
Here is the list of SBF for many motorola devices. Jus click in Milestone 3 Firmware at the end of the 1st post:
http://forum.xda-developers.com/showthread.php?t=1370721
I am so Happy

protechcertifiedrepair said:
Hi, I am a professional phone repair guy and I am very familiar with adb, rooting, android OS ect. So I will probably only need to be pointed in the right direction... I have searched 3 days for a solution and I know that I haven't tried EVERY possible recovery solution... But the links on the SBF Droid 3 flash files are "DEAD" and I can't find them...
So I used psouza4's one click and got this...
AP Fastboot Flash Mode (S) (Boot Failure)
0A.53
Battery OK
OK to Program
ConectUSB
Data Cable
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CG HAB (CG: system, status: 0X0035 )
Invalid CG OTV (CG: system)
I know I most likely just need an SBF file for whichever STOCK firmware I was on, not sure which so if someone can link me the file or at least point me in the right direction to restore this phone. (Had it 2 days and soft bricked)
Thanks in Advance
Click to expand...
Click to collapse
If your a professional phone repair guy y are you asking for help? You may be phone repair guy but not a professional because a professional will have done it with out asking for are help but I do think if you call your self a professional then you must be very good at it is all but not as good as a professional
Sent from my XT862 using XDA

leerpsp said:
If your a professional phone repair guy y are you asking for help? You may be phone repair guy but not a professional because a professional will have done it with out asking for are help but I do think if you call your self a professional then you must be very good at it is all but not as good as a professional
Sent from my XT862 using XDA
Click to expand...
Click to collapse
Not trying to start something, but he could be a phone repair person for a different company (not Motorola), he may usually deal with phones that have unlocked bootloaders, who knows.
In the workplace-and life in general-it is an admiral trait to ask for help rather than just "wing it". Even company heads ask for help. If he made a mistake, he could end up with a few hundred dollar paper weight.
Sent from my DROID3 using xda premium

Related

[Q] Unbrick Moto X

Hello!
This is my first post... then sorry if i mest something,
well im from mexico (cancun)
and i have a moto X but now is brick,
im sure hard brick not vibrated not on not recovery,
i was reading in this forum possibilities about this issue,
i have the "QHUSB_DLOAD"
How i can turn alive my phone?
Is it completely dead?
someone can help me? i will express gratitude and someone show me how i can repair... of curse i will pay them. thanks alot
AT&T 32 gb
The first thing to do on xda is always do a search or browse through the different sections for your phone.
http://forum.xda-developers.com/showthread.php?t=2629057
Sent from my N5 cell phone telephone....
kj2112 said:
The first thing to do on xda is always do a search or browse through the different sections for your phone.
http://forum.xda-developers.com/showthread.php?t=2629057
Sent from my N5 cell phone telephone....
Click to expand...
Click to collapse
well, i was doing that any way i can put my phone in recovery but not success with flashing to come alive
davcastroruiz said:
well, i was doing that any way i can put my phone in recovery but not success with flashing to come alive
Click to expand...
Click to collapse
we need more info why can't you flash it back to stock what error's are you getting. more then likely you are trying to flash the wrong version of android and that is why it wont flash.
so we need
1. what error's you got
2. what model or carrier your phone is with
preflash validation failed
dray_jr said:
we need more info why can't you flash it back to stock what error's are you getting. more then likely you are trying to flash the wrong version of android and that is why it wont flash.
so we need
1. what error's you got
2. what model or carrier your phone is with
Click to expand...
Click to collapse
Thank u for reply
Ox56 failed to hab check for boot
Preflash validation failed for boot
" For" recovery
PIV block validation forma system failed
Invalid piv image: system
Also i try with att's fimwares
But 4.4.2 is not yet
I almost forget it before i see a conde
Partition (boot) security versión downgraded
I guess i need at't 4.4.2 right?
Or why i can do nothing ? With vwz or anything else like retails in other motorola..
try this: http://forum.xda-developers.com/moto-x/development/script-moto-x-restore-utility-windows-t2597625
helped me
ericizzy1 said:
try this: http://forum.xda-developers.com/moto-x/development/script-moto-x-restore-utility-windows-t2597625
helped me
Click to expand...
Click to collapse
thanks ericizzy but seems like there is not link for windows man :C only mac and linux i tried on ubuntu system 13.14 but doesnt work do u have the exe, for windows?? could u upload to a server ?? thank you!
davcastroruiz said:
thanks ericizzy but seems like there is not link for windows man :C only mac and linux i tried on ubuntu system 13.14 but doesnt work do u have the exe, for windows?? could u upload to a server ?? thank you!
Click to expand...
Click to collapse
http://rootjunkysdl.com/?device=Moto X
ericizzy1 said:
http://rootjunkysdl.com/?device=Moto X
Click to expand...
Click to collapse
doesnt work for me sir :/
failed also in piv and recovery and boot
anyway i guess i have to be patient and wait for the sw upgrade of at&t
thank you any way for the link i have now moto x restore utility

[Q] Dead in the water, unless a miracle comes along...

Well I decided to sell this Atrix HD I just recently acquired and of course because I have no luck at all not even 5 mins after posting the ad on craigslist I ended up potentially bricking it, sadly. I've spent the better part of the past 2 hours scouring threads and posts hoping for a solution but so far I've had no luck so I'll take this last step and ask if anyone might have any advice or solutions. Here's the situation:
- Atrix HD, originally with JB 4.1.1 on it (pre-final AT&T update, mind you)
- rooted with motochopper then bootloader unlocked with motopocalypse, no issues over the past 10 days or so that I've owned this AHD at all)
- was running CM11 nightly without issues (installed with CWM 6.0.5.1, had flashed several ROMs over the past 10 days including CM12, the Mexican retail ROM, and then back to pure AT&T several times, actually
- about 2 hours before making this post I listed it on craigslist and then used Myth Tools to go back to stock (stock being MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27)
- no issues with the flashing process, booted up as expected, worked fine for a few mins then I connected to Wi-Fi and grabbed the final JB update released by AT&T, when it finished I clicked "Install now" to do the reboot and install it
- rebooted into the install and seemed to finish ok, didn't glitch or error out in any respect
- somewhere in the middle of the final reboot after the upgrade it crapped out and then went into the bootloader loop to AP Fastboot (S) mode
- got the following error (which is known to a few other members in the past based on postings I located):
Code:
(typical info at the top of the screen)
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup:0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
usb connected
As stated, this AHD was bootloader unlocked without any issues but for whatever is now showing as LOCKED. The thing that concerns me is that if I use fastboot devices it doesn't show the proper info as it used to (the typical TA00etcetcetc model number) - it's showing an 8 digit alphanumeric number I've never seen before so that's a big red flag right there.
I've attempted every process I can locate so far and had zero success at all - only one single fastboot command gives me an OKAY message and that's fastboot oem fb_mode_clear. Every other fastboot command offers up a FAILED (remote failure) error, all of them and I've tried pretty much all of them.
I cannot flash anything to the AHD it seems so I'm guessing that means it's 100% "bricked" in the sense that it's powering up, can be seen from the PC/laptop using fastboot devices, but that's it just not actually there at all for whatever reason.
I've attempted to use 2 different laptops, 1 desktop, multiple various USB ports, cables, you name it I'm pretty confident I've attempted to use it in some respect and still nada, zip, zilch, nothing has come from my efforts. If it's totally bricked then so be it, I'll live, but I keep holding out hope that something I missed will help but it's starting to look like this is beating a dead horse now.
I've attempted using RSD Lite to push the Mexican retail ROM to it (with the edited xml file), the AT&T retail ROM, etc - I can't locate any FXZ files at all so that might still be an option but I simply cannot find any of them if they exist.
So apparently for whatever reason the final JB update pooched this device (even in spite of it not doing it in the past week when I rolled back to stock at least 3 prior times in testing). I'm suspecting - but can't say for certain - that potentially the CWM 6.0.5.1 which I just installed like 2 days ago could be the culprit here; previously using 6.0.4.4 I had no issues whatsoever and that is the only variable that's changed in my flashing process that I can recall.
Anyway, that pretty much covers the situation - if anyone has any advice that might bring this AHD back to life I'm definitely interested in hearing it. I don't have JTAG hardware, don't have a factory cable (if one is required), don't have anyone in the area that does that I'm aware of, etc. Basically if I can't get it resolved on my own then it's a dead device I'll toss in a drawer till that miracle comes along...
Thanks for reading, regardless.
br0adband said:
Well I decided to sell this Atrix HD I just recently acquired and of course because I have no luck at all not even 5 mins after posting the ad on craigslist I ended up potentially bricking it, sadly. I've spent the better part of the past 2 hours scouring threads and posts hoping for a solution but so far I've had no luck so I'll take this last step and ask if anyone might have any advice or solutions. Here's the situation:
- Atrix HD, originally with JB 4.1.1 on it (pre-final AT&T update, mind you)
- rooted with motochopper then bootloader unlocked with motopocalypse, no issues over the past 10 days or so that I've owned this AHD at all)
- was running CM11 nightly without issues (installed with CWM 6.0.5.1, had flashed several ROMs over the past 10 days including CM12, the Mexican retail ROM, and then back to pure AT&T several times, actually
- about 2 hours before making this post I listed it on craigslist and then used Myth Tools to go back to stock (stock being MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27)
- no issues with the flashing process, booted up as expected, worked fine for a few mins then I connected to Wi-Fi and grabbed the final JB update released by AT&T, when it finished I clicked "Install now" to do the reboot and install it
- rebooted into the install and seemed to finish ok, didn't glitch or error out in any respect
- somewhere in the middle of the final reboot after the upgrade it crapped out and then went into the bootloader loop to AP Fastboot (S) mode
- got the following error (which is known to a few other members in the past based on postings I located):
Code:
(typical info at the top of the screen)
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup:0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
usb connected
As stated, this AHD was bootloader unlocked without any issues but for whatever is now showing as LOCKED. The thing that concerns me is that if I use fastboot devices it doesn't show the proper info as it used to (the typical TA00etcetcetc model number) - it's showing an 8 digit alphanumeric number I've never seen before so that's a big red flag right there.
I've attempted every process I can locate so far and had zero success at all - only one single fastboot command gives me an OKAY message and that's fastboot oem fb_mode_clear. Every other fastboot command offers up a FAILED (remote failure) error, all of them and I've tried pretty much all of them.
I cannot flash anything to the AHD it seems so I'm guessing that means it's 100% "bricked" in the sense that it's powering up, can be seen from the PC/laptop using fastboot devices, but that's it just not actually there at all for whatever reason.
I've attempted to use 2 different laptops, 1 desktop, multiple various USB ports, cables, you name it I'm pretty confident I've attempted to use it in some respect and still nada, zip, zilch, nothing has come from my efforts. If it's totally bricked then so be it, I'll live, but I keep holding out hope that something I missed will help but it's starting to look like this is beating a dead horse now.
I've attempted using RSD Lite to push the Mexican retail ROM to it (with the edited xml file), the AT&T retail ROM, etc - I can't locate any FXZ files at all so that might still be an option but I simply cannot find any of them if they exist.
So apparently for whatever reason the final JB update pooched this device (even in spite of it not doing it in the past week when I rolled back to stock at least 3 prior times in testing). I'm suspecting - but can't say for certain - that potentially the CWM 6.0.5.1 which I just installed like 2 days ago could be the culprit here; previously using 6.0.4.4 I had no issues whatsoever and that is the only variable that's changed in my flashing process that I can recall.
Anyway, that pretty much covers the situation - if anyone has any advice that might bring this AHD back to life I'm definitely interested in hearing it. I don't have JTAG hardware, don't have a factory cable (if one is required), don't have anyone in the area that does that I'm aware of, etc. Basically if I can't get it resolved on my own then it's a dead device I'll toss in a drawer till that miracle comes along...
Thanks for reading, regardless.
Click to expand...
Click to collapse
Did you edit the script when flashing the stock JB with Mythtools or RSD lite?
Sent from my ATRIX-RAZR HD using XDA Free mobile app
Yep, it even states that in my post:
I've attempted using RSD Lite to push the Mexican retail ROM to it (with the edited xml file), the AT&T retail ROM, etc - I can't locate any FXZ files at all so that might still be an option but I simply cannot find any of them if they exist.
Click to expand...
Click to collapse
Nothing will flash to the device which is the biggest issue of all; if I could flash the gpt_main0.bin file I'd be getting somewhere (since as I understand it that sets the partition layout for the partition img's that will follow in the flashing process).
As stated, the only thing that works in terms of a fastboot command is fb_mode_clear which gets an OKAY response (although fb_mode_set does too, actually). But no other fastboot commands are functional - I tried fastboot -w and get:
Code:
D:\motopocalypse\motopocalypse>fastboot -w
erasing 'userdata'...
Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.140s
so then I try:
Code:
D:\motopocalypse\motopocalypse>fastboot erase userdata
erasing 'userdata'...
Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.141s
and so on and so forth. No attempts to erase data nor write it in any manner are successful. RSD Lite basically is useless as well (pic attached below). Since I can't write any data to the device at all then as I've said, it's dead in the water unless a miracle comes along. Was looking at eBay in the hopes of finding a busted/broken AHD (damaged glass, etc) and swapping the mobo from that one back into my housing but they're a bit expensive for busted ones at the moment, guess I'll just keep hoping for that miracle.
I've never used a JTAG or factory cable on any devices I've ever owned but I have to wonder if such a contraption might get this back to a working state. Suppose I'll need to do some research into things - I tried to contact Motorola about it but of course since the AHD is so old now and I'm not the original owner, even though I registered the device in my name they won't honor the warranty without a proof of purchase (meaning the retail one years ago when it was new).
Out of over 100 smartphones and other devices I've owned over the decades this is the first time one's actually up and died on me and go figure: it died when doing an OTA update on a clean stock ROM installation.
How ironic...
Have you tried this http://forum.xda-developers.com/showthread.php?t=2259661
Sent from my LG-D850 using XDA Free mobile app
bmatney said:
Have you tried this http://forum.xda-developers.com/showthread.php?t=2259661
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Yep, it's all the same basic process whether it's done scripted or manually, same result: as stated, nothing will flash to the AHD and kicks back the same error each time (partition errors). I have no idea what that damned OTA did but it totally wrecked the whole thing...
Even tried doing this under Linux - the issue isn't with fastboot or the builds, it's with the AHD itself because it's not writing anything I'm trying to flash to the device and I'm confident it's because the partition structure is pooched for whatever reason.
I'm still wondering about using a factory cable (will have to buy one off eBay I suppose) will make any difference at all, I just have no experience using them and if the phone isn't flashing/writing data to the device because the partitions are pooched, I can't imagine using a different albeit specific cable will make that much of a difference.
Bleh... I hate it when crap goes wrong, I really do.

FAILED (data transfer failure (Unknown error)) when trying to flash anything to phone

I have S-ON and a non-HK phone with an OS of 2.16.651 I believe. @Sloth tried to help me but to no success, so I'll try to see if anybody else can help me figure out the issue.
Basically, everything works up until I actually start to flash the phone. It gives me this error:
FAILED (data transfer failure (Unknown error))
There's a bit more to it, but that's mostly unrelated stuff (the command and blahblahblah).
I've tried 2 different computers and different ports on all of them. I don't have any other USB cables for my phone available, but this one works with my PS4 controllers finely so I'm guessing it should work fine.
If someone could help me and anyone else with my luck in the future, please answer. I don't want to have to resort to a store as I have no money and the store is quite far. Thanks!
EDIT: Something else to mention, there is no firmware on this device and only has an accessible bootloader and recovery. I currently have the bootlocker relocked. I had ViperOneM8, although uninstalled after realizing I had no access to WiFi (I ignored the disclaimer :c). I don't have a SIM card as this phone was given and I didn't buy it myself from any carrier, I have no service. Some other stuff to mention is that I verified the MD5 of the firmware and it was not corrupt, I had the proper working drivers as I checked if it found my device, and that's it.
F0rZ3r0 said:
I have S-ON and a non-HK phone with an OS of 2.16.651 I believe. @Sloth tried to help me but to no success, so I'll try to see if anybody else can help me figure out the issue.
Basically, everything works up until I actually start to flash the phone. It gives me this error:
FAILED (data transfer failure (Unknown error))
There's a bit more to it, but that's mostly unrelated stuff (the command and blahblahblah).
I've tried 2 different computers and different ports on all of them. I don't have any other USB cables for my phone available, but this one works with my PS4 controllers finely so I'm guessing it should work fine.
If someone could help me and anyone else with my luck in the future, please answer. I don't want to have to resort to a store as I have no money and the store is quite far. Thanks!
EDIT: Something else to mention, there is no firmware on this device and only has an accessible bootloader and recovery. I currently have the bootlocker relocked. I had ViperOneM8, although uninstalled after realizing I had no access to WiFi (I ignored the disclaimer :c). I don't have a SIM card as this phone was given and I didn't buy it myself from any carrier, I have no service. Some other stuff to mention is that I verified the MD5 of the firmware and it was not corrupt, I had the proper working drivers as I checked if it found my device, and that's it.
Click to expand...
Click to collapse
So no RUU works? Try using this fastboot version... simply unzip it and copy the files you want to flash into the resulting directory and run your commands from there.
https://www.androidfilehost.com/?fid=95784891001612150
dottat said:
So no RUU works? Try using this fastboot version... simply unzip it and copy the files you want to flash into the resulting directory and run your commands from there.
https://www.androidfilehost.com/?fid=95784891001612150
Click to expand...
Click to collapse
Erm, resulting directory?

Battery drain 10%/h and vibration not working

Hi everyone,
I tried to install the CM 13 in my moto X 2014, but I forgot to install Gapps before rebooting my phone. So I had to flash android 6.0 and try all over again. I dont´t know if my mistake in the procedure has something to do with the problems below.
I realized that my phone is not vibrating anymore and the battery drain has been drasticaly increased, like 10% per hour while in idle. When I use my phone (whatsapp, chrome etc) the battery drain seens to be like in idle (no apps running on background).
A full charge takes 4 hours with normal charger or 8 hours if connected to my computer.
I Tried android versions 4.4.4, 5.0, 5.1, 6.0, NX 10.1 and CM13. I don´t know what to do. Motorola assistance said the motherboard is the source of my problems just because i unlocked my bootloader.
Rodrigo_Codina said:
Hi everyone,
I tried to install the CM 13 in my moto X 2014, but I forgot to install Gapps before rebooting my phone. So I had to flash android 6.0 and try all over again. I dont´t know if my mistake in the procedure has something to do with the problems below.
I realized that my phone is not vibrating anymore and the battery drain has been drasticaly increased, like 10% per hour while in idle. When I use my phone (whatsapp, chrome etc) the battery drain seens to be like in idle (no apps running on background).
A full charge takes 4 hours with normal charger or 8 hours if connected to my computer.
I Tried android versions 4.4.4, 5.0, 5.1, 6.0, NX 10.1 and CM13. I don´t know what to do. Motorola assistance said the motherboard is the source of my problems just because i unlocked my bootloader.
Click to expand...
Click to collapse
What is currently installed on each of the phones partitions?
JnNn98 said:
What is currently installed on each of the phones partitions?
Click to expand...
Click to collapse
You mean the S.O. version?
I´ve flashed these firmwares via fastboot/RSD Lite 6.2.4.
mega.nz/#F!kd9WULBb!m_X_fQGJ6UnEOMJXzcv-Yw
Rodrigo_Codina said:
You mean the S.O. version?
I´ve flashed these firmwares via fastboot/RSD Lite 6.2.4.
mega.nz/#F!kd9WULBb!m_X_fQGJ6UnEOMJXzcv-Yw
Click to expand...
Click to collapse
I feel like it's possible that you downgraded the bootloader in the process, and that could be the only problem. In that case flash this to get stock, as it'll be the latest firmware.
http://www.filefactory.com/file/13ee8myr4sjh/VICTARA_RETBR_XT1097_6.0_MPE24.49-18_cid12_CFC.xml.zip
Use the instructions from this thread.
http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
Also check the cable you're using to charge the phone, with regards to the slow charging.
If there's still things wrong afterwards it is probably a hardware problem. Good luck.
JnNn98 said:
I feel like it's possible that you downgraded the bootloader in the process, and that could be the only problem. In that case flash this to get stock, as it'll be the latest firmware.
http://www.filefactory.com/file/13ee8myr4sjh/VICTARA_RETBR_XT1097_6.0_MPE24.49-18_cid12_CFC.xml.zip
Use the instructions from this thread.
http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
Also check the cable you're using to charge the phone, with regards to the slow charging.
If there's still things wrong afterwards it is probably a hardware problem. Good luck.
Click to expand...
Click to collapse
Sorry I did not reply you earlier, canaval holidays... back to real life today.
I tried what you suggested but without success.
When I try to execute "fastboot flash partition gpt.bin" it fails (I´m not at home right now and I don´t remember exactly the message I got), but all other commands runs like expected.
I saw this thread " forum.xda-developers.com/moto-x-2014/help/managed-to-screw-phone-bootloader-to-t3309241?nocache=1 ". It has a command that in the other you suggested has not.
"fastboot getvar max-sparse-size"
What is it for?
Rodrigo_Codina said:
Sorry I did not reply you earlier, canaval holidays... back to real life today.
I tried what you suggested but without success.
When I try to execute "fastboot flash partition gpt.bin" it fails (I´m not at home right now and I don´t remember exactly the message I got), but all other commands runs like expected.
I saw this thread " forum.xda-developers.com/moto-x-2014/help/managed-to-screw-phone-bootloader-to-t3309241?nocache=1 ". It has a command that in the other you suggested has not.
"fastboot getvar max-sparse-size"
What is it for?
Click to expand...
Click to collapse
The error for the flash partition may be a result of using fastboot and not motorola's own fastboot. I've attached a motorola fastboot in a zip, so you can try again using that fastboot file. The extra commands don't help with anything really because they do not affect the flashing of partitions.
The fastboot getvar command is literally "get variable", so in that case it would just return the maximum file size that can be flashed I believe, and in case you were wondering:
fastboot oem fb_mode_set - Makes the phone automatically reboot into bootloader mode.
fastboot oem fb_mode_clear - Just resets the above commands setting back to normal booting.
The message I mentioned when I execute the command "fastboot flash partition gpt.bin"
sending 'partition' <32KB>...
OKAY [ 0.030s]
writing 'partition'...
<bootloader> Preflash validation failed
FAILED <remote failure>
finished. total time: 0.130s
Nevermind... I was trying to flash an old gpt.bin.
I guess that's the end, I give up. I don't know what to do, nothing works.
I'm thinking of buying an used device with broken screen for 1/3 of the price of a new one (350 reais, almost 100 dollars), disassemble everything and assemble only the motherboard in my device.
I really appreciate your help but I guess I need the Blanckflash and I searched and no one has it because motorola did not released for us.

Moto X Dev Edition stuck in fastboot

I get this error on my moto x dev edition with verizon xt1060 in fastboot. i cant flash any images. i was told to use rsd lite but it doesnt detect my phone.
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
RandyThor said:
I get this error on my moto x dev edition with verizon xt1060 in fastboot. i cant flash any images. i was told to use rsd lite but it doesnt detect my phone.
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
Click to expand...
Click to collapse
Do you install Motorola drivers..?
Salik Iqbal said:
Do you install Motorola drivers..?
Click to expand...
Click to collapse
yes the newest drivers are installed. It shows up in device manager as "MOT Single ADB Interface". I can also detect it in fastboot, though most commands won't work.
i had a similar kind of problem on my ghost. Firmware crash, due to which phone was stuck at the bootloader. No recovery nor did any fastboot worked at that time. I referred this and this. It worked for me.
varunpilankar said:
i had a similar kind of problem on my ghost. Firmware crash, due to which phone was stuck at the bootloader. No recovery nor did any fastboot worked at that time. I referred this and this. It worked for me.
Click to expand...
Click to collapse
when following the second link steps i get stuck at step 8. Im not sure what he means by click on the device. does he mean the 'Mot Single ADB Interface' device? i clicked properties on that then i clicked update and i selected the folder where i kept the signed sys files. there was nothing about QHSUSB_DLOAD as it said in the tutorial though. anyway afterwards there was no port called Qualcomm HS-USB QDLoader 9008 so i couldn't get a portnumber to continue the process.
The other link you gave i assumed id go to Moto X BE\1_Repair_Boot (RSD Lite)\1060 and flash the gpt.bin and the motoboot.img but i got this error:
C:\Users\Jake\Desktop\New folder\Moto X BE\1_Repair_Boot (RSD Lite)\1060>mfastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.290s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.210s
C:\Users\Jake\Desktop\New folder\Moto X BE\1_Repair_Boot (RSD Lite)\1060>mfastboot flash motoboot motoboot.img
sending 'motoboot' (1604 KB)...
OKAY [ 0.420s]
writing 'motoboot'...
Motoboot: Unknown partition name
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.700s
I'm in basically the same situation with my XT1060 Developer Edition. Tried a long list of fixes, none has done the trick. All I have available is the fastboot menu. Phone won't boot into OS, won't go into recovery, hasn't accepted any flashes or erases. This happened because after downgrading to 4.4.4 I allowed an OTA update to 5.1. Phone rebooted and hasn't left the flashboot menu since. I, too, am looking for any help I can get on the matter.
Just like you, I tried that trick involving the fancy drivers, but my phone shows up as "Mot Single ADB Interface" in device manager, so that fix doesn't apply. If my phone reported as QHSUSB_DLOAD in device manager, it would be a different story. Though my phone was rooted and unlocked before downgrading to 4.4.4, at this point it's locked (happened without my knowledge), which I believe is why I can't reflash a recovery image.
It seems pretty clear to me that the phone has either an absent or corrupted partition scheme, as gpt.bin won't flash AND my phone doesn't acknowledge the existence of partitions. I suspect my phone began writing the 5.1 OTA update before erroring out, thus leaving me in a limbo mode halfway between 5.1 and 4.4.4. If anyone out there has experience with this seemingly unique brick situation, I would appreciate it. OP, good luck with your phone.
OrlandoAlex said:
I'm in basically the same situation with my XT1060 Developer Edition. Tried a long list of fixes, none has done the trick. All I have available is the fastboot menu. Phone won't boot into OS, won't go into recovery, hasn't accepted any flashes or erases. This happened because after downgrading to 4.4.4 I allowed an OTA update to 5.1. Phone rebooted and hasn't left the flashboot menu since. I, too, am looking for any help I can get on the matter.
Just like you, I tried that trick involving the fancy drivers, but my phone shows up as "Mot Single ADB Interface" in device manager, so that fix doesn't apply. If my phone reported as QHSUSB_DLOAD in device manager, it would be a different story. Though my phone was rooted and unlocked before downgrading to 4.4.4, at this point it's locked (happened without my knowledge), which I believe is why I can't reflash a recovery image.
It seems pretty clear to me that the phone has either an absent or corrupted partition scheme, as gpt.bin won't flash AND my phone doesn't acknowledge the existence of partitions. I suspect my phone began writing the 5.1 OTA update before erroring out, thus leaving me in a limbo mode halfway between 5.1 and 4.4.4. If anyone out there has experience with this seemingly unique brick situation, I would appreciate it. OP, good luck with your phone.
Click to expand...
Click to collapse
For both of you.. @RandyThor and @OrlandoAlex check thread after 12hrs.. i have something for you which may hopefully fix thay issue.
I'm in the same boat. At least I've finally learned why I always refuse OTA updates (until now it hadn't really dawned on me that I had to blankflash because I downgraded after having updated official firmware).
A solution would be much appreciated, as nothing I've done has worked to this point. I'll read more on here to see whether someone has already posted a solution, and I should be able to check back on this thread in a couple of hours.
EDIT:
It does not look like there is a common solution, from what I can tell in the Q&A. Will search elsewhere next.
PiArc said:
I'm in the same boat. At least I've finally learned why I always refuse OTA updates (until now it hadn't really dawned on me that I had to blankflash because I downgraded after having updated official firmware).
A solution would be much appreciated, as nothing I've done has worked to this point. I'll read more on here to see whether someone has already posted a solution, and I should be able to check back on this thread in a couple of hours.
EDIT:
It does not look like there is a common solution, from what I can tell in the Q&A. Will search elsewhere next.
Click to expand...
Click to collapse
Was busy and forgot that sorry, i put alarm for that now will update this thread in some hours.
Salik Iqbal said:
Was busy and forgot that sorry, i put alarm for that now will update this thread in some hours.
Click to expand...
Click to collapse
No worries. Whenever you get the chance.
RandyThor said:
No worries. Whenever you get the chance.
Click to expand...
Click to collapse
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
@Salik Iqbal, you've done it! Can you tell me exactly why that worked? Which version of the bootloader was that? Also, THANK YOU!
PiArc said:
@Salik Iqbal, you've done it! Can you tell me exactly why that worked? Which version of the bootloader was that? Also, THANK YOU!
Click to expand...
Click to collapse
It was from att latest firmware gpt and aboot.
Salik Iqbal said:
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Click to expand...
Click to collapse
you are the GOAT my friend
Salik Iqbal said:
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Click to expand...
Click to collapse
One last thing. The phone is working fine now but recovery doesn't seem to work. I've tried reflashing it and it works but when i enter recovery i just get that dead android guy with the error symbol. Any ideas?
RandyThor said:
One last thing. The phone is working fine now but recovery doesn't seem to work. I've tried reflashing it and it works but when i enter recovery i just get that dead android guy with the error symbol. Any ideas?
Click to expand...
Click to collapse
Oh nevermind i apologize. My recovery was working fine i forgot i have to hold vol up and tap power to get to the recovery options...
Anyway thanks again you're a life saver!!!!!
RandyThor said:
Oh nevermind i apologize. My recovery was working fine i forgot i have to hold vol up and tap power to get to the recovery options...
Anyway thanks again you're a life saver!!!!!
Click to expand...
Click to collapse
So lets close the thread by requesting moderator..
Salik Iqbal said:
So lets close the thread by requesting moderator..
Click to expand...
Click to collapse
do i have to do that lol? im a noob

Categories

Resources