Hi guys! I was trying to root my moto x and somehow messed up. I can get into fastboot, but havent been able to root it with RSD lite as im running into the same error as this person, and no, his fix doesnt work for me.
"I have a Verizon 2013 Moto X(XT1060) running 4.4.4(KXA21.12-L1.26) and I'm running Windows 7 64bit. And I'm following this guide.
I'm trying to root my phone but I'm stuck trying to revert it to stock 4.4.4. I have the drivers install, it shows up in windows explorer and in device manager, RSD Lite recognizes the device as Fastboot ghost S when I'm in the bootloader and says it's connected, the firmware I'm trying to use is called "VZW_XT1060_4.4.4-KXA21.12-L1.26_CFC_1FF.xml.zip", I've removed the "<step operation="getvar" var="max-download-size" />" line from the XML but whenever I try to start the flash I get an error saying "Failed flashing process. 2/17 flash partition "gpt.bin"-> Phone returned FAIL." and my phone reads "process oem command: fb_mode_set, getvar max-download-size, downloading 32768 bytes, done." I've tried moving the files multiple places, running RSD as admin and so far no luck and I completely wiped my phone. Any ideas?
edit:I fixed this by navigating to C:\Program Files (x86)\Motorola\RSD Lite and changing the SLD.exe to run in XP service pack 3 mode and as administrator."
Failed flashing process. 2/17 flash partition "gpt.bin" -> Phone returned FAIL.
The factory stock before this happened was 5.1 ghost
I would like to get it back to it but any version would work!
Thanks
ebirdy9 said:
Hi guys! I was trying to root my moto x and somehow messed up. I can get into fastboot, but havent been able to root it with RSD lite as im running into the same error as this person, and no, his fix doesnt work for me.
"I have a Verizon 2013 Moto X(XT1060) running 4.4.4(KXA21.12-L1.26) and I'm running Windows 7 64bit. And I'm following this guide.
I'm trying to root my phone but I'm stuck trying to revert it to stock 4.4.4. I have the drivers install, it shows up in windows explorer and in device manager, RSD Lite recognizes the device as Fastboot ghost S when I'm in the bootloader and says it's connected, the firmware I'm trying to use is called "VZW_XT1060_4.4.4-KXA21.12-L1.26_CFC_1FF.xml.zip", I've removed the "<step operation="getvar" var="max-download-size" />" line from the XML but whenever I try to start the flash I get an error saying "Failed flashing process. 2/17 flash partition "gpt.bin"-> Phone returned FAIL." and my phone reads "process oem command: fb_mode_set, getvar max-download-size, downloading 32768 bytes, done." I've tried moving the files multiple places, running RSD as admin and so far no luck and I completely wiped my phone. Any ideas?
edit:I fixed this by navigating to C:\Program Files (x86)\Motorola\RSD Lite and changing the SLD.exe to run in XP service pack 3 mode and as administrator."
Failed flashing process. 2/17 flash partition "gpt.bin" -> Phone returned FAIL.
The factory stock before this happened was 5.1 ghost
I would like to get it back to it but any version would work!
Thanks
Click to expand...
Click to collapse
Greetings and welcome to assist. Have you tried asking in this guide thread? Perhaps one of the users there has had a similar issue
Good Luck
Sawdoctor
Related
Hey again, so, trying to fix the problem described here: http://forum.xda-developers.com/showthread.php?t=2523194, I decided to go back to stock rom (JellyBean 4.1.2 from LiquidSmooth 2.1). I did it trough fastboot (with a batch file) because I'm on windows 8.1 and can't get RSD to work.
So, fasboot gives me the error several times:
"(bootloader) variable not supported
target reported max download size of 3147280 bytes"
Now a have a phone that won't go past motorola logo. I can get to fastboot mode (but can't use rsd, doesn't recognice my phone) and my have my bootloader unlocked.
How should I proceed to bring it back to life? I've been trying everything I could.
Edit: Well, my phone is working again. I installed TWRP again and CM10.1
But I still not able to install a stock rom. So, I also was going to try with a virtual machine with different os but decided to not take (more?) risks.
If could be of use, I could install windows 7 on my machine.
daro.brussa said:
Hey again, so, trying to fix the problem described here: http://forum.xda-developers.com/showthread.php?t=2523194, I decided to go back to stock rom (JellyBean 4.1.2 from LiquidSmooth 2.1). I did it trough fastboot (with a batch file) because I'm on windows 8.1 and can't get RSD to work.
So, fasboot gives me the error several times:
"(bootloader) variable not supported
target reported max download size of 3147280 bytes"
Now a have a phone that won't go past motorola logo. I can get to fastboot mode (but can't use rsd, doesn't recognice my phone) and my have my bootloader unlocked.
How should I proceed to bring it back to life? I've been trying everything I could.
Edit: Well, my phone is working again. I installed TWRP again and CM10.1
But I still not able to install a stock rom. So, I also was going to try with a virtual machine with different os but decided to not take (more?) risks.
If could be of use, I could install windows 7 on my machine.
Click to expand...
Click to collapse
by "batch script" do you mean you tried this? http://forum.xda-developers.com/showthread.php?t=2474393
shouldn't give errors unless something in your partition table is messed up.
********Edit, i just read the other post and see you are on a 925, do not flash the script i suggested above.
bweN diorD said:
by "batch script" do you mean you tried this? http://forum.xda-developers.com/showthread.php?t=2474393
shouldn't give errors unless something in your partition table is messed up.
********Edit, i just read the other post and see you are on a 925, do not flash the script i suggested above.
Click to expand...
Click to collapse
Hey, I fixed it using this tool http://forum.xda-developers.com/showthread.php?p=38190729.
It installed stock rom by sending big files "in parts", I believe. So I dind't have problems with size. Thanks for your answer though.
Hey,
i was flashing a new ROM, the installation was all completed but when i rebooted the system, its now stuck in fastboot mode.
Tried flashing with KDZ as well as lgmdp but my phone refuses to get detected inspite of me having all the updated drivers. tried in 3 different comps, uninstalling everything n starting over at least 3-4 times in each. the phone just doesn't get detected. in each comp, the first plug-in showed the installation of only 3 drivers instead of the reqd 4 and did not get detected in any of the subsequent attempts.
shed some light here, guys..
[edit]
I just tried Android Flash Recovery. log says,
"fastboot: erase:recovery
fastboot: download:00701000
fastboot: flash:recovery
writing 7344128 bytes to 'recovery'
flash_write_image: out of space"
:-/
also, upon removing and re-attaching the data chord, fastboot says,
"--suspend--
--suspend--
--reset--
EP1/out FAIL nfo=40 pg0=74000
--portchange--
usb_read() transaction failed
fastboot: oops!"
oops??!! wht the F...!!
Morphie said:
Hey,
i was flashing a new ROM, the installation was all completed but when i rebooted the system, its now stuck in fastboot mode.
Tried flashing with KDZ as well as lgmdp but my phone refuses to get detected inspite of me having all the updated drivers. tried in 3 different comps, uninstalling everything n starting over at least 3-4 times in each. the phone just doesn't get detected. in each comp, the first plug-in showed the installation of only 3 drivers instead of the reqd 4 and did not get detected in any of the subsequent attempts.
shed some light here, guys..
[edit]
I just tried Android Flash Recovery. log says,
"fastboot: erase:recovery
fastboot: download:00701000
fastboot: flash:recovery
writing 7344128 bytes to 'recovery'
flash_write_image: out of space"
:-/
also, upon removing and re-attaching the data chord, fastboot says,
"--suspend--
--suspend--
--reset--
EP1/out FAIL nfo=40 pg0=74000
--portchange--
usb_read() transaction failed
fastboot: oops!"
oops??!! wht the F...!!
Click to expand...
Click to collapse
What device do you have? And what ROM did you attempt to install?
I'm guessing the "log" is what got printed on your screen? Unfortunately there's no actual way to log whats happening on the Windows end of fastboot. That's all output from fastboot on the phone. From what I'm seeing in what you posted, you tried to flash a recovery that is too big for the recovery partition. This may be a by-product from flashing with KDZ or the failed ROM you installed.
Try this, open a command-prompt in the \bin folder where Android Flash Recovery ( AFR ) resides on your hard drive. Attach your device to your PC and type 'fastboot devices' ( without the quotes ) and hit Enter. The response should look similar to the following if the device is detected by fastboot.exe ( PC end ):
Code:
list of devices attached
1234567890ABCDEF ????????
If only the 1st line and 2nd blank line are printed and not the 3rd line then fastboot.exe doesn't detect your phone either.
If your phone is detected, then more than likely the ROM you installed messed up your partition tables.
shinobisoft said:
What device do you have? And what ROM did you attempt to install?
I'm guessing the "log" is what got printed on your screen? Unfortunately there's no actual way to log whats happening on the Windows end of fastboot. That's all output from fastboot on the phone. From what I'm seeing in what you posted, you tried to flash a recovery that is too big for the recovery partition. This may be a by-product from flashing with KDZ or the failed ROM you installed.
Try this, open a command-prompt in the \bin folder where Android Flash Recovery ( AFR ) resides on your hard drive. Attach your device to your PC and type 'fastboot devices' ( without the quotes ) and hit Enter. The response should look similar to the following if the device is detected by fastboot.exe ( PC end ):
Code:
list of devices attached
1234567890ABCDEF ????????
If only the 1st line and 2nd blank line are printed and not the 3rd line then fastboot.exe doesn't detect your phone either.
If your phone is detected, then more than likely the ROM you installed messed up your partition tables.
Click to expand...
Click to collapse
I own a LG p500. and yes, i ended up getting it detected in lgmdp. i think we're supposed to connect the phone within a few seconds of entering emergency mode. i was attempting to install AOKP's JB build [aokp_tass_jb 30.05.13] and i guess the build is corrupted cos i got my phone working into a stock ROM, rooted it and installed it all over again, and yes, leaving me stuck in fastboot all over again.
I repaired it back into stock, rooted and flashed an earlier backup of an iCySnap build. however, my phone does not catch any network. i tried rebooting but nothin seems to happen.
Is it because i flashed it directly from froyo? should i try flashing the new baseband? (this thing just occurred to me, i will try it now.)
Morphie said:
I own a LG p500. and yes, i ended up getting it detected in lgmdp. i think we're supposed to connect the phone within a few seconds of entering emergency mode. i was attempting to install AOKP's JB build [aokp_tass_jb 30.05.13] and i guess the build is corrupted cos i got my phone working into a stock ROM, rooted it and installed it all over again, and yes, leaving me stuck in fastboot all over again.
I repaired it back into stock, rooted and flashed an earlier backup of an iCySnap build. however, my phone does not catch any network. i tried rebooting but nothin seems to happen.
Is it because i flashed it directly from froyo? should i try flashing the new baseband? (this thing just occurred to me, i will try it now.)
Click to expand...
Click to collapse
Flash the OldBBfix if you had the old baseband
But remember you have to flash it every time after you flash a newBB ROM (Cyanogen 7.1+ and every other GB+ ROM)
Read this thread by RC @shinobisoft for more information - http://forum.xda-developers.com/showthread.php?t=2149636
Sent from my GT-I9082 using Tapatalk
akiratoriyama said:
Flash the OldBBfix if you had the old baseband
But remember you have to flash it every time after you flash a newBB ROM (Cyanogen 7.1+ and every other GB+ ROM)
Read this thread by RC @shinobisoft for more information - http://forum.xda-developers.com/showthread.php?t=2149636
Sent from my GT-I9082 using Tapatalk
Click to expand...
Click to collapse
v10 is the old BB, isnt it? i'd flashed it but it had failed. got it working by flashing a v20 version. anyways, none of this had ever occurred whenever i had rooted earlier, though i usually updated from froyo to gb before rooting and flashing. is that the reason? and is there anything i can do bout it??
Hey all,
Having an issue with RSD Lite. My phone is rendered useless and I am stuck in fastboot mode. I have the correct version of the fastboot files, I have done everything (I think) correctly. However, when I try to restore my phone and flash the file, I get an error saying: Failed flashing process. Unknown command [getvar]
What is wrong? Any help at all would be really appreciated.
-nrsmac
Hi, I wonder if anyone can help me get out of this...
[EDIT: The fastboot option 'Normal powerup' eventually worked and phone seems to be back to normal]
So I finally decided I'd had enough of the Lollipop bugs and decided to downgrade to Kitkat following this guide -
http://forum.xda-developers.com/moto-g/general/restore-to-kitkat-lollipop-moto-g-t3011553
Instead of typing the commands in separately I created a .bat file, and when I ran it I got the 'Preflash validation failed' error message for boot.img and the system.img files so I cancelled the bat file. However, the recovery.img file appears to have been written correctly.
When I now try to boot my phone it only gets as far as fastboot, which displays the error message 'UTAG "flashfail" configured as fastboot.'
Searching these forums shows me a lot of contradictory information so I'm hoping someone out there knows exactly what to do. If it's relevant, the bootloader has never been unlocked, the phone never rooted and it was running the latest UK Lollipop (5.02, 5.1?)
Thanks for any help!
In fastboot mode enter:
fastboot oem fb_mode_clear
Now your phone should boot normally.
I have run into trouble using this method: https://www.youtube.com/watch?v=hb0jKB8OFko to flash stock firmware
My device: Droid Maxx
Bootloader locked, not rooted
4.4.4 at the start of the process
I downloaded the suggested firmware and ran into problems.
The first time I attempted it RSD appeared to flash everything except system.img which got hung up and the bootloader gave me a message in red stating: "no valid piv block in sp for system" This occured with the 1FF-obake-maxx_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip 1.0.0 software.
Figuring I had the incorrect firmware i tried two other roms: 1. CFC-obake-maxx_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip 1.0.0 and 2. 1FF-obake-maxx_verizon-user-4.4.4-SU6-7-release-keys.xml.zip 1.0.0. Both failed with a different error message. This time RSD and the bootloader told me "preflash validation failed for gpt".
I have tried this with RSD 6.1.5 and 6.2.4
My suspicion is that I don't have the correct firmware, but I could be wrong.
The bad news is that the phone will not boot into recovery or normally. The good news is that the phone WILL enter bootloader mode and RSD WILL recognize it.
Anyways any help would be greatly appreciated.
Stanleywinthrop said:
I have run into trouble using this method: https://www.youtube.com/watch?v=hb0jKB8OFko to flash stock firmware
My device: Droid Maxx
Bootloader locked, not rooted
4.4.4 at the start of the process
I downloaded the suggested firmware and ran into problems.
The first time I attempted it RSD appeared to flash everything except system.img which got hung up and the bootloader gave me a message in red stating: "no valid piv block in sp for system" This occured with the 1FF-obake-maxx_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip 1.0.0 software.
Figuring I had the incorrect firmware i tried two other roms: 1. CFC-obake-maxx_verizon-user-4.4.4-SU6-7.2-release-keys.xml.zip 1.0.0 and 2. 1FF-obake-maxx_verizon-user-4.4.4-SU6-7-release-keys.xml.zip 1.0.0. Both failed with a different error message. This time RSD and the bootloader told me "preflash validation failed for gpt".
I have tried this with RSD 6.1.5 and 6.2.4
My suspicion is that I don't have the correct firmware, but I could be wrong.
The bad news is that the phone will not boot into recovery or normally. The good news is that the phone WILL enter bootloader mode and RSD WILL recognize it.
Anyways any help would be greatly appreciated.
Click to expand...
Click to collapse
Okay, as long as you can enter fastboot (bootloader mode) there is hope. That's the first thing.
Since RSD recognizes your phone then there is obviously something wrong with the flashing process. You can use either the 1FF obake-maxx or CFC obake-maxx firmware. The 1FF keeps your apps and data intact while the CFC firmware wipes everything off your phone and you start clean. I would recommend using the CFC so you do not anything left over from previous flashes. Also, make sure the entire firmware file is downloaded. I got only partial downloads( like 150/200 mb) several times when I tried to download the files. Both the 1FF and CFC should be about 900 or so mb each. Exactly what steps are you following? And where are you getting your downloads from?
classic757 said:
Okay, as long as you can enter fastboot (bootloader mode) there is hope. That's the first thing.
Since RSD recognizes your phone then there is obviously something wrong with the flashing process. You can use either the 1FF obake-maxx or CFC obake-maxx firmware. The 1FF keeps your apps and data intact while the CFC firmware wipes everything off your phone and you start clean. I would recommend using the CFC so you do not anything left over from previous flashes. Also, make sure the entire firmware file is downloaded. I got only partial downloads( like 150/200 mb) several times when I tried to download the files. Both the 1FF and CFC should be about 900 or so mb each. Exactly what steps are you following? And where are you getting your downloads from?
Click to expand...
Click to collapse
Thanks for your help, but it appears that I have resolved the issue. As it turns out, the software need to be extracted to and launched from a clean folder. I had been placing it in the same folder I had adb and fastboot. My guess is that having the other version of fastboot in the same folder as the XML file confused RSD and caused the problem.
Stanleywinthrop said:
Thanks for your help, but it appears that I have resolved the issue. As it turns out, the software need to be extracted to and launched from a clean folder. I had been placing it in the same folder I had adb and fastboot. My guess is that having the other version of fastboot in the same folder as the XML file confused RSD and caused the problem.
Click to expand...
Click to collapse
Great! Glad to hear you resolved your problem. :good: