Database Users

[q] problems with lg gt540

hi guys.. could you help me with my problem.!
I have an LG GT540 android 1.6 firmware version(stock)
So here are my problems:
1. I tried to upgrade it from 1.6 to 2.1 using this tutorial http://forum.xda-developers.com/show...27&postcount=3 thanks to lavero.burgos for posting it, I was successful at first part, but I cant follow the next because my device wont go to fast boot,, I tried putting it off, then camera+poweron but it doesnt do anything. It doesn't light, no lg logo appears, just nothing although the computer can read the drive when I connect it through usb. So I cannot flash it to 2.3,2.3 because it just wont go to fastboot.
2. When I turn it on normally, It takes long before it response like after 30sec to light, but just light, no lg logo appears although it wasnt bricked because I can use it normally after just waiting to on.(annoying)
3. Since I upgraded it to 2.1, I lost all 3rd party application and the internal apps were the only left, so I copied all my saved apps (.apk) to my sd card but the problem is there is no saved app on my phone to read and install those apps from my sd card.(irritating)
4. My device wont read my sim card, when I start it it says "sim card unprovisioned" so basically I cant connect to mobile networks here in the philippines(im using globe telecom). I feel that Im stucked in the middle of nowhere since I cannot contact and txt all my family and friends.
5. I cant connect to wifi,, when my device detects wi-fi, I try to connect to it but from the log it only try to connect but doesn't obtain the ip address. Even when the wi-fi signal is strong, it does the same thing.
So please help me guys,,I want to hear from my fellow xda-developers badly,,,
PS. also those who have problems with their LG GT540 pls feel free to post and share it with us here... thank you all guys in advance....

hi so let me get it right the phone is working (can turn on and use but cant call) yes? hmmmmm..... try this
MUST DOWNLOAD THIS DRIVERS!!!!
http://dottech.org/android/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/
Step one!
1.turn off phone.
2.hold the POWER button till you feel the beep.
3.let go of the POWER button when you feel the beep and hold onto the CAMERA button only.
4.hopefully it turns on to a blackscreen and nothing else(fastboot)
5.unzip this CLICK ME!! to desktop and open the flash all no wipe file
or......
1.turn on your phone.
2.go to settings>applications>development>tick the usb debugging
3.connect phone to computer (make sure phone is on)
4.unzip this CLICK ME!! to desktop and open the flash all no wipe file
5. phone should boot into blackscreen like the one above......
Click to expand...
Click to collapse
Step 2!
both should flash a recovery image. Next
1.make sure the phone is off
2.press POWER button
3.when you feel the beep let go of POWER button and press the HOME button only.
4.phone should boot into recovery mode.
5.take out battery again
6. download a rom into the sdcard using computer
7.go to recovery again using the steps above (steps 1 to 4)
8.select wipe all data factory reset or something like that....
9.install zip from sdcard
10.select from sdcard
11.choose the file you downloaded
12.finish flash and reboot phone.
Click to expand...
Click to collapse

excellent guide! big thanx

bs828 said:
hi so let me get it right the phone is working (can turn on and use but cant call) yes? hmmmmm..... try this
MUST DOWNLOAD THIS DRIVERS!!!!
http://dottech.org/android/26188/usb-adb-and-fastboot-drivers-for-windows-for-all-android-phones/
Click to expand...
Click to collapse
Thanks,, Ive tried the 2nd option on step one and i think my phone successfully got to fastboot(just clean blank screen) so the cmd automatically run and states
C:\Desktop\adb rebootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: protocol fault <no status>
C:\Desktop\fastboot flash recovery recovery.img
< waiting for device >
Did I miss something???

ok try again this time with the phone turned on. and then run the script and did you install the drivers?

bs828 said:
ok try again this time with the phone turned on. and then run the script and did you install the drivers?
Click to expand...
Click to collapse
yeah I installed the drivers...

hmmm maybe there are no fastboot drivers(main suspect....) there are a few ways to get it but for mine i just plug my phone in to my pc (windows 7 64bit) it just recognize it and tries to get the "google fastboot interface" drivers from windows update...

Try Volume Up+Search Key+Power to go into Fast boot Mode, There's different keys to activate Fastboot Mode (There is different versions of Fastboot)
Sent from my LG GT540 CM9 PreRC Polish Blood using xda premium

