Database Info

[guide] blu life xl (model: #l050u) [root / bootloader unlock / faq]

The BLU LIFE XL phone is an unlocked GSM platform device.
Currently there are absolutely no threads on the internet with information related to this device. I am not responsible for any damage done to your device, you assume sole responsibility for whatever you do to your devices. If you have questions, please reply to this or PM me, I'll be glad to help any of you!
================
Things you should know before you do anything listed in this post:
- Bootloader unlocking WILL ERASE USER DATA!!!!
- Successful root attempts disable OTA updates. (Unroot + Factory Reset MIGHT fix this)
- You must have OEM unlocking & USB debugging enabled in the developer menu.
- Common sense, don't flash anything you find on the internet randomly, you will cause irreparable damage, I learned that the hard way.
- Download & install the ADB Universal drivers & Android SDK tools (links @ bottom)
================
If you'd like to make a backup of your stock ROM, you can use romdump, it's a nifty tool that does exactly what it says, and it works on pretty much any rooted android phone. (yay) DL: http://d-h.st/ErS
- Download & extract to root directory of your sdcard.
- Open Root Browser (Or any file browser that's for rooted devices)
- Navigate to the path where you copied/downloaded romdump
- Move romdump to /data/local/
- Long press romdump and check all 3 rows of boxes above and press"OK"
- Open terminal emulator (or any equivalent terminal emulator app)
- Type "export PATH=/data/local/bin:$PATH"
- Type "su"
- Type "chmod 04755 /data/local/romdump"
- Type "/data/local/romdump"
- Wait until the process finishes, do NOT do anything with your device, set it down and leave it.
================
Rooting The Device:
- Have USB debugging, OEM unlocking & unknown sources enabled.
- Download & install the latest version of KingRoot.
- Swipe up three times, press "try it"
NOTICE: If your device restarts through the process, don't worry, your device isn't broken, but there's a good chance the root attempt failed.
================
Unlocking/Locking The Bootloader (THIS WILL ERASE ALL OF YOUR DATA!):
- Power off the BLU LIFE XL
- Hold down POWER + VOL UP until the phone turns on.
- Release POWER button, wait for the android to appear on your screen, it might say "No Command", in that case, just press the POWER button once to pull up the recovery menu.
- Use VOL DOWN to navigate down to "Reboot to bootloader" & Press VOL UP
- Plug your phone into your computer
- Navigate to your android SDK folder, and find fastboot. (If you don't have the android SDK downloaded, refer below)
- Type fastboot devices and see if your android device is recognized.
- Type "fastboot oem unlock"
- A menu should appear on your phone screen telling you about unlocking your phone, press VOL UP to unlock your bootloader, or VOL DOWN to cancel.
Alternatively, if you wish to re-lock your bootloader, follow these steps above, however type "fastboot oem lock" instead of "fastboot oem unlock"
================
FACTORY MODE & DEVICE TESTING MENUS:
- Power off BLU LIFE XL
- Press POWER & hold VOL DOWN until the phone turns on.
- Release grip of power button, whilst holding VOL DOWN.
================
Downloads:
Android SDK: https://dl.google.com/android/android-sdk_r24.4.1-windows.zip
ADB Universal Drivers: http://www.mediafire.com/download/uo3t409a9vz3kh3/adbdriver_v1.0.zip
KingRoot: https://androidmtk.com/download-kingroot-application
Romdump: http://d-h.st/ErS

My phone bricked while updating via OTA. It was a fresh L050U, so I don't know why it happened. The only existing stock firmware for repairing is behind a paywall, and I've only found a fw for L050L. Should I use them or what...?

redkvothe said:
My phone bricked while updating via OTA. It was a fresh L050U, so I don't know why it happened. The only existing stock firmware for repairing is behind a paywall, and I've only found a fw for L050L. Should I use them or what...?
Click to expand...
Click to collapse
I'm not sure what the differences are between the L050L & L050U. If you could provide me the ROM link, I'll peel through it and compare it to the dumped L050U rom that I have and get back to you.
By the way, I also replied to your comment on reddit.

TheDarknessz0rz said:
I'm not sure what the differences are between the L050L & L050U. If you could provide me the ROM link, I'll peel through it and compare it to the dumped L050U rom that I have and get back to you.
Really could use both those rom links. Can you guys help? rooted my phone and now OTA updates have been disabled.
Click to expand...
Click to collapse

blkkalel said:
TheDarknessz0rz said:
I'm not sure what the differences are between the L050L & L050U. If you could provide me the ROM link, I'll peel through it and compare it to the dumped L050U rom that I have and get back to you.
Really could use both those rom links. Can you guys help? rooted my phone and now OTA updates have been disabled.
Click to expand...
Click to collapse
The ROM I have dumped has personal applications and accounts integrated, I will get around to dumping a clean ROM for you guys soon.
Papa bless
Click to expand...
Click to collapse

BLU Life XL needs all that the mainstream devices have.
Thank you for the info above. It's such a shame this device has such limited info online. I'm not really a Noob, but also not close to a developer. How does one go about creating a custom recovery and a sweet ROM? Do you think you tube might have a how to that is on point or is there a spot here that we as users could request pros to check on it?

BLUE LIFE XL (L050U) has anyone else been successful using this root kit?
@do_root / TheDarknessz0rz, hey just wondering if the BLUE LIFE XL (L050U) you designed this tutorial for had a specific build that is needed to do this without bricking (like markressler/redkvothe whotf-ever did with his device)? In other words what was the build# of the L050U you designed this root process around? Just wondering man so I can get this done without any worries. I shouldn't have any issues using your root process on my BLU LIFE XL (L050u) Build: ALPS.L1.MP6.V2.15.2_6592.WET_P37 Custom Build version: BLU_L050U_V12_GENERIC, right? I've rooted every android device I've owned back to the original Droid1 without ever bricking during the flashing process. Just wondered if there might be a specific reason this other dude bricked his device.
Thanks in advance for even making a root kit for this device. Would appreciate any advice you have here.
-jim :fingers-crossed:
Edit: I'm ready to do this - just wanted to hear your feedback before I give it a rip.

@heatgap, I also have a L050U device. Where you able to unlock bootloader and root your BLU LIFE XL using the procedure desribed above? BTW, Thank you @TheDarknessz0rz
I am new at rooting, etc... Any additional steps you had to do? Or any advice you might give a rookie/noob to be able to get this done?
Many thanks!
Sisafokker

MOSTLY Stock images / Seeking assistance with recovery
Okay, I've dumped all of the raw images.
Most of them are stock, with the exception of system.img and recovery.img
recovery: insecure ADB, which really does no good until I can put together a custom recovery, or at least get a shell.
system: pre-rooted with SuperSU. Also, will NOT reflash recovery to stock on reboot.
Coming from stock, after you've backed up your user data (because it will be wiped), boot into fastboot mode.
Issue a "fastboot oem unlock-go" to unlock the bootloader. (This only has to be done once.) THIS WIPES EVERYTHING!
Then "fastboot flash system system.img" (This takes a while.)
After first boot and setup, download SuperSU from play store, install and update.
I'm working on putting together a working custom recovery, but I'm not an expert at this.

Succeded!!! Rooted device!
Following @TheDarknessz0rz initial post, plus some additional help from other posts (I am a noob, needed extra help) I was able to Root my Blu XL Life. Thank you @TheDarknessz0rz for you post, I took the liberty to expand on it in to make it more "Noob friendly" :
BTW, my Blu Life XL is:
Custom Build Version: BLU_L050U_V13_GENERIC
Android Version: 5.1
This is exactly what I did:
1 - Installed Android SDK on your computer: download the program, extract, Start the "SDK Manager" file and deselect everything except “Android SDK Platform-tools”)
2 - Power off the BLU LIFE XL
3 - Hold down POWER + VOL UP until the phone turns on.
4 - Release POWER button, wait for the android to appear on your screen, it might say "No Command", in that case, just press the POWER button once to pull up the recovery menu.
5 - Use VOL DOWN to navigate down to "Reboot to bootloader" & Press VOL UP
6 - Plug your phone into your computer with a USB cable. Your phone should indicate that the device is connected.
7 - On your computer, Navigate to your android SDK folder , open the "platform-tools" subfolder and Shift+Right Click on an empty area. Choose “Open a Command Prompt Here”
8 - On your computer, On the Command Prompt: Type "fastboot devices" and see if your android device is recognized.
9 - On your computer, On the Command Prompt: Type "fastboot oem unlock"
10 - A menu should appear on your phone screen telling you about unlocking your phone, press VOL UP to unlock your bootloader, or VOL DOWN to cancel.
11 - You should see on your computer´s command prompt "OKAY, Finished total time 20.4345 sec" (approx).
12 - Your phones screen should remain black, with a few rebooting options available. In my case, I had to type on the command prompt "fastboot continue" to make the phone reboot as the "volumen up or down" were not recognized when I pressed them on my phone.
13 - Phone will be hard rebooted. All data errased.
After you have successfully unlocked your Bootloader,
Download the Kingo Root and Root Checker apps
Run Kingo Root (I had to run it two times as the first time it rebooted when at 20% and it failed) and root the device
Run Root Checker to verify the device has been rooted.
CONGRATULATIONS, this is the first step.... read below.
Once your device has been rooted, then you need to:
1) Install Custom Recovery:
I was able to install a custom recovery on my device following a youtube tutorial: search on youtube for "CUSTOM RECOVERY TWRP PARA EL BLU LIFE XL" by Luis Robert (sorry, cannot post external links)
2) Update your SU Binary (you will be told about this when you open either SuperSu or Kingo Super User...
I had massive problems updating the SU Binary, tried 5 different methods but the only one that worked was this youtube tutorial: search for "How to Replace Kinguser KingRoot with SuperSU No PC" by Iron Tech. The tutorial was meant to replace KingoRoot by SuperSU, but in the process it updated my SU Binary (I spent at least a full day trying different methods that did not work for me)
In theory, now you can enjoy all the benefits and options that a rooted device provides...
Hope this helps
Thanks again for the help!
Cheers
Sisafokker

This is going to sound stupid, I screwed something up when I was editing a file in /system and now I'm in a boot loop. Also, when I went ot go try to download the raw stock roms images, the download would not initiate. Could you put the upload them somewhere else or is there anything that I can do with the stock recovery that could get me out? I also do not have like anything dumped or anything. L0051UU variant by the way. Thanks in advance

br21763 said:
This is going to sound stupid, I screwed something up when I was editing a file in /system and now I'm in a boot loop. Also, when I went ot go try to download the raw stock roms images, the download would not initiate. Could you put the upload them somewhere else or is there anything that I can do with the stock recovery that could get me out? I also do not have like anything dumped or anything. L0051UU variant by the way. Thanks in advance
Click to expand...
Click to collapse
I do not have any stock images, the images i have are for my device specifically, i'd have to rid the image of custom files first.

Okay, thanks I think I understand, but is there anything that you can think of that could help me in my situation? Or would I be best off contacting BLU?
Thanks again

br21763 said:
Okay, thanks I think I understand, but is there anything that you can think of that could help me in my situation? Or would I be best off contacting BLU?
Thanks again
Click to expand...
Click to collapse
well if you've got nothing to lose, I'd just try to flash the L050L firmware onto the device.

sisafokker said:
Following @TheDarknessz0rz initial post, plus some additional help from other posts (I am a noob, needed extra help) I was able to Root my Blu XL Life. Thank you @TheDarknessz0rz for you post, I took the liberty to expand on it in to make it more "Noob friendly" :
BTW, my Blu Life XL is:
Custom Build Version: BLU_L050U_V13_GENERIC
Android Version: 5.1
This is exactly what I did:
1 - Installed Android SDK on your computer: download the program, extract, Start the "SDK Manager" file and deselect everything except “Android SDK Platform-tools”)
2 - Power off the BLU LIFE XL
3 - Hold down POWER + VOL UP until the phone turns on.
4 - Release POWER button, wait for the android to appear on your screen, it might say "No Command", in that case, just press the POWER button once to pull up the recovery menu.
5 - Use VOL DOWN to navigate down to "Reboot to bootloader" & Press VOL UP
6 - Plug your phone into your computer with a USB cable. Your phone should indicate that the device is connected.
7 - On your computer, Navigate to your android SDK folder , open the "platform-tools" subfolder and Shift+Right Click on an empty area. Choose “Open a Command Prompt Here”
8 - On your computer, On the Command Prompt: Type "fastboot devices" and see if your android device is recognized.
9 - On your computer, On the Command Prompt: Type "fastboot oem unlock"
10 - A menu should appear on your phone screen telling you about unlocking your phone, press VOL UP to unlock your bootloader, or VOL DOWN to cancel.
11 - You should see on your computer´s command prompt "OKAY, Finished total time 20.4345 sec" (approx).
12 - Your phones screen should remain black, with a few rebooting options available. In my case, I had to type on the command prompt "fastboot continue" to make the phone reboot as the "volumen up or down" were not recognized when I pressed them on my phone.
13 - Phone will be hard rebooted. All data errased.
After you have successfully unlocked your Bootloader,
Download the Kingo Root and Root Checker apps
Run Kingo Root (I had to run it two times as the first time it rebooted when at 20% and it failed) and root the device
Run Root Checker to verify the device has been rooted.
CONGRATULATIONS, this is the first step.... read below.
Once your device has been rooted, then you need to:
1) Install Custom Recovery:
I was able to install a custom recovery on my device following a youtube tutorial: search on youtube for "CUSTOM RECOVERY TWRP PARA EL BLU LIFE XL" by Luis Robert (sorry, cannot post external links)
2) Update your SU Binary (you will be told about this when you open either SuperSu or Kingo Super User...
I had massive problems updating the SU Binary, tried 5 different methods but the only one that worked was this youtube tutorial: search for "How to Replace Kinguser KingRoot with SuperSU No PC" by Iron Tech. The tutorial was meant to replace KingoRoot by SuperSU, but in the process it updated my SU Binary (I spent at least a full day trying different methods that did not work for me)
In theory, now you can enjoy all the benefits and options that a rooted device provides...
Hope this helps
Thanks again for the help!
Cheers
Sisafokker
Click to expand...
Click to collapse
My device always returns status locked when I tell fastboot to dump the variables. I'm not sure why, bootloader unlock process says it's successful, however when it comes time to press VOL_UP to finish the process, none of the hardware keys are recognized, I've even issued fastboot continue from command prompt, yet the bootloader refuses to unlock. I'm going to try once more with "fastboot oem unlock-go" and see what happens from there.

TheDarknessz0rz said:
well if you've got nothing to lose, I'd just try to flash the L050L firmware onto the device.
Click to expand...
Click to collapse
Don't mean to sound so clueless but how would I go about doing that? I mean I couldn't find any firmware anywhere, even for other models so could you help me with that part? Also would I be flashing it from the "apply update from sd card" option on the stock recovery?
Thanks a lot

Never mind, I was able to figure out how to flash the system.img file onto my phone. Now it seems to be working perfectly. Thank you very much for all of the help and for uploading the img files, i really appreciate it.
Have a nice day

blu-life-xl Hard brick No problem !!!!!
blu-life-xl Hard brick No problem !!!!!
http://www.needrom.com/download/blu-life-xl-3g-l050l/
dont use the sp flash tool it has a virus only the img
download sp fflash tool from there own site

BLU download site
samgr said:
blu-life-xl Hard brick No problem !!!!!
http://www.needrom.com/download/blu-life-xl-3g-l050l/
dont use the sp flash tool it has a virus only the img
download sp fflash tool from there own site
Click to expand...
Click to collapse
Hey thanks for this link - - - - this site could help a lot of people
My phones backed up and i want to test the download file

hard brick NO! problem
Rickrocks013 said:
Hey thanks for this link - - - - this site could help a lot of people
My phones backed up and i want to test the download file
Click to expand...
Click to collapse
try it it works!!!!!!!!!!!!!!!!!!!:laugh:

How I downgraded from Pie to Oreo

This is how I downgraded from Pie to Oreo. I can't guarantee it works for everyone but it worked for me. It required an SD card and a computer.
This is not a guide for the android development savy users but for people who preferred oreo to pie. It works without an unlocked bootloader and an unrooted phone. You will have to wipe your data so backup everything beforehand!
STEP 0) Remove your google account from your phone so you can prevent it automatically updating to Pie on first boot. Go to Settings > Accounts and remove your google account from the phone.
1) First download the zips that include Oreo with the November security patch and the December security update. Put these in the root of the SD card and rename them so you remember which is which.
I have found November Oreo links for both TA1012 and TA1004 but reportedly they both work for all Nokia 8 phones as the main payload.bin file is the same. I used the TA1012 zip with my TA1012 phone.
THMSP said:
https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
Don't worry about the TA-1004 stuff, all Nokia 8 software is generic, only google makes a difference between the model IDs.
Click to expand...
Click to collapse
MD5: 07e5b0c46e86919a66d2e6279613047d
TeddyBeers said:
Rollback for TA-1012 from Pie Beta to Latest Oreo
Official link just captured a minute ago.
https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip
Click to expand...
Click to collapse
MD5: e00affc410525d63200c0c18bc8e0622
December Security update can be downloaded here (file is called NB1-488L-0-00WW-B01-488K-0-00WW-B01-update.zip):
https://tmsp.io/fs/xda/nb1/ota/
MD5: a8ed8cac0cf4dd7763f9dd0fb00971d5
2) Boot into recovery mode.
a) To do this on Pie, plug your phone into a computer and wait for the drivers to get installed. Windows 7 downloaded a few megabytes from windows update for this.
b) Unplug your phone and turn it off. Hold Volume up and plug your phone into your computer. Keeping holding volume up.
c) When the sad android appears with 'No command' showing, release Vol+. Hold the power button and press Vol+ to get into the recovery menu.
3) Use the Vol+ and Vol- to navigate down to 'Apply Update From SD card' click the power button to select it. In the next menu select the November Oreo zip file. It'll then verify the downloaded zip and install it. This takes a few minutes.
4) Select Wipe data/factory reset from the recovery menu. You need to do this cause data created on Pie doesn't work on Oreo.
6) Repeat steps 3 & 4 for the December security update. I don't know whether you need to factory reset both times but it shouldn't do any harm.
5) Finally select Reboot system now and it'll boot into Oreo. This takes a few minutes.
6) Don't connect to any wifi during setup. Go to settings > system > about phone. Tap the build number at the bottom until you unlock developer options. Go to settings > system > developer options and disable Automatic system Updates.
Hopefully this helps someone. Thanks to @THMSP, @TeddyBeers and @al mak for various posts that helped me downgrade and write this guide.

