Develop Bugs

Rooting phone without wiping

Hello, I'm not sure if this has been discussed before, but atleast I didn't find a complete answer to my question.
I unlocked my bootloader some time ago, and I flashed a new Image, a stock 4.2 maguro image, but the problem is that I forgot to root the new image, i've been using my phone for some time now, and I wanted to root the phone, but is there a way to root the phone without wiping all the data and settings?
Braien

is your bootloader still unlocked?
if so, just flash or boot into a custom recovery and then flash the supersu.zip package. this will not wipe your data.

Zepius said:
is your bootloader still unlocked?
if so, just flash or boot into a custom recovery and then flash the supersu.zip package. this will not wipe your data.
Click to expand...
Click to collapse
Should be unlocked, but how can I be sure of that?
And how can I enter the custom recovery, I can't remember.

braien334 said:
Should be unlocked, but how can I be sure of that?
Click to expand...
Click to collapse
2 ways,
when you reboot your phone, do you see a little unlocked lock?
other way: boot into fastboot mode and the lock status will say "UNLOCKED"

braien334 said:
Should be unlocked, but how can I be sure of that?
Click to expand...
Click to collapse
During the boot, the padlock in the lower half is open if the device is unlocked .

Okay, it's unlocked, but how to enter the recovery mode?
If I press volume up+down and power, and I select recovery, it just says no command.
Is there some tutorial for rooting like this?

http://forum.xda-developers.com/showthread.php?t=1529058
follow the section after unlocking your device.

I used Nexus toolkit, but I guess it works the same, but is automatic.
But thanks anyways:good:

[Q] Trying a custom ROM for the first time from complete stock

Hi,
I'm looking to try some 4.4 custom ROMs on my GF's GSM Galaxy Nexus for the first time coming from stock.
Am I right that, I need to: 1) Unlock the bootloader and 2) Install a custom recovery before I can flash a ROM, right?
What would we be the easiest way to achieve both? I've read some stickied posts and I think using the Nexus toolkit is the easiest way. Someone please let me know if it isnt.
Also, I shouldn't worry about rooting the device for now, right?
One last question, I plan to factory reset the phone before installing the custom ROM. A NANDROID backup should allow me to easily revert back to the pristine stock if ever my GF doesnt like the custom ROM, right?
Hope someone can help clarify these things before I actually go on and try the whole thing.
Thanks.

@torchwood0829
You can use the toolkit but I would use command prompt / terminal for unlocking bootloader and flashing recovery.
1. When you unlock the bootloader all data from Nexus will be gone.
2. You need Nexus USB / Fastboot / ADB drivers:
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW
3. You need fastboot files:
http://galaxynexusroot.com/galaxy-n...iversal-guidegsmverizonsprintwindowslinuxmac/
4. Command to unlock the boot loader:
fastboot oem unlock
5. Command to flash recovery:
fastboot flash recovery file-name.img
CWM recovery .img file: http://www.clockworkmod.com/rommanager
To root: Don't worry about it...

Carlos_Manuel said:
@torchwood0829
You can use the toolkit but I would use command prompt / terminal for unlocking bootloader and flashing recovery.
1. When you unlock the bootloader all data from Nexus will be gone.
2. You need Nexus USB / Fastboot / ADB drivers:
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW
3. You need fastboot files:
http://galaxynexusroot.com/galaxy-n...iversal-guidegsmverizonsprintwindowslinuxmac/
4. Command to unlock the boot loader:
fastboot oem unlock
5. Command to flash recovery:
fastboot flash recovery file-name.img
CWM recovery .img file: http://www.clockworkmod.com/rommanager
To root: Don't worry about it...
Click to expand...
Click to collapse
Thanks for the reply.
Will try the command prompt method.
After I unlock bootloader and flash CWM, i'm basically left with factory reset phone, right? Would be a great time to do a NANDROID backup then so I can revert to it in case I want to, right?

