Database Develop

Recovery Bootloop (XT1053- Unlocked Bootloader)

Hey everyone,
Got myself into an interesting situation here. I have the GSM Unlocked Moto X (XT1053) and I'm using it on T-Mobile USA.
I have unlocked the bootloader, installed TWRP (twrp-2.6.3.1-ghost-4.4), SuperSU, Xposed all that jazz. Phone ran wonderfully until I saw the 4.4.2 update zip.
Downloaded the zip, put the phone into fastboot and attempted to flash the stock recovery. I had some trouble finding it and ended up using the one I found here. After doing this the phone started to bootloop, showing the ugly white "WARNING: BOOTLOADER UNLOCKED" screen and then nothing then looped. I put the phone back into fastboot and reflashed TWRP.
Now the phone just bootloops into TWRP. To attempt to remedy this I fixed permissions, wiped cache/Dalvik but to no effect. I can actually successfully boot into Android if I go into fastboot and select the "Factory" option in the menu, however I seem to have lost my service.
So looks like I broke a pretty big rule, don't flash until you know exactly what it was you had- but I got impatient and greedy and now I'm paying the price :victory:.
How can I repair the damage I've done? I don't mind losing data (currently making a backup in Android).
INFO RECAP
XT1053
rooted, bootloader unlocked 30.B2
twrp 2.6.3.1

http://forum.xda-developers.com/showthread.php?t=2477132
[TOOL] Moto X Toolkit v1.3.4 [Backup/Restore,Drivers,Return to stock,Root,Bootani] you could use this to flash back to stock and get a fresh start
Sent from my Nexus 7 using XDA Premium 4 mobile app

sounds like you flashed something that was not a recovery i would return to stock and then follow this guide
http://forum.xda-developers.com/showthread.php?t=2603358

thanks for the replies,
using the toolkit i have more or less fixed everything. however, my stock recovery is borked- it shows no options, just the android recovery background. i am currently downloading the entire firmware here and plan to extract the stock recovery.img to flash with fastboot.
hopefully this will trigger the ota and everything will be as usual from there on.

DarK_MischieF said:
thanks for the replies,
using the toolkit i have more or less fixed everything. however, my stock recovery is borked- it shows no options, just the android recovery background. i am currently downloading the entire firmware here and plan to extract the stock recovery.img to flash with fastboot.
hopefully this will trigger the ota and everything will be as usual from there on.
Click to expand...
Click to collapse
you can't trigger the OTA even if you are root and have a custom recovery you will still get the OTA you just wont be able to install it.

DarK_MischieF said:
thanks for the replies,
using the toolkit i have more or less fixed everything. however, my stock recovery is borked- it shows no options, just the android recovery background. i am currently downloading the entire firmware here and plan to extract the stock recovery.img to flash with fastboot.
hopefully this will trigger the ota and everything will be as usual from there on.
Click to expand...
Click to collapse
Check this video for booting stock recovery it's kinda tricky yours might not be borked http://www.youtube.com/watch?v=kjNXkRtEQlo&list=PL0V3YBytQ2FudO8sUC_EHgdMqUB_tVb8d

jmcdonald58 said:
Check this video for booting stock recovery it's kinda tricky yours might not be borked http://www.youtube.com/watch?v=kjNXkRtEQlo&list=PL0V3YBytQ2FudO8sUC_EHgdMqUB_tVb8d
Click to expand...
Click to collapse
Thanks for the video, you were correct, my recovery is working as intended. To actually activate the options in the stock recovery you need to hold the Volume up button and press the Power button.
4.4.2 sideloaded successfully, nothing noteworthy for my personal use- wasn't there mention of the Google dialer in a Canadian update release notes?

