Database Info

[Q] OTA Update 2.2 has bricked my brand new ST?

So I just got my Shield Tablet today and of course I get notifications of OTA updates. I applied the first two (1.something and 2.1) just fine. Then the 2.2 update downloads and I tell it to install, which it starts to do. Little Android with his chest open shows up and the status bar does it's thing, then it reboots back to the nvidia boot image.... and hangs there. For over an hour I let it stay to see if it was doing some updating in the background, but nothing else happens. So I power it down by holding the power button, then turn it back on. Same deal. Stuck at the boot image.
Of course I'm not unlocked or rooted, so I only have the stock recovery. Any suggestions on how to resurrect this, or am I headed to customer support for an exchange?

Nastybutler said:
So I just got my Shield Tablet today and of course I get notifications of OTA updates. I applied the first two (1.something and 2.1) just fine. Then the 2.2 update downloads and I tell it to install, which it starts to do. Little Android with his chest open shows up and the status bar does it's thing, then it reboots back to the nvidia boot image.... and hangs there. For over an hour I let it stay to see if it was doing some updating in the background, but nothing else happens. So I power it down by holding the power button, then turn it back on. Same deal. Stuck at the boot image.
Of course I'm not unlocked or rooted, so I only have the stock recovery. Any suggestions on how to resurrect this, or am I headed to customer support for an exchange?
Click to expand...
Click to collapse
you need to unlock the bootloader

Daniele12 said:
you need to unlock the bootloader
Click to expand...
Click to collapse
I am facing the same problem after OTA 3.0 update.
I tried all methods of unlocking bootloader but couldn't.
Please help me if any new method of unlocking bootloader is available.

VijayBais said:
I am facing the same problem after OTA 3.0 update.
I tried all methods of unlocking bootloader but couldn't.
Please help me if any new method of unlocking bootloader is available.
Click to expand...
Click to collapse
Can you not get it to boot into the bootloader? (Press and hold Vol - and then press the power button)

Keithn said:
Can you not get it to boot into the bootloader? (Press and hold Vol - and then press the power button)
Click to expand...
Click to collapse
yes i can get into the fastboot mode.
But the point is that i couldn't unlock the device using "fastboot oem unlock" command.
Also USB Debugging is disabled, and cant boot inside android to enable it.

