Database Users

I could use some help with my nexus 7

I've tried to flash custom ROMs on my nexus 7, 3 times now, each time has the same result. I flash the ROM, then the Gapps and wipe data/cache. What happens afterwards is an endless boot cycle and a frozen bootloader (after rebooting into bootloader pressing up and down do nothing, neither does power button.) So i pull the battery and reboot into bootloader, now it works. This time it is a little different. Usually I can go into CMD and re flash stock, fallowing the instructions on this forum. This time when I try the command "adb reboot bootloader" I get "Failed to find device",even tho my computer recognizes it as an "Android ADB Interface." So I decided to try and re install my ADB drivers and I get "Failed to handshake device' or something along those lines.
My bootloader also reads a little differently than usual so I'll list the information below, it might be helpful.
"Product name - grouper
Variant - not defined yet
HW version - ER3
Baseband version - N/A
Signed - not defined yet
Lock state - unlocked'"
So I'm stuck with a nexus 7 in bootloader and my computer is not able to connect to it. Any help would be nice. I've already tried fallowing the returning to stock guide 3 times so please don't give me a bunch of **** about that.
Help would be nice, information/instructions would be amazing. Please help.

CptHoovsen said:
Help would be nice, information/instructions would be amazing. Please help.
Click to expand...
Click to collapse
After you boot into the boot loader, Windows sees the device name as Grouper - and there is no Windows driver for Grouper.
Try to find a Linux system to connect with. Linux is much less picky about device names.

[Q] New Nexus 7, Win 7, Nexus 7 Toolkit can't boot into Fastboot, "Too Many Links"