torchwood0829 said:
Thanks for the reply.
Will try the command prompt method.
After I unlock bootloader and flash CWM, i'm basically left with factory reset phone, right? Would be a great time to do a NANDROID backup then so I can revert to it in case I want to, right?
Click to expand...
Click to collapse
When you unlock your phone, it'' be automatically wiped... so you don't have to do any factory reset.
I don't know how do you make a nandroid backup when boot loader is locked and recovery is the stock one..

It is just one time wipe when unlocking bootloader. If you decide to revert to stock, you can flash factory image and start over.
Unlocked bootlader gives you ability to flash custom recovery which gives you nandroid backup.

Nexus 5X Permanently Bricked and Locked

I unlocked the Nexus 5X, installed TWRP recovery and then locked the bootloader again. Locking the bootloader stops TWRP from working and stops the phone from booting into Android. And since the phone is locked, it's impossible to install anything else via the bootloader or unlock it since Android doesn't boot. I think the phone is now permanently bricked and locked.

Don't have my phone yet, but can you boot into the bootloader? That's usually all you need to unlock the bootloader via fastboot. Did you try the skipsoft toolkit?

Shouldn't you just be able to power volume down boot into the bootloader. Then fastboot oem unlock and then go from there?
Sent from my Nexus 5X using Tapatalk

The_Automator said:
Shouldn't you just be able to power volume down boot into the bootloader. Then fastboot oem unlock and then go from there?
Click to expand...
Click to collapse
Nope. You have to enable unlocking from within Android before the device can be unlocked from the bootloader. And since Android won't boot up after the device is re-locked... "fastboot oem unlock" fails with "FAILED (remote: oem unlock is not allowed)".

Twrp is in the recovery partition, which is not the same partition the boot loader resides in.
Since the only way to lock the boot loader is via fastboot, and since you successfully did this, we know your boot loader is working. Get back into the boot loader and unlock your device. You can enter the boot loader via hardware key combination. Also, you can enter the boot loader even if the phone has no is and no recovery since it is independent of those.

_jordan_ said:
Twrp is in the recovery partition, which is not the same partition the boot loader resides in.
Since the only way to lock the boot loader is via fastboot, and since you successfully did this, we know your boot loader is working. Get back into the boot loader and unlock your device. You can enter the boot loader via hardware key combination. Also, you can enter the boot loader even if the phone has no is and no recovery since it is independent of those.
Click to expand...
Click to collapse
I can get into the bootloader no problem. In the bootloader, the DEVICE STATE is locked. When I do "fastboot oem unlock" it fails with:
FAILED (remote: oem unlock is not allowed)
This is because you must first enable unlocking in the Settings menu in Android before the fastboot command works. Android doesn't boot anymore since I re-locked the device, so there is no way to unlock the device...hence it is permanently bricked.

Interesting didn't know that the developer option for oem unlocking unchecked itself when you locked the bootloader. That seems pretty dangerous
Sent from my Nexus 5X using Tapatalk

Can you enter safe mode? I thought there's a safe mode function built into Android
Sent from my Nexus 5

Can't you just flash a stock recovery?

@simms22 they need your help here Same issues as w/ Nexus 6.

nyjumpman said:
Can't you just flash a stock recovery?
Click to expand...
Click to collapse
Nope. You can't flash stock images unless the device is unlocked. If I run "flash-all.sh" it says "FAILED (remote: device is locked. Cannot flash images)".
This phone is totally bricked.

fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
Do these work?
I'm pulling out stuff from an interesting N9 thread
Which linked to this post

PhoenixTank said:
Do these work?
I'm pulling out stuff from an interesting N9 thread
Which linked to this post
Click to expand...
Click to collapse
Nope. "fastboot format userdata" returns:
FAILED (remote: device is locked. Cannot erase)

I'm not sure why your phone isn't booting into Android, since it's stock, but you could try a factory reset inside TWRP. If that doesn't work, did you make a back-up you can flash or sideload in TWRP? If not, you may have to wait until someone either uploads a flashable OTA, or a custom ROM you can flash in TWRP.
Edit: If none of these methods work, you could try pushing the stock images via TWRP and then a factory reset/wipe. I'm not sure if you can do this with a locked bootloader, though. Also, if the re-locking wiped your device, you'll have lost root, which will render this option useless.

