Related
I made the mistake of flash this file MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-AHD MX.xml.zip in my AHD AT&T on JB 4.1.1, now when I try to flash, I get this error:
RSDLite: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL.
ATRIX HD: security downgraded version
gpt_main version update failed
preflash validation failed for GPT.
any ideas to fix this?
PD. Excuse my english
How is there a Mexican firmware for this phone??? I haven't seen this phone available in Mexico...
3z3-8917 said:
I made the mistake of flash this file MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-AHD MX.xml.zip in my AHD AT&T on JB 4.1.1, now when I try to flash, I get this error:
RSDLite: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL.
ATRIX HD: security downgraded version
gpt_main version update failed
preflash validation failed for GPT.
any ideas to fix this?
PD. Excuse my english
Click to expand...
Click to collapse
+1
joel_sinbad said:
How is there a Mexican firmware for this phone??? I haven't seen this phone available in Mexico...
Click to expand...
Click to collapse
Yes the mexican firmware is avaliable for dowload in sbf.droid-developers, but it's but it's no compatible with AHD AT&T.
I lost the signal constantly in my AHD AT&T 4.1.1 stock JB, for that reason I flashing mexican firmware for fix this, but I brick my phone, not is posible reflashing MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip, I get this error en RDS: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL
3z3-8917 said:
Yes the mexican firmware is avaliable for dowload in sbf.droid-developers, but it's but it's no compatible with AHD AT&T.
I lost the signal constantly in my AHD AT&T 4.1.1 stock JB, for that reason I flashing mexican firmware for fix this, but I brick my phone, not is posible reflashing MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip, I get this error en RDS: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL
Click to expand...
Click to collapse
I learned YEARS ago never to flash an sfb\fastboot\odin\whatever if its not made specifically for your device+OS+carrier until the super smarts have determined if the signatures\values are compatible (or wait until a post like this shows up ). Motorola's notorious for setting up sbf's in a way that will brick you, prevent you from ever going back to stock, and\or downgrading. Knowing that, I made a rom from MR instead of flashing the fastboot.
ATRIX HD: security downgraded version -- that line worries me the most, especially if that's what it says if you're trying to flash AT&T now -- It could mean that MR has a higher CG value than AT&T. You'll never be able to install the AT&T fastboot again if that ends up being the case -- you've blown an efuse.
I'm gonna need some more details: Did the MR flash fully finish the first time used? If it fully finished and didn't boot or loops, do a factory reset in the stock reocovery. You could also try to unlock the bootloader (worth a shot at any rate) -- seems like you still have fastboot access so its at least worth trying -- it would be great if MR is the secret fastboot that unlocks us (I mean, the rom itself has no entitlement checking whatsoever, maybe its bootloader doesn't either...)
.
Can you still access SS or does it boot directly into fastboot\stock recovery? . If fastboot only, try flashing just the boot.img from the fastboot (probably won't work if an efuse has been blown). If you still have SS then we can put the boot.img in a zip and flash that -- its how we safely tested Defy sbf's without blowing an efuse.
After trying all of the above and if none of them work you should attempt flashing the Bell JB fasboot as a last ditch effort.
loading into fastboot only with error "flash failure"
marshok said:
loading into fastboot only with error "flash failure"
Click to expand...
Click to collapse
I'm not really sure what to tell you. You could try flashing just AT&T boot.img and devtree....Maybe make a hybrid fastboot, replace what fails during the AT&T flash with files from the MR fastboot (and modify the xml accordingly). Since it seems you're using the MR fastboot menu it, trying the unlock command is worth a shot.
All my other suggestions involve trying to connect directly to the nand and manually dd in the mbr and such -- I've never even tried connecting to my phone like that, so you'll have to search for those methods on your own, sorry. You'll also be diving in to full on brick territory too. You're just semi bricked, so you can still get lucky if you don't change that.
There is still hope (maybe) -- Apparently 4.2 is in testing and a fastboot should pop up for it before or after it's released. If its like every other major sbf\fastboot release I've seen it should have higher signatures\cg values and could possibly be a fix for you. That's all an assumption, but its based on credible rumor (a Mattlgroff post) and Motorola's past actions. The point is -- You still have access to fastboot, don't do anything to screw that up because your needed fix might not be available yet.
Or you could send in your phone for warranty; check Motorola's website to see if your still covered under factory warranty -- I am and my phone is a 99 cent refurbished model -- I still have 11 months left You get 12-24 months coverage when you register (length depends on New or Refurb). I was truthful on my Purchase Date, but I suppose you could lie and say you just recently bought it and it quit working when you started to upgrade it.
Did the MR flash fully finish the first time used?
Click to expand...
Click to collapse
no the flashing not completed, I got the error just flash boot.img
You could also try to unlock the bootloader (worth a shot at any rate) -- seems like you still have fastboot access so its at least worth trying -- it would be great if MR is the secret fastboot that unlocks us (I mean, the rom itself has no entitlement checking whatsoever, maybe its bootloader doesn't either...)
Click to expand...
Click to collapse
how I can do this? when my AHD is briked
Can you still access SS or does it boot directly into fastboot\stock recovery? . If fastboot only, try flashing just the boot.img from the fastboot (probably won't work if an efuse has been blown). If you still have SS then we can put the boot.img in a zip and flash that -- its how we safely tested Defy sbf's without blowing an efuse.
Click to expand...
Click to collapse
if boot directly into fastboot and I have acces stock recovery
After trying all of the above and if none of them work you should attempt flashing the Bell JB fasboot as a last ditch effort.
Click to expand...
Click to collapse
I try flash Bell JB fasboot and I get the same error
thanks for your help skeevy420
PD. Excuse my english
del
3z3-8917
How do you help skeevy420?
you have restored your phone after flashing on MB886_niimx-user-4.1.2-9.8.2Q-50_MB886?
In the same boat
Hey guys I'm in the same boat. I rooted my Atrix HD and was happy until I installed busy box 9.2, which managed to overwrite /system/bin and I don't know what else I could no longer mount/remount, change w/r in root, use the ls or many other commands and wifi, mobile data, bluetooth, or OS factory reset all gone.
I should have made a copy of my system before doing anything else but I went ahead and used the boot menu recovery, which didn't do anything to help the problem.
I then flashed the MR rom with RSD Light in an attempt to recovery my phone, it was 4.1.2 and seemed like a good (hindsight horrible) idea at the time.
Now I can fastboot flash recovery images from att JB but it does no good because the boot partition fails. The RSD Light MR boot flash failed but somehow the security version stuck, and the Bell 4.1.2, Att 4.1.1, and 7.7.1Q-144, roms boot.img all return Partition (boot) Security Version Downgraded. If anyone knows a way around this please let me know.
It seems kind of tragic that Dan's bootloader unlocking came out, pretty much the day after I got stuck in this locked bootloader loop
You have to use a special xml, unzip your stock-rom replace the old xml with this one: for ICS and this one for JB.
Then try to flash it again with https://www.box.com/s/cmoz84iachug77tghdlo version of rsd lite. Make sure you have these latest drivers.
3z3-8917 said:
Yes the mexican firmware is avaliable for dowload in sbf.droid-developers, but it's but it's no compatible with AHD AT&T.
I lost the signal constantly in my AHD AT&T 4.1.1 stock JB, for that reason I flashing mexican firmware for fix this, but I brick my phone, not is posible reflashing MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip, I get this error en RDS: Failed flashing process. 1/23 flash partion \ \ gpt_main0.bin - Phone returned FAIL
Click to expand...
Click to collapse
it can fix?????? i did the same flash at my atrix hd
rorrito said:
it can fix?????? i did the same flash at my atrix hd
Click to expand...
Click to collapse
for the moment it's not possible, wait bootloader unlock tool for AHD briked....
Codex01 said:
You have to use a special xml, unzip your stock-rom replace the old xml with this one: for ICS and this one for
JB
Then try to flash it again with this version of rsd lite. Make sure you have these latest drivers.
Click to expand...
Click to collapse
Ok downloaded the JB you linked and upgraded from RSD Light 6.1.4 to 6.1.5, I edited the XML to remove getvar, and ran RSD Light but it still fails on step 1.
"Failed Flashing Process 1/23 "gpt_main0.bin -> Phone returned FAIL."
On the Phone "preflash validation failed for gpt_main0.bin"
The only stock rom that made it past step 1 has been the MR that bricked my phone, so I replaced the system.img, boot.img, and recovery.img of the MR with the JB 4.1.1 you linked but it still fails at step 15, flashing boot.img. Preflash validation falure
BRICK AHD
Exactly same situation here, Flashing Mexican Firmware.
Now i got Partition (Boot) Security Version Downgraded
Hope it can be fixed:crying:
fix fail on part 1 rsd
use the stickyboot fix from general got it from skeevydude it works, try using mythtools after!
ickysjazz said:
Exactly same situation here, Flashing Mexican Firmware.
Now i got Partition (Boot) Security Version Downgraded
Hope it can be fixed:crying:
Click to expand...
Click to collapse
Shame on me :S
Well, I just bricked an ATT AHD in the same manner, trying to flash the Mexican JB version (I bought 3 of this phones to sell here in Mexico and wanted them to look as the phones they sell here by replacing the broken digitizers with ones with no ATT logo and flashing local firmware) ...But yeah, I made a big mistake, I wasn't aware I had to unlock BL before flashing other carrier SBF's... :S At least I've learned from this and didn't made the same mistake with the other 2 AHD's I have (And I'm planning to go back to stock and deodex em' because Mex fw isnt working pretty well on this AHD's...)
Trying to repair this thing by reflashing ATT JB stock fw... RSD & Myth seem not to work;
-In RSD I can't even get past step 1/23 (flash partition "gtp_main0.bin" failed"); when trying to flash Mexican rom I got to step 15/23 till I got the error.
-In Myth It looks like some files get flashed (It even gets me to the "Load Recovery" option, I obviously choose Stock as I don't want to f'up the phone even more ) and then "finishes" but when rebooting, shows "Dual Core tech" bootscreen and sends me back to Fastboot (Reason: Sticky bit factory_fastboot), tried stickyboot solution on cmd and then reflash on myth, same result.
Also I get the messages "downgraded security version" and "Invalid PIV Image: System" in AHD Fastboot. I don't know what else to do now, I still haven't tried Bell rom as I think I'll mess things up even more so I've stayed away from it At this point I guess I'm pretty much f***ed...
@ickysjazz
@vananucho
You're using the wrong fastboot...I can tell that by the error code...use snapdragon fastboots...those are the only ones for us to use. Any other fastboot will result in errors.
So Download those
DL Mex Retail
Extract it
Open terminal to that extracted directory
Do the sticky_bit fix.
Do these commands in this order
Code:
fastboot flash partition gpt_main0.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash sbl3 sbl3.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot flash cdrom cdrom
fastboot erase cache
fastboot erase userdata
And that's how you manually flash a fastboot. I've never used MythTools or RSD. That is how I do it, always have done it, always will do it -- with the same fastboot linked above with same commands posted. Those are for Mex Retail, but should work on any JB fastboot...ICS fastboots need a few minor tweaks.
Do the fastboot commands as root on Linux or as a Windows Admin (set the admin privileges for the app in the right click properties menu)
Replaced the fastboot with the one provided by Skeevydude and still get the same error but I guess it's due to the fact that I'm running out of battery (Started showing low bat advice after 3rd failed attempt, using regular cable), I'll try this again as soon as I make a flashing cable, I'll keep updated!
Yesterday my moto x alerted me that the KitKat update had been downloaded and was ready to install. I selected INSTALL and the installation began. About a minute into it, it kicked me to the bootloader with the message, "Failed to hab check for recovery: 0x56. Boot up failed".
Also see my post at androidcentral.com at forums.androidcentral.com/moto-x/336036-kitkat-crashed-my-moto-x-unrecoverable.html
Note that my moto x has never been rooted.
forums.androidcentral.com/attachments/moto-x/92779d1384906583-kitkat-crashed-my-moto-x-unrecoverable-kitkat_error.jpg
I selected "Recovery" and it rebooted and attempted to re-install, but then I was met with a image very similar to this except it said "ERROR":
forums.androidcentral.com/attachments/moto-x/92780d1384906685-kitkat-crashed-my-moto-x-unrecoverable-android-error.jpg
Then a few seconds later it rebooted again and now it just gets stuck at the Motorola logo:
forums.androidcentral.com/attachments/moto-x/92781d1384906724-kitkat-crashed-my-moto-x-unrecoverable-moto_x_boot_logo_featured_small.jpg
If I try any of the other options in the boot loader, the behavior is the same.. it gets stuck at the Motorola logo. Yesterday it sat that way for 4 hours before the battery died.
Today I tried connecting it to my computer via USB. My Mac doesn't appear to recognize that it's been connected even though the drivers have been installed. In a Windows VM with MDM it recognized the first time I connected it, but the MDM icon promptly disappeared from the status bar.
I spoke with Verizon tier 2 tech support yesterday and they didn't seem very knowledgeable - the person I spoke with didn't even know what KitKat is.
Surprisingly, I thought I had set up the Motorola data backup to the cloud, but verizon tech support said I must not have enabled it. So my biggest worry is that I've lost all my data (pictures/videos/contacts/etc...).
I'm hoping that somebody on this forum might have some advice for me.
Thanks,
Chris
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
xpc21 said:
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
Click to expand...
Click to collapse
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
cbridgers said:
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
Click to expand...
Click to collapse
cbridgers, that error happened to me while i was trying to flash through RSD Lite the leaked version of Kitkat. Because it was only to AT&T phones, it gave me that error cause i didnt have an unlocked bootloader. So what i did was flash back the 4.2.2 and for my surprise the phone was with all my config and data, nothing was erased.
Few suggestions...
cbridgers said:
Thanks for your response. I could certainly do that.. but I first want to make sure I've pursued every avenue for recovering my data before I reflash/wipe.
Click to expand...
Click to collapse
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
xpc21 said:
cbridgers, if you had some battery you could try download 4.2.2 sbf file and recover through RSD Lite.
Click to expand...
Click to collapse
SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
Click to expand...
Click to collapse
Thanks for your detailed instructions! Solution #1 didn't work for me. Solution #2 gives me the following error when I run "fastboot flash system system.img":
load_file: could not allocate 870593756 bytes
error: cannot load 'system.img'
I'm not sure I want to try Solution #3 yet. May try to talk to Motorola first.
Thanks again for the detailed advice!
Chris
SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
In any case, try the following remedies (in order of severity):
** I'm assuming you have RSD Lite, fastboot, ADB and the Moto X drivers installed and working **
-- Solution #1 - Easiest --
1) Go into Fastboot mode (power button and vol. down)
2) In your console, type in "fastboot erase cache"
- This solved the issue in one of my test scenarios. It's the easiest and least severe to implement
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
- This should preserve your user data and works in most circumstances, depending on how far the KitKat install proceeded before failing -
-- Solution #3 - Severe - Factory Reset --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org).
2) Unzip the ROM and edit the XML file. Delete the step operation that says "getVar". It should be the first line under step operations.
3) Use RSD lite to flash the firmware
- This will erase EVERYTHING. Say goodbye to your data. And porn.
Hope you get to recover using only the first two steps. If not, rinse then repeat. Good luck!
Click to expand...
Click to collapse
OK, I got past the previous error by increasing the RAM allocated to my Windows VM. Now I get the following error when running "fastboot flash system system.img":
sending 'system' (850189 KB)...
(bootloader) Data size exceeds download buffer
FAILED (remote failure)
finished. total time: 0.313s
cbridgers said:
Thanks for your detailed instructions! Solution #1 didn't work for me. Solution #2 gives me the following error when I run "fastboot flash system system.img":
load_file: could not allocate 870593756 bytes
error: cannot load 'system.img'
I'm not sure I want to try Solution #3 yet. May try to talk to Motorola first.
Thanks again for the detailed advice!
Chris
Click to expand...
Click to collapse
Make sure you are using the newest fastboot files, the older ones do not chunk the system image and it is too large to flash.
New fastboot for Mac -- > http://www.teamblackhat.net/Downloads/Darwin.zip
New fastboot for Windows --> http://www.teamblackhat.net/Downloads/fastboot.zip
Use the house if moto save data option you can fxz using rsd or fastboot and it will not erase data at all. I have used it many times works great.
SamSpadeXX said:
I had the same issue. I was able to recover it once, but recreated the scenario for good measures. My best guess is this issue is free space related (you should have at least 3gb free), but I'll confirm later today.
Click to expand...
Click to collapse
How sure are you about this?
Also, I had xt1058 (americamovil) with TMO firmware with the camera update (unlocked BL) and I flashed stock vzw firmware (with the camera update). No problems after a full wipe. The OTA was downloading too slow so I downloaded the OTA zip file in other thread. When I tried to install the update via stock recovery i got this message:
"/modem/image/dsps.b00" has unexpected contents.
Installation aborted
Click to expand...
Click to collapse
So i waited for the normal OTA and it just says installation failed, and i had it just wiped so i can't be free space.
Finally I flashed the 4.4 TMO leak
Try this
fastboot oem fb_mode_clear
fastboot reboot-bootloader
then take all the files from the first OTA sbf and flash them in order
does that work?
waiflih said:
How sure are you about this?
Also, I had xt1058 (americamovil) with TMO firmware with the camera update (unlocked BL) and I flashed stock vzw firmware (with the camera update). No problems after a full wipe. The OTA was downloading too slow so I downloaded the OTA zip file in other thread. When I tried to install the update via stock recovery i got this message:
So i waited for the normal OTA and it just says installation failed, and i had it just wiped so i can't be free space.
Finally I flashed the 4.4 TMO leak
Click to expand...
Click to collapse
There are 5 parts that need to be stock, that is the only thing that needs to be done.
system, boot, recovery, modem, fsg.
the only way to know why it is failing is to sideload, load from recovery, or check the update error log.
If it were me I'd just fastboot all five of those partitions and take the update.
jimmydafish said:
There are 5 parts that need to be stock, that is the only thing that needs to be done.
system, boot, recovery, modem, fsg.
the only way to know why it is failing is to sideload, load from recovery, or check the update error log.
If it were me I'd just fastboot all five of those partitions and take the update.
Click to expand...
Click to collapse
I dont know where to find modem files for stock vzw
Enviado desde mi XT1052
waiflih said:
I dont know where to find modem files for stock vzw
Enviado desde mi XT1052
Click to expand...
Click to collapse
They are in the FXZ file named NON-HLOS.bin
Thx! I didnt know those were modem related. Can i flash back the modem files to tmo or att firmware?
Enviado desde mi XT1052
waiflih said:
Thx! I didnt know those were modem related. Can i flash back the modem files to tmo or att firmware?
Enviado desde mi XT1052
Click to expand...
Click to collapse
Well what are you trying to do? but if unlocked you can flash anything you want. I would stay far away from flashing any bootloader, tz, gpt, or sbl files though.
Only flash those files I named before.
Yes, i only flash the files i know are safe to flash, i dont like to use rsdlite. Thx again
Enviado desde mi XT1052
I seem to have run into the same issue..
Any updates, OP?
Here's my thread: http://forum.xda-developers.com/showthread.php?p=47747140#post47747140
ekraincg said:
I seem to have run into the same issue..
Any updates, OP?
Here's my thread: http://forum.xda-developers.com/showthread.php?p=47747140#post47747140
Click to expand...
Click to collapse
I'm having the same problem with my T-Mo moto x I received yesterday. I tried the fastboot erase cache method. It works to the extent that I can boot back into 4.2.2 but I can't update or perform a factory reset from the settings menu.
When I give the command to fastboot erase cache the bootloader says 'get-var partition type' and 'erasing cache' however the bootloader never says 'cache erased' or any other confirmation message. Fastboot on the desktop does say 'cache erased' though.
Finally, I would try to flash the stock images but I can't seem to find them anywhere. Can someone point me to them please?
Hey guys,
So I wasn't paying attention while trying to restore my HTC One to stock. I ended up formatting and erasing all data on the entire phone. It has no OS now. Here's what I am ABLE to do:
Boot into Bootloader and Fastboot
Access TWRP Recovery
HTC Dev Lock and Re-Lock
Here's what I am UNABLE to do:
Sideloading ADB is unavailable due to error messages stating Unable to mount <partition> and every partition is unable to mount.
I have tried to mount the partitions within TWRP, this doesn't work.
Achieve S-Off
I just need to get the phone back to some type of working order so that I can sideload a ROM over or fastboot a fully stock zip. Can anybody help me here? I've seen very similar issues all over the forums, all of the problems they encountered could be fixed by ADB sideloading a ROM, again, I cannot access ADB sideloading.
Sidkain said:
Hey guys,
So I wasn't paying attention while trying to restore my HTC One to stock. I ended up formatting and erasing all data on the entire phone. It has no OS now. Here's what I am ABLE to do:
Boot into Bootloader and Fastboot
Access TWRP Recovery
HTC Dev Lock and Re-Lock
Here's what I am UNABLE to do:
Sideloading ADB is unavailable due to error messages stating Unable to mount <partition> and every partition is unable to mount.
I have tried to mount the partitions within TWRP, this doesn't work.
Achieve S-Off
I just need to get the phone back to some type of working order so that I can sideload a ROM over or fastboot a fully stock zip. Can anybody help me here? I've seen very similar issues all over the forums, all of the problems they encountered could be fixed by ADB sideloading a ROM, again, I cannot access ADB sideloading.
Click to expand...
Click to collapse
U can use a USB OTG cable. Download ARHD(or any rom of ur choice), copy it to a USB. then using the OTG cable, u can flash the rom from TWRP. Once u have a working OS, continue with the RUU process
One other note, I have downloaded two different instances of the shipped ROM for this phone. When trying to "fastboot update update.zip" on either of them, I get the following error message and a failure to update:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Sidkain said:
One other note, I have downloaded two different instances of the shipped ROM for this phone. When trying to "fastboot update update.zip" on either of them, I get the following error message and a failure to update:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Click to expand...
Click to collapse
start by posting a "fastboot getvar all" (excluding IMEI and s/n) and what version number of TWRP you're using
your probably just using an outdated twrp version, flash 2.6.3.3 and then retry sideloading
I am in the exact same situation. Phone literally ground to a halt last night, so rebooted it and it got stuck in a boot loop. Phone isn't rooted, it wasn't unlocked at the time (it is now, since I've been trying to fix it for the past day) and I literally have no idea how to fix it. Although I think my situation is worse, I can't access anything else other than the bootloader...
I've tried RUU (which I can't do because I'm not S-Off and I'm on hboot 1.45)
I've tried just flashing a new recovery (but whenever I try to enter the recovery it gets stuck saying 'Entering Recovery' then the phone goes back into the boot loop)
Like literally the only thing I have access to is the bootloader, everything else sends it into a boot loop, hell I can't even format or flash imgs (apart from recovery imgs) without fastboot giving me an error message.
I fear the phone is completely ****ed, and this has come out of completely nowhere. Except now that I've unlocked the bootloader to try and fix it, it says TAMPERED and UNLOCKED which means I WONT GET A REPAIR...
glaringradio said:
I am in the exact same situation. Phone literally ground to a halt last night, so rebooted it and it got stuck in a boot loop. Phone isn't rooted, it wasn't unlocked at the time (it is now, since I've been trying to fix it for the past day) and I literally have no idea how to fix it. Although I think my situation is worse, I can't access anything else other than the bootloader...
I've tried RUU (which I can't do because I'm not S-Off and I'm on hboot 1.45)
I've tried just flashing a new recovery (but whenever I try to enter the recovery it gets stuck saying 'Entering Recovery' then the phone goes back into the boot loop)
Like literally the only thing I have access to is the bootloader, everything else sends it into a boot loop, hell I can't even format or flash imgs (apart from recovery imgs) without fastboot giving me an error message.
I fear the phone is completely ****ed, and this has come out of completely nowhere. Except now that I've unlocked the bootloader to try and fix it, it says TAMPERED and UNLOCKED which means I WONT GET A REPAIR...
Click to expand...
Click to collapse
have you tried to fastboot erase cache after flashing recovery
xnknown said:
have you tried to fastboot erase cache after flashing recovery
Click to expand...
Click to collapse
Yep, it still just hangs on "Entering Recovery" before rebooting and entering the boot loop again...
I'm fearing that this phone is just completely doomed now
glaringradio said:
Yep, it still just hangs on "Entering Recovery" before rebooting and entering the boot loop again...
I'm fearing that this phone is just completely doomed now
Click to expand...
Click to collapse
then you may want to try flashing an older version of twrp
xnknown said:
then you may want to try flashing an older version of twrp
Click to expand...
Click to collapse
I have tried, no matter what version I flash it still does not let me get beyond "Entering Recovery"
glaringradio said:
I have tried, no matter what version I flash it still does not let me get beyond "Entering Recovery"
Click to expand...
Click to collapse
try all three
fastboot erase cache
fastboot erase system
fastboot erase data
glaringradio said:
I have tried, no matter what version I flash it still does not let me get beyond "Entering Recovery"
Click to expand...
Click to collapse
1- are you sure you're using the correct recovery for your phone (e.g. M7_U/UL vs Sprint!!)
2- have you checked MD5 of the download, to make sure it's not corrupt; TWRP site doesn't play nice with download managers, so please check MD5
xnknown said:
try all three
fastboot erase cache
fastboot erase system
fastboot erase data
Click to expand...
Click to collapse
Cache is fine, it erases properly
I get "FAILED (remote: not allowed)" when I try to erase system or data
I have tried flashing every single img from the official TeamWin projects site (the ones that look like openrecovery-twrp-2.6.3.3-m7.img) and absolutely none of them work. They all say "Okay" as if they flash correctly, however when I select to go into recovery from bootloader, it brings up "Entering Recovery" then reboots and goes back into the boot loop
glaringradio said:
Cache is fine, it erases properly
I get "FAILED (remote: not allowed)" when I try to erase system or data
I have tried flashing every single img from the official TeamWin projects site (the ones that look like openrecovery-twrp-2.6.3.3-m7.img) and absolutely none of them work. They all say "Okay" as if they flash correctly, however when I select to go into recovery from bootloader, it brings up "Entering Recovery" then reboots and goes back into the boot loop
Click to expand...
Click to collapse
nkk is right is ur phone a sprint or verizon?
xnknown said:
nkk is right is ur phone a sprint or verizon?
Click to expand...
Click to collapse
It's an international (I'm with the operator 3 in the UK)
glaringradio said:
It's an international (I'm with the operator 3 in the UK)
Click to expand...
Click to collapse
have you checked MD5?
glaringradio said:
It's an international (I'm with the operator 3 in the UK)
Click to expand...
Click to collapse
hmmm that is really wierd lol, the only other thing I can think of is updating your firmware and hboot to the latest and then reflash twrp and erase cache
xnknown said:
hmmm that is really wierd lol, the only other thing I can think of is updating your firmware and hboot to the latest and then reflash twrp and erase cache
Click to expand...
Click to collapse
i hate to be insistent, but has he checked MD5?
nkk71 said:
have you checked MD5?
Click to expand...
Click to collapse
I have, I literally have no idea as to why they aren't working...
xnknown said:
hmmm that is really wierd lol, the only other thing I can think of is updating your firmware and hboot to the latest and then reflash twrp and erase cache
Click to expand...
Click to collapse
My hboot is currently on 1.55, is that not the latest? The phone was on 4.3, and it literally just started boot looping out of absolutely nowhere. This sucks so much and I have no idea how to fix it and can't find anybody who can
When I try to flash a different hboot, I get the error "FAILED (remote: 99 unknown fail)".
Again, MD5s on the TWRP files I downloaded are fine. All I can do is use fastboot to varying degrees of success, and nothing works when I try to use RUU... It's a soft brick, but it's completely and utterly broken and I can't see any way to recover it (and I can't send it for repair since it is now marked as tampered)
glaringradio said:
I have, I literally have no idea as to why they aren't working...
My hboot is currently on 1.55, is that not the latest? The phone was on 4.3, and it literally just started boot looping out of absolutely nowhere. This sucks so much and I have no idea how to fix it and can't find anybody who can
Click to expand...
Click to collapse
and 1 more try: have you checked MD5?
I Can't flash recovery for my moto x, I have unlocked the bootloader and appears to me on fastboot: Device is UNLOCKED. Status Code:3
I don't know if this is right, but I can't flash a recovery in it.
Error:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8030 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.116s
I tested various recovery's but don't work.
Sorry for my bad english
Murilo900 said:
I Can't flash recovery for my moto x, I have unlocked the bootloader and appears to me on fastboot: Device is UNLOCKED. Status Code:3
I don't know if this is right, but I can't flash a recovery in it.
Error:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8030 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.116s
I tested various recovery's but don't work.
Sorry for my bad english
Click to expand...
Click to collapse
Are you using mfastboot? You should be..
Sent From Droid Ultra
In addition to mFastboot, make sure your battery is charged more than 80%
Caseyk621 said:
Are you using mfastboot? You should be..
Sent From Droid Ultra
Click to expand...
Click to collapse
KidJoe said:
In addition to mFastboot, make sure your battery is charged more than 80%
Click to expand...
Click to collapse
Yes,
I did on mfastboot and appears the same thing, and the battery is full, when I try to flash on moto x appears : getvar-download-size
Murilo900 said:
Yes,
I did on mfastboot and appears the same thing, and the battery is full, when I try to flash on moto x appears : getvar-download-size
Click to expand...
Click to collapse
What ROM is on your phone right now? Which recovery are you trying to flash?
What state was your phone in when you started trying to flash recovery?
KidJoe said:
What ROM is on your phone right now? Which recovery are you trying to flash?
What state was your phone in when you started trying to flash recovery?
Click to expand...
Click to collapse
The ROM on my phone is 4.4.2 KitKat, I tried to flash twrp recovery 2.6.3.1 and cwm recovery for motox
The state was the same, I unlocked bootloader, following tutorials on internet but I'm stuck on flash the recovery because this problem, I get this error and on my phone appears getvar-download-size, and Download Failed.
Murilo900 said:
The ROM on my phone is 4.4.2 KitKat, I tried to flash twrp recovery 2.6.3.1 and cwm recovery for motox
The state was the same, I unlocked bootloader, following tutorials on internet but I'm stuck on flash the recovery because this problem, I get this error and on my phone appears getvar-download-size, and Download Failed.
Click to expand...
Click to collapse
Ok.
Try the mfastboot from inside -> http://mark.cdmaforums.com/X-STUFF/Mfastboot-4.4.zip (will have to rename fastboot.exe to mfastboot.exe).. or from -> http://mark.cdmaforums.com/X-STUFF/ADB-MFASTBOOT.zip they are the ones I use and they have worked for me.
and is this the twrp you are using? -> http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
Oh god! Thanks, this mfastboot you just send works!, I don't know if the problem was my mfastboot that I have here, but finally I flashed! Leveraging the topic can you suggest me some roms for moto x, and if you know some way to take off the boot the sign that the bootloader is unlocked blablabla, Anyway thank you.
Murilo900 said:
Oh god! Thanks, this mfastboot you just send works!, I don't know if the problem was my mfastboot that I have here, but finally I flashed! Leveraging the topic can you suggest me some roms for moto x, and if you know some way to take off the boot the sign that the bootloader is unlocked blablabla, Anyway thank you.
Click to expand...
Click to collapse
I run stock, unlocked and rooted, so I can't suggest an alternate roms.
As for the unlocked bootloader warning message... sure. there is a big thread -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961 start around post 150 of that thread for how to make your own... in a couple of hours I'll refresh this file -> http://mark.cdmaforums.com/X-STUFF/X-LogoBins.zip adding even more logo.bin files (i have about 7 or 8 more to test before I can re-zip and upload it)
HELP!!
I am at a loss. No matter what fastboot/mfastboot I use, no matter what YouTube video I follow, I can not flash recovery.
I get the same error as the OP. I tried the links posted a few posts up, it wont work.
I type the commands, I get the top error message (among others depending on the mfastboots I try) and then nothing.
I am truly at a loss.
Verizon Developer Moto X
4.4.2
Device is: Unlocked
Status Code: 3
In one video I watched it said that I needed to have it say Status Code:1. Is that where I am going wrong?
Any help would be greatly appreciated.
Thanks!!
n99hockey said:
I am at a loss. No matter what fastboot/mfastboot I use, no matter what YouTube video I follow, I can not flash recovery.
I get the same error as the OP. I tried the links posted a few posts up, it wont work.
I type the commands, I get the top error message (among others depending on the mfastboots I try) and then nothing.
I am truly at a loss.
Verizon Developer Moto X
4.4.2
Device is: Unlocked
Status Code: 3
In one video I watched it said that I needed to have it say Status Code:1. Is that where I am going wrong?
Any help would be greatly appreciated.
Thanks!!
Click to expand...
Click to collapse
What recovery are you trying to flash? Stock or other? Unlocked Status Code 3 is needed to flash an alternate or 3rd party recovery.
Besides the error listed in the first post, exactly what "others" do you see as error codes?
Things to try... (in no special order)
this mfastboot -> mfastboot-442.zip
re-download the recovery you are trying to flash
update your ADB and Platform Tools
There are several versions of TWRP that can work.
Unofficial TWRP 2.6.3.1 for 4.4 -> http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
Unofficial TWRP 2.7.0.0 -> http://androidhosting.org/Devs/Dhacker29/MotoX/TWRP-2.7.0.0-moto_msm8960dt.img
Official TWRP 2.7.1.1 -> http://techerrata.com/browse/twrp2/ghost
of those, I've only used the 2.6.3.1 on my VZW Dev X with 4.4.2 and below.
KidJoe said:
What recovery are you trying to flash? Stock or other? Unlocked Status Code 3 is needed to flash an alternate or 3rd party recovery.
Besides the error listed in the first post, exactly what "others" do you see as error codes?
Things to try... (in no special order)
this mfastboot -> mfastboot-442.zip
re-download the recovery you are trying to flash
update your ADB and Platform Tools
There are several versions of TWRP that can work.
Unofficial TWRP 2.6.3.1 for 4.4 -> http://goo.im/devs/Hashcode/motox/unlocked/twrp-2.6.3.1-ghost-4.4.img
Unofficial TWRP 2.7.0.0 -> http://androidhosting.org/Devs/Dhacker29/MotoX/TWRP-2.7.0.0-moto_msm8960dt.img
Official TWRP 2.7.1.1 -> http://techerrata.com/browse/twrp2/ghost
of those, I've only used the 2.6.3.1 on my VZW Dev X with 4.4.2 and below.
Click to expand...
Click to collapse
Thanks for the reply.
However I should have known better, I changed the USB port and it worked just fine with the mfastboot I downloaded longer than I would like to admit before I posted my question.
</sigh>
Still can't flash custom recovery
I have a Verizon XT1060 Developer Edition. Unlocked bootloader. Drivers seem to be installed correctly, "Fastboot devices" identifies the phone. Battery is 90%+. Fastboot menu says "Device is unlocked. Status Code 3". I have tried different USB ports on the PC, different cables to connect the phone and just about every other variable that I can think of.
I have followed all of the suggestions listed in this post and I still cannot flash a custom recovery. I have tried multiple versions of TWRP, Fastboot, Mfastboot etc.. Here is the error message...
(bootloader) Variable not supported!
error: cannot open 'twrp-2.6.3.1-ghost-4.4.img'
Actually depending on the method I am trying at the time, fastboot mfastboot etc., I may get a couple of additional lines that mention Max download size etc. but it always starts with the bootloader comment and ends with "Cannot open......"
Searching for "(bootloader) Variable not supported!" returns a lot of hits but I have not found anything to clear the issue. Any help would be appreciated.
Ric214 said:
....Here is the error message...
(bootloader) Variable not supported!
error: cannot open 'twrp-2.6.3.1-ghost-4.4.img'
...
Click to expand...
Click to collapse
That usually means that mFastboot (or fastboot) can't find the IMG file on your PC.
My first question would be... does that file exist in your current directory/folder?
i.e... at the command prompt.. type dir *.img is the twrp file listed there? If no, that is your issue. change to the folder (directory) where the TWRP IMG file is, and try it.
It is there. Here is what I got.
C:\Users\Ric\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x86
_64-20140321\sdk\platform-tools>dir *.img
Volume in drive C is OS
Volume Serial Number is 76F9-C97B
Directory of C:\Users\Ric\Downloads\adt-bundle-windows-x86_64-20140321\adt-bund
le-windows-x86_64-20140321\sdk\platform-tools
06/13/2014 10:54 PM 8,417,280 openrecovery-twrp-2.7.1.1-ghost.img
06/03/2014 11:10 PM 10,090,496 twrp-2.6.3.1-ghost-4.4.img
2 File(s) 18,507,776 bytes
0 Dir(s) 426,324,336,640 bytes free
Since this has been driving me crazy for a couple of days I have several folders with different versions of Fastboot and Mfastboot in them along with some different versions of TWRP and CWM and I am getting the same error with all of them. This last time I just stuck the TWRP file in my platform -tools folder to try and make sure I had a good Fastboot file.
Thanks for the reply. If you have any other ideas I am eager to hear them.
Ric214 said:
It is there. Here is what I got.
C:\Users\Ric\Downloads\adt-bundle-windows-x86_64-20140321\adt-bundle-windows-x86
_64-20140321\sdk\platform-tools>dir *.img
Volume in drive C is OS
Volume Serial Number is 76F9-C97B
Directory of C:\Users\Ric\Downloads\adt-bundle-windows-x86_64-20140321\adt-bund
le-windows-x86_64-20140321\sdk\platform-tools
06/13/2014 10:54 PM 8,417,280 openrecovery-twrp-2.7.1.1-ghost.img
06/03/2014 11:10 PM 10,090,496 twrp-2.6.3.1-ghost-4.4.img
2 File(s) 18,507,776 bytes
0 Dir(s) 426,324,336,640 bytes free
Since this has been driving me crazy for a couple of days I have several folders with different versions of Fastboot and Mfastboot in them along with some different versions of TWRP and CWM and I am getting the same error with all of them. This last time I just stuck the TWRP file in my platform -tools folder to try and make sure I had a good Fastboot file.
Thanks for the reply. If you have any other ideas I am eager to hear them.
Click to expand...
Click to collapse
Had you made ANY prior modifications to your unit before now? Any possibility you used one of the previous root/write protect disable exploits, and THEN got the bootloader unlocked?
I've seen alot of users in this situation recently -thanks to middleman
I suggest you follow the 'return to stock' thread here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You should flash the 4.4.2 VZW SBF file from here: http://sbf.droid-developers.org/phone.php?device=0
SBFing back to stock is very different from a Factory Reset in that it can actually repair a damaged filesystem, and even un-do any previous exploits you may have used.
There are 2 methods - many report that the "Manual Method" is easier than using RSD Lite. Either should work equally well, but pay close attention to the steps.
You will want to do a couple of things just a little bit differently. First, use mfastboot as suggested by KidJoe for ALL flashing commands.
Second, once your phone has been placed into bootloader mode (AP Fastboot), before you proceed with the fastboot commands listed under Manual Method, do this first:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
Your device should reboot back to the bootloader. NOW, proceed with the entire list of commands (using mfastboot for all of them). Yes, you will be flashing partition and motoboot again...don't worry. It is intentional.
After you have completed the rest of the steps, you will likely be able to flash TWRP (or custom recovery of your choice) without issue.
Let us know if this fixes your issues.
samwathegreat said:
Had you made ANY prior modifications to your unit before now? Any possibility you used one of the previous root/write protect disable exploits, and THEN got the bootloader unlocked?
I've seen alot of users in this situation recently -thanks to middleman
I suggest you follow the 'return to stock' thread here: http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
You should flash the 4.4.2 VZW SBF file from here: http://sbf.droid-developers.org/phone.php?device=0
SBFing back to stock is very different from a Factory Reset in that it can actually repair a damaged filesystem, and even un-do any previous exploits you may have used.
There are 2 methods - many report that the "Manual Method" is easier than using RSD Lite. Either should work equally well, but pay close attention to the steps.
You will want to do a couple of things just a little bit differently. First, use mfastboot as suggested by KidJoe for ALL flashing commands.
Second, once your phone has been placed into bootloader mode (AP Fastboot), before you proceed with the fastboot commands listed under Manual Method, do this first:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
Your device should reboot back to the bootloader. NOW, proceed with the entire list of commands (using mfastboot for all of them). Yes, you will be flashing partition and motoboot again...don't worry. It is intentional.
After you have completed the rest of the steps, you will likely be able to flash TWRP (or custom recovery of your choice) without issue.
Let us know if this fixes your issues.
Click to expand...
Click to collapse
I had not done any modifications prior to unlocking the bootloader but going back to stock is about the only thing that I could think of that I have not already tried. I will give this a shot tomorrow night and let you know how it went. Thanks for your help.
Ric214 said:
I had not done any modifications prior to unlocking the bootloader but going back to stock is about the only thing that I could think of that I have not already tried. I will give this a shot tomorrow night and let you know how it went. Thanks for your help.
Click to expand...
Click to collapse
One last thing I can suggest before return to stock:
Are you trying to flash the recovery -while booted into Android-? If so, you have to have USB Debugging enabled. Some users have experienced difficulty using fastboot while booted into Android even with USB debugging enabled.
----------------
You can try flashing from bootloader (AP Fastboot Mode) instead.
To do this, unplug the phone from USB. Power off the phone. Hold down VOL DOWN and power the phone back on. You should now be booted into bootloader.
Now plug the USB back in, and try:
mfastboot flash recovery twrp_filename.img
samwathegreat said:
One last thing I can suggest before return to stock:
Are you trying to flash the recovery -while booted into Android-? If so, you have to have USB Debugging enabled. Some users have experienced difficulty using fastboot while booted into Android even with USB debugging enabled.
----------------
You can try flashing from bootloader (AP Fastboot Mode) instead.
To do this, unplug the phone from USB. Power off the phone. Hold down VOL DOWN and power the phone back on. You should now be booted into bootloader.
Now plug the USB back in, and try:
mfastboot flash recovery twrp_filename.img
Click to expand...
Click to collapse
Thanks for the advice but I am not booted into Android. I started with the phone off and got into the bootloader exactly as you suggested. I will have some time over the next few days to flash back to stock and start over again. I will post the results. In the meantime if you think of anything else, let me know. Thanks for your help.
Ric214 said:
Thanks for the advice but I am not booted into Android. I started with the phone off and got into the bootloader exactly as you suggested. I will have some time over the next few days to flash back to stock and start over again. I will post the results. In the meantime if you think of anything else, let me know. Thanks for your help.
Click to expand...
Click to collapse
try shortening the path the IMG resides in...
i.e. make a folder off the root of drive C call it FLASH... drop the TWRP.img into c:\flash and try flashing it from there.
I did a factory reset from within the settings of the phone, it shows the erasing android and then flickers with and image of an android with triangle. Does this several times and then just stops on the android with red triangle. I can get into stock recovery, tried resetting from there but same thing happens. Also, if I just leave the phone it reboots and then tries to erase and then I get the same loop of it trying and failing.
Any ideas how to fix this? Phone is on the stock 5.0 rom and I have the pure edition.
Thanks
Raistlin1 said:
I did a factory reset from within the settings of the phone, it shows the erasing android and then flickers with and image of an android with triangle. Does this several times and then just stops on the android with red triangle. I can get into stock recovery, tried resetting from there but same thing happens. Also, if I just leave the phone it reboots and then tries to erase and then I get the same loop of it trying and failing.
Any ideas how to fix this? Phone is on the stock 5.0 rom and I have the pure edition.
Thanks
Click to expand...
Click to collapse
I would get into bootloader mode and reflash the system.img.
JulesJam said:
I would get into bootloader mode and reflash the system.img.
Click to expand...
Click to collapse
I am having a hard time trying to flash system.img. I found the system.img for my rom version and tried using ms fast boot v2 but it just hangs in the command window. I have installed the moto drivers and computer recognizes phone when it's in fast boot mode.
I even tried using someone's toolkit to return completely stock u rooted 4.4 but that doesn't work either.
Been reading tons of threads on here but can't seem to get it to flash.
Raistlin1 said:
I am having a hard time trying to flash system.img. I found the system.img for my rom version and tried using ms fast boot v2 but it just hangs in the command window. I have installed the moto drivers and computer recognizes phone when it's in fast boot mode.
Click to expand...
Click to collapse
Are you flashing a single file system.img or sparsechunks? Do you have mfastboot version 2?
Also, you can install Motorola Device Manager on your computer and when your phone is connected in fastboot mode, run MDM and see if it detects it.
JulesJam said:
Are you flashing a single file system.img or sparsechunks? Do you have mfastboot version 2?
Also, you can install Motorola Device Manager on your computer and when your phone is connected in fastboot mode, run MDM and see if it detects it.
Click to expand...
Click to collapse
System img is a single file, I also have a zip that has sparse chunks but haven't tried them. I am pretty sure I downloaded version 2 of mfastboot.
MDM saw my phone and said it had the most recent version.
Raistlin1 said:
System img is a single file, I also have a zip that has sparse chunks but haven't tried them. I am pretty sure I downloaded version 2 of mfastboot.
MDM saw my phone and said it had the most recent version.
Click to expand...
Click to collapse
I would try flashing the sparsechunks if you can't flash the single file image.
JulesJam said:
I would try flashing the sparsechunks if you can't flash the single file image.
Click to expand...
Click to collapse
Tried them using fastboot and only the first sparsechunk worked, they rest gave some error about bootloader.
I then tried in the mfastboot folder I created and it just hangs saying waiting for device, that's why I tried using fastboot.
I am really screwing myself, now while in bootloader and I try to boot or recovery I get failed to validate. Never had these problems flashing my N5, oh well.
Raistlin1 said:
Tried them using fastboot and only the first sparsechunk worked, they rest gave some error about bootloader.
I then tried in the mfastboot folder I created and it just hangs saying waiting for device, that's why I tried using fastboot.
Click to expand...
Click to collapse
How large is your mfastboot? It should be 521KB. If it is smaller than that, you don't have the right one.
What was the bootloader error?
Also now that you have flashed 1 sparsechunk, try MDM again.
You also can try flashing the 4.4.4 system.img if you can find it and then run MDM again b/c it will try to update you.
JulesJam said:
How large is your mfastboot? It should be 521KB. If it is smaller than that, you don't have the right one.
What was the bootloader error?
Also now that you have flashed 1 sparsechunk, try MDM again.
You also can try flashing the 4.4.4 system.img if you can find it and then run MDM again b/c it will try to update you.
Click to expand...
Click to collapse
I am getting bootloader failed to erase partition, failed remote failure.
MDM says phone is on latest version. mfastboot is the size you stated.
Raistlin1 said:
I am getting bootloader failed to erase partition, failed remote failure.
Click to expand...
Click to collapse
This happened to others. One guy had an unlocked bootloader and TWRP installed as recovery and was able to format the data partition through TWRP and that solved the problem for him:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-fastboot-flash-img-failed-t3098727
Can you get into recovery from the bootloader mode? I would get into recovery and wipe cache and then do a wipe data/factory reset and see what happens.
JulesJam said:
This happened to others. One guy had an unlocked bootloader and TWRP installed as recovery and was able to format the data partition through TWRP and that solved the problem for him:
http://forum.xda-developers.com/moto-x-2014/help/xt1095-fastboot-flash-img-failed-t3098727
Can you get into recovery from the bootloader mode? I would get into recovery and wipe cache and then do a wipe data/factory reset and see what happens.
Click to expand...
Click to collapse
I will check out that thread, thanks. I cannot get into recovery from bootloader because it reboots into the erasing android which fails and then I get android with triangle and then I can get into recovery. But wiping cache and factory resetting from there does nothing, it reboots into the erasing android and then it fails to erase again.
Raistlin1 said:
I will check out that thread, thanks. I cannot get into recovery from bootloader because it reboots into the erasing android which fails and then I get android with triangle and then I can get into recovery. But wiping cache and factory resetting from there does nothing, it reboots into the erasing android and then it fails to erase again.
Click to expand...
Click to collapse
Can you reflash stock recovery?
Your bootloader is locked correct?
JulesJam said:
Can you reflash stock recovery?
Your bootloader is locked correct?
Click to expand...
Click to collapse
Reflashing recovery fails like systemail and my bootloader was unlocked prior to all of this happening.
Any way I can flash TWRP in the state I am in?
Raistlin1 said:
Reflashing recovery fails like systemail and my bootloader was unlocked prior to all of this happening.
Any way I can flash TWRP in the state I am in?
Click to expand...
Click to collapse
I would certainly try it.
Also, when you are in recovery and type adb devices, does it recognize your device?
JulesJam said:
I would certainly try it.
Also, when you are in recovery and type adb devices, does it recognize your device?
Click to expand...
Click to collapse
I am spent, going to bed and will pick up again tomorrow. Thanks for helping out.
JulesJam said:
I would certainly try it.
Also, when you are in recovery and type adb devices, does it recognize your device?
Click to expand...
Click to collapse
Tried fastboot boot twrp.img but it won't boot, then tried flashing using fastboot and mfastboot but twrp won't install. Nothing will finish installing, tried flashing everything I can but it keeps failing.
Got the 4.4 image and started with flash partition gpt.bin but got bootloader failed to write primary GPT, bootloader failed to progra partition table, failed remote failure.
On phone I see incomplete boot image for booting, mismatched partition size (recovery). MDM sees my phone and says it is on the current version but I cannot get out of this factory erase looping. Nothing is flashing successfully, I remember seeing something about RSD Lite, will that help me in any way?
Thanks
Raistlin1 said:
Tried fastboot boot twrp.img but it won't boot, then tried flashing using fastboot and mfastboot but twrp won't install. Nothing will finish installing, tried flashing everything I can but it keeps failing.
Got the 4.4 image and started with flash partition gpt.bin but got bootloader failed to write primary GPT, bootloader failed to progra partition table, failed remote failure.
On phone I see incomplete boot image for booting, mismatched partition size (recovery). MDM sees my phone and says it is on the current version but I cannot get out of this factory erase looping. Nothing is flashing successfully, I remember seeing something about RSD Lite, will that help me in any way?
Thanks
Click to expand...
Click to collapse
RSDLite will just use mfastboot to flash. You definitely CANNOT downgrade the partition table - it would leave you with a bootloader partition table version mismatch. So don't attempt that.
You are on the 5.0 bootloader (60.11) correct? If so, did you try flashing the 5.0 partition table (gpt.bin)?
Is your device recognized when you are in recovery and you type in the commad:
adb devices
JulesJam said:
RSDLite will just use mfastboot to flash. You definitely CANNOT downgrade the partition table - it would leave you with a bootloader partition table version mismatch. So don't attempt that.
You are on the 5.0 bootloader (60.11) correct? If so, did you try flashing the 5.0 partition table (gpt.bin)?
Is your device recognized when you are in recovery and you type in the commad:
adb devices
Click to expand...
Click to collapse
As of now I can only get into fastboot mode, I don't believe the phone can even cycle through trying to boot any more. I tried rebooting from fastboot mode but there was an error and it failed.
I tried finding the exact image for 5.0 but I was only able to find the thread that had system, recovery and boot. Do you know a link to find the 5.0 partition table?
Raistlin1 said:
I tried finding the exact image for 5.0 but I was only able to find the thread that had system, recovery and boot. Do you know a link to find the 5.0 partition table?
Click to expand...
Click to collapse
http://www.graffixnyc.com/motox.php
JulesJam said:
http://www.graffixnyc.com/motox.php
Click to expand...
Click to collapse
Downloaded the 5.0 file from there, started flashing those files and it worked up until recovery, then I got the same bootloader message I was getting previously. Tried them over again and they all failed.
When in recovery adb devices starts the daemon and then says list of devices attached but I don't see anything after that.
I think it is fubar`d, going to have to file a warrant claim or use the moto care I purchased.