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:

Re-Locked Bootloader (i think?)

Today i did something very silly and used the Asus Flash tool to flash what i thought was the correct raw image for my ZE551ML (to try and re-lock the bootloader), it turned out that I in fact flashed the ZE550ML raw file by mistake !!! Upside is that the only difference i saw was the change in screen resolution and no harm seems to have been done to my phone.
I have now found a ZE551ML raw file and flashed that to my device and it seems to have worked and re-locked the bootloader.
The boot screen is now black again, but is there any other way to test or find out if it is indeed re-locked?

Try to flash TWRP

Kona67 said:
Try to flash TWRP
Click to expand...
Click to collapse
Installed temporarily, should i get an error or should it refuse to flash?

shake1963 said:
Installed temporarily, should i get an error or should it refuse to flash?
Click to expand...
Click to collapse
any custom recovery can not be flashed if bootloader is lock.
recovery was installed means bootloader is unlocked.

rajlko said:
any custom recovery can not be flashed if bootloader is lock.
recovery was installed means bootloader is unlocked.
Click to expand...
Click to collapse
But he said it was temporary... I assume he means it went back to stock after the second reboot?

azthemansays said:
But he said it was temporary... I assume he means it went back to stock after the second reboot?
Click to expand...
Click to collapse
Yes, back to stock after second boot...

rajlko said:
any custom recovery can not be flashed if bootloader is lock.
Click to expand...
Click to collapse
You can run a tethered TWRP without unlocking.
shake1963 said:
Yes, back to stock after second boot...
Click to expand...
Click to collapse
That was likely the "tethered" recovery then. Try the untethered, but of course skip the part where you unlock the bootloader. In short:
reboot into bootloader
fastboot flash recovery twrp.img
reboot into recovery (press volume down twice until "Reboot recovery" shows up, then press power button)
If that boots into TWRP I suppose the bootloader is still unlocked. It may not be the easiest, but it should give you an answer.

wutr said:
You can run a tethered TWRP without unlocking.
That was likely the "tethered" recovery then. Try the untethered, but of course skip the part where you unlock the bootloader. In short:
reboot into bootloader
fastboot flash recovery twrp.img
reboot into recovery (press volume down twice until "Reboot recovery" shows up, then press power button)
If that boots into TWRP I suppose the bootloader is still unlocked. It may not be the easiest, but it should give you an answer.
Click to expand...
Click to collapse
Seems bootloader is still unlocked.... TWRP untethered stuck so back to the drawing board lol..
I would love to know what the process for unlocking does when the terminal commands are processed. I have a spare ZF2 with a broken screen that I can experiment with so no great loss if I trash it...
Any recommendations for reading... or do I need to maybe learn a bit of code?
I saw a method on here somewhere where a couple of files are flashed from the ifwi.zip file found in stock rom (I think that is a method used in another zenfone variant .... The 5 or 4.) which re locks the bootloader.
Doesn't work on the ZF2 though....

Can't boot into recovery or into android

Hi I just locked my 1+3 after flashing with a rom, but now I can't access the recovery and when trying to boot into android it asks me for a pattern but doesn't recognise it, can anybody please help? many thanks

Can you long press power button from pattern screen to get reboot options? Then reboot to recovery?
Sent from my SM-G930F using XDA-Developers mobile app

booloader locked, pattern bug and no recovery access
Hi!
I just got myself into big trouble. As I wanted to use my 1+3 for work, I wanted to bring it into its original status. Coming from Ressurection Rom, I wiped it, and intalled the original rom from the oneplus website.
With that it also got unrooted. Then I wiped it completely (no backups etc.), but decided to stay with twrp as I thought IT of my company won´t recognise it. But then I had to relock the bootloader. so I used the Oneplus3&3T Toolkit v4.7U and locked the bootloader.
So and now I am stuck here, as it seems I got this bug that my pattern for unlock doesnt work anymore AND the device cannot boot into recovery.
Bootloader is stated as locked.
Please, can anyone help me with this?
Many thanks in advance!

