[Q] Bricked My Moto G, Please Help! - Moto G Q&A, Help & Troubleshooting

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!

Related

IT WAS THE FINAL STEP... and it did not work. (Stuck on boot loader warning screen)

FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Original post:
SHORT VERSION:
My god this has been one crazy root journey.
I have done absolutely EVERYTHING I could pull up on google to fix my phone, and what seemed to be the final piece to the puzzle, still has not fixed anything.
My phone is bricked, and i would really appreciate help at this point.
The current problem:
When I turn on my phone, it vibrates, and displays the WARNING BOOT LOADER UNLOCKED screen, and stays there forever.
I can access my boot loader, and recovery, but I dont know what to do at this point.
I tried a quick flash stock recovery kit kat with moto tool AIO, and it didnt help.
Any ideas?
LONG VERSION (backround info may help to understand the current issue)
Now, if you want to know what began all of this, continue reading, otherwise the above is my current issue.
After successfully unlocking and rooting my phone
I downloaded SWITCHME, an app that lets you create multible users on the phone. the instructions say that you can use a sub account to test and mess around with anything because you can simply go back to the admin account that has everything untouched.
That was a lie.
1.I deleted .setup, along with a few other things THAT WHERE NOT FLAGGED AS IMPORTANT, assuming the phone would still work. and my phone went bonkers, displaying this infinite message: UNFORTUNATELY, SETUP HAS STOPPED. It was impossible to use the phone, and I could only access bootloader.
2.After endless googling, driver downloading, xda mod installing, I managed to set up my boot loader to do the guide restore stock firmware:http://forum.xda-developers.com/showthread.php?t=2542219
Sadly, I flashed the wrong model number package, I was flashing x35, when I later discovered that my phone is x45.
Flashing the x35 firmware bricked my phone further, to where it would "fail to boot up" and would only display bootloader over and over after attempting to turn the phone on.
3. Simple, I realized I flashed the wrong thing, so I downloaded the x45 firmware from the firmware teem on this website, flashed all of the commands, and bam, the phone starts up with the boot loader warning, and DOES NOT get stuck in the previous boot loader issue I had.
But now the phone wont get past that warning screen so... now im pissed.
Please, if anyone can help me I would greatly appreciate it, Im so close to getting my phone back...
EDIT 2: Looks like the phone wont stay shut down, I realized that if I dont open up boot loader, it will turn itself on and display the warning message.
EDIT:
The stuffs I have, ready to try anything:
CWM touch mod
Moto Tool AIO
Minimal ADB and Fast boot
RETUS x1045 factory firmware
All directories, folders, cmd commands are set up and working properly between all of the programs.
The phone appears to be responding to all cmd commands properly.
I also have the windows one touch super boot root method. (he superboot-windows.bat )
Im afraid to try anything major after freshly flashing the x45 firmware that seemed to bring me one step closer without the help of someone else.
I restored stock to my phone using this link yesturday http://www.ibtimes.co.uk/how-restore-motorola-moto-g-stock-firmware-1447290
it may work for you
I have almost the same problem as if the fastboot not install anything despite not display errors
great that you got it done.
maybe my few cents about my "bricking" story. (xt1032 moto g)
yesterday i wanted to change the rom from cm11 nightly to another custom rom like ehndroix/carbonrom...
first i thought that will be done in a few mins, after having already flashed a custom rom.
then the story began, getting adb work, but, 2weeks ago everything was setup and went fine. dunno why my laptop lost the "drivers".
thats the link which solved that problem: tinyurl . com / kgffjh4 [sorry cant post links outside of xda yet, spam protection]
so after a few hours of getting that fixed i, i began flashing.
suddently i got stuck in bootscreen (ehndroix logo for example)...
then i wanted to go back with my previous backup made internaly of clockworkmod. though i couldnt restore my backup because there was an error message while restoring /data of my backup
also when restoring to factory/wipe in cwm there was that error message about clouldnt "touch" /data, i dont remember the message exactly.
after thinking i bricked everything, i though lets wipe my internal sdcard, maybe that causes the /data error.
then i restarted the device and went for a shower... after 15min i came back and my device was "started".
now i dont know that exactly helped, maybe wiping all data on my phone, or just letting my device boot for a "long" time...
so, thats my yesterdays brick story.
do a factory reset if the bootloader has that option.. otherwise install or run/boot a custom revovery, then either
try the factory reset option there and reboot or..
wipe everything and install a rom
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
ngr.hd said:
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
Click to expand...
Click to collapse
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
angelgzg said:
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
Click to expand...
Click to collapse
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
ngr.hd said:
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
Click to expand...
Click to collapse
I flash the recovery but rebooted into recovery, the android keeps popping up (no commands)
FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Sorry I'm traveling a d couldnt update thread fast enough.