DarK_MischieF said:
Thanks for the video, you were correct, my recovery is working as intended. To actually activate the options in the stock recovery you need to hold the Volume up button and press the Power button.
4.4.2 sideloaded successfully, nothing noteworthy for my personal use- wasn't there mention of the Google dialer in a Canadian update release notes?
Click to expand...
Click to collapse
I am note sure I usually just use the search feature or google now when looking I have a Nexus 5 I rarely use the dialer but it is nice to have seems like it would be available

[Q] Is Moto G safe to root?

Hi, as the title states, is the new moto g safe to root despite the various bugs and issues with the recovery?

mahendru1992 said:
Hi, as the title states, is the new moto g safe to root despite the various bugs and issues with the recovery?
Click to expand...
Click to collapse
Yea go ahead. Its totally safe to root. No issues or bugs faced till now. Follow this thread : http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245/
I have rooted and flashed TWRP v 2.8.0.1. I am hoping someone compiles a working CWM recovery for our device.

mahendru1992 said:
Hi, as the title states, is the new moto g safe to root despite the various bugs and issues with the recovery?
Click to expand...
Click to collapse
Yes you can root and unlock boot loader but I think the guy who posted it pulled the recovery part and closed his thread due to recovery bug issues.

Okay I will, thanks.
Though what's strange is the version number. I went to the official site of TWRP and the version was 2.8.0.0, but on the root thread, the version is 2.8.0.1.

Better use this recovery i found somewhere (image file, use flashify). With 2.8.0.1 i wasn't eable to create backups
https://drive.google.com/folder/d/0B0AbMwIJ-N7xM25CdjlQOUl2Qlk/edit

marcviado said:
Yes you can root and unlock boot loader but I think the guy who posted it pulled the recovery part and closed his thread due to recovery bug issues.
Click to expand...
Click to collapse
Yup current TWRP v2.8 has some issues while flashing KK ROMS and taking too much time to clear cache. The device reboots automatically while taking a TWRP system backup.
We need a CWM recovery ASAP :fingers-crossed:
---------- Post added at 03:12 AM ---------- Previous post was at 03:06 AM ----------
KingGehl said:
Better use this recovery i found somewhere (image file, use flashify). With 2.8.0.1 i wasn't eable to create backups
https://drive.google.com/folder/d/0B0AbMwIJ-N7xM25CdjlQOUl2Qlk/edit
Click to expand...
Click to collapse
Same here.
Thanks a ton I wanted to rollback to the previous version. I didnt have the latest system backup after the OTA update.

KingGehl said:
Better use this recovery i found somewhere (image file, use flashify). With 2.8.0.1 i wasn't eable to create backups
https://drive.google.com/folder/d/0B0AbMwIJ-N7xM25CdjlQOUl2Qlk/edit
Click to expand...
Click to collapse
No problems with this one right?

mahendru1992 said:
No problems with this one right?
Click to expand...
Click to collapse
v2.7 is relatively bugless as compared to v2.8

mahendru1992 said:
No problems with this one right?
Click to expand...
Click to collapse
Nope, works as expected

Okay, I need a little help here. I flashed the old twrp via fastboot but then got the mismatched partition size error. Well I thought what the hell, and I selected recovery from the menu, but the problem is that the phone doesn't go into recovery, just reboots. What should I do?
EDIT: I also tried rebooting via recovery when the phone wasn't connected to the laptop. If i press the power button on any of the options - normal powerup, recovery, factory or barcodes - the phone switches off.
EDIT 2: I tried getting into recovery via adb, but all I get is a 'no command' message when the phone reboots. A quick google search showed me that the no command message means that the phone still has the stock recovery. It seems like twrp isn't flashing. Any ideas!?

Nvidia SHIELD Portable Root

Hi everyone!
This morning I woke up to find my SHIELD with the so waited notification of Lollipop update. I'm really happy to finally have lollipop running on my device, but sadly I found a problem after the update. I was trying to re-root my device, but neither the SHIELD RAM tool or Root Genius could do the trick. But I didn't gave up, I searched in Google any way to root my SHIELD with the still fresh update, and found that the Kinguser app can root it without trouble.
You just need to download the apk, install it on your SHIELD and open it.
Btw, the old recovery isn't working anymore, you can flash it with the RAM tool, but the device will reflash the stock recovery.