Use the toolkit to try to go into TWRP recovery and if that doesn't work then flash it with the toolkit otherwise flash stock recovery

My OP3 is Dead! Any help is appreciated!

Long story short, I made my phone bricked with a small mistake:
I had Freedom OS (latest build) and then tried to flash Miui rom. To do so, I needed to flash back to official Hygrogen/Oxygen OS (MM). The mistake I made was to lock bootloader first. Then, phone got into bootloop....I searched and found Qualcomm software can revive any Qualcomm phone. I downloaded Qualcomm app and driver for Oneplus 3 and tried reviving my phone....What happened finally was that the phone was restarted and a screen showing Cache failed, System failed, userdata failed appeared. I tried to find Cache, system img ...of OOS 4.02 to flash separately....while I couldn't find them anywhere...I just tried fastboot flashing a recovery (both official and TWRP) but got error that partition doesn't allow writing (I guess because phone is locked now)....anyway, phone can boot only in fastboot and I wonder what else I can do....
Any help is very much appreciated!

alireza.nasibi said:
Long story short, I made my phone bricked with a small mistake:
I had Freedom OS (latest build) and then tried to flash Miui rom. To do so, I needed to flash back to official Hygrogen/Oxygen OS (MM). The mistake I made was to lock bootloader first. Then, phone got into bootloop....I searched and found Qualcomm software can revive any Qualcomm phone. I downloaded Qualcomm app and driver for Oneplus 3 and tried reviving my phone....What happened finally was that the phone was restarted and a screen showing Cache failed, System failed, userdata failed appeared. I tried to find Cache, system img ...of OOS 4.02 to flash separately....while I couldn't find them anywhere...I just tried fastboot flashing a recovery (both official and TWRP) but got error that partition doesn't allow writing (I guess because phone is locked now)....anyway, phone can boot only in fastboot and I wonder what else I can do....
Any help is very much appreciated!
Click to expand...
Click to collapse
Try this method now it will work
https://forum.xda-developers.com/showpost.php?p=68245482&postcount=111

The point is I can't flash anything on any partition as phone is locked and can't be unlocked!

alireza.nasibi said:
The point is I can't flash anything on any partition as phone is locked and can't be unlocked!
Click to expand...
Click to collapse
If you can access fastboot mode then you can definitely flash by other method

abhi0502 said:
If you can access fastboot mode then you can definitely flash by other method
Click to expand...
Click to collapse
you mean the 2nd method?

You said you lock the bootloader in 5th line, in order to flash any recovery you need to unlock bootloader again.
I also tried to lock bootloader last week and then my op3 got bricked with bootloop.
-First get into fastboot and unlock bootloader this will wipe your all data including you saved ROM files.
- after this flash TWRP or OnePlus recovery and sideload OOS ROM. Or transfer the ROM file using mtp in TWRP recovery.
- then you can easily do anything you want. Don't relock bootloader.

Those red things on your screen basically means your phone misses partitions, without these partitions it doesn't boot duhh.
If method 2 of the unbrick tool doesn't work, you can manually flash those files in Fastboot, the program has a folder that has all partitions like, cache.img, boot.img etc. I've been here as well nothing to worry about just keep us updated so we can help you

There's no mention in your post on which unbrick method you used. Was it first or second? By the looks of the end result, it was the first.
Just follow the same steps, but use method 2, that should leave you with a phone like out of the factory. Afterwards, you can simply set it up and let it update through OTA if you want to remain stock, or simply unlock bootloader, flash TWRP and flash whatever you want.

use the second method. the file you have to download contains all the raw room and when you follow the process, it would work. happened to me two times and i used this method

Just simply use fastboot oem unlock in fastboot mode then flash a recovery via fastboot flash recovery then go to recovery and once wipe all the partions and install a rom and then tried booting

Thank you all for your time and support. Method 2 saved my phone!

Bootloader - No Command Error [solved]

