Database Info

[Q] No rom seems to work, phone doesn't boot up

Hi everyone,
this is my first post, so i hope i'm posting it right, following every rule.
I've got a problem with my moto g. At the moment i bought it, I unlocked the bootloader, rooted it, upgraded it into KitKat, tried out a few different roms, installed Xposed, etc. and i never had any problem ( at least not one i coudn't figure out how to resolve).
However yesterday i wanted to try out Cyanogenmod 11, with yesterday's nightly 09/04/2014. I downloaded it from this post :
http//forum.xda-developers.com/showthread.php?t=2608377
Downloaded Gapps, too. Put both of them as zip in the moto g, did the 3 wipes and installed both zip's ( first cyanogen and then gapps).
However, once it rebooted, the cyanogen arrow kept moving around, endlessly. ( i waited for around 20 min)
In case it's relevant, i'll say that at the moment of downloading the nightly i lost internet connection, however i managed to resume the download and decided to keep going.
But after seeing that i didn't manage to install the rom properly I decided to download the nightly again and push it via "adb push .... ".
I installed it again with CWM, but the cyanogen logo kept loading. Nothing happend.
I also tried to install other Roms : GPE, 4.4.2 stock version and i even tried downgrading it to 4.3 ( which had previously worked, but not this time :crying: ) .
Everytime i got the same error, the mobile stucks at the logo ( Google logo, motorola logo, cyanogen logo,... )
My bootloader is unlocked and i've already the 3 wipes, and chache & system format ( via CWM )
and if i try to install a zip via CMW i get the following error : "E: Can't mount /sdcard"
wipe dalvick cache doesn't work and there is no error displayed.
¿Can someone help me?
Thank you very much!

Best way for you right now is to flash your stock firmware back (through fastboot) and try cm11 on that.

small-mallet said:
Best way for you right now is to flash your stock firmware back (through fastboot) and try cm11 on that.
Click to expand...
Click to collapse
Yap you should do a factory flash just download the pack "Moto g back to stock script" and do a full wipe while in fast boot and then flash CW root and install r0m u wish

[SOLVED] Moto G 4.4.3 Update Puts Phone in Boot Loop?

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

[Q] Moto OTA update Failed

[Edit] I've a backup saved on the pc, how can i restore that backup? (it was a backup of CM11) shall I zip the whole folder with the img files or shall I copy the whole folder into the phone?
I've tried both but when I choose "restore" from the TWRP nothing shows up
Hi all,
some months ago I've flashed the kitkat 4.2 rom successfully.
Yesterday I've got the message that a system update was available, (kit kat 4.4 the latest one)
I've downloaded it, then the phone rebooted to itself loading the TWRP recovery page therefore not installing the update.
I am now stuck and I don't know what to do.
- If from the TWRP menu I choose to reboot the phone, it loads fine but after a minute it reboot itself trying to install the OTA, rebooting again to TWRP menu
- I've tried to flash the OTA via TWRP from the cache folder but it fails.
Can you help me please?
Andrea :crying:
.

You can apply OTA patch only with full stock (also stock recovery, etc.)
To return to stock, read this thread.

crazypixel said:
[Edit] I've a backup saved on the pc, how can i restore that backup? (it was a backup of CM11) shall I zip the whole folder with the img files or shall I copy the whole folder into the phone?
I've tried both but when I choose "restore" from the TWRP nothing shows up
Hi all,
some months ago I've flashed the kitkat 4.2 rom successfully.
Yesterday I've got the message that a system update was available, (kit kat 4.4 the latest one)
I've downloaded it, then the phone rebooted to itself loading the TWRP recovery page therefore not installing the update.
I am now stuck and I don't know what to do.
- If from the TWRP menu I choose to reboot the phone, it loads fine but after a minute it reboot itself trying to install the OTA, rebooting again to TWRP menu
- I've tried to flash the OTA via TWRP from the cache folder but it fails.
Can you help me please?
Andrea :crying:
.
Click to expand...
Click to collapse
Hi Andrea,
I got the same issue.
You can go into TWRP, then wipe the dalvik/cache and cache partitions (about 4 secs).
then reboot your phone, it will update all your app again but you should be fine.
Hope that helps.

Arsgb said:
You can apply OTA patch only with full stock (also stock recovery, etc.)
To return to stock, read this thread.
Click to expand...
Click to collapse
Hi,
I forgot to mention that it was the stock rom,
how can I apply the ota patch only?
Thanks

mhaxor said:
Hi Andrea,
I got the same issue.
You can go into TWRP, then wipe the dalvik/cache and cache partitions (about 4 secs).
then reboot your phone, it will update all your app again but you should be fine.
Hope that helps.
Click to expand...
Click to collapse
Hi, it worked, thank you very much indeed

