adb sideload fails - can't mount anything - Moto G Q&A, Help & Troubleshooting

I have a Boost 1031 and I unlocked bootloader and rooted with no issues. Phone was 4.4.1 and auto-updated to 4.4.4. I installed TWRP and tried flashing CM13 which indicated 1031 was compatible. Couldn't install due to outdated bootloader version so followed post saying edit text out of rom to bypass and it will update automatically. I did, and it worked, but I just got the CM13 logo bootloop. Thought maybe I could go back to stock and take it slower with a stock 5.1 or GPE but can't "downgrade" now since CM13 did successfully flash.
via command in fastboot I am on bootloader version 411A.
I have tried:
adb sideloading factory image for Boost Falcon - failed due to partition error.
adb sideloading 5.1 optimized rom, CM12 and CM13 - failed due to not able to mount anything.
extracted and via fastboot:
4.4 stock factory image - successfully installed w/initial errors relating to downgrade as warned, stuck on 'unlocked bootloader' screen
5.1 optimized rom - successfully installed, stuck on loop of sad broken android on his side.
CWM recovery
3 versions of TWRP
Is there anything else I can try? I can still get into fastboot and the custom recovery.
Thanks!

static.chaos73 said:
I have a Boost 1031 and I unlocked bootloader and rooted with no issues. Phone was 4.4.1 and auto-updated to 4.4.4. I installed TWRP and tried flashing CM13 which indicated 1031 was compatible. Couldn't install due to outdated bootloader version so followed post saying edit text out of rom to bypass and it will update automatically. I did, and it worked, but I just got the CM13 logo bootloop. Thought maybe I could go back to stock and take it slower with a stock 5.1 or GPE but can't "downgrade" now since CM13 did successfully flash.
via command in fastboot I am on bootloader version 411A.
I have tried:
adb sideloading factory image for Boost Falcon - failed due to partition error.
adb sideloading 5.1 optimized rom, CM12 and CM13 - failed due to not able to mount anything.
extracted and via fastboot:
4.4 stock factory image - successfully installed w/initial errors relating to downgrade as warned, stuck on 'unlocked bootloader' screen
5.1 optimized rom - successfully installed, stuck on loop of sad broken android on his side.
CWM recovery
3 versions of TWRP
Is there anything else I can try? I can still get into fastboot and the custom recovery.
Thanks!
Click to expand...
Click to collapse
Try to flash the 5.1 Factory Firmware Image:
http://forum.xda-developers.com/showthread.php?t=2542219
http://forum.xda-developers.com/moto...mware-t3110795
From that point you can move on to custom ROMs if you wish

satanas17 said:
Try to flash the 5.1 Factory Firmware Image:
http://forum.xda-developers.com/showthread.php?t=2542219
http://forum.xda-developers.com/moto...mware-t3110795
From that point you can move on to custom ROMs if you wish
Click to expand...
Click to collapse
Yes I have tried that. The problem is that I can't flash anything because there is no recognized system. No matter what rom it is, it can't mount sd card, data, /dev/block/platform etc. After more research I think I may need to reformat the partitions but in adb I get an error of no superuser. I'm trying to see if I can do it in fastboot instead.

static.chaos73 said:
Yes I have tried that. The problem is that I can't flash anything because there is no recognized system. No matter what rom it is, it can't mount sd card, data, /dev/block/platform etc. After more research I think I may need to reformat the partitions but in adb I get an error of no superuser. I'm trying to see if I can do it in fastboot instead.
Click to expand...
Click to collapse
OK, finally got it working! I used fastboot to partition with the gpe image of the rom I was trying to flash, then fastboot to format. Then I went into recovery and tried to mount data/system/cache. Data was still not available, so I used recovery to format data and got it mounted. I tried a few different roms and finally was able to get cyanpop marshmallow to load up and run. I'm going to try and figure out what the difference is because I want CM13 nightly eventually. I tried to downgrade back to 4.4 stock but never could get past the downgrade errors when flashing in recovery, and flashing via fastboot or adb sideload would just fail.
Anyway, thanks for your help!