That's exactly the way to do it.
Actually works both ways as upgrade or downgrade, as Nokia kindly provides full rom oreo/pie instead of just incremental update.

Usb debug need to be enabled or not?

Setup updates from Android 8 back to Android 9 Again
Useful guide, thanks, but after downgrading from Pie to Oreo how do you avoid being forced to upgrade to Pie again in setup, after you Wipe data/factory reset the phone?
I downgraded back to Oreo from Pie, but when I restart in setup I get forced to search for updates and it finds, downloads and installs the Pie update again, and I dont seem to be able to avoid it?

Disable in Developer Options
nb111 said:
Useful guide, thanks, but after downgrading from Pie to Oreo how do you avoid being forced to upgrade to Pie again in setup, after you Wipe data/factory reset the phone?
I downgraded back to Oreo from Pie, but when I restart in setup I get forced to search for updates and it finds, downloads and installs the Pie update again, and I dont seem to be able to avoid it?
Click to expand...
Click to collapse
You have to enable Developer Options then disable Automatic system updates. You will always get the notification that a system update is available but it will not download automatically. Going further, you can even turn this notification off and forget about it.

The problem is that it happens before you get to a point where I know how to access the developer menu to do that.
It happens during the setup wizard, which I can't see how to complete without selecting a wifi network or mobile network, it then searches for downloads and installs the update before it sets up the phone and drops me at the home screen.

