Related
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
I had the same issue you don't need to toggle the option on marshmallow. The error looks like you need to do a sudo fastboot if your using linux.
The only other thing to remember is you need to remove the factory reset protection (frp) see here http://forum.xda-developers.com/honor-5x/help/unlock-bootloader-issues-kiw-t3411032
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
Just because that option is not available does not mean your bootloader is locked, plus you can unlock using ADB.
Just enable usb debug only
Sent from my KIW-L24 using XDA-Developers mobile app
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
This option is not there in Marshmallow. not sure if there is still a way to unlock as this option itself is not there...try enabling USB debugging couple of times and see if it prompt you for authorisation. if it does, you can still do the required things.
did u unlocked bootloder???
did u unlocked bootloder???
i m having same problem
princereshim said:
did u unlocked bootloder???
i m having same problem
Click to expand...
Click to collapse
What problem?
no oem unlock option
no oem unlock option
in developer option
princereshim said:
no oem unlock option
in developer option
Click to expand...
Click to collapse
If you are in lollipop it will be there but if u r on marshmallow then it wont be there. Just enable usb debugging and you r good to proceed.
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
How did u get the unlock code on KIW-L22 model because i have tried i dont know how many time but the emui website return me error that either model number is wrong or the verification code
Harsh007agrawal said:
, I always get stuck at
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
How did u get the unlock code on KIW-L22 model because i have tried i dont know how many time but the emui website return me error that either model number is wrong or the verification code
Click to expand...
Click to collapse
Try Chinese site to get same.
And which rom are u sing could you give me link to latest twrp and rooting files needed
Harsh007agrawal said:
And which rom are u sing could you give me link to latest twrp and rooting files needed
Click to expand...
Click to collapse
See the pinned post in the guides tab... It has all the information and links
Sent from my KIW-L21 using Tapatalk
im also getting the same problem. it does not recognize device.. im on stock marshmallow and there is no option of oem unlock
Harris Aamir said:
im also getting the same problem. it does not recognize device.. im on stock marshmallow and there is no option of oem unlock
Click to expand...
Click to collapse
Just enable the usb debugging if you r on stock mm. Try changing the usb port amd see if it work
seams rolling back is the only solution ! .
Romiui said:
seams rolling back is the only solution ! .
Click to expand...
Click to collapse
Why what happened?
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
I cant find mine either, but i have a suspicion that they just removed/edited the files to just have one state of locked and no controls or commands to unlock it.
Find out the file name and path for the "OEM unlock" setting in the developer options.
then search for it using the ADB, if the files aren't there then you might need to put the phone in to download mode and "sideload" the the full files back on to it.. if it's possible.
it might be more complicated than that. that's what i would've done as a Carrier if i wanted to keep modders and phone thieves out.
also on my Carrier phone when i put it into Download mode it seems to run like there own unlock before it does anything else, might need to run that first to unlock the lock so you can unlock it...
this is kind of a BS response, but at least it's an idea to look into. Sorry.
also you could try loading PDANet to see if the device will recognise.
Tamoghna Chowdhury from Android.stackexchange TOO NEW CAN'T POST LINKS said:
To unlock the boot loader you need to have the ADT with all the packages installed and configured.
Later once the configuration is done properly then you can connect your device and enable USB Debugging under the options.
Download Modaco’s Superboot files and save them to your computer.
Once downloaded, extract it by right clicking and extract all.
On your phone, click on Settings > Developer Options > Turn USB Debugging On.
Plug the device in to your computer via USB cable.
Open the superboot folder that we just extracted (until you see the folder with fastboot-windows inside it), then hold the shift key down on your computer and right click any blank area.
Now, select open command window here.
In the command prompt, type the following with hitting enter at the end of each line.
adb-windows reboot bootloader (and wait for the device to reboot)
fastboot-windows oem unlock
(If it gets stuck at waiting for device here, download and install PDANet on your computer, once installed, unplug then plug the device back in and see if that fixes it)
Once it runs the device should display a screen asking you if you are sure. Click yes using the volume buttons. The device will go back to the bootloader screen but say unlocked at the bottom.
Click to expand...
Click to collapse
Leftcatcher said:
I cant find mine either, but i have a suspicion that they just removed/edited the files to just have one state of locked and no controls or commands to unlock it.
Find out the file name and path for the "OEM unlock" setting in the developer options.
then search for it using the ADB, if the files aren't there then you might need to put the phone in to download mode and "sideload" the the full files back on to it.. if it's possible.
it might be more complicated than that. that's what i would've done as a Carrier if i wanted to keep modders and phone thieves out.
also on my Carrier phone when i put it into Download mode it seems to run like there own unlock before it does anything else, might need to run that first to unlock the lock so you can unlock it...
this is kind of a BS response, but at least it's an idea to look into. Sorry.
also you could try loading PDANet to see if the device will recognise.
Click to expand...
Click to collapse
Never mind, I did unlock my bootloader. Thanks for your help though.
Fixed !!!
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
It's Ok,In Adb Write "adb enable oem unlocking"
I Learned That From A Video
Called:
"How To Unlock Bootloader-Huawei GR5 & Honor 5X EMUI 4.0"
From The Channel Called:"NoNDrOiD"
Hi.
Before my question I'll write about my experience because I am sure it will help many many people.
As many of you, I always ROOT my smartphones.
Nowadays, the new phones, they come with this new technology to avoid root and other things called " OEM Lock " under the Developer's Options.
Following every step provided in the root guide for you phone, the new step to enable OEM Unlock under Developer Options
is a must!
The only thing that they don't say is that you MUST leave OEM Unlock ALWAYS ENABLED during and AFTER the root, and not only during the root
process.
Not knowing that, what did I do? Right After rooting my Samsung Note 5 I disabled the OEM Unlock. When I restarted the smartphone, it got into something called FAP Protection Black Screen where you are not able to leave not even if you try to root the phone again with the img file!
If you get in the FAP Protection Screen, like I did, despair will take over, I promise! And Google will not help you!
Is there a solution?
I found one, but not in any Google Page.
You need to download the firware img file for your phone, exactly same model,
in my case it was SM-N920G (Samsung Note 5), and for your specific country. Luckily for my phone it was not so hard to find, just hard to download (1,7GB with average 15 kB/s speed!). You will find different versions, some related to a Phone Company Operator that your country has, other related to no operator at all (sure I chose that).
After you get the firware file, just use Odin with that file to flash the phone, just like how you did to root the phone, but now, instead of using the root img file with Odin Software, you'll use the firmware file. That will not only solve the problem and give you access to your phone again, but in my case the Operator Flag disappeared and the data and apps installed miraculously were intact! I was pretty sure I was supposed to lose everything, but that didn't happen!
I'm sure what I wrote above will help many desperate people out there!
Now, my main question here:
You can never disable OEM Unlock in your life, with a rooted phone, period! So, it's really dangerous to leave the developer options enabled, allowing anyone that uses the phone to change it, even if by accident. In my case, as another example, besides rooting my phone, I rooted my father's phone too (because it was previously mine). I'd like to avoid by any means that by any chance me, or my father, disable to the OEM Unlock.
So, my question:
If I disable the Developer Option in order to "hide" it, will the changes that I did inside it remain working perfectly? I'm afraid that if I disable the developer options, somehow, it might take every option inside it back to the "default", just like it was before I enabled the developer Options, meaning in this case, OEM Unlock would get DISABLED again!
Is it safe to disable the Developer Options when OEM Unlock is Enable and MUST Remain like that?
Thank you.
Lost a night of sleep for the same problem with a Samsung S8.
This should be added to *every* mod guide.
In my case was worse too...if you root the phone and wipe data, when you open first time developer option you'll find "OEM Unlock" disabled (but I assume it's enabled at bootloader level). So when I check / uncheck it I doom my phone to lock on next restart...
how to get to boot menu on htc u12 plus, smallest width setting got adjusted wrong in developer options and power got cycled, all I can see on lock screen are 1,2 and 3 cant unlock, any ideas?
Hello XDA, I've been wanting to root my S6 for a while now, and i think you can do it with adb. So when trying this i noticed i needed an unlocked bootloader, and i thought i had it because i had CRom service on my S6, but never opened it. When i did, it just crashed. Now, i'm not sure if I can just use
Code:
fastboot oem unlock
or i need something else. I'm on Mac so i am very, very limited. I at least can get adb to work. If i can use adb and or fastboot to unlock my device's bootloader (without messing DM Verity) then please tell me right away.
iLoveMuffinz said:
Hello XDA, I've been wanting to root my S6 for a while now, and i think you can do it with adb. So when trying this i noticed i needed an unlocked bootloader, and i thought i had it because i had CRom service on my S6, but never opened it. When i did, it just crashed. Now, i'm not sure if I can just use or i need something else. I'm on Mac so i am very, very limited. I at least can get adb to work. If i can use adb and or fastboot to unlock my device's bootloader (without messing DM Verity) then please tell me right away.
Click to expand...
Click to collapse
What variant s6 do you have?
Go to Settings - About Device - Build number. Tap on that repeatedly until you see that Developer Options has been enabled.
Go back to Settings. You will now see a new entry called Developer options. Tap on that.
Under Developer options you will see OEM Unlock. Switch that to On.
And you are done! Just that easy!
koop1955 said:
Go to Settings - About Device - Build number. Tap on that repeatedly until you see that Developer Options has been enabled.
Go back to Settings. You will now see a new entry called Developer options. Tap on that.
Under Developer options you will see OEM Unlock. Switch that to On.
And you are done! Just that easy!
Click to expand...
Click to collapse
It's not that easy, the option is called "Allow OEM unlocking" which I already have turned on. All that option does is allow the bootloader to be unlocked.
sofir786 said:
What variant s6 do you have?
Click to expand...
Click to collapse
920T Unlocked.
I know. A rare S6 model, bought in Panama.
iLoveMuffinz said:
920T Unlocked.
I know. A rare S6 model, bought in Panama.
Click to expand...
Click to collapse
What version android are you on, btw the user previous is correct, once you use OEM unlock all you need to do is flash cf-autoroot, OEM unlock make sure that after rooting the phone does not trip frp and just lock you out of your device.
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Just another note the g920t is classified as a T-mobile variant, it's got its own whole forum here on xda, if you don't get any luck here might be an idea to pop on over there and have a look see
sofir786 said:
What version android are you on, btw the user previous is correct, once you use OEM unlock all you need to do is flash cf-autoroot, OEM unlock make sure that after rooting the phone does not trip frp and just lock you out of your device.
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Just another note the g920t is classified as a T-mobile variant, it's got its own whole forum here on xda, if you don't get any luck here might be an idea to pop on over there and have a look see
Click to expand...
Click to collapse
Ok, I'm on 6.0.1 (Y is Samsung so slow when releasing updates) and a quick reminder: I'm on Mac, how am I supposed to flash CF-autoroot?
And I got confused by "make sure after rootingthe phone does not trip frp and just lock out of your device" Do you mean to be careful not to brick my device?
iLoveMuffinz said:
Ok, I'm on 6.0.1 (Y is Samsung so slow when releasing updates) and a quick reminder: I'm on Mac, how am I supposed to flash CF-autoroot?
And I got confused by "make sure after rootingthe phone does not trip frp and just lock out of your device" Do you mean to be careful not to brick my device?
Click to expand...
Click to collapse
FRP is factory reset protection, if you don't allow OEM unlock when after you have carried out root and try to log into phone again you won't be able to do so, it's a security feature, frp is very tricky and it's important you make sure you have OEM unlock enabled before trying to do anything. You can use a software called heimdall which is similar to Odin and can be downloaded for mac. Yeah samsung always rolls out updates for international before anything else, just how they work. Before doing anything I highly advise you to visit the g920t forums, you will get more info there than you will here on the international forum. I hope you manage to get things done
sofir786 said:
What version android are you on, btw the user previous is correct, once you use OEM unlock all you need to do is flash cf-autoroot, OEM unlock make sure that after rooting the phone does not trip frp and just lock you out of your device.
Click to expand...
Click to collapse
Thanks for pointing that out. I don't know why I expect people to be grateful on XDA, just because someone tries to help them.
Using a Mac, you flash files using Heimdall: http://glassechidna.com.au/heimdall/
Ok so I think I'm good to go:
I attached some screenshots checking if everything is correct. Also, is http://glassechidna.com.au/heimdall/ the correct and official site to get Heimdall? And my device's build is G920TUES5DQD1 which was released a few days ago, and I'm not sure if the CF auto root file was based on an earlier update. Will I still be able to use it?
is g920v bootloader unlockable?
is it possible to downgrade thanks to this oem unlock?
sofir786 said:
FRP is factory reset protection, if you don't allow OEM unlock when after you have carried out root and try to log into phone again you won't be able to do so, it's a security feature, frp is very tricky and it's important you make sure you have OEM unlock enabled before trying to do anything. You can use a software called heimdall which is similar to Odin and can be downloaded for mac. Yeah samsung always rolls out updates for international before anything else, just how they work. Before doing anything I highly advise you to visit the g920t forums, you will get more info there than you will here on the international forum. I hope you manage to get things done
Click to expand...
Click to collapse
My phone has the front tripped, is there any way to reset it? I can't even figure out how to pull up the system info, I can pull up the recovery menu and hard reset but I don't know how to, if possible, reset the front. Any advice?
Sent from my LGE LG-LS777 using XDA Labs
iLoveMuffinz said:
Hello XDA, I've been wanting to root my S6 for a while now, and i think you can do it with adb. So when trying this i noticed i needed an unlocked bootloader, and i thought i had it because i had CRom service on my S6, but never opened it. When i did, it just crashed. Now, i'm not sure if I can just use
Code:
fastboot oem unlock
or i need something else. I'm on Mac so i am very, very limited. I at least can get adb to work. If i can use adb and or fastboot to unlock my device's bootloader (without messing DM Verity) then please tell me right away.
Click to expand...
Click to collapse
Install Windows in a Virtual Machine, Use ODIN to flash TWRP, flash Magisk.
help with unlock bootloader s6 920v
first, i want to thank the ones that can help and enlight others. thanks.
Now, i have a verizon s6 920v and doesnt present the "OEM..." option in Dev section. could i know if is unlock the bootloader, in other way?
thanks again.
joeknz said:
first, i want to thank the ones that can help and enlight others. thanks.
Now, i have a verizon s6 920v and doesnt present the "OEM..." option in Dev section. could i know if is unlock the bootloader, in other way?
thanks again.
Click to expand...
Click to collapse
As far as I know, and what has been the fact since the release of the 920V, there's has been no known case where the bootloader has been unlocked. Due to Verizon's restrictions, the S6 is hardlocked. The only way that it might ever be unlocked is if someone reverse engineers the bootloader software, creating an unlocked version that can be flashed, and that will still pass the phone's security checks. I wouldn't hold your breath for it though, because it's been 3 years and no solution yet.
i had same issues
i have been trying to unlock my s6 smg 9208 everything that i tried failed need really your help i can't use my keyboard and mouse ????
Most Samsung phones are unlocked, Only a small percentage of Samsung phones has locked bootloaders. Just pop a different carrier SIM and make sure it works, If different sims work then your device has an unlocked bootloader.
mzayd786 said:
Most Samsung phones are unlocked, Only a small percentage of Samsung phones has locked bootloaders. Just pop a different carrier SIM and make sure it works, If different sims work then your device has an unlocked bootloader.
Click to expand...
Click to collapse
That is incorrect, what you are referring to is carrier locked. and is done to most phones sold in the US. Most can be unlocked once fully paid for and after 90 days of service.
Bootloader lock has nothing to do with sim cards at ALL!! It does have everything to do with being able to install other roms and firmware via non official sources.
Sprint Samsung Galaxy S6 model SM g920p FRP lock is blocking me from enabling OEM unl
koop1955 said:
Go to Settings - About Device - Build number. Tap on that repeatedly until you see that Developer Options has been enabled.
Go back to Settings. You will now see a new entry called Developer options. Tap on that.
Under Developer options you will see OEM Unlock. Switch that to On.
And you are done! Just that easy!
Click to expand...
Click to collapse
Hello to you super techs I'm a newbie to this hope i'm not posting out of place but my question is how do I set up my Windows PC with ADB to use ADB fastboot unlock to unlock my bootloader because FRP protection has me locked out of the phone and I can't use the build number 2 unlock OEM or is that even possible I have been searching the web and XDA 2 try and find a way to open this phone I bought for myself for Christmas not knowing anything about a phone being FRP locked to a Google account is it possible to unlock this phone so that I can Flash it and maybe be able to use it I checked the IMEI number and it comes back good so say Sprint customer service but they couldn't help me with the FRP because I bought the phone second hand could you guys please point me in the right direction if I'm in the wrong spot posting my apologies to the thread host
Hello recently I tried to root my phone, wanting to fix ghost touch, I did something wrong and the phone stopped working, "Only official binary blah blah blah ..." popped up during startup, I decided to reinstall the official stock, the phone started working normally, even ghost touch repaired, I looked at the Root Checker application if I have root, it turned out not, which is all right, but when I want to add the card to google pay or open McDonald's applications, I get a message that the phone is rooted or was somehow rooted modified, what can I do in such a situation, please help me, I tried to install other stocks from other operators and restore the phone to factory settings: _ (
I saw one solution, probably in this forum where someone wrote to enable OEM Unlock and USB Debugging then disable and enable again, something like this, but I don't see OEM Unlock in the developer option, I know that with a failed root attempt, I somehow unlocked this option, but I don't remember how and I prefer someone to help me as best as he can, because I don't want to break anything anymore, I just want Google Pay to start working for me
OEM is probably hidden cause your device isnt older than 7 days. Connect to wifi and enable automatic time and date, than disable once done set the date atleast 7 day forward and oem should appear but you will have to lock ur bootloader before you disable oem and if you are running a custom firmawre make sure to backup data if you wanna go to normal firmware
But I use official firmware from some Samsung firmware site, i think my bootloader is locked, anyway do you have any solves to make work google pay?
I tried to unlock OEM but this solution with data & time doesn't work for me.
Hey, when I go to Google Play Shop there is an information that my device isn't certified, I tried to register my ID Device and still doesn't work can It be a problem, because of that Google Pay doesn't work?
syonox said:
OEM is probably hidden cause your device isnt older than 7 days. Connect to wifi and enable automatic time and date, than disable once done set the date atleast 7 day forward and oem should appear but you will have to lock ur bootloader before you disable oem and if you are running a custom firmawre make sure to backup data if you wanna go to normal firmware.
Click to expand...
Click to collapse
If i wait 7 days OEM option should unlock automatically?
Is it good idea to root this device correctly and use magisk to make google pay work good or for example root this device and then unroot to make work google pay?
Eco24 said:
If i wait 7 days OEM option should unlock automatically?
Click to expand...
Click to collapse
before you do this if odin says you are in custom mode backup all your data before doing this. no it wont automatically, first you have to go to odin mode and hold up for a bit until the screen shuts and shows the question (do you wanna lock your bootloader) you select yes once done if you are on custom it will bring up only odin mode before anything thats where u flash firmware, now that should get rid of the root, and then if u wanna disable oem connect to wifi disconnect date and time unselect automatically and go 7 days ahead and the option will appear.
How to check if i have custom mode and what i have to hold up?? please explain better because i don't know what i have to do
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.