Database Users

i interruped my update to 6.01

My phone wont boot back up because i interrupted the download by holding down the power button during install...it just keeps flashing google !!!
Help only had for 1 hour !!

Don't panic, flash a factory image and everything will be fine again

Gorgtech said:
Don't panic, flash a factory image and everything will be fine again
Click to expand...
Click to collapse
how do i do that ?

please tell me you enabled adb debugging and oem unlock (in developer settings)
and why? why did you power down during the update?

I am not sure if I debugged anything ....all I did was unlock the system Ui or something like that by tapping on something 7 times to unlock some hidden features !
I was paying attention to the phone and had the buttons held down while holding

On the screen when I try to recover in the bottom left it says device is locked along with a bunch of stuff and then the last line says connect USB CABLE .

akoda said:
I am not sure if I debugged anything ....all I did was unlock the system Ui or something like that by tapping on something 7 times to unlock some hidden features !
I was paying attention to the phone and had the buttons held down while holding
Click to expand...
Click to collapse
if you didn't alter anything within those "hidden features" you're almost certainly out of luck.
you need to have enabled "adb debugging" to likely get yourself out of this jam... plus you didnt unlock your device
try some of the things listed in this thread: http://forum.xda-developers.com/nexus-6p/help/mess-locked-bootloader-os-t3316463
if they dont work, im sorry to day, you pooched your device. will need repairs.

There's probably nothing you can do. Your bootloader is locked so you can't use fastboot to flash anything. If the stock recovery supports adb sideload you could try that, otherwise you're fresh out of luck and need it to be repaired.

WOW ...i cant believe this .....what should i say when i return it ?

You could say it powered off during the update.

akoda said:
WOW ...i cant believe this .....what should i say when i return it ?
Click to expand...
Click to collapse
well.. if nothing else, a hard lesson to NOT touch the phone at all when it's updating.
really sucks, and clearly just a mistake. hopefully they take pity on you

dratsablive said:
You could say it powered off during the update.
Click to expand...
Click to collapse
thanks ...i appreciate all you guys help !!!

Possible to 'crack' 6P locked by ADM?

Long shot as this shouldn't be possible, but I figured I'd try asking here anyways. Is there any way to unlock a 6P that's pin-locked by Android's Device Manager?
The goal is to get the pictures off this phone. It was my brother's phone before he passed away and I've been holding on to it for the past few months - just haven't had the energy to try to deal with it...
-I have access to the gmail account.
-I tried changing the pin through Google's device manager, but since the phone was already locked, the new pin did not take. I get the message on the phone about the new pin, but it doesn't unlock it.
-Developer mode is not enabled (i.e. USB debugging).
-Not rooted or anything like that and most likely has the latest updates (t-mobile). As a matter of fact, the lock screen says that a new system update has been downloaded.
Thanks.

Try putting twrp in your adb folder, boot into fastboot and use "fastboot boot twrp.img"

clappe said:
Long shot as this shouldn't be possible, but I figured I'd try asking here anyways. Is there any way to unlock a 6P that's pin-locked by Android's Device Manager?
The goal is to get the pictures off this phone. It was my brother's phone before he passed away and I've been holding on to it for the past few months - just haven't had the energy to try to deal with it...
-I have access to the gmail account.
-I tried changing the pin through Google's device manager, but since the phone was already locked, the new pin did not take. I get the message on the phone about the new pin, but it doesn't unlock it.
-Developer mode is not enabled.
-Not rooted or anything like that and most likely has the latest updates (t-mobile). As a matter of fact, the lock screen says that a new system update has been downloaded.
Thanks.
Click to expand...
Click to collapse
The only way I can think of is by installing twrp on the phone. The only way it wouldn't work would be if he didn't have USB debugging enabled, which if he didn't then you might be out of luck... I'm so sorry.

Ghstudent said:
The only way I can think of is by installing twrp on the phone. The only way it wouldn't work would be if he didn't have USB debugging enabled, which if he didn't then you might be out of luck... I'm so sorry.
Click to expand...
Click to collapse
Unfortunately, I am pretty sure USB debugging is not enabled...sorry that's what I meant when I wrote developer mode (I've tinkered with making apps, so I know what it is).
Thanks.

Same situation here and I try to figure a solution for many days.In my opinia the only way to bypass is a modified google account manager ! Could anybody help?

@clappe Just pretty sure? It wasn't mentioned in the OP, so I'll ask. Have you tried to install ADB on your PC and using ADB pull to grab the files from /storage/emulated/0/DCIM/Camera ? That's the directory to the location where the pictures are stored.
Also, to anyone mentioning TWRP. That's a flat out no-go. He stated bootloader was locked. You can't do that unless you unlock the bootloader.
Edit: He didn't say that, I assumed when he wrote not rooted or anything. Can you power cycle the device? Hold power until it shuts off then boot it up again. Do you see a padlock icon under the Google logo right when it starts up or no?
Edit2: Later today (after work, around 10 hours or so) I'll flash my 6P to stock factory images and relock my bootloader. I'll use device manager to pin lock it and pretend I don't know the password. I'll try a few things and see what I can do. Also, you have my condolences. Sorry for your loss.

