Database Users

Stuck on Google Logo, Can't Unlock Bootloader

Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?

Durvid said:
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Click to expand...
Click to collapse
This is exactly why you should never mess with updates or flashing anything with a locked bootloader. If a factory reset doesn't fix it you're likely out of luck.

if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA

hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
I'll attempt this. Weirdly enough when I look at device info in adb it shows it as being on the newest version. But Yeah I'll attempt to flash what I was on before.
Yeah, I mean I've done this before with no issues on my Nexus 6 and there were no issues but that was unlocked when I got it. I just thought you didn't have to unlock the bootloader to sideload OTA's? I may be wrong.

hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.

Durvid said:
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Click to expand...
Click to collapse
You just said you had a nexus 6 unlocked, how did you not know the switch existed?

hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
akellar said:
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
Click to expand...
Click to collapse
I bought it used on /r/hardwareswap and whoever I got it from had already unlocked it.

I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?

Heisenberg said:
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Click to expand...
Click to collapse
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M

Durvid said:
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Click to expand...
Click to collapse
OK, but I need the name of the zip please.

Heisenberg said:
OK, but I need the name of the zip please.
Click to expand...
Click to collapse
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/

Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?

Heisenberg said:
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Click to expand...
Click to collapse
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/

Durvid said:
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Click to expand...
Click to collapse
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.

Heisenberg said:
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Click to expand...
Click to collapse
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.

Durvid said:
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Click to expand...
Click to collapse
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.

Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
Hilarious that the top comment is mine telling you why doing this is a bad idea

Heisenberg said:
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Click to expand...
Click to collapse
Yeah, I'll probably wait for the update over the air for a while and maybe if I feel reallly eager I'll just make sure I unlock and such. Annoying that you can't unlock via fastboot anymore without that toggle. I get that Google is trying to make Android super secure but It's not too useful for folks like us. Sure it's bricked a lot of devices.

akellar said:
Hilarious that the top comment is mine telling you why doing this is a bad idea
Click to expand...
Click to collapse
I've done it before with other devices. I wouldn't say it's inherently bad. It's just that there was one toggle that I wasn't aware of that caused the issue. You live and you learn.

THIS IS NOT MY IDEA !
I found this in a N9 thread and it worked according to the user with the issue, apply this with the correct t factory image ( do it with the version you have on your device not the one you tried to update to ! )
This might not work but its worth a try ! Before doing this read about ADB and Fastboot !!!!!!!!!!!!!!!! Try and understand the basics and know what the commands are doing to help backtrack e.C.t
If it does work - go to settings and allow OEM Unlock and USB debug !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Then go read from reputable sources how to flash images manually via adb !!!!!!!!!!!!!!!!!!!!!!!
I'd follow vomers guides.
Had this problem with another device cool thing to remeber is that on locked devices the only thing that is different is that there is a signature before the MAGIC header so the solution is to pull the android stock images from https://developers.google.com/android/nexus/images. Once done extract the images in both the zip and the tar that is inside the zip. You will see recovery.img inside the tar. One thing about the boot process of TWRP is that it enables adb in preboot meaning while in the boot loop you should have access to adb. With access to adb all you need to do is dd the images over the corresponding partitions: i.e.
PLEASE NOTE NOT FOR THE FEINT OF HEART. I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR DEVICE.
Quote:
adb push recovery.img recovery.img
adb shell dd if=recovery.img of=/dev/block/<recoverymmcblock>
I dont know if the default recovery has adb push update so id probably recommend doing this on every partition thats inside the tar, i.e. system, boot.

Getting Cyanogen on SM-G900F