VijayBais said:
yes i can get into the fastboot mode.
But the point is that i couldn't unlock the device using "fastboot oem unlock" command.
Also USB Debugging is disabled, and cant boot inside android to enable it.
Click to expand...
Click to collapse
USB debugging isn't necessary, that's for ADB. What does it tell you when you try to use that command? Is it "waiting for device" ? I would check to make sure you have drivers for fastboot and that the shield is using them (sometimes it won't automatically load the proper driver).
Also, no custom recovery?

Keithn said:
USB debugging isn't necessary, that's for ADB. What does it tell you when you try to use that command? Is it "waiting for device" ? I would check to make sure you have drivers for fastboot and that the shield is using them (sometimes it won't automatically load the proper driver).
Also, no custom recovery?
Click to expand...
Click to collapse
It shows following unknown error
C:\Downloads\nv-recovery-image-shield-tablet-lte-row-update2_2_1\image>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 5.003s

I know this won't help VijayBais, but after a while I guess the stock kernel and everything settled in and it stopped random restarting and when I did restart, after installing apps and whatnot, it booted right back up. Now that I'm on 5.1, I haven't had any issues with it freezing up, or random restarts. Crisis averted.

VijayBais said:
It shows following unknown error
C:\Downloads\nv-recovery-image-shield-tablet-lte-row-update2_2_1\image>fastboot oem unlock
...
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 5.003s
Click to expand...
Click to collapse
Not sure what else to do. Is your recovery stock? Have you tried to do a factory reset then unlock?

Keithn said:
Not sure what else to do. Is your recovery stock? Have you tried to do a factory reset then unlock?
Click to expand...
Click to collapse
No, I haven't done any factory reset till now.
Even the recovery option doesn't proceed to further options on bootloader page.

You can't get into the recovery menu? When you chose it and get the dead android do you quickly tap the power+volume up combo?

How to save my media files from a bootlooping OnePlus One?

Hi,
I am totally lost and need help to get my personal data (images, videos most important) back from my bootlooping phone.
I browsed the privacy guard settings and disabled some boot and caller rights for google services and google play (with the intention to prevent it from looking up for updates constantly and drain my battery).
Then it restarted itself as I plugged it in for charge and is bootlopping since.
I have no root, the latest official CM update and a the build in Cyanogen recovery, since it came out of nowhere no usb bugging enabled (I believe).
When I try to enter the phone via ABD sideload from the CM Recovery "pull" my folders it says error:closed. adb backup wont work either.
It tells me: adb: unable to connect for backup: closed
This whole topic is kind a new for me - I never was in that situation and for now all I want is my images and videos back from my phone at least. I will try any method to save them.
I hope some can help me - I don´t know what to do anymore

This should theoretically work.
Flash TWRP by fastboot, then boot into this newly installed TWRP, then connect the device to your PC, as TWRP natively supports MTP, your Internal & External SD (If any) should be visible and you can copy your data over.

Thank you so much for this hint!
I will try that.
So I Just change my recoverer with this method right? This is possible without root and usb debugging?

Joshwin Aranha said:
This should theoretically work.
FlashTWRP] by fastboot, then boot into this newly installed TWRP, then connect the device to your PC, as TWRP natively supports MTP, your Internal & External SD (If any) should be visible and you can copy your data over.
Click to expand...
Click to collapse
It says:
writing recovery
FAILED (remote: Device not unlocked cannot flash or erase)
Is this game over?

Sore6 said:
It says:
writing recovery
FAILED (remote: Device not unlocked cannot flash or erase)
Is this game over?
Click to expand...
Click to collapse
Well no, it means your device has a locked bootloader, and you'll have to unlock it, the problem there is unlocking bootloader formats the device. Not always, but there's a good chance that you might lose your data, still thought give this a try,
fastboot devices (to confirm that your One is detected by the PC)
fastboot oem unlock (to unlock the device)
fastboot flash recovery recovery.img (to flash the recovery)
if this succeeds, disconnect the device and manually boot in to recovery, not to system, this is important because system will overwrite the TWRP with CYNGN recovery, so boot into recovery and try connecting your device to PC, see if MTP works.
PS - sorry for the late reply, i slept the whole sunday
EDIT - Wait, did you say that USB debugging is disabled ? then i think it might not work, give it a shot anyway tho.

Joshwin Aranha said:
Well no, it means your device has a locked bootloader, and you'll have to unlock it, the problem there is unlocking bootloader formats the device. Not always, but there's a good chance that you might lose your data, still thought give this a try,
fastboot devices (to confirm that your One is detected by the PC)
fastboot oem unlock (to unlock the device)
fastboot flash recovery recovery.img (to flash the recovery)
if this succeeds, disconnect the device and manually boot in to recovery, not to system, this is important because system will overwrite the TWRP with CYNGN recovery, so boot into recovery and try connecting your device to PC, see if MTP works.
PS - sorry for the late reply, i slept the whole sunday
EDIT - Wait, did you say that USB debugging is disabled ? then i think it might not work, give it a shot anyway tho.
Click to expand...
Click to collapse
Thanks for your help here - I guess I can´t win here with all my preconditions :/
One last question is:
Is there any method to wipe or flash the phone with a higher chance of keeping data even if little?

Try booting a recovery.img instead of flashing it.
Get the latest TWRP, copy the img file to the fastboot folder, enter fastboot mode and type fastboot boot twrp_file.img. It might work even with a locked bootloader.

Sore6 said:
Thanks for your help here - I guess I can´t win here with all my preconditions :/
One last question is:
Is there any method to wipe or flash the phone with a higher chance of keeping data even if little?
Click to expand...
Click to collapse
I was just about to say to try booting into the recovery, follow @nitrobg's instructions, get the recovery and instead of flashing the recovery, just try booting into it, command is
fastboot boot recovery.img
Hope it helps you, the pain of losing precious data isn't unknown to the best of us
EDIT - What caused the bootloop ? Who knows, maybe we manage to fix that

EDIT - What caused the bootloop ? Who knows, maybe we manage to fix that
Click to expand...
Click to collapse
I disabled some google play and google services from booting via the official cm privacy settings
Reason was to disable the battery drain by play when searching constantly for GOOGLE android updates...
Needed to disable that in cm12 back then and it helped.

nitrobg said:
Try booting a recovery.img instead of flashing it.
Get the latest TWRP, copy the img file to the fastboot folder, enter fastboot mode and type fastboot boot twrp_file.img. It might work even with a locked bootloader.
Click to expand...
Click to collapse
I will try that! Thank you.
I get back here with the result.

nitrobg said:
Try booting a recovery.img instead of flashing it.
Get the latest TWRP, copy the img file to the fastboot folder, enter fastboot mode and type fastboot boot twrp_file.img. It might work even with a locked bootloader.
Click to expand...
Click to collapse
Unfortunately it gives me this in the commandline:
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.430s

That's unfortunate.
Do you have adb access to your phone in the CM recovery? If you do, try removing/renaming com.google.android.gms from both system and data partitions. You might have to play around trying to get root or to remount the partitions but it could work.

nitrobg said:
That's unfortunate.
Do you have adb access to your phone in the CM recovery? If you do, try removing/renaming com.google.android.gms from both system and data partitions. You might have to play around trying to get root or to remount the partitions but it could work.
Click to expand...
Click to collapse
Sadly no - all adb commands end in "error:closed"

Try this:
Power Down the OnePlus One
Hold the Power Button Until Android Starts to Boot Up
As Soon as Android Starts Booting Up, Let Go of the Power Button
Then Immediately Start Holding Both the Volume Up and Volume Down Buttons
Continue Holding Both Volume Buttons Until Android is Fully Booted
If you did everything correctly, Android *should* boot up just fine and show "Safe mode" on the lower left corner of the screen.

nitrobg said:
Try this:
Power Down the OnePlus One
Hold the Power Button Until Android Starts to Boot Up
As Soon as Android Starts Booting Up, Let Go of the Power Button
Then Immediately Start Holding Both the Volume Up and Volume Down Buttons
Continue Holding Both Volume Buttons Until Android is Fully Booted
If you did everything correctly, Android *should* boot up just fine and show "Safe mode" on the lower left corner of the screen.
Click to expand...
Click to collapse
Didnt work because as far as i know one has to be in the android ui - hold pwer off key and then hold the restart menu item and then the volume buttons + power buttons code should work.
Thanks anyway - i wiped it now.
it works but all data is gone

Not really, you hold volume buttons while the OS is booting and it should force a safe mode boot with all apps disabled.
Well, too bad now. It could've worked.

nitrobg said:
Not really, you hold volume buttons while the OS is booting and it should force a safe mode boot with all apps disabled.
Well, too bad now. It could've worked.
Click to expand...
Click to collapse
Honestly - I held it for 4 Minutes. There was a Vibrate Signal everytime it wanted to boot up into android but it didnt. Then it kept the cynogenmod loader til the next little vibration. It was a loop with no entry to android GUI

It's sad that you had to lose your data
Anyway, Take a lesson from this, weekly nandroid backups
(That's what I do)

Joshwin Aranha said:
It's sad that you had to lose your data
Anyway, Take a lesson from this, weekly nandroid backups
(That's what I do)
Click to expand...
Click to collapse
Thanks man - jeah I took care of such case beforehand now and rooted, bought titaniuam backup and enabled usb debugging instantly...
Also I am now using TWRP.
Lesson learned.
Thanks to you all for helping me!
I am really thankful for your effort.
Kind regards

Some kind thanks on my replies maybe ?
Haha, anyway. Take care.

Nexus 5 Bootloop + No Power Button + Locked Bootloader + NO ADB -- Recover Data

Hey guys, so I have this dilemma on my hands. One of my friends has a Nexus 5 that has a power button issue. It seemed like a stuck power button, because even cleaning it did not solve the issue. So I removed the power button, and it finally turned on. However, it's now stuck in a Google logo bootloop.
The Objective:
To recover all data on the device. This is a must.
The Obstacles:
- No physical power button, but I can place a pair of tweezers on the terminals on the board to simulate a power button press.
- Bootloader is locked (I can unlock it, but that erases all data on the phone).
- Cannot enter proper stock recovery (I get a "no command" error when I do; I've tried all button combinations afterwards, including the ones from HERE, but to no avail).
- USB debugging was not enabled on the phone when booting normally, so even though the phone is recognized by my PC, I cannot do anything using ADB.
- Fastboot mode is the only successful mode I can reach on the phone.
The Final Question:
Does anyone know how I can successfully recover all the data on the phone using ADB or any other method, having the above obstacles?
Thanks in advance.

If you can reach fastboot without any problem, you can try to boot a custom recovery image using the following command : fastboot boot recovery yourcustomrecovery.img
(if you dont have a custom recovery, you need to flash one with : fastboot flash recovery yourcustomrecovery.img)
It will boot in recovery mode and, I hope, allow you to have an adb access and recover your data.
edit : since your bootloader is locked, i guess this won't work.

MrKhozam said:
Hey guys, so I have this dilemma on my hands. One of my friends has a Nexus 5 that has a power button issue. It seemed like a stuck power button, because even cleaning it did not solve the issue. So I removed the power button, and it finally turned on. However, it's now stuck in a Google logo bootloop.
The Objective:
To recover all data on the device. This is a must.
The Obstacles:
- No physical power button, but I can place a pair of tweezers on the terminals on the board to simulate a power button press.
- Bootloader is locked (I can unlock it, but that erases all data on the phone).
- Cannot enter proper stock recovery (I get a "no command" error when I do; I've tried all button combinations afterwards, including the ones from HERE, but to no avail).
- USB debugging was not enabled on the phone when booting normally, so even though the phone is recognized by my PC, I cannot do anything using ADB.
- Fastboot mode is the only successful mode I can reach on the phone.
The Final Question:
Does anyone know how I can successfully recover all the data on the phone using ADB or any other method, having the above obstacles?
Thanks in advance.
Click to expand...
Click to collapse
I bit of a trick. Try 'fastboot flash boot recovery.img' but instead of kernel flash twrp. After flash do a 'fastboot reboot'. It will boot recovery. Via twrp the pc will recognize phone as a media storage. You will not erase any data

icrunchbanger said:
I bit of a trick. Try 'fastboot flash boot recovery.img' but instead of kernel flash twrp. After flash do a 'fastboot reboot'. It will boot recovery. Via twrp the pc will recognize phone as a media storage. You will not erase any data
Click to expand...
Click to collapse
Thanks for the response, but the bootloader has to be unlocked for that to work, and while I can do that, it will wipe the data I need.

[GUIDE] How to unlock bootloader on Nokia 3

*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

[GUIDE] Unlock bootloader without losing user data.

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