RoyJ said:
@clappe Just pretty sure? It wasn't mentioned in the OP, so I'll ask. Have you tried to install ADB on your PC and using ADB pull to grab the files from /storage/emulated/0/DCIM/Camera ? That's the directory to the location where the pictures are stored.
Also, to anyone mentioning TWRP. That's a flat out no-go. He stated bootloader was locked. You can't do that unless you unlock the bootloader.
Edit: He didn't say that, I assumed when he wrote not rooted or anything. Can you power cycle the device? Hold power until it shuts off then boot it up again. Do you see a padlock icon under the Google logo right when it starts up or no?
Edit2: Later today (after work, around 10 hours or so) I'll flash my 6P to stock factory images and relock my bootloader. I'll use device manager to pin lock it and pretend I don't know the password. I'll try a few things and see what I can do. Also, you have my condolences. Sorry for your loss.
Click to expand...
Click to collapse
Connecting the device to a Windows 10 PC, it will recognize the 6P, but using Windows Explorer will show no files.
Running 'adb devices' lists no devices.
When I power on the 6P, first I get the 'Google' text logo, then the colorful 'spinny' android logo, then the 'android' text logo. Then it goes to the usual lock screen (shows the time, background, etc). On this screen are the normal shortcut buttons on the bottom - microphone, padlock, camera. After a few seconds it shows the 'Locked by Android Device Manager' screen, this has a padlock symbol in the middle along with the pin code that I set online through Google's device manager.
Thanks.

Might be worth a shot to try to contact Google. You'll need proof of your identity, and the passing of your brother though. Best of luck. Sorry about your loss.
If you end up not being able to get a rep that can help via email or phone calls; you might have to do a hardmod.

tr4nqui1i7y said:
Might be worth a shot to try to contact Google. You'll need proof of your identity, and the passing of your brother though. Best of luck. Sorry about your loss.
If you end up not being able to get a rep that can help via email or phone calls; you might have to do a hardmod.
Click to expand...
Click to collapse
Hardmod? I did a quick search and the only hardmod I found was to deal with temperature.
Thanks.

RoyJ said:
@clappe Just pretty sure? It wasn't mentioned in the OP, so I'll ask. Have you tried to install ADB on your PC and using ADB pull to grab the files from /storage/emulated/0/DCIM/Camera ? That's the directory to the location where the pictures are stored.
Also, to anyone mentioning TWRP. That's a flat out no-go. He stated bootloader was locked. You can't do that unless you unlock the bootloader.
Edit: He didn't say that, I assumed when he wrote not rooted or anything. Can you power cycle the device? Hold power until it shuts off then boot it up again. Do you see a padlock icon under the Google logo right when it starts up or no?
Edit2: Later today (after work, around 10 hours or so) I'll flash my 6P to stock factory images and relock my bootloader. I'll use device manager to pin lock it and pretend I don't know the password. I'll try a few things and see what I can do. Also, you have my condolences. Sorry for your loss.
Click to expand...
Click to collapse
Did you have a chance to try it?
Thanks.

How I Rooted Walmart Onn Tablets (No TWRP Needed)

I'll be making a video for this with the 7 inch tablet on Nov. 29th or 30th (depending on the time I have)
General Disclaimer: I'm not responsible if you brick your tablet. This is how I did it personally as other methods here didn't work for me. I have yet to test this method on a 7 inch, also do not have access to the Surf variants. This has only been tested on the 10.1 inch with the keyboard. Will update when I test with the 7 inch.
What's Needed:
MTK Fastboot Drivers: https://online.mediatek.com/Public Documents/MTK_Android_USB_Driver.zip
Magisk Manager Canary: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Stock Boot Image: https://forum.xda-developers.com/wa...eral/stock-stock-backups-images-otas-t3998227
ADB and Fastboot: https://www.xda-developers.com/what-is-adb/
Prerequisites:
Personally, I had issues getting my PC to recognize the tablets in Fastboot mode. The drivers wouldn't install. This might be optional for some of you, but I thought I'd include it just in case.
Installing MTK Fastboot Drivers from the link above
If you plugin your device in fastboot mode and your PC doesn't recognize it, follow these steps. If it did, skip this part.
1.) Download the drivers above and unzip the Zip file somewhere on your PC (desktop or My Documents is easiest)
2.) Boot your Tablet into Fastboot Mode by holding Vol + and Power, then select Fastboot from the Menu
*NOTE* There is a bug with these tablet's that the volume buttons are mislabeled. Really dumb, but I guess that's why they were 55 bucks for the 10 inch on black friday
3.) Plug the device into your PC and open Device Manager by pressing WinKey+R and typing devmgmt.msc, hit Enter
4.) If there's an Other Device listed called Android, follow these steps. If it isn't there, follow the next set of steps
5.) Open a Command Prompt window as Admin and type the following command
Code:
bcdedit.exe /set nointegritychecks on
6.) Hit enter, then restart your PC
7.) Once the PC is restarted, make sure your tablet is connected in Fastboot mode and open Device Manager again
8.) Right click Android under Other Devices and select Update Drivers
9.) Click the Browse my Computer for driver software button and select the MTK Folder you extracted from the download link above
10.) From there, you can open command prompt, type fastboot devices and see if your tablet shows up and move on to root!
Unlocking your Bootloader
From here, you can unlock your bootloader very easily to Root your device
This will wipe all data off the tablet!
0.) Enable OEM Unlock and USB Debugging on the tablet by going to Settings->About and tap Build Number 7 times. From here, enter the new Developer Options that unlock and turn on OEM Unlock and USB Debugging.
1.) Boot your tablet into Fastboot mode and connect it to your PC
2.) Open a Command Prompt window and type the following command, then hit enter
Code:
fastboot flashing unlock
3.) Follow the instructions on screen to unlock your bootloader
4.) Now Boot your device and we'll move on to making a rooted Boot Image
Creating a Rooted Boot Image with Magisk Manager
0.) Make sure you already have Wifi setup and connected before the first time you open Magisk Manager on your device! Make sure it auto connects as well
1.) Download Magisk Manager Canary from the link above
2.) Install it to your device
3.) Download boot Image from the Stock Boot Image part of the Prerequisites above and put the boot.img on your devices internal memory
4.) Open Magisk Manager and select Install Magisk
5.) Select Patch File and select the boot.img from your internal storage
6.) Once its done patching the image, take magisk_patched.img from the downloads folder of your device and move it onto your PC
7.) Boot your tablet into Fastboot mode and plug it into your PC
8.) Open Command Prompt and type the following command and hit enter (make sure you know your magisk_patched.img file location)
Code:
fastboot flash boot magisk_patched.img
9.) Reboot the device and you'll be Rooted!
Optional Steps like Modules and Debloating
My basic debloat script: https://forum.xda-developers.com/wa...s-general/root-walmart-bloat-remover-t4011639
Will be testing GSI roms on the spare 7 inch and will list those here
Recommended Magisk Modules:
Viper4Android Legacy
FDE.AI
MagiskHide Props Config
Systemless Hosts
Youtube Vanced Black
Magisk Setting to Enable:
Magisk Hide
Rename Magisk Manager App (keeps app from detecting magisk root)
Credits:
Myself for this root method @byproxy for reminding me to add the steps for OEM Unlock and enabling wifi before opening Magisk Manager for the first time