Hi guys,
So yesterday I bought myself the Samsung Galaxy S5 (SM-G900F). Being very Linux friendly, I like having control over all my kit and my phone is no exception.
I've run into a few things that I don't quite understand with this phone...
First, whilst scouring the internet to try and install Cyanogen 13 on it I came across a few guides that say something like "After enabling developer mode (DM), enable OEM Unlock". When I go into DM and look for said "OEM Unlock", it's non-existant. Now after looking around a little more I then find out that this could be due to the bootloader already being unlocked and the best way to check is to go into "Download Mode" and see if it says so. I go into Download Mode and it says that the KNOX flag is 0x0 and so on but no "Bootloader Unlocked" or anything of the sorts.
What do you guys make of that?
Still, should I have a go at trying to unlock the bootloader? If so, how? If not, then when I attempt to try installing TWRP will it wipe all data on my phone? Or leave things alone until I actually want to install CM13?
With CM13, there's a number of versions for the S5. Is mine (SM-G900F) the "klte" version? It used to be EE (I'm in the UK) by the look of it, but was unlocked, does that matter?
If all else, something, god forbid, goes wrong either with flashing TWRP or CM13, can I revert back to Samsungs 6.0.1?
I know that's a lot of questions but I want to sort of have peace of mind before attempting to do anything as this phone was cheap, but not cheap enough to be turned into a paper weight.

If you have G900F just flash TWRP with odin, and then flash CyanogenMod 13. That is all. No play around bootloader unlock and bla bla bla. And yes there is no OEM Unlock option in G900F in devmode. So like I said, just flash TWRP with odin and install CM13. And when flashing TWRP you don't have data loss. Good Luck.

spiramedia said:
If you have G900F just flash TWRP with odin, and then flash CyanogenMod 13. That is all. No play around bootloader unlock and bla bla bla. And yes there is no OEM Unlock option in G900F in devmode. So like I said, just flash TWRP with odin and install CM13. And when flashing TWRP you don't have data loss. Good Luck.
Click to expand...
Click to collapse
OK, but what version of CM13 do I actually install? Is it the "klte" version?

Jamie_Edwards said:
OK, but what version of CM13 do I actually install? Is it the "klte" version?
Click to expand...
Click to collapse
klte from official cm site.

Unlocked bootloader of SM-G900f klte qualcomn
Is it true that the bootloader of samsung s5 is already unlocked
Jamie_Edwards said:
Hi guys,
So yesterday I bought myself the Samsung Galaxy S5 (SM-G900F). Being very Linux friendly, I like having control over all my kit and my phone is no exception.
I've run into a few things that I don't quite understand with this phone...
First, whilst scouring the internet to try and install Cyanogen 13 on it I came across a few guides that say something like "After enabling developer mode (DM), enable OEM Unlock". When I go into DM and look for said "OEM Unlock", it's non-existant. Now after looking around a little more I then find out that this could be due to the bootloader already being unlocked and the best way to check is to go into "Download Mode" and see if it says so. I go into Download Mode and it says that the KNOX flag is 0x0 and so on but no "Bootloader Unlocked" or anything of the sorts.
What do you guys make of that?
Still, should I have a go at trying to unlock the bootloader? If so, how? If not, then when I attempt to try installing TWRP will it wipe all data on my phone? Or leave things alone until I actually want to install CM13?
With CM13, there's a number of versions for the S5. Is mine (SM-G900F) the "klte" version? It used to be EE (I'm in the UK) by the look of it, but was unlocked, does that matter?
If all else, something, god forbid, goes wrong either with flashing TWRP or CM13, can I revert back to Samsungs 6.0.1?
I know that's a lot of questions but I want to sort of have peace of mind before attempting to do anything as this phone was cheap, but not cheap enough to be turned into a paper weight.
Click to expand...
Click to collapse

NO OEM unlocking with S off

I just bought a new Verizon HTC 10 that is S off. The bootloader is locked and I don't have an option to check the OEM unlocking, just isn't there.
download mode
*** LOCKED***
htc_pmewl PVT S-OFF
CID-VZW_001
Any idea on how I can get the OEM unlocking to show so I can unlock the bootloader?
The only thing I am not sure of is that there is no simm card yet. Do I need to have my simm card in to get the OEM unlocking to appear.