[Q] New Nexus 7, Win 7, Nexus 7 Toolkit can't boot into Fastboot, "Too Many Links"
SOLVED!
So I went ahead, tried flashing the stock recovery, no joy (no recovery menu at all - just a bad-android image). After a while, tried flashing CWM touch (via Toolkit) - and now it's working. So, everything seems good now.
----------------
UPDATE 5 - PARTIALLY SOLVED:
So, after the last couple of things, I began to suspect bad hardware, as I alluded in those updates. And I was right.
But... it wasn't the hardware you might have thought.
It was...
(this is embarrassing)
The USB cable.
Yes, the USB cable. It was the wild variations in recognizing the fastboot mode that made me suspicious. Replaced the USB cable with another one and... stability, achieved. Unlock, root, recovery program and SU program all went without a hitch. In fastboot mode, for the first time, the device serial number shows.
HOWEVER - things are not perfect. The recovery mode from the bootloader still gives the bad-android icon.
I just used the toolkit to reflash stock recovery back to the device. This completed rapidly, without error. I then tried the recovery option in the bootloader, but again, no joy.
So at this point, I point a finger partly at the tools used to flash this - they claim there is no problem, yet the flash doesn't take at all, and no error is given. As a sometimes firmware developer, I'm used to flash being followed up by a checksum or other test to verify success of the flash. Is that not being done (shame, if not). If it is, then apparently the flash works, but the software being flashed doesn't? The stock recovery???
Any ideas on how to get this back? I just did the full unlock, which wiped all user data, and proceeded from there. I now have a solid connection, but don't really know how to get things back.
Perhaps I need to manually reinstall 4.2.2?
----------------
UPDATE 4:
So, on a lark, from fastboot in Android, I selected the "Recovery" option - it starts to boot that, then gives the Android with red triangle and exclamation point. So, looks like the recovery was toasted.
This was a brand new device earlier today. It has been completely wiped twice, and none of this has gone away. Seriously: bad device?
-----------------------
UPDATE 3:
So, I thought I'd try the direct approach, as outlined here:
http://forum.xda-developers.com/showthread.php?t=1741395
Device is in Fastboot, Device Manager shows it as ok.
I run fastboot flash recovery <file> -- and IMMEDIATELY get "fastboot has stopped working" - that's right, a hard crash in fastboot. And this is repeatable.
Am I wrong in thinking this looks more and more like a driver problem? I note that fastboot is recognized as a device maybe half the time - the other half, it gets an exclamation point in Device Manger. All I do then is restart the bootloader using the bootloader menu, and usually it fixes right up. But that's obviously a huge red flag, as the device should be recognized every time.
Is this a defective Nexus? The only thing that seems dicey is anything relating to fastboot/bootloader (which is, however, unlocked - or at least it says it is).
----------------
UPDATE 2: Using the "restart bootloader" in fastboot results in slightly worse non-recognition of the device. When I do that, I get a straight "USB Device Not Recognized" from windows - the device manager doesn't even show "Android Phone" as a class of device in this case.
---------------------
UPDATE 1: I found the thread talking about missing entries in the INF file. I added these, and got a somewhat, but not entirely, stable recognition of the Nexus 7 when in fastboot mode. Basically, sometimes it is recognized, other times it is not. By "recognized", I mean that the Windows Device Manager shows the device as "Android Bootloader Interface", with no indication of a problem (which it only does in fastboot mode - it shows as a composite ADB device when booted normally).
However - it seems it fails to recognize fastboot about half the time, although it seems that that is related to reboots - that is, a fresh boot, then going to fastboot through adb seems to work. But restarting fastboot manually fails to be recognized (Windows shows a bang by the "Android Bootloader Interface", and says the device "failed to start").
So, using 4.3.5 Nexus 7 toolkit, I tried to unlock the bootloader. Windows recognized fastboot mode, but the process errored out anyway, after maybe 15 seconds, saying "Too Many Links" - the same error as before.
Again, brand new 32gb wi-fi-only Nexus 7, with 4.2.2 update and the most basic configuration only (dev mode, usb on, etc.)
Any ideas?
-------------------------------------------------------
ORIGINAL
So this is a new, out of the box nexus 7. The only setup has been to connect to wifi, update to 4.2.2, and enable developer mode and USB debugging.
Running latest paid-for toolkit - Update 29 Feb 13, version 4.3.5
Just about everything requires the insecure fastboot, but every time I try any operation that attempts it, I get:
Booting into fastboot mode
downloading 'boot.img' ...
FAILED <status read failed <Too many links>>
I basically can't do anything - in this case, I was trying to backup.
It is being done on 64-bit win7 system that had drivers, and worked for another nexus 7 a couple months ago. But, just to be safe, I uninstalled the drivers, rebooted, and installed.
However, I see this on the home page of the toolkit:
FASTBOOT MODE [If serial shows, drivers are installed]
List of Devices attached
ADB Mode
List of devices attached
<numeric code> device
From this, it seems I should expect the word "serial" to show up if the drivers are installed?
I then unplugged the Nexus, refreshed the menu, and both Fastboot and ADB show no devices.
I then plug in the nexus - I get the usual two tone "device attached" sound, no warning or error message from Windows.Checking the Windows device manager, I see a section "Android Phone" with the entry "Android Composite ADB Interface". There are no unknown devices, which would seem then that drivers are working.
So, another refresh of the main menu, and again, I see, under ADB MODE, a single device ID number, and the word "device".
I don't know what to make of this. Apparently, per the "if serial shows" message in the main menu, drivers a NOT installed. But according to Windows, they are.
This perhaps matches the fastboot failure.
Should I see "serial"?
In any case, what do I do to get the drivers to work properly if they aren't?
And if they ARE working, then what is wrong with fastboot?
At this point, I think the toolkit is broken, and worked a couple months ago.

No, you should not see "serial". Your devices serial number should be displayed under whichever path is valid at that time. If you are in the bootloader, your device serial number should be under "fastboot". If you are booted normally, your device serial number should be under "ADB".
I used this guide:
http://forum.xda-developers.com/showthread.php?t=1741395&highlight=guide