I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.

Are you online? I had the same problem.
Xavster2 said:
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Click to expand...
Click to collapse

Xavster2 said:
I'll start this off saying i'm an amateur at this, but I cannot for the life of me get an option to show up in magisk to patch the boot image even though it's on my 7" tablet. Any thoughts?
The bootloader was unlocked and it was successful so that's not the issue.
Click to expand...
Click to collapse
Sorry, been a busy few days, but make sure you're connected to Wifi, close Magisk Manager, then reopen it and you'll be good to go!

Onn 8" walmart tablet
I purchased the 8" Onn walmart tablet second hand from a store called dirt cheap. Box didnt look to be opened but it had been. The tablet had been setup with someones gmail account that i do not know. The tablet was for a 4yo girl to use to learn preschool. Is there just any simple way to remove this google FRP lock ? I dont care if i lose the info on it as its not mine. I just want her to be able to use the tablet. Any help would be much appreciated please

CoachDad said:
I purchased the 8" Onn walmart tablet second hand from a store called dirt cheap. Box didnt look to be opened but it had been. The tablet had been setup with someones gmail account that i do not know. The tablet was for a 4yo girl to use to learn preschool. Is there just any simple way to remove this google FRP lock ? I dont care if i lose the info on it as its not mine. I just want her to be able to use the tablet. Any help would be much appreciated please
Click to expand...
Click to collapse
Forced factory reset should do it. There is small pin hole near the power button. I believe pressing this hidden button(with a Sim card ejector, or paper clip).
If pressing does not do anything. Maybe press the button then hold power button too

mrmazak said:
Forced factory reset should do it. There is small pin hole near the power button. I believe pressing this hidden button(with a Sim card ejector, or paper clip).
If pressing does not do anything. Maybe press the button then hold power button too
Click to expand...
Click to collapse
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.

CoachDad said:
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
Click to expand...
Click to collapse
This is an mtk device not Samsung. So there is no Odin or download mode. There is spflash tool, and preloader.
And if you flash firmware (with default frp partition) then frp lock is cleared.
But you will have to find that file. It maybe in the stock firmwares that are shared, I do not know.

EDIT:
i was having issues but figure it out. maybe it should be so common knowledge that it shouldn't need to be included as a step, but since i don't do this THAT often i didn't think about it and it took me a bit to figure out why i was having issues.
once you get your computer to recognize your device (mine did without needing to mess with any drivers) you need to first make sure to got into the tablet settings -> about and then tap on the build number 7 times to access developer options. then you need to go into developer options and turn on OEM Unlocking & USB Debugging.
THEN follow the guide to unlock bootloader.
then (since the tablet is factory reset once you unlock) do the above AGAIN to turn USB Debugging back on after you reboot.
also note that you need to have an internet connection on the tablet to utilize magisk. once you got all that square, then continue on with steps for full root.
hope that helps!