nb111 said:
The problem is that it happens before you get to a point where I know how to access the developer menu to do that.
It happens during the setup wizard, which I can't see how to complete without selecting a wifi network or mobile network, it then searches for downloads and installs the update before it sets up the phone and drops me at the home screen.
Click to expand...
Click to collapse
I've been having the same issue. I think it is new. I've done the process as early as January 9th with no forced update. As of yesterday it is forced. I've posted my experience in the thread for NOST. Pie may be life now because there are no custom ROMs and I expect all Oreo ROMs to have the force update thing inside them.

ululalbab said:
Usb debug need to be enabled or not?
Click to expand...
Click to collapse
Not as far as I am aware, though it might be needed if you are booting into recovery mode bia adb.

@nb111 @hodiedodie
Is it possible to either get through the entire setup without connecting to any network - you will have to forgo logging into a google account at first. Or only use mobile data in the hopes that google is smart enough to realise that people don't want to download 1.5GB on their data plans?

Optimus_Toaster said:
@nb111 @hodiedodie
Is it possible to either get through the entire setup without connecting to any network - you will have to forgo logging into a google account at first. Or only use mobile data in the hopes that google is smart enough to realise that people don't want to download 1.5GB on their data plans?
Click to expand...
Click to collapse
I doubt I'll do this myself but I would suggest doing a man in the middle attack on the phone with arpspoof in a Linux distro. Use Wireshark to see what servers it calls out to. Then I would go in my home WiFi router and block those IP addresses. Then reset the phone and connect to the WiFi network and see if that works.