Your phone is/was bricked
Hey, I'm sorry to bing back such an old thread, but I just wanted to say this for posterity: your phone has/had a soft-brick. This means: you can't see Android nor LG boot logos, can't enter Recovery and (maybe) can't access Fastboot, but I'm not too sure on that last one. Besides that, the phone works "okay", but you should try to fix it.
Basically this soft-brick is almost always caught when upgrading from 1.6 to 2.1, so everyone should have it, including me. It took me a whole year to realize how to friggin' fix it lol, but here goes what I did:
Thanks for your help everyone, I came to a solution after a full year lol. Here's my enlightenment, from another Thread:
------------------------------------------------------------------------------------------
Just wanted to leave my 2 cents here, I've been trying to do my best since around august 2014, no success. 2 days ago I retried this, and I DID IT! I will tell everyone what I did very shortly:
My problem that I solved: I can boot, device works like a charm. But: no boot logos, no recovery.
My solution for TL;DR: UNINSTALL ALL DRIVERS FROM DEVICE MANAGER 1ST, then reinstall. After that, flash a fastboot ROM and use it to WIPE ALL THE DATA IN YOUR PHONE! THIS was what I needed and was never explained: you had to WIPE the old data in order to get the boot screens back.
IN THIS ORDER (THANK YOU to those people from previous replies, gathering all your info was of great value):
Uninstall all of your phone drivers from your PC!!! This is what made most of my headaches go away, just use Device Manager and uninstall anything from LGE. After that, plug in your device in your USB ports (always BACK ports, not front ports, important). It should detect all drivers and download them.
IF it fails (it generally does with LGE USB Modem), you can go to Device Manager > Unknown Device (the one that wasn't recognized) > Right Click and Update > Choose 2nd option, then choose "choose from a list of local controllers" (or whatever the button says). After that, scroll down to LG Electronics, Inc. and install what didn't install.
I also found these drivers, but I did not test them: http://www.mediafire.com/download/p693hcz6kkouh19/USB_Driver_LG_GT540.zip
Huzzah!
Now you're set to begin:
FIRST thing you wanna do is a factory reset, this is something I'd forgotten with time, don't make the same mistake as I did. You can do it by turning your phone on and pressing Volume +/- & Home & Quick Search buttons all together for 5 seconds (it works, be patient and wait for it, even if you open the camera or any other stuff).
Download this Google SDK Tools (unzip and put the folder in C:\ drive) and this Fastboot drivers for GT540 (unzip and put the files inside the folder in C:\android-sdk).
Skip this next line if you know your ROM has fastboot.
Now, if you don't have a ROM with fastboot, I recommend you use either European Open+Fastboot or V20C Orange France Fastboot ROM.
Click to expand...
Click to collapse
Since you have Fastboot enabled, now all you need to do is turn off your device (all this with its battery on it, no weird things) and hold the Camera button before turning it back on. This should take you either to a black screen, or simply to no display, like me. Either one will work anyways.
Now press the Windows key > Type cmd and open it with Right Click > Run as Administrator.
In it, type all this, command by command (you can paste by right clicking):
cd C:\android-sdk
fastboot -w
fastboot erase boot
fastboot erase system
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
And now it's go time! Do what everyone else says in here: Take out your phone's battery, SD and SIM cards, fire KDZ Updater up as Administrator (If your KDZ freezes, then it's either faulty or you did not install msxml, look for a good KDZ that comes with that file and delete your current one), choose CS_Emergency PhoneMode and:
1-Plug your phone while holding the volume DOWN button (don't worry! My phone didn't show "Download Mode" either, if you hear the Windows "Somethingpluggedin" Bump noise, it's ok).
2-Flash French V20A
3-Unplug your phone once KDZ says "==FINISHED==".
4-Plug it once again, holding the volume DOWN button.
5-Flash out.kdz (remember! it's CS_Emergency).
Click to expand...
Click to collapse
THANK YOU XDA!
--------------------------------------------------------------------------------------
Also, if you look in here you'll find how to flash an awesome ROM, Cyanogen Mod 10 (should say "Final Version#2).

What did I do?!

Okay, I was trying to load android 6.0 on my oneplus one and I don't have any idea what I've done. I was following the instructions in this video https:/ /m.youtube.com/.watch?v=x8zuQcJHQy4 but I wanted to try to do it without using my laptop. So I downloaded the gapps from here http: //opengapps.org/ directly onto my phone. I restored my phone back to factory setting from the settings menu on my phone, and then tried to follow the instructions from the YouTube video. So I removed my existing op system and then tried to install the the new gapps from the recovery menu. The instal failed, so I went back and fired up the laptop and started to follow the instructions in the video. The problem is that my laptop won't connect with my phone for some reason. I plug it in to the computer but it won't recognize my phone. So I am unable to transfer the new gapps from my laptop to my phone. Now the problem is that my phone will not start up, it just sits on the starting screen (picture attached). What do i do?! I should mention that I have no idea what I'm doing if that isn't already extremely obvious. Please help!

Look as you described there maybe more than one solution to this..
As for me the easiest method would be is to flash a custom recovery by going into fastboot mode. And from there you can boot into your recovery and transfer whatever files you need from laptop to your phone. Then flash your custom ROM.
Recovery link : https://twrp.me/devices/oneplusone.html
Custom ROM: http://forum.xda-developers.com/oneplus-one/development/rom-ressurrection-remix-m-t3270147
Look my advice is don't make this whole process as few steps guide.
Divide it into small parts like first installing recovery. Then second part flashing custom ROM. It makes its easy. And for individual part you can find tutorial online.
Thanks me if I have helped and if you have any more doubt PM me.
Sent from my A0001 using Tapatalk

i started this process for the "recovery" in the link you gave me and i cant complete the instruction that tells me to go into the device settings and tap on the build number 7 times. I can even start the phone enough to get into the settings area. Any ideas?

Just go into fastboot mode and flow the given instruction..
Sent Using Awesome Nethunter Device.

Mr.Jlu said:
Just go into fastboot mode and flow the given instruction..
Sent Using Awesome Nethunter Device.
Click to expand...
Click to collapse
By fastboot do you mean where I power it up and hold the "down volume" button for a few seconds??

OnePlus One Fastboot
Power Down the OnePlus One
Press and Hold the Volume Up and Power Button at the Same Time
Hold These Buttons Down Until You See the Text “Fastboot”
When You See the Text “Fastboot”, Let Go of the Power and Volume Up Buttons
Sent Using Awesome Nethunter Device.
---------- Post added at 12:34 AM ---------- Previous post was at 12:34 AM ----------
In order to issue commands to your OnePlus One via tools like ADB and Fastboot, you need to boot your device up into Fastboot Mode. So, instead of allowing your OnePlus One to boot up into regular Android, you are going to do something special which tells the device to boot up into Fastboot Mode. This might take you a few tries until you get the hang of it. There’s no need to panic or worry if you get it wrong. Simple power down the OnePlus One again and give it another shot.
Sent Using Awesome Nethunter Device.

I can boot it up into fast boot mode without any problems, I just don't know what do do once there. That's the part I need help with.

turbo224 said:
I can boot it up into fast boot mode without any problems, I just don't know what do do once there. That's the part I need help with.
Click to expand...
Click to collapse
1. You need configured fasboot tools first.
2. Flash twrp using fastboot
3. Reboot to recovery
4. Connect your phone with the computer
5. Copy ROM and gapps to your phone and disconnect.
6. Make a full wipe in recovery
7. Flash ROM and gapps
8. Reboot

1. Follow this guide on setting up adb and fastboot - http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
2. Download twrp-3.0.2-0-bacon recovery from here - https://dl.twrp.me/bacon/
3. Put the recovery image in the same folder fastboot and adb exe is.
4. Put your phone in fastboot mode and connect to pc
5. Open a command prompt and type "fastboot flash recovery twrp-3.0.2-0-bacon.img"
6. Do Not issue the fastboot reboot command, instead press and hold power and vol down till phone reboots into recovery

I give up, i'm way over my head. I cant do any of this **** because I can't even get the right ****ing usb driver on my computer so it even recognizes my phone. I've tried three different methods and none of them work.

turbo224 said:
I give up, i'm way over my head. I cant do any of this **** because I can't even get the right ****ing usb driver on my computer so it even recognizes my phone. I've tried three different methods and none of them work.
Click to expand...
Click to collapse
Don't give up.
That's pretty simple if you follow the guide below TO THE LETTER.
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Basically, you just erased the Android operating system from your phone. The gapps is NOT the Android system. Gapps stands for Google Apps (play store, calendar, youtube, etc...). They are just additional apps, like Office for Windows for example.
Good luck!

Turbo224,from which country you are from? If you don't mind me asking!
Sent Using Awesome Nethunter Device.

Problems Reverting to Stock

I briefly took over another thread where this issue didn't belong, but since I am still having issues, I thought I would start my own thread. Okay, so I am on Sprint, sideloaded several of the updates, including most recently the Oreo Beta. I have been very happy with the beta, and was looking forward to the update due this week. However, yesterday evening I dropped the phone on the sidewalk and it cracked very badly, and as I am paying insurance with Sprint I want to bring it to a store and have it fixed. Not only is the screen badly cracked, but the keyboard is acting up a bit also.
Anyway, I was getting advice on the Oreo thread about how to do this, and as I said, I had hijacked the thread, but I was at work and didn't get to try this until tonight when I got home. Anyway, I had originally plan to just find the Ota and sideload it, but it was recommend that I use flashall and the full image file from the Essential site. I tried to do that, but when I restart the phone to get into Bootloader mode, it disappeared from the list of devices visible on my desktop and via adb. It was a bit disturbing to me as I am not used to working in Bootloader, previously did anything like this via recovery, and I wasn't sure how to exit the bootloader, but I chose power off, and saw a weird screen with what looked like a coffee cup, and eventually the phone rebooted and seems unchanged at the moment.
I still want to revert to the sprint nougat before I bring the phone in, but I admit I am a little nervous now about the best way to do this. I could use some suggestions. I hope this post is not too long-winded, but I wanted to explain as much of what has happened as possible.

maltydog said:
I briefly took over another thread where this issue didn't belong, but since I am still having issues, I thought I would start my own thread. Okay, so I am on Sprint, sideloaded several of the updates, including most recently the Oreo Beta. I have been very happy with the beta, and was looking forward to the update due this week. However, yesterday evening I dropped the phone on the sidewalk and it cracked very badly, and as I am paying insurance with Sprint I want to bring it to a store and have it fixed. Not only is the screen badly cracked, but the keyboard is acting up a bit also.
Anyway, I was getting advice on the Oreo thread about how to do this, and as I said, I had hijacked the thread, but I was at work and didn't get to try this until tonight when I got home. Anyway, I had originally plan to just find the Ota and sideload it, but it was recommend that I use flashall and the full image file from the Essential site. I tried to do that, but when I restart the phone to get into Bootloader mode, it disappeared from the list of devices visible on my desktop and via adb. It was a bit disturbing to me as I am not used to working in Bootloader, previously did anything like this via recovery, and I wasn't sure how to exit the bootloader, but I chose power off, and saw a weird screen with what looked like a coffee cup, and eventually the phone rebooted and seems unchanged at the moment.
I still want to revert to the sprint nougat before I bring the phone in, but I admit I am a little nervous now about the best way to do this. I could use some suggestions. I hope this post is not too long-winded, but I wanted to explain as much of what has happened as possible.
Click to expand...
Click to collapse
Just an FYI, I found that putting Oreo on the phone resulted in ADB not working 100% anymore, such as attempting to reboot into recovery/etc. It would just reboot back into the O.S..
Here is what I did to flash the stock firmware.
- download the current release you want to flash. (e.g. NMJ32F), then unzip it into a new folder.
- on your phone, verify that USB debugging and OEM unlocking are turned on in the developers menu.
- reboot your phone into the fastboot mode (power and volume down buttons)
- from your adb command line: type: fastboot flashing unlock
- This will make your phone show a new screen asking if you want to unlock the bootloader. Use the volume down to select YES, and hit the power button. It will now reboot and erase the phone. It will eventually end up booting up too request you setup the phone. (that is what it did for me.)
- reboot the phone back into the fastboot mode (power and volume down buttons)
- you should now see the bootloader listed as unlocked (vs locked)
- from your adb command line: type: fastboot devices (which should show your phones serial number and fastboot next too it.
- on your computer, using the command line, go to the unzipped folder of the NMJ32F build you downloaded
- in the folder there is a batch file you will run called flashall.bat. run it
- your phone will start flashing the NMJ32F build
- when it completes it will reboot a couple of times, erase the phone, and end up at the "lets get started" screen.
- reboot the phone back to the fastboot mode
- from your adb command line: type: fastboot flashing lock
- select the option to lock your bootloader. The phone will reboot/erase I believe, and then end up back to the "lets get started" screen.
- after you setup your phone, you can go back into the developers menu to turn off the oem unlocking
The above steps pretty much follow essentials instructions. (the essential instructions don't give some specifics.)
You are all done. (I recommend you review my instructions and the essential instructions carefully, don't copy paste commands as I may have spelled something wrong, etc.. Just wanted to give you a flow of the process.)

I was following those directions, but what happens is that though the phone appears as a device in adb before rebooting, once I reboot into fastboot mode, it is no longer listed. I also noticed that when tried to reboot the phone into bootloader mode with an adb command, instead, it did a regular reboot, and when it did that reboot, it again was no longer listed as a device, because it went into charging mode. So I'm not sure how to keep this from happening.

maltydog said:
I was following those directions, but what happens is that though the phone appears as a device in adb before rebooting, once I reboot into fastboot mode, it is no longer listed. I also noticed that when tried to reboot the phone into bootloader mode with an adb command, instead, it did a regular reboot, and when it did that reboot, it again was no longer listed as a device, because it went into charging mode. So I'm not sure how to keep this from happening.
Click to expand...
Click to collapse
The reason why the adb command (to go into bootloader mode) didn't work is it is broken when you installed Oreo, that is why you need to do it manually.
When you put your phone into fastboot mode (power button / volume down) plug in your phone into your computer, and from command prompt (make sure you are in the adb folder), type fastboot devices (don't type adb devices) and see if anything replies back.

kbonnel said:
The reason why the adb command (to go into bootloader mode) didn't work is it is broken when you installed Oreo, that is why you need to do it manually.
When you put your phone into fastboot mode (power button / volume down) plug in your phone into your computer, and from command prompt (make sure you are in the adb folder), type fastboot devices (don't type adb devices) and see if anything replies back.
Click to expand...
Click to collapse
Thanks, I understand now. I can't start this tonight, but I will try the again next time I have time at the desktop.

You are probably missing the phone's driver. Download this, Essential device driver for Windows machines. Supports 32/64 bit on Windows 7, 8 and 10., from the essential developer site and install it.

damn it, I read somewhere that there are problems while using adb on the current official beta. There was a command for getting connection again. But I can't find it right now.
Just to be clear. when the phone is on, you enabled USB debugging and plugged in the USB cable and checked the tickbox before you granted debugging access, right? If you don't check the box, there is no access granted after a phone reboot.
take care, I had problems getting through the initial phone setup after I did a factory reset. The Oreo beta still has some hickups. I got it to work after a few reboots. Without finishing the intial phone setup you can't enable USB debugging, you know.

emowing said:
You are probably missing the phone's driver. Download this, Essential device driver for Windows machines. Supports 32/64 bit on Windows 7, 8 and 10., from the essential developer site and install it.
Click to expand...
Click to collapse
Good point on the driver, I wasn't even thinking about that.

Well, my phone was being read when I previously sideloaded updates, so I think I have the right drivers, but I will double check. Can anyone suggest why the phone keeps defaulting to charging mode rather than file transfer every time I reboot it?

maltydog said:
Well, my phone was being read when I previously sideloaded updates, so I think I have the right drivers, but I will double check. Can anyone suggest why the phone keeps defaulting to charging mode rather than file transfer every time I reboot it?
Click to expand...
Click to collapse
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?

iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes.

iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes, I did, thanks.

F
iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes, I did, thanks. Trying to reply and it doesn't appear. Edit: Sorry for the multiple posts,they all appeared at once.

Okay, I am back to this now, I had time today. I installed the windows drivers from the Essential site (I am running Windows 10 64 bit) and the device was recognized in fastboot devices. The phone wiped my data and restarted with a setup screen. So far, so good. So I shut down the phone again, turned it on again in fastboot mode, it was unlocked. I went into a CMD screen and typed fastboot devices, and the phone was still listed there. So I opened windows explorer and got to the folder where I had unpacked the image files and also copied the flashboot file. I right-clicked the flashall.bat file, chose run as administrator. When I did this, I got a bunch of error messages that went by so fast, they were practically impossible to read, though they seem to say something about files not found. I didn't see any log file in the folder, so I guess they are not created. I went back to the Essential site and downloaded the zip file with the correct image files again and tried a second time, with the same results. Anyway I have wiped my phone, but still have not reinstalled the Sprint nougat software I need on this phone. Any other suggestions?

Okay, I tried again, and I was able to read the error message. They all said cannot load "filename" no such file or directory. It sounds like some kind of path error, right? I expanded the file from the Essential download for build Build NMI81C into their own directory, a subdirectory of a library where I have been keeping various android files, and I copied the flashboot file into the same directory from the platform-tools download, but only that file. That seems to be what instructions specify.
Also, I notice on this thread https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681/page3 it mentions also using the command "fastboot flashing unlock_critical" but I do not see that elsewhere.

I was able to get flashall to run using the command prompt instead of Windows Explorer. It seemed to run okay, except a couple of items cause me some concern.
I got a message "FAILED (remote: Flashing is not allowed for Critical Partitions)" for the abl.img file.
And the other command "Did you mean to fashboot format this ext4 partition".
Are either of these a problem?

Try running the commands one at a time. Open the flash-all.sh in a text editor and copy the commands.

As I said in my last message, I was able to get Flashall to work when I ran it in the CMD prompt rather than in windows explorer (which is how it was done in the video posted on Youtube, but didn't work for me). My only concern at this point is whether I should be concerned about the two commands posted in the email.
Interestingly enough, my phone did an update to the build NMJ32F as soon as I started it up.

maltydog said:
As I said in my last message, I was able to get Flashall to work when I ran it in the CMD prompt rather than in windows explorer (which is how it was done in the video posted on Youtube, but didn't work for me). My only concern at this point is whether I should be concerned about the two commands posted in the email.
Interestingly enough, my phone did an update to the build NMJ32F as soon as I started it up.
Click to expand...
Click to collapse
Did u not do the flashing unlock_critical?

Airwolf79 said:
Did u not do the flashing unlock_critical?
Click to expand...
Click to collapse
No I didn't. It was not mentioned by anyone but me in this thread until you did.
So far I have received no error messages since I did the reversion to stock. As I said,
I did get an update almost immediately.

My experience with FRP lock and how I solved it...

So my nephew brings me his galaxy s6 t-mobile phone... He forgot his lock pin so he factory reset it. Now he can no longer get into the phone because he doesnt know the correct email or password. I did some digging through the net watched a few videos... and found none of the methods they used to bypass the lock would work on his phone. Then I read about the Combination Rom (Factory Binary)... At this time I do not have any windows pc's and my VM will not read the usbs of the phone... (im not that experienced with vm to set this up) So i grabbed JOdin for linux and proceeded to try to flash the binary. However, JOdin did not work for me. So i found Heimdall and installed to learn that i had to find some weird way to run it as SU for it to work... Tho Heimdall worked like a charm.... With Heimdall I had to take the rom and completely extract it to a folder and find all the img files in it to install on heimdal like sboot, boot, cm, system, and quite a few others as well.I used the "PIT" file from the combination rom (which came in the download). When done installing the phone boots into Factory Binary... Interesting little rom... From here you can access settings, tho the instructions tell you to enable developer options and turn on usb debugging... in this rom they are set on by default i believe, so that was kind of a waste of time... then from the main menu you click the icon that looks like a calculator and type in "*#0808# where you are then presented with usb options. Select the last one on the list with adb at the end of it, click save and reboot. At this point I thought i was supposed to install the stock rom back (that was where i was lost) however all you have to do is let it boot back to binary. After it has reloaded... plug it into the pc and send it the proper adb instructions to disable frp lock. Techeligible has a batch file for use in windows, however if you dont have windows like me that does no good... So I went into the batch file with a text reader and extracted the information i needed ( 3 adb commands).In terminal i made sure my adb and fastboot were updated and working. I learned that when you type "adb devices" it will show the phone and if it says nothing else you are good to go. However it may give you a problem with permissions. If this is the case then unplug and make sure usb debuggin is on, you can also check that the adb is enabled again by doing the *#0808# command again and make sure the last selection is checked. When all is in order... At first I thought all commands must work for it to succeed... However this is not true at all. Only one of the adb commands will not give an error and at that time you can reboot into download mode and install the stock rom back on. After installation the phone will reboot and FRP Lock is no longer on... Now you can go into settings open up developer settings (tap build number till it unlocks) and select "OEM Unlock" and turn it on. Make sure usb debugging is on and you can boot back into download mode and install TWRP without a hitch.
I tried installing a couple of custom roms, however I have had no success with getting one to boot. (always stuck in boot loop even with wipe or factory reset) so I gave up and left him with the stock rom. If anyone has any idea of how i could get passed the bootloop maybe i can try again for him sometime and see how he likes various custom roms, but now he is happy he has his phone back working and it only took me a week of off and on frustration to figure it out... Hope this helps someone... (please dont ask for links) but if you do need help or have questions feel free to ask.

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