[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

Nexus 5 Recovery issues

Hi there, first post on here!
I've bought a nexus 5 off of eBay from some person who tried to root it and failed, thinking it would be an easy matter of restoring it.
However, the standard stock recovery process did not work, and I've encountered a number of issues:
When the device gets to erasing 'cache', it stays there for upwards of half an hour with no results.
With stock recovery flashed, pressing power + volUp immediately makes it erase /data, with no other options given.
It also does not show the stock recovery icon, instead a standing up android figure with a spinning poly in front of it.
Flashing TWRP and booting into recovery, it says 'e' is locked and goes into a boot loop.
Also no options in CWM recovery​
I thought I would ask on here because it's out of my league now, I've tried on both windows and mac with no luck and I'm not sure what to try next, maybe just leave it until cache finally erases?
Thanks in advance!
You need to read read and read some more.
Start here:
http://forum.xda-developers.com/google-nexus-5/general/resource-guides-info-threads-linked-read-t2784527
It sounds like the bootloader is locked.
It's almost impossible to brick a nexus.
I've managed to get a version of CWM loaded.
Performing factory reset gives the error that /data cannot be mounted for wiping.
Bootloader is definitely open.
M1kesky said:
I've managed to get a version of CWM loaded.
Performing factory reset gives the error that /data cannot be mounted for wiping.
Bootloader is definitely open.
Click to expand...
Click to collapse
Ok :good:. That means you can install TWRP 3.0.
Try this: flash back to a completely stock MM or LP ROM by manually flashing each partition, inlcuding the userdata.img file. When you have finished flashing all partitions, boot directly to recovery from fastboot mode, perform a factory wipe, and reboot.
I've tried doing that but it just results in the standing up android icon, with power+up leading to it trying to wipe data again. no option to do a factory wipe.
I put TWRP 3.0.0 on just to test and ended up in a worse bootloop, which failed to load TWRP but occasionally got into it and displayed this:
imgur.com/RKyZIJf
Sorry as I am a new user it doesn't let me use links
audit13 said:
Try this: flash back to a completely stock MM or LP ROM by manually flashing each partition, inlcuding the userdata.img file. When you have finished flashing all partitions, boot directly to recovery from fastboot mode, perform a factory wipe, and reboot.
Click to expand...
Click to collapse
Thanks, I gave it another try and did the recovery partition last, and made sure I manually put it into recovery mode from bootloader.
The red triangle and recovery menu are back, I can't thank you enough!
Glad you got it to work. I suggest using TWRP 2.8.7.1. For some reason version 3.0 does not work properly with all N5 phones.
It's still happening.
I've been away for a few days so only had the chance to respond now.
I got into the ususal recovery screen as mentioned previously and tried to do a factory reset, but it had problems with /data again.
I left it the entire night while I slept and it was still saying formatting /data in the morning, nothing had changed.
Anybody got any more suggestions? It's also back to the android with the rotating poly instead of the android with the exclamation mark.
EDIT: when flashing userdata, no matter what version of android I try, it always hangs.
It started on 6.0.1 if that helps.
The userdata.img file is included with each stock rom. I advise against mixing userdata.img files from different stock ROMs.
Sorry, I mean that I've flashed completely whole different versions of android and the result is the same across all of them, not that I've used different userdata img's on the same version of android.
Could be an emmc problem which would require a motherboard swap.
Is that likely to happen when the previous owner said it was fine before they tried to root?

HELP! Mismatched partition size for TWRP on Moto G Falcon

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.

Moto G Bricked?

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

Categories

Resources