twrp works, but SU binary still wont flash :/
edit - the combination of this APK and TWRP gave me all I need for root + rebooting and keeping root

Yeah, I was about to say that. The TWRP recovery works like a charm, but Supersu binary won't install. But well, the KingRoot app is pretty good.

I can confirm some problem with supersu and update 103. I flashed 2.46 and my portable wouldn't boot. Like, something broke so bad I had to reflash 101 and update again. The later might indicate backups are broke in my twrp, I'll have to look into that. For now, I'm going try kingroot as suggested here and continue other development.

Steel01 said:
I can confirm some problem with supersu and update 103. I flashed 2.46 and my portable wouldn't boot. Like, something broke so bad I had to reflash 101 and update again. The later might indicate backups are broke in my twrp, I'll have to look into that. For now, I'm going try kingroot as suggested here and continue other development.
Click to expand...
Click to collapse
So you were successful in getting TWRP installed, SuperSU installed and removing KingRoot clean - leaving only SuperSU on the system, surviving a reboot?

Ink Rampant Wolf said:
Yeah, I was about to say that. The TWRP recovery works like a charm, but Supersu binary won't install. But well, the KingRoot app is pretty good.
Click to expand...
Click to collapse
hey wolf, what is the easiest way to flash twrp with the 103 upgrade? thanks

You might wanna include the instructions as shown here,
http://forum.xda-developers.com/xpe...how-to-root-lollipop-xperia-tablet-z-t3115107
It basically tells you how to install SuperSU and remove the entire KingRoot library after that. It worked on my Z and on my SHIELD as well.

This was essentially what I did:
http://greenrobotgamer.com/shieldzone/root-shield-portable-lollipop-5-1/

Mine seems to be working just fine, after obtaining root and installing SuperSU. I didn't bother with installing TWRP, I just hotboot the recovery. I'm rebooting my SHIELD as we speak, see if there's any issue
EDIT: Scractch that, it's not booting. How do I flash the latest image back in?

JCESAR2 said:
hey wolf, what is the easiest way to flash twrp with the 103 upgrade? thanks
Click to expand...
Click to collapse
Boot the SHIELD in fastboot and connect it to your pc, then open a command window in a folder with the adb files and the recovery image and type: fastboot flash recovery -the name of the recover-.img, and it will flash the recovery. You can do that with the stock too.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.

Ink Rampant Wolf said:
Boot the SHIELD in fastboot and connect it to your pc, then open a command window in a folder with the adb files and the recovery image and type: fastboot flash recovery -the name of the recover-.img, and it will flash the recovery. You can do that with the stock too.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Click to expand...
Click to collapse
thanks for the reply, also, when i boot the shield into fastboot it says in the first line : boot loader version ..../ device locked, does that matter? i rooted the shield already with kingroot.

JCESAR2 said:
thanks for the reply, also, when i boot the shield into fastboot it says in the first line : boot loader version ..../ device locked, does that matter? i rooted the shield already with kingroot.
Click to expand...
Click to collapse
You need to unlock your bootloader first.

ok long story short: since i had the shield drivers installed and tha adb drivers installed i did the oem unlock and after a confirmation screen on the shield i did it, then i immediately flashed the twrp image from the same command line. now the shield is stuck in nvidia android boot logo. any suggestions? thanks

I am in fact stuck in the boot as well. Anyone's got stock image we can flash?

nevermind, after like 10 minutes the thing just booted fine, these are the perks of being a newb.

341464 said:
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
Click to expand...
Click to collapse
JCESAR2 said:
nevermind, after like 10 minutes the thing just booted fine, these are the perks of being a newb.
Click to expand...
Click to collapse
Search for the SHIELD RAM Tool, it have everything that you all need to flash recovery or old firmware to unbrick the device. It also comes with the necessary files and drivers to work ADB Fastboot.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.

