Related
Due to a bug, I have been able to get root on my OnePlus 2 running Oxygen 2.1.1 without a wipe.
DISCLAIMER: This may not give you root on yours, and obviously it may also loose you data, so don't do it unless you know you can cope with that. YMMV, but I've documented here for posterity how to do it!
I had unlocked the bootloader previously, because my device is an import, so it is possible, though unlikely that it simply doesn't wipe on an unlock after re-lock (OTA locks bootloader).
The basic steps are :
Encrypt your device
Unlock the bootloader (this won't wipe because of encryption!)
Boot TWRP
use adb to push SuperSu to your device and then flash it
Then you will have root. Step by step instructions below.
Note that TWRP currently doesn't support encryption on our devices, so you'll have to use something other than that to back up your data if you want to use a custom rom. This simply gives you rooted stock Oxygen.
After rooting :
Code:
$ adb shell
[email protected]:/ $ su
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
Step 1: Encrypt your device.
This is irritating but fairly simple. You have to have fully charged your device AND keep it plugged in, and it takes ~50 minutes to complete. It's the standard android encryption, so follow any guide for this, such as https://support.google.com/nexus/answer/2844831?hl=en-GB
Step 2: Unlock the bootloader.
Again, this is well documented - here's a guide : http://forum.xda-developers.com/oneplus-2/general/guides-how-to-guides-beginners-t3146568 - The important thing is that if you're encrypted, this does not do a wipe, in my experience.
Step 3: Boot TWRP
Download TWRP from https://dl.twrp.me/oneplus2/ and save it somewhere you can find it later - I'm going to assume you're on linux and have saved it in ~/Downloads/TWRP.img
Reboot into bootloader mode (Power and Volume up) and start TWRP by issuing the following command (substituting your path to twrp) :
Code:
~$ fastboot boot Downloads/twrp-2.8.7.0-oneplus2.img
Step 4: Root it!
This is a bit tricky because once you're encrypted you can't access the SDCard, so you need a bit of magic to flash the zip.
First, do the swipe to enable modifications, then in mount, tick the /system option.
Then, on your PC, download SuperSU's .zip update from https://download.chainfire.eu/696/supersu/ (similar to above, assuming same download location) and use adb push to put it on the device in /tmp :
Code:
adb push Downloads/UPDATE-SuperSU-v2.46.zip /tmp/su.zip
Next, from the main TWRP menu, select Install. Navigate up (you start in sdcard that is empty) and into tmp, then select the su.zip file in there.
Swipe to install the zip - TWRP will complain because it can't access /data, but handily, /data is not needed to root!
Select Reboot, and viola, you have SuperSU and root! Now you can install Titanium Backup and back up your device.
Cool, perhaps renaming the title like "Unlock and root without wiping" could make more sense?
ranyardm said:
I had unlocked the bootloader previously, because my device is an import, so it is possible, though unlikely that it simply doesn't wipe on an unlock after re-lock (OTA locks bootloader).
Click to expand...
Click to collapse
OTAs don't re-lock the bootloader though...
If you've unlocked it previously, it'll stay unlocked unless you boot into fastboot mode and do a "fastboot oem lock".
Spannaa said:
OTAs don't re-lock the bootloader though...
If you've unlocked it previously, it'll stay unlocked unless you boot into fastboot mode and do a "fastboot oem lock".
Click to expand...
Click to collapse
Not true I'm afraid. The OP2 OTA to 2.1.0 did indeed relock the bootloader. I know this because I would never want to lock the bootloader, and I'm on a Chinese OP2 which came with masses of spyware, so to install clean 2.0.1 I had to unlock the bootloader originally (they managed to get the spyware into the recovery image!). Anyway, it's irrelevant to this thread how the bootloader got relocked, I just documented this fiddly way of getting an unlocked bootloader with root on a locked OP2.
ranyardm said:
Not true I'm afraid. The OP2 OTA to 2.1.0 did indeed relock the bootloader. I know this because I would never want to lock the bootloader, and I'm on a Chinese OP2 which came with masses of spyware, so to install clean 2.0.1 I had to unlock the bootloader originally (they managed to get the spyware into the recovery image!). Anyway, it's irrelevant to this thread how the bootloader got relocked, I just documented this fiddly way of getting an unlocked bootloader with root on a locked OP2.
Click to expand...
Click to collapse
Maybe my post should have said "OTAs don't re-lock the bootloader since 2.1.0"
Anyway, if your method works then great :good:
There's another way to do it here.
Can everyone who's done this attest that the data indeed doesn't get wiped?
cheekrox said:
Can everyone who's done this attest that the data indeed doesn't get wiped?
Click to expand...
Click to collapse
I'd also be very happy to have this confirmed by another party!
Confirmed. Data does NOT get wiped.
cheekrox said:
Confirmed. Data does NOT get wiped.
Click to expand...
Click to collapse
Confirmed on 2.2.0 or still on 2.1.X?
Can confirm, this still works on 2.2.0.
i didnt try this tutorial, but when i rooted my phone, my data didnt got wiped either.
will root on 6p running android n dev preview wipe phone?
Any chance this works also on 1+1? I'm desperate for a way to root without unlocking so I can install titanium/nandroid and do a full proper backup before wiping clean (battery life is utter crap). Running latest stock 6.01 COS. Never unlocked, never wiped since 15R.
Thanks!
anyone tried this on OOS 3 ?
Yeah, bump!
Now my OP2 is on Oxygen 3.0.2, and Android 6.0.1 - stock.
My phone had always been (bootloader) unlocked and rooted, since the day after I got it.
But to get the new OTA update to Oxygen 3, I tried a different method this time, where some people said you can do a temporary un-root, get the stock OTA update, and then re-root.
I followed their instructions, but I can't re-root as simple and easy as they said.
Before the process, I didn't do a nandroid backup because my sdcard doesn't have room :-|
So now I need to re-root without losing data.
And I've tried helium before, many times, and it never works for me.
Any other ideas, or has anyone tried this encryption trick yet with Oxygen 3?
Thanks!
tried it on oos 3.1:
everything worked until a bootloop at the last restart.
also twrp asked me to unlock the phone, i did that.
what to do now?
Did anyone ever have any success with this approach on 3.1?
LoL How do you boot/flash TWRP on locked bootloader?
aIecxs said:
LoL How do you boot/flash TWRP on locked bootloader?
Click to expand...
Click to collapse
Lol, you can't.
Hi!
Today I tried for a few hours the official bootloader unlock method and I never succeded, or so it seems???
I always got stuck at 50% and never reached 100%.... But once I was in fastboot after trying for a few hours I could see that the bootloader was unlocked by typing
fastboot oem device-info
So can I in some way see if the device is unlocked by the official method, or that I actually got it unofficial unlocked from the seller (geekbuying).
More than likely it is unofficial unlocked by your seller.
Check you MIUI Version: - Settings - About Phone - MIUI Version
Report what you find there, you may also have a vendor rom!
corkiejp said:
More than likely it is unofficial unlocked by your seller.
Check you MIUI Version: - Settings - About Phone - MIUI Version
Report what you find there, you may also have a vendor rom!
Click to expand...
Click to collapse
MIUI Global 8.0 Stable 8.0.1.0.0 (LHOCNDG)
Are you sure? Cause it might have still "worked" while I was testing... If it helps to answer the question MI Unlock says "Couldn't verify device - No need to unlock this device"
katolo said:
MIUI Global 8.0 Stable 8.0.1.0.0 (LHOCNDG)
Are you sure? Cause it might have still "worked" while I was testing... If it helps to answer the question MI Unlock says "Couldn't verify device - No need to unlock this device"
Click to expand...
Click to collapse
It is a Vendor Rom!
Official roms come with four numbers (x.x.x.x)!
And since you can only unlock the bootloader on official roms. It has definitely been unlocked by the unofficial method.
Vendor roms may come with spyware/adware, so I would advise you to flash an official rom as soon as possible.
As your unlocked unofficially take care how you flash roms.
If you flash the latest Marshmallow roms, your bootloader may be locked again.
See the linked wiki above and read some of the threads here.
corkiejp said:
It is a Vendor Rom!
Official roms come with four numbers (x.x.x.x)!
And since you can only unlock the bootloader on official roms. It has definitely been unlocked by the unofficial method.
Vendor roms may come with spyware/adware, so I would advise you to flash an official rom as soon as possible.
As your unlocked unofficially take care how you flash roms.
If you flash the latest Marshmallow roms, your bootloader may be locked again.
See the linked wiki above and read some of the threads here.
Click to expand...
Click to collapse
Ok. Thanks.. But what would you recommend? I want to unlock the offical way. So should I flash the Marshmallow rom and let it lock and I unlock via the official?
@katolo That is a good question, which I don't have an answer for.
It may work, but also you may end up with a device you can not unlock officially.
See here :- https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
And this thread: - http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Flash Alka TWRP and make backup of all partitions first.
corkiejp said:
@katolo That is a good question, which I don't have an answer for.
It may work, but also you may end up with a device you can not unlock officially.
See here :- https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
And this thread: - http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Flash Alka TWRP and make backup of all partitions first.
Click to expand...
Click to collapse
Just for info for other people... I just flashed the MIUI Global DEV ROM and went into fastboot and checked the bootloader and now it is LOCKED again.
Now I will try to unlock it officially. Crappy geekbuying putting ****ty ROM on phone..
Thanks for the help.
katolo said:
Hi!
Today I tried for a few hours the official bootloader unlock method and I never succeded, or so it seems???
I always got stuck at 50% and never reached 100%.... But once I was in fastboot after trying for a few hours I could see that the bootloader was unlocked by typing
fastboot oem device-info
So can I in some way see if the device is unlocked by the official method, or that I actually got it unofficial unlocked from the seller (geekbuying).
Click to expand...
Click to collapse
corkiejp said:
@katolo That is a good question, which I don't have an answer for.
It may work, but also you may end up with a device you can not unlock officially.
See here :- https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
And this thread: - http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
Flash Alka TWRP and make backup of all partitions first.
Click to expand...
Click to collapse
Just got to be a bit careful here. I'd recommend flashing "Safe TWRP" recovery once you have backed up all your partitions with alka TWRP.
@katolo Report back if you can successfully unlock by the official method.
Plenty of threads here on the steps required to do so.
corkiejp said:
@katolo Report back if you can successfully unlock by the official method.
Plenty of threads here on the steps required to do so.
Click to expand...
Click to collapse
Worked perfectly. Thanks for the help.
I'm on MM MIUI now... Will flash ALKA TWRP > FULL BACKUP > CM13 (goodix) then I'm set...
Jeanz Sensation said:
Just got to be a bit careful here. I'd recommend flashing "Safe TWRP" recovery once you have backed up all your partitions with alka TWRP.
Click to expand...
Click to collapse
Can I use Safe TWRP to flash CM13/CM14 and MIUI roms?
What is the difference between ALKA and SAFE TWRP?
katolo said:
Can I use Safe TWRP to flash CM13/CM14 and MIUI roms?
What is the difference between ALKA and SAFE TWRP?
Click to expand...
Click to collapse
If your bootloader is unlocked officially then you can use either of the recoveries. But if the bootloader has been unlocked unofficially then strictly use SAFE TWRP if you are flashing MIUI ROM.
The main difference between SAFE and Alka is that Alka gives you the option to backup few more partitions within the phone's memory as compared to SAFE. Bear in mind that these extra partitions may not be necessary for you to backup, hence eliminating the need for Alka recovery at all.
Jeanz Sensation said:
If your bootloader is unlocked officially then you can use either of the recoveries. But if the bootloader has been unlocked unofficially then strictly use SAFE TWRP if you are flashing MIUI ROM.
The main difference between SAFE and Alka is that Alka gives you the option to backup few more partitions within the phone's memory as compared to SAFE. Bear in mind that these extra partitions may not be necessary for you to backup, hence eliminating the need for Alka recovery at all.
Click to expand...
Click to collapse
Ok. Thanks.
I was unofficially unlocked. But after I flashed MIUI via edl method it got locked again. So then I officially unlocked it.
I guess I can keep alka then. Or?
Sent from my Redmi Note 2 using XDA-Developers mobile app
Cleaning this up and clarifying as my original post was vague:
It is recommended that you unlock your bootloader before the 7.0 Nougat update. Although it will still be possible the process will be more difficult and risky afterwards.as you will need to use one of the edl mode tools (axon7backup, axom7tool).
The easiest way is to download this kit f you have the A2017U: (I can't speak to other models) (This kit and instructions are thanks to @jcadduono)
https://build.nethunter.com/misc/axon7/AXON7-A2017U-BL-UNLOCK-KIT.zip
https://build.nethunter.com/misc/axon7/INSTRUCTIONS.txt
The basic steps, which the above zip with take you through in detail are:
1. Flash Official B20 , enable OEM UNLOCKING after flashing.
2. Flash BLFastboot zip provided by ZTE when they had unlock method.
3. Enable OEM UNLOCKING in Developers Option
4. Boot to Bootloader
5. type : fastboot oem unlock
6. Done
Note: If you do not have the OEM UNLOCKING flag set in developer options you will get a soft brick. Also bear in mid this will wipe data.
All that being said I've heard Nougat to is going to be great from those in the know. In their words ”Well worth the wait! Hang in there!” from a HIGHLY credible source.
Why would anyone relock before update? I do agree anyone who wants to unlock should do it now.
lokissmile said:
For anyone looking to bootloader unlock, I've heard that the methods might change when the N update rolls out. It's a major update and although I personally don't have N and can't get a direct answer because those who know for sure are under NDA. I can tell you that the advice given to me is to not re-lock. So if you are thinking of unlocking your bootloader I'd do it soon while the methods are stable. Google confirmed that daydream is certified in an upcoming update so the daydream version of the stock ROM has been through googles QA. Might as well get ready now, we will probably have another surge of custom ROMS shortly after. I'm just sharing what I think is a best practice.
Click to expand...
Click to collapse
OK, so just to make it quick, for everyone, unlock your bootloader sooner than later. It is safe since you can revert it to a locked state at any time later.
lafester said:
Why would anyone relock before update? I do agree anyone who wants to unlock should do it now.
Click to expand...
Click to collapse
I do it on occasion to test things I'm working on. Better to warn people who might do it to get PoGo or SafetyNet working I figured.
lokissmile said:
I do it on occasion to test things I'm working on. Better to warn people who might do it to get PoGo or SafetyNet working I figured.
Click to expand...
Click to collapse
No need to bootloader lock an Axon 7 to get SafetyNet (Android Pay, PoGo, etc). Just do it the XDA way. But never relock!!!!
Could one of you guys explain whats so dangerous about relocking bootloader since u seem to know something I don't.
I have unlocked and relocked my bootloader several times by fastboot oem lock and restoring my stock fbop partition.
Have I done something wrong?
Regards,
mischa_martin
mischa_martin said:
Could one of you guys explain whats so dangerous about relocking bootloader since u seem to know something I don't.
I have unlocked and relocked my bootloader several times by fastboot oem lock and restoring my stock fbop partition.
Have I done something wrong? [emoji14]
Regards,
mischa_martin
Click to expand...
Click to collapse
Read the OP.
I think what the op is trying to say is that by unlocking the bootloader you won't get ota updates. You would need to wait until a twrp flashable update is out or a rom running Android 7.
stevecaboose said:
I think what the op is trying to say is that by unlocking the bootloader you won't get ota updates. You would need to wait until a twrp flashable update is out or a rom running Android 7.
Click to expand...
Click to collapse
That's how it's been since modifying the bootloader was a thing. Unlocked bootloader = no OTA.
tzbigworm said:
That's how it's been since modifying the bootloader was a thing. Unlocked bootloader = no OTA.
Click to expand...
Click to collapse
@stevecaboose
Unlocking Bootloader = Yes to OTA's.
Modding System and Boot = NO OTA's
hope that clear things up.
Close enough lol!
To be clear, it would be best to unlock before N is pushed out. I have it on good authority that unlocking your bootloader after you update to N will be more difficult and risky. Relocking would put you in the same situation. It's trivial to return to stock system+boot with an unlocked bootloader and TWRP and then the OTA will come through just fine. Or you can just wait for the TWRP flashable N stock ROM.
So to be clear, since I'm not 100% sure what affects the "system" and "boot" areas: I can unlock my BL using only guide 2 in this link ( https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ) and still get OTAs? If I install TWRP does that make me OTA-ineligible?
ScaryBugThing said:
So to be clear, since I'm not 100% sure what affects the "system" and "boot" areas: I can unlock my BL using only guide 2 in this link ( https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 ) and still get OTAs? If I install TWRP does that make me OTA-ineligible?
Click to expand...
Click to collapse
TWRP/BL unlock doesn't affect OTA, ROOT does.
raystef66 said:
TWRP/BL unlock doesn't affect OTA, ROOT does.
Click to expand...
Click to collapse
You're totally wrong there,
TWRP will affect OTA's if the OTA need to check/patch recovery, BUT been Bootloader Unlock will NOT effect OTA.
To manage a clean/successful OTA's installation, you need to be FULL STOCK. (System, boot, Recovery, aboot if the OTA need to patched).
I think the OP was trying to say that it's possible current tools will not work to unlock the bootloader after the 7.x ota is installed.
DrakenFX said:
You're totally wrong there,
TWRP will affect OTA's if the OTA need to check/patch recovery, BUT been Bootloader Unlock will NOT effect OTA.
To manage a clean/successful OTA's installation, you need to be FULL STOCK. (System, boot, Recovery, aboot if the OTA need to patched).
Click to expand...
Click to collapse
I'm not fully agreed with that. You can install OTA's when you receive it, download it, install it when first booted into twrp cache. Only if you're not rooted. When you're rooted first unroot and in principle this should work.
There are several cases on internet about that. Even I did it with an unrooted but TWRP-ed Zopo C2. Received an OTA and installed it.
Im always glad to learn but IMO there are some possibilities to do the ota after all. But I am willing to accept it's a general fact that twrp could affect the normal OTA.
Edit : let's wait and see when B10 is rolling out and if I get a notification about that and if I can install it as a normal OTA(not with SD) with TWRP. Keep you updated:cyclops:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
eladmitz said:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
Click to expand...
Click to collapse
I`m on the same boat. What should be the safer procedure to unlock BL an still get the N OTA?
eladmitz said:
Noob here, forgive me ...
So what is the best way to only unlock bootloader without flash twrp?
A2017U, B29.
Thanks
Click to expand...
Click to collapse
felipe.vella said:
I`m on the same boat. What should be the safer procedure to unlock BL an still get the N OTA?
Click to expand...
Click to collapse
1- Download Official B20 from ZTE SITE (look Software Updates for the 6gb variant)
2- look in the forum for the B20fastboot zip file
3- Move both files to your SDCARD.
4- Enable OEM Unlocking under Developers Option
5- boot to stock recovery.
6- Install B20 official update via SDCARD (this will wipe Data)
7- boot and re-enable OEM Unlocking
8- boot to recovery and install B20fastboot zip
9- boot to Bootloader and Unlock bootloader using this command.
Code:
fastboot oem unlock
If I remember correctly will reboot and factory reset the device , you'll need to re-enable OEM UNLOCKING and boot to Bootloader to flash TWRP 3.0.3 USING fastboot commands
I see tons of people complaining that the Mi Unlock fails at 50%. I had that too, but solved it (somewhat) after downloading and using a newer version of the Mi Unlock (version 2.3).
Although I get past the 50% mark, the Mi Unlock program fails after verifying phone. [I tried to put a picture of the result below but XDA bars me from this practice until after I have submitted 10 posts.] Since XDA bans me from posting a picture of the result, I will try to verbally illustrate:
The Mi Unlock process runs the entire course - 100% - and then gives me green check mark and says, "Verified". The next step the Mi Unlock program takes is to unlock the bootloader. However it is at this step the process fails. Instead of unlocking, I get a message saying "Couldn't Unlock." Under those words is the following message, "After 72 hours of trying to unlock this device".
Anyone even know what that is supposed to mean? Is that just chinglish? Or better still, how can I get my device unlocked?
I SEE TONS OF PEOPLE WITH THIS SAME PROBLEM! Anyone have any idea what is going wrong? How do I deal with it? Am I to assume the message is suggesting we wait that particular number of hours before we can make the thing unlock the bootloader? Anyone? This IS a question that plagues many in the MIUI forum! And after going back roughly 70 pages into the forum, I see no solution; no answers! Just the same complaint over and over again and again.
I tried the unlocker a few times afterward, over the course of the day, with the same result. However curiously, there is one change to the message. It now says, "After 63 hours of trying to unlock this device". Is this suggesting I have to wait and try it in 63 hours?
Again, I see this same complaint time and time again on the MIUI forum for this phone. Anyone have any idea how to handle this dilemma?
One last question: How do I change out my MIUI ROM (currently MIUI 8.6.8.18 Beta) to a developer ROM? Ultimately I want to install a custom RR Rom or some other custom ROM. But MIUI 8.6.8.18 is android 5.0 LL; and the new Custom ROMs available are using android 7.0. My understanding is I need at least an MIUI Dev Rom with android 6.0 MM on the phone before it will let me leap over to some other Custom ROM with android 7.0. [I tried it. And though everything worked perfectly, (got my device rooted, and installed ZCX TWRP, etc.), it just bootlooped after flashing in TWRP. I tried it with several Custom ROMs - Always with the same bootloop. After exhaustive reading in web forums, the suggestion out there seems to be that I have to go back and install a DEV Rom with android 6.0 MM; then free the bootloader again, reinstall SuperSU (or similar), and then TWRP, etc. , and finally I will be able to Flash to one of the new Custom Rom's that uses Android 7.0.]
With this objective in mind, I downloaded the Dev Rom to my phone (7.7.20 - which is the latest for this phone). However, the UPDATER app on the phone won't update from the MIUI 8.6.8.18 Beta to the MIUI 7.7.20 Global Dev Rom. I select it in the updater by browsing over to it, then click "OK", but nothing happens. Instead of installing the MIUI 7.7 Dev Rom, the app just says that there are no updates...
Any ideas? Thanks
Unlock fails
Hi,
did you find a solution to your unlock problem. I have exactly the same problem and found only lots of solution for other problem with unlock.
Oliver
Now the process of unlocking bootloader is quick.
I deleted my MI account & created a new one. So, applied for permissions again & unlocked in 5 mins after approval.
VaibhavKumar07 said:
Now the process of unlocking bootloader is quick.
I deleted my MI account & created a new one. So, applied for permissions again & unlocked in 5 mins after approval.
Click to expand...
Click to collapse
Please can you provide the exact steps you have taken?
IMHO this would help users like me who did follow the instructions to unlock the bootloader and run into this problem.
I did run into the problem, "After 72 hours of trying to unlock this device", even that I followed the instructions:
Create a Mi acoount (with my phone nr.)
Apply for unlocking, with giving reason
wait for confirmation sms
download unlocking tool
on the phone: activate dev options, switch on usb debugging, OEM unlocking and bind phone to Mi account in "Mi Unlock Status"
reboot phone in fastboot mode
run Mi Unlock prog on PC and log in
when prompted connect phone
The Mi unlocking tool stopped after verifying (green hock) at "Unlocking" with a red cross and show then "After 72 hours of trying to unlock this device".
I do not see where I went wrong...
IMHO this is a f***ed up process of unlocking the bootloader and Xiaomi should work on this.
I haven't read the post, but you don't need to unlock bootloader to root or flash custom roms
asakurato said:
I haven't read the post, but you don't need to unlock bootloader to root or flash custom roms
Click to expand...
Click to collapse
Hi,
As far as I know unfortunately if you want to install a custom rom you need to replace the Xiaomi recovery with a custom one, like twrp. In order to do that you need to unlock the bootloader first. Then you can flash the custom recovery with the command "fastboot flash recovery twrp-x.x.x-x-mido.img" for the Redmi Note 4 SD for example.
tinaeire said:
Hi,
As far as I know unfortunately if you want to install a custom rom you need to replace the Xiaomi recovery with a custom one, like twrp. In order to do that you need to unlock the bootloader first. Then you can flash the custom recovery with the command "fastboot flash recovery twrp-x.x.x-x-mido.img" for the Redmi Note 4 SD for example.
Click to expand...
Click to collapse
I haven't unlocked bootloader, have custom recovery (Red Wolf) and Android 8.1 installed (Nitrogen OS). Can show screenshot from cmd that bootloader is locked.
asakurato said:
I haven't unlocked bootloader, have custom recovery (Red Wolf) and Android 8.1 installed (Nitrogen OS). Can show screenshot from cmd that bootloader is locked.
Click to expand...
Click to collapse
how? Any link to steps? I have currently resurrection remix 5.7.4 with OFFICIALLY unlocked bootloader, but it's useless because all new ROMs require new firmware and I don't have anymore access to my Xiaomi account which had granted bootloader permission, would like to move from marshmallow to Oreo, but that would require flashing me MIUI, relock bootloader and I will get stuck there and don't wanna apply anymore for official unlock, it's PITA
Forget all of this follow https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
And Apply ur brains, it will work as smooth as it needs to be.
evansourav said:
Forget all of this follow https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
And Apply ur brains, it will work as smooth as it needs to be.
Click to expand...
Click to collapse
Yeah, this one. Tbh, this needs to be pinned, it's often buried under other posts so people don't know how to do it.
Hi, have been reading posts here, but I'm trying to get a grasp on all involved to root my phone. I am pc literate but this is all new.
One site I got instructions on, https://www.thenextdroid.com/root-motorola-moto-g-play-2021-pc-via-magisk/, does not mention unlocking Bootloader with magisk~ just run magisk. Zip, Android it's rooted.
So my question, is that does the magisk v23 unlock Bootloader for you, or was that nugget just left out of this article?
I am obviously not new to this so would appreciate any counsel on this~ it does seem too easy 2 be right, but would appreciate some verification.
Thanks in advance
Roger S
rnshepard said:
Hi, have been reading posts here, but I'm trying to get a grasp on all involved to root my phone. I am pc literate but this is all new.
One site I got instructions on, https://www.thenextdroid.com/root-motorola-moto-g-play-2021-pc-via-magisk/, does not mention unlocking Bootloader with magisk~ just run magisk. Zip, Android it's rooted.
So my question, is that does the magisk v23 unlock Bootloader for you, or was that nugget just left out of this article?
I am obviously not new to this so would appreciate any counsel on this~ it does seem too easy 2 be right, but would appreciate some verification.
Thanks in advance
Roger S
Click to expand...
Click to collapse
You must unlock the bootloader first.
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
rnshepard said:
Hi, have been reading posts here, but I'm trying to get a grasp on all involved to root my phone. I am pc literate but this is all new.
One site I got instructions on, https://www.thenextdroid.com/root-motorola-moto-g-play-2021-pc-via-magisk/, does not mention unlocking Bootloader with magisk~ just run magisk. Zip, Android it's rooted.
So my question, is that does the magisk v23 unlock Bootloader for you, or was that nugget just left out of this article?
I am obviously not new to this so would appreciate any counsel on this~ it does seem too easy 2 be right, but would appreciate some verification.
Thanks in advance
Roger S
Click to expand...
Click to collapse
For unlocking the bootloader I followed the instructions from Dr.E (Max Lee) here
it still works for all Motorola devices currently and I used magisk to flash my stock firmware boot.img to root I also installed a twrp image from this forum I went into 2 bootloops trying to root this phone but I can say it's way better rooted than locked
supapapibrando said:
For unlocking the bootloader I followed the instructions from Dr.E (Max Lee) here
it still works for all Motorola devices currently and I used magisk to flash my stock firmware boot.img to root I also installed a twrp image from this forum I went into 2 bootloops trying to root this phone but I can say it's way better rooted than locked
Click to expand...
Click to collapse
The bootloops were caused by my own negligence and trial and error