Erik.Leach said:
No, you should not see "serial". Your devices serial number should be displayed under whichever path is valid at that time. If you are in the bootloader, your device serial number should be under "fastboot". If you are booted normally, your device serial number should be under "ADB".
I used this guide:
http://forum.xda-developers.com/showthread.php?t=1741395&highlight=guide
Click to expand...
Click to collapse
I've since figured that out. There was nothing at all, when in fastboot mode, only ADB. But then I found the thread describing two missing INF entries. I added those, updated the driver, and now the fastboot mode (which wasn't even recognized by windows) is now ok in the Device Manager. However, in the main menu, it shows, literally, "??????????" instead of a serial number - that is, there are question marks instead of serial number, Following that, a few spaces and then "fastboot".
Apparently, there are still inadequacies in the driver as relates to very, very new models running 4.2.2 (which this is).

BTW, I do believe I read somewhere that the stock recovery initially comes up with just the android on his back with the warning sign. You then have to hold power and tap volume up or something like that and the recovery menu becomes visible. I could be wrong, I know I had to do this on my old GNex, and those were the steps that worked.

Erik.Leach said:
BTW, I do believe I read somewhere that the stock recovery initially comes up with just the android on his back with the warning sign. You then have to hold power and tap volume up or something like that and the recovery menu becomes visible. I could be wrong, I know I had to do this on my old GNex, and those were the steps that worked.
Click to expand...
Click to collapse
Interesting. I did re-flash the stock recovery, and could get that without the android image.

stickplayer said:
Interesting. I did re-flash the stock recovery, and could get that without the android image.
Click to expand...
Click to collapse
That may have been a GNex thing that I am remembering. Either way, I'm glad you got everything all straightened out. :good:
I'm still kinda new at this stuff too, but if you need any more help, feel free to hit me up. Even if I don't know the answer to the question, I'll help you find it.

Erik.Leach said:
That may have been a GNex thing that I am remembering. Either way, I'm glad you got everything all straightened out. :good:
I'm still kinda new at this stuff too, but if you need any more help, feel free to hit me up. Even if I don't know the answer to the question, I'll help you find it.
Click to expand...
Click to collapse
Thanks! Next is trying to put 4.x on a Samsung Vibrant.

Possibly dead boot MP Rio, Help/Suggestions Please T.T

So apparently, I went home and usually put my phone into my desk.
While I took it from my pocket, I noticed the hardware buttons were lit but no display, I removed the battery to restart, during the week, frozen screen were occurring a dozen times when playing Clash, that though I didn't mind I just said to myself I will reflash the rom in the weekend.
But up to now,
It won't turn on, recovery mode or anything also doesn't work
It wont charge
Tried a new battery but still no luck
I think PC reads it but SPFT wont
Any suggestion on how I can revive my phone?
Attached is the error I get from SPFT

