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.
Related
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 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
Hi,
I've searched for instructions but can't find my situation.
I'd like to unroot, go back to LG stock, and lock bootloader so I can sell my LGv30 US998.
I have the actual US998 from B&H (not one that's been converted from something else).
Current build is: US99820a with March 1, 2018 Security.
Can someone let me know the procedure? I believe I'd like to go to the latest Oreo version "h" I think.
PS. I've tried to install LGUP tool, LG Flash Tool and none of them seem to detect my phone on Windows 10 from https://lgflash.com/download/ There are so many versions of all of these programs I don't know which one is correct. I've also installed the LGMobileDriver_WHQL_Ver_4.5.0.exe
So, some links to LGUP that actually works would be great.
Thanks
glhelinski said:
Hi,
I've searched for instructions but can't find my situation.
I'd like to unroot, go back to LG stock, and lock bootloader so I can sell my LGv30 US998.
I have the actual US998 from B&H (not one that's been converted from something else).
Current build is: US99820a with March 1, 2018 Security.
Can someone let me know the procedure? I believe I'd like to go to the latest Oreo version "h" I think.
PS. I've tried to install LGUP tool, LG Flash Tool and none of them seem to detect my phone on Windows 10 from https://lgflash.com/download/ There are so many versions of all of these programs I don't know which one is correct. I've also installed the LGMobileDriver_WHQL_Ver_4.5.0.exe
So, some links to LGUP that actually works would be great.
Thanks
Click to expand...
Click to collapse
follow instructions from ChazzMatt's thread, they have LG UP dual linked and the instructions to flash kdz
Thanks. He has lots of threads. Do you have a link?
I believe it's the one/main thread he maintains on how to root/unlock the phone. You'll have to do some thinking on how to go "backwards" from there, but the software and steps are all in there.
Generally speaking, it's NOT recommended to relock the BL because if the phone isn't 100% stock ROM, I believe you could end up bricking or bootlooping. I think you can leave the BL unlocked and just KDZ flash US998 and leave it unrooted (no Magisk, etc). This should look "stock" to anyone who cares to have a stock-specific phone anyway.
I'm concerned a buyer wouldn't like the opening "corruption. lock the bootloader" screen. My assumption is locking the bootloader would get rid of that... Does anyone know if that's true?
glhelinski said:
I'm concerned a buyer wouldn't like the opening "corruption. lock the bootloader" screen. My assumption is locking the bootloader would get rid of that... Does anyone know if that's true?
Click to expand...
Click to collapse
Yes, re-locking the bootloader will get rid of the warning screen. Just make sure you are 100% complete stock (all partitions) before you re-lock it. Otherwise the phone may brick itself.
Also, make sure you remove your Google account in the OS before you wipe/re-flash the phone. Otherwise it will trigger FRP and require the new user to enter the previous username and password.
I might be in the same boat here, would love to know how to just return to stock and relock bootloader (for someone who didn't make an initial backup)
How about these steps:
1) Make sure you have working ADB on your computer, including latest LG USB drivers.
2) Boot into the OS and remove your account using Settings -> General -> Accounts -> (select Google account) -> Remove account. This prevents Android's Factory reset Protection from kicking in, which otherwise would require the previous account to be re-entered after wiping the phone.
3) Go to ChazzMatt's US998 Pie KDZ thread and download and install LGUP exactly as described under How to Install Dev Patched LGUP towards the bottom of post #2. Remember to thank Chazz.
4) Download the KDZ for your current OS version (Oreo or Pie) either from the relevant KDZ ROM thread in the V30 ROM sub-forum or from LG-firmwares.com. Verify its MD5.
5) Enter Download mode: With the phone off, hold Vol Up, and plug in the USB cable that is connected to your PC.
6) Assuming you manage to get into Download mode, launch LGUP and make sure it detects the phone.
7) Flash the KDZ you downloaded using LGUP Refurbish mode. If you're on a custom ROM and/or if you want to do a particularly thorough job, you may consider FIRST flashing Nougat using LGUP Partition DL mode, THEN flashing back up to Oreo or Pie, again using Partition DL Mode.
8) After LGUP (hopefully) completes flashing the KDZ unplug the cable and let phone reboot.
9) Once (hopefully) you're booted into the OS, tap Settings -> General -> About phone -> Software info- > Build number until Developer Options are enabled.
10) Enable Settings -> General -> Developer Options -> Enable OEM unlock.
11) Turn phone off and unplug the cable.
12) With phone off, enter fastboot mode by holding Vol Down and plug in the USB cable that is connected to your PC.
13) In ADB window on computer, enter fastboot devices to verify ADB is working.
14) In ADB window, enter fastboot oem lock to re-lock the bootloader.
15) Use fastboot keys to reboot phone into OS. See that it works.
16). Run Settings -> General -> Reset -> Factory data reset. Do NOT use Master Reset (button dance) or the new user might trigger FRP/kill switch (although shouldn't happen if you removed the account previously and didn't enter it again).
17) Done. Hand off the phone to its new user.
These steps were written off the top of my head. If anybody sees glaring mistakes or omissions, then please let me know.
Note: Some carrier models cannot readily get into fastboot mode. For those you will need to convert back to stock US998 to re-lock the bootloader (using Frankenstein like when you first rooted) and THEN convert back to the carrier firmware (again using Frankenstein).
Thank you
TheDannemand said:
How about these steps:
1) Make sure you have working ADB on your computer, including latest LG USB drivers.
2) Boot into the OS and remove your account using Settings -> General -> Accounts -> (select Google account) -> Remove account. This prevents Android's Factory reset Protection from kicking in, which otherwise would require the previous account to be re-entered after wiping the phone.
3) Go to ChazzMatt's US998 Pie KDZ thread and download and install LGUP exactly as described under How to Install Dev Patched LGUP towards the bottom of post #2. Remember to thank Chazz.
4) Download the KDZ for your current OS version (Oreo or Pie) either from the relevant KDZ ROM thread in the V30 ROM sub-forum or from LG-firmwares.com. Verify its MD5.
5) Enter Download mode: With the phone off, hold Vol Up, and plug in the USB cable that is connected to your PC.
6) Assuming you manage to get into Download mode, launch LGUP and make sure it detects the phone.
7) Flash the KDZ you downloaded using LGUP Refurbish mode. If you're on a custom ROM and/or if you want to do a particularly thorough job, you may consider FIRST flashing Nougat using LGUP Partition DL mode, THEN flashing back up to Oreo or Pie, again using Partition DL Mode.
8) After LGUP (hopefully) completes flashing the KDZ unplug the cable and let phone reboot.
9) Once (hopefully) you're booted into the OS, tap Settings -> General -> About phone -> Software info- > Build number until Developer Options are enabled.
10) Enable Settings -> General -> Developer Options -> Enable OEM unlock.
11) Turn phone off and unplug the cable.
12) With phone off, enter fastboot mode by holding Vol Down and plug in the USB cable that is connected to your PC.
13) In ADB window on computer, enter fastboot devices to verify ADB is working.
14) In ADB window, enter fastboot oem lock to re-lock the bootloader.
15) Use fastboot keys to reboot phone into OS. See that it works.
16). Run Settings -> General -> Reset -> Factory data reset. Do NOT use Master Reset (button dance) or the new user might trigger FRP/kill switch (although shouldn't happen if you removed the account previously and didn't enter it again).
17) Done. Hand off the phone to its new user.
These steps were written off the top of my head. If anybody sees glaring mistakes or omissions, then please let me know.
Note: Some carrier models cannot readily get into fastboot mode. For those you will need to convert back to stock US998 to re-lock the bootloader (using Frankenstein like when you first rooted) and THEN convert back to the carrier firmware (again using Frankenstein).
Click to expand...
Click to collapse
not sure if you can help. i asked chaz as well but haven't received a resolution. i've done this but the phone at aroud >10 says that it needs to enable oem unlock to move forward with fastboot commands. except that this option is greyed out in the dev options. says phone is bootloader is already unlocked and doesn;t give option to enable it?? sigh i have tried 4 versions nougat and oreo ... none worked... any ideas??
johnp357 said:
not sure if you can help. i asked chaz as well but haven't received a resolution. i've done this but the phone at aroud >10 says that it needs to enable oem unlock to move forward with fastboot commands. except that this option is greyed out in the dev options. says phone is bootloader is already unlocked and doesn;t give option to enable it?? sigh i have tried 4 versions nougat and oreo ... none worked... any ideas??
Click to expand...
Click to collapse
I've heard of this before, where OEM Unlock was greyed out in the Developer Settings menu. I believe the answer was you have to wait a few days and it will change. But that's very frustrating when you're trying to get this phone back to stock.
Just to make sure I understood you correctly: You have tried booting into fastboot and run "fastboot oem lock" even with OEM Unlock greyed out, right? Otherwise definitely try that.
I am afraid I don't have any other suggestions.
@ChazzMatt: I remember you posting about this one time. Do you have more to add?
TheDannemand said:
I've heard of this before, where OEM Unlock was greyed out in the Developer Settings menu. I believe the answer was you have to wait a few days and it will change. But that's very frustrating when you're trying to get this phone back to stock.
Just to make sure I understood you correctly: You have tried booting into fastboot and run "fastboot oem lock" even with OEM Unlock greyed out, right? Otherwise definitely try that.
I am afraid I don't have any other suggestions.
@ChazzMatt: I remember you posting about this one time. Do you have more to add?
Click to expand...
Click to collapse
yes. i have tried it anyway but the pc says waiting for devices. it does not recognize it since oem unlock isn't triggered.. doesn't work....sigh
johnp357 said:
yes. i have tried it anyway but the pc says waiting for devices. it does not recognize it since oem unlock isn't triggered.. doesn't work....sigh
Click to expand...
Click to collapse
Understood. Question: Did you flash KDZ with Refurbish or Partition DL? Maybe one of them will clear this state and the other won't. But DON'T go experimenting with other LGUP modes!
Also, you could try a Factory reset and/or Master Reset (button dance) and see if that clears it.
If none of that works, you may have to just wait it out.
Edit: I googled around a bit. It seems Factory reset, then letting the OS connect to the internet (enable WiFi) can make the difference. Try googling as there are many references to this.
TheDannemand said:
Understood. Question: Did you flash KDZ with Refurbish or Partition DL? Maybe one of them will clear this state and the other won't. But DON'T go experimenting with other LGUP modes!
Also, you could try a Factory reset and/or Master Reset (button dance) and see if that clears it.
If none of that works, you may have to just wait it out.
Edit: I googled around a bit. It seems Factory reset, then letting the OS connect to the internet (enable WiFi) can make the difference. Try googling as there are many references to this.
Click to expand...
Click to collapse
i tried both refurbished and partition dl.. i may start tinkering with the others but people have warned against some so i'm hesitant of trying it... this really sucks.. need to return it to VZ on a trade in and running out of time
johnp357 said:
i tried both refurbished and partition dl.. i may start tinkering with the others but people have warned against some so i'm hesitant of trying it... this really sucks.. need to return it to VZ on a trade in and running out of time
Click to expand...
Click to collapse
Why can't you wipe it and return it to VZ like that? They don't care if it's rooted, bl unlocked, etc. They're going to wipe it when they get it and try to resell it regardless, why do their job for them?
ldeveraux said:
Why can't you wipe it and return it to VZ like that? They don't care if it's rooted, bl unlocked, etc. They're going to wipe it when they get it and try to resell it regardless, why do their job for them?
Click to expand...
Click to collapse
i read somewhere that rooting a phone violates their terms and makes it invalid as a trade in...
johnp357 said:
i read somewhere that rooting a phone violates their terms and makes it invalid as a trade in...
Click to expand...
Click to collapse
It voids whatever warranty existed between you, Verizon, and LG, but I haven't seen anything about trade ins. Where'd you read that?
johnp357 said:
i tried both refurbished and partition dl.. i may start tinkering with the others but people have warned against some so i'm hesitant of trying it... this really sucks.. need to return it to VZ on a trade in and running out of time
Click to expand...
Click to collapse
Did you try a Factory reset from the menu, then setup phone again with WiFi enabled? Heck, possibly even entering you Google account during setup and let it sync, if that's what it takes. As long as you perform a Factory reset from the menu to remove your account before trading it in.
@ldeveraux is probably right that Verizon won't care. But I am cautious person too when it comes to these things, and would prefer to trade in the phone in a clean state. Just in case the person you end up dealing with is a nitpick.
TheDannemand said:
Did you try a Factory reset from the menu, then setup phone again with WiFi enabled? Heck, possibly even entering you Google account during setup and let it sync, if that's what it takes. As long as you perform a Factory reset from the menu to remove your account before trading it in.
@ldeveraux is probably right that Verizon won't care. But I am cautious person too when it comes to these things, and would prefer to trade in the phone in a clean state. Just in case the person you end up dealing with is a nitpick.
Click to expand...
Click to collapse
i did try the factory reset. both from within and the buttons. and connected with wifi. didn't work... sadly. removing my account is not an issue. every time I install 1 of 4 diff nougat or oreo kdz in lgup, I put skip in the login so it doesn't have my info anymore... resetting doesn't really do it. messing with the date like others have suggested didn't either.
johnp357 said:
i did try the factory reset. both from within and the buttons. and connected with wifi. didn't work... sadly. removing my account is not an issue. every time I install 1 of 4 diff nougat or oreo kdz in lgup, I put skip in the login so it doesn't have my info anymore... resetting doesn't really do it. messing with the date like others have suggested didn't either.
Click to expand...
Click to collapse
That is indeed puzzling. I did this twice on my old H932 before sending it in for warranty, and never saw that problem.
I am sorry I don't have more suggestions to offer
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
Recently purchased a used Galaxy Tab S6. I was warned it had a warning about the bootloader being unlocked. No big deal. The seller couldn't remember his Samsung account credentials so we couldn't factory reset at time of purchase via Settings. No big deal. I went into Download Mode and relocked the bootloader. I went into Recovery Mode and Factory Reset.
Then I ran into "This tablet is protected by Know Cloud Service. To continue setup, connect to a wi-fi or mobile network." I've done that (since I can't skip the step) and get the dreaded "Can't create work profile" error and that's as far as the set up will go.
So I used Odin to flash the latest stock ROM and factory reset again and wiped the cache and I'm still having that problem.
In download mode, I've confirmed that Knox has been tripped.
I've googled like mad and I'm not finding a solution. Can anyone help me out? I'd prefer to stay on Stock ROM so there are no hardware issues (particularly with the SPen) as I'm planning to use this device extensively for note-taking (with OneNote). However, I'm open to custom ROM if that's my best/easiest/simplest route.
Thanks in advance!
If you're able, unlock the bootloader again. When you flashed with Odin, did you use the CSC or HOME_CSC file?
V0latyle said:
If you're able, unlock the bootloader again. When you flashed with Odin, did you use the CSC or HOME_CSC file?
Click to expand...
Click to collapse
I used CSC. As I understand it, that is the "deeper" reset option.
snick17 said:
I used CSC. As I understand it, that is the "deeper" reset option.
Click to expand...
Click to collapse
Correct, that wipes user data.
Unlock the bootloader again, which will wipe the device (again), and see if it's removed the FRP. If not, you should be able to flash TWRP, from which you should be able to flash this to disable the FRP.
I can't access the developer options because I can't get through the setup wizard. So I can't flip the OEM Unlocking so the download mode doesn't give me the option to unlock. I can connect to ADB via the Recovery Mode but Fastboot doesn't see it so I can't do "oem unlock." Are there any other methods to unlock it? My friend Google hasn't found any yet.
Seller was able to login to both his Google and Samsung accounts and remove the device from them. That got me through the 100% Know Enrollment Service before it hung up in the "update" portion again. He was also able to send a message to the tablet from the Samsung account to try and release it further but, of course, since I've wiped it, that message can't get through.
I'm getting desperate. I might have bought a paperweight! Any once else have a suggestion?
Checked with the seller. He bought it from Kijiji as well from the original owner. It's always been a personal device, never an institutional one.
Last night's searching of the internet determined that the device is in "prenormal" status so I'm just going to wait 7 days and reboot. That might be sufficient. Nothing to lose at this point.