You seem to be making things more complicated than necessary. You should be aware Firmware Images can only be flashed via Fastboot. Flashing the GPE firmware image formatted userdata (/data) to EXT4. Stock ROMs will not boot if you have an EXT4 /data partition. See the FAQ in my Stock ROM collection thread.

lost101 said:
You seem to be making things more complicated than necessary. You should be aware Firmware Images can only be flashed via Fastboot. Flashing the GPE firmware image formatted userdata (/data) to EXT4. Stock ROMs will not boot if you have an EXT4 /data partition. See the FAQ in my Stock ROM collection thread.
Click to expand...
Click to collapse
OK that makes sense. I will read through your FAQ before attempting to flash anything else. Thank you for the information!

Related

Accidentally wiped everything

So in the process of updating my rom, I managed to damage my /data/ partition, meaning I now have no ROM on my phone. I've updated TWRP to the newest version, I've got a stock firmware on file and a custom firmware if needed, both CWM and TWP on file, I've tried flashing or running all of the above but I can't get anything to actually load to the phone. I've also tried loading a rom via USB-OTG but I can't get it to mount. Normally in this situation I'd run an odin update for the stock firmware but I can't find anything about that, and all the brick threads in XDA don't seem to be helping. Does anyone have some suggestions?
Edit: I do have fastboot access but no ADB. Sideload isn't working through TWRP and I don't know why.
You have to return to stock using flash boot... It happened to me as well...
Well, I tried http://forum.xda-developers.com/showthread.php?t=2542219 and now I'm looking at the "warning: unlocked bootloader" screen...

[Q] I just can't make my phone work!!PLEASE HELP!!