Here are the steps that got me to where I am.
1. Stock Pixel XL March 2017
2. Installed TWRP
3. Installed SU
4. All worked correctly for the last month
5. Saw that there was a new April release
a. It would not install as I was rooted
b. I installed the April OTA using TWRP
c. Rebooted
6. Saw that I was no longer rooted
7. Tried to go to Bootloader
8. Got dead droid with no command error
9. Went to recovery (Power + up vol) to enter sideload
10. Sideloaded the April updated
11. Rebooted
a. Same no command error
b. Went to recovery (Power + up vol) to enter factory restore
c. Rebooted
12. Tried to go into boot loader
a. Same no command error
13. Problem is that twrp was not asking for pattern And would not install correctly with image file. Solution was to keep loading the twrp image file until it asks for pattern. Then follow standard twrp /su instructions.
Thanks.

Power device off, use key combo (power+voldown) to boot bootloader. Fastboot flash stock boot.img to both slot a and b. Then reboot, take the OTA, or sideload it. Reboot. Now reboot to bootloader, fastboot boot TWRP, then reboot to twrp. Now you can flash TWRP to keep it as the recovery, or just su then reboot. Should be good.
Sent from my Pixel XL using Tapatalk

This should be posted under Q&A not development

wyrdtrtle said:
Power device off, use key combo (power+voldown) to boot bootloader. Fastboot flash stock boot.img to both slot a and b. Then reboot, take the OTA, or sideload it. Reboot. Now reboot to bootloader, fastboot boot TWRP, then reboot to twrp. Now you can flash TWRP to keep it as the recovery, or just su then reboot. Should be good.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Bootloader does not load.

When you get the dead Droid just hit vol up, no power button.
Sent from my Pixel XL using Tapatalk

Then what?

bschatzow said:
Then what?
Click to expand...
Click to collapse
I think I know where you went wrong you installed an incremental OTA with TW RP. If I'm not mistaken that new firmware had an updated bootloader and I believe that's dangerous to do. You may be out of luck

Why would the built in factory restore fix it?

bschatzow said:
Why would the built in factory restore fix it?
Click to expand...
Click to collapse
Can you get into fastboot?

So no bootloader.
Just my thoughts. I don't know if that's even possible.
Isn't it possible to edit the ota script to flash a bootloader?
Or even make a full factory update like this?

To use fastboot you need to be in bootloader mode.

mikaole said:
So no bootloader.
Just my thoughts. I don't know if that's even possible.
Isn't it possible to edit the ota script to flash a bootloader?
Or even make a full factory update like this?
Click to expand...
Click to collapse
If it is, I don't know how. I would need it to be able to load from Sideload.

Does phone boot at all? To OS?

Yes it does. Only thing not working is bootloader. Without out this I can't root.

bschatzow said:
Yes it does. Only thing not working is bootloader. Without out this I can't root.
Click to expand...
Click to collapse
Ok..if phone boots ur bootloader is still there. Phone wouldnt boot without it. You on stock rom? Hit me up on hangouts and I will try to help you if you want. For the sake of time. Im sure you wanna get this resolved ASAP.

Sent you a pm requesting contact info.

Moderator Close
Worked for a long time with BDogg718. He generously spent a great deal of his time with me and opened several Chats with Developers and No one had a solution. He is very knowledgeable and really did not want to give up. For now the solutions seems to be send it back to Google and get a replacement. It would be nice if someone could talk to Google, as a phone that has a recovery built in firmware should be able to restore itself. The dual slots seems to be a problem for them as well.

I think I had the same thing happen with me! I installed the update via TWRP. The update installation seemed to crash at the end, resulting in a reboot. The phone did install 7.1.2 successfully, but I lost root and the ability to successfully boot into any recovery. I tried flashing TWRP again, but it failed "FAILED (remote: partition recovery doesn't exist). It appeared to attempt to flash it into slot "_b", if that means anything.

TWRP will not boot on 7.1.2. At least that's the conclusion formed last night in #twrp while the devs were working with someone else with this issue. I don't think they know why yet, but I doubt it will be overly long til they figure it out.
Sent from my Pixel XL using Tapatalk

Glad to hear someone is on the case. I will be sure to send a few shekels their way for my clumsiness.