ol2 said:
Nope. "fastboot format userdata" returns:
FAILED (remote: device is locked. Cannot erase)
Click to expand...
Click to collapse
When you are in TWRP (broken, right? but will it just hang on the logo?), can you get adb to work?
Can you get adb shell to work?
If yes,
This might provide some help.
Bear in mind, those dd commands probably aren't correct for this device. I don't have an n5x yet to check...

PhoenixTank said:
When you are in TWRP (broken, right? but will it just hang on the logo?), can you get adb to work?
Can you get adb shell to work?
If yes,
This might provide some help.
Bear in mind, those dd commands probably aren't correct for this device. I don't have an n5x yet to check...
Click to expand...
Click to collapse
Awesome idea. TWRP is broken but there's a slight delay before it reboots itself. I'm trying to get the timing right to issue some adb commands before the reboot.

I made this same stupid mistake on my Nexus 6 a while back. I locked the bootloader for some reason and then ended up in the same position. Using the following commands while in the bootloader solved it for me. It took me hours to figure it out. In fact, I think Simms was the one who recommended it.
fastboot format userdata
fastboot format cache
If they are not working for you, then I wish you the best of luck. I feel your pain man.

The_Automator said:
Interesting didn't know that the developer option for oem unlocking unchecked itself when you locked the bootloader. That seems pretty dangerous
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I agree. I will have to keep it in mind and the geniuses that write guides hopefully will mention it.
Edit: Crud, that sounded sarcastic. It wasn't.

How about fastboot boot twrp-bullhead-blah.img
This will boot into twrp but not flash it. Adb will work if you can get in.
Also, try just flashing the os image file with fastboot update image-bullhead-marshmallow-delta-tango.zip (unzipb from the factory image)
The flash all command will try to flash the bootloader which is forbotten.
Make sure you are using the latest fastboot too. There are some new commands- flashboot flashing unlock blah to unlock the non-bootloader bits. I'm not sure if it will work for you, but at this point it can't hurt.
I don't think that you are locked out just yet.

Have you tried flashing factory images in fastboot?

OP3 with TWRP 3.0.2 reverts back to stock recovery on reboot

Has anyone seen the OP3 automatically revert back to stock recovery no matter how many times TWRP is successfully installed via fastboot?
At first I thought it was the "Advanced reboot" enabled causing it since when "recovery" is selected from within the OS power button menu, a "factory data reset" message appears prior to reboot....BUT I tried cycling the phone with "Advanced reboot" disabled and a clean install of TWRP working - and it still didn't stick. Regardless, whenever I enter the OS and then either turn the phone OFF or manually reboot it, the stock recovery gets automatically rewritten.
Could that annoying "device unlocked" pre-boot warning message be the cause? Do I need to relock the bootloader and/or disable "OEM unlocking"?
To confirm, I currently have the OP3 bootloader unlocked and NOT rooted (need Android Pay). The same issue occurs with the OP3 running OOS 3.1.2, 3.1.3, and 3.2.0.
I never had this issue with my OnePlus 1 so I am a little bewildered why this keeps happening.
Scott-

Which developers TWRP are you using? I had that happen, I forget which one I was on. Grarak 's TWRP works great and doesn't revert back to stock recovery.

marcjames513 said:
Which developers TWRP are you using? I had that happen, I forget which one I was on. Grarak 's TWRP works great and doesn't revert back to stock recovery.
Click to expand...
Click to collapse
Yes, TWRP by Grarak. I have not tried the "official" TWRP yet.
To confirm, all you do is:
1. Enable USB debugging, OEM unlock, and Advanced reboot...
2. Reboot in to the bootloader and decrypt user data via "fastboot format user data" (not required{??})
3. Allow the phone to wipe and re-establish itself...
4. Set the phone up again....enabling USB debugging, OEM unlock, and Advanced reboot...
5 Reboot in to the bootloader and unlock the bootloader via fastboot oem unlock...
6. Allow the phone to wipe and re-establish itself...
7. Set the phone up again....enabling USB debugging, OEM unlock, and Advanced reboot....
8. Go back in to the bootloader and Install TWRP via "fastboot flash recovery <TWRP.img>...
That is it, yes?
It seems relocking the bootloader doesn't do anything for me. Also, even though I decrypted the user data partition, it still shows the "encrypt phone" being "encrypted" within the Security & fingerprint menu. Maybe something related is blocking the recovery image from sticking past a reboot.
Thanks,
Scott-