Ink Rampant Wolf said:
Search for the SHIELD RAM Tool, it have everything that you all need to flash recovery or old firmware to unbrick the device. It also comes with the necessary files and drivers to work ADB Fastboot.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Click to expand...
Click to collapse
Guess I'll have to flash the old firmware then, it's been sitting there forever.

341464 said:
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
Click to expand...
Click to collapse
try this shield thread
http://forum.xda-developers.com/showthread.php?t=2388870

JCESAR2 said:
try this shield thread
http://forum.xda-developers.com/showthread.php?t=2388870
Click to expand...
Click to collapse
I just re-flashed the system using RAM, should be fine now. I'll just have wait for the OTA all over again. UGH.
I wish someone could provide a KitKat version tho.
EDIT: Annnd battery's at 15% so the system won't let me OTA yet.

SuperSU will work fine with my latest TWRP builds posted here. The older 2.8.5.0 builds will not work, neither will any build in the linked thread before yesterday. I used SuperSU 2.49 Beta and it worked as expected.
Side Note: The older builds will have the problem where boot will just hang. That seems to be because the older builds didn't have selinux policies built in, so some things never get set up right and the boot panics.

Flashed a TWRP Recovery but can't boot into recovery...

Everytime I install the TWRP Recovery and try to boot into recovery mode it just reboots to the regular phone framework.
Whats going on and what do I do now?
HTC Desire 626s
Bootloader Unlocked
using this twrp recovery from here
Edit: So I rooted my phone using the Cyanogenmod recovery since I had gaven up and just tried the next best thing,I got SuperSU Binaries & APK installed so I'm all good. However I would like to know if there is anything I should know when using a recovery and why in the above forum thread they said to use the TWRP method instead of Cyanogenmod ("Highly recommended")
Thank you for your time XDA (aprox. 14minutes replies and 18minutes views)!

EDIT: just realized you incluided your twrp source. Try mine from here
i had the same issue, it means the twrp you used isnt right for your phone. is the twrp you used mine? if so, you need to go into bootloader mode and tell me what the hardware model of your phone. should start with a32XXX i developed for the a32eul and tmobile.
If you grabbed it from captain_throwback that is meant for the sprint variant. there are no other twrp for any other carriers.

Jmingels said:
EDIT: just realized you incluided your twrp source. Try mine from here
i had the same issue, it means the twrp you used isnt right for your phone. is the twrp you used mine? if so, you need to go into bootloader mode and tell me what the hardware model of your phone. should start with a32XXX i developed for the a32eul and tmobile.
If you grabbed it from captain_throwback that is meant for the sprint variant. there are no other twrp for any other carriers.
Click to expand...
Click to collapse
Just an FYI, captain throwbacks version worked on my MetroPCS variant.
To the OP, did you ever have any custom recovery flashed? Like the partially working CM recovery ? If you have root access already you could use rashr or flashify to flash a recovery .img

Jmingels said:
EDIT: just realized you incluided your twrp source. Try mine from here
i had the same issue, it means the twrp you used isnt right for your phone. is the twrp you used mine? if so, you need to go into bootloader mode and tell me what the hardware model of your phone. should start with a32XXX i developed for the a32eul and tmobile.
If you grabbed it from captain_throwback that is meant for the sprint variant. there are no other twrp for any other carriers.
Click to expand...
Click to collapse
Thank you for replying anyway,unfortunate I can't use it anymore (or don't have to),
Used the Cyanogenmod method from the same thread mentioned in OP's Post.
My carrier is TMobile (comes with the app & stuff).
If I tried the Sprint variant should I be worried I tried (and failed)?
talksickisil said:
Just an FYI, captain throwbacks version worked on my MetroPCS variant.
To the OP, did you ever have any custom recovery flashed? Like the partially working CM recovery ? If you have root access already you could use rashr or flashify to flash a recovery .img
Click to expand...
Click to collapse
The partially working CM recovery? Perhaps you are referring to Cyanogenmod?
I didn't try anything but this TWRP,but now I used the Cyanogenmod and installed the SuperSU v2.52 binaries and everything,so its fine now,but if you are referring to Cyanogenmod then why is is partially working and should I be aware of any problems?

