Database Info

[Q] Katkiss upgrade question.

Does anyone know how long katkiss rom upgrade take? I flashed my tf101 with rogue rom and installed katkiss 4.3.25 & gapps-katkiss and upon reboot i can see the dog/circles animation on screen. However this has been going on for more than 35 mins now. Can someone please advise if this is normal or if anything went wrong? I didn't see any error message during root & installing custom rom's. How long does the whole upgrade take?
I started the whole process while battery % was around 50 and now with the upgrade still going on, not sure how long the battery will last. Is there anyway i can bypass the reminder of upgrade and still boot into a functional tablet?
Thanks in advance.

Doesn't take that long, sounds like you have a boot loop,
My advice, flash TWRP recovery with Easyflasher, then flash KatKiss ROM and Gapps again from TWRP

Actually it did finish after about 2-3 hrs i think. Not sure if my tablet itself is slow (TF101), low memory or something else. But i can boot into 4.3 now . I can definitely see a boost in performance now, earlier tablet used to drag like a snail, now it's quite nippy Hope it stays this way.
Is 4.4 in the works ?
Thanks for your help.
*Detection* said:
Doesn't take that long, sounds like you have a boot loop,
My advice, flash TWRP recovery with Easyflasher, then flash KatKiss ROM and Gapps again from TWRP
Click to expand...
Click to collapse

Tim was working in 4.4 but hit some road blocks. He is back on 4.3 but said when he gets time he will resume 4.4.
So far I haven't heard anyone else working on 4.4 for the TF101

mubharad said:
Actually it did finish after about 2-3 hrs i think. Not sure if my tablet itself is slow (TF101), low memory or something else. But i can boot into 4.3 now . I can definitely see a boost in performance now, earlier tablet used to drag like a snail, now it's quite nippy Hope it stays this way.
Is 4.4 in the works ?
Thanks for your help.
Click to expand...
Click to collapse
Do you have like 2000 apps installed or something ?
Never heard of first boot taking 2-3 hours before
Glad it booted in the end though

No, I had only about 20 apps or so. Initially i did a factory reset before flashing but for some reason it didn't go well so after reboot all my apps got downloaded. Subsequently in the 2nd attempt i got the root working and able to install custom rom, but i didn't do factory reset, maybe that could've delayed it. But no 2000 apps for sure
Thanks for the reply.
*Detection* said:
Do you have like 2000 apps installed or something ?
Never heard of first boot taking 2-3 hours before
Glad it booted in the end though
Click to expand...
Click to collapse

When I try to flash my tf101 with KatKiss 4.3.1, I got 'E:signature verification fail' problem, can anyone help? TIA.

Disable the signature verification in TWRP. Can't remember exactly where it is, but I think it's in the options/extras/settings menu.

[Q] New Moto G OTA Update causing boot loop

The new update today for the moto g is causing my phone to be in a boot loop. I really don't know why. It's rooted and I use twrp recovery to wipe the cache and it works again but if I try to install the update it will just cause the boot loop again. Please help I really need this update my internet is slow on my phone! Thanks.

The same thing happened here, with CWM recovery. The update probably expects stock recovery.

Same here
Sent from my XT1032 using xda app-developers app

Nevermind
Doesn't matter. I remember reading somewhere that you no longer get updates from motorola once you root your device. I'll wait for someone to release a flash for it. Thanks.

cillian334 said:
Doesn't matter. I remember reading somewhere that you no longer get updates from motorola once you root your device. I'll wait for someone to release a flash for it. Thanks.
Click to expand...
Click to collapse
Not true. I rooted, flashed custom recovery and all, and STILL received the update. The trick is how to get it into the phone without the bootloop.
Try the suggestions I put in this thread
http://forum.xda-developers.com/showthread.php?t=2663205
A little attention is all that is needed...

Just went to hell and back.
I just reflashed to stock and it turns out it was a bad rom and i couldn't fix it but i think it's ok now.

I have the Indian dual sim version, and my Moto G is having bootloop problem after a month of installing the OTA :\
Can anyone help me out? I have tried reflashing the stock firmware but of no use.
Just the motorola blue logo shows up and then black screen. The recovery also doesn't work

ahank said:
I have the Indian dual sim version, and my Moto G is having bootloop problem after a month of installing the OTA :\
Can anyone help me out? I have tried reflashing the stock firmware but of no use.
Just the motorola blue logo shows up and then black screen. The recovery also doesn't work
Click to expand...
Click to collapse
Did You found any solution?
I have same problem here...