Ok solved this one, had to Update to P remove the Google Account linked to the Device and downgrade again.
It's Part of the Factory Reset Protection that you cant skip the Wifi and Update Screens.

thanks a lot ，my ta1052 downgraded successfully use your 1004firmware

fushanhu said:
thanks a lot ，my ta1052 downgraded successfully use your 1004firmware
Click to expand...
Click to collapse
Do you still have dual sim support? All bands work as before downgrading with 1004 firmware?

jskamxmxm said:
Do you still have dual sim support? All bands work as before downgrading with 1004 firmware?
Click to expand...
Click to collapse
I didn't try out dua sim because i have only 1 sim and it works well . don't worry bro, any problem can be solved as long as you done downgrade，it's easy to unlock BootLoader under Oreo ，so you can flash your original official firmware use OST tool or NOST in case any issue . （i downloaded my TA 1052 firmware from google，but i didn't flash it because this 1004 so far no problem）
i downgraded because my battery drained very fast and phone became hot frequently ，but i cant find any other way to downgrade or unlock BootLoader under Pie ，the official unlocking method doesn't working with Pie. i unlock it successful after downgrading by flash this 1004 stuff .
There's a small surprise when flash 1004 firmware，it's showing failed:'version old ，not support downgrade' or something i dont remember，my phone off and stucked at starting log and can restart even holding power button 1 minute，so i thought it fu*ked and bricked，after some time i tried hold power and volume + button finally it switched off and in recovery mode i did factory reset and restart ，Oh sh*t ....... it's Oreo already ！！!
haha i wrote too much！

jskamxmxm said:
Do you still have dual sim support? All bands work as before downgrading with 1004 firmware?
Click to expand...
Click to collapse
thanks for reminding the dual sim，i think better to flash my 1052 firmware again，i'm not sure could there be any issue in future in case two sim in use

i have trouble please help me
My friend who hadn't elect Wipe data/factory when downgrade pie to oreo , so the phone can't open into system . Can't go through the Recovery too!
How can I do?

[email protected] said:
My friend who hadn't elect Wipe data/factory when downgrade pie to oreo , so the phone can't open into system . Can't go through the Recovery too!
How can I do?
Click to expand...
Click to collapse
Force shutdown the phone by keeping volume up, volume down and power pressed for some time (2 - 3 minutes). Then directly boot into recovery by holding down volume up while connecting the phone to the PC via. USB.

Optimus_Toaster said:
This is how I downgraded from Pie to Oreo. I can't guarantee it works for everyone but it worked for me. It required an SD card and a computer.
This is not a guide for the android development savy users but for people who preferred oreo to pie. It works without an unlocked bootloader and a rooted phone. You will have to wipe your data so backup everything beforehand!
1) First download the zip that includes Oreo with the November security patch and put it in the root of the SD card.
I have found links for both TA1012 and TA1004 but reportedly they both work for all Nokia 8 phones as the main payload.bin file is the same. I used the TA1012 zip with my TA1012 phone.
MD5: 07e5b0c46e86919a66d2e6279613047d
MD5: e00affc410525d63200c0c18bc8e0622
2) Boot into recovery mode.
a) To do this on Pie, plug your phone into a computer and wait for the drivers to get installed. Windows 7 downloaded a few megabytes from windows update for this.
b) Unplug your phone and turn it off. Hold Volume up and plug your phone into your computer. Keeping holding volume up.
c) When the sad android appears with 'No command' showing, release Vol+. Hold the power button and press Vol+ to get into the recovery menu.
3) Use the Vol+ and Vol- to navigate down to 'Apply Update From SD card' click the power button to select it. In the next menu select the downloaded zip file. It'll then verify the downloaded zip and install it. This takes a few minutes.
4) Select Wipe data/factory reset from the recovery menu. You need to do this cause data created on Pie doesn't work on Oreo.
5) Finally select Reboot system now and it'll boot into Oreo. This takes a few minutes.
Hopefully this helps someone. Thanks to @THMSP, @TeddyBeers and @al mak for various posts that helped me downgrade and write this guide.
Click to expand...
Click to collapse
hi everyone,
just now want to try downgrade Pie to Oreo, but struggling to entry the recovery mode.
i already 'success' to access "android sad - no command" but after that, when i press-hold vol up and power always going to home screen (android pie)
can you guys please advise what should i do?
should i unlockbootloader? i try with HMD unlock bootloader but error message "device not support"
fyi, i check on developer option, "OEM unlocking" still grey
also on my device manager, only appear "android composite adb interface"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thanks as so much for help

worked for me (downgraded from Pie, January 2019), thanks

I successfully rolled back to Oreo.
I wonder if removing the Google account before the rollback prevent you from rollback - install the forced updates - rollback again (I had to do it because I was forced to install the updates the first time, while the second one I had the possibility to skip the configuration)

Phone won't turn on, no system

I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.

zhou111 said:
I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.
Click to expand...
Click to collapse
1. Never boot into the system when there is a 'no OS' warning.
2. Use this TWRP next time (https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-twrp-3-3-1-proper-t3933531)
Does the phone charge or get detected by the computer when connected via USB?
If MiFlash doesn't seem to work try using ADB to Fastboot the ROM
If all hope is lost, the service centres can fix it.

Naveenthemi said:
1. Never boot into the system when there is a 'no OS' warning.
2. Use this TWRP next time (https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-twrp-3-3-1-proper-t3933531)
Does the phone charge or get detected by the computer when connected via USB?
If MiFlash doesn't seem to work try using ADB to Fastboot the ROM
If all hope is lost, the service centres can fix it.
Click to expand...
Click to collapse
when connected it is detected as qualcom 9008. I searched I think the phone is hardbricked, so can't enter fastboot. I think it can turn on and off. After holding power for 15 seconds, the usb is no longer detected. I could do the same to turn it back on. Do you know a service centre in Toronto?

Fcyrp Zip Need to Flash After Flash any Custom Rom
And Come in Telegram Official Group For Any Support of Redmi Note 7 Pro https://t.me/Rn7proGlobal