[solved] root/recovery borked since 6.0 update - can't apply 4.1 update

OK, so I've got the original shield tablet. I have lost root, and whenever I try to boot to recovery, the system attempts, goes to a black screen, then proceeds to normal system boot. Environment:
stock 6.0
non-rooted (not since updating to 6.0)
shield version 4.0
build MRA58K.41524_664.1902
previously had TWRP
I understand loss of root/recovery w/that last update is normal. However, I've tried:
flashing the new TWRP via fastboot w/o success (3.0.2)
flashing the rooted boot img w/o success
even flashing the stock recovery w/o success
ADB & fastboot commands chug happily along, & I'm left with the same behavior. Flashing the stock recovery actually gave me the dead android at the recovery screen (was this b/c I flashed the one for 4.0.1 & I need the one for 4.0?). So, what's my next move here?

Aaaaaaannnnnd.... I've also completely lost my WiFi. Says that it's on, but it's got the slash through it in quick settings & doesn't find any networks.

t-readyroc said:
OK, so I've got the original shield tablet. I have lost root, and whenever I try to boot to recovery, the system attempts, goes to a black screen, then proceeds to normal system boot. Environment:
stock 6.0
non-rooted (not since updating to 6.0)
shield version 4.0
build MRA58K.41524_664.1902
previously had TWRP
I understand loss of root/recovery w/that last update is normal. However, I've tried:
flashing the new TWRP via fastboot w/o success (3.0.2)
flashing the rooted boot img w/o success
even flashing the stock recovery w/o success
ADB & fastboot commands chug happily along, & I'm left with the same behavior. Flashing the stock recovery actually gave me the dead android at the recovery screen (was this b/c I flashed the one for 4.0.1 & I need the one for 4.0?). So, what's my next move here?
Click to expand...
Click to collapse
1) the twrp you linked to is for lollipop, states that in the notes section half way down the page.
2) to get root with this method you also have to install phh superuser
3) that dead Android IS the stock recovery
Now for help: flash this recovery(there are two here read and find the one for MM)
https://r.tapatalk.com/shareLink?ur...share_tid=2877117&share_fid=3793&share_type=t
[RECOVERY] [unofficial] TWRP 3.0.2-0 (2.8.7.1 for Lollipop) [2016-04-05]
Sent from my SHIELD Tablet K1 using Tapatalk

Thanks Exile. I've got TWRP installed ok now, but it doesn't seem to be able to wipe anything - just kinda hangs there (trying to wipe dalvik & cache - just sits at "formatting cache using make_ext4fs"). It's also weirdly unresponsive with UI lag on button presses; not sure if that's a known thing. I'm assuming that the "E: Failed to mount decrypted adopted storage device" is in reference to my external SD card.
I also still don't have my WiFi. I've grabbed the WiFi full OTA from this post & adb pushed it. TWRP was able to successfully flash it, but then couldn't do the ensuing dalvik/cache wipe. I let it sit for a good 10mins just to see if it would finish, but it still sat at the same point. Force power-cycling booted it into the new 4.1/6.0.1 version, and I do have my WiFi back
So, how to get root back? Can I just flash the SU 2.65 I have from TWRP? Or do I have to flash the rooted boot img again? I do already have the Superuser app installed...

t-readyroc said:
Thanks Exile. I've got TWRP installed ok now, but it doesn't seem to be able to wipe anything - just kinda hangs there (trying to wipe dalvik & cache - just sits at "formatting cache using make_ext4fs"). It's also weirdly unresponsive with UI lag on button presses; not sure if that's a known thing. I'm assuming that the "E: Failed to mount decrypted adopted storage device" is in reference to my external SD card.
I also still don't have my WiFi. I've grabbed the WiFi full OTA from this post & adb pushed it. TWRP was able to successfully flash it, but then couldn't do the ensuing dalvik/cache wipe. I let it sit for a good 10mins just to see if it would finish, but it still sat at the same point. Force power-cycling booted it into the new 4.1/6.0.1 version, and I do have my WiFi back
So, how to get root back? Can I just flash the SU 2.65 I have from TWRP? Or do I have to flash the rooted boot img again? I do already have the Superuser app installed...
Click to expand...
Click to collapse
Ok, from here just flash the supersu.zip and you should be good. I can't remember if 2.65 works or not but I know you can find a copy of 2.71. someone else has a problem with 2.72 so it may or may not work.
As for twrp it has touch screen lag issues, I don't think any of the mm compatible versions have been able to fully fix this. I've had the same problem with dalvik cache and cache wipe, it is slow as molasses but will complete eventually. Once you have root I would suggest using a program called flashfire to flash zips and do things like cache wipe. It works like a charm.
https://r.tapatalk.com/shareLink?ur...share_tid=3075433&share_fid=3793&share_type=t
[Android 4.2+][ROOT][2016.05.11] FlashFire v0.33 - Play BETA
Sent from my SHIELD Tablet K1 using Tapatalk