anderson96007 said:
I just bought a new Verizon HTC 10 that is S off. The bootloader is locked and I don't have an option to check the OEM unlocking, just isn't there.
download mode
*** LOCKED***
htc_pmewl PVT S-OFF
CID-VZW_001
Any idea on how I can get the OEM unlocking to show so I can unlock the bootloader?
The only thing I am not sure of is that there is no simm card yet. Do I need to have my simm card in to get the OEM unlocking to appear.
Click to expand...
Click to collapse
If its S-off already there is no need for the bootloader to be unlocked.

Thanks
Thanks for the help the reason I ask is because I thought I read that the bootloader has to be unlocked in order to root and install a custom rom. I've done this before but always started from a factory phone so getting one s off already is new to me.

anderson96007 said:
Thanks for the help the reason I ask is because I thought I read that the bootloader has to be unlocked in order to root and install a custom rom. I've done this before but always started from a factory phone so getting one s off already is new to me.
Click to expand...
Click to collapse
The 10 is a little different.
Locked and unlocked work basically the same, and it's my understanding it's suggested to be S-OFF locked from Sunshine crew.
I've been S-OFF locked since release of vzw S-OFF and everything works perfectly.
Hope this helps a little.

Just doesn't work
I have been trying for hours to get it to accept Supersu but it just doesn't. I flashed TWRP and when I try to flash Supersu it goes through the motions and says everything is OK but my phone never gets rooted. I was thinking of trying fastboot OEM unlock. I don't know how they achieved S off and read that may have something to do with it. I wanted to flash the new Venom ROM but maybe I will have to stick with TWRP and the stock ROM if I can't get it figured out. Thanks for your help so far I do appreciate it.
Steve

anderson96007 said:
I have been trying for hours to get it to accept Supersu but it just doesn't. I flashed TWRP and when I try to flash Supersu it goes through the motions and says everything is OK but my phone never gets rooted. I was thinking of trying fastboot OEM unlock. I don't know how they achieved S off and read that may have something to do with it. I wanted to flash the new Venom ROM but maybe I will have to stick with TWRP and the stock ROM if I can't get it figured out. Thanks for your help so far I do appreciate it.
Steve
Click to expand...
Click to collapse
I would leave the phone locked.
If you plan on flashing Venom, and you have already flashed twrp, there really is no need to root the current rom. Just make a backup of it in twrp (just in case) and flash Venom. Just make sure you select the correct firmware that matches the phones firmware in the aroma installer.

OK will give that a shot tomorrow thanks

If you're S-OFF. You shouldn't have any issues flashing the latest N firmware for your device, latest TWRP, and then latest N ViperROM. And since Viper comes pre-rooted, you will only need flash ViperROM.
Get a hold if you need some help, I'll do my best to assist.

Andy Bones in May I was asking you about flashing the Viper rom then got sidetracked. Now I would like to do it. I have an HTC 10 I bought that was already S off and locked. I installed TWRP 3.1.0.1 and my firmware is 6.0.1. I tried to flash Viper 10_5.9.0. I use the 6.0.1 button when asked which firmware I want to flash to although the 7. is already checked. Everything installs OK as far as the info page goes but when trying to restart the HTC start screen comes up and the phone just hangs. Reflashed backup and the phone is back to how I got it now. If you can tell me what I am doing wrong that would be great thanks.

anderson96007 said:
Andy Bones in May I was asking you about flashing the Viper rom then got sidetracked. Now I would like to do it. I have an HTC 10 I bought that was already S off and locked. I installed TWRP 3.1.0.1 and my firmware is 6.0.1. I tried to flash Viper 10_5.9.0. I use the 6.0.1 button when asked which firmware I want to flash to although the 7. is already checked. Everything installs OK as far as the info page goes but when trying to restart the HTC start screen comes up and the phone just hangs. Reflashed backup and the phone is back to how I got it now. If you can tell me what I am doing wrong that would be great thanks.
Click to expand...
Click to collapse
My HTC 10 is S-OFF Locked bootloader, this is what Sunshine crew suggests, and works the same (on the 10, previous devices are different) as unlocked bootloader.
It seems you are in a simple bootloop. Would need recovery log to see more, and Viper devs would be able to understand their stuff better than myself.
I do have suggestion as to what I would do.
You are on 6.0.1, you should update to the latest Nougat 2.41.605.18. Either by flashing the firmware, or flashing the RUU. Read up on encryption with Nougat.
Everything you said you did sounds correct to me. And as are as selecting the correct firmware in Aroma, that is for the fingerprint to work, and can easily be fixed if you accidentally select N instead of MM.
I hope this helps in some way.