jayrocky11 said:
Did You found any solution?
I have same problem here...
Click to expand...
Click to collapse
Wipe cache, it sabed MY bacon for sure. Use fastboot

Hardbricked Moto G after CM 12 Nightly Update (Did not downgrade to KitKat)

Please pardon me for any faux pas as I am new here.
Mods please refer me to the appropriate thread and close this one, in case this one is a duplicate.
It seems my Moto G 1 Gen XT1033 is hardbricked. I had been running a CM 12 for falcon - nightly release since May 2015 and had had no problems so far. I had also upgraded my recovery to CWM Touch.
Two weeks ago, my phone got stuck in a boot loop (I now realise that that is called a softbrick), I managed to boot into recovery and updated my OS with the latest nightly release of CM 12 for my phone. I also tried to upgrade the recovery version with the same as that of the OS version but I don't think that it got upgraded. (I'm not sure what it said).
Anyway my phone was working fine for an hour or so until CM gave some errors on opening the themes configuration, so I thought rebooting my phone would solve the problem.
My phone never booted after that. It didn't even turn on or boot into the bootloader/recovery etc. I checked the battery etc. and it was fine. There was no issue with the hardware.
I then connected my phone to my laptop and it recognised it as qhsusb_bulk. I have spent a lot of time searching and trying various methods like:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
http://forum.xda-developers.com/moto-g/orig-development/bootloader-tool-motoflasher-t2959076
Using the MotoTool All In One etc.
I cant seem to figure out the problem. I don't even know what my bootloader version was etc.
Is there a problem with my bootloader or recovery? I can't seem to understand.
Can someone please help me with this?
Thanks

Oh man that's unexpected. I never think CM could cause this. I hope you can get it fixed.
Bumping the topic

motolollipop said:
Oh man that's unexpected. I never think CM could cause this. I hope you can get it fixed.
Bumping the topic
Click to expand...
Click to collapse
Thanks man. But no help so far

Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?

Tass99 said:
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Click to expand...
Click to collapse
No bro. I've bough a spare phone to survive on till I get a solution for this.
But nothing has worked so far.

CoolCrusader said:
No bro. I've bough a spare phone to survive on till I get a solution for this.
But nothing has worked so far.
Click to expand...
Click to collapse
That happened to me too, I think even the same image! It was a long time ago and I have now switched to a Oneplus One after using a Moto E which actually isn't that bad - I got it new super cheap. For me, Cyanogen restarted to update and after a LONG period of time stopped doing anything (I have upgraded before). I couldn't mount anything in CWM and I lost all data irrecoverably. The partition table got all messed up, and I had to flash a dual sim image as it was the only one that loaded - done through fastboot. I then flashed the original kitkat image and then massively messed up and updated, making my phone qhs_bulk.
Basically everyone who has had lollipop on their devices and have this are waiting for files to be leaked from Motorola so they can make their phones work. Not much is happening currently, you might as well get a new budget phone - some of the new ones are much better than the Moto G 1st gen! Or you could do what some people are doing which is ordering broken Moto Gs off eBay and replacing the board. Good luck!
---------- Post added at 01:49 AM ---------- Previous post was at 01:42 AM ----------
Tass99 said:
Bit of an old topic, but wondering whether there's any update? I have a similar issue. I was running 12.1, and installed the nightly update from yesterday, not noticing it was for 13 (Android 6.0). I was then able to get back into recovery and flash a working 12.1 image. The issue now is the phone is stuck in a boot loop, going through "Optimizing app x of 133", gets to the end and then reboots. I can get into the boot menu and select recovery, but it reboots and goes back into the same boot loop. Likewise if I chose Factory from the boot menu.
Any luck on your side?
Click to expand...
Click to collapse
You may want to go the fastboot method to flash a stock lollipop image and CWM recovery - if you don't have a backup, you may want to try just flashing something like TWRP to see if you can get some files off your device, then completely flash over it.

One plus get stuck in bootloop

Hi guys, I have a problem with a one plus one that can't exit from bootloop.
I just tried to flash a stock firmware (11S) and the one plus restoretool but with no success. I can only acced recovery and fastboot. The device is also unlocked. Can it be a hardware problem? Thank u for your help.

BlackSkorpion said:
Hi guys, I have a problem with a one plus one that can't exit from bootloop.
I just tried to flash a stock firmware (11S) and the one plus restoretool but with no success. I can only acced recovery and fastboot. The device is also unlocked. Can it be a hardware problem? Thank u for your help.
Click to expand...
Click to collapse
You don't give much detail as to what happened or what you were doing prior to your bootlooping. I suffered from a bootloop that took me several months to finally resolve on the very device I'm responding to you with. I was able to resolve it by installing the latest Oxygen OS from the OPO forums. I followed the directions exactly, then after booting into Oxygen it turned out that my WiFi and Bluetooth were refusing to turn on. After several attempts and force close reboots I was able to get them to function. Then I reinstalled TWRP, then flashed CMOS12, then finally CM which I'm using now. BTW for more detail look for my post about it in this forum. Hope this helps.

Odysseus1962 said:
You don't give much detail as to what happened or what you were doing prior to your bootlooping. I suffered from a bootloop that took me several months to finally resolve on the very device I'm responding to you with. I was able to resolve it by installing the latest Oxygen OS from the OPO forums. I followed the directions exactly, then after booting into Oxygen it turned out that my WiFi and Bluetooth were refusing to turn on. After several attempts and force close reboots I was able to get them to function. Then I reinstalled TWRP, then flashed CMOS12, then finally CM which I'm using now. BTW for more detail look for my post about it in this forum. Hope this helps.
Click to expand...
Click to collapse
Hi, i dont know what happened before because the Phone is not mine, is of the gf of a friend. I can reach fastboot and recovery and I also changed the recovery to twrp and installing a new rom, but bootloop still is running. What can i do else?

BlackSkorpion said:
Hi guys, I have a problem with a one plus one that can't exit from bootloop.
I just tried to flash a stock firmware (11S) and the one plus restoretool but with no success. I can only acced recovery and fastboot. The device is also unlocked. Can it be a hardware problem? Thank u for your help.
Click to expand...
Click to collapse
Do you have a backup? try restoring just the system and the data of your backup.. i used to flash the boot too but as far as i know flashing boot doesn't solve the issue (still bootloop-ing). if you are still in bootloop and really have no idea, try consider a full reset of your phone (all except your custom recovery, ofc) and flash a new flashable.zip rom.. (data+media also wiped) you can always copy files to your phone while in recovery by mounting a usb drive, in case you don't have a zip on your phone. of course, this is not the solution, and is not recommended, but take this as your last choice if any other method didn't work
hope it helps!

Kevin1705 said:
Do you have a backup? try restoring just the system and the data of your backup.. i used to flash the boot too but as far as i know flashing boot doesn't solve the issue (still bootloop-ing). if you are still in bootloop and really have no idea, try consider a full reset of your phone (all except your custom recovery, ofc) and flash a new flashable.zip rom.. (data+media also wiped) you can always copy files to your phone while in recovery by mounting a usb drive, in case you don't have a zip on your phone. of course, this is not the solution, and is not recommended, but take this as your last choice if any other method didn't work
hope it helps!
Click to expand...
Click to collapse
I dont have a backup, so i also tried yet everything you said. I dont have to save datas, so i flashed everything new, but still dont work. I also tried to flash everything from oneplusrecoverytool that in any difficult situations helped me, but in this case it did not worked. Is there any radical solution to get this Phone working? (i can install twrp and reach fastboot, but after installing something, it's always in bootloop. ?

i have the same problem , don't know what to do , i even used the tool to return to stock
maybe an overheat problem? i don't know

Gentlemen, please try the method I suggested above in my response. Go to the OPO forums and follow the procedure to switch to Oxygen OS exactly as they lay out. As long as you're unlocked and can get to the bootloader and recovery you aren't hard-bricked and will be able to eventually fix your handsets. I know from personal experience, because as I mentioned this device was hopelessly stuck in a bootloop for months before I was able to get it running again. Do a search for my previous post for instruction and as I said follow the guide to installing Oxygen to the letter. More than likely you've got several corrupt partitions and this method will resolve it. Once you've got your handset successfully running again on Oxygen you can then begin to flash other ROMs with no issues. For some reason the Oxygen OS is more robust in that it will boot up when there are issues with these corrupted partitions when CM based ROMs won't. I believe the title of my previous post was "hopelessly stuck in bootloop (solved)". I hope this helps.

Odysseus1962 said:
Gentlemen, please try the method I suggested above in my response. Go to the OPO forums and follow the procedure to switch to Oxygen OS exactly as they lay out. As long as you're unlocked and can get to the bootloader and recovery you aren't hard-bricked and will be able to eventually fix your handsets. I know from personal experience, because as I mentioned this device was hopelessly stuck in a bootloop for months before I was able to get it running again. Do a search for my previous post for instruction and as I said follow the guide to installing Oxygen to the letter. More than likely you've got several corrupt partitions and this method will resolve it. Once you've got your handset successfully running again on Oxygen you can then begin to flash other ROMs with no issues. For some reason the Oxygen OS is more robust in that it will boot up when there are issues with these corrupted partitions when CM based ROMs won't. I believe the title of my previous post was "hopelessly stuck in bootloop (solved)". I hope this helps.
Click to expand...
Click to collapse
i tried your solution but nothing changed i also tried this procedure http://forum.xda-developers.com/one...lusrecovery-tool-v1-0-restore-t2991851/page23 , the process is success but at the reboot the phone is always in bootloop

still same problem here =/

Download the latest fastboot image from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471 follow step #8

In a right mess trying to return to stock

Please could someone help ! I'm trying to unlock my XT1032. I have the correct Sim-Unlock (network unlock) code from my old telco, but... it won't work because the phone is rooted, bootloader unlocked (S-ON) running CM13.
I figured that returning it to a stock build would allow me to unlock the phone, then I could re-root and return to CM13 on my new network.
However..... there are about a dozen guides on returning a Moto G to stock and the first one I tried left the phone stuck on the 'Warning: Bootloader is unlocked' message. Since then, I've tried several other guides and have got nowhere fast. I've been on this for four hours now and the only thing I seem to be able achieve is to get TWRP or CWM recovery on there by flashing from fastboot. Every other image I try either gives 'preflash validation failed' messages, sticks on the Bootloader Unlocked screen or gets it stuck in a bootloop!
I just want to switch networks... Why is this so bloody difficult ?

What Firmware did your XT1032 originally come with? or which Carrier?

Kitkat I think, and it's Tesco (UK).
I subsequently did the OTA update to Lollipop and then.... WHOAAAAA.... hold on... it's booting !!!
I don't know how, or what I've done to get this far, but the only thing I can think of that's changed is that the battery is now at 100% charge. It appears as though it's successfully flashed the 5.1 untouched ROM from http://forum.xda-developers.com/devdb/project/?id=7981#downloads
But, I've tried flashing that loads of times this evening and it's failed everytime.
Having said that it's booting, it's sitting here on the Motorola logo - and it hasn't got that far in the last five hours.... I'll be back shortly !
Update: It worked ! It completed the boot, I put the new SIM in, it asked for the unlock code and this time it worked OK. Now I'm tackling putting CM13 back on it. I think I'll stick with TWRP rather than CWM recovery, as long as TWRP can handle the automatic updating for the CM nightlies.
I have no idea what went wrong there - maybe it was just that the battery had to be at 100% ?? Who knows... Thankfully I doubt I'll be tackling that again !

I don't know if things have changed, but I would be careful with OTA Updates in CM. People have hard-bricked (phone is effectively destroyed) applying updates in this way. I also suggest you avoid official Motorola updates, rather use the factory firmware images available here: (which already include the content of OTA Updates)
[INDEX] Moto G [Falcon][Peregrine] Factory Firmware Images​

Thanks for replying anyway mate. In the end, it's all good now. Unlocked and back on CM13 and on my new network !

Ahhh... not so good after all. The phone reboots every time you try to uninstall an app. I've tried flashing back to CM12.1, the latest stable release, and it does the same, so I've obviously screwed something up along the way.
Could someone help me flatten this thing completely and get it working normally please?
I've tried reflashing loads of times, even tried Cyanogen Recovery instead of TWRP but nothing I do gets rid of this reboot problem.
Can anyone assist please?

OK, so I've followed the procedure detailed here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 and flashed the Untouched 5.0.2. EU Stock ROM successfully, but it still reboots when you try to uninstall any app.
Whatever it is that's causing this is not getting overwritten by the flashing procedures I'm using is it ?
HELP !!!!!

@aneng64 - You have not done what I told you to do. Read my post again.

Yes I did... and I still had the same problem. It was only once I stopped trying to flash zips from TWRP and used mfastboot to flash the whole set individually (non-hlos, motoboot etc) that I got it to behave. The issue, incidentally, seemed to be the same one mentioned elsewhere here that also causes settings to crash when you try to go into settings, security.
Once it was stable with a stock ROM, I was able to flash CM13 again and it's now sorted. Thanks for your help anyway.