byproxy said:
EDIT:
i was having issues but figure it out. maybe it should be so common knowledge that it shouldn't need to be included as a step, but since i don't do this THAT often i didn't think about it and it took me a bit to figure out why i was having issues.
once you get your computer to recognize your device (mine did without needing to mess with any drivers) you need to first make sure to got into the tablet settings -> about and then tap on the build number 7 times to access developer options. then you need to go into developer options and turn on OEM Unlocking & USB Debugging.
THEN follow the guide to unlock bootloader.
then (since the tablet is factory reset once you unlock) do the above AGAIN to turn USB Debugging back on after you reboot.
also note that you need to have an internet connection on the tablet to utilize magisk. once you got all that square, then continue on with steps for full root.
hope that helps!
Click to expand...
Click to collapse
I did not realize I didn't include that step. Total noob mistake when typing a tutorial up for android. I do this almost daily at work, so I forget to include it

CoachDad said:
Thank you for responding so fast. I've boot into recovery mode /wiped everything...its back to factory. The pinhole reset button does nothing other than reboot it . Ive tried all combos to with the reset button but nothing. Also i've read that its possible to use odin? if i can get it into download mode.
Ive downloaded the stock rom posted on an sdcard wondering if i can possibly update in recovery mode? Im sorta a newb at this stuff. I've been reading for 4 days on this matter. I've practiced a root on an old tablet with success. I guess at this point unless i can sell it as is giving the customer that it has this frp lock on it. If the know how to fix it so be it. Im not sure there is a working solution for frp bypass on these tablets.
Click to expand...
Click to collapse
I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot.

no worries! i didn't think about it either until i was having issues. thanks for the tutorial... it was super helpful!! btw it definitely works on the 8" tablet.

Hello! I'm new to all of this, but what I'm trying to accomplish is removing the Google account from this tablet and putting a new image on the ONA19TB002, ONA19TB003, ONA19TB007, Surf 7 and 10 tablets. I followed all of the steps as far as installing the drivers. I had to go through hoops to get the MediaTek Drivers installed, but I have a "warning" cone by it. I haven't been able to find any resolution to this. Any help would be appreciated. I' have a Windows 10 64-bit system that I'm using and the tablet I'm specifically working on at the moment is the ONN ONA19TB003 tablet. The tablet is not being recognized by my laptop when I run the 'fastboot devices' command in PowerShell. Is there something that I'm missing? Any help would be appreciated.

'Quis said:
Hello! I'm new to all of this, but what I'm trying to accomplish is removing the Google account from this tablet and putting a new image on the ONA19TB002, ONA19TB003, ONA19TB007, Surf 7 and 10 tablets. I followed all of the steps as far as installing the drivers. I had to go through hoops to get the MediaTek Drivers installed, but I have a "warning" cone by it. I haven't been able to find any resolution to this. Any help would be appreciated. I' have a Windows 10 64-bit system that I'm using and the tablet I'm specifically working on at the moment is the ONN ONA19TB003 tablet. The tablet is not being recognized by my laptop when I run the 'fastboot devices' command in PowerShell. Is there something that I'm missing? Any help would be appreciated.
Click to expand...
Click to collapse
Personally, I avoid PowerShell at all costs. This kinda stuff has always just seemed to work better with CMD.exe instead of Powershell.
These tablets are kind of a nightmare for this. If you've done the mediatek drivers and still have the warning cone icon, I'm not sure what's next as I haven't hit that wall myself. All I can maybe recommend is right click delete drivers in Device Manager, then start over with the driver install
Removing the Google Account would be needing a FRP Bypass. Someone above stated "I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot. " so if you can get it recognized, try that

KaptinBoxxi said:
Personally, I avoid PowerShell at all costs. This kinda stuff has always just seemed to work better with CMD.exe instead of Powershell.
These tablets are kind of a nightmare for this. If you've done the mediatek drivers and still have the warning cone icon, I'm not sure what's next as I haven't hit that wall myself. All I can maybe recommend is right click delete drivers in Device Manager, then start over with the driver install
Removing the Google Account would be needing a FRP Bypass. Someone above stated "I was able to remove FRP lock on one of mine by flashing the stock rom with SP Flash Tool. I used the full wipe and download selection with every partition selected including boot. " so if you can get it recognized, try that
Click to expand...
Click to collapse
Ok, thank you! This is a shot in the dark, but in order for ADB to work, USB debugging has to be enabled. I can't do that as the tablet is locked by FRP and I have looked countless times on Google and MSN to see if it's possible. Do you have any tips for that?

I don't know what I'm doing wrong, but for some reason I can't seem to get. The tablet to stay in fastboot mode. It just says waiting for device.

will this root onn 8 inch tablet running android 9

soateufel said:
I don't know what I'm doing wrong, but for some reason I can't seem to get. The tablet to stay in fastboot mode. It just says waiting for device.
Click to expand...
Click to collapse
Sorry for late reply. Been away from home with work. When fastboot mode indicates "waiting for device," it generally means that your device is not properly communicating with your PC or laptop. This is nearly always due to missing or incorrect drivers 9n your computer. There are several comprehensive guides here on XDA for installing necessary ADB & Fastboot drivers.

installed magisk manager on onn 8 and also have img zip but win i go to patch it magisk manager crashes

when you mean patch boot img do mean to unzip file on onn 8

Samsung Galaxy Tab A 8.0 SM-T290 2019, unable to unlock bootloader

Can anyone with this device provide the exact steps to unlock the bootloader. I have tried the many ways offered via google search and none seem to work. I have USB debugging and OEM unlock allowed in the device settings. I can boot into the bootloader via keys and using ADB. I've tried various key combos to get to the page (supposedly available) that allows one to switch the bootloader from locked to unlocked - no luck.
All help appreciated.

