Database Info

[Q] Stuck in TWPRP menu?

Last night i was unlocking the bootloader and it worked but i am now stuck in the TWRP menu and cannot do anything. I have tried to factory reset and nothing works. can someone please help me restore my phone to stock?

hodorprime said:
Last night i was unlocking the bootloader and it worked but i am now stuck in the TWRP menu and cannot do anything. I have tried to factory reset and nothing works. can someone please help me restore my phone to stock?
Click to expand...
Click to collapse
I did this on a OnePlus this am, so I wonder if it would work for a G3 as well? Hopefully someone with better know how will stop by.
Perhaps consider entering fast boot with your phone, on your PC use adp along with the full ROM version you wish to 'return to'. Unzip the ROM into the directory where adp is. Use the adp command to make sure your device is seen, of so you should be good.
There is a flash all .bat file that will flash all the necessary files, one at a time, and you can reboot from there. I'm in-between patients, so can not look up the link right now.
Remember, the above was for a OnePlus. Since they are both Android, I'm hoping someone will confirm this will work on a G3, as well.

http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827

[Completed] [Q] Can I update android version after rooting, if so how ?

Today when I decided to update to the latest android (5.1.1) with rooted nexus 5. I rebooted
my phone and it started installing when suddenly a picture of the android robot with a red triangle sign on top appears and under it it says error so I restarted my phone by holding down the power button for several seconds and when I get in to my phone it says that I'm updated to 5.1. But what I understand that's correct so now I'm wondering how to deal with future updates because I can't afford to brick my phone and I thought I could just download OTA updates normally after root so my question is, can I normally install OTA updates, if not How?
[Edit]Later today I got the update to 5.1.1 message again and its really annoying and I want the update now so how do I get it?
Thanks for reading.

Hi, thank you for using XDA Assist. No, you can't use the OTA if your rooted with 5.x and above. To update you'll most likely need to flash the stock frimware. but you never let us know what your device is so i can't point you in the right direction.

jd1639 said:
Hi, thank you for using XDA Assist. No, you can't use the OTA if your rooted with 5.x and above. To update you'll most likely need to flash the stock frimware. but you never let us know what your device is so i can't point you in the right direction.
Click to expand...
Click to collapse
Thank you for answering, I have a nexus 5 but I guess I´ll have to flash the stock firmware if there is no other way that isn´t too complicated.

All right. You'll want to see these, http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217 , http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217 It's possible to update by only flashing the system, boot, and radio images files with fastboot. You'll lose root but you can easily regain it by flashing supersu in your custom recovery.
Also don't forget there's a complete forum for the Nexus 5 here, http://forum.xda-developers.com/google-nexus-5

jd1639 said:
All right. You'll want to see these, http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217 , http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217 It's possible to update by only flashing the system, boot, and radio images files with fastboot. You'll lose root but you can easily regain it by flashing supersu in your custom recovery.
Also don't forget there's a complete forum for the Nexus 5 here, http://forum.xda-developers.com/google-nexus-5
Click to expand...
Click to collapse
I just spent 2 hours trying to flash the system but all i ended up with was a factory reset after following this guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 so all i want to do now is just getting rid of root so I can update but the guides that i understand doesn´t work because when I tried to flash the hammerhead bootloader it said the my device requires another version. The i took the version that my nexus is in right now 5.1.0 and it appeared to be working so when it was finished I followed the guide and i wiped my system for about 5 minutes and then i chose reboot system from the recovery mode menu. And now im back at where i started.
(Edit) Now I´m installing SDK and following another guide online http://www.talkandroid.com/guides/b...-lollipop-factory-image-on-your-nexus-device/

It turns out all i had to do was to unlock my phone and then I installed 5.1.1 just fine

Yep, that's the first step. Glad you got it working. I'll close this thread.

OPO recovery boot error.