zhou111 said:
when connected it is detected as qualcom 9008. I searched I think the phone is hardbricked, so can't enter fastboot. I think it can turn on and off. After holding power for 15 seconds, the usb is no longer detected. I could do the same to turn it back on. Do you know a service centre in Toronto?
Click to expand...
Click to collapse
Yes it's hardbricked for sure! But are you sure MiFlash doesn't detect it?
If so any good service centre around you should be able to fix it, it's something to do with the software so they won't need Mi authorised parts...

Naveenthemi said:
Yes it's hardbricked for sure! But are you sure MiFlash doens't detect it?
If so any good service centre around you should be able to fix it, it's something to do with the software so they won't need Mi authorised parts...
Click to expand...
Click to collapse
Mi flash detects it as COM10 or COM20 depending on which USB. But when I flash I get error like no hello packet. Also I am not sure if I am suppose to put prog emmc sdm660 in the images folder or not.

zhou111 said:
Mi flash detects it as COM10 or COM20 depending on which USB. But when I flash I get error like no hello packet. Also I am not sure if I am suppose to put prog emmc sdm660 in the images folder or not.
Click to expand...
Click to collapse
Ok so Hello Packet errors are caused due to corrupted files or also if your flashing is interrupted in the middle
Try:
1. Making sure your PC isn't 32 bit
2. Draining out the phone battery and try again
3. Disabling driver signature enforcement(https://www.androidfoot.com/2016/08/how-to-disable-driver-signature.html)
4. An older version of MiFlash
5. If all of the above don't work ,try using another PC
6. Also make sure the USB ports are in working condition ( I think yours is working tho)

Naveenthemi said:
Ok so Hello Packet errors are caused due to corrupted files or also if your flashing is interrupted in the middle
Try:
1. Making sure your PC isn't 32 bit
2. Draining out the phone battery and try again
3. Disabling driver signature enforcement(https://www.androidfoot.com/2016/08/how-to-disable-driver-signature.html)
4. An older version of MiFlash
5. If all of the above don't work ,try using another PC
6. Also make sure the USB ports are in working condition ( I think yours is working tho)
Click to expand...
Click to collapse
My pc is 65 bit. I can't try #2 yet since it takes a while for battery to drain. I disabled driver signature enforce and using old mi flash and tried new pc still doesn't work. My boot loader is unlocked but maybe I accidently locked it? I don't know how to check.

zhou111 said:
My pc is 65 bit. I can't try #2 yet since it takes a while for battery to drain. I disabled driver signature enforce and using old mi flash and tried new pc still doesn't work. My boot loader is unlocked but maybe I accidently locked it? I don't know how to check.
Click to expand...
Click to collapse
Try this in ADB
(fastboot getvar all)
Without the brackets, now check for the unlocked line in the output and see if it shows yes or no
1. 64 eh, ok then no probs there
2. Oh ok take your time draining it
3. Try fastbooting the ROM via ADB see if that's works too

Naveenthemi said:
Try this in ADB
(fastboot getvar all)
Without the brackets, now check for the unlocked line in the output and see if it shows yes or no
1. 64 eh, ok then no probs there
2. Oh ok take your time draining it
3. Try fastbooting the ROM via ADB see if that's works too
Click to expand...
Click to collapse
I entered the command says waiting for device. how do you flash with adb?

zhou111 said:
I entered the command says waiting for device. how do you flash with adb?
Click to expand...
Click to collapse
Oh that means ADB isn't recognizing it.
There isn't much we can do if ADB doens't recognize it!
Did you look up for Service Centres?

zhou111 said:
I have a xiaomi redmi note 7 pro from china and I was planning on rooting it and changing the rom. Anyways I unlocked boot loader and installed twrp but couldn't install the rom using twrp recovery mode. Then I followed a video which rebooted the phone into recovery mode again after clearing some things. However, before rebooting it says no OS but the video did it anyways. In the video the phone rebooted back into recovery mode fine, but my phone does not boot. It constantly boots up to the redmi logo, flashes and boots again into redmi logo. This continues forever. I can, however, at this point enter fast boot. I thought the problem must be I have no rom so I just need to flash a rom. Using mi flash tool didn't work there was always some error and I turned the phone off. After turning the phone off, I cannot turn it back on again!!! Nothing, not holding power, not holding power + volume, just pure blank can't boot at all. I really don't know wtf I can do know it just doesn't turn on at all no matter what. Please help guys.
Click to expand...
Click to collapse
I had the same issue, but my phone went to fastboot from there I flashed it, the process was simple :
1. Download the fastboot rom and extract it (I guess two times, the first extraction extracts a file, open that with some extraction tool and uzip again, there you will see the fw with certain folders and images etc ).
2. Download the adb/fastboot zip file I"ll attach that here, extract it to the same folder where your fw files are. (fw = firmware).
3. You will find 3 bat files, flash all, flash all and lock, flash except storage, choose flash all (execute it).
4. Once done, reboot to recovery (stock), do a data wipe again.
This worked for me, hope it does for you too.
4.

hackeroid said:
I had the same issue, but my phone went to fastboot from there I flashed it, the process was simple :
1. Download the fastboot rom and extract it (I guess two times, the first extraction extracts a file, open that with some extraction tool and uzip again, there you will see the fw with certain folders and images etc ).
2. Download the adb/fastboot zip file I"ll attach that here, extract it to the same folder where your fw files are. (fw = firmware).
3. You will find 3 bat files, flash all, flash all and lock, flash except storage, choose flash all (execute it).
4. Once done, reboot to recovery (stock), do a data wipe again.
This worked for me, hope it does for you too.
4.
Click to expand...
Click to collapse
He/She said the phone doesn't boot into Fastboot either so that's very unlikely to work :-\

Pocophone F1 Flash Stock ROM with LOCKED bootloader and USB debugging OFF

*Note: Only tested with Pocophone F1 Global ROM, but might work with other Xiaomi phones since I used a xiaomi flashing tool.
This guide is intended for users who have not made any modifications requiring superuser priveleges.
Simply put, plain stock ROM.
This will or will not erase your data depending on the issue. (I had to erase mine though.)
This Guide is for users who have:
Boot Looped Pocophone F1
LOCKED bootloader
USB debugging OFF
Stock Recovery
My phone got into bootloop because I accidentally changed the DPI to 1000 ("Smallest Width" setting in Developer Options), which worked before, but was bugged in MIUI 11.
(full thread about this here: https://forum.xda-developers.com/poco-f1/help/help-pocophone-f1-t4084113)
This solution is only proven working for DPI bootloop in Pocophone F1. I think it might work on other units and other bootloop issues as well, since this process just flashes your phone to stock rom even with bootloader locked and USB debugging off.
Requirements:
1. Google account linked with the phone
2. Mi Account binded to devices
3. Stock Recovery (Mi-Recovery 3.0) ("Vol+" + "Power")
4. MiFlash Pro
5. Stock ROM
6. Steady Internet connection
Step 1. Download and install 15 seconds ADB installer by Snoop05.: https://forum.xda-developers.com/showthread.php?t=2588979
Step 2. Download MiFlash Pro: https://xiaomiwiki.github.io/wiki/Tools_for_Xiaomi_devices.html#xiaomiadb-by-francesco-tescari
It is preferred to Run the tool as administrator to not encounter any problems.
After installation, MiFlash Pro as admin.
Step 3. Get your official stock rom using MiFlash Pro. It has a ROM downloader built-in. There will be two search results for each version of your rom. Choose the one stated as RECOVERY. See image below for reference. I chose the latest rom because it is also the MIUI version I am currently using before bootloop. I read somewhere that downgrading bricks your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 4. Boot into Recovery Mode.
Press VOL+ and POWER buttons simultaneously. If your phone is bootlooping, just press VOL+ and it will go to recovery.
Select "Connect to MIAssistant"
Go to MiFlash Pro, click refresh. If IMEIs appeared, that means your phone is now detected. You can choose to Wipe Userdata first or Flash now.
Do not erase google account. I am not sure what will happen if you do, since FRP might need it.
a. Press Wipe User Data
Wait for process to finish.
b. Click Flash
*If Flash fails, click the button repeatedly until it works (This worked in my case.)
*Sometimes after pressing Wipe User Data, it automatically starts flashing as well.
Step 5. After finish flashing, your phone will boot up.
*In my first try I did not wipe userdata. The bootloop still persisted. So I really had to wipe userdata.
a. Connect to a network
b. Verify your Mi Account
c. If it asks for a PIN, it most likely won't work even if you know your pincode previously. (This happened to me)
-So you choose to log in to google account previously used instead.
Step 6. After this, your phone should boot up now. Cheers!
I recommend you to unlock your bootloader now and also to install custom recovery. That's what I did to no longer go through this hassle. I hope this guide serves it's purpose.

hey buddy.. i am going through the same problem...
BUT I DONT WANT TO LOOSE MY DATA.
I messed up with minimum screen width value in developers options on POCO F1.
It was 391 for my device and by mistake I did change to 3920 or something.
Which resulted to a complete black screen. This is the point where I sensed that I have messed up with that setting and tried to reboot my phone when I saw that the reboot, power off, etc options' buttons turned so so so much tiny that you barely can see them, and I could have missed them if I wasn't looking for the same.
Following that reboot attempt my phone is now stuck in boot loop.
It is getting rebooted continuously and automatically to recovery mode after showing the Poco logo..
1)The can be detected when connected to the laptop and
2)it is not unlocked.
Please help me out to get my phone working again.
And
I don't want to loose my data.
I DONT WANT TO LOOSE MY DATA.
I DONT WANT TO LOOSE MY DATA.
Please if there is any way to back up my data in this state and then flash the rom by your method.
and just a question that
Why does not MiFlash tools provide any option to recover or back up data before flashing a device?
Thank you.
VIJAY
[email protected]

Bro its not let me wipe user data it says wipe data failed and it disconnect my internal storage and connect it again with pc but not connect in miflash pro so for connect i need to disconnect phone and reconnect again to show my imei no on app

vijaym123 said:
hey buddy.. i am going through the same problem...
BUT I DONT WANT TO LOOSE MY DATA.
I messed up with minimum screen width value in developers options on POCO F1.
It was 391 for my device and by mistake I did change to 3920 or something.
Which resulted to a complete black screen. This is the point where I sensed that I have messed up with that setting and tried to reboot my phone when I saw that the reboot, power off, etc options' buttons turned so so so much tiny that you barely can see them, and I could have missed them if I wasn't looking for the same.
Following that reboot attempt my phone is now stuck in boot loop.
It is getting rebooted continuously and automatically to recovery mode after showing the Poco logo..
1)The can be detected when connected to the laptop and
2)it is not unlocked.
Please help me out to get my phone working again.
And
I don't want to loose my data.
I DONT WANT TO LOOSE MY DATA.
I DONT WANT TO LOOSE MY DATA.
Please if there is any way to back up my data in this state and then flash the rom by your method.
and just a question that
Why does not MiFlash tools provide any option to recover or back up data before flashing a device?
Thank you.
VIJAY
[email protected]
Click to expand...
Click to collapse
Hi VIJAY,
This actually is the only solution I have come up after trying also not to lose my data. I made this guide for people who also encountered the same issue, since there was no guide for it yet.
In my case, since there was no way of backing up data, I just started finding way just to get my phone back and running again.
aztigin009