I also had this problem with one of the other unofficial TWRPs. Grarak's TWRP worked in the end.

You need to allow TWRP to modify the system partition. If you said to leave it read-only on first boot, it will revert to stock recovery.
The problem is if you flash TWRP now, it wont give you that option again. To find it, reflash, boot into TWRP, go to Mount and change it towards the bottom where it says Mount system partition read-only.

karthikrr said:
You need to allow TWRP to modify the system partition. If you said to leave it read-only on first boot, it will revert to stock recovery.
The problem is if you flash TWRP now, it wont give you that option again. To find it, reflash, boot into TWRP, go to Mount and change it towards the bottom where it says Mount system partition read-only.
Click to expand...
Click to collapse
Still doesn't help. Keeps reverting to stock. I'm on OB35 TWRP 3.2.1. Need to flash a rom. I dont need root. Any ideas guys?

Rony John said:
Still doesn't help. Keeps reverting to stock. I'm on OB35 TWRP 3.2.1. Need to flash a rom. I dont need root. Any ideas guys?
Click to expand...
Click to collapse
Needing root and having root are two different things. Flashing Magisk immediately after flashing TWRP will solve the issue. If you don't want root at all, I don't know of any other method to solve this.

tnsmani said:
Needing root and having root are two different things. Flashing Magisk immediately after flashing TWRP will solve the issue. If you don't want root at all, I don't know of any other method to solve this.
Click to expand...
Click to collapse
Already flashed the rom and the problem is solved. Now im in search for a good rom for battery and relatively good camera. Any suggestions. RR seems to be draining so quickly. I ll just wait till 3-4 charge cycle.

Stock, Locked BL, Cannot Boot OS - Save User Files

My Android Knowledge is pretty good, however I have NEVER dealt with a stock recovery. I have a friend's 5x that will not boot into the OS, it's just bootlooping. Fixing that is not my issue, I'll deal with that easily. However, I do want to pull his photos and other user data off the emulated storage partition before wiping it to fix his boot. Is there anyway within the stock recovery or within fastboot to use adb or something else I'm unaware of to pull user files? Again, bootloader is LOCKED, so flashing a custom recovery to access adb from within recovery is not an option. I use Linux, is there a way to mount the user data partition from within the stock recovery or within fastboot so I can pull these files off the device before I reset it for him?

I never had this problem but have you tried the pull files option in NRT, it is able to do a lot of things with loked Bl, Stock Recovery?

annoyingduck said:
My Android Knowledge is pretty good, however I have NEVER dealt with a stock recovery. I have a friend's 5x that will not boot into the OS, it's just bootlooping. Fixing that is not my issue, I'll deal with that easily. However, I do want to pull his photos and other user data off the emulated storage partition before wiping it to fix his boot. Is there anyway within the stock recovery or within fastboot to use adb or something else I'm unaware of to pull user files? Again, bootloader is LOCKED, so flashing a custom recovery to access adb from within recovery is not an option. I use Linux, is there a way to mount the user data partition from within the stock recovery or within fastboot so I can pull these files off the device before I reset it for him?
Click to expand...
Click to collapse
Not easily. The userdata partition is encrypted and you have a locked phone, so essentially you would need to hack the phone.
If you had an unlocked phone, you could boot into TWRP and you know the rest.