I don't own the A120 anymore. That is almost similar to this, as you might know.
Anyway, as nobody has answered your question, I will try to help as much as I can.
Does it give you a haptic feedback(vibration) when you try to power on the device?
Are you saying that it won't turn on completely?
If it is being detected on the computer and not on SPFT, you might want to check with the drivers you have. Do you have the MTK VCOM drivers installed? (I'm not really sure about the name, but it was something like that).
And try flashing the Stock ROM with SPFT with your battery removed from the phone.
Download the drivers.
Connect your phone without the battery and keep your device manager open, if it shows a device with a yellow exclamation mark beside it, right click and click on properties. You will have to do this quickly.
Once that is done, go to driver tab on the properties window. Select Update Driver. Browse my computer and enter the location of your downloaded and unzipped drivers.
(You might get a digital signature error or something similar. I'll tell you how to bypass that in the end. If you get that, go to the end, follow those steps and then come back and do all the steps after the downloading part.)
If the drivers are successfully installed, then unplug your device, run the SPFT and load the Scatter file of the Stock ROM.
Now select Download only and start the download, it will wait for you to connect the phone.
Plug in your phone without the battery. This should initialize the download process.
Now wait for the flash to be completed and if it is successful, take out your phone and boot it. If it boots up, congratulations.
If it does not, flash the same ROM the same way another time and check, if it is still not working, try with Firmware upgrade mode, twice. It should work in those tries.
Digital Signature Error bypassing.
I know only one method which works on Windows 8 and above(Tested).
Hold the Shift key while pressing Reboot.(Yes, you have to reboot your PC)
Once there is a blue screen with options, you should see "Troubleshoot". Select that.
Then Advanced Options and then Start Up settings. Then press Restart.
This will show you a menu with a lot of options. Select the option number which says "Disable Driver Signature Enforcement".
This will log you into the PC normally, but now, you can go back and do all the steps again and you won't get an error.
Cheers!
If this still doesn't help you, let me know on what happens so I can try to get you back your phone. Hope this helps.

WalterWh1te said:
I don't own the A120 anymore. That is almost similar to this, as you might know.
Anyway, as nobody has answered your question, I will try to help as much as I can.
Does it give you a haptic feedback(vibration) when you try to power on the device?
Are you saying that it won't turn on completely?
If it is being detected on the computer and not on SPFT, you might want to check with the drivers you have. Do you have the MTK VCOM drivers installed? (I'm not really sure about the name, but it was something like that).
And try flashing the Stock ROM with SPFT with your battery removed from the phone.
Download the drivers.
Connect your phone without the battery and keep your device manager open, if it shows a device with a yellow exclamation mark beside it, right click and click on properties. You will have to do this quickly.
Once that is done, go to driver tab on the properties window. Select Update Driver. Browse my computer and enter the location of your downloaded and unzipped drivers.
(You might get a digital signature error or something similar. I'll tell you how to bypass that in the end. If you get that, go to the end, follow those steps and then come back and do all the steps after the downloading part.)
If the drivers are successfully installed, then unplug your device, run the SPFT and load the Scatter file of the Stock ROM.
Now select Download only and start the download, it will wait for you to connect the phone.
Plug in your phone without the battery. This should initialize the download process.
Now wait for the flash to be completed and if it is successful, take out your phone and boot it. If it boots up, congratulations.
If it does not, flash the same ROM the same way another time and check, if it is still not working, try with Firmware upgrade mode, twice. It should work in those tries.
Digital Signature Error bypassing.
I know only one method which works on Windows 8 and above(Tested).
Hold the Shift key while pressing Reboot.(Yes, you have to reboot your PC)
Once there is a blue screen with options, you should see "Troubleshoot". Select that.
Then Advanced Options and then Start Up settings. Then press Restart.
This will show you a menu with a lot of options. Select the option number which says "Disable Driver Signature Enforcement".
This will log you into the PC normally, but now, you can go back and do all the steps again and you won't get an error.
Cheers!
If this still doesn't help you, let me know on what happens so I can try to get you back your phone. Hope this helps.
Click to expand...
Click to collapse
Thanks bro, but I already gave up and bought a new one because I badly need an android device for my mini accounts in CoC. Haha but I am till trying to revive my Rio during my free time, this has been my phone for 1 1/2 year..
Yes I am aware that Rio is rebranded A120, I also asked from CM12.1 and AOSP LP Wiko Rainbow threads and some suggested help. Tried all that but still same errors.
No, there's no response of any kind including vibration when turning on. Hmn, as per the drivers, I've been using Tinno Driver since the jelly bean era of this phone, no problems or whatsoever from jb to kk to lp using that driver, so I thought there would be no problems. Still no luck in getting success. Using different versions of SPFT, using sp flashable Rio jb, kk, MMX A120 jb, kk, Wiko kk,lp stock roms, still no luck. Tried every port and cord. And I am using the Win7 64bit, I also resorted to MTK drivers, both the preloader and Da. Still.. No luck. Haha. I also tried, download only, format all+download, and firmware upgrade option with every possible combination from above but no success..
Thanks for your answer btw!

Newbie trying (and failing so far) at my first root

Hi all,
First message in this wonderful community.
Anywas, having owned a Galaxy Note 3 for a few years now I thought I'd give it a shot at installing a new ROM to get it in better shape and try to stay with it a bit longer. Nothing really wrong with the phone other than getting a bit sloooow, specially the camera.
Anyways, not being a very geeky person, I soon realized the learning curve is steep.
This is what I've done so far:
1) Identified the model (SM-N9005)
2) Downloaded and unzip the SDK platform tools
3) Downloaded the TWRP custom recovery
4) Unlocked developer tools, allow unknown source (not sure if that is needed) and allowed USB debugging. In this phone I think there is no option for OEM unlocking.
5) Installed latest Samsung USB driver
5) Tried to proceed with unlocking the bootloader. This is where I ran into issues:
- I installed ADB Installer saying YES to everything
- Connected phone to pc with a usb cable
- From the command prompt (in my user) I executed adb reboot bootloader. I initially got an error (something about daemon and a port?....) but was able to move ahead
- The green android logo appeared along with this message "Downloading ...Do not turn off target!!"
At this point, pressing the volume down, power and select at the same time I tried to get out but kept on coming back to the same android menu stuck in "Downloading ...Do not turn off target!!". After the third try, a new warning message came up asking me if I want to proceed or reboot phone (pressing volume down) and I rebooted the phone to "escape" this predicament. I thought I was going to brick the thing!
Anyways, any recommendations on how to proceed? Is there an easier method to root the phone? Or to circumvent the issue I encountered?
As you might have guessed by my message, I can (sometimes) follow instructions but the underlying knowledge of what I am doing is .... well ...missing? :silly:
Hope you guys can help me. Thank you all in advance for your assistance.