So, while I was messing around with my phone, I accidentally screwed stuff up. Unfortunately, I decided to get extra stupid and lock my bootloader. So now whenever i try to unlock my bootloader, boot into recovery or basically do anything beyond using CM11s, I get this youtu.be/tuWRHJA50hA. If any of you have any solutions, please help. If you need any extra details, I will be glad to answer. Thanks in advance for the help.

kurroption said:
So, while I was messing around with my phone, I accidentally screwed stuff up. Unfortunately, I decided to get extra stupid and lock my bootloader. So now whenever i try to unlock my bootloader, boot into recovery or basically do anything beyond using CM11s, I get this youtu.be/tuWRHJA50hA. If any of you have any solutions, please help. If you need any extra details, I will be glad to answer. Thanks in advance for the help.
Click to expand...
Click to collapse
You need to provide more information, like a detailed description of exactly what steps lead to this situation.

Heisenberg said:
You need to provide more information, like a detailed description of exactly what steps lead to this situation.
Click to expand...
Click to collapse
I wrote a detailed explanation on the OnePlus forums so here is it copy pasted.
TL;DR: Recovery won't boot, this happens
I've posted this on multiple sites to get as much help as possible. Check /u/braden26 for my posts on reddit about my issue. What I'm having trouble with is a strange issue when entering a recovery. . I'm guessing my recovery is corrupted or nonexistent, due to a few dumb mistakes I made. I first flashed the wrong rom and soft bricked my phone. At this time it was rooted, running cm 12.1 nightlies and using twrp. After this soft brick, I restored to cm11s, unlocked the bootloader and rooted. I installed sultan's cm12.1, but got another weird issue, so I decided to go back to cm12.1. Here's where my issue begins. When I tried to enter recovery, twrp was gone despite developer option for overwriting recoveries was off. So I downgraded to cm11s and tried again. Then it wouldn't install twrp at all. So I erased my recovery and accidentally hit oem lock instead of unlock. When I tried oem unlock after wards, it would reboot then do this which I already showed . The device runs fine, but I can't update cm11s to 12s or I stall custom recoveries. So I'm in a little bit of a problem here. I'm familiar with how to use fastboot, not all the commands, so don't be afraid to give them to me. Thank you for any help and if you need any more details please let me know.

kurroption said:
I wrote a detailed explanation on the OnePlus forums so here is it copy pasted.
TL;DR: Recovery won't boot, this happens
I've posted this on multiple sites to get as much help as possible. Check /u/braden26 for my posts on reddit about my issue. What I'm having trouble with is a strange issue when entering a recovery. . I'm guessing my recovery is corrupted or nonexistent, due to a few dumb mistakes I made. I first flashed the wrong rom and soft bricked my phone. At this time it was rooted, running cm 12.1 nightlies and using twrp. After this soft brick, I restored to cm11s, unlocked the bootloader and rooted. I installed sultan's cm12.1, but got another weird issue, so I decided to go back to cm12.1. Here's where my issue begins. When I tried to enter recovery, twrp was gone despite developer option for overwriting recoveries was off. So I downgraded to cm11s and tried again. Then it wouldn't install twrp at all. So I erased my recovery and accidentally hit oem lock instead of unlock. When I tried oem unlock after wards, it would reboot then do this which I already showed . The device runs fine, but I can't update cm11s to 12s or I stall custom recoveries. So I'm in a little bit of a problem here. I'm familiar with how to use fastboot, not all the commands, so don't be afraid to give them to me. Thank you for any help and if you need any more details please let me know.
Click to expand...
Click to collapse
You were using a toolkit?
Ok, so TWRP didn't initially stick and that's normal since Lollipop came out. It's in the FAQ thread, so doing some research most likely would have saved you from this whole situation. Right now though you're kinda screwed. With no recovery and a bootloader that won't unlock there's pretty much nothing you can do.

Bootloop 2013 Moto G Boost Mobile XT1031 8GB

Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.

blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.

I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.

You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?

blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).