Look and unlock bootloader with official method

In other posts there is procedure , for device with bootloader unlocked with unofficial method, for look and unlook officially, but is confused and in other arguments.
Is possible have this post for this argument, with clear guide , because I think is important question.
This maybe procedure:
1. miflash to official China Beta rom first. Flash without relock.
1b. Download from PC VPN app, install on phone and set connection to China. Then you are able to active usb developer options
2. re-lock bootloader with official China Beta rom. Flash and relock.
3. unlock bootloader again with official China Beta rom. Need to tie up with Mi account and insert a SIM card. For me, need to wait for 720 hours before MM3 can be unlocked. I checked chinese miui forum. This apparently is a new requirement. One full month later. Gosh...
4. miflash to official Global rom and stop there.
5. Do not re-lock bootloader with official Global rom""
I don't try this procedure......

What's the point of looking the bootloader just to get it unlocked again after whatever hours waiting!?
Do you experience problems with the device being unlocked unofficialy? Or this is just another "good advice/info" coming from MIUI forums...
Be happy somebody already took care of that and enjoy the unlocked bootloader freedom you get.

nijel8 said:
What's the point of looking the bootloader just to get it unlocked again after whatever hours waiting!?
Do you experience problems with the device being unlocked unofficialy? Or this is just another "good advice/info" coming from MIUI forums...
Be happy somebody already took care of that and enjoy the unlocked bootloader freedom you get.
Click to expand...
Click to collapse
The device comes unlocked but your Mi account has not permission to unlock this specific device because you never followed the official unlock procedure.
Xiaomi with its new policy does not let you use a Chinese version of a phone with a global rom and a locked bootloader. If you flash the global rom and for some reason the bootloader gets locked, your phone will stuck on the recovery with the following message "this miui version cannot be installed on this device", at this stage you must unlock the bootloader to be able to boot again, if the bootloader was unlocked officialy with you own account, you can use the mi unlock tool to unlock again and make the phone bootable, if the bootloader was unofficialy unlocked or unlocked by other account, in this case you can't unlock with the Mi unlock tool, you can't flash another rom since the bootloader is locked, you can't follow the official unlock procedure because you are stuck in recovery, the only solution is to use the test point method with EDL authorized account

Ok, I guess sounds reasonable for majority of the users.
But me personally? I could care less...
You can backup bootloader unlocked status and restore it if locked by accident...

panospc said:
The device comes unlocked but your Mi account has not permission to unlock this specific device because you never followed the official unlock procedure.
Xiaomi with its new policy does not let you use a Chinese version of a phone with a global rom and a locked bootloader. If you flash the global rom and for some reason the bootloader gets locked, your phone will stuck on the recovery with the following message "this miui version cannot be installed on this device", at this stage you must unlock the bootloader to be able to boot again, if the bootloader was unlocked officialy with you own account, you can use the mi unlock tool to unlock again and make the phone bootable, if the bootloader was unofficialy unlocked or unlocked by other account, in this case you can't unlock with the Mi unlock tool, you can't flash another rom since the bootloader is locked, you can't follow the official unlock procedure because you are stuck in recovery, the only solution is to use the test point method with EDL authorized account
Click to expand...
Click to collapse
But the procedure in first post, work in unofficial unlocked bootloader ?
If yes, after I am able to install global fastboot ROM when will be available ?

