Weirdest problem, and not one that I've ever encountered after playing around with Android since the G1 days!
My Boost Moto G 2013 will only boot into the recovery, no matter what I do. I've searched and searched through Google and on XDA and found nothing that matches my problems exactly.
I can get into the bootloader (am running version 41.1A) and flash a new recovery. I've got TWRP on there right now, but I've tried CWM as well -- same problem. I've actually installed Android 5.1 from the stock flashable zip, and it says it flashes fine, but still won't boot into it. No matter how I restart the phone, it just goes straight into recovery.
Any ideas?
I'm assuming that you've tried different ROMs? I had a weird problem where I could no longer flash any ROM's without getting an error. Only after I did a complete wipe of everything (including internal storage which was the key) was I able to properly boot up. Not quite the issue you're having but worth a shot, make sure you can access the phone on your PC so that you can copy over the ROM after the wipe.
I have had this problem recently. I believe I had to fastboot flash stock recovery, then an older, smaller CWM to avoid partition mismatch problems. Then flash the TWRP you want with a zip with CWM.
Sent from my XT1031 using Tapatalk
Related
Hi,
is it possible somehow to cleare the partitions "deeper" then it's possible with the build in format command inside CWM?
I tried the fastboot erase (system, data, boot) with the result "permission denied" also.
The problem is the Moto G got messed up during the update to 4.4.
Since that moment the Moto G won't boot up with any stock Rom i flashed and i checked up many, many different stock roms (4.3 and 4.4.2).
It is possible to access recovery. (only CWM-swipe is working, CWM-touch, TWRP or the stock recovery won't boot) (Somehow TWRP booted once, but never again...) Sometimes i even can't access CWM-swipe, than I have to erase userdata and cache inside bootloader.
The other thing is it was possible to boot up the G with the Lego Rom, but it rebooted very often (30secs, 1min, 10secs....)
At this moment even that doesn't work it's getting stuck inside the bootlogo like every other custom rom i tried (Slim, CM11).
This behaviour makes me belief that things must be messed up depper inside.
I like to wipe everything!
Try this to restore your system
http://forum.xda-developers.com/showthread.php?t=2644703
I dont know what happened woth your g , but this delets everything except of the bootloader and then flashes the normal stock Rom, so that your moto g is like new.
It could be that sth. is wrong with your recovery as you cant wipe or flash anything, maybe flashing another recovery via fastboot would make you able to flash roms again and you wont need to restore stock.
Hopefully this works but remember that it doesnt metter what you do, you are responsible for everything and noone else. I dont guarentee that this works.
Hi,
this is what i had done about 40 times with almost 20 different stock roms. They all doesn't boot up
The Lego-Rom is the onlyone which had booted up completly but rebooted automaticly. Now Lego is hanging in bootlogo.
Like i wrote in the first post. CWM-swipe is the only recovery that still works most of the time. And I tried the stock recovery, CWM-touch (philz-touch) and TWRP.
I need to go deeper with the wipe/format if it is possible.
Otherwise i need to dump the G.
Thats really weird. If this all doesnt work then i dont know.
Yep, this is why I'm asking for help! Maybe someone know more.
ikarugaski said:
Yep, this is why I'm asking for help! Maybe someone know more.
Click to expand...
Click to collapse
I WAS IN A SIMilar situation a few days back
i couldnt boot up nor boot to recovery so to make a slong story short, i simply took a system img and a boot img and a cwm recovery img and fasboot flashed all 4 one at a time and somehow it worked fully stock but at least i could reset up all my stuff from there.
kep i mind before this method i i tried the guide "restore stock moto g rom" for 2 days straight with fastboot failing to flash it each time. if ur ok with starting anew apps wise try to flash a stock rom.
I have a Moto G X1032 rooted with TWRP installed. I've been using the stock firmware for 4.4.2 without any issues for a while, but after June 6th's OTA update to 4.4.3, my phone has gotten stuck in a boot loop. It turns on and runs Android as usual, without any issues, for less than a minute and then shuts down. It then continues to boot back up and continue the process. The only way to stop the loop is to boot into the bootloader from TWRP and power off the phone from there. Luckily I have a backup to that reverts me back to 4.4.2, which successfully stops the loop. But after several attempts to update to 4.4.3, it has become quite clear that this boot loop is inevitable unless I stick with 4.4.2. I read an article that seems to address some conflict with rooted phones and 4.4.3, but I'm not quite sure what the conflict is. Can anyone explain to me why this boot loop is most likely happening, what I could do to fix it, or if it is even possible to have a rooted X1032 with 4.4.3 installed? Any help whatsoever would be greatly appreciated. Thank you.
Are you saying you tried to install the OTA with TWRP installed and not the stock recovery?
Just go into recovery clear all cache,kavik cache that should do
NerdNoob1210 said:
I have a Moto G X1032 rooted with TWRP installed. I've been using the stock firmware for 4.4.2 without any issues for a while, but after June 6th's OTA update to 4.4.3, my phone has gotten stuck in a boot loop. It turns on and runs Android as usual, without any issues, for less than a minute and then shuts down. It then continues to boot back up and continue the process. The only way to stop the loop is to boot into the bootloader from TWRP and power off the phone from there. Luckily I have a backup to that reverts me back to 4.4.2, which successfully stops the loop. But after several attempts to update to 4.4.3, it has become quite clear that this boot loop is inevitable unless I stick with 4.4.2. I read an article that seems to address some conflict with rooted phones and 4.4.3, but I'm not quite sure what the conflict is. Can anyone explain to me why this boot loop is most likely happening, what I could do to fix it, or if it is even possible to have a rooted X1032 with 4.4.3 installed? Any help whatsoever would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
secretkloud said:
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
Click to expand...
Click to collapse
Thank you. I will try that. Before I do though, do you know of any places I could find 4.4.3 online, so I could just download it from my PC and flash it over via sideload? I usually prefer to flash things that way, rather than straight from the phone.
bozzykid said:
Are you saying you tried to install the OTA with TWRP installed and not the stock recovery?
Click to expand...
Click to collapse
Yes. This is my first time doing so, excuse my lack of knowledge on the subject. In retrospect, I suppose I should have known there must be a different method with which I install it. Secretkloud gave me a good suggestion though. Is there a reason in particular as to why I can't do OTA updates with custom recovery installed?
secretkloud said:
The bootloop is caused by the recovery. It can't update 4.4.3 and keeps trying. Start the update again and let the OTA file download, then copy it out of /cache and into the sdcard. If it's not in cache it won't bootloop. I suggest flashing PhilZ recovery and updating with that instead. Flash the file in the sdcard and post whatever errors are listed...
Click to expand...
Click to collapse
I just downloaded the zip from my phone and flashed it from Phillz recovery. It worked very well and the update was successful. Thanks for pointing me to Phillz recovery by the way. It's the only functional recovery image that allows me to mount the sdcard.
NerdNoob1210 said:
Thank you. I will try that. Before I do though, do you know of any places I could find 4.4.3 online, so I could just download it from my PC and flash it over via sideload? I usually prefer to flash things that way, rather than straight from the phone.
Click to expand...
Click to collapse
Copy the one you have in your phone onto your PC. Smallest chance of error if you do it that way...
it's not easy getting out of the loop.
I did a factory reload of a rooted phone with CWM.
Now for the CWM issue the Moto G loaded OK and then said there was an update for android to fix some bugs. This was 4.4.3. I loaded it and it gets half way and it then says
"Signature verification fail"
at the bottom of the screen and
" Install Untrusted Package"
The options are yes, no or go back
at the top....
whichever one I try it then tries to boot shows the Android / Motorola screen and starts up gets a txt message for 2-3 seconds... it then goes back to Android CWM recovery with the same options as above and repeats the process. again and again and again. No function keys will stop this cycle which just repeats again. This continues until the battery dies.
any ideas ? how can I override this action in CWM v6.0.4.6 and force it to do a factory reload ? any help or advice much appreciated.
If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose.
Sent from my XT1032 using XDA Premium 4 mobile app
NerdNoob1210 said:
If you can still power your phone, can you still access the boot loader? If so, I would suggest using adb from a computer to flash Phillz recovery. CWM always gave me a lot of random errors when flashing items. You could use PhillZ to flash the stock ROM for 4.4.2. After that, just follow the same process I did. Download the update zip via the OTA download when it prompts you. Once it's finished, DON'T boot back into Android. Boot into Phillz recovery from the boot loader, move the zip out of the cache and onto sdcard or your computer, and then flash it either straight from the phone or by sideloading it from your computer. Then you'll have a working version of vanilla 4.4.3, and you can flash over a custom ROM in the future if you so choose.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
unfortunately I can't get into bootloader. I can connect usb and it makes no difference. therefore adb commands dont work. it just goes straight into screen described with those three options. I'm hoping that there is an override action in CWM which isn't power and volume down which do nothing.
thanks for the suggestion tho. it was a good idea.
Hm... Without access to the boot loader, I'm not sure there's much of anything you can do anymore... You've completely lost the ability to communicate any sort of commands to your phone save for the 3 options that menu provides. I assume that what CWM is trying to do is install the zip from your cache and is failing to do so. The only viable option would be to flash a new recovery image and install the zip manually, but that's impossible for you given your current circumstances. I would give up looking for an override command for CWM, your best hope is to find an alternative means with which you can access your boot loader. I suggest you start a thread dedicated to your issue and see if a more experienced user can provide you with the information you need. Sorry, I hope you get the help you need. :/
Sent from my XT1032 using XDA Premium 4 mobile app
Thanks for trying to help. I have followed your advice and opened a thread
NerdNoob1210 said:
Hm... Without access to the boot loader, I'm not sure there's much of anything you can do anymore... You've completely lost the ability to communicate any sort of commands to your phone save for the 3 options that menu provides. I assume that what CWM is trying to do is install the zip from your cache and is failing to do so. The only viable option would be to flash a new recovery image and install the zip manually, but that's impossible for you given your current circumstances. I would give up looking for an override command for CWM, your best hope is to find an alternative means with which you can access your boot loader. I suggest you start a thread dedicated to your issue and see if a more experienced user can provide you with the information you need. Sorry, I hope you get the help you need. :/
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have been trying for hours to install both TWRP and CWM recoveries, and my phone will not accept them.
It goes through the process, yet upon the reboot into recovery, it just starts normally.
the message on the phone is: Mismathched partition size (recovery)
I have a Canadian version of 4.4.2 stock rom on my Moto G.
It is boolader unlocked and rooted.
Any ideas how to install the recovery?
My ultimate goal is to install a rom that supports russian language.
retfeg said:
I have been trying for hours to install both TWRP and CWM recoveries, and my phone will not accept them.
It goes through the process, yet upon the reboot into recovery, it just starts normally.
the message on the phone is: Mismathched partition size (recovery)
I have a Canadian version of 4.4.2 stock rom on my Moto G.
It is boolader unlocked and rooted.
Any ideas how to install the recovery?
My ultimate goal is to install a rom that supports russian language.
Click to expand...
Click to collapse
same problem here! brand new phone, 4.4.2 o2 UK.
the mismatched partition size error is not important i know that.
have tried Philz (got it to work once, but after rebooting, had gone again. ever after letting it fix the rom rewrite on exit!). also tried stock CWM 6046 and 6047.
have tried entering recover immediately after flashing.
have tried flashing multiple times.
have tried different usb ports.
ideas please?
i've never had this much trouble with any phone (have experience over 3 years with Blade, G300, Xperia range etc.)
edit: tried using fastboot -S 0 parameter also, seems to make no difference. phone won't boot into recovery. this is slightly different to the problem i had with old phone, that one would boot Philz but not boot any ROMs. this one is booting stock ROM. if i can get Philz to "take" again i could try flashing CM, but i wanted to stay on stock, and just root it..
edit2: just started working! bizarre.. hope this doesn't jinx it. i wrote two recovery images with -S 0 and it works, not sure if because of that or something else. btw Philz won't backup the stock rom, odd - it just errors out, CWM standard works though.
hurrah! i rebooted normally, went back to fastboot and recovery still there. this is with recovery-clockwork-6.0.4.7-falcon.img
now i can hopefully root it..
wonder if my 3rd moto g will get any easier! this is a huge PITA of random non-workiness so far.
Alright so I have a Moto G original version, currently running 4.4.4. I previously rooted it and stuck TWRP on it, but then when it became available to update to Lollipop on the Moto G I tried to get stock recovery on it. I used "MotoToolAIOV3" to put "Kitkat Stock Recovery" on it. This seemed to work fine, until it came to update, which then it errored every time I tried. I then realised the stock recovery that "MotoToolAIOV3" must be faulty or something, so I tried reputting TWRP on my Moto G by flashing it from an app called "Rashr". This seemed to be successful, HOWEVER I went to reboot my phone to check if it had worked, put it into bootloader, then went into recovery and it still came up with the stock recovery "MotoToolAIOV3" had given me. I was confused, so I tried "normal powerup", which THEN sent me into TWRP, however this time, when the bootloader unlocked warning came up, a weird blurry line went through my screen every so often, and then it went into TWRP, with the line going across the screen in TWRP as well. I've tried to boot into normal powerup through TWRP, Bootloader, normal powerup, holding down power button but every time I try, it goes into TWRP with a dodgy line going across my screen. I'm currently doing exams and I really need my phone as I have revision notes on apps that I can only access on that phone, and things such as exam timetable saved in the actual phone.
Please, somebody help ):
Again my phone is a Moto G Original Gen running 4.4.4 stock android, on a tesco thing (cant remember what its called might be kernel).
Thank you.
bump
bump
bump2
bump2
Arcenum said:
bump2
Click to expand...
Click to collapse
Seems like you have flashed TWRP into the kernel partition. Seem like the "Rashr" app or whatever flashed it there by mistake. I recommend that you install TWRP via a more standard procedure, such as using fastboot(if bootloader unlocked) or using the instructions given where ever you downloaded TWRP. Your situation is not serious as long as you are careful....
1. Install recovery to correct partition
2. Boot to that recovery and wipe/factory reset etc...
3. Install an new ROM.
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
kozaqu said:
Hi,
I think the problem is in the modified .dtb try flash the original file.
Or : https://forum.xda-developers.com/showpost.php?p=82359331&postcount=39
greetings
Click to expand...
Click to collapse
That got me in the right direction and I can at least get back into recovery now. Thanks! :good:
Also in the same boat
mkhopper said:
Well, not fully bricked, but it's completely non-working just the same.
I've had the K1 for a few years now and have been fine with the standard, stock OTA updates. Recently though I've been seeing constant notifications that I'm short on ram and after uninstalling apps, deleting old files, it would work ok for a few days and then start complaining about low memory again. So I figured that something must be corrupt and now is a good a time as any to root and see about flashing a new rom.
I've owned many android devices over the years and have rooted and patched most of them. so I'm familiar with the tools.
This time however, I think I must have crossed something up somewhere.
What I did was this:
Grabbed the minimal ADB package and fastboot drivers.
Booted into the bootloader and ran the fastboot oem unlock. No problem.
From the nVidia site, I then grabbed and flashed the latest stock image and recovery, just to ensure I was on a clean slate. No problem.
Flashed the latest TWRP for the device. No problem.
Flashed SuperSU. No problem.
Booted into the stock system to make sure everything was still working and it was. But, this is the start of where I maybe hosed things up(?).
While running stock, I converted the SD card to internal memory, just so I wasn't having to mess with it later, not thinking that I'd have to do it again anyway after flashing a new rom.
Rebooted back to TWRP and proceeded to flash the new rom (AOSP Extended (AEX) 5.8).
I flashed it by way of the sideload method rather than from a zip file sitting on the SD card. This all seemed to work just fine.
Next I went ahead and flashed OpenGapps Mini. This resulted in an error 70 and after reading about it, it was a simple matter of going into the advanced settings in TWRP and extending the system partition. Did that and OpenGapps then flashed with no problem.
Finally I wrapped it up by flashing tegra124-tn8-p1761-1270-a04-e-battery.dtb and rebooted.
... Nothing. Now I know that when flashing a new rom, the first boot can take some time, but I let it sit for about 2 hours with no result. It didn't appear to be boot looping, but instead just stuck on the nVidia boot screen. Forced it to boot back to the bootloader and brought up TWRP. I obviously did something wrong, so I prepared to reflash the stock image.
Did the wipe, flashed the files and rebooted. Again, nothing.
This time however, not only can I not boot to the system, I now also can't get back into recovery.
No matter how many times I reboot, or attempt to reflash anything, it hangs on the boot screen when attempting to get back into recovery.
So I'm stuck. I've tried reflashing TWRP, stock recovery and stock system, with the SD card in and out, a number of times, all with no joy.
I can access the bootloader, so I can at least run fastboot commands, but that's all I can do. Without being in recovery, I can't access an ADB shell if I need to repair anything.
If you're still with me after this rambling mess, do I have any hope at all in recovering this thing?
Click to expand...
Click to collapse
I'm also sort of in the same boat i had a custom rom installed and decided to go back to stock os and now i'm stuck at either the Nvidia Logo or the Fastboot menu there's nothing else it let's me do i'd take any advice at this point. I can use Fastboot commands and I've tried Flashing Twrp.img and also flashing all the stock os which goes through with no problems i reboot the device and it's just stuck at the Nvidia logo
Ps: how did you manage to get back into recovery
Hello.
I think i had the same Problem.
I Flashed a Custom Rom, MiniGapps and the tegra...Battery file and since then i had boot loop an the NVidia Logo.
The Problem was: i flashed the tegra-Battery.ZIP file!!!
I noticed that i have to unzip it and flash teh tegra-..battery.DTP file.
since then it booted up again.
the OpenGappMini was buggy. it worked with the Nano!
Hope this helps for you as well!
OMG you guys. I did the exact same damn thing. Flashed the ZIP instead of the DTP file. 100 million thanks to you. I'm going to give it a shot now.
It worked! I wonder how many other folks didn't realize it wasn't a zip to flash to dtb and bricked their devices.