Do you mean that the command fastboot oem unlock doesn't work?
Note that: Unlocking bootloader wipes all device's data!

XDHx86 said:
Do you mean that the command fastboot oem unlock doesn't work?
Note that: Unlocking bootloader wipes all device's data!
Click to expand...
Click to collapse
Thanks for your reply and new suggestion. No that does not work either. I go to bootloader download mode, enter the command "fastboot oem unlock" and get "waiting on device". I am connected to the device as I get a response when queried "adb devices". Any other thoughts/suggestions?

[email protected] said:
Thanks for your reply and new suggestion. No that does not work either. I go to bootloader download mode, enter the command "fastboot oem unlock" and get "waiting on device". I am connected to the device as I get a response when queried "adb devices". Any other thoughts/suggestions?
Click to expand...
Click to collapse
You're supposed to boot the device to fastboot/bootloader by adb reboot bootloader not download mode.
Also to detect the device in fastboot the command is fastboot devices
Please if you're new to this stuff then don't do it. May I ask why you're trying to unlock bootloader?

XDHx86 said:
You're supposed to boot the device to fastboot/bootloader by adb reboot bootloader not download mode.
Also to detect the device in fastboot the command is fastboot devices
Please if you're new to this stuff then don't do it. May I ask why you're trying to unlock bootloader?
Click to expand...
Click to collapse
Again, thanks for your reply. I have previously installed Lineage on a Fire HD8. So not quite a newbie but everyone is new once - right? I am trying to install Lineage on this SM-T290.
The command "fastboot devices" is not returning anything but "adb devices" does which leads me to believe my hardware connections are correct. "adb reboot bootloader" does take me to the bootloader but it indicates download mode.
I suspect I am missing something simple. Your help is appreciated. Thanks

You need to enable OEM unlock and debugging mode first. And make sure the PC is allowed to debug on your phone.
Also if fastboot command doesn't return anything then most likely you need the correct device driver, you can get it from here.
Alternatively you can try this method:
Boot to download mode.
Long press volume up. This will wipe your data and automatically reboot.
After reboot you should have unlocked bootloader and OEM unlock option greyed out in the settings.
Installing custom ROM doesn't make your device better.

XDHx86 said:
You need to enable OEM unlock and debugging mode first. And make sure the PC is allowed to debug on your phone.
Also if fastboot command doesn't return anything then most likely you need the correct device driver, you can get it from here.
Alternatively you can try this method:
Boot to download mode.
Long press volume up. This will wipe your data and automatically reboot.
After reboot you should have unlocked bootloader and OEM unlock option greyed out in the settings.
Installing custom ROM doesn't make your device better.
Click to expand...
Click to collapse
Thanks but still no go.
I have enabled usb debugging and enabled OEM unlock (both done previously)
I have (had) installed latest drivers previously
adb devices returns my unit data
adb reboot bootloader command puts device in "download mode !!"
fastboot devices returns "waiting on device"
fastboot oem unlock also returns "waiting on device"
Attempted your alternative method, no go
I understand custom ROM doesn't make device better. I like the learning challenge. Hope you understand. Appreciate your help thus far and any other ideas you might have.

This is 100% driver issue, I already provided the driver link.
The device driver may be different from internet provided driver through windows device manager. Or the driver installed upon connecting the device.

XDHx86 said:
This is 100% driver issue, I already provided the driver link.
The device driver may be different from internet provided driver through windows device manager. Or the driver installed upon connecting the device.
Click to expand...
Click to collapse
Thanks. I had installed a driver from the link you supplied (there were a few options). I'll try others. I appreciate all your help!