lucaxxaa said:
But the procedure in first post, work in unofficial unlocked bootloader ?
If yes, after I am able to install global fastboot ROM when will be available ?
Click to expand...
Click to collapse
My brother's Mi Max 3 came with unlocked bootloader, I just flashed china stable with clean and lock without problems.
I have seen some reports of bricked devices from people who tried to flash and lock, honestly, I do not know what went wrong in their case.
nijel8 said:
You can backup bootloader unlocked status and restore it if locked by accident...
Click to expand...
Click to collapse
Does this involves EDL mode?
As far as I know, EDL mode is locked on newer xiaomi devices.
Check this thread for more info https://www.reddit.com/r/Xiaomi/comments/98jr79/psa_a_potential_fix_for_flashing_in_edl_mode/

panospc said:
...
Does this involves EDL mode?
As far as I know, EDL mode is locked on newer xiaomi devices.
Check this thread for more info https://www.reddit.com/r/Xiaomi/comments/98jr79/psa_a_potential_fix_for_flashing_in_edl_mode/
Click to expand...
Click to collapse
It requires either root or EDL or TWRP...
And no, EDL is not locked, it's not Xiaomi's feature to lock it, it's Qualcomm business... MiFlash is locked which is irrelevant... Who needs their stupid front end when you can use Qualcomm tools...

nijel8 said:
Who needs their stupid front end when you can use Qualcomm tools...
Click to expand...
Click to collapse
Quote from the link a gave you
Users have been experimenting with older versions of MiFlash as well as Qualcomm's official flashing tool QFIL, but to no avail, they couldn't flash in EDL because the programs could not bypass the requirement for authentication.
Click to expand...
Click to collapse
Is this irrelevant?

panospc said:
Quote from the link a gave you
Is this irrelevant?
Click to expand...
Click to collapse
Maybe, we are not talking QFIL and flashing roms here. Will let you know when I get my Max 3 and test it.

your help is highly appreciated
panospc said:
The device comes unlocked but your Mi account has not permission to unlock this specific device because you never followed the official unlock procedure.
Xiaomi with its new policy does not let you use a Chinese version of a phone with a global rom and a locked bootloader. If you flash the global rom and for some reason the bootloader gets locked, your phone will stuck on the recovery with the following message "this miui version cannot be installed on this device", at this stage you must unlock the bootloader to be able to boot again, if the bootloader was unlocked officialy with you own account, you can use the mi unlock tool to unlock again and make the phone bootable, if the bootloader was unofficialy unlocked or unlocked by other account, in this case you can't unlock with the Mi unlock tool, you can't flash another rom since the bootloader is locked, you can't follow the official unlock procedure because you are stuck in recovery, the only solution is to use the test point method with EDL authorized account
Click to expand...
Click to collapse
that is exactly what just has happens with me few minutes ago.
I bought the MAX3 through Ali Express with "fake" global Rom, and open bootloader, however since the global ROM is officially released by Xiaomi so I was trying to flash it through XiaomiFalsh but, mistakenly, and unfortunately, I kept the tick mark on "clean all and lock" and now the phone is stuck on recovery, I called the service center of Xiaomi by they said since it is not officially announced in my country so it is not their baby and they asked me to contact the seller "who ali experess! no way!!"
guys who can help me to get out of this issue will be really appreciated, but keep in mind I'm not an expert.
awaiting your kindness

maherd said:
that is exactly what just has happens with me few minutes ago.
I bought the MAX3 through Ali Express with "fake" global Rom, and open bootloader, however since the global ROM is officially released by Xiaomi so I was trying to flash it through XiaomiFalsh but, mistakenly, and unfortunately, I kept the tick mark on "clean all and lock" and now the phone is stuck on recovery, I called the service center of Xiaomi by they said since it is not officially announced in my country so it is not their baby and they asked me to contact the seller "who ali experess! no way!!"
guys who can help me to get out of this issue will be really appreciated, but keep in mind I'm not an expert.
awaiting your kindness
Click to expand...
Click to collapse
Apply for unlock bootloader here: https://en.miui.com/unlock/
Wait time is 720 hours. No other way around it. Sorry, buddy.

