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
Related
Hey everyone,
Yesterday i tried flashing the latest CM12 nightly straight onto my Moto G over stock KitKat. After i flashed the ROM, i tried booting and noticed it was taking a lot longer than normal to boot. Ten minutes had gone past so i tried rebooting it again and the same thing happened, just got stuck booting for ages.
So i decided to boot into recovery and do a factory reset to see if this would make any difference. But even after doing this the phone still wouldn't boot, so i decided to just flash the stock KitKat ROM back onto the phone and forget about all the Lollipop stuff.
The KitKat ROM wasn't on my phones storage so i downloaded it from the internet and flashed it via fastboot using and included Windows batch file. I've used this method numerous times to get me out of situations like this and it's always worked, but this time no!
Tried booting after flashing the new stock ROM and now it just keeps going to the 'Warning, bootloader unlocked' screen and then booting back in a loop.
When i boot into ClockworkMod recovery it gives me these errors:
Can't mount /cache/recovery/log
Can't open /cache/recovery/log
Can't mount /cache/recovery/last_log
Can't open /cache/recovery/last_log
Can't mount /cache/recovery/last_install
Can't open /cache/recovery/last_install
And if i attempt to format /data, it says this:
Error mounting /data
Error formatting /data
I hate asking for help like this but unfortunately i don't have much option this time, no idea what to do despite searching forums for many hours.
Please help, any advice would be greatly appreciated!
Bump
You can try getting into fastboot and run commands fastboot erase userdata and fastboot erase cache from your computer to pretty much factory reset the phone.
Sent from my Moto X 2014 Pure Edition
Pursain said:
You can try getting into fastboot and run commands fastboot erase userdata and fastboot erase cache from your computer to pretty much factory reset the phone.
Sent from my Moto X 2014 Pure Edition
Click to expand...
Click to collapse
Thanks for the response. I tried entering the commands you suggested but the problem is still the same, phone stuck in the 'Warning, bootloader unlocked' loop. Does anyone have any other ideas? Really need some help with this, my little Moto has been dead for days!
And just an update on the situation, i noticed that if i go into CWM and select 'Wipe and Format Options' then 'Custom Format Options', choosing to format the cache and /data/media (/sdcard) options will stop the errors stated in the original post, but when i try flashing the ROM again the errors come straight back!
V3-571G said:
Thanks for the response. I tried entering the commands you suggested but the problem is still the same, phone stuck in the 'Warning, bootloader unlocked' loop. Does anyone have any other ideas? Really need some help with this, my little Moto has been dead for days!
And just an update on the situation, i noticed that if i go into CWM and select 'Wipe and Format Options' then 'Custom Format Options', choosing to format the cache and /data/media (/sdcard) options will stop the errors stated in the original post, but when i try flashing the ROM again the errors come straight back!
Click to expand...
Click to collapse
So sad to hear your Moto dead for the last days. Could you tell me more about your Moto? Can it turn off? Get into fastboot? Do you have recovery (stock or custom? Etc.
Sent from my Moto X 2014 Pure Edition
Pursain said:
So sad to hear your Moto dead for the last days. Could you tell me more about your Moto? Can it turn off? Get into fastboot? Do you have recovery (stock or custom? Etc.
Sent from my Moto X 2014 Pure Edition
Click to expand...
Click to collapse
Yeah it sucks having a pretty much lifeless Moto, kinda scary as well not knowing if i'll be able to get it working again! But in response to your questions, i can turn it off and get into fastboot, i'm also able to boot into my recovery which is Philz Touch (ClockworkMod). If you take a quick look at the original post, i updated it a short while ago to show more details about the errors which are displayed.
Bump, still dead!
V3-571G said:
Bump, still dead!
Click to expand...
Click to collapse
If you can get into fastboot you can flash the stock firmware (not backup) back onto your phone that way. I have used fastboot many times to restore my xt1028 Moto G many times after seemingly bricking it. You will need the stock firmware for your phone to do this.
Here is a tutorial:
http://forum.xda-developers.com/showthread.php?t=2542219
and here is a link to moto firmwares:
http://motofirmware.com/
Hope this helps.
classic757 said:
If you can get into fastboot you can flash the stock firmware (not backup) back onto your phone that way. I have used fastboot many times to restore my xt1028 Moto G many times after seemingly bricking it. You will need the stock firmware for your phone to do this.
Here is a tutorial:
http://forum.xda-developers.com/showthread.php?t=2542219
and here is a link to moto firmwares:
http://motofirmware.com/
Hope this helps.
Click to expand...
Click to collapse
Thanks for taking the time to respond to my request for help. I have already tried flashing the stock ROM via fastboot mode but it makes no difference to the situation, even though the new ROM flashes perfectly without error, when i try to boot it just gets stuck in the reboot loop on the 'Warning, bootloader unlocked' screen. I have no idea what to do now!
V3-571G said:
Thanks for taking the time to respond to my request for help. I have already tried flashing the stock ROM via fastboot mode but it makes no difference to the situation, even though the new ROM flashes perfectly without error, when i try to boot it just gets stuck in the reboot loop on the 'Warning, bootloader unlocked' screen. I have no idea what to do now!
Click to expand...
Click to collapse
I would suggest you try to install a custom recovery through fastboot (I use TWRP 2.7.1.0)
Just replace the stock recovery with TWRP in the fastboot file and use the command "flash recovery recovery.img" then reboot into recovery(hold power and volume down button down together for about ten seconds, release and you should see the fastboot screen. Then press recovery and then wipe>advanced>wipe ONLY cache and dalvik and then reboot)
See if that does the trick.
Try this: http://forum.xda-developers.com/showpost.php?p=58116154&postcount=14
You have not stated your model. Don't use batch files to fastboot flash the firmware. Make sure the image is 4.4.4.
classic757 said:
I would suggest you try to install a custom recovery through fastboot (I use TWRP 2.7.1.0)
Just replace the stock recovery with TWRP in the fastboot file and use the command "flash recovery recovery.img" then reboot into recovery(hold power and volume down button down together for about ten seconds, release and you should see the fastboot screen. Then press recovery and then wipe>advanced>wipe ONLY cache and dalvik and then reboot)
See if that does the trick.
Click to expand...
Click to collapse
lost101 said:
Try this: http://forum.xda-developers.com/showpost.php?p=58116154&postcount=14
You have not stated your model. Don't use batch files to fastboot flash the firmware. Make sure the image is 4.4.4.
Click to expand...
Click to collapse
Thanks very much for the responses. Unfortunately i already had Philz ClockwordMod recovery installed on the phone and had attempted the various wipe options a number of times without any success. However, i thought that as i'd only tried flashing the UK ROM to the device, i would attempt flashing a different ROM just to ensure there wasn't an issue here somewhere. I downloaded the stock US ROM and after extracting the archive i ran the Windows batch file to flash the files onto the phone. After the process had completed i rebooted the phone (Didn't bother going into recovery and wiping/formatting cache) and to my surprise the phone booted up completely fine! So weirdly it seems that just flashing a different ROM did the trick. But anyway, my Moto is alive again now, i'm very pleased to say the least!
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.
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!
Hi everyone. I'd appreciate it if I got some help fixing my Moto G as it's been gathering dust ever since I couldn't boot into the recovery and stuck in the bootloader. I accidentally deleted the OS and when I try to install the stock rom, it just goes straight back to the bootloader. I really want to get this phone working again. When I try installing a recovery, it says "Mismatched Partition Size". It's the same with TWRP and CWM. My goal is to revert back to the stock ROM, which is 4.4.4 Boost Mobile. Manually flashing the ROM in sequences didn't work.
If any of you can, please help me.
Thanks in advance.
Anyone flashing a custom recovery on Falcon gets this same error. Ignore it. Your issue is something else.
Latest TWRP: http://forum.xda-developers.com/showpost.php?p=57672469&postcount=1
What is the issue? Unlocked my moto g falcon, then tried to install twrp 3 but an error occurrs: partition size doesn't match. Have been searching for solutions for two hours now. Can anyone help?
schoebi_zh said:
What is the issue? Unlocked my moto g falcon, then tried to install twrp 3 but an error occurrs: partition size doesn't match. Have been searching for solutions for two hours now. Can anyone help?
Click to expand...
Click to collapse
Solved: I had to update the bootloader first.
I've been getting the same recovery partition size doesn't match error. I've tried TWRP 3.0.0.0.2 and 3.0.0.0 for falcon and get this error with both. I've rooted HTC, Sony Xperia and Nexus devices before without any problems.
The previous poster said he updated the (I'm guessing Motorola) bootloader. Where and how do I find this update.
My bootloader is: 41.1A (sha-80481ae, 2015-04-10 14:30:20) The phone is a 1st gen Moto G 1GB/16GB.
David _J_D said:
I've been getting the same recovery partition size doesn't match error. I've tried TWRP 3.0.0.0.2 and 3.0.0.0 for falcon and get this error with both. I've rooted HTC, Sony Xperia and Nexus devices before without any problems.
The previous poster said he updated the (I'm guessing Motorola) bootloader. Where and how do I find this update.
My bootloader is: 41.1A (sha-80481ae, 2015-04-10 14:30:20) The phone is a 1st gen Moto G 1GB/16GB.
Click to expand...
Click to collapse
41.1A is the latest available bootloader
and the error of the mismatched partition can be ignored, just reboot to twrp after you flashed it and it will be fine
Just tried to reboot into TWRP, but I got the robot with a red triangle and 'no command'.
I'll try reflashing TWRP and report back later
Davdi_j_d said:
Just tried to reboot into TWRP, but I got the robot with a red triangle and 'no command'.
I'll try reflashing TWRP and report back later
Click to expand...
Click to collapse
After you flashed twrp, don't reboot using fastboot command, just power down using the power button and boot to twrp using the power+volume down button. Just try that and see if it successfull.
I had same issue, after HOURS i found out why, thanks to this guide:
http://www.droidthunder.com/root-install-twrp-recovery-moto-g-2013/
ALL OTHERS guide i read, included the istruction on twrp site itself, was wrong.
after you use fastboot to flash twrp, you must NOT restart, but simply:
After successfully installing the TWRP recovery, on your phone (in fastboot mode) go to the Recovery option by pressing volume down button and then press volume up button to select it.
Click to expand...
Click to collapse
like this, FINALLY, my motog loaded the twrp.
hope this will help others with this same issue, to save the 2 hours i lost, lol.
Hi.
A friend gave me his Moto G1 2013 to install Linage OS but I'm really having troubles with it, first of all it doesn't allow me to install TWRP, when I type fastboot flash recovery recovery.img it says that it installs but it doesn't, when I try to boot on it it just doesn't boot, the way I had access to TWRP was typing fastboot boot recovery.img...
When I got in I did the first step when you install a new Custom ROM that is wipe system, cache and dalvik cache, then I tried to install the ROM zip file but it gave me "error 7" I looked for solutions and I found one that is modifying updater-script file, I did it but it gave me another error about mount system, I looked for solutions too and I found one that is modifying file system format to anotherone and then bringing it back to the original format but still having the same error.
After that I decided to go back to stock ROM, I have flashed many times the stock ROM with fastboot commands but it just doesn't boot into the OS, when I try to boot the phone it boots into bootloader again... Any solution to this? Is it a hardware problem? Please help me I'm so embarrased with my friend.
Same thing happened to me!
Basidialfiddle said:
Hi.
A friend gave me his Moto G1 2013 to install Linage OS but I'm really having troubles with it, first of all it doesn't allow me to install TWRP, when I type fastboot flash recovery recovery.img it says that it installs but it doesn't, when I try to boot on it it just doesn't boot, the way I had access to TWRP was typing fastboot boot recovery.img...
When I got in I did the first step when you install a new Custom ROM that is wipe system, cache and dalvik cache, then I tried to install the ROM zip file but it gave me "error 7" I looked for solutions and I found one that is modifying updater-script file, I did it but it gave me another error about mount system, I looked for solutions too and I found one that is modifying file system format to anotherone and then bringing it back to the original format but still having the same error.
After that I decided to go back to stock ROM, I have flashed many times the stock ROM with fastboot commands but it just doesn't boot into the OS, when I try to boot the phone it boots into bootloader again... Any solution to this? Is it a hardware problem? Please help me I'm so embarrased with my friend.
Click to expand...
Click to collapse
Hi! I tried something similar with a similar result. I first unlocked my Moto G's bootloader. Then installed TWRP using fastboot. After that I tried flashing Resurrection Remix rom which failed. I've been stuck in a kind of bootloop since then. My handset powers up, finds something wrong, tries to go into recovery, fails and does this over and over again.
Since I am able to boot into bootloader mode, I tried to flash the stock rom by following instructions from this thread https://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I have tried different variations from many different forums (fora?) all with the same result. Still stuck in the bootloop-thingie.
Btw, I also tried the unbricking guide from this thread
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788 without any success. My phone shows up as a Motorola ADB device and also as XT1033 in Device Manager when its plugged in.
Anyone know anything to help me out?
gaurav.kar said:
Hi! I tried something similar with a similar result. I first unlocked my Moto G's bootloader. Then installed TWRP using fastboot. After that I tried flashing Resurrection Remix rom which failed. I've been stuck in a kind of bootloop since then. My handset powers up, finds something wrong, tries to go into recovery, fails and does this over and over again.
Since I am able to boot into bootloader mode, I tried to flash the stock rom by following instructions from this thread https://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I have tried different variations from many different forums (fora?) all with the same result. Still stuck in the bootloop-thingie.
Btw, I also tried the unbricking guide from this thread
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788 without any success. My phone shows up as a Motorola ADB device and also as XT1033 in Device Manager when its plugged in.
Anyone know anything to help me out?
Click to expand...
Click to collapse
Hi, I found the solution time ago, sorry for answering to late, hope I can still be helpful.
Well, what I did is, I booted into TWRP, then I did a total format to the storage, after that I did something kind of crazy, I switched my storage format to anotherone and then I turned it back to how it was before (example: I was on fat32, I switched to exFAT and then I switched again to fat32) after doing that I tried to flash LinageOS and it allowed me, it booted and now my friend has Android Oreo on his Moto G1
Hope it works for you mate, those situations are very frustrating, good luck