Here's how I did it.
Enable Developer mode, usb debug, OEM unlock (you've already done those, by the sound of things).
Power the tablet OFF.
Have your USB cable plugged into the computer but NOT the tablet.
Hold the volume up AND volume down keys simultaneously, then connect the USB cable.
The tablet will vibrate and show a blue-green screen, with Warning at the top and a white triangle with an exclamation mark at the bottom. (This is different from download mode.)
From here, long-press volume up to go into device unlock mode. Follow the instructions.

Heeni said:
Here's how I did it.
Enable Developer mode, usb debug, OEM unlock (you've already done those, by the sound of things).
Power the tablet OFF.
Have your USB cable plugged into the computer but NOT the tablet.
Hold the volume up AND volume down keys simultaneously, then connect the USB cable.
The tablet will vibrate and show a blue-green screen, with Warning at the top and a white triangle with an exclamation mark at the bottom. (This is different from download mode.)
From here, long-press volume up to go into device unlock mode. Follow the instructions.
Click to expand...
Click to collapse
Thanks again but no luck. Let's start with some basics:
My device is a Galaxy Tab A SM-T290 8.0 2019 one UA core version 2.1
Android 10
When I, with power off, press both UP & DOWN volume keys simultaneously, wait a few seconds, insert the USB cable (already in computer), I get a vibration but then a circle with a lightning bolt that shows the battery charge status. The screen does not go blue-green and there is no warning.
I have tried releasing the buttons after the vibration and after I see the battery power circle. No change.
I continue to appreciate your help but feel I am missing something simple or my device is not same as yours.
Let me know if you have given up!

[email protected] said:
Thanks again but no luck. Let's start with some basics:
My device is a Galaxy Tab A SM-T290 8.0 2019 one UA core version 2.1
Android 10
When I, with power off, press both UP & DOWN volume keys simultaneously, wait a few seconds, insert the USB cable (already in computer), I get a vibration but then a circle with a lightning bolt that shows the battery charge status. The screen does not go blue-green and there is no warning.
I have tried releasing the buttons after the vibration and after I see the battery power circle. No change.
I continue to appreciate your help but feel I am missing something simple or my device is not same as yours.
Let me know if you have given up!
Click to expand...
Click to collapse
I see that your tablet has One UA core.
That may make a difference. I can't remember now where I saw it (somewhere on these forums), but I recall seeing that One UI Core is more locked down than the "ordinary" One UI version. Incidentally, I get the same response as you if I plug the tablet into a charger (not computer) while pressing both volume keys.
I'll mention at this point that I'm on the point of going back to stock and relocking the bootloader, because I've not been able to have a custom ROM or recovery and a screenlock (PIN, password, or pattern) at the same time, and no one seems to know any workaround for this. I'm starting to wonder if my tablet is somehow odd.
It's a nice piece of hardware, but a right pain to do any mods to, and Samsung's extra security "features" can cause problems.

Heeni said:
I see that your tablet has One UA core.
That may make a difference. I can't remember now where I saw it (somewhere on these forums), but I recall seeing that One UI Core is more locked down than the "ordinary" One UI version. Incidentally, I get the same response as you if I plug the tablet into a charger (not computer) while pressing both volume keys.
I'll mention at this point that I'm on the point of going back to stock and relocking the bootloader, because I've not been able to have a custom ROM or recovery and a screenlock (PIN, password, or pattern) at the same time, and no one seems to know any workaround for this. I'm starting to wonder if my tablet is somehow odd.
It's a nice piece of hardware, but a right pain to do any mods to, and Samsung's extra security "features" can cause problems.
Click to expand...
Click to collapse
Hey! Once again want to thank you for hangin' in with me on this. So, it seems we have slightly different machines. I purchased mine at COSTCO. They offer a lot of good stuff at low prices. I've noticed, however, they tweak their offerings a little bit so they can honestly say "you can't get this somewhere else." Perhaps the difference in our machines explains that.
I definitely had my unit plugged into the USB port on my computer, not a power supply.
My only purpose in attempting this was the satisfaction of doing it and having two tablets with different operating systems.
Thanks again for your help. All the best!

Here's the reference to One UI Core that I was thinking of: https://forum.xda-developers.com/t/root-for-sm-t290-tab-a-8-0-2019.3965624/post-84355183
I'm not based in North America, and the local market isn't big enough to have retailer-specific variants (or, at least, I've never heard of any), so I probably have a standard item. But from what I've read, specially locked-down items are reasonably common in the US. Which doesn't make it any less frustrating.

Heeni said:
Here's the reference to One UI Core that I was thinking of: https://forum.xda-developers.com/t/root-for-sm-t290-tab-a-8-0-2019.3965624/post-84355183
I'm not based in North America, and the local market isn't big enough to have retailer-specific variants (or, at least, I've never heard of any), so I probably have a standard item. But from what I've read, specially locked-down items are reasonably common in the US. Which doesn't make it any less frustrating.
Click to expand...
Click to collapse
I read the post and tried the extra step of holding the up volume key when the power screen came on. It also didn't work. Unless something new shows up, my quest to unlock this bootlocker is over. I'll find some other technical challenge to chase.
I had the thought of contacting Samsung to see if they would tell me how to do this. My unit is well out of warranty so why should they care? Likely they wouldn't tell me anything but .....
I'm on Denver CO. Where are you? In my work and fun travels I've had the opportunity to visit many parts of the world. Perhaps I've been to your country?
Again thanks for all your help. I could not have gotten as far as I did without it.

I'm in Auckland, New Zealand. It's a good place to live but not if you want cheap tech. Freight costs tend to be high.

Heeni said:
I'm in Auckland, New Zealand. It's a good place to live but not if you want cheap tech. Freight costs tend to be high.
Click to expand...
Click to collapse
Never been to New Zealand. On the bucket list as it seems a beautiful place to live. Been to your close neighbor Austrailia a number of times. Want to go there again to snorkel on the barrier reef. All the best!

[email protected] said:
I read the post and tried the extra step of holding the up volume key when the power screen came on. It also didn't work. Unless something new shows up, my quest to unlock this bootlocker is over. I'll find some other technical challenge to chase.
I had the thought of contacting Samsung to see if they would tell me how to do this. My unit is well out of warranty so why should they care? Likely they wouldn't tell me anything but .....
I'm on Denver CO. Where are you? In my work and fun travels I've had the opportunity to visit many parts of the world. Perhaps I've been to your country?
Again thanks for all your help. I could not have gotten as far as I did without it.
Click to expand...
Click to collapse
Try method below. It worked for me.
Root for SM-T290 (tab a 8.0 2019)
Hi guys, I just bought an SM-T290 for my wife and I was unable to find any info here about rooting it. As most Tab-A tablets "are here", can I use a guide (and twrp) for an older tablet for this newer model?
forum.xda-developers.com

bignikescar said:
Try method below. It worked for me.
Root for SM-T290 (tab a 8.0 2019)
Hi guys, I just bought an SM-T290 for my wife and I was unable to find any info here about rooting it. As most Tab-A tablets "are here", can I use a guide (and twrp) for an older tablet for this newer model?
forum.xda-developers.com
Click to expand...
Click to collapse
Holding vol up and down, with the tablet off, and plugging in the USB from PC to tablet, works. And it makes no difference which end of the cable you plug in last, so long as the buttons are already pressed before both ends are attached.

XDHx86 said:
Do you mean that the command fastboot oem unlock doesn't work?
Note that: Unlocking bootloader wipes all device's data!
Click to expand...
Click to collapse
You do not need a PC to unlock the bootloader. Turn off the device, then you will want to do Volume Up + Volume Down + USB Cable, and then Long Press Volume Up, and then press Volume Up again.

ROOT SM-T555 Nougat (Android 7.1.1)

Hello...
I am looking for a working way to root my SM-T555
The device is running android 7.1.1;
base ver. "T555XXU1CQHA";
build ver. "NMF26X.T555XXU1CRG1";
Samsung experience 8.5;
Android security patch August 2017.
So far, the several attempts I made using every T55X related software I found in this website have been unsuccessful.
It would seem that the rooting software available is for "Marshmallow only", thus not Nougat specific,
though I read some comments stating that the TWRP made for MM worked on Nougat too and, after that, Magisk would/could do the job...
So I gave it a try but, after installing the recovery, my tablet got stuck every time: refused to boot normally
and if I turned it off, long pressing the power key, I couldn't turn it on again as if it was bricked.
Every time I had to re-start it in download mode and re-flash the original stock rom with Odin in order to have it working again.
On top of that, the "OEM unlock" key is not present in the developer mode list: none of the "date changing tricks" I found around the web seems to fit this model.
I am inclined to believe this "might" be the mother of my problems in rooting the device though, supposedly, the patches were not for Nougat, anyway...
The developer options page, once activated, can only be "turned off" ("greyed out") but cannot be deactivated;
while, on other devices, if you turn it off the page usually disappears after rebooting then you have to tap 7 times the build version, again, in order to make it appear.
I never had problems in rooting any of the phones and tablets I have /had, including an SM-T819 running Nougat 7.1.1,
thanks to the great job done by the coders in this community to whom I would like to express my appreciation for what they do for the benefit of us all.
But this thing seems to reject everything I throw at it and it's been the most stubborn "phone like object" I ever fought with.
So far I am the one loosing the fight... I wish some of you guys could give me the means to defeat it.
Thanks in advance to whoever may be available to help me out.

Flash TWRP, then install Magisk in TWRP.

V0latyle said:
Flash TWRP, then install Magisk in TWRP.
Click to expand...
Click to collapse
thanks for your reply.
maybe my post was too long and boring so you didn't read it all
Of course I already tried the solutions posted in the page you suggested but they did not work.
not the autoroot files, not the recovery, etc...
I quote: "after installing the recovery, my tablet got stuck every time: refused to boot normally
and if I turned it off, long pressing the power key, I couldn't turn it on again as if it was bricked.
Every time I had to re-start it in download mode and re-flash the original stock rom with Odin in order to have it working again."
If there is a TWRP file specific for my Nougat version available I'd be happy to give it a shot

endlessquest said:
thanks for your reply.
maybe my post was too long and boring so you didn't read it all
Of course I already tried the solutions posted in the page you suggested but they did not work.
not the autoroot files, not the recovery, etc...
I quote: "after installing the recovery, my tablet got stuck every time: refused to boot normally
and if I turned it off, long pressing the power key, I couldn't turn it on again as if it was bricked.
Every time I had to re-start it in download mode and re-flash the original stock rom with Odin in order to have it working again."
If there is a TWRP file specific for my Nougat version available I'd be happy to give it a shot
Click to expand...
Click to collapse
Did you follow a guide when flashing TWRP? Did you unlock your bootloader?
You need to be clear and concise in your posts as yo what you did and how.

V0latyle said:
Did you follow a guide when flashing TWRP? Did you unlock your bootloader?
You need to be clear and concise in your posts as yo what you did and how.
Click to expand...
Click to collapse
of course I did follow the guide by the book. also, the recovery appears to be installed properly, Odin showing a nice green PASS sign, but it doesn't work anyway
now about unlocking the bootloader, as I mentioned in my first post:
"the "OEM unlock" key is not present in the developer mode list: none of the "date changing tricks" I found around the web seems to fit this model.
I am inclined to believe this "might" be the mother of my problems in rooting the device"
every time I had to re install the system, so there clock want back to zero. Maybe I should be waiting for the allotted number of days to pass on order for the OEM unlock key to appear...
but before my first attempt to root the device, almost one month was past and the OEM unlock key wasn't there, notwithstanding...
I hope there was a chance that the bootloader was already unlocked...

to be concise (schematic):
tablet in download mode
untick auto reboot in Odin
AP loaded with "smt550_cf-autoroot.tar"
flash with Odin, OK, green sign PASS
reboot manually home+volume down+power,
then switch to volume up when screen becomes black
the Samsung logo appears and stays there indefinitely
So I turn the device off, long pressing the power key
then I try and turn on the tablet but does not turn on anymore,
not even pressing the power button for 30 second
then I press home+volume down+power again
to enter download mode and reinstall stock rom
(the same happens with
sm-t550_p550_p555_cf-autoroot.tar
or twrp_3.0.2-1_sm-t550_mm_7816.tar,
I also tried
twrp_3.1.1-1_sm-t355_251117
remark: none of them mentions T555 nougat)

Put your tablet in Download Mode and take a picture of the text at the upper left of the screen.

V0latyle said:
Put your tablet in Download Mode and take a picture of the text at the upper left of the screen.
Click to expand...
Click to collapse

What process did you follow to unlock your bootloader?
Stop trying to use Autoroot. Let's figure out what we need to do to get TWRP on your device. Once we do that, you can flash Magisk in TWRP for root.
Please read this guide, sections 1 through 4 (don't worry about the GSI stuff) and tell me what you have or have not done.

ok, I wasn't able to do this:
Unlock Bootloader
Enable Developer Options and turn on OEM Unlocking
OEM Unlocking is missing in the list, as I mentioned in my previous posts
I tried the date change trick but it didn't work

endlessquest said:
ok, I wasn't able to do this:
Unlock Bootloader
Enable Developer Options and turn on OEM Unlocking
OEM Unlocking is missing in the list, as I mentioned in my previous posts
I tried the date change trick but it didn't work
Click to expand...
Click to collapse
This is the first step. You cannot flash custom or modified images if the bootloader is locked.
Connect to the Internet and check for updates in system options, then check Developer Options again.

I did that step too, several times:
the system found an update available
the first times I cancelled the download
then I downloaded the update without installing it
then I tried and installed it
no result at all the attempts: the OEM Unlock key does not appear in developer options

endlessquest said:
I did that step too, several times:
the system found an update available
the first times I cancelled the download
then I downloaded the update without installing it
then I tried and installed it
no result at all the attempts: the OEM Unlock key does not appear in developer options
Click to expand...
Click to collapse
Has it ever appeared before?

V0latyle said:
Has it ever appeared before?
Click to expand...
Click to collapse
it is the first time I work on this specific device, so I couldn't tell: so far I couldn't find the OEM unlock option in the list
it never happened before on any of the several devices I have rooted in my life,
included another Samsung tablet SM-T819 running Nougat 7.1.1: the option was right there and all I had to do is tick it.
I used fastboot for other brands
I wish there was a way to use fastboot to unlock the bootloader on Samsung
if there is any I don't know it
adb is working, but when I give the "adb reboot fastboot" command, the tablet enters the download mode and fastboot does not see the tablet anymore from the computer

endlessquest said:
it is the first time I work on this specific device, so I couldn't tell: so far I couldn't find the OEM unlock option in the list
it never happened before on any of the several devices I have rooted in my life,
included another Samsung tablet SM-T819 running Nougat 7.1.1: the option was right there and all I had to do is tick it.
I used fastboot for other brands
I wish there was a way to use fastboot to unlock the bootloader on Samsung
if there is any I don't know it
adb is working, but when I give the "adb reboot fastboot" command, the tablet enters the download mode and fastboot does not see the tablet anymore from the computer
Click to expand...
Click to collapse
Samsung devices do not have a fastboot mode.
Since this is a Snapdragon device, it probably cannot be unlocked, especially if it was marketed in the US.
Only Exynos and international Snapdragon devices can be unlocked, unfortunately.

V0latyle said:
Samsung devices do not have a fastboot mode.
Since this is a Snapdragon device, it probably cannot be unlocked, especially if it was marketed in the US.
Only Exynos and international Snapdragon devices can be unlocked, unfortunately.
Click to expand...
Click to collapse
actually I am in Rome, Italy so I am quite positive it was marketed here...
is there a way to know for sure whether or not it is international?

the Samsung SM-T819 I am writing from has a snapdragon chip
but I had no problem unlocking/rooting it,
I bought both the devices here in Rome
now that's a mystery...

endlessquest said:
actually I am in Rome, Italy so I am quite positive it was marketed here...
is there a way to know for sure whether or not it is international?
Click to expand...
Click to collapse
Usually the model number is a good indication with phones - the G908U vs G908N for example, but I don't see that being the case here
Have you tried signing into a Samsung or Google account on the device before checking for updates and looking for OEM Unlocking?

V0latyle said:
Usually the model number is a good indication with phones - the G908U vs G908N for example, but I don't see that being the case here
Have you tried signing into a Samsung or Google account on the device before checking for updates and looking for OEM Unlocking?
Click to expand...
Click to collapse
I did that too...
on a freshly installed rom:
I connected the internet thru wireless
signed into my Google account
completed the tablet configuration, etc
then I went and enable the developer options
no OEM Unlocking yet again...

endlessquest said:
I did that too...
on a freshly installed rom:
I connected the internet thru wireless
signed into my Google account
completed the tablet configuration, etc
then I went and enable the developer options
no OEM Unlocking yet again...
Click to expand...
Click to collapse
You manually checked for an update too?
Did you try disconnecting from the Internet, disabling network time, and manually setting the time ahead 1 week?