PierreBCN said:
Hi all,
First message in this wonderful community.
Anywas, having owned a Galaxy Note 3 for a few years now I thought I'd give it a shot at installing a new ROM to get it in better shape and try to stay with it a bit longer. Nothing really wrong with the phone other than getting a bit sloooow, specially the camera.
Anyways, not being a very geeky person, I soon realized the learning curve is steep.
This is what I've done so far:
1) Identified the model (SM-N9005)
2) Downloaded and unzip the SDK platform tools
3) Downloaded the TWRP custom recovery
4) Unlocked developer tools, allow unknown source (not sure if that is needed) and allowed USB debugging. In this phone I think there is no option for OEM unlocking.
5) Installed latest Samsung USB driver
5) Tried to proceed with unlocking the bootloader. This is where I ran into issues:
- I installed ADB Installer saying YES to everything
- Connected phone to pc with a usb cable
- From the command prompt (in my user) I executed adb reboot bootloader. I initially got an error (something about daemon and a port?....) but was able to move ahead
- The green android logo appeared along with this message "Downloading ...Do not turn off target!!"
At this point, pressing the volume down, power and select at the same time I tried to get out but kept on coming back to the same android menu stuck in "Downloading ...Do not turn off target!!". After the third try, a new warning message came up asking me if I want to proceed or reboot phone (pressing volume down) and I rebooted the phone to "escape" this predicament. I thought I was going to brick the thing!
Anyways, any recommendations on how to proceed? Is there an easier method to root the phone? Or to circumvent the issue I encountered?
As you might have guessed by my message, I can (sometimes) follow instructions but the underlying knowledge of what I am doing is .... well ...missing? :silly:
Hope you guys can help me. Thank you all in advance for your assistance.
Click to expand...
Click to collapse
flash custom recovery.download supersuzip latest version is 2.82.push it to your phone.reboot to recovery mode.flash supershu zip.reboot to system.your phone is rooted.that's it.
Sent from my SM-N930F using Tapatalk

Normal method .
Flash TWRP via Odin.Put custom rom on SD card .
Boot to TWRP recovery and flash .
N9005 does not have a locked bootloader .

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