Hey guys, i'm having some SERIOUS problems with my 1st generation moto g XT1033.
Some days ago, i flashed stock android 5.0. Alright... So, i discovered that that were cm12 nightlies on the official cyanogenmod site and i flashed it. So, just after that i discovered that dual sim wasn't ported yet so i tried to change to stock 5.0, but my phone entered in a boot loop so i flashed stock 4.4.4, with no luck... now i flashed 5.0 but it's still not booting, i am now thinking about going back to CM12, which already have dual sim... the problem is that i dont know why, TWRP MTP isn't working, so now i just cant pass the CM12 zip to the phone because of that. please i need help i dont know what to do, if there's some way to flashing it without using TWRP's MTP. Thanks a lot and sorry about the english
pedrocarboni said:
Hey guys, i'm having some SERIOUS problems with my 1st generation moto g XT1033.
Some days ago, i flashed stock android 5.0. Alright... So, i discovered that that were cm12 nightlies on the official cyanogenmod site and i flashed it. So, just after that i discovered that dual sim wasn't ported yet so i tried to change to stock 5.0, but my phone entered in a boot loop so i flashed stock 4.4.4, with no luck... now i flashed 5.0 but it's still not booting, i am now thinking about going back to CM12, which already have dual sim... the problem is that i dont know why, TWRP MTP isn't working, so now i just cant pass the CM12 zip to the phone because of that. please i need help i dont know what to do, if there's some way to flashing it without using TWRP's MTP. Thanks a lot and sorry about the english
Click to expand...
Click to collapse
Bad idea, never try to downgrade... If you can still access fastboot you are VERY luck that your phone did not end up in a hard brick. :fingers-crossed:
Try and flash stock 5.0 from fastboot mode. And wipe everything including userdata.
Goodluck!
skyguy126 said:
Bad idea, never try to downgrade... If you can still access fastboot you are VERY luck that your phone did not end up in a hard brick. :fingers-crossed:
Try and flash stock 5.0 from fastboot mode. And wipe everything including userdata.
Goodluck!
Click to expand...
Click to collapse
Thanks for Helping!!! Just one question: How can i pass the stock zip to the phone to flash it if mtp is not working?Any suggestions? Because i think its not possible to flash 5.0 using fastboot, just on the stock recovery
update: I have just figured out that adb is working with CWM, which i have installed right now Yay!now I can push files from my computer!!
https://androidxda.net/how-to-unbrick-moto-g-1st-gen-2013-after-lollipop-5-0-android-update/ :laugh::laugh:
pedrocarboni said:
Thanks for Helping!!! Just one question: How can i pass the stock zip to the phone to flash it using if mtp is not working?Any suggestions? Because i think its not possible to flash 5.0 using fastboot, just on the stock recovery
Click to expand...
Click to collapse
If you have unlocked boot loader then go into fastboot mode and run "fastboot boot customrecovery.img" where customrecovery.img is CWM or TWRP. I recomment TWRP. From there you can adb sideload the zip. Only flash it if you know exactly what you are doing or you may end up in a hard brick.
skyguy126 said:
If you have unlocked boot loader then go into fastboot mode and run "fastboot boot customrecovery.img" where customrecovery.img is CWM or TWRP. I recomment TWRP. From there you can adb sideload the zip. Only flash it if you know exactly what you are doing or you may end up in a hard brick.
Click to expand...
Click to collapse
i used sideload flashing CM12,but i have recieved the error message "could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4 mount:failed to mount /dev/block/platform/msm_sdcc.1/byname/system: Invalid Argument
unmount of /system failed; no such volume detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and when i try mounting /system, CWM says Error mounting /system!
pedrocarboni said:
i used sideload flashing CM12,but i have recieved the error message "could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4 mount:failed to mount /dev/block/platform/msm_sdcc.1/byname/system: Invalid Argument
unmount of /system failed; no such volume detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and when i try mounting /system, CWM says Error mounting /system!
Click to expand...
Click to collapse
Do this at your own risk:
Your system partition is corrupt, you need to enter adb shell and format /system into ext4s. Search on google for the command as I do not have it on the top of my head. I believe it has something to do with make_ext4s function.
pedrocarboni said:
Hey guys, i'm having some SERIOUS problems with my 1st generation moto g XT1033.
Some days ago, i flashed stock android 5.0. Alright... So, i discovered that that were cm12 nightlies on the official cyanogenmod site and i flashed it. So, just after that i discovered that dual sim wasn't ported yet so i tried to change to stock 5.0, but my phone entered in a boot loop so i flashed stock 4.4.4, with no luck... now i flashed 5.0 but it's still not booting, i am now thinking about going back to CM12, which already have dual sim... the problem is that i dont know why, TWRP MTP isn't working, so now i just cant pass the CM12 zip to the phone because of that. please i need help i dont know what to do, if there's some way to flashing it without using TWRP's MTP. Thanks a lot and sorry about the english
Click to expand...
Click to collapse
Pedro, I have the same problem.
I can only access bootloader and recovery, but using adb sideload I can't flash any image (and version) that works.
I just get boot looping as you, and gpt.bin and motoboot.img files can't be flashed.
I've found that with Lollipop bootloader we can't install an older Android version.
My Moto G is now a paperweight, until the final stock Lollipop comes.
pedrocarboni said:
i used sideload flashing CM12,but i have recieved the error message "could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4 mount:failed to mount /dev/block/platform/msm_sdcc.1/byname/system: Invalid Argument
unmount of /system failed; no such volume detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and when i try mounting /system, CWM says Error mounting /system!
Click to expand...
Click to collapse
Hi, I experienced the same problem. Have you fixed your phone? Please give me some suggestion. Thank you.
Same problem with my Moto G 2013.
I've tried to downgrade and got problem. Now I can't flash an older motoboot.img and gpt.bin.
I'm using CyanogenMod 12, but every time when I boot, there is a line going down over the screen.
This line only disappear when I turn off and on the screen. Then everything backs to normal.
Is there a way to solve this?
This happened to me yesterday, i wento from my US Retail 4.4.4 to BR Retail 4.4.4 then via stock recovery flashing the OTA of 5.0, installed Xposed but gave me slow boots, like 5 min per boot, so i decided to downgrade, flashed 4.4.4 BR but after boot a black screen comes and doesn't go, think of flashing 4.4.2 US but the same isue, then decided to update again to 5.0 BR but stock recovery don't let me flash because an error, i flashed philz touch and do a factory reset, wipe data, cache, and everything, then flashed flashing 4.4.4 BR and then 4.4.2 US, the line down problem is nothing, only appears when you boot and, if you lock your phone for about 2-3 seconds, it dissappear (until you boot again), hope it helps, sorry for bad english
For all with bootloops, there is a major issue caused with a boot animation memory leak. Search on the forum to find the fix. You may need to delete the bootanimation binary.
skyguy126 said:
For all with bootloops, there is a major issue caused with a boot animation memory leak. Search on the forum to find the fix. You may need to delete the bootanimation binary.
Click to expand...
Click to collapse
skyguy126, I've not found any solution for this on forum.
Could you please show me a way?
For those that have problems downgrading, download this and follow this steps.
Once finished flash TWRP recovery and restore your nandroid.
Moto G not Booting, HELP
Hi everyone, I really need help with my moto G, it´s not booting into android after pressing the power button the moto logo comes up and the phone goes directly into fastboot displaying a message in pink color: version downgrade for boot
Failed to validate boot image.
I have been hours checking around for a solution and working now for the third day trying to solve the problem with no luck.
I have downloaded the original firmware for the device, tried to flash it and it doesn´t work, tried other countries firmware and they doesn´t work either.
The process will be partially ok but as it goes to flash the boot.img, recovery and system files it will give an error.
I also tried bootloader refresh, bootloader bricker and blankflash to try fix any possible bootloader issues.
The device has a locked bootloader since it is a moto g from AIO.
Please Help, It´s my only device and I cannot afford another one at this time.
There´s a few images from the flash process and device info
:crying:
You need to unlock your bootloader in order to flash various ROMs.
but in this model the bootloader cannot be unlocked it is CID 0X0010
How did this happen to your phone? What model phone do you have?
It´s a Moto G 2013, xt1032
It all begin trying to install a signed stock firmware that was supposed to be for that specific model: AIO_XT1032_4.4.2-KXB20.9-1.10-1.9_CFC_1FF.xml
During the flash process it send some error messages but the process keep running until it finishes, once the device reboot it went straight to fastboot and since then I haven´t been able to get it back working.
Are you manually flashing each partition?
Maybe try a 4.4.4 ROM.
Yes, I have. I´ve also tried other signed firmware that have a .bat file that run all by itself but neither way it worked. It comes up with the error message: Invalid signed Image and below Preflash Validation Fail

