Related
*Unlocking bootloader will remove all your data!*
I'm using Windows 7, and that's the steps i did. (it should be simmilar for other systems too)
Getting code:
Code will look simmilar to this: DB1ED223C5537BA756FB0671E425D650
Method 1 (no root):
Go to
https://passwordsgenerator.net/md5-hash-generator/ copy paste serial number and click generate. Then you should see code in "MD5 Hash of your string". You can also go to simmilar md5 hash generator sites, but this site automatically converts small letters to big letters.
Method 2 (root):
Okay, this is new method that is much easier and you don't need to send IMEI and wait for @the_laser to give you code. Go to terminal emulator, type su and execute it. Then type this and execute it:
redweaver said:
Actually the command is
echo -n NE1GAM4770133666 |md5sum |tr [:lower:] [:upper:]
If you don't use the -n flag, the newline character is also passed and you get a different result
Click to expand...
Click to collapse
Unlocking bootloader:
Download platform-tools which activates adb and fastboot commands (first you need Nokia 3 driver installed if you didn't)
Nokia 3 driver: http://www.devfiles.co/download/3iK0k7Sv/Nokia_3_USB_Drivers.zip
platform-tools Windows: http://www.devfiles.co/download/KtLsN6fX/platform-tools-latest-windows.zip
platform-tools Mac: http://www.devfiles.co/download/OkrfluP0/platform-tools-latest-darwin.zip
platform-tools Linux: http://www.devfiles.co/download/vk5DudZX/platform-tools-latest-linux.zip
Enable usb debugging in Developer options before running adb. To get Developer options, go to settings, about phone and press build number 7 times. Also enable OEM unlock.
Now Connect phone to computer via usb and enable usb file transfer, run cmd as administrator, then type this command which runs adb:
chdir C:/Users/John/Desktop/platform-tools (this is just a example, you need to type your own location of platform-tools)
then type this command to check is your device connected to adb, it will show serial number of your device, if it hangs at waiting device, then you need to reinstall drivers (if you're doing this first time, then it will ask to allow usb debugging on your computer, just tick always allow from this computer and click OK)
adb devices
then type this command to reboot to recovery (you can boot to recovery by holding power on + volume up (only with usb connected) if this command doesn't works)
adb reboot recovery
when booted to recovery, choose reboot to bootloader option with volume sliders (this will boot to fastboot)
when booted to fastboot, it will show text 'FASTBOOT MODE' in down-left corner
now type this command to check is your device connected properly to fastboot.
fastboot devices
if it show characters like 0123456789ABCDEF or simmilar then it is connected properly, if it hangs on waiting device, then you need to reinstall drivers like mentioned above.
Android Nougat (7.0 & 7.1.1):
Now type these commands to unlock bootloader
fastboot.exe -i 0x2e04 oem key (type your key after oem key)
fastboot.exe -i 0x2e04 oem unlock
then press volume up, when asked
Android Oreo (8.0 & 8.1):
First download NE1-0-215H.lk.bin:
https://my.pcloud.com/publink/show?code=XZaLMs7ZclQ2wvKwSb0ofUraMmrsiHh6uk1X
Now type these commands to unlock bootloader
fastboot oem dm-verity <your_unlock_key>
fastboot flash lk NE1-0-215H.lk.bin
fastboot reboot-bootloader
Proceed your unlock procedure.
If you have problem on flashing the lk partition, you can use MTK Smart Phone Flash Tool to flash lk partition manually.
After lk partition flashed, you may encounter "Red State" when booting the phone. Ignore that and boot your phone to Fastboot mode directly with OST LA.
That is it, i tried to explain for you to understand everything i did to unlock bootloader.
Credits:
@the_laser for codes, some additional steps and corrections. Also thanks for new method. @redweaver for new method.
@Hikari_kalyx for Android Oreo method. @bigrammy for NE1-0-215H.lk.bin link.
way to enter recovery without adb -
power off phone
press and hold volume up + power on buttons, insert cable immediately
countdown will start on phone, hold both keys until countdown ends, then IMMEDIATELY release power on key, still holding volume up
you will enter recovery shortly
after installing TWRP it is very important - DO NOT allow /system modification until supersu package installation ! ( or you will require reflashing phone with OST )
another note - can't enter recovery by combination volume-up + power button, if phone not connected to computer
one man reported, that even he successfully flashed TWRP image with "fastboot flash recovery <twrp image>", he still got original recovery.
workaround is to use "fastboot boot <twrp image>" - as we need to have USB cable connected to enter TWRP recovery anyway, not big problem.
the_laser said:
way to enter recovery without adb -
power off phone
press and hold volume up + power on buttons, insert cable immediately
countdown will start on phone, hold both keys until countdown ends, then IMMEDIATELY release power on key, still holding volume up
you will enter recovery shortly
after installing TWRP it is very important - DO NOT allow /system modification until supersu package installation ! ( or you will require reflashing phone with OST )
another note - can't enter recovery by combination volume-up + power button, if phone not connected to computer
one man reported, that even he successfully flashed TWRP image with "fastboot flash recovery <twrp image>", he still got original recovery.
workaround is to use "fastboot boot <twrp image>" - as we need to have USB cable connected to enter TWRP recovery anyway, not big problem.
Click to expand...
Click to collapse
Someone told me that if you flashed twrp, that it automatically removes data encryption. Is that true?
EDIT: i find out that is not true, it asks for some password to decrypt data, but the problem is that idk what is the password
DON'T install xposed! It bootlops.
EDIT: My fault, it actually work but you need to wait more than usual to boot.
That is great guys.
Do we have a working recovery yet?
nafnist said:
That is great guys.
Do we have a working recovery yet?
Click to expand...
Click to collapse
I use this twrp https://1drv.ms/u/s!AsmTb5aqoY12mDZqDZbPOp47QVMV
I have stock recovery, but I use fastboot command 'fastboot boot recoveryname.img' when I need TWRP, and that's awesome because I don't lose stock recovery which is useful to flash OTAs and Nokia zips. I flashed SuperSu 2.79 just fine, but expect some crashes like software update, device monitor crash, but actually everything works, software update works just fine.
SkaboXD said:
Someone told me that if you flashed twrp, that it automatically removes data encryption. Is that true?
EDIT: i find out that is not true, it asks for some password to decrypt data, but the problem is that idk what is the password
Click to expand...
Click to collapse
TWRP can't handle Android 7.x default disk encryption, just press "cancel" and we need to use sdcard as storage for backups and packages because of this
Can I return the bootstrapper lock?
Where are you getting the codes from @the_laser?
abetterlie said:
Where are you getting the codes from @the_laser?
Click to expand...
Click to collapse
Yes
shokohiw said:
Yes
Click to expand...
Click to collapse
you mean to get bootloader locked again?
yes you can just instead of oem unlock type oem lock
I mean where are you getting the OEM unlock keys from?
SkaboXD said:
you mean to get bootloader locked again?
yes you can just instead of oem unlock type oem lock
Click to expand...
Click to collapse
abetterlie said:
I mean where are you getting the OEM unlock keys from?
Click to expand...
Click to collapse
idk, ask @the_laser
the bootloader I unlocked how to install root and twrp
shokohiw said:
the bootloader I unlocked how to install root and twrp
Click to expand...
Click to collapse
link for twrp
https://1drv.ms/u/s!AsmTb5aqoY12mDZqDZbPOp47QVMV
when downloaded, copy twrp to folder platform-tools and rename it to recovery.img
reboot to fastboot, then type this command:
fastboot flash recovery recovery.img
then reboot, fastboot reboot
if it didn't worked, use this command just to boot to twrp (you need to do this everytime when you are connected to PC)
fastboot boot recovery.img
To install root, first disable system modification on twrp then flash this zip for root.
This is not the latest version of SuperSU, but newest releases have some problems and crashes. (at least for me). This is last version that works for me.
That is it.
Thank you!
Is it possible after unlocking, installing twrp and root, to return the device to factory settings for ota updates? If so, how?
shokohiw said:
Is it possible after unlocking, installing twrp and root, to return the device to factory settings for ota updates? If so, how?
Click to expand...
Click to collapse
on twrp, there is a option wipe, click on it, then you will see option swipe to factory reset. then wait and reboot.
And you can now enable system modification if you want (it is recommended to enable it because some zips fails to flash because this option is disabled)
After installing TWRP and rebooting, does not want to boot Android, weighs in on the initial splash screen what to do
Your device has failed verification and may not work properly
shokohiw said:
After installing TWRP and rebooting, does not want to boot Android, weighs in on the initial splash screen what to do
Your device has failed verification and may not work properly
Click to expand...
Click to collapse
Weird, when it says your device has failed verification?
For me reboot works fine
Root your "Barns & Noble Nook 7" BNTV450 using Magisk's Patch Boot Image File option.
BE CAREFUL!
There are always risks involved when you start messing around with a device.
If something goes wrong, you may end up with a non-working "bricked" device.
This is especially true when you start flashing partitions. (In this case boot.)
Disclaimer
I am not responsible for your non-working "bricked" devices.
I have a few of my own.
Requirements
Barns & Noble Nook 7" BNTV450
A computer with working adb and fastboot
USB cable
WiFi connection
Magisk Manager (Link below)
Stock boot image (Link below)
Tested on:
BNTV450-v1.0.2-20161230 Security patch October 5, 2016
BNTV450-v2.0.4-20170927 Security patch August 5, 2017
BNTV450-v2.0.5-20170110 Security patch November 5, 2017 ota update
macOS 10.13.x
Windows 7 Pro
Steps
Unlock bootloader
Boot Magisk patched boot image
Pull stock boot and recovery images from device
Use Magisk to patch pulled stock image
Test and flash new patched boot image
Notes:
Google updates were needed to get everything working correctly.
PlayServices and WebView
Mac users. As with some other devices, I had to unplug and plugin the USB cable between some of the fastboot commands.
fastboot flash boot patched_boot.img and fastboot boot bntv4-recovery.img
Magisk:
There have been a lot of changes in Magisk since I originally used it to root.
Way too many to mention so, just the basics that apply to this device.
Newer versions of Magisk use the Download directory instead of creating and using the MagiskManager directory.
Some apps search for this directory and used it to determine if the device is rooted.
If you previously used Magisk to root and have a MagiskManager directory, you will want to delete it.
To update Magisk Manager.
Use the update option, it will download and install the newest version.
To update Magisk.
The safest way is to patch the boot image again. Test and flash.
The Direct Install option works but, may lead to a non-desirable outcome.
To uninstall Magisk.
Test boot your original boot image to make sure it works.
Check with Magisk Manager, it should say Magisk not installed.
If so, then flash your stock boot image back using fastboot.
If your stock boot image will not boot, then you are stuck with Magisk patched boot images.
Hardware Keys:
Power and Volume Up = Recovery Mode
Power and Volume Down = Factory Mode
It will show on the bottom Left (Sideways on the top left) Detecting boot mode. With bootloader unlocked it flashes this message very fast so you might not see it.
I still can not produce the same results continuously across mine. The newer ones, that came with v2.0.5 seem to work but, the older ones still it's a 50 % chance if I can get it to work. The bricked ones, do not seem to register the key combo on boot.
Files Needed
Magisk
xda Magisk forum. Link
Magisk and MagiskManager Official github downloads. Link
Boot Images
Magisk patched boot image downloads. Link
Stock recovery and boot image downloads. Link
Credits and Thank You:
@topjohnwu - The creator and brilliant mind behind Magisk.
Everyone who has helped me learn through the years.
Last edited 23.Sep.2018
"QUICK" Guide - BNTV450 Nook 7
Unlock Bootloader
THIS WILL VOID YOUR WARRANTY.
Unlocking the bootloader WILL wipe and Factory Reset your device. Make sure to copy, backup and logout of everything before you begin.
Note: adb and fastboot need to be installed and working.
On device
Go to Settings - About and tap on the build number seven times to enable Developer options.
Go to Settings - Developer options and Enable OEM unlocking and USB debugging
Connect to computer and Allow USB debugging?
On computer
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot flashing unlock
On device
Follow the prompts on the device.
Unlock bootloader?
If you unlock the bootloader,you will be able to install custom operating system software on this phone.
A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly.
To prevent unauthorized access to your personal data,unlocking the bootloader will also delete all personal data from your phone(a "factory data reset").
Press the Volume UP/Down buttons to select Yes or No.
Yes (Volume UP):Unlocking(may void warranty).
No (Volume Down): Do not unlock bootloader.
After it returns to fastboot mode, use the power button to turn off, unplug it from computer and then turn on.
It will reboot a few times, including an Erasing... screen.
Once device reboots, run through the initial setup.
Note: Sometimes mine would get stuck on the nook .... animation screen. Give it a few minutes (I wait at least 5 minuets) then power off and power back on.
Note: You will now have the annoying boot delay and "Orange State" message.
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
"QUICK" Guide - BNTV450 Nook 7
Root using Magisk.
MagiskManager 6.0.0 Download
Magisk 17.2 patched v2.0.5 Download
Using Magisk Manager and the provided Magisk patched boot image.
Note: When booting an image from "fastboot", you should not see the initial "orange boot" screen.
Make sure to grant permission if and when prompted on device.
Some of the adb and fastboot commands may require input on the device.
On device
Go to Settings - About and tap on the build number seven times to enable Developer options.
Go to Settings - Developer options and Enable USB debugging
Connect to computer and Allow USB debugging?
On computer
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot m172_v205_boot.img
Wait for device to boot then.
Reminder. Make sure to grant permission if and when prompted on device.
Code:
adb install -r MagiskManager-v6.0.0.apk
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/bntv4-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/bntv4-recovery.img"
adb pull /sdcard/bntv4-boot.img
adb pull /sdcard/bntv4-recovery.img
Test the images you just made.
Code:
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot bntv4-recovery.img
Wait for device to boot into recovery mode then.
On device
In Stock Recovery use the volume down key to highlight Reboot to bootloader and press the power button.
Wait for device to boot into fastboot mode then.
On computer
Code:
fastboot boot bntv4-boot.img
Wait for device to boot then.
On device:
If you haven't setup WiFi, do so now.
Open MagiskManager
Tap on Install
Select Install
Select Patch Boot Image File
Tap on Internal storage
- Note: If Internal storage is not displayed. Tap on the 3-dot menu (upper right corner) and select Show SD card.
Scroll down and tap on bntv4-boot.img
When Magisk is done patching the image file, select CLOSE
You can close MagiskManager as well.
Copy and test your Magisk patched boot image.
On computer
Code:
adb pull /sdcard/download/patched_boot.img
adb reboot bootloader
Wait for device to boot into fastboot mode then.
Code:
fastboot boot patched_boot.img
On device
Open MagiskManager
Note: You should see that Magisk is installed and active.
To do a quick check.
On Computer
Code:
adb shell
[email protected]:/ $su
[email protected]:/ #exit
[email protected]:/ $exit
If it worked, and you are ready to say goodbye to stock Non-root.
Code:
adb reboot bootloader
fastboot flash boot patched_boot.img
fastboot boot bntv4-recovery.img
Once it's booted into Recovery, unplug the device.
On device
In Stock Recovery use the volume down key to highlight Wipe cache partition and press the power button.
-- Wiping /cache...
Formatting /cache...
Cache wipe complete.
Then with Reboot system now highlighted press the power button.
You are now rooted and running Magisk.
Last edited 23.Sep.2018
Links to my shell logs.
Unlock bootloader. Pastbin
Root. Pastbin
volume button does not react
Hi
unlocking does not work
As mentioned in the other discussion, the volume up button does not seem to react and so the unlocking does not work. Also one user suggested using the reset button after pressing the volume up button for the unlock; that also does not work for me
Do u have any other suggestions to unlock ?;
arrmusic said:
Hi
unlocking does not work
As mentioned in the other discussion, the volume up button does not seem to react and so the unlocking does not work. Also one user suggested using the reset button after pressing the volume up button for the unlock; that also does not work for me
Do u have any other suggestions to unlock ?;
Click to expand...
Click to collapse
I never ran into this problem. So short answer - No.
Can you point me to that other discussion?
What do you get if you run fastboot oem lks
fastboot oem unlock is supported on this device. You could give that command a try and see if there is a difference.
Not sure what you have tried.
I would start with "Factory Reset" in stock recovery. Skip through the initial setup and try again.
Note: Developer option menu has a toggle at the top, make sure it is turned On.
Sent from my BNTV450 using XDA Labs
Volume up button not recognised while fastboot unlock
Hi
Here is the discussion thread that I was referring to where people are stuck with unresponsive volume up button for fastboot unlock
https://forum.xda-developers.com/nook-7/help/nook-rootable-t3510289
I didn't do the factory reset. So maybe I will do that and see if it works.
unlock not working
Hi
Just to further update you on your reply; i did a factory reset and tried to unlock the bootloader but i get to the same problem; the volume button does not respond; so stuck with the message 'press the volume up button to unlock the bootloader'
I did the fastboot oem lks and that commands executes well and it gives me a OK output.
Cheers & New year greetings!
Any update on the unlock issue
Hi
Is there any update on the unlock issue i reported some time back? My last update on this was executing the command => 'I did the fastboot oem lks and that commands executes well and it gives me OK output.'
not sure if my last update was interpreted in the right way; it does nothing when i type fastboot oem lks except saying it is OK (which i suppose is the expected output of fastboot oem lks). So i do not know how to get around the volume keys not being recognised to go further in unlocking
I still can not use the volume keys for the unlock as it does not seem to react. just stuck a bit on this
@arrmusic I guessed it it looked more like this.
Code:
fastboot oem lks
...
(bootloader) lks = 1
OKAY [ 0.000s]
finished. total time: 0.000s
lks = 0 would be unlocked.
I am looking for a way to un-brick these. I think that may be the best way to correct the button problem also.
What os version are you running? (BNTV450-vx.x.x-20xxxxx)
What do you get when you run fastboot flashing get_unlock_ability ?
Tested a few things tonight.
I was NOT able to re-lock the bootloader on either of my rooted devices.(BNTV450-v2.0.4)
Found some more inconsistencies with power and volume key boot combinations. (Among other things.)
"FAILED (remote: not support on security)" apparently is not just for unlocked devices.
Sent from my BNTV450 using XDA Labs
not able to unlock yet
Hi
Many thanks for your reply.
I seem to have the software version v1.0.2;
I tried to find by googling v2.0.4 but i am not able to find that security update anywhere to download; do you have the v2.0.4 file? can i have it somehow?
I ran the commands u had mentioned in your previous reply.
fastboot flashing get_unlock_ability
...
(bootloader) unlock_ability = 16777216
OKAY [ 0.012s]
finished. total time: 0.012s
fastboot oem lks
...
(bootloader) lks = 1
OKAY [ 0.004s]
finished. total time: 0.008s
What is the origin of the boot.img?
What is the origin of the boot.img? I'd rather not just flash something without knowing where its come from.
74178951237895321 said:
What is the origin of the boot.img? I'd rather not just flash something without knowing where its come from.
Click to expand...
Click to collapse
v2.0.3 boot came from a supposed "N" rom for this device and was the first boot image I was able to make bootable. It was still API 23 "M" by the way.
I would have to find and unpack the original file to see what I edited to make it bootable.
All others are "dd" copies from my own device(s).
I am working on updating the OP and the "Quick Guide"
Boot Images
Download Magisk 15.3 patched v2.0.5 (Preferred and current boot image.)
Sent from my ford using XDA Labs
Scatter file for Mediatek MT8163, opening the tablet
Can you post the scatter file for the Mediatek MT8163?
I've been trying to make my own image dumps for the Nook 7, but have run into an issue where the device won't stay in a readable mode for SP Flash Tools long enough while the battery is still connected. So, the solution for most phones is to disconnect the battery and have it powered over USB only so that it won't go past the preloader and into the charging mode.
But I can't get the darned thing open! My phone has a similar style housing and I had to use a suction cup on the glass while prying at the edges to gain access. But for the Nook 7 its just not working.
Edit: This started while trying to soft load TWRP to make the image dumps. When I do
Code:
fastboot boot twrp.img
It tells me that the kernel address lies outside of memory. Its possible to supply an address to load it at with the fastboot command which you are supposed to learn from the scatter file. I found what I thought was a valid MT8163 scatter file but using the address found within did not fix the issue.
I forgot you mentioned that you didn't pull the original image from your device yourself. I've been trying to root this without relying on images from others. Your latest guide to pulling and modifying your own boot.img is a decent enough middle ground for me to use. Thanks.
@74178951237895321
Sent from my Nexus 7 (2013) using XDA Labs
I was able to get a successful root by following the steps in this thread in combination with those mentioned in this one. ipdev, just to satisfy my curiosity, where did you find this "N rom" image?
ipdev said:
So we hit a snag using Magisk 15.4+ to patch a stock boot image on this device.
Click to expand...
Click to collapse
So, I was dumb and went through with updating Magisk without checking this thread first, and now my tablet's stuck in a bootloop that I can't seem to get out of. @ipdev, do you have any ideas on how this happened/how to get out of it? The tablet can't get past the "Orange state your device has been unlocked etc. etc." screen, and I can't get it to boot into recovery either (using Power+Volume Down, is the combination something else on this tablet?). fastboot won't discover it either, probably because it reboots within seconds and never gets to a point where it could be recognized. I'm thinking of letting it bleed out until its battery dies (unfortunately, the battery is soldered and glued in, so I can't just disconnect it), and checking on it in the morning to see if it will be cooperative enough to let me flash the modified Magisk image.
@saagarjha
I have a few in the same condition. As you noticed, the battery is soldered in so the best you can do is disconnect the screen. (Connector to the right of battery.)
One of these days, I was going to try sp flashtools to see if I could recover one of mine. (I'm not sure if it works with these.)
Sent from my Nexus 5 using XDA Labs
I let the tablet run out of battery and then plugged it back in again and it immediately got stuck in the same bootloop, so it looks like it's actually bricked rather than just pretending. I think SP Flash Tools is the way to go at this point; we'd have to find a functioning preloader driver and scatter file to do that, however. It might be possible to simulate disconnecting the battery by shorting the battery's leads, but I'm not sure if this would work (or is even safe to do).
I was having trouble with unlocking the boot loader on my v1 launch version of this Nook. Recently I dropped it and got a new one via the replacement plan - this one was marked 'v2', came with a 2.x firmware that I wasn't able to even get on my launch Nook 7.
Anyway, this one unlocked without any problems. Thought this might be helpful to anybody having trouble unlocking the bootloader. Consider the revision of the Nook you have. Maybe the solution here is flashing the v2 firmwares to the v1? Hard to say.
unable to unlock
So I did "adb reboot bootloader" and the tablet rebooted and says "=> FASTBOOT mode..." on the screen.
I then did "fastboot flashing unlock" on the computer. Nothing happened on the device and my computer says "< waiting for device >". Could anyone please let me know what I did wrong? Thank you very much.
Hi all!
You have just upgraded to Oreo 8.1, you want to use Google Camera but you need locked bootloader and you want to preserve your data?
This IS possible, but you MUST follow all steps otherwise you may lose your data, so do it at your own risk. (you have been warned)
WARNING !!!
After May update unlocking/relocking bootloader will wipe your data. This can be avoided if you hold Vol- when running these scripts.
Let's start:
-Read carefully all steps twice
-Download support tool HERE
-Install ADB drivers (option 0 from support tool)
-Enable USB debug and OEM unlock on Mi a1
-Connect Mi a1 to PC with USB cable
-Select option 1 on support tool. Phone will be rebooted in fastboot mode.
-Confirm pressing Y
BEFORE PRESSING ENTER ON PC YOU MUST PRESS AND HOLD VOL- ON MI A1
-Press ENTER
Bootloader should be unlocked and phone should be in fastboot mode without losing data.
Press any key on PC running support tool and phone will be booted with temporary root access.
-Install Magisk Manager (OPTION 2 support Tool)
-Open command prompt in adb folder on PC and type:
Code:
adb shell
then
Code:
su
Shell should ask Superuser access: from Magisk Manager allow root access.
In the same Command prompt type:
Code:
setprop persist.camera.HAL3.enabled 1
-Reboot phone and test if API2 are enabled (Google Camera port shouldn't crash anymore)
-Uninstall Magisk Manager (optional)
(Optional) If you have an unmodified system you can relock bootloader.
-Select option 3 in support tool
-Confirm
BEFORE PRESSING ENTER ON PC YOU MUST PRESS AND HOLD VOL- ON MI A1
-Press Enter
Bootloader will be relocked without losing data
Hold power button until phone reboots
OTA should work fine.
Camera2 Api should remain active until factory reset.
Credits:
@flex1911
@IjazCI
Have you tried this trick?
yes it worked.. !!! thanks @sipollo
Worked for me , thanks
So trick is pressing vol- when executing "fastboot oem unlock" & that will skip wipe.
Thank ?
.:Addicted:. said:
So trick is pressing vol- when executing "fastboot oem unlock" & that will skip wipe.
Thank ?
Click to expand...
Click to collapse
Yes, but after that if you boot TWRP data will be wiped anyway. (For security purposes)
Anyway in this guide TWRP is not booted, only Magisk-patched boot is used. So no wipes
I used this method to bypass wipe. If i reboot after the unlock/lock command, it does not perform a wipe. And I booted to twrp and executed some adb commands also without wiping.
solis_f said:
I used this method to bypass wipe. If i reboot after the unlock/lock command, it does not perform a wipe. And I booted to twrp and executed some adb commands also without wiping.
Click to expand...
Click to collapse
If I understood correctly wipe is performed only the first time you boot TWRP after changing bootloader status. Then you can boot TWRP without problems, i've done it several times.
I'm stuck on the su command nothing happens on the magisk manager... And in the cmd it shows "su: nothing found"... can anyone help?
haftzes said:
I'm stuck on the su command nothing happens on the magisk manager... And in the cmd it shows "su: nothing found"... can anyone help?
Click to expand...
Click to collapse
If you open Magisk Manager says that Magisk is installed or not?
sipollo said:
If you open Magisk Manager says that Magisk is installed or not?
Click to expand...
Click to collapse
Not installed...
haftzes said:
Not installed...
Click to expand...
Click to collapse
Go where did you extract tool, open prompt and type FILES\adb reboot bootloader, then when in fastboot mode type FILES\fastboot boot bootmagisk.img. Phone should boot with temporary root. Continue following the guide.
sipollo said:
Go where did you extract tool, open prompt and type FILES\adb reboot bootloader, then when in fastboot mode type FILES\fastboot boot bootmagisk.img. Phone should boot with temporary root. Continue following the guide.
Click to expand...
Click to collapse
followed the instractions but phone stuck on android one screen ... what should i do know ?
haftzes said:
followed the instractions but phone stuck on android one screen ... what should i do know ?
Click to expand...
Click to collapse
Press power button and vol- until phone reboots to fastboot and retry with fastboot boot FILES\bootmagisk.img Sometimes Magisk makes this jokes...
sipollo said:
Press power button and vol- until phone reboots to fastboot and retry with fastboot boot FILES\bootmagisk.img Sometimes Magisk makes this jokes...
Click to expand...
Click to collapse
done !!! thanks !! also i can enable EIS now ??
haftzes said:
done !!! thanks !! also i can enable EIS now ??
Click to expand...
Click to collapse
Some users say you have to type setprop persist.camera.eis.enable 1 but for me it is not necessary, you can enable eis in Google camera video options. Reboot and try yourself.
sipollo said:
Some users say you have to type setprop persist.camera.eis.enable 1 but for me it is not necessary, you can enable eis in Google camera video options. Reboot and try yourself.
Click to expand...
Click to collapse
No data will be wiped ???
Amanpreetsingh said:
No data will be wiped ???
Click to expand...
Click to collapse
If you follow carefully all steps your data will be safe.
sipollo said:
If you follow carefully all steps your data will be safe.
Click to expand...
Click to collapse
With this method ota will work or not ??
There's a ton of information out there, but finding it can sometimes be a challenge, especially for a newbie. And then there's posts to read through, in case a process has changed and it's only talked about in a single place, buried any number of pages back. So this is my attempt to put all Pixel 3 how-to's into a single thread. Everything below is what worked for me, from start to finish, with a fresh phone directly from Google that was bootloader-locked, unrooted, and running stock Android. Comments are welcome and encouraged: if something doesn't work for you, or you have a better/quicker/more reliable way of doing something, or maybe I made a mistake...let me know!
A few things:
Everything in this guide was tested on a "regular" Pixel 3 (blueline). It should all work exactly the same on a Pixel 3 XL (crosshatch), as long as you download the appropriate files (specifically the factory/OTA images and TWRP). I'm posting this in both blueline and crosshatch forums.
This first post will have links to files and the tools you need, as well as general things (like how to enable debugging and boot into recovery). The second post has how-to's for the big stuff (flashing images, TWRP, unlocking, etc).
I'm not responsible for anything you do. Follow these guides at your own risk. Doing so may also void your warranty.
Files and URLs
Official Android files
Factory (wipes device and requires unlocked bootloader): https://developers.google.com/android/images
Full OTA (leaves data intact, can be done via ADB sideload): https://developers.google.com/android/ota
Preview/beta OTA: https://developer.android.com/preview/download-ota.html
TWRP
XDA thread: https://forum.xda-developers.com/pixel-3-xl/development/twrp-3-2-3-0-pixel-3-xl-t3861623
Download: https://dl.twrp.me/crosshatch/
Magisk
XDA thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
ADB and Fastboot
Google USB drivers: https://developer.android.com/studio/run/win-usb
SDK platform tools: https://developer.android.com/studio/releases/platform-tools
Download the ZIP and open (no need to extract the whole thing)
Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
General
Enable USB debugging
Download Google USB drivers (see above)
Download SDK platform tools and copy required files to their own directory (see above)
Enable USB debugging (Settings > About > tap Build 7 times > back > Developer options)
Plug phone into computer and when "Allow USB debugging" box comes up, check the box and allow (may need to have adb daemon running on the computer already, see below)
Fastboot mode (using hardware keys) aka bootloader
Power off
Hold VOL- and press/hold PWR until bootloader (fastboot) comes up
Recovery mode (using hardware keys)
Get into Fastboot mode (see above)
Use VOL buttons to find Recovery in the list, use PWR to select (should boot to broken android image)
Hold PWR and press VOL+ once to get into recovery
Useful ADB and Fastboot commands
Enable USB debugging (see above)
ADB (used while phone is "on" and booted up):
Use "adb devices" to ensure the computer is authorized
Use "adb reboot bootloader" to get into Fastboot
Fastboot mode
Use "fastboot devices" to verify computer can see your phone
Update #1: Items below marked through were removed since they don't really apply to Android 10.
Update #2: Edited to reflect changes in root with Android 11.
A quick note: everything below is assuming you're using Windows 10. When it says "Type...", this assumes you've opened a command window in the location of adb/fastboot and that all files referenced are in the same directory and (in some cases) renamed as I reference them (short names without spaces simplifies things). If you're using Powershell, you will probably need to change "adb" and "fastboot" to read ".\adb" and ".\fastboot" so Powershell will use the local files.
Unlocking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
In Developer Options, enable OEM unlocking and confirm (it may ask you to input fingerprint or PIN/pattern/password)
Boot into Fastboot mode (see above)
Type to unlock:
Code:
fastboot flashing unlock
Use VOL+ key to get the options on the screen to read "Unlock the bootloader" and use PWR button to select
Type to reboot:
Code:
fastboot reboot
Locking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Boot into Fastboot mode (see above)
IMPORTANT: restore stock recovery if you replaced it with TWRP (this should prevent the "Can't find valid operating system" issue)
Type to lock:
Code:
fastboot flashing lock
Use VOL buttons to find "Lock the bootloader" and use PWR to select
Type to reboot:
Code:
fastboot reboot
Factory reset via fastboot (can also do this without wiping data)
THIS COULD WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Download factory image ZIP and unzip all files into their own folder
Unlock bootloader (see above)
Reboot into Fastboot mode
You have 2 options:
Register the location of fastboot.exe with the PATH system variable and run "flash-all.bat"
Wipe data: just run "flash-all.bat" and call it a day
Do not wipe data: open "flash-all.bat" in a text editor (careful not to double-click and run it!), remove the "-w" from the last line to disable the wiping of data, then save, close, and run
Move the 3 files (bootloader IMG, radio IMG, image ZIP) into the ADB folder, rename for simplicity if you want, launch cmd or Powershell, and run the commands below (which come from "flash-all.bat")
Wipe data: type out commands below, but at last line, add "-w" flag: fastboot -w update image.zip
Do not wipe data: type out commands below as written (no "-w" flag)
The commands:
Code:
fastboot flash bootloader bootloader-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot flash radio radio-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot update image-blueline-XXXX.zip
Note: The last command (update image) will launch the red "fastbootd" screen, so don't worry and be patient while the command line tells you what's happening. The phone will reboot on its own into the Android system (not fastboot) afterward.
Root Android 10+ using Magisk (Canary channel)
This must be done after every update, and you cannot use the patched file from a different phone!
Unlock bootloader (see above)
Download factory image (not OTA, see link above)
Download and install Magisk Manager Canary (see link above)
In Magisk Manager settings, set Update Channel to "Canary"
Extract boot.img from image-blueline-XXXX.zip found in the factory image you downloaded
Place boot.img on your phone's internal storage
Open Magisk Manager and do:
tap "Install" button (next to "Magisk" in first block on the main screen)
"Select and Patch a File" option
Find boot.img file you just placed on your phone
tap "Let's Go"
When finished, move the newly-created magisk_patched.img file over to your computer's ADB directory
Reboot into bootloader
Type:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Open up Magisk Manager and make sure everything's good!
Note : if you get stuck in fastboot mode or in a boot loop, flash the stock boot.img to both slots and try again
Code:
fastboot flash boot boot.img --slot all
Optional:
for adblocking, tap "Systemless hosts" in Magisk Manager, then install AdAway using F-Droid
install a performance kernel like Kirisakura for Bluecross (R)
Updating Android 10+ while rooted
You can't take an OTA while rooted, so updating Android 10+ (as in monthly updates) can be one of two ways.
Method #1 (faster, but more chance for issues)
Download OTA ZIP and move it to ADB folder (don't unzip it)
This does not require an unlocked bootloader, but does require USB debugging (see above)
Get boot.img from the factory image (see first post on where to download this) and place your ADB directory
Reboot into bootloader / fastboot and type to restore stock boot to both slots:
Code:
fastboot flash boot --slot all boot.img
fastboot reboot bootloader
[wait for reboot]
Use VOL buttons to select "Apply update from ADB"
Type (where filename is the name of the file you want to sideload):
Code:
adb sideload filename.zip
Wait for it to finish, will take you back to Recovery when it's done
Reboot using menu
Method #2 (takes longer, but best bet for minimal issues)
Follow "Factory reset via fastboot" instructions (see above, make sure you don't wipe your data!)
Take the OTA in the official way (through Android)
Follow "Root Android 10+ using Magisk Canary" instructions (see above)
Boot into TWRP (3.3.0-0 or higher)
Download TWRP IMG and place in ADB folder (rename the file to twrp.img)
If not already done, unlock the bootloader (see above)
Reboot into bootloader
Type to boot TWRP (it will restart and should boot into TWRP):
Code:
fastboot boot twrp.img
OPTIONAL: Replace recovery by installing TWRP
Your phone should automatically mount, so move twrp.img from PC to Download folder on phone's internal storage
Advanced > Install Recovery Ramdisk > choose TWRP IMG > Swipe to install
Back > Fix Recovery Bootloop > Reboot System > Do Not Install when asked if TWRP should install app
Root using Magisk (18.1 or higher)
Download Magisk ZIP and move to device
Boot into TWRP (see above)
Enter your PIN/pattern/password to decrypt (unnecessary if you are not using security on your phone)
Swipe to Allow Modifications (to system)
Install > find and select the Magisk ZIP > Slide to install
Wipe cache > Reboot system > Do Not Install when asked if TWRP should install app
Open Magisk Manager to verify latest and to install modules
"Can't find valid operating system" booting issue
Unlock your bootloader again (see above)
Follow steps for "Factory reset via fastboot" (see above) and keep the wipe flag
After it reboots, power off (press PWR and select "Power off" from menu)
Follow steps for "Locking the bootloader" (see above)
After it reboots into Fastboot mode, have it start using the PWR button
Android Recovery / "Cannot load Android system" booting issue
This can happen for a number of reasons, but the fix is the same: "Factory reset via fastboot" (see above). You probably do not need to wipe user data, so you can omit the "-w" flag.
If you still get the error message, select the "Try again" option. If it still doesn't work, try "Factory reset via fastboot" again, as well as "Try again". If it doesn't work this time, you probably have no choice but to do a factory reset (in which you will definitely lose your data).
If it happens after flashing Magisk in TWRP, though, you've got a slightly different issue and the problem will persist no matter how many times you flash the factory images and re-install Magisk. This is probably due to something leftover in the previous Magisk installation that conflicts with the new installation. There are two ways to handle this.
First and easiest: uninstall Magisk Manager app before rebooting into the bootloader and running fastboot commands. Then proceed as usual (sideload OTA or flash factory images via fastboot, boot TWRP, and flash Magisk). All guides for this are above. This method preserves any modules you have installed.
Second and more complete (if the above method still gives you trouble):
download to your phone the Magisk ZIP, Magisk Uninstaller ZIP, and Magisk APK from this XDA thread
uninstall the Magisk Manager app
reboot to bootloader
using fastboot, boot into TWRP using IMG (you don't need to replace boot with TWRP)
flash Magisk Uninstaller ZIP
wipe Dalvik
flash Magisk ZIP
wipe Dalvik
reboot system (do not install TWRP)
install Magisk Manager APK and re-install any modules
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
farfegnugen said:
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Click to expand...
Click to collapse
Is your bootoader Locked or Unlocked?
---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------
mcwups1 said:
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
Click to expand...
Click to collapse
No it does NOT matter which build you unlocked your BL
*edit*
Try to go into settings and force the update or you can always flash the entire factory img for april
farfegnugen said:
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Click to expand...
Click to collapse
1.) If you somehow have an unlocked bootloader, yes, it would work for the Verizon Pixel 3 XL. However, I was under the impression that Google will not unlock the BL for the Verizon variant and there is currently no way to "hack" it.
2.) It should work the same whether you're on P or Q, though if you want to remain with Q, make sure you download the beta files directly from Google (rather than the P images) and use Magisk 19.0 instead of 18.1.
mcwups1 said:
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
Click to expand...
Click to collapse
You can force it to check for updates; when you unlocked the BL shouldn't matter if you're using a patched boot image.
HACK3DANDR0ID said:
Is your bootoader Locked or Unlocked?
---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------
No it does NOT matter which build you unlocked your BL
*edit*
Try to go into settings and force the update or you can always flash the entire factory img for april
Click to expand...
Click to collapse
I haven't done anything to the phone since I got it 3 weeks ago but hoping to. Can the VZ version be unlocked? If so please point me in the right direction.
farfegnugen said:
I haven't done anything to the phone since I got it 3 weeks ago but hoping to. Can the VZ version be unlocked? If so please point me in the right direction.
Click to expand...
Click to collapse
No, but they working on finding a way to unlock it: [Bounty] Unlock Bootloader VZW Pixel 3 XL by coolhandz
Homeboy76 said:
No, but they working on finding a way to unlock it: [Bounty] Unlock Bootloader VZW Pixel 3 XL by coolhandz
Click to expand...
Click to collapse
Thanks so much for the info! Its difficult trying to find the current status of all the diff devices' root statuses.
Thanks for this guide, when using the flash-all.bat and wiping the device will this method flash to both slots?
CadTechBGMC said:
Thanks for this guide, when using the flash-all.bat and wiping the device will this method flash to both slots?
Click to expand...
Click to collapse
yes, if you are flashing with wipe all option (without removing -w) it does flash to both slots.
Regarding getting to fastboot:
Since I have flashed April security update and after lightly bricking my Pixel 3Xl, (I have not lost data but I was unable to boot till solving the brick), the phone doesn't stay in fastboot when I use the adb command to get into it and all I can do to get to stay in fastboot is the power and volume down combo for more than 40 seconds.
I have my pixel working perfectly with root and kirisakura kernel but it is a bit of a pain getting to boot TWRP from fastboot for flashing stuff.
EMJI79 said:
Regarding getting to fastboot:
Since I have flashed April security update and after lightly bricking my Pixel 3Xl, (I have not lost data but I was unable to boot till solving the brick), the phone doesn't stay in fastboot when I use the adb command to get into it and all I can do to get to stay in fastboot is the power and volume down combo for more than 40 seconds.
I have my pixel working perfectly with root and kirisakura kernel but it is a bit of a pain getting to boot TWRP from fastboot for flashing stuff.
Click to expand...
Click to collapse
yeah if i try to get into fastboot directly from a power on state it doesn't stick on fastboot blinks for a second and then starts with reboot process, probably we are pressing it too long.
what i do normally is to power off the device first wait for few seconds then then use key combination to get it to fastboot from power-off state. Booting from fastboot to twrp never had any issues unless i had messed up the twrp installation due to some mess i did.
SacredDeviL666 said:
yeah if i try to get into fastboot directly from a power on state it doesn't stick on fastboot blinks for a second and then starts with reboot process, probably we are pressing it too long.
Click to expand...
Click to collapse
I have to press the keys 40 seconds even from power off.
EMJI79 said:
I have to press the keys 40 seconds even from power off.
Click to expand...
Click to collapse
definitely not 40seconds from power off state for me. not sure whats happening there
Maybe a short video would be a help to some of us newbies
Dumb question. Probably gonna upgrade from an original Pixel XL soon. As long as I buy it from store.google.com, I should be able to unlock the bootloader without worrying about a crack/hack, correct? Thanks!
Drashnar said:
Dumb question. Probably gonna upgrade from an original Pixel XL soon. As long as I buy it from store.google.com, I should be able to unlock the bootloader without worrying about a crack/hack, correct? Thanks!
Click to expand...
Click to collapse
That is correct. I made the same switch from an OG Pixel and Pixel XL to P3 and P3XL right after release. Unlock the bootloader before you mess around a lot since it will do a factory reset.
How about backups? Does anyone backup and restore, or not?
If so, how do you do it with this 2 partition system?
installed and I like it. I cant get the clock off the lock screen. all settings says it is off.
wished it had MicroG installed instead of gapps
Hi, I am writing this guide because many people followed other guides in the forum and lost their data. This is the proper way of unlocking the bootloader without losing your data.
0 - Read the whole guide before proceeding and proceed at your own risk!
1 - Make sure you have adb and fastboot installed on your device,
For Windows follow this guide (I suggest installing it system-wide, so that you can execute commands from every directory on your PC): https://forum.xda-developers.com/showthread.php?t=2588979
For MacOS and Linux : https://www.xda-developers.com/install-adb-windows-macos-linux/
2 - After the required tools are installed go to Settings -> About Phone on your phone and keep tapping on build number until a toast notification tells you that the developer settings are enabled.
3 - Go to Settings -> System -> Developer Settings and enable OEM unlocking option.
4 - Turn off the phone and when it's fully off, hold power + vol down button to boot into fastboot mode. When you've done this step successfully, you will see a blue FASTBOOT text on the screen with a bunny scrambling the internals of Android.
5 - Connect your phone to your PC and open a CLI/terminal/PowerShell window and type this but do NOT hit enter :
Code:
fastboot oem unlock
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again. This basically tricks the phone to boot into Fastboot mode instead of erase mode. To make sure the phone doesn't boot into erase mode on the next boot you need to do the following:
6 - While in fastboot mode type this into the CLI/terminal/PowerShell window but do NOT hit enter :
Code:
fastboot reboot
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
7 - Now you are ready to boot into your system. Either boot by holding power button or typing
Code:
fastboot reboot
into the terminal and hitting enter.
By rebooting twice, you make sure the phone doesn't boot into erase mode. If you flash the stock ROM beforehand and setup your device (login to Play Store), your device will still be Play Store certified by this method. But if you unlock the bootloader and the phone erases its storage, you won't be able to download apps like Netflix, because your device will not be certified by Play Store, this is because the Play Store checks for unlocked bootloaders. But by making it check the certification while it's locked and then unlocking the bootloader, you can make this issue go away. Feel free to ask for more proper guides for dummies, if you need. I have bricked my device many times and learnt by trial and error, so I'd be happy to make you avoid those same mistakes. Cheers.
No need double reboot
Os_Herdz said:
No need double reboot
Click to expand...
Click to collapse
It is not necessary, but a preventative measure. I've had instances where I hadn't rebooted twice and the phone booted into erase mode. This is a guide for people who want to make sure they won't lose data.
Another tip:
If you're with stock everything and don't want to loose data, do not boot into recovery mode (power + vol+) as it sometimes try to wipe data without any confirmation. Did happened here once, back in March 2019, but thankfully my pictures and most data are stored in MicroSD card.
RFD80M-75679 said:
Another tip:
If you're with stock everything and don't want to loose data, do not boot into recovery mode (power + vol+) as it sometimes try to wipe data without any confirmation. Did happened here once, back in March 2019, but thankfully my pictures and most data are stored in MicroSD card.
Click to expand...
Click to collapse
Can confirm, if your bootloader is unlocked and you don't have TWRP installed, booting into recovery mode will wipe the device.
marstonpear said:
Hi, I am writing this guide because many people followed other guides in the forum and lost their data. This is the proper way of unlocking the bootloader without losing your data.
0 - Read the whole guide before proceeding and proceed at your own risk!
1 - Make sure you have adb and fastboot installed on your device,
For Windows follow this guide (I suggest installing it system-wide, so that you can execute commands from every directory on your PC): https://forum.xda-developers.com/showthread.php?t=2588979
For MacOS and Linux : https://www.xda-developers.com/install-adb-windows-macos-linux/
2 - After the required tools are installed go to Settings -> About Phone on your phone and keep tapping on build number until a toast notification tells you that the developer settings are enabled.
3 - Go to Settings -> System -> Developer Settings and enable OEM unlocking option.
4 - Turn off the phone and when it's fully off, hold power + vol down button to boot into fastboot mode. When you've done this step successfully, you will see a blue FASTBOOT text on the screen with a bunny scrambling the internals of Android.
5 - Connect your phone to your PC and open a CLI/terminal/PowerShell window and type this but do NOT hit enter :
Code:
fastboot oem unlock
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again. This basically tricks the phone to boot into Fastboot mode instead of erase mode. To make sure the phone doesn't boot into erase mode on the next boot you need to do the following:
6 - While in fastboot mode type this into the CLI/terminal/PowerShell window but do NOT hit enter :
Code:
fastboot reboot
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
7 - Now you are ready to boot into your system. Either boot by holding power button or typing
Code:
fastboot reboot
into the terminal and hitting enter.
By rebooting twice, you make sure the phone doesn't boot into erase mode. If you flash the stock ROM beforehand and setup your device (login to Play Store), your device will still be Play Store certified by this method. But if you unlock the bootloader and the phone erases its storage, you won't be able to download apps like Netflix, because your device will not be certified by Play Store, this is because the Play Store checks for unlocked bootloaders. But by making it check the certification while it's locked and then unlocking the bootloader, you can make this issue go away. Feel free to ask for more proper guides for dummies, if you need. I have bricked my device many times and learnt by trial and error, so I'd be happy to make you avoid those same mistakes. Cheers.
Click to expand...
Click to collapse
When I type fastboot oem unlock and press enter, a screen shows on the device to select unlock or do not unlock. Then what?
softgadget said:
When I type fastboot oem unlock and press enter, a screen shows on the device to select unlock or do not unlock. Then what?
Click to expand...
Click to collapse
It shouldn't ask you to unlock phone or not in fastboot mode, as what I did unlocked mine for months ago. It should return you to fastboot mode in a flash (a fraction of seconds) and manually restart your phone by holding up power button until you'll see unlocked warning and AndroidOne logo.
If it is, try to select "unlock", but your data may wipe afterwards.
RFD80M-75679 said:
It shouldn't ask you to unlock phone or not in fastboot mode, as what I did unlocked mine for months ago. It should return you to fastboot mode in a flash (a fraction of seconds) and manually restart your phone by holding up power button until you'll see unlocked warning and AndroidOne logo.
If it is, try to select "unlock", but your data may wipe afterwards.
Click to expand...
Click to collapse
I am running Android 10 latest update on my Mi A2 and my phone shows a screen to select Unlock or Not to Unlock options. It is in fastboot mode. What is the problem?
softgadget said:
I am running Android 10 latest update on my Mi A2 and my phone shows a screen to select Unlock or Not to Unlock options. It is in fastboot mode. What is the problem?
Click to expand...
Click to collapse
You have another device. This is for Mi A2 Lite, not Mi A2. And on top of that, it works for Android Pie. I don't know for stock Android 10 since we (Mi A2 Lite users) don't have it yet (as of my writing).
RFD80M-75679 said:
You have another device. This is for Mi A2 Lite, not Mi A2. And on top of that, it works for Android Pie. I don't know for stock Android 10 since we (Mi A2 Lite users) don't have it yet (as of my writing).
Click to expand...
Click to collapse
Oh. OK then.thank you
I downgrade to oreo and now when power om phone show message that is bootloader unlocked, so can lock again bootloader to remove that message without lost data or must live with that? If can do that, how? I forgot to say after flash oreo bootloader was locked, but i must unlock again to fix sim cards.
popadic022 said:
I downgrade to oreo and now when power om phone show message that is bootloader unlocked, so can lock again bootloader to remove that message without lost data or must live with that? If can do that, how? I forgot to say after flash oreo bootloader was locked, but i must unlock again to fix sim cards.
Click to expand...
Click to collapse
You can unlock with the same method. But I believe you will flash a zip from TWRP to fix SIM cards and that will break your phone if you lock the bootloader. So after fixing the SIM cards, you need to leave the phone unlocked, otherwise phone will be bricked. If you want to get rid of the ugly splash screen, you can flash a custom splash you can find in the forum.
marstonpear said:
Can confirm, if your bootloader is unlocked and you don't have TWRP installed, booting into recovery mode will wipe the device.
Click to expand...
Click to collapse
So after unlocked the devices, it's recommended to install TWRP to avoid this right ?
gusbalaa said:
So after unlocked the devices, it's recommended to install TWRP to avoid this right ?
Click to expand...
Click to collapse
You can leave it as is, but don't ever boot into recovery if you value your data from Internal Storage or if haven't backed up data to MicroSD.
RFD80M-75679 said:
You can leave it as is, but don't ever boot into recovery if you value your data from Internal Storage or if haven't backed up data to MicroSD.
Click to expand...
Click to collapse
I think I'm gonna install TWRP for safety, my data is already on MicroSD.
EDIT : Is possible to install TWRP & Root without losing data / need to flash Decrypt ?
gusbalaa said:
I think I'm gonna install TWRP for safety, my data is already on MicroSD.
EDIT : Is possible to install TWRP & Root without losing data / need to flash Decrypt ?
Click to expand...
Click to collapse
You don't need to decrypt. You can install TWRP and flash Magisk through TWRP.
marstonpear said:
You don't need to decrypt. You can install TWRP and flash Magisk through TWRP.
Click to expand...
Click to collapse
Thanks, already done it.
Flashed TWRP & Magisk without losing any data.
marstonpear said:
Hi,
Click to expand...
Click to collapse
will this metode also work on mi10
-fluffy- said:
will this metode also work on mi10
Click to expand...
Click to collapse
I'm not sure but probably not. Because Mi 10 is a MIUI device and this is an Android One. Still you gotta try to make sure, but the risk is all yours. Cheers.
marstonpear said:
Hi, I am writing this guide because many people followed other guides in the forum and lost their data. This is the proper way of unlocking the bootloader without losing your data.
0 - Read the whole guide before proceeding and proceed at your own risk!
1 - Make sure you have adb and fastboot installed on your device,
For Windows follow this guide (I suggest installing it system-wide, so that you can execute commands from every directory on your PC): https://forum.xda-developers.com/showthread.php?t=2588979
For MacOS and Linux : https://www.xda-developers.com/install-adb-windows-macos-linux/
2 - After the required tools are installed go to Settings -> About Phone on your phone and keep tapping on build number until a toast notification tells you that the developer settings are enabled.
3 - Go to Settings -> System -> Developer Settings and enable OEM unlocking option.
4 - Turn off the phone and when it's fully off, hold power + vol down button to boot into fastboot mode. When you've done this step successfully, you will see a blue FASTBOOT text on the screen with a bunny scrambling the internals of Android.
5 - Connect your phone to your PC and open a CLI/terminal/PowerShell window and type this but do NOT hit enter :
Code:
fastboot oem unlock
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again. This basically tricks the phone to boot into Fastboot mode instead of erase mode. To make sure the phone doesn't boot into erase mode on the next boot you need to do the following:
6 - While in fastboot mode type this into the CLI/terminal/PowerShell window but do NOT hit enter :
Code:
fastboot reboot
when you are ready to execute the command, start pressing only vol down button and then hit enter, HOLD vol down until the phone boots into fastboot mode again.
7 - Now you are ready to boot into your system. Either boot by holding power button or typing
Code:
fastboot reboot
into the terminal and hitting enter.
By rebooting twice, you make sure the phone doesn't boot into erase mode. If you flash the stock ROM beforehand and setup your device (login to Play Store), your device will still be Play Store certified by this method. But if you unlock the bootloader and the phone erases its storage, you won't be able to download apps like Netflix, because your device will not be certified by Play Store, this is because the Play Store checks for unlocked bootloaders. But by making it check the certification while it's locked and then unlocking the bootloader, you can make this issue go away. Feel free to ask for more proper guides for dummies, if you need. I have bricked my device many times and learnt by trial and error, so I'd be happy to make you avoid those same mistakes. Cheers.
Click to expand...
Click to collapse
Wowwww! Thank you very much, time ago I've unlocked the bootloader without losing any data
That's a very good solution