Thanks again, Exile. I actually had to re-flash TWRP, oddly, but after some searching, I found a mirror for su2.71, & adb pushed it. Once I had TWRP back in order, I was able to then flash it & my root is back together.

Glad you got it working. Have fun and be safe
Sent from my SHIELD Tablet K1 using Tapatalk

[Bricked] One of the harder ones =|

I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Whole story:
This whole episode began when I wanted to install Magisk to use MagiskManager's HideMe feature. This required me to install TWRP recovery which inturn lead me to unlock my bootloader in the process, straightforward and went off nicely. Now it was time to gain superuser which I already had done before on another device, installing SuperSU through TWRP recovery was painless but after booting found out MagiskManager needs Magisk Root to work. I then followed Android Exlpained's article to do so. Running unSU through recovery went smoothly but running Magisk didn't, on the initial run I was prompted to use Adrian DC's BootBridge which after removing a few Assert lines ran nicely. However there was no root install, SuperSU was removed though.
At the time I wasn't sure what exactly I was doing and ended up soft-bricking by flash boot through TWRP, at this time FRP was unlocked. After many many hours I restored to stock firmware by using YMNDLZ's guide. I used BLN-L24C567B370(OTA-MF-FULL) for the img files then proceed to flash the vendor.img using TWRP and the rest (boot.img, recovery.img, system.img) using fastboot in that order as instructed. The only part which didn't work was the forced update, it always failed at 5% however after more hours going recovery mode (now stock) wiping the cache and data/factory reset did the trick (Note: my model showed BLN-L24C567B369). I proceeded to reinstall TWRP, installed MagiskManager, tried to install Magisk 16.0 which ran but didn't root me but was fine because MagiskManager's download worked. I then thought since I went through all this trouble might as well install a custom rom, EliteRom was my ROM of choice. At this point I had logged in with my gmail credentials FRP was now locked.
*Before further action was taken I took the precaution to backup my current stable stock ROM after installing EliteROM but before booting*
The steps to install EliteROM went by flawlessly, installed EliteTWRP reboot into it, ran EliteROM
went through the setup without any hiccups. However up system restart I the ROM wouldn't boot leading me to boot into my recovery only to be prompted for an encryption password (???). Since I didn't recall setting one, couldn't boot into the OS, and FRP was locked I couldn't read my own internal storage. So I reformatted the internal storage and tried what had worked before, flashing the img files using TWRP then booting into stock recovery wiping cache and data/hard reset. . . this did not work. And here I am FRP locked so fastboot isn't useful (I think?), stock recovery doesn't work, eRecovery fails connection, and force update still fails at 5% with "Software install failed!".
Click to expand...
Click to collapse
Lemme know if there is any insight anyone can provide and thanks in advance.

This problem has been solved?

MisterRee said:
I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Lemme know if there is any insight anyone can provide and thanks in advance.
Click to expand...
Click to collapse
you have to follow only xda methods to root or change to custom rom. i have never heard about flashing stock images from twrp. i think u didn't followed elite rom instructions clearly. you need to formate data then reboot to recovery then wipe everything then flash the os in this way you won't get encription error. anyway now your frp is locked so there is no way to flash twrp so download all the available firmwares for your phone oeminfo then do flashing via dload you will get it worked.
even i was also once stuck with elite rom. i didn't liked it because missing apps icon and forgetting permission. i tried to go back to stock but stuck at 5% error. then went to google searched stock rom for honor 6x india and downloaded nearly 3 roms last one worked helped me to get back to stock.
never flash system images boot,vendor etc from fastboot and twrp unless you are on emui8 and going to try gsi roms.

hey i cant revert back to stock rom. it fails to get package from server. does jio voice calling works on this device?? if no then plz guide me how to go back to stock rom..

MisterRee said:
I'm gonna keep it simple, here is the scenario:
ROM is corrupted.
Bootloader is unlocked.
FRP lock is on. (fastboot can't do much)
TWRP was flashed back to stock.
Stock hard-reset fails. (even wipe option)
Force upgrade stops at 5% (swear I am using the same one)
eRecovery does not work.
Can't flash. Can't push files.
Wat do.
Model: BLN-L24C567B369 (pretty sure this was it)
Lemme know if there is any insight anyone can provide and thanks in advance.
Click to expand...
Click to collapse
Register for update using firmware finder and Puts dns address in the router settings and then use erecovery