_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.

@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!

Recovery/Bootloader

So is it really so that the Xperia XZ does not have a recovery/bootloader menu?
I have unlocked the bootloader which needed the fastboot which works but now that I want to root the device and need TWRP I am getting nowhere since I can not get the device to go into recovery mode. this is annoying me badly, my phone is basically useless until I am done with this.
Any advice?

kane_1371 said:
So is it really so that the Xperia XZ does not have a recovery/bootloader menu?
I have unlocked the bootloader which needed the fastboot which works but now that I want to root the device and need TWRP I am getting nowhere since I can not get the device to go into recovery mode. this is annoying me badly, my phone is basically useless until I am done with this.
Any advice?
Click to expand...
Click to collapse
During the initial unlocking of the device of course it doesn't carry any recovery. Maybe ought to try powering down your device and press and hold the volume up key while connecting your device to the computer until the blue led is lit that's fastboot mode. Do this fastboot flash recovery recovery name.img then try accessing recovery after that. You now should have a working recovery.
---------- Post added at 06:09 AM ---------- Previous post was at 06:06 AM ----------
You can find the available recovery.img on androplus website https://kernel.andro.plus/tone2.html for your corresponding firmware and androplus kernel fastboot flash boot boot.img.
---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------
The available instructions are posted on the website. Please make sure you have the perquisites.

Thanks.
Would you recommend running a custom rom or sticking to stock android and run xposed?

also, the first step it say boot into recovery bootloader, I don't understand how i am supposed to do that when there is none in the beginning.

I have tried everything any guide says and it just doesn't seem to work.
The adb says waiting for device as if the device is not there, the one click tool just doesn't do anything.
Idk anymore

kane_1371 said:
I have tried everything any guide says and it just doesn't seem to work.
The adb says waiting for device as if the device is not there, the one click tool just doesn't do anything.
Idk anymore
Click to expand...
Click to collapse
background (look at the date - some content is for Z3 xperias and older that do not have DM-Verity):
https://forum.xda-developers.com/crossdevice-dev/sony/noob-guide-to-sony-ericsson-xperia-t3209012
For the newer phones follow the instructions you find in the device-fora.
Here (after a full wipe) you get started following the instructions written by AndroPlus.
You need the right ROM and TWRP (recovery) for your ROM-version. Look at the changelog.
e.g.: I am on 39.2.A.0.374. There is no kernel for that right now -> I can not get into recovery -> no root for me ATM
fastboot boot TWRP_xy boots the recovery
You will become a "developer" on your device once you tapped seven times on the build number -> then you switch on adb debugging in the developer options

"When you unlock your bootloader you will lose all the DRM features on your device, this makes it valuable to have a backup of the unmodified version stowed away somewhere safe. You will need root level access to create that backup before unlocking. There is a tool called Backup TA which is widely used to create and restore backups of the TA partition. TWRP in XZDualRecovery can do the same. "
What the heck?
I need to backup TA, ok, but I need to have root to do this? ok, but to have root access I need to unlock my bootloader and flash a root boot which messes up with the TA?
It seems like every single one of these posts that I read just make things more confusing.
Why can't there just be a simple step by step that tells you what to do?
NVM, I actually flashed a recovery into the phone by using a combination of one click tool and Quickimage.
God this community need better tutorials and step by steps
Anyway now it is asking me for a password which is a surprise to me
OK past that too, did a backup and no I see that I have nothing but the recovery to boot to, hmmmm still figuring this thing out
It is amazing to imagine how **** is constantly hitting the fan.
The quick image thread has very little explanation and two screen shots which show that they are flashing the image to boot.
So I did exactly that and now I have no Boot but a recovery instead hhahahahahaha.
I am fairly depressed and desperate at this point
Well I somehow managed to install Xplayztation.
As mentioned before the only way possible for me to get a recovery installed was through flashing it on boot and loosing my access to the android at first and then installing a new rom through Twrp.
I have no idea what will the outcome for this be.
Any suggestions?