[Q] No OS||Stuck at bootloop

So i decided to install the CM 12 on my MotoG.I downloaded the files and followed the instructions.I wiped cache,dalvik,data and did Format System but the installation failed.So I reboot my phone only to see that it was stuck at a bootloop.I get back to TWRP and I see that there was no OS installed.I decided then to flash 4.4.4 which worked,but after rebooting i was in a bootloop with no OS once again.I installed PhilZ Touch to see what's wrong.It says that I can't mount the system and the sdcard.I've tried Sideloading,adb pushing but everything fails...Is there anything i can do?Help is much appreciated
Have you tried to flash a stock ROM via fastboot commands?
Yes nothing happened..still stuck at bootloop...
nikoschasapis said:
Yes nothing happened..still stuck at bootloop...
Click to expand...
Click to collapse
which stock rom did you try to flash using fastboot?
if it's the stock 4.4.4 it's probably going to fail, you need certain things to do (you can search around here) if you're using xt1033, you can search for (xt1033 stock) there's a guide that will get you up and going. On my moto g that has flashed stock 5.0.2 and cm12, i found out that i can't use the normal method to flash the stock 4.4.4 rom, rather i was forced to flash the 5.0.2 rom, since the fastboot command fails at almost everything, which would leave the phone unusable
oh yeah, here's the guideRESTORE TO STOCK
Nevermind.I formatted the data and it let me adb push the stock 4.4.4
ROM

[Q] No Rom, failure when flashing