opasha said:
Apply for unlock bootloader here: https://en.miui.com/unlock/
Wait time is 720 hours. No other way around it. Sorry, buddy.
Click to expand...
Click to collapse
There is no way to apply for unlock without a bootable phone, He must go to Developer options -> Mi Unlock status -> Add account and device but this is not possible because the phone is stuck in recovery.
The only solution right now is to use the test-point method to flash the chinese rom.

panospc said:
There is no way to apply for unlock without a bootable phone, He must go to Developer options -> Mi Unlock status -> Add account and device but this is not possible because the phone is stuck in recovery.
The only solution right now is to use the test-point method to flash the chinese rom.
Click to expand...
Click to collapse
Someone I helped fastboot flash China 8.8.9 mistakenly did this and was able to boot. Is Global rom entirely different in this situation?

opasha said:
Someone I helped fastboot flash China 8.8.9 mistakenly did this and was able to boot. Is Global rom entirely different in this situation?
Click to expand...
Click to collapse
Yes, it's different
chinese device + global rom + locked bootloader = stuck in recovery
Check my previous post here https://forum.xda-developers.com/showpost.php?p=77574305&postcount=3

panospc said:
Yes, it's different
chinese device + global rom + locked bootloader = stuck in recovery
Check my previous post here https://forum.xda-developers.com/showpost.php?p=77574305&postcount=3
Click to expand...
Click to collapse
Oh right, now I remember. This was that very big announcement. Completely forgot. Thanks for the reminder. Yes, then test point is the only option, unfortunately.
Again, this was why I urged people to steer clear of global and stick to Eu roms. More harm than good especially related to such situations (many new flashers accidentally locking bootloaders).

panospc said:
There is no way to apply for unlock without a bootable phone, He must go to Developer options -> Mi Unlock status -> Add account and device but this is not possible because the phone is stuck in recovery.
The only solution right now is to use the test-point method to flash the chinese rom.
Click to expand...
Click to collapse
Thank you so much guys for your feedback, for now I have the flowing questions:
1- the phone is stuck in recovery mode, how I shutdown the phone.
2- If I wait for Xiaomi to launch MAX3 officially in y country do you think they will be able to help me even with charged service?
3- can any of you expert guys direct me to some useful link to see how do it use the test-point method.
4- If I succeeded to unlock the bootloader through the test-point method, is it mandatory to flash the Chinese version or I can flash global Rom and keep the bootloader unlocked.
thank you in advance for your time.

maherd said:
Thank you so much guys for your feedback, for now I have the flowing questions:
1- the phone is stuck in recovery mode, how I shutdown the phone.
2- If I wait for Xiaomi to launch MAX3 officially in y country do you think they will be able to help me even with charged service?
3- can any of you expert guys direct me to some useful link to see how do it use the test-point method.
4- If I succeeded to unlock the bootloader through the test-point method, is it mandatory to flash the global Rom and keep the bootloader unlocked.
thank you in advance for your time.
Click to expand...
Click to collapse
1. Hold power and volume down until boots to fastboot mode, leave it and it should turn off automatically after few seconds.
3. You can find some information scattered to the following threads
https://en.miui.com/forum.php?mod=viewthread&tid=3667214
https://en.miui.com/thread-3765172-1-1.html
https://forum.xda-developers.com/mi-max-3/help/guess-somewhat-kinda-bricked-nitrogen-t3848922
https://forum.xda-developers.com/mi-max-3/help/help-mi-max-3-hard-bricked-anti-roll-t3834769
How to take apart Mi Max 3 https://www.youtube.com/watch?v=aQhhbzQ6l2s (check from 0:00 to 3:00 minute)
Click to expand...
Click to collapse
4. With the test-point method you can flash the chinese rom even if the bootloader is locked, after succesfully flashing the china rom you have to apply for official unlock, after getting the unlock permission you can flash global rom by leaving the bootloader unlocked.
XiaomiTool official page is proposing another solution but you need to wait for a global dev rom to be released and it is not guaranteed to work
If you get the message "this miui can't be installed on this device" and your device is bricked you might be able to recover it using xiaomiadb by first installing global developer and then installing china developer OF SAME VERSION (for example 8.8.16->8.8.16) using "xiaomiadb sideload_miui -otarom CurrentRom [ZIP_ROM_FILE]"
Click to expand...
Click to collapse