kane_1371 said:
God this community need better tutorials and step by steps
Click to expand...
Click to collapse
Go ahead!
You will find everything HERE and on
https://forum.xda-developers.com/crossdevice-dev/sony
There is more than plenty on the Z5 and Z3+ foro too...
In the Z5 forum you can really get to the technical beef if you want. The tutorial I quoted is gentle but written at a time when it was easier to root the devices.
The TA-Backup works via a vulnerability that raises the rights temporarily. This is not rooting per se since this does not survive a reboot.
Why can't there just be a simple step by step that tells you what to do?
Click to expand...
Click to collapse
Here on this forum (after a full wipe) you get started following the instructions written by AndroPlus.
or:
https://forum.xda-developers.com/showpost.php?p=70370065&postcount=7

DHGE said:
Go ahead!
You will find everything HERE and on
https://forum.xda-developers.com/crossdevice-dev/sony
There is more than plenty on the Z5 and Z3+ foro too...
In the Z5 forum you can really get to the technical beef if you want. The tutorial I quoted is gentle but written at a time when it was easier to root the devices.
The TA-Backup works via a vulnerability that raises the rights temporarily. This is not rooting per se since this does not survive a reboot.
Here on this forum (after a full wipe) you get started following the instructions written by AndroPlus.
or:
https://forum.xda-developers.com/showpost.php?p=70370065&postcount=7
Click to expand...
Click to collapse
Thanks for the links man.
Well I somehow managed to install Xplayztation.
As mentioned before the only way possible for me to get a recovery installed was through flashing it on boot and loosing my access to the android at first and then installing a new rom through Twrp.
I have no idea what will the outcome for this be.
Any suggestions?
Also I had already unlocked my bootloader when I learned about TA backup.
And then was confused that I am supposed to Root for it to work, so what are my options now?
Are the DRM keys reverseable through flashing my regions latest firmware via the flashtool?

kane_1371 said:
Thanks for the links man.
Also I had already unlocked my bootloader when I learned about TA backup.
Click to expand...
Click to collapse
You are welcome
Your TA-keys are gone. NO WAY to revover them. Do not even try - you will hardbrick your phone.
Follow the links I gave.

OK
Well I have the insurance on it, so if anything ever happens that is not reversible I will bust the phone and get a new one lol.
For now I will enjoy the stuff
It was a lot of trouble but I got what I wanted (moded Spotify app haha )

I want to root my xz too. Did you root it. If you did, how.? Plz reply

Im just gonna ask confirmation New to sony scene and never knew i had to backup the TA partion (Shouldve came here first normally would) but i assume theres no way to recovery DRM keys (i did install Androplus Kernel)

Well yes I did manage to do the work but I imagine the XZ is built in a manner that you can not root it without burning all the bridges behind you however I am basically the only person in this forum that I found to either have rooted their XZ or had to go through these many hassles.
As you can read in earlier posts I did have to backup the TA but by the time I knew about that I had already deleted the TA. The extended permission didn't work for me either so Idk if it was me doing something wrong or Sony going hard against rooters.
Also no TA is not reversible so once you do root and if you don't have the TA backed up don't even go for reinstalling the original rom because it will not work period.
I had to flash my boot and install recovery on that which is not the intended way of using recovery but I couldn't do it any other way, when you do that you basically are left with a paperweight the shape of a phone and then from there I would go to Boot instead of recover since recovery partition was empty and the recovery image was flashed on boot partition and use the recovery to install the rom.
But you should try to follow the step by steps posted in this forum by other people so maybe you won't have to endure the pain I did.
I have to say at this time I really feel like it wasn't even worth it because XZ is a pretty underwhelming phone even though I had a busted Z3 before this I never experienced such a slow phone with that.
XZ is just constantly out of ram and slows down and reboots the rom's shell which is pretty annoying.