mohd.fatmi said:
Bro its not let me wipe user data it says wipe data failed and it disconnect my internal storage and connect it again with pc but not connect in miflash pro so for connect i need to disconnect phone and reconnect again to show my imei no on app
Click to expand...
Click to collapse
Hey there. This actually happened to me as well. I just retried to wipe it again, and somehow it wiped the data after several tries.
Also in case you might ask, I didn't wipe my phone from stock recovery. I only wiped it from MiFlash Pro.
aztigin009

aztigin009 said:
*Note: Only tested with Pocophone F1 Global ROM, but might work with other Xiaomi phones since I used a xiaomi flashing tool.
This guide is intended for users who have not made any modifications requiring superuser priveleges.
Simply put, plain stock ROM.
This will or will not erase your data depending on the issue. (I had to erase mine though.)
This Guide is for users who have:
Boot Looped Pocophone F1
LOCKED bootloader
USB debugging OFF
Stock Recovery
My phone got into bootloop because I accidentally changed the DPI to 1000 ("Smallest Width" setting in Developer Options), which worked before, but was bugged in MIUI 11.
(full thread about this here: https://forum.xda-developers.com/poco-f1/help/help-pocophone-f1-t4084113)
This solution is only proven working for DPI bootloop in Pocophone F1. I think it might work on other units and other bootloop issues as well, since this process just flashes your phone to stock rom even with bootloader locked and USB debugging off.
Requirements:
1. Google account linked with the phone
2. Mi Account binded to devices
3. Stock Recovery (Mi-Recovery 3.0) ("Vol+" + "Power")
4. MiFlash Pro
5. Stock ROM
6. Steady Internet connection
Step 1. Download and install 15 seconds ADB installer by Snoop05.: https://forum.xda-developers.com/showthread.php?t=2588979
Step 2. Download MiFlash Pro: https://xiaomiwiki.github.io/wiki/Tools_for_Xiaomi_devices.html#xiaomiadb-by-francesco-tescari
It is preferred to Run the tool as administrator to not encounter any problems.
After installation, MiFlash Pro as admin.
Step 3. Get your official stock rom using MiFlash Pro. It has a ROM downloader built-in. There will be two search results for each version of your rom. Choose the one stated as RECOVERY. See image below for reference. I chose the latest rom because it is also the MIUI version I am currently using before bootloop. I read somewhere that downgrading bricks your phone.
Step 4. Boot into Recovery Mode.
Press VOL+ and POWER buttons simultaneously. If your phone is bootlooping, just press VOL+ and it will go to recovery.
Select "Connect to MIAssistant"
Go to MiFlash Pro, click refresh. If IMEIs appeared, that means your phone is now detected. You can choose to Wipe Userdata first or Flash now.
Do not erase google account. I am not sure what will happen if you do, since FRP might need it.
a. Press Wipe User Data
Wait for process to finish.
b. Click Flash
*If Flash fails, click the button repeatedly until it works (This worked in my case.)
*Sometimes after pressing Wipe User Data, it automatically starts flashing as well.
Step 5. After finish flashing, your phone will boot up.
*In my first try I did not wipe userdata. The bootloop still persisted. So I really had to wipe userdata.
a. Connect to a network
b. Verify your Mi Account
c. If it asks for a PIN, it most likely won't work even if you know your pincode previously. (This happened to me)
-So you choose to log in to google account previously used instead.
Step 6. After this, your phone should boot up now. Cheers!
I recommend you to unlock your bootloader now and also to install custom recovery. That's what I did to no longer go through this hassle. I hope this guide serves it's purpose.
Click to expand...
Click to collapse
i have a poco f1 with pixel experience and blocked bootloader, i can back to stock?

HeyImVitor said:
i have a poco f1 with pixel experience and blocked bootloader, i can back to stock?
Click to expand...
Click to collapse
Not quite sure on this one since i got bootloop whole on stock rom.
But this method just flashes stock rom on your phone.

My poco f1 is on MIUI 11 can I go back to 10 stable with this way ?. I'm newbie and noob. Thanks.

Hello!!
Mine Device doesn't get any OTA, it always shows that "No updates available ".
I'm currently running on MIUI 10.9.6.27.
I want to Upgrade to MIUI 12.
How could i do it ??
I tried to flash MIUI12 Rom but it throws error.
It says "Looks like current Android version is different from that in the recovery package"
Thanks in advance for help!!

Thank's for the guides, buddy:good::good::good:. It's really help me.
I have the similar condition:crying::crying::crying:; and my Pocophone's condition is...
1. Boot Looped Pocophone F1 (after update to MIUI 12)
2. LOCKED bootloader
3. USB debugging OFF
4. Stock Recovery
5. Wiped User Data: the data on my Pocophone has been wiped out
Buddy, i follow the steps in your guide, but i got stuck at step 4...
Because my phone was bootlooped, I only pressed the VOL + button in about 15 seconds....then the screen goes blank (no logo, just black screen)...
...So, I can't select "Connect to MIAssistant".:crying::crying::crying:
Then... I checked out via cmd (adb)... the messages appeared...
C:\adb>adb devices
92fc0fd2 unauthorized
I think it's not in recovery mode... Then I read again your guide slowly, word by word, step by step....and....I found something missing....
"...When do i have to plug the usb data cable...?"
...Then i tried to plug the usb data cable before running the Miflash Pro...
DO the steps in your guide again from step 4... Press and hold only the VOL + button until Mi Recovery mode screen appeared...
...And voila!... my pocophone was in recovery mode... now i was able to select "Connect to MIAssistant" button... :highfive: :highfive: :highfive:
Not waiting for long... then I go to the next step...
4.a. Press Wipe User Data -> Succeed
4.b. Click Flash -> Succeed
5. Flashed successfully. The phone booted up... then the phone still bootlooped...
--> Trying to enter Recovery Mode... then wipe user data via MiFlash Pro... after that... still bootlooped...
--> Trying to enter Recovery Mode... then wipe user data via MiRecovery... after that... still bootlooped...:crying::crying::crying:
Buddy,... please help me... !!!... :crying::crying::crying::crying::crying:

Same like above! Any solution?

Problem with installing a custom recovery (custom binary blocked by OEM lock)

I have bought a used Samsung S10e (SM-G970F/DS) it came with Android 12 and it was reseted.
My goal is to install iodeOS. Even if the iodeOS website says "Update the stock firmware to the latest" I considered the instructions from LineageOS and installed the latest Android 11 version, following this (https://iode.tech/en/iodeos-installation/#1629185391421-4cf1f5c8-d900) uninstall instructions.
After Android 11 was installed I enabled the developer options. OEM-Unlock was not available. Therefore I followed these instructions (https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/) and the OEM-Unlock was available again.
Now it seemed that everything is ready to install iodeOS or LineageOS. Therefore I followed this instructions (https://wiki.lineageos.org/devices/beyond0lte/install). It worked fine until "Installing a cutom recovery using heimdall"
after the "heimdall flash --RECOVERY <recovery_filename>.img --no-reboot" command the S10e shows a bar which is filled from the left to the right and then it shows "Custom Binary (RECOVERY) Blocked By OEM Lock"
Now I have no clue what to do :-(
I would be glad for any help.
​

You need to unlock the bootloader. You've toggled the OEM Unlocking switch, so unlocking the bootloader is the next step.
Make sure you have the Samsung USB drivers installed on your PC.
Turn off your device.
While holding the Bixby and Volume Down buttons, connect your phone to your PC.
The device should start in Download Mode. Hold down Volume Up until you get a warning about unlocking the bootloader. Unlocking the bootloader will wipe your data. Click Volume Up to confirm.
Your device will wipe data, then reboot. At this point, you can reboot to download mode and flash a custom recovery using Odin or Heimdall.

Thanks a lot for all your help!
The problem was I entered the download mode by the adb command "adb reboot-bootloader" and this mode seems to be different to the one which can be accessed by pressing the keys.
Now everything worked fine

I have exactly the same problem here:
SM-A205G with OEM Unlock enabled
There is no unlock bootloader in the bootloader no option anymore
at least in the bootloder of this edition
And I suppose that if it is the bootloader that flashes everything, it is COMPLETELLY LOCKED, could be jailbroken by some new method, but until them... no option :sad:
V0latyle said:
You need to unlock the bootloader. You've toggled the OEM Unlocking switch, so unlocking the bootloader is the next step.
Make sure you have the Samsung USB drivers installed on your PC.
Turn off your device.
While holding the Bixby and Volume Down buttons, connect your phone to your PC.
The device should start in Download Mode. Hold down Volume Up until you get a warning about unlocking the bootloader. Unlocking the bootloader will wipe your data. Click Volume Up to confirm.
Your device will wipe data, then reboot. At this point, you can reboot to download mode and flash a custom recovery using Odin or Heimdall.
Click to expand...
Click to collapse

It seems that this <confirm> option in the bootloader is being removed by samsung, so... even if unlock oem is enabled... it will not work...
I can only reach the bootloader by going to recovery mode them selecting reboot bootloader, or by adb reboot bootloader, but it boots directly in download mode without the option to long-press volume up key
A flasher that doesn't flashes doesn't makes sense. Maybe samsung have hidden something new in there?...

Ok. I've found the solution
1 - Power the phone off
2 - Hold both volume up and down
3 - PLUG THE USB BUTTON WHILE YOU HOLD BOTH these buttons
4 - NO NEED TO PRESS POWER BUTTON
I guess this will work for all phones that don't have the option to start with power+down
Yes. A flasher that does not flash don't exists.
Good luck ! \o/
source:
HELP!!! Custom Binary (BOOT) Blocked By OEM Lock
Hi there, I've been having trouble rooting my Samsung Galaxy A20 - SM-A205GN for awhile now. I'm officially on Android Version 10 with One UI Version 2.0, I've followed the provided guide to root my device but it fails on Odin "all versions" when...
forum.xda-developers.com

wavedevice said:
Ok. I've found the solution
1 - Power the phone off
2 - Hold both volume up and down
3 - PLUG THE USB BUTTON WHILE YOU HOLD BOTH these buttons
4 - NO NEED TO PRESS POWER BUTTON
I guess this will work for all phones that don't have the option to start with power+down
Yes. A flasher that does not flash don't exists.
Good luck ! \o/
source:
HELP!!! Custom Binary (BOOT) Blocked By OEM Lock
Hi there, I've been having trouble rooting my Samsung Galaxy A20 - SM-A205GN for awhile now. I'm officially on Android Version 10 with One UI Version 2.0, I've followed the provided guide to root my device but it fails on Odin "all versions" when...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, you don't unlock the bootloader VIA the bootloader in Samsung phones.

so you know what happened? I accidentaly reset my phone! I have gone into download mode and there was additional choices: to unlock bootloader holt volup, so I did, then again to confirm unlocking press volup. I did so and then there was for a brief moment android logo and "erasing" and then after about 2 minutes of just Samsung logo phone restarted and asked me to perform setup as it was new! WTH? There was nothing mentioned about deletion

DaHansi said:
I have bought a used Samsung S10e (SM-G970F/DS) it came with Android 12 and it was reseted.
My goal is to install iodeOS. Even if the iodeOS website says "Update the stock firmware to the latest" I considered the instructions from LineageOS and installed the latest Android 11 version, following this (https://iode.tech/en/iodeos-installation/#1629185391421-4cf1f5c8-d900) uninstall instructions.
After Android 11 was installed I enabled the developer options. OEM-Unlock was not available. Therefore I followed these instructions (https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/) and the OEM-Unlock was available again.
Now it seemed that everything is ready to install iodeOS or LineageOS. Therefore I followed this instructions (https://wiki.lineageos.org/devices/beyond0lte/install). It worked fine until "Installing a cutom recovery using heimdall"
after the "heimdall flash --RECOVERY <recovery_filename>.img --no-reboot" command the S10e shows a bar which is filled from the left to the right and then it shows "Custom Binary (RECOVERY) Blocked By OEM Lock"
Now I have no clue what to do :-(
I would be glad for any help.
​
Click to expand...
Click to collapse
I had the same problem on my samsung tab a10.1. That's why I had to flash the stock firmware 3 times. Every time I flashed twrp with odin, I got the error (custom binary blocked by oem lock).
I write what they should do in order.
1. Turn on the phone.
2. Open Developer mode
3. USB debugging mode - on
4. oem unlocking - on
5. then turn off the phone and disconnect from usb
6. Connect the phone to the PC with USB by holding down the volume up and volume down buttons at the same time. WITHOUT PRESSING THE POWER BUTTON
7. Press and hold the volume up button according to the instructions in the pop-up window.
oem unlocked

Sorry that, I had another problem. May I know how to unlock the OEM if my S10e phone can't turn on.
My device always on "samsung" display page, can't open to index. Do you know this issue? Expecting your reply.

Hi! I have the same issue on my Xiaomi Mi 11 Pro (It was Chinese) but it came unlocked with xiaomi.eu rom.
After i installed a global rom, and google wallet nfc pay did not work, so i thought okay i will lock it then so maybe wallet would accept it, (with the eu rom it worked before) so i put the device in fastboot and used fastboot oem lock on cmd...
And from then it stucks on miui recovery 5.0 screen, and says, this miui version can't be installed on this device...
I might not enabled oem unlocking before i shut if off, but i added it to my mi account so i dont know if after a week i can maybe unlock it. But i think the other possible solution would be to sideload the original chinese stock rom, which is for M2102K1AC, Mi 11 pro, codename mars, but i couldn't find it anywhere... If someone can upload a link to it, that would be a huge help! Or any idea! thx!

geraldmany said:
HI! i got a mi 11 pro 1 year ago, and it was offically chinese, but it came unlocked with Xiaomi.eu firmware, but i could't update it via the updater app, so i searched and found the global star version and just flashed it, everything worked, only now google pay nfc didnt work, it said that its probably because of the unlocked bootloader, so i got to fastboot and in cmd i sent fastboot oem lock, and since then my phone is stuck in miui recovery 5.0 screen and says that i cannot run this firmware on the device, i tried to unlock it but failed, maybe after a week, but i think that i didnt turn on oem unlocking on the phone itself before this... So im just hoping that after a week unlocking could be done... Or my other idea is, that i could install the original chinese rom with sideload, because i managed to install another global version on it since, but the result is still the same, the only problem is that i cannot find literally anywhere a mars codenamed firmware...
Click to expand...
Click to collapse
Anyone who might have the same situation, i found a simple, but effective solution, not sure if it works on every xiaomi device, but i will write down the steps here:
You need to use XiaomiADB, here is the download link and the description for how to use it -> https://xiaomiui.net/how-to-use-xiaomiadb-8044/ (if the page is not available, then feel free to msg me!)
For xiaomi adb, you need to go to 3rd option on the miui recovery screen, NOT THE FASTBOOT
So basically i went through the steps to “xiaomiadb sideload_miui <filename>”
And I tried to install a rom, BUT IT DIDNT ACCEPT IT!
The message was:
ERROR: This rom cannot be installed, server code -> 2001, server message -> Can't install unofficial rom
after trying 4 times all the same and: Installation of this rom via stock recovery is not allowed by Xiaomi
Says Installation failed, and then i just decided to download another rom so i PLUGGED OUT THE PHONE right after this, and went to another room to connect to wired network, to download and try a different rom... when i came back, to all my surprise, the phone was turned on, so i went to the setting dev ops and enabled bootloader unlocking, linked it to my account enabled adb and everything that is needed to flash another rom later, so then i rebooted and again, miui recovery 5.0 screen, but now i enabled unlocking, so i put the phone in fastboot, and tried MI UNLOCKER TOOL again, now it says: Please unlock 168 hours later. And do not add your account in MIUI again, otherwise you will wait from scratch.
So that means, after 7 days i wll be able to unlock it, until then, i can turn it on with the above method, in short try to sideload (copy and install) a rom to it, and then after it failed, plug it out and just wait like 10-20 maybe 30 seconds and bam your device is normally booted... I hope it helps to some of you, (i have been searching for the solution for almost a week, my other option was to pay someone who can MAYBE do it or send the phone back to china and pay the repairs, so im really happy with this method! If it helps to you, please reply so i and the others will know that it worked! Have a nice day!