Hi all. I own a Moto G xt1032 UK version. (GSM right?)
I was on 4.4.4 Epsilon ROM but I wanted to flash stock 4.4.4, so I used a tutorial I found on youtube that set me up to stock 4.4.2, then I upgraded to 4.4.4 and THEN there was another update to 5.0.1. So as you can guess, I upgraded to lollipop and that was it - bootloop. I have tried flashing other roms through fastboot and nothing worked, I get an error when I flash ''system'' that says ''image is too large'' once all is done, phone restarts and its stuck on bootloop once again. The bootlogo changes when I flash different rom etc. But I don't know what to do, any ideas? :/ I have also tried to flash a custom recovery and sideload the Epsilon ROM but I only get an error in my command line that says no device connected after I hit the command. Any suggestions guys? I appreciate any sort of help, thanks guys.
I'll also add that I think I have the 41.18 bootloader if it helps (it says so in the bootloader settings)
When flashing a ROM in fastboot, are you also flashing the gpt file?
Yeah. I flash everything there's to flash as all tutorials instruct.
To try and get your phone up and running, flash a custom recovery from fastboot. Once the recovery image has been flashed, use the phone's volume buttons to boot into recovery. If you can get into recovery, try and flash a custom ROM.
Ah, I forgot to add. When I attempt to flash anything from my storage it says some sort of error coun't mount /sdcard and others when the recovery opens up. I tried flashing other recoveries, TWRP, CWM both show the exact same errors..Can't mount SDcard etc. :/ That is why I tried the sideload method which didn't work for me either.
You're flashing recovery for the falcon?
Yes..for falcon. I've done it a bunch of times before, however I never had the unable to mount error in the recovery..
I don't have my moto g on me but I found Philz Touch (based on CWM) worked besr for me after i switched back from GPE to CM12. I was getting weird error messages in TWRP.

another BRICK in the wall

Hi, I got shield tablet, first version, previous owner brick the device, it stuck on AICP logo and not booting. I can enter in fastboot mode, device is unlocked, but it display bootloader version UNDEF_BUIDL, when I try go to recovery mode I got nvidia logo and black screen. I also try install the stock recovery, do all steps in official instructions, no errors and no changes, It's still bricked on custom rom logo. Any chances to fix it? I'don't know what to do now
flamner said:
Hi, I got shield tablet, first version, previous owner brick the device, it stuck on AICP logo and not booting. I can enter in fastboot mode, device is unlocked, but it display bootloader version UNDEF_BUIDL, when I try go to recovery mode I got nvidia logo and black screen. I also try install the stock recovery, do all steps in official instructions, no errors and no changes, It's still bricked on custom rom logo. Any chances to fix it? I'don't know what to do now
Click to expand...
Click to collapse
You flashed manually via fastboot every file? Even the bootloader?
if you mean "fastboot flash boot boot.img", then yes
Now i can enter in recovery mode, and run TWRP, but i takes veeeery long time to boot :/ In TWRP wipe data failed, there are errors in data and cache partition, I can't format it or repait, It shows that partitions are presents, but they have 0MB size
Perhaps try flashing new firmware? It should be somewhere on Steel01's thread (5.0 bootloader, or nougat bootloader or something like that) for lineageos 14.1, it is a requirement to run los on this device and it fixes some bootloader stuff. Though, you may want to get a second opinion on this one because I am no developer whatsoever.
fpozar said:
Perhaps try flashing new firmware? It should be somewhere on Steel01's thread (5.0 bootloader, or nougat bootloader or something like that) for lineageos 14.1, it is a requirement to run los on this device and it fixes some bootloader stuff. Though, you may want to get a second opinion on this one because I am no developer whatsoever.
Click to expand...
Click to collapse
I can't flash rom in TWRP, when I try I get status failed :/ I don't know what to d next :/
Problem is in mounting cache and data partition in internal memory. I think l tried all ways to do that, last one was in adb shell, mount /system ok, mount /data and mount /cache not ok
my conclusions:
I can't flash anything on this tablet, even recovery, I figure it out because I try to flash TWRP version 3.2.1 it works only when i run boot TWRP in fastboot on computer, when I do it in device(run in fastboot mode, select recovery) i got after several minutes TWRP version 2... So, it means that internal memory is broken?
Mine does that too flamner, not sure what to do. I will try a bootloader flash perhaps

Categories

Resources