hello all, if someone can help me, i have my mi max3 with locked bootloader.
now i dont have any rom on it so trying to load a rom but getting an error ERASE is not allowed in locked state
what rom can i flash on it ?
tried to unlock bootloader via the tool, it gets stuck at 50% cannot verify phone.

had the same problem, was able to recover it with the test point method and flashing chinese rom, and switching to english language.
the procedure is described here:
https://androidfilebox.com/tips/edl-test-point-mode-redmi-note-4x/
the installation process of the qualcom drivers is special.
you have to open te backcover, which is very special too, dont forget to the 2 mini screws at the usb port and the drawer on the side . search and look on youtube.
look further, where the testpoints are on the mi max3
follow strictly the procedure, load and double extract the chinese rom for the mi max 3.
It is real work, and real danger that you break something mechanical, one shoud have a calm hand and a lot of patience, but for me all went good and the phone spang to live again.
Another solution could be this, but I have no experience with it:
https://s-unlock.com/productsandservices/server

[SM-G950W] Running official Android 9 on Samsung S8, help me understand my options (root, custom ROM)

Canadian SM-G950W Snapdragon Samsung S8 on Android 9 user here.
I've been reading a lot trying to figure out what I can do with regards to rooting & installing custom ROM. But the available info is confusing and contradicting.
Could anyone please answer my questions below?
1. Can I root S8 that is running Android 9?
I've tried naively to flash CF-Auto-Root with Odin , but got an error.
2. Knowing that bootloader is locked I thought I could downgrade to Android 7 and unlock the bootloader
Paid for SAMMOBILE firmware, but Odin failed to flash Android 7. Then I read somewhere that you CAN NOT downgrade Samsung phones. Is that the case?
3. What is the roadmap for flashing custom kernel, ROM and rooting SM-G950W Snapdragon Samsung S8 on Android 9?
At the end of my wits here... Thank you in advance!

temuri said:
Canadian SM-G950W Snapdragon Samsung S8 on Android 9 user here.
I've been reading a lot trying to figure out what I can do with regards to rooting & installing custom ROM. But the available info is confusing and contradicting.
Could anyone please answer my questions below?
1. Can I root S8 that is running Android 9?
I've tried naively to flash CF-Auto-Root with Odin , but got an error.
Click to expand...
Click to collapse
Use Magisk. Flash TWRP, then install Magisk in TWRP. This won't be possible if the bootloader cannot be unlocked
temuri said:
2. Knowing that bootloader is locked I thought I could downgrade to Android 7 and unlock the bootloader
Paid for SAMMOBILE firmware, but Odin failed to flash Android 7. Then I read somewhere that you CAN NOT downgrade Samsung phones. Is that the case?
Click to expand...
Click to collapse
Depends on the binary version, the screen text in Download Mode should tell you. You can't downgrade the binary, so if it changed from 3 to 4 (for example) and is currently on 4, you can only flash binary 4 firmware, but you can't downgrade to 3.
temuri said:
3. What is the roadmap for flashing custom kernel, ROM and rooting SM-G950W Snapdragon Samsung S8 on Android 9?
At the end of my wits here... Thank you in advance!
Click to expand...
Click to collapse
I'll try to put this simply:
Enable OEM unlocking in developer options
Unlock bootloader (wipes data)
Boot device, set up Google/Samsung account, connect to the Internet
Perform a manual update check, do not download update
Check to ensure OEM Unlocking is still visible
Put device in download mode and flash TWRP; immediately boot TWRP, do not allow device to reboot into system, otherwise it will restore the stock recovery
Make sure you flash the Multidisabler in TWRP to disable encryption and recovery restoration
Flash Magisk in TWRP to gain root
Boot into system and set up device, install the Magisk app to manage root.

I would leave it on Pie. Anything below that has nasty vulnerabilities like X helper.
If you want more performance optimize it with Package Disabler or adb edits.
If that doesn't get it, get a N10+, a huge performance and cam increase.
How to read Samsung build numbers

