Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
I'm with same problem here!
Suckmymfdick17 said:
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
Click to expand...
Click to collapse
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
knjigo said:
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
Click to expand...
Click to collapse
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Suckmymfdick17 said:
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Click to expand...
Click to collapse
What do you mean with "I blocked my bootloader"?
Twrp is easy to flash. Root is integrated in ressurection remix rom. And this rom is great. Just try to flash twrp in Fastboot and than ressurection remix with twrp.
Can you boot in Fastboot?
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
tjgibri said:
I'm with same problem here!
Click to expand...
Click to collapse
I solved it, I finally flashed the stock rom to my phone and it works.
Apparently my pc was not flashing the stock rom in adb, and the phone turned off when loading the software. I did it 3 times until I load correctly and start well.
if you have the same problem apparently then OEM Blocking is not responsible. You have to flash the most current rom or the one that you had by default when the brick happened to you, you flash it in a normal way with commands of adb and ready, I would have to come back to life.
download from firmware center MotoZ Griffin the most current rom stock at 7.1.1
echo92 said:
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
Click to expand...
Click to collapse
Thanks for your help friend, I finally flashed it with a recent android 7.1.1 update. Apparently the OEM lockout was not the culprit, but it was an interrupted flash of android 7.1.1 at some point when loading the software to the phone, it would shut down on its own and not complete the installation, which showed me the mentioned message. I didn't realize that and thought it was the OEM blockade.
I finally did it on another pc and it worked. the phone came back to life.
I have one Moto Z2 Force (XT1789-05), bought from coolicool.com, I didn't know device came Unlocked Bootloader, Device rom had problem with many apps, I googled and found one topic in XDA developer to Install Stock Rom, I downloaded and Installed India Rom, it's worked somehow fine, but still had problem, I downloaded Verizon Rom, Android 8, after Installed Android 8 Verizon Rom, Locked device bootloader immediately, now device stuck at Welcome Wizard in Android 8, after select language I got this message: (Please wait, this may take a few minutes) this is proof video (http://ahmn.co/Upload/IMG_0161.MOV), after this issue, device already locked, I can't unlock, because need to go to the Developer Option in Setting, I stucked in Welcome Wizard, there isn't any bypass, So, I start to search in Google, XDA-Forum, Android Central and more, I created many threads, many requests, no one can't help me, I tried to reach google developer support to the tell to me how can I bypass Android 8 Welcome Wizard, there is must be a way, but I can't find it, now I can access to Android Recovery and Bootloader
1. if you help me to FORCE UNLOCK device without need Developer Option in setting my problem will solve
2. If you help me to Bypass Android Welcome Wizard, access setting and enable OEM Unlock
3. If you help me to update the device from Android 8 to Android 9 Verizon ROM via ADB Sideload or Update from SD card in Recovery mode
4. If you have any idea to how can I fix it
Extra Information: I bought Belkin and Uni USB-C to Ethernet Adaptor to help me bypass Android 8 Welcome Wizard, I bought WSKY WIFI Adaptor because device Wifi can't find any network (I found QR setup by tap several times in Language Selection), after this section need to download google device policy apk, my device can't find any Wifi Network and my Ethernet Adaptor can't help me either, So, I just remained with my phone, and I can't do anything,
Please, someone, help me
My Device SKU: XT1789-05
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
Hey folks,
I've tried my best so far, but I am stuck.
I wanted to change the ROM on my wife's Redmi 3 pro. It was running on a rather old RR version and I wanted to go back to MIUI to have a better camera.
After an unsuccesful attempt to flash this, I was stuck in a bootloop.
This - in general - was no problem: I've decieded to flash an official firmware via MiFlash, but this apparently didn't work as well.
So, now MiFlash has locked the phone again but not properly installed anything.
I can access Fastboot and the pre-installed recovery, but nothing more.
The unlock tool tells me that I can't unlock it because it is apparentyl not bound to my MI account (and I have no clue with which account I've unlocked it the last time).
Desperately appreciation any kind of help!
Thanks in advance.
UPDATE: I was apparently not patient enough. After quite a while it finally booted. Now I can access the system again, but still can't unlock the phone.
UPDATE 2: I also found out with which account I've unlocked it and thus everything worked after all. Now sporting Lineage 14 with camera mod.
Please, feel free to explain how can it finally booted. Your experience might be help somebody sometime.
?
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
Samsung A02s(SM-A025F)
I do these steps any body help
1.I unlock oem through developer option
2.I unlock bootloader successfully
3.I downloaded firmware and patch AP with magisk to root
4.I flash Patched AP
5.After getting my phone rooted successfully I want to install TWRP Recovery
6.I downloaded unofficial version of TWRP from xdaforums....
7.I followed the steps guided here
The steps are as follows
1.reboot to boot loader and flash vbmeta_disable.tar
2.Put TWRP tar in AP and flash
3.Reboot to recovery
4.Disable encryption
Go to Advanced >Terminal : type "multidisabler"
5.Go back to wipe>Format Data>type "yes"
6.Reboot system
This is my first experience to root and flash TWRP.... but after that when I reboot my phone got lock .... only official binaries allowed to be installed....and stuck there
I got frightened so I locked my bootloader
But nothing happens...
I downloaded stock firmware and flash.....now my phone works perfectly But I want to root my phone I searched and found a correct way to root but now oem unlock option is not found in developer options....
I watched hundreds of videos on yt and searched a lot on Google but
found no proper solution.....someone tell me to wait 7 days....
In about phone> phone status>uptime
Uptime should be equal to 7days... then oem unlock option will appear but ...... I want another solution date change and WiFi connect is not solution ... If any body knows any other solution please guide me ... I'll be very thankful.....
@ladlabaloch512
Perhaps your device has the same "OEM unlock" block like mine.
On mine I was supposed to wait 7d after turning on dev options.
I bypassed that by
1. switching to airplane mode
2. Setting manually date back one month
3. Restart (still in airplane mode)
4. Turning off airplane mode and let it sync date
and voila OEM unlock option was there.
Perhaps that works on your device as well.
bmwdroid said:
@ladlabaloch512
Perhaps your device has the same "OEM unlock" block like mine.
On mine I was supposed to wait 7d after turning on dev options.
I bypassed that by
1. switching to airplane mode
2. Setting manually date back one month
3. Restart (still in airplane mode)
4. Turning off airplane mode and let it sync date
and voila OEM unlock option was there.
Perhaps that works on your device as well.
Click to expand...
Click to collapse
Thanks for reply...
This bypass method doesn't work in my device
Im too
i have tried everything But I read on somewhere that policy was upgrade to 1000 hours so i waited and hopping thats work!
Now it's almost 700 and i restarted before it on 200 so it's supposed to be 900
Mahmoudm.kamal said:
Im too
i have tried everything But I read on somewhere that policy was upgrade to 1000 hours so i waited and hopping thats work!
Now it's almost 700 and i restarted before it on 200 so it's supposed to be 900
Click to expand...
Click to collapse
Keep us updated.. I'd like to get my OEM unlock to come out of hiding.. this is frustrsting.. i see all these tutorials for the A02s root, twrp and ROMs and whatnot and I'm itching to get flashing!
Is it possible to flash an unlocked carrier firmware in ODIN and then be able to unlock OEM? Without carrier issues or anything? I'm a little nervous to be the first to try.. and not sure where to find US unlocked carrier firmware or if location even matters... I have the SM-A025AZ (US Cricket variant).. I guess as long as Download Mode (fastboot) is still accessible I could just flash the Cricket version back to the device.. bricked my LG-E980 back in the day.. took me a few months how to get it back up and running with LG flash tool.. i just dont want to repeat that fiasco lol... so anybody got any updates on hacking this OEM (un)lock bs??? Or any idea on flashing some other variant to the device without interrupting carrier stuff??.. seems like alot just to get a damn virtual switch to turn on.. but damnit I need root access! Lol.. about to just exchange this phone for an actual rootable phone.. i disagree with charging for hotspot.. that should be illegal.. getting charged twice to use th same bs internet.. eff that.. i just want Rooooooot!!!
Hello,
I have also been having these troubles, with no way to unlock oem after stock flash, and the closest I've got to finding a solution was this, but I simply cannot find samsung's bootloader unlocking form like it says in the guide. I bought my phone just for a bootloader unlockable version (A025M), and now I am very angry at samsung.
also, since over a 1000 hours have gone by since last post, have any one of you solved this issue just by waiting?
Noobiu said:
Hello,
I have also been having these troubles, with no way to unlock oem after stock flash, and the closest I've got to finding a solution was this, but I simply cannot find samsung's bootloader unlocking form like it says in the guide. I bought my phone just for a bootloader unlockable version (A025M), and now I am very angry at samsung.
also, since over a 1000 hours have gone by since last post, have any one of you solved this issue just by waiting?
Click to expand...
Click to collapse
Nope, More than 2000 hours and also changed firmwares and waited again an again and tried alot of ways but enable oem still disappeared
Im also very angry from samsung
Mahmoudm.kamal said:
Nope, More than 2000 hours and also changed firmwares and waited again an again and tried alot of ways but enable oem still disappeared
Im also very angry from samsung
Click to expand...
Click to collapse
its not only samsung that does this, many other companies like motorola does this. Dont be angry, just try a different device. Also, snapdragon US models (i dont think) arent able to be unlocked. If its a mediatek model and isnt sim/carrier locked, u can try MTKClient
Swyen said:
its not only samsung that does this, many other companies like motorola does this. Dont be angry, just try a different device. Also, snapdragon US models (i dont think) arent able to be unlocked. If its a mediatek model and isnt sim/carrier locked, u can try MTKClient
Click to expand...
Click to collapse
Yes dear, i had changed it since more than 7 months with A52S , thanks.
Mahmoudm.kamal said:
Yes dear, i had changed it since more than 7 months with A52S , thanks.
Click to expand...
Click to collapse
And, my A037W doesnt have the OEM Unlock option. Use an MTK tool to unlock it, thats how I did it
ewrecc said:
Is it possible to flash an unlocked carrier firmware in ODIN and then be able to unlock OEM? Without carrier issues or anything? I'm a little nervous to be the first to try.. and not sure where to find US unlocked carrier firmware or if location even matters... I have the SM-A025AZ (US Cricket variant).. I guess as long as Download Mode (fastboot) is still accessible I could just flash the Cricket version back to the device.. bricked my LG-E980 back in the day.. took me a few months how to get it back up and running with LG flash tool.. i just dont want to repeat that fiasco lol... so anybody got any updates on hacking this OEM (un)lock bs??? Or any idea on flashing some other variant to the device without interrupting carrier stuff??.. seems like alot just to get a damn virtual switch to turn on.. but damnit I need root access! Lol.. about to just exchange this phone for an actual rootable phone.. i disagree with charging for hotspot.. that should be illegal.. getting charged twice to use th same bs internet.. eff that.. i just want Rooooooot!!!
Click to expand...
Click to collapse
STOP TRYING TO UNLOCK A US DEVICE ITS NOT POSSIBLE
Swyen said:
And, my A037W doesnt have the OEM Unlock option. Use an MTK tool to unlock it, thats how I did it
Click to expand...
Click to collapse
Which tool did you use?
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.