Vulkaistos said:
I never had this problem but have you tried the pull files option in NRT, it is able to do a lot of things with loked Bl, Stock Recovery?
Click to expand...
Click to collapse
If it can't be done manually, NRT won't be able to do it either. Plus I feel that toolkits will someday become the foundation for the demise of humanity as a whole.
sfhub said:
Not easily. The userdata partition is encrypted and you have a locked phone, so essentially you would need to hack the phone.
If you had an unlocked phone, you could boot into TWRP and you know the rest.
Click to expand...
Click to collapse
That's what I'm coming up with. I'm wondering if the adb sideload option within the stock recovery will grant me access to traditional adb commands instead of it's singular purposed commands - I'll find out soon. On another note, looks like I might not even be able to flash a system image for him either. Apparently now an OEM unlock option needs to be checked off in DEV options - which will require a bootable OS. So strange. Hopefully at a minimum a recovery reset will at least get the phone booting. If not, I won't be able to even unlock his BL to flash a fresh system image without having a currently bootable OS in order to check off that OEM unlock option. By the sounds of it, current locked BL Nexus's turn a softbrick into a hardbrick with no way to recover?!? Very un-Nexus!!

annoyingduck said:
That's what I'm coming up with. I'm wondering if the adb sideload option within the stock recovery will grant me access to traditional adb commands instead of it's singular purposed commands - I'll find out soon. On another note, looks like I might not even be able to flash a system image for him either. Apparently now an OEM unlock option needs to be checked off in DEV options - which will require a bootable OS. So strange. Hopefully at a minimum a recovery reset will at least get the phone booting. If not, I won't be able to even unlock his BL to flash a fresh system image without having a currently bootable OS in order to check off that OEM unlock option. By the sounds of it, current locked BL Nexus's turn a softbrick into a hardbrick with no way to recover?!? Very un-Nexus!!
Click to expand...
Click to collapse
adb sideload doesn't have full adb access, only adb sideload.
You can flash without unlocking if you download the FULL OTA google started providing a couple of months ago. This can be flashed via adb sideload and is essentially equivalent to factory image, but flashable from stock recovery without needing to unlock bootloader. Factory reset when done and it will have same effect as flashing factory image.

sfhub said:
adb sideload doesn't have full adb access, only adb sideload.
You can flash without unlocking if you download the FULL OTA google started providing a couple of months ago. This can be flashed via adb sideload and is essentially equivalent to factory image, but flashable from stock recovery without needing to unlock bootloader. Factory reset when done and it will have same effect as flashing factory image.
Click to expand...
Click to collapse
Yeah, just tried that. Still not booting. Something's corrupted, may even be hardware related. At this point it seems only a full image flash would be the only option to get the device to even boot - which simply cannot be done due to the OEM unlock option not being enabled. Me no likely that new addition
Sent from my XT1575 using Tapatalk

annoyingduck said:
Yeah, just tried that. Still not booting. Something's corrupted, may even be hardware related. At this point it seems only a full image flash would be the only option to get the device to even boot - which simply cannot be done due to the OEM unlock option not being enabled. Me no likely that new addition
Click to expand...
Click to collapse
The FULL OTA *is* a full image flash.
Did you factory reset?

The image flash fails, then reads succeeded. Still will not boot past the splash screen. Hangs, then goes black. I don't think the OTA zips flash all partitions like the factory image does.
Sent from my XT1575 using Tapatalk

annoyingduck said:
The image flash fails, then reads succeeded. Still will not boot past the splash screen. Hangs, then goes black. I don't think the OTA zips flash all partitions like the factory image does.
Click to expand...
Click to collapse
Guarantee they (the FULL OTA from factory image site) do. Open up the zip file. They even flash in more granular detail than the factory image. The only thing it doesn't do is wipe user/cache, which can be performed by factory reset.
I don't know what it means for the image flash to fail then read succeeded.

sfhub said:
Guarantee they (the FULL OTA from factory image site) do. Open up the zip file. They even flash in more granular detail than the factory image. The only thing it doesn't do is wipe user/cache, which can be performed by factory reset.
I don't know what it means for the image flash to fail then read succeeded.
Click to expand...
Click to collapse
Neither do I, it's a first.
Sent from my XT1575 using Tapatalk

annoyingduck said:
Neither do I, it's a first.
Click to expand...
Click to collapse
Sorry, I should be more clear, could you list what it says.
It sounds like the flash script is not checking for errors at the end so there is some error flashing within one of the partitions, but the overall script is saying everything good.