Hi there,
Long story short, i've got BLA-L09 which was branded, i wanted to debrand it using a box, and I ended up without Enable OEM unlock option in devs options, and 0EXD build. None of the boxes i've got can perform anything more than "read info" (and it isn't full either) all the boxes respond that they either do not support chipset or security patch, even though i used same boxes to change vendor on some other BLA-L09 and it worked perfectly fine.
Phone doesn't have SD slot so i can't flash it this way, Firmware finder doesn't work either, it creates VPN server but phone can't find any uptades. I can't flash any custom recovery without enabled OEM unlock, but i can't enable because there is no option to do so. Any ideas what to do in this case?
Related
So, here's my cautionary tale of why jumping into things without research is a bad idea.
TLDR: Nougat Android Pay doesn't like unlocked bootloaders; locking the bootloader can be a bad idea, and IMEI restoration seems to work (at least, if it partially worked with IMEI 0)
I just upgraded to an A2017U from a Nexus 5 on Marshmallow, which had its bootloader unlocked, with SuperSu installed but root disabled and hidden, and Android Pay set up. All fine and dandy.
When I got my Axon 7, I thought it'd be a good idea to unlock the bootloader in case I needed to recover data, so using the Axon 7 Toolkit and some guides, that went just fine.
However, when I tried using Android pay, I found out that it didn't work on bootloader unlocked devices on Nougat, so I thought I'd just lock the bootloader again.
One "fastboot oem lock" later, I found myself in a world of trouble. The phone wouldn't boot, but at least I still had the stock recovery. Tried putting one of the EDL zips on an SDcard to see if it would flash. Nope.
Tried the Axon7Toolkit's EDL mode unbricker, but due to MD5 mismatches/missing files, it wouldn't take.
Tried Tenfar's official B07 EDL flash. Got "Error: Bad format" when I tried it after deleting the two files he mentioned, so somehow, I thought it'd be a good idea to add those files back in and try again. Nope.
Then I tried flashing the B15 EDL image. Somehow got dropped into "Factory Test Mode" and couldn't leave.
Then I flashed the B19 EDL image, which, finally got me back onto a working OS, with a locked bootloader.
At this point, everything connected fine, but I found out that my IMEI was 0 in both SIM 1 and SIM 2. Didn't think about it too much at the time, since everything worked, until I realized I couldn't receive any calls (placing them was fine). The culprit? Wi-Fi calling and VoLTE (on my carrier, T-Mobile) was on. Disabling those worked, but I realized that these technologies probably needed a valid IMEI to work.
Thus, it was time to go back into the business of unlocking bootloaders; I followed the GizDev guide to reprogramming IMEIs, which worked on the rooted, stock B19 image (the only thing the guide doesn't mention is that you need to manually install the 901D driver from device manager; it showed up in the list of already-installed drivers, probably from the XiaoMi flash tool installation).
Now, with the original IMEI back in place, I was elated to find out that Wi-Fi calling and VoLTE worked again! And now, here I am, exasperated yet excited, to have restored the functionality of my Axon before that fated "fastboot oem lock". Now, only if I could find a way to get Android Pay working again...
Use Magisk. If you want to stay stock you have to use an older version. Look at the version used by bad boyz.
I have the same problem that was the method he used to restore his image and helped me to thank infinitely
Hi all,
I have a P10 Lite that is running Nougat, EMUI 5.1. The phone displays the very ominous 'This phone has been unlocked and is therefore not secure' message at every boot. I would like to get rid of this message as we are putting it back on sale within the store and do not want to scare customers with this warning. I have the bootloader lock/unlock code but whether it is locked/unlocked, the message still appears AND OEM unlocking is greyed out in developer settings. Additionally after 'locking' it in fastboot, when put back into fastboot mode it still displayed as 'Phone Unlocked'. I have tried updating it through SD card but that did nothing. Is it basically stuck in this state now?
Just flash official firmware to replace bootloader.
Skyhuppa said:
Just flash official firmware to replace bootloader.
Click to expand...
Click to collapse
How can I flash if OEM unlocking is greyed out?
pandatechrma said:
How can I flash if OEM unlocking is greyed out?
Click to expand...
Click to collapse
I think flashing it original full firmware will work for you, whether OEM unlocking at settings has greyed or disappear. Ones the device drivers can be recognize by computer at this stage it should support full flash. That is why is always advisable to keep device full backup before tempering with it. Download the device original firmware online, use it supported flash tool and flash through computer.
Since you are also on sale point or shop, you can take same phone from shop if available, backup then restore the files to the OEM greyed phone.
But before performing full flash make sure you keep backup of exiting firmware, so that you can restore back when new firmware does not support your device.
I think flashing it original full firmware will work for you, whether OEM unlocking at settings has greyed or disappear. Ones the device drivers can be recognize by computer.
Check this link but follow all instructions and comments
https://forum-xda--developers-com.c...pilation-firmware-flasheables-huawei-t3736754
I bricked my device... Didnt flash both partitions I believe? Regardless after I unbricked using msm 2028 variant my oem unloick is now toggled off and greyed. Not quite sure if this might have been thew cause but I broke my screen ribbon cable connected on the logic board so I went to ebay to get a replacement. It came sim locked but with a unlocked bootloader. Before I tried flashing a custom ROM I rooted and unlocked my network without using the app provided by carrier (So device still shows locked in settings and APP but if I insert any sim the phone will read and activate on the network no issues) I flashed a custom rom and the network lock still shows locked but any sim card works HOWEVER OEM unlocking is now toggled off and greyed so I can not do anything with the bootloader and since I replaced the logic board I have a different IMEI than before and my old unlock.bin does not work. Is there a way to be able to activate oem unlocking again?
Go to your carrier, let them know. Inform of them of the new IMEI.
I swear there was another thread that used one of the debloat scripts from another O+ fone (the 7?) and axing one of the system packages enabled it (on other models, incl the N10 5G)... never tried it myself tho.
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
SM-T227U is an American model wich doesn't have the OEM unlocking option, you could unlock using unofficial ways but those are not pretty "stable".
coocooguy246 said:
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
Click to expand...
Click to collapse
Hey man! Still got your tab 7? I also have a SM-T227U and have oem unlocked! After doing the usual stuff, you will want to turn off automatically update in developer settings. After that, go to settings>General management>Date and time and select manual time and date, and set it for exactly 10 days before the day you attempt this. OEM unlock will appear in dev settings!!!
Then turn off device and while holding power up + power down, plug into PC. It will show the pre-download mode screen where it asks if you want to continue. Just follow the on screen instructions to unlock bootloader!
*note that the bootloader unlocking results in an unavoidable factory reset**
evan5935 said:
Hey man! Still got your tab 7? I also have a SM-T227U and have oem unlocked! After doing the usual stuff, you will want to turn off automatically update in developer settings. After that, go to settings>General management>Date and time and select manual time and date, and set it for exactly 10 days before the day you attempt this. OEM unlock will appear in dev settings!!!
Then turn off device and while holding power up + power down, plug into PC. It will show the pre-download mode screen where it asks if you want to continue. Just follow the on screen instructions to unlock bootloader!
*note that the bootloader unlocking results in an unavoidable factory reset**
Click to expand...
Click to collapse
Sweet! I will absolutely try this when I get home this afternoon, will report back with results!
But just for clarity. Let's say I start with a freshly wiped tablet. Go through set up and connect to wifi, do I need to add a Google and Samsung account? Then in dev settings, enable USB debugging, also enable wifi debugging? Then change the date. Is there any step I am missing?
coocooguy246 said:
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
Click to expand...
Click to collapse
If it has Mediatek chipset then you can use SP flash tool to format the tablet firmware and reflash it.
I would strongly recommend you to backup the NV DATA and NVRAM files before you format the tablet.
coocooguy246 said:
Sweet! I will absolutely try this when I get home this afternoon, will report back with results!
But just for clarity. Let's say I start with a freshly wiped tablet. Go through set up and connect to wifi, do I need to add a Google and Samsung account? Then in dev settings, enable USB debugging, also enable wifi debugging? Then change the date. Is there any step I am missing?
Click to expand...
Click to collapse
You can follow this guide actually! ( https://forum.xda-developers.com/t/...220-t225-install-lsposed-magisk-mods.4406933/) it recommends just skipping the setup junk
I have found that many times, rooting methods work across different models of the same device unless there are some sort of major differences in chipsets or some sort of random change lol
The only thing that doesn't seem to work for our model is section V of the guide which is for the removal of the "bootloader is unlocked" screen at startup. so you will still need to press the power button on that screen to boot up. It's a tiny hassle, but otherwise no big deal in my personal opinion
Make sure to read all the way to the end of the root section (section 4) and especially remember step 7. I retried probably 4 times and even patched the entire AP file of the firmware for use in odin (doing this gives a second warning on Knox screen that it isn't samsung official fw then boots normally into the bootlogo screen) before realizing everything was going fine.. I recommend just using the patched Magisk boot.img first just because I find it unsightly
Just flash the boot.tar in the AP slot. Don't download any of the boot imgs from the guide because they are for the t220's and t225's. I'll link the one I made according to the guide below. It'll save you some time and you won't need to install zarchiver and Magick just to have it factory reset again lol. Just download the latest Magisk apk (26.1) from the official github (https://github.com/topjohnwu/Magisk/releases) and install it when you have completed the 2nd factory reset/the patched boot img install.
Currently, RSA does not support XT2311-3 for unknown reason. However, I found a ROM for Tracfone, but the boot works with unlocked version.
Download: https://www.androidfilehost.com/?fid=10620683726822053015
MD5 60f8e629cbe7e969923c07538d6c3c7c
Bootloader unlock required. However, VPN disappeared after bootloader unlocked. You have to set up user account if you need VPN
Note: your phone is wiped during bootloader unlock process. Since RSA does not work with this phone at this time, you may not be able to rescue if something goes wrong.
Note: Titanium Backup does not work with Android 13. You need Swift Backup (pay $2.5 a year to use your choice of cloud service)
You should do it before initial setup. Wi-Fi connection and/or data connection needed for Magisk. Transfer the boot.img downloaded to your phone and patch it with Magisk, and transfer the patched boot back to host computer.
Now reboot the phone to bootloader or fastbootd
Code:
adb reboot fastboot
Flash patched boot
Code:
fastboot flash boot
Press space once, drag-and-drop the patched_boot onto command window, and press enter.
Post process:
Install the following as modules and you should install Fox's Magisk Module Manager
ADB fastboot
shamiko (you can setup Deny List but you don't have to enable because shamiko takes care of it)
Universal SafetyNet Fix 2.4.0
Systemless host within Magisk
liboemcrypo disabler is not required as it plays Netflix fine after these modules added, and it appears L1 on mine (good)
You can complete setup after root is done. Make sure you add Play Store and Play Services into Deny List as well as any app can detect root
How do you unlock the bootloader on this phone? When I copy & paste my device ID into the Motorola bootloader unlock page and click on "Can my device be unlocked" button, I get a message saying, "Your device does not qualify for bootloader unlocking".
dmw_4814 said:
How do you unlock the bootloader on this phone? When I copy & paste my device ID into the Motorola bootloader unlock page and click on "Can my device be unlocked" button, I get a message saying, "Your device does not qualify for bootloader unlocking".
Click to expand...
Click to collapse
Did you purchase your phone through Motorola directly?
I originally ordered a Moto G Stylus 5g (2023) from Amazon and tried several times to get the Motorola site to issue an unlock code. When I tried factory resetting this phone, I got a ROM not found error so I am returning this phone to Amazon. I then ordered a Moto G Power 5G (2023) directly from Motorola. My first attempt at getting an unlock code failed but I kept trying and finally was able to get through the process and now have the unlock code (sent via email).
When I tried to use fastboot to unlock the bootloader, I received this message "Check 'Allow OEM Unlock' in Android Settings > Developer Options". I have factory reset the Moto G Power 5g (2023) and am hoping the OEM Unlock option will be enabled soon. (If anyone has any 'tricks' on getting this Developer option enabled, please chime in)
If it helps, I used instructions from here: https://www.hardreset.info/devices/.../bootloader-moto-unlock-lenovo-motorola-root/
(They have a download for MFASTBOOT, which I did use but I am thinking the old FASTBOOT would work as well)
basixs_2 said:
Did you purchase your phone through Motorola directly?
I originally ordered a Moto G Stylus 5g (2023) from Amazon and tried several times to get the Motorola site to issue an unlock code. When I tried factory resetting this phone, I got a ROM not found error so I am returning this phone to Amazon. I then ordered a Moto G Power 5G (2023) directly from Motorola. My first attempt at getting an unlock code failed but I kept trying and finally was able to get through the process and now have the unlock code (sent via email).
When I tried to use fastboot to unlock the bootloader, I received this message "Check 'Allow OEM Unlock' in Android Settings > Developer Options". I have factory reset the Moto G Power 5g (2023) and am hoping the OEM Unlock option will be enabled soon. (If anyone has any 'tricks' on getting this Developer option enabled, please chime in)
If it helps, I used instructions from here: https://www.hardreset.info/devices/.../bootloader-moto-unlock-lenovo-motorola-root/
(They have a download for MFASTBOOT, which I did use but I am thinking the old FASTBOOT would work as well)
Click to expand...
Click to collapse
I got mine from Best Buy
Now there's a workaround for missing VPN
Get App Ops from Play Store and add sui (zygisk) module on Magisk
Check the list on App Ops and allow VPN on app needed
Moreover, Netflix works after USNF @Displax mod added, added Play Store and Play Services in Deny List, and Shamiko module added.
Mine shows L1 and Netflix (and cable TV app) work
basixs_2 said:
Did you purchase your phone through Motorola directly?
I originally ordered a Moto G Stylus 5g (2023) from Amazon and tried several times to get the Motorola site to issue an unlock code. When I tried factory resetting this phone, I got a ROM not found error so I am returning this phone to Amazon. I then ordered a Moto G Power 5G (2023) directly from Motorola. My first attempt at getting an unlock code failed but I kept trying and finally was able to get through the process and now have the unlock code (sent via email).
When I tried to use fastboot to unlock the bootloader, I received this message "Check 'Allow OEM Unlock' in Android Settings > Developer Options". I have factory reset the Moto G Power 5g (2023) and am hoping the OEM Unlock option will be enabled soon. (If anyone has any 'tricks' on getting this Developer option enabled, please chime in)
If it helps, I used instructions from here: https://www.hardreset.info/devices/.../bootloader-moto-unlock-lenovo-motorola-root/
(They have a download for MFASTBOOT, which I did use but I am thinking the old FASTBOOT would work as well)
Click to expand...
Click to collapse
I bought mine at Best Buy, but that shouldn't make any difference. It's the unlocked version for use on any carrier, so it should be bootloader unlockable.
I enabled Developer Options, but I noticed that "OEM Unlocking" is grayed out. When trying to Google this and find out why, I came upon a Lenovo forum where people were asking the exact same thing, and Lenovo's response was that the phone needs an Internet or Wi-Fi connection for 7 days before the "OEM Unlocking" option will become available(?!).
Now, I'm wondering if that's what's going on here, and why I'm getting the message that my phone isn't eligible for bootloader unlocking. I guess I'll see in a few days, LOL!
dmw_4814 said:
I bought mine at Best Buy, but that shouldn't make any difference. It's the unlocked version for use on any carrier, so it should be bootloader unlockable.
I enabled Developer Options, but I noticed that "OEM Unlocking" is grayed out. When trying to Google this and find out why, I came upon a Lenovo forum where people were asking the exact same thing, and Lenovo's response was that the phone needs an Internet or Wi-Fi connection for 7 days before the "OEM Unlocking" option will become available(?!).
Now, I'm wondering if that's what's going on here, and why I'm getting the message that my phone isn't eligible for bootloader unlocking. I guess I'll see in a few days, LOL!
Click to expand...
Click to collapse
I know this is weird.
Mine takes 7 days and it's on internet/SIM active
Back then my situation was more difficult because even RSA was not ready for the phone (it says not supported). I needed boot.img for rooting
I think I'm on day 2 of waiting... It's only on WiFi as I need the SIM for my old phone. Kind of frustrating that it's not a more immediate result/change.
Yesterday was 7 days from when I bought my Moto G Power 5G, and I checked it this morning - lo and behold, OEM Unlocking is available!
I don't understand the reasoning/desire behind Lenovo's wanting to impose this 7 day waiting period, but it is what it is. Time to {hopefully!} go unlock my bootloader.
dmw_4814 said:
Yesterday was 7 days from when I bought my Moto G Power 5G, and I checked it this morning - lo and behold, OEM Unlocking is available!
I don't understand the reasoning/desire behind Lenovo's wanting to impose this 7 day waiting period, but it is what it is. Time to {hopefully!} go unlock my bootloader.
Click to expand...
Click to collapse
Good Luck!!!
I'm still waiting (on day 5) but this is great to hear
basixs_2 said:
Good Luck!!!
I'm still waiting (on day 5) but this is great to hear
Click to expand...
Click to collapse
What a pain in the a$$!! I had to keep trying over and over before it would work. It worked the first or second time (gave me the option to get an unlock code), but I forgot to put it in bootloader mode, so I got an error. Then, I had to try multiple times before it would give me another chance to get the unlock code (kept telling me my device wasn't eligible for unlock). Finally got it unlocked, and then rooted!