I made the mistake of reading G2x when it really said LG 2X in a forum and flashed the flash.bat file. Now my phone's partitions are jacked
I get the error failed executing command 14 NvError 0x120000
command failure: partition download failed
After I did the flash.bat file it was like I had the Optimus 2x. Now I do not have a working baseband even though I have tried a nandroid back up that is stock. It gets stuck in a loop at the G2X screen. I have a feeling I'm stuck unless there is a flash.bat file for the G2x that I can flash through nvflash
There is a G2X firmware thread in Development sub-forum, but there is no guide and I could not tell if anyone actually successfully flashed the below and restored to stock with it.
http://www.multiupload.com/G1PX7W2D0I
Related
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??
I'm trying to set a up a device for a relative of mine who, whilst not the most tech savvy of people, has a habit of breaking things accidentally and likes to push buttons. I've boot unlocked their device, flashed on a custom recovery and rooted their device for them, but when trying to stick a stock recovery back on (as a .img file) I keep getting a "Preflash validation failed" error when I fire off the flash command from Moto-Fastboot.
Has anyone got a version of the KK stock recovery that works via this method or who knows of a guide to doing this (preferably via the moto-fastboot or adb tools as I'd rather not install anything else on my laptop)?
Moto g
charliesutton said:
So I have a Moto G with an unlocked bootloader but no root. So I wanted to flash an android L cyanogen mod rom onto it and I first of all had to install custom recovery. I decided to use twrp. I downloaded all the latest drivers from motorola and the adb folders. I downloaded the recovery image and put it into the 'platform-tools' folder with 'fastboot.exe' in it as well (the boot image was specifically for the moto g btw) and flashed it onto the phone. It installed it but when I went on recovery the boot up image showed for about a quarter of a second but afterwards I was returned back to the moto g fastboot screen with some returned text on the bottom saying 'Boot up failed'. I had followed every step and I tried redoing the process but that didnt work. So I restored my device so I got the stock recovery and I tried cwm instead. This returned the same error message. Im not really sure where I went wrong in the process.
I also have some other questions as well though. I thought that maybe if I put the boot.img boot image from the cyanogen mod folder into the platform tools folder I could open cmd and type 'fastboot boot boot.img' and maybe it would flash it straight on however I dont want 'Boot up failed' from both 'Recovery' and 'Normal Powerup' in the fastboot menu. I was also wondering if I could convert the zip file for the custom rom to .tar.md5 and maybe flash it from odin? However whenever i watch odin tutorials they always use a samsung device and it also says that its for samsung. Or preferably just some help to get past the 'Boot up failed' error would be appreciated. Thanks
Click to expand...
Click to collapse
Odin is a Samsung factory restore tool. Rsd lite is for motorola. I just got got this phone today so I'm not familiar with it yet to know anther way, sounds like you may just need to download your stock firmware and rsd. that should get ya back to stock at least
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
I'll start by apologizing if this has been solved elsewhere I have searched but found no answers.
I have the global variant and was rooted with twrp. I wanted the ota update so I unrooted and updated. Today I had some time so I flashed twrp wiped and entered bootloop. I attempted a full factory reset through twrp but still bootlooped. I have fastboot rom and have attempted to use miflash to fix it but get the "cannot found lock.bat" error though when first starting miflash I get the "can't find flash script" error. The drivers are properly installed yet the error persists. I cannot get adb to sideload which is, I'm guessing because of the wipe removing debugging mode? Is there any way to get the ROM image to the phone(I tried adb push command but says no device. Yet flashing recovery works so I know it's connected and recognized) so I can flash it via TWRP or the stock recovery img to flash and work from there? I'm kind of at a loss here. Am I now the proud owner of a very neat paper weight? I seriously hope not as I'm not exactly made of money and I've only owned the phone for a couple months.
Any and all help is greatly appreciated.
Update
I have managed to get adb push to start sending global v10.2.2.0 to the root folder. I'm hoping this will allow me to flash from twrp.
Mota420 said:
I'll start by apologizing if this has been solved elsewhere I have searched but found no answers.
I have the global variant and was rooted with twrp. I wanted the ota update so I unrooted and updated. Today I had some time so I flashed twrp wiped and entered bootloop. I attempted a full factory reset through twrp but still bootlooped. I have fastboot rom and have attempted to use miflash to fix it but get the "cannot found lock.bat" error though when first starting miflash I get the "can't find flash script" error. The drivers are properly installed yet the error persists. I cannot get adb to sideload which is, I'm guessing because of the wipe removing debugging mode? Is there any way to get the ROM image to the phone(I tried adb push command but says no device. Yet flashing recovery works so I know it's connected and recognized) so I can flash it via TWRP or the stock recovery img to flash and work from there? I'm kind of at a loss here. Am I now the proud owner of a very neat paper weight? I seriously hope not as I'm not exactly made of money and I've only owned the phone for a couple months.
Any and all help is greatly appreciated.
Click to expand...
Click to collapse
Update 2 phone working but still confused.
Pushing the ROM via ADB did indeed allow me to flash from twrp and restore the phone. My question now is why did it happen? Is the new OTA MIUI 10.3... update incompatible with twrp or did something anomalous happen with the flash? I flashed exactly the same method I used with the 10.2.2 ROM a few weeks ago....
OTA's should only be used when completely stock! Even though you uninstalled root, there were still system modifications that more than likely caused your issues. The fastboot version of the firmware is different than the TWRP image. You can not flash a TWRP image via fastboot, hence the missing scripts and bat files. If you had actually downloaded the fastboot image, you would have had a flash_all.bat file that would have returned your device completely to stock with a single run of that file.
Thanks for the reply and information. I actually expected my issues to begin upon installing the ota update and was quite surprised that it updated without error. What confuses me is how flashing twrp after the update caused the issues. I went through the normal process when flashing twrp and still ended up bootlooped. I made the mistake of thinking boot.img was the old stock recovery i renamed when i first rooted and flashing that as recovery. Obviously this was not the recovery file but fastboot. It was then that panic mode kicked in and things went from bad to worse. I formatted planning to flash the stock rom via adb which didn't work. Given that I never touched the fastboot image on the phone I'm confused on how the bat files and scripts weren't found.
I'll admit I'm not extremely well versed in this area.
Is it possible that the ota update contained different bat files and scripts than the previous rom had? Which would cause miflash to not recognize them when attempting to flash an older rom? I'm sorry if my questions are ignorant lol. I'm a process guy and a troubleshooter by nature which means even though I've resolved the issue, I need to figure out what caused it.
Would flashing fastboot to the phone as the recovery image have screwed up the bat and scripts? Having two instances of boot.img on the partition messed it up maybe? Was it the formatting even though I was still able to boot into fastboot after? Or was it something that happened during the unrooting and updating that messed it up and it didn't manifest until I flashed twrp? Like I said the update worked fine and the phone was fully functional until I tried to reroot.
Thanks again for taking the time to help. It's definitely appreciated.
Mota420 said:
Thanks for the reply and information. I actually expected my issues to begin upon installing the ota update and was quite surprised that it updated without error. What confuses me is how flashing twrp after the update caused the issues. I went through the normal process when flashing twrp and still ended up bootlooped. I made the mistake of thinking boot.img was the old stock recovery i renamed when i first rooted and flashing that as recovery. Obviously this was not the recovery file but fastboot. It was then that panic mode kicked in and things went from bad to worse. I formatted planning to flash the stock rom via adb which didn't work. Given that I never touched the fastboot image on the phone I'm confused on how the bat files and scripts weren't found.
I'll admit I'm not extremely well versed in this area.
Is it possible that the ota update contained different bat files and scripts than the previous rom had? Which would cause miflash to not recognize them when attempting to flash an older rom? I'm sorry if my questions are ignorant lol. I'm a process guy and a troubleshooter by nature which means even though I've resolved the issue, I need to figure out what caused it.
Would flashing fastboot to the phone as the recovery image have screwed up the bat and scripts? Having two instances of boot.img on the partition messed it up maybe? Was it the formatting even though I was still able to boot into fastboot after? Or was it something that happened during the unrooting and updating that messed it up and it didn't manifest until I flashed twrp? Like I said the update worked fine and the phone was fully functional until I tried to reroot.
Thanks again for taking the time to help. It's definitely appreciated.
Click to expand...
Click to collapse
OTA's are not a complete image. It is a partial update that only replaces what it has to replace. If MiFlash dis not recognize the image, it was either the wrong image or a corrupt image.
Sometimes updates to the system and recovery partitions fix exploits that things like root and TWRP take advantage of.
Fastboot isn't something you flash to the phone. It is a command line used to flash a dull factory image to the device properly. You do not need MiFlash to flash a fastboot factory image. All you do is extract the full image to your ADB folder unless it is system wide, boot your device into the bootloader, connect ir to your PC, and run the flash_all.bat command contained in the folder you extracted. A command prompt window will open, everything will complete after about a few minutes the window will close, and your phone will reboot.
So the "fastboot" rom is a rom designed to be flashed using fastboot? The miflash error was given because the rom I was trying to flash was corrupted. That makes sense as I'd never known of a fastboot rom before. But it has been a few years since I rooted and romd my phone. I always did the typical flash from the rom image from twrp. I'm still not sure how I got myself in a boot loop unless when I wiped after flashing twrp I accidentally selected another option that erased more than I wanted.. Which makes perfect sense. I knew it had to be an ID10T error lol.
Thanks for the explanation.