@V0latyle
> Use Magisk. Flash TWRP, then install Magisk in TWRP. This won't be possible if the bootloader cannot be unlocked
But the bootloaded IS locked on Android 9, thus Magisk/TWRP can't be installed. Or did I get something wrong?
And since @blackhawk just said to leave it on Android 9 - can anything be done at all?

temuri said:
@V0latyle
> Use Magisk. Flash TWRP, then install Magisk in TWRP. This won't be possible if the bootloader cannot be unlocked
But the bootloaded IS locked on Android 9, thus Magisk/TWRP can't be installed. Or did I get something wrong?
And since @blackhawk just said to leave it on Android 9 - can anything be done at all?
Click to expand...
Click to collapse
I heard that Extreme Syndicate for S9 series may seem nice. (OUDATED THOUGH TAKE EVERYTHING NOT FOR THE FAINT OF HEART.)

temuri said:
@V0latyle
> Use Magisk. Flash TWRP, then install Magisk in TWRP. This won't be possible if the bootloader cannot be unlocked
But the bootloaded IS locked on Android 9, thus Magisk/TWRP can't be installed. Or did I get something wrong?
Click to expand...
Click to collapse
Are you saying it can't be unlocked? Or simply that it is not unlocked?
The bootloader unlock has nothing to do with the Android version. Whether you can unlock it might though.
temuri said:
And since @blackhawk just said to leave it on Android 9 - can anything be done at all?
Click to expand...
Click to collapse
Blackhawk is a cranky old curmodgeon, don't listen to him. Totally kidding, he's a smart guy.
So let's focus on Step 1. Enable Developer Options, do you see the OEM Unlocking toggle?

@V0latyle
first of all, thank you for your time and patience.
nope, no such thing under Developer options. neither grayed out, it's just not there.

temuri said:
@V0latyle
first of all, thank you for your time and patience.
nope, no such thing under Developer options. neither grayed out, it's just not there.
Click to expand...
Click to collapse
Your device is set up, you have a Google account added, and you're connected to the Internet?

V0latyle said:
Your device is set up, you have a Google account added, and you're connected to the Internet?
Click to expand...
Click to collapse
that's correct.

temuri said:
that's correct.
Click to expand...
Click to collapse
Okay. Current firmware version?
Settings > About phone > Software information

Baseband version: G950WVLU8CUF3

temuri said:
Baseband version: G950WVLU8CUF3
Click to expand...
Click to collapse
Okay, so you're on the latest update. See if you can download and flash CSL1
If that works try AQD9
Next time you're in download mode, either take a picture of your screen or post what it says for SW REV or RP REV

consider downloaded - 6min left.

should I use standard ODIN to flash it?

Bad news but OEM Unlock does not exist on North American models. So you are out of luck unless you have a low bit number which then you can go to @afaneh92 for US/Canada Samsung BL unlocking

webhook said:
Bad news but OEM Unlock does not exist on North American models. So you are out of luck unless you have a low bit number which then you can go to @afaneh62 for US/Canada Samsung BL unlocking
Click to expand...
Click to collapse
uh-oh... can you please explain the "low bit" part and how do I check it?

@V0latyle
An attempt to flash CSL1 failed with:
FAIL! (Auth)
Complete(Write) operation failed

Disregard message

ouchies. was too quick and contacted the guy already

temuri said:
ouchies. was too quick and contacted the guy already
Click to expand...
Click to collapse
2023 SM-G950U/U1/W Rev8 One Click Root/Safestrap Inject Method
Root Method For S8 U/U1/W Series Phones Rev8 Bootloader New 1 Click Method Brought To Everyone By oakieville He provide this free of charge so If you like maybe give him a little donation Paypal email is [email protected] Before Starting...
forum.xda-developers.com
I've tried this with my T-Mobile US GS8+. Works like a charm. Since you are on Bit 8 the stuff there is compatible with your phone. However you may brick stuff so be careful
You can join their Telegram chat for more information.