Xevioni said:
Thank you for replying anyway,unfortunate I can't use it anymore (or don't have to),
Used the Cyanogenmod method from the same thread mentioned in OP's Post.
My carrier is TMobile (comes with the app & stuff).
If I tried the Sprint variant should I be worried I tried (and failed)?
The partially working CM recovery? Perhaps you are referring to Cyanogenmod?
I didn't try anything but this TWRP,but now I used the Cyanogenmod and installed the SuperSU v2.52 binaries and everything,so its fine now,but if you are referring to Cyanogenmod then why is is partially working and should I be aware of any problems?
Click to expand...
Click to collapse
Before captain throwbacks TWRP somebody had uploaded a version of cyanogen mod recovery to work on the desire 626s. But it wasn't fully functional. It didn't read from external storage which also made nandroid backups not an option. But what it did do however, is allow us to flash super SU from internal storage. But if you have flashed superuser and have achieved root you can go ahead and flash the twrp .IMG with rashr or flashify
---------- Post added at 08:56 AM ---------- Previous post was at 08:54 AM ----------
As far as which one you should use, use the one Jmingels posted as he says that works on T-Mobile ... I can only confirm MetroPCS for captain throwbacks version. I'm not sure about if it will work for a t mobile phone or not. But if the recovery you have is the CM one posted in the how to root thread you are definitely going to want to update to twrp for a full featured recovery. Just download jmingels file, download rashr or flashify from playstore, and install the .IMG file you downloaded.. With rashr select recovery from storage, or with flashify select flash a recovery/choose file,flash it, reboot, done. Easy as that

talksickisil said:
Before captain throwbacks TWRP somebody had uploaded a version of cyanogen mod recovery to work on the desire 626s. But it wasn't fully functional. It didn't read from external storage which also made nandroid backups not an option. But what it did do however, is allow us to flash super SU from internal storage. But if you have flashed superuser and have achieved root you can go ahead and flash the twrp .IMG with rashr or flashify
---------- Post added at 08:56 AM ---------- Previous post was at 08:54 AM ----------
As far as which one you should use, use the one Jmingels posted as he says that works on T-Mobile ... I can only confirm MetroPCS for captain throwbacks version. I'm not sure about if it will work for a t mobile phone or not. But if the recovery you have is the CM one posted in the how to root thread you are definitely going to want to update to twrp for a full featured recovery. Just download jmingels file, download rashr or flashify from playstore, and install the .IMG file you downloaded.. With rashr select recovery from storage, or with flashify select flash a recovery/choose file,flash it, reboot, done. Easy as that
Click to expand...
Click to collapse
Alright,Thank you very much for this explanation,I'll keep note of this and go ahead and flash the t-mobile one at some point today or tomorrow.

Currently rooted on 20i MM, what do I need to do if I want to update? (with root)

Hey XDA,
I'm currently rooted on T-Mobile's H811 version 20i. I just got the stupid update notification and I'd like to get rid of it (by updating to the latest version, and root the phone + install a custom ROM).
I can backup most of my data through Google and all my pictures are on my SD card, so I dont have to worry about losing data through the upgrade.
What steps do I need to take to:
• Update my G4 to the latest version + root
• (dont delete my photos from my SD card)
I'm afraid I'll brick my G4, since I almost brick it the last time I rooted my G4.
Thank you!

You still get over the air update even if your rooted. If you custom recovery it, you will no longer get over the air update from tmobile. Its a good thing i flash my stuff using twrp manager.

SilentBangHD said:
You still get over the air update even if your rooted. If you custom recovery it, you will no longer get over the air update from tmobile. Its a good thing i flash my stuff using twrp manager.
Click to expand...
Click to collapse
Do I keep my root and everything? Or does the root break (like on iOS devices)

NoWayIn said:
Do I keep my root and everything? Or does the root break (like on iOS devices)
Click to expand...
Click to collapse
Once rooted you will always be rooted unless you delete the root files. For every new version of android comes out, there need to be new method to root your phone. But since you've rooted, you will keep the root even if you updated to new android version. Even factory reset cant get rid of root. you cant get rid of it updating to new version of android. (correct me if im wrong)

Well, I clicked the install button and my phone went into two recovery but it failed to install the update. However , the notification is gone now so I guess that's ok

NoWayIn said:
Well, I clicked the install button and my phone went into two recovery but it failed to install the update. However , the notification is gone now so I guess that's ok
Click to expand...
Click to collapse
Lucky you ( Else you would have been stuck on TWRP Screen) till you flash the G4, best way to update when you are rooted and custom recovery installed is to use LGUP. Download latest KDZ file of 20o and flash it via KDZ you will loose recovery only but all your stuff and Root remains.

SignatureBoy said:
Lucky you ( Else you would have been stuck on TWRP Screen) till you flash the G4, best way to update when you are rooted and custom recovery installed is to use LGUP. Download latest KDZ file of 20o and flash it via KDZ you will loose recovery only but all your stuff and Root remains.
Click to expand...
Click to collapse
OMG that would suck, because I am leaving to go to the airport tomorrow so I NEED my phone.
I'm going to update tomorrow in the morning before I go, in case there was some problem.
Thanks man.

Mine is rooted and unlocked on 20i. I flashed TWRP 2.8.7.2. I did remove a couple OEM apps that were a bit annoying. I back-up the 3 suggested partitions, system, boot, data.
Can I update to the OTA using just TWRP or adb/fastboot without screwing the pouch?
Or do I need to take a different route to the OTA?

NoWayIn said:
Well, I clicked the install button and my phone went into two recovery but it failed to install the update. However , the notification is gone now so I guess that's ok
Click to expand...
Click to collapse
once you take 20o you stuck there so you cant downgrade or youll brick phone..
---------- Post added at 07:00 PM ---------- Previous post was at 06:58 PM ----------
metropical said:
Mine is rooted and unlocked on 20i. I flashed TWRP 2.8.7.2. I did remove a couple OEM apps that were a bit annoying. I back-up the 3 suggested partitions, system, boot, data.
Can I update to the OTA using just TWRP or adb/fastboot without screwing the pouch?
Or do I need to take a different route to the OTA?
Click to expand...
Click to collapse
if you do youll get camear and sound problems... the best way its to start fresh..
download LGUP and h811 20o KDZ. the flash using refurbished this will wipe everything.. then install twrp and root..

I really find LG way more annoying than HTC ever was. This should be a simple process.
Finally got LGUP working on Virtual Box 5.026 running W7, from Mavericks OSX. But it took some doing to get the 20o update in.
Had to add Guest additions to VB in order to enable USB 2 control, so VB would see the LG.
And the proper LG Mobile drivers v4.04.exe.
A restart or 2 of the Mac.
Then ran LGUP, changed the browse extension to .kdz and navigated to the H81120o_00_0613.kdz.
LGUP ran and the G4 restarted a few times over about 5 mins or so.
Can't get twrp flashed.
I get this error: FAILED (remote: unknown command).
So I disregarded and tried fastboot boot twrp-2.img.
File not found.
Ideas?

this from Macs Terminal app or I suppose the equal in Doze 7.
Terminal:
adb reboot bootloader
fastboot boot (drag and drop the twrpxxx.img into the Terminal window)
This will boot you into a "temp" TWRP recovery. Install twrp.img (select .img button bottom right)
Then install SuperSu 2.6.7.zip.
REBOOT SYSTEM