Database Users

Read BEFORE flashing!!

Ok, so I know this will eventually get buried in the forums but I thought I would attempt to give a little basic info here. Right now the QA section is flooded with people that have flashed and are now soft bricked (have problems but can recover) or hard bricked (have problems and cannot recover). I'm hoping that I can help some people prevent these issues to an extent.
Terminology, the differences in my opinion.
Soft brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your hardware buttons work or ADB works and you are able to boot into DOWNLOAD mode.
Hard brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your unlucky and hardware buttons do not allow access to DOWNLOAD mode or ADB is not downloading.
Also, after a new flash or flash to stock, it's a good idea to immediately enable USB debugging. Menu, Settings, Applications, Developement, check the box for USB debugging. It will make things easier later on.
1. First. BEFORE you flash, can you access download mode with your buttons??? Test it.
3 Methods.
Method 1: (ADB - from recovery or normally booted with usb debugging on)
Open a cmd prompt/console/shell
adb shell
adb reboot download
Method 2: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold Volume Up + Volume Down + Power
Method 3: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold both Volume buttons (from i9000 just down, don't touch the power button)
Plug in the USB cable and continue holding both Volume buttons
If not, use designgears fix. http://forum.xda-developers.com/showthread.php?t=812434
2. Second. Download the SDK, drivers for your PC, and learn some basic ADB commands, ie, adb reboot download, adb reboot recovery, adb shell. Here's my quick guide. ADB can be used when the OS is running, when in recovery, and when stuck on ATT boot screen.
Here's what I do. After you download the sdk and unzip. There is a folder called tools. I copy that to c:
Then open a command prompt and type,
C:
CD tools
Then issue adb commands.
adb reboot, adb reboot download or whatever command you need.
Of course make sure your phone is connected via USB and debugging is enabled.
Here's another method for using adb.
1) start-> run-> sysdm.cpl
this will start the system properties. you can reach this from right clicking "My Computer" and hitting properties. Windows 7 though is different. The above method is most universal.
2) Move to Advanced Tab that pops up. From there click the "Environment Variables" button.
http://wtfokc.com/sef****/sysdm-1.gif
3) In the window that pops up, find the "PATH" area in the "System Variables" listbox at the bottom:
http://wtfokc.com/sef****/sysdm-2.gif
4) Click edit again, put in path to the AndroidSDK tools folder. Do it like shown otherwise you can biff something up. DO NOT REMOVE ANYTHING. Just add a SEMICOLON ( ; ) to the last of the line that's already there, then the path to the folder.
http://wtfokc.com/sef****/sysdm-3.gif
5) If on Win7 you shouldnt have to reboot. XP however will. Then you are set. You can now just load a CMD prompt and do ADB without having to CD TOOLS.
3. Third. Install Clockwork Recovery! Root your phone and download ROM Manager from market. Install Clockwork recovery from ROM Manager. BOOT into recovery to make sure it works. You will have to choose reinstall packages from stock recovery. What ROM Manager does, it put an update.zip on the root of your SDcard, then when you choose reinstall packages from stock recovery it install update.zip. I personally leave the update.zip file on my sdcard at all times, just in case.
Once you have clockwork installed, make a Nandroid backup of a good running rom. In case something happens, if you can boot into recovery, then you can possibly restore your nandroid to at least get you up and running quickly, and without the need of a pc.
NEW Info!!! You can recover from a hard brick, maybe. Here's how to create a USB Jig to reproduce the button download mode for you folks who don't have it.
http://forum.xda-developers.com/showthread.php?t=841512
Here's another thread about the USB Jig method.
http://forum.xda-developers.com/showthread.php?t=819551&highlight=USB+jig
If my captivate was one that had the missing button recovery/download out of the box, I would probably know how to make a USB jig or have one already before flashing. Even with the 3 button fixes that are out, it looks like some people are still bricking.
****Disclaimer****
This is just from personal exprience. I have flashed most roms available, and I have experienced every variation of soft brick mentioned above and have recovered.
I find that being able to get your phone into download mode and knowing how to use Odin will be your 2 biggest life savers after something bad happens.
This will not keep you from getting a bad flash or something else, but having this knowledge ahead of time may help you recover from issues more quickly and without asking a question on the forums that have been asked dozens of times.
Also, personally, if I cannot perform step 1, access download mode with buttons, I personally would be VERY cautious about flashing! ADB reboot download is nice, but if you are stuck at ATT logo or phone--!--PC mode then ADB doesn't work, YOU HAVE TO USE BUTTONS.
Just my 2 cents, take it or leave it.
Edit. Added some new info to post. Thanks for extra info guys. I'll mirror the links to the images later when not at work.

+sticky
excellent write up. a must-read for anyone even thinking about flashing

Original Post updated to add my information

bobbylx said:
ADB reboot download is nice, but if you are stuck at ATT logo
Click to expand...
Click to collapse
Ok first off something that should be added to this is always may sure you have usb debug mode Settings>Applications>Development>USB Debugging enabled on your phone. Don't take it out of debug mode. This will allow you to issue adb commands if you have.
If you are getting to the att logo screen and not beyond that and you have debug mode enabled then you can use adb to reboot into either recovery or download mode.
Steps
1: Get the command prompt up and que up the adb command you want to issue either reboot download or reboot recovery. Don't press enter yet.
2: When the att screen comes on your pc should make a notification sound that the device is connected.
3: On the second notification sound issue your adb command and the phone will reboot into the mode you selected.
Mileage may vary but should work.
This has saved me a few times.

STICKY
Sent from my SAMSUNG-SGH-I897 using XDA App

Thanks for the extra info. Malfuncion, awesome write up with pics, I'll add to first post later. I always forget about adding a system variable.
Sparker366, thanks, I always thought that at the ATT screen adb didn't, but you know what, I never tried.
I figured since I'm not a dev and don't have that knowledge I would try to help start this up to contribute a bit. And honestly, if you hop over to the QA sections there are so many threads that could be solved by knowing this info ahead of time. I doubt everyone will read it, but I hope it helps the ones that do.

bulletproof1013 said:
STICKY
Click to expand...
Click to collapse
+1
This is my first smart phone and first experience with Android. I also don't have any experience with linux. Fortunately, I was able to avoid problems when I first started by reading, reading, reading. This type of information would have been invaluable. In fact, the tip on keeping debug mode on all the time is great to know, and I never saw that before.
Sent from my SAMSUNG-SGH-I897 using XDA App

This thing is getting buried in the BS posts....BACK TO THE TOP!
definitely sticky

Bump Bump Bump
Great Info

Updated original post with extra info.

Shameless bump here. New version of Cog uploaded, so that means there will be questions soon.

Thanks, great info.

FWIW........
I feel like I am of average intelligence, and would think I could nail download mode everytime by the 3 button method, but damn if it is hit and miss for me every other time.
One way I found (I didnt discover it, but read it somewhere) to nail it EVERYTIME is to remove sd and sim. Plug the usb to the phone AND THE PC, while odin is sitting and waiting. Then while holding both up and down volume buttons, insert the battery. It works every time with no fuss.
Thanks for the post, my vote for sticky as well.

+1 sticky
Sent from my SAMSUNG-SGH-I897 using XDA App

Moving this to the top. More questions in QA that can be helped by reading these tips first.

I would also suggest that anyone who wants to flash actually test their phone's USB transfer ability before flashing.
The best way is to find a large file, perhaps one just under 2G in size and transfer it to the internal SD storage.
Test md5 checksums on the source and this file and make sure these match.
(you can use the 'md5sum <filename>' command from the terminal app, from Windows you can use a md5sum port for the source file win32 md5sum).
This will ensure your USB connection is stable enough for long, error free transfers to the phone.
Also important: it's useful to disable any powersave actions on your PC while using an app like ODIN.

Sorry all, moving this to the top. There are about 6 or 7 bricked phone Questions in Q & A now.

Awesome, clear and concise. Been trying to figure out how to make nandroid backups and this explained it very simply Thank you!

thanks for the reminder
there's so many steps to install a rom...
specially with download mode keycomb, i tend to not to remove sim and memory card cuz i dont want to lose or damaged my mcard. now i will remove each time!
another good reason flashing stock with odin before flashing new rom

I would also say its a good idea to back up your efs folder. Mine got all borked up when that jpc rom came out a while ago and it is a ton of work to fix. Sgs tools copies your nvdata.bin and. /nvdata.bak files to your sd card if you do a product code check. Or you can use root explorer.

Recording video audio sync issue

Hello everyone,
Someone I am trying to help is reporting a weird issue with her Nexus 4 with video recording. The audio goes out of sync after a couple seconds in the recordings.
Here are some facts :
1) Issue arise regardless of which camera is used (front or back)
2) Issue arise regardless of the resolution setting. From SD to HD, always the same issue.
3) This is a stock device with no root
4) Device has been updated to the latest version 4.4. Whent from 4.2, 4.3 and 4.4.
5) Device has been reset to factory default and still the same issue
6) When rebooting the divice, if we go directly in the camera app without doing nothing prior that, the problem is less evident and it takes longer to start seeing de-sync audio from video
7) The issue is NOT there when the phone is connected to a MAC laptop through USB. In that case, video recording is perfect
8) No test done with a PC at this time
9) The sync issue is STILL there when the phone is connected with a USB wall charger. Only when connected to a MAC laptop makes the problem disapear.
I have seen a video of the issue and it is not a slight sync issue. It is really noticable only after 15 or 20 seconds of recording and the more you record, the worst it becomes.
I will try to have some youtube links so you guys can see the issue.
Any ideas ?

Video example
Bump !
Anyone have a clue on what is going on ?
Here is a video example of the issue :
Thanks !

Since you're stock, you should go to apps and select the camera app and delete user data, cache and try again. If it still not working, i suggest you a full wipe, or even re-installing the whole system.

sky0165 said:
Since you're stock, you should go to apps and select the camera app and delete user data, cache and try again. If it still not working, i suggest you a full wipe, or even re-installing the whole system.
Click to expand...
Click to collapse
Thanks for your reply, the clear cache and full whipe have been done and still the same issue...
Not sure though how to re-install the whole system though... I guess that mean I need to root since it is a carrier Nexus 4...
Oh and another note is that the phone is loosing track of time pretty quickly. If the phone is NOT on the network (airplane mode), it looses time. You can't use the alarm clock since that in 10 or 12 hours, the phone can get off by 2 hours !
Sent the phone 2 times for repair already and still the same issue. They always say everything is fine with it when there is clearly an issue with it. Not sure if it is a hardware issue or a software issue like you are suggesting...

Aleziss said:
Thanks for your reply, the clear cache and full whipe have been done and still the same issue...
Not sure though how to re-install the whole system though... I guess that mean I need to root since it is a carrier Nexus 4...
Oh and another note is that the phone is loosing track of time pretty quickly. If the phone is NOT on the network (airplane mode), it looses time. You can't use the alarm clock since that in 10 or 12 hours, the phone can get off by 2 hours !
Sent the phone 2 times for repair already and still the same issue. They always say everything is fine with it when there is clearly an issue with it. Not sure if it is a hardware issue or a software issue like you are suggesting...
Click to expand...
Click to collapse
If you send things to repair and they came back broken, you need to fix it by yourself.
I guess you're not used to do such things, so i'll make a quick tutorial for you, if you're interested of course.
Code:
1- Download [URL="http://www.purespeedx.net/index.php/Thread/160-KOT49H-PSX-PSK-v3-0-2-Pure-Speed-X-for-Nexus-4/?postID=3706#post3706"]PureSpeed[/URL] ROM, it's the best ROM you can find. Download the ROM, PSX Gapps and SuperSU in the PSX-Addons.
2- You'll need to download ADB to flash recovery. You can find it [URL="http://forum.xda-developers.com/showthread.php?t=638150"]Here[/URL]. Extract it on the Desktop.
3- Install all Nexus 4 drivers. Connect an USB cable to your computer and wait all drivers to be loaded correctly. Switch from MTP to Camera to install both drivers as well. When it finishes, disconnect USB cable.
4- Once you have everything set up, open CMD (Windows + R button) and type CMD. A black screen will appear and you'll do the following: type cd: (location where you have extracted ADB folder. Ex: cd: C:\Users\zzz\Desktop\ADB
5- Connect your USB cable again and type: adb devices. If everything is fine, you should see a bunch of letters and numbers, like [URL="http://duarterenato.files.wordpress.com/2012/05/adb-devices.png"]this [/URL]
6- Restart your phone into bootloader. type: adb reboot bootloader. You should see [URL="http://cdn-static.cnet.co.uk/i/c/blg/cat/mobiles/nexus-4-root/fastboot1.jpg"]this [/URL]screen.
7- On ADB, type: fastboot oem unlock. You'll see an image like [URL="http://cdn.redmondpie.com/wp-content/uploads/2010/12/thumb_550_Nexus-S-oem-unlock.jpg"]this[/URL]. With this code, you'll unlock your nexus 4 bootloader to be able to install Custom ROM. Everything will be wiped, so be sure to backup everything and you can proceed.
8- Wait all the process, it won't take too long. Once you boot into Android, just type again: fastboot reboot bootloader.
9- This time we'll install a Custom Recovery. You can find it [URL="http://www.androidfilehost.com/?fid=23212708291678949"]here[/URL]. Download it and extract recovery.img into the ADB folder that is in your Desktop. Once this was done, type: fastboot flash recovery recovery.img. You should see some lines with OKAY.
10- Navitage using Vol + and Vol - and select Recovery option and press Power to enter it. You should see something like [URL="http://phota.me/AgsV.png"]this[/URL]. Tap Backup for future reasons, if you want to back to your stock carried ROM. Once complete, keep the backup somewhere safe and boot to android normally and transfer PureSpeed ROM, Gapps and SuperSu on the root of the storage. Once complete, type: adb reboot recovery.
11- Select Wipe and wipe eveything, except usb-otg. DON'T WIPE INTERNAL STORAGE.
12- Once complete, select Install and install PureSpeed ROM for first, when Gapps and for last SuperSu. I suggest you to wipe Data, Dalvik Cache and Cache for stability reasons.
If you follow this tutorial, you'll have one of the best ROMs available for Nexus 4 and also will be safed in case you want to back to your stock ROM.
If you still have problem using telephony, I suggest you to update your phone modem, but this is tutorial for another post.
I hope it helps you.

Great !
sky0165 said:
If you send things to repair and they came back broken, you need to fix it by yourself.
I guess you're not used to do such things, so i'll make a quick tutorial for you, if you're interested of course.
Code:
1- Download [URL="http://www.purespeedx.net/index.php/Thread/160-KOT49H-PSX-PSK-v3-0-2-Pure-Speed-X-for-Nexus-4/?postID=3706#post3706"]PureSpeed[/URL] ROM, it's the best ROM you can find. Download the ROM, PSX Gapps and SuperSU in the PSX-Addons.
2- You'll need to download ADB to flash recovery. You can find it [URL="http://forum.xda-developers.com/showthread.php?t=638150"]Here[/URL]. Extract it on the Desktop.
3- Install all Nexus 4 drivers. Connect an USB cable to your computer and wait all drivers to be loaded correctly. Switch from MTP to Camera to install both drivers as well. When it finishes, disconnect USB cable.
4- Once you have everything set up, open CMD (Windows + R button) and type CMD. A black screen will appear and you'll do the following: type cd: (location where you have extracted ADB folder. Ex: cd: C:\Users\zzz\Desktop\ADB
5- Connect your USB cable again and type: adb devices. If everything is fine, you should see a bunch of letters and numbers, like [URL="http://duarterenato.files.wordpress.com/2012/05/adb-devices.png"]this [/URL]
6- Restart your phone into bootloader. type: adb reboot bootloader. You should see [URL="http://cdn-static.cnet.co.uk/i/c/blg/cat/mobiles/nexus-4-root/fastboot1.jpg"]this [/URL]screen.
7- On ADB, type: fastboot oem unlock. You'll see an image like [URL="http://cdn.redmondpie.com/wp-content/uploads/2010/12/thumb_550_Nexus-S-oem-unlock.jpg"]this[/URL]. With this code, you'll unlock your nexus 4 bootloader to be able to install Custom ROM. Everything will be wiped, so be sure to backup everything and you can proceed.
8- Wait all the process, it won't take too long. Once you boot into Android, just type again: fastboot reboot bootloader.
9- This time we'll install a Custom Recovery. You can find it [URL="http://www.androidfilehost.com/?fid=23212708291678949"]here[/URL]. Download it and extract recovery.img into the ADB folder that is in your Desktop. Once this was done, type: fastboot flash recovery recovery.img. You should see some lines with OKAY.
10- Navitage using Vol + and Vol - and select Recovery option and press Power to enter it. You should see something like [URL="http://phota.me/AgsV.png"]this[/URL]. Tap Backup for future reasons, if you want to back to your stock carried ROM. Once complete, keep the backup somewhere safe and boot to android normally and transfer PureSpeed ROM, Gapps and SuperSu on the root of the storage. Once complete, type: adb reboot recovery.
11- Select Wipe and wipe eveything, except usb-otg. DON'T WIPE INTERNAL STORAGE.
12- Once complete, select Install and install PureSpeed ROM for first, when Gapps and for last SuperSu. I suggest you to wipe Data, Dalvik Cache and Cache for stability reasons.
If you follow this tutorial, you'll have one of the best ROMs available for Nexus 4 and also will be safed in case you want to back to your stock ROM.
If you still have problem using telephony, I suggest you to update your phone modem, but this is tutorial for another post.
I hope it helps you.
Click to expand...
Click to collapse
Of course it does help ! I will look into this carefully and thanks again for your help ! It's really appreciated !

Fixed
Just a follow up on that issue to say that the nexus 4 had a problem...
After trying a big bunch of things/reset/procedures describe here, it never fixed the issue.
the whole main board was replaced and it fixed the problem so it was really a hardware issue.
It just took 3 time before they finally ack that there was indeed a problem. First to time in repair they said it was ok when it was clearly not specially when the phone time was desyncing so badly...
Thanks for all your input guys ! Really appreciated !

The T-Mobile LG K7 Thread

Firstly, I'd like to start by saying that I am making this post because there is little information on the T-Mobile LG K7(K330) and what little information is found is scattered throughout the site.
The LG K7 is a budget phone and you do get the biggest bang for your buck if money is tight. Right now, you can get the Walmart version (for $50!) and flash it to T-Mobile which I will explain in the steps below.
I HAVE ONLY TESTED THIS ON THE WALMART FAMILY MOBILE VERSION OG THE LG K7, THIS PROBABLY WON'T WORK WITH OTHER DEVICES
This is a really great phone and awesome phone to start developing on if one chooses to do so. That being said, let's go ahead and flash the phone to T-Mobile if you haven't already. Most of this information came from Billybobjoe13245's Beautiful Post
Disclaimer: I tested this on Android Lollipop version 5.1.1 and that's what worked. Feel free to try whatever you feel but in any case, I am not responsible for what YOU do to YOUR device, if YOU mess up, YOU will have to deal with the consequnces. Now that that's out of the way,
You're going to need:
Windows Computer with Administative Priviledges (because LG binaries)
An LG K7 (K330)
A USB Cable
About 20 minutes
Once you have all those ready, start downloading the necessary files:
LG UP Software (You're looking for Lab Version 1.10) OFFICIAL | MIRROR
LG Mobile Driver Software(I used ver. 4.0.4.0 but the latest might work) TESTED VERSION | LATEST OFFICIAL
The "WEB_K33010h_00.kdz" file from Billybobjoe13245's Mega Repo
And now it begins.
Install the Mobile Driver Software
Install the LG UP Software
Turn you LG K7 off
Turn on your K7 while holding the DOWN button to boot into Download Mode
Open the LG UP Software
Select "Upgrade" in the separator between the two lists
Hover over "BIN FILE" under "FILE TYPE" and you should see three dots (...) to select a file
Here you select where you've downloaded the WEB file
Click start and let it do it's thing
Once it is finished it will reboot your device and tell you that it has been completed. You should now be able to use a T-Mobile nano-SIM card with absolutely no issues.
Next you Probably want to
ROOT YOUR DEVICE
THIS WILL COMPLETELY WIPE YOUR PHONE SO BACK UP WHATEVER YOU NEED TO
You'll need an internet connection for this to work properly . Let's go:
Make sure your phone has enough charge (%75+)
Go to Settings > General > About Phone > Software Info
Click Build Number 7 times or until it says "You are now a developer"
Go back to General Settings
Go to "Developer Options"
Enable "OEM Unlock"
Enable "USB Debugging"
Next youl'll want to make sure that you have the Android Debug Bridge (ADB) installed. If you don't have it , these guys have your back. Make certain that it is correctly installed and that you can access it using your command line.
Download this Team Win Recovery Project image on your PC (it's from my mirror)
Make sure it 's in the folder that ADB is in or that ADB can recognize
Plug in your phone into your computer if it's not already
You'll want to boot into the bootloader using adb so type:
Code:
adb reboot bootloader
Wait for it to reboot into the bootloader (shouldn't take long)
MAKE SURE THAT IT SAYS "BOATLOADER UNLOCKED" ON THE TOP LEFT, IF NOT
Type the follow to confirm that it sees your device:
Code:
fastboot devices
If you see you're device, all is good. Now we have to unlock the bootloader with:
Code:
fastboot oem unlock
If it reboots, use adb to go back to the bootloader
Time to flash the recovery with:
Code:
fastboot flash recovery twrp-image-3.img
Finally:
Code:
fastboot reboot
You now have the TWRP recovery on your phone but YOU'RE NOT DONE AS YOU DONT HAVE ROOT PERMISSIONS and your phone should have been wiped clean so you might have to reinput your details.
To finish getting root access:
Make sure youer phone is still plugged in
Download ChainFire's SuperSu on your computer
Move SuperSu from wherever you downloade it to your device
Reboot your phone into recovery by turning it off and turning it back on while HOLDING the UP button.
You should see the TWRP recovery screen.
Click install and choose the SuperSU zip file that you downloaded from ChainFire's site
If you want, you can select "Reboot after Installation" if you wish.
Swipe the slider all the way to right to start the install
Reboot
You should now have SuperSu on your device , allowing you root access
That's all you need if all you wanted is to root, but you're probably going to want BusyBox, Xposed Framework and an Equalizer if you're like me because by default the sound is terrible and Equalizers like Viper4Android makes it a whole lot better and works with Spotify! Let's get started:
How to get BusyBox
It's actually pretty simple.
Go to Play Store
Search "BusyBox"
Download "BusyBox" or "BusyBox Pro" by Stephen(Stericson)
Install it
Open it
Select the directory where you would like it installed, I installed in both "/system/xbin" and "system/bin" for everything to work how I wanted
It will ask you to grant it Root Permissions, select "GRANT"
Wait for it to install
You now have BusyBox!
If you don't know what BusyBox is, to put it shortly , it's a set of command line tools for Unix and Unix-like systems, like Android, to make things a bit more developer friendly. You can read more at he BusyBox official site.
Next I'll show you how to get the
Xposed Framework
Most of this information came from this post so if you need more information, read that post.
Go to Settings > General and select "Security" under the "Privacy" Category.
Scroll down to the "Phone Administration" category and make sure "Unknown Sources" is checked.
Download The Xposed 3.1 apk installer on your phone
Install it
The actual framework won't work because you have to install it in your recovery so then,
Download the LG K7 Xposed Framework image and put it on your phone's internal storage
Reboot into recovery and Install the Xposed Framework image you just put on your device.
Once it is installed, you can reboot and it should be working in the app.
Lastly, if you want better sound, you'll want
ViPER4ANDROiD
Most (if not all) of this information came from this post.
Go to Settings > General > Developer Options
Scroll down to the "Media Category" and select "Use AwesomePlayer (deprecated)" as Viper won't work with NuPlayer
Download SELinux Mode Changer OFFICIAL | MIRROR
Install it
Open it and grant it Root Permissions
Select Permissive Mode
Download this version of ViPER4ANDROiD | MIRRIR
Reboot into Recovery and Install the ViPER4ANDROiD zip file
Once it's done, you can reboot
Open the ViPER4ANDROiD app
It will ask you to install/update the driver
It should continue with no problems and you should have better sound
And you're done! That's everything I know thus far. There are no custom ROMs yet but I want to attempt on working on one(although I've never developed or ported a ROM before) as soon as I get all the information on how to do so . Be sure to thank the Original Posters/Developers and donate to them if you have the means as they put a lot of time and effort into bringing you the best experience possible.
PLEASE PLEASE PLEASE let me know if I forgot something or if there is a type and I will fix it right away!

i have a K7 from metropcs, but sim unlocked working absolutely perfectly on tmobile. all i did was get metropcs to unlock my sim, and i was only with them for nearly 2 weeks, not 90 days. anyways, we have a twrp for the lg k7 thread here on xda too, with lots of other modding talk going on in it http://forum.xda-developers.com/general/general/qa-metro-pcs-lg-k7-lgms330-t3331678 btw, there is no such thing as an official team win recovery project for the k7, it is ported to the k7.

simms22 said:
i have a K7 from metropcs, but sim unlocked working absolutely perfectly on tmobile. all i did was get metropcs to unlock my sim, and i was only with them for nearly 2 weeks, not 90 days. anyways, we have a twrp for the lg k7 thread here on xda too, with lots of other modding talk going on in it http://forum.xda-developers.com/general/general/qa-metro-pcs-lg-k7-lgms330-t3331678 btw, there is no such thing as an official team win recovery project for the k7, it is ported to the k7.
Click to expand...
Click to collapse
Thank you for the reply. I remember seeing this post but wasn't sure if it worked for the K330, I had only put things in this thread that I tested but I will try the image pointed out in your post and add it. I will also edit out the "official twrp" statement. Thanks again for the feedback.

Bughora said:
Thank you for the reply. I remember seeing this post but wasn't sure if it worked for the K330, I had only put things in this thread that I tested but I will try the image pointed out in your post and add it. I will also edit out the "official twrp" statement. Thanks again for the feedback.
Click to expand...
Click to collapse
yea, the k7 isnt popular enough for official twrp

Nice writeup OP.
Unfortunately, I picked up the TMobile branded K7, unlocked the bootloader, then attempted to flash twrp -- I can never boot into TWRP (I get the red exclamation warning).
Is there any hope for me?
If I return it and and then pick up the walmart one will it support my Tmobile 4G/LTE?
Thanks.

ladendroid said:
Nice writeup OP.
Unfortunately, I picked up the TMobile branded K7, unlocked the bootloader, then attempted to flash twrp -- I can never boot into TWRP (I get the red exclamation warning).
Is there any hope for me?
If I return it and and then pick up the walmart one will it support my Tmobile 4G/LTE?
Thanks.
Click to expand...
Click to collapse
its the same phone, doesnt mattrr if metropcs or tmobile. maybe youre not flashing it right? there could be a whole lot of other mistakes you vould be doing as well. describe how you are flashing twrp please, and ill try to help you.

ladendroid said:
Nice writeup OP.
Unfortunately, I picked up the TMobile branded K7, unlocked the bootloader, then attempted to flash twrp -- I can never boot into TWRP (I get the red exclamation warning).
Is there any hope for me?
If I return it and and then pick up the walmart one will it support my Tmobile 4G/LTE?
Thanks.
Click to expand...
Click to collapse
If that's the easiest route for you then yes, I picked up the Walmart Family Mobile version, flashed the T-Mobile kdz and now I'm using the Simple Prepaid plan(which means I get Binge On.)

Bughora said:
If that's the easiest route for you then yes, I picked up the Walmart Family Mobile version, flashed the T-Mobile kdz and now I'm using the Simple Prepaid plan(which means I get Binge On.)
Click to expand...
Click to collapse
you like binge on? i dont. i have their unlimited plan(average around 30gb per month), and disable binge on. id rather watch whatever i watch in its full quality

simms22 said:
you like binge on? i dont. i have their unlimited plan(average around 30gb per month), and disable binge on. id rather watch whatever i watch in its full quality
Click to expand...
Click to collapse
I wasn't aware that they had an unlimited plan but I usually just use it for music and YouTube videos from time to time. The plan I'm on is 40 bucks so I can't complain

Bughora said:
I wasn't aware that they had an unlimited plan but I usually just use it for music and YouTube videos from time to time. The plan I'm on is 40 bucks so I can't complain
Click to expand...
Click to collapse
yea, they do, and its getting more expensive as we go on. i signed up when it was 65, so its 65 for me now as well. but it cost 90 now. when they just started with binge on, i noticed my youtube always lagging. when i disabled it, no more lag, and stuff looks great in 2K

simms22 said:
its the same phone, doesnt mattrr if metropcs or tmobile. maybe youre not flashing it right? there could be a whole lot of other mistakes you vould be doing as well. describe how you are flashing twrp please, and ill try to help you.
Click to expand...
Click to collapse
Thanks, I'll attempt to add more details. I purchased this phone (walmart.com/ip/T-Mobile-LG-K7-TD-Prepaid-Smartphone/51671353).
Model #: LG-K330
Software version: K33010h
1. Used windows (via virtualization) to update to WEB_K33010h_00.kdz and it worked.
1a. enable dev settings, usb debug, oem unlock.
2. Downloaded adb bridge for Mac which comes with adb and fastboot commandline tools
3. plug in phone and ran 'adb reboot bootlader' to enter bootloader in order to use fastboot to unlock
4. run 'fastboot oem unlock', rebooted and use 'adb reboot bootloader' to flash twrp -- I now see bootloader unlocked in upper left
5. run '.fastboot flash recovery twrp-image-3.img' and 'fastboot reboot'
6, at this point I just shut off my phone and attempt to enter recovery with "Reboot your phone into recovery by turning it off and turning it back on while HOLDING the UP button."
It is at that point I see the android icon with a red exclamation. I have to pull out my battery to reboot the phone.
[Sat Oct 22 14:18] ~/Downloads/Android : ./Mac/adb reboot bootloader
[Sat Oct 22 14:18] ~/Downloads/Android : ./Mac/fastboot devices
3da30d9 fastboot
[Sat Oct 22 14:18] ~/Downloads/Android : ./Mac/fastboot flash recovery ~/Downloads/twrp-image-3\(1\).img
target reported max download size of 268435456 bytes
sending 'recovery' (12614 KB)...
OKAY [ 0.401s]
writing 'recovery'...
OKAY [ 0.510s]
finished. total time: 0.913s
[Sat Oct 22 14:21] ~/Downloads/Android : ./Mac/fastboot reboot
rebooting...
finished. total time: 0.001s
[Sat Oct 22 14:21] ~/Downloads/Android : ./Mac/adb reboot recovery
It then reboots and red exclamation.
Click to expand...
Click to collapse

ladendroid said:
Thanks, I'll attempt to add more details. I purchased this phone (walmart.com/ip/T-Mobile-LG-K7-TD-Prepaid-Smartphone/51671353).
Model #: LG-K330
Software version: K33010h
1. Used windows (via virtualization) to update to WEB_K33010h_00.kdz and it worked.
1a. enable dev settings, usb debug, oem unlock.
2. Downloaded adb bridge for Mac which comes with adb and fastboot commandline tools
3. plug in phone and ran 'adb reboot bootlader' to enter bootloader in order to use fastboot to unlock
4. run 'fastboot oem unlock', rebooted and use 'adb reboot bootloader' to flash twrp -- I now see bootloader unlocked in upper left
5. run '.fastboot flash recovery twrp-image-3.img' and 'fastboot reboot'
6, at this point I just shut off my phone and attempt to enter recovery with "Reboot your phone into recovery by turning it off and turning it back on while HOLDING the UP button."
It is at that point I see the android icon with a red exclamation. I have to pull out my battery to reboot the phone.
Click to expand...
Click to collapse
Before step 5, try copying this into the cmd prompt:
Code:
fastboot boot twrp-image-3.img
and then allow it to make modifications to your system. Then go to reboot > bootloader and then let it install supersu, then flash the TWRP image in step 5. This fixed the red triangle problem for me. Also, once you are back in android, tap the notification for SuperSU and tap TWRP to let it finish the process.
Hey, @Bughora I can't seem to boot to recovery via the key combo you describe. I hold Vol-UP and then press and hold power while still holding Vol-UP and also tried without holding power, but it doesn't take me to TWRP. If I hold both Power+Vol-UP, oddly it will start optimizing apps again but if I don't continue to hold Power, it just boots normally... am I misinterpreting what you mean in the OP?
EDIT: Other methods of getting to recovery like "adb reboot recovery" work flawlessly.

QuickNET Tech said:
Before step 5, try copying this into the cmd prompt:
Code:
fastboot boot twrp-image-3.img
and then allow it to make modifications to your system. Then go to reboot > bootloader and then let it install supersu, then flash the TWRP image in step 5. This fixed the red triangle problem for me. Also, once you are back in android, tap the notification for SuperSU and tap TWRP to let it finish the process.
Click to expand...
Click to collapse
You were right on the money. Thank you so much! :good::good::good:

ladendroid said:
Before step 5, try copying this into the cmd prompt:
You were right on the money. Thank you so much! :good::good::good:
Click to expand...
Click to collapse
You're welcome. Also, try this version of TWRP which will let you boot into TWRP with the hardware keys described in the OP. Here is a snippet of the OP explaining how:
Twrp with button combo.
With device off press and hold power and volume down until LG logo pops up quickly release the power and press power quickly until the factory reset dialog pops up press volume down to yes press power to select than it will show the same dialog with yes already selected use power to select and you will be taken to Twrp recovery.
Click to expand...
Click to collapse
I know it says factory reset, but it will take you to TWRP. If you are hesitant (like I was initially), boot to recovery with ADB first, make a backup, and then try it. Good luck, and happy modding!

http://forum.xda-developers.com/android/development/twrp-m1-lg-k7-t3462130

TWRP for T-Mobile & Metro PCS
In case you missed it, czarsuperstar created Twrp for the K7 (Metro/T - Mobile)
(XDA link)
~~~~~~~
update:
Doh! I just saw that the TWRP link is posted just above this post. :silly:

Okay so I'm very new to all this so I apologize ahead of time if my issue is super simple but I don't know what to do. I've been following the steps word for word (had a couple minor hiccups) and I'm at the point where I need to install supersu. I moved the zip file to my internal storage, then when I attempt to restart the phone in recovery mode it automatically goes into download mode followed by freezing at software update, instead of letting me choose to install supersu as the steps state. Can someone help me figure this out please?
EDIT: Well it took me a while but I figured out my issue. From what I understand, the twrp was successfully flashed on my phone but when rebooting the manufacturer kernal was wiping that recovery and replacing with the stock recovery. Instead of rebooting with adb I manually turned off my phone then booted up my phone into the recovery and the twrp menu came up!

Bughora said:
Firstly, I'd like to start by saying that I am making this post because there is little information on the T-Mobile LG K7(K330) and what little information is found is scattered throughout the site.
The LG K7 is a budget phone and you do get the biggest bang for your buck if money is tight. Right now, you can get the Walmart version (for $50!) and flash it to T-Mobile which I will explain in the steps below.
I HAVE ONLY TESTED THIS ON THE WALMART FAMILY MOBILE VERSION OG THE LG K7, THIS PROBABLY WON'T WORK WITH OTHER DEVICES
This is a really great phone and awesome phone to start developing on if one chooses to do so. That being said, let's go ahead and flash the phone to T-Mobile if you haven't already. Most of this information came from Billybobjoe13245's Beautiful Post
Disclaimer: I tested this on Android Lollipop version 5.1.1 and that's what worked. Feel free to try whatever you feel but in any case, I am not responsible for what YOU do to YOUR device, if YOU mess up, YOU will have to deal with the consequnces. Now that that's out of the way,
You're going to need:
Windows Computer with Administative Priviledges (because LG binaries)
An LG K7 (K330)
A USB Cable
About 20 minutes
Once you have all those ready, start downloading the necessary files:
LG UP Software (You're looking for Lab Version 1.10) OFFICIAL | MIRROR
LG Mobile Driver Software(I used ver. 4.0.4.0 but the latest might work) TESTED VERSION | LATEST OFFICIAL
The "WEB_K33010h_00.kdz" file from Billybobjoe13245's Mega Repo
And now it begins.
Install the Mobile Driver Software
Install the LG UP Software
Turn you LG K7 off
Turn on your K7 while holding the DOWN button to boot into Download Mode
Open the LG UP Software
Select "Upgrade" in the separator between the two lists
Hover over "BIN FILE" under "FILE TYPE" and you should see three dots (...) to select a file
Here you select where you've downloaded the WEB file
Click start and let it do it's thing
Once it is finished it will reboot your device and tell you that it has been completed. You should now be able to use a T-Mobile nano-SIM card with absolutely no issues.
Next you Probably want to
ROOT YOUR DEVICE
THIS WILL COMPLETELY WIPE YOUR PHONE SO BACK UP WHATEVER YOU NEED TO
You'll need an internet connection for this to work properly . Let's go:
Make sure your phone has enough charge (%75+)
Go to Settings > General > About Phone > Software Info
Click Build Number 7 times or until it says "You are now a developer"
Go back to General Settings
Go to "Developer Options"
Enable "OEM Unlock"
Enable "USB Debugging"
Next youl'll want to make sure that you have the Android Debug Bridge (ADB) installed. If you don't have it , these guys have your back. Make certain that it is correctly installed and that you can access it using your command line.
Download this Team Win Recovery Project image on your PC (it's from my mirror)
Make sure it 's in the folder that ADB is in or that ADB can recognize
Plug in your phone into your computer if it's not already
You'll want to boot into the bootloader using adb so type:
Wait for it to reboot into the bootloader (shouldn't take long)
MAKE SURE THAT IT SAYS "BOATLOADER UNLOCKED" ON THE TOP LEFT, IF NOT
Type the follow to confirm that it sees your device:
If you see you're device, all is good. Now we have to unlock the bootloader with:
If it reboots, use adb to go back to the bootloader
Time to flash the recovery with:
Finally:
You now have the TWRP recovery on your phone but YOU'RE NOT DONE AS YOU DONT HAVE ROOT PERMISSIONS and your phone should have been wiped clean so you might have to reinput your details.
To finish getting root access:
Make sure youer phone is still plugged in
Download ChainFire's SuperSu on your computer
Move SuperSu from wherever you downloade it to your device
Reboot your phone into recovery by turning it off and turning it back on while HOLDING the UP button.
You should see the TWRP recovery screen.
Click install and choose the SuperSU zip file that you downloaded from ChainFire's site
If you want, you can select "Reboot after Installation" if you wish.
Swipe the slider all the way to right to start the install
Reboot
You should now have SuperSu on your device , allowing you root access
That's all you need if all you wanted is to root, but you're probably going to want BusyBox, Xposed Framework and an Equalizer if you're like me because by default the sound is terrible and Equalizers like Viper4Android makes it a whole lot better and works with Spotify! Let's get started:
How to get BusyBox
It's actually pretty simple.
Go to Play Store
Search "BusyBox"
Download "BusyBox" or "BusyBox Pro" by Stephen(Stericson)
Install it
Open it
Select the directory where you would like it installed, I installed in both "/system/xbin" and "system/bin" for everything to work how I wanted
It will ask you to grant it Root Permissions, select "GRANT"
Wait for it to install
You now have BusyBox!
If you don't know what BusyBox is, to put it shortly , it's a set of command line tools for Unix and Unix-like systems, like Android, to make things a bit more developer friendly. You can read more at he BusyBox official site.
Next I'll show you how to get the
Xposed Framework
Most of this information came from this post so if you need more information, read that post.
Go to Settings > General and select "Security" under the "Privacy" Category.
Scroll down to the "Phone Administration" category and make sure "Unknown Sources" is checked.
Download The Xposed 3.1 apk installer on your phone
Install it
The actual framework won't work because you have to install it in your recovery so then,
Download the LG K7 Xposed Framework image and put it on your phone's internal storage
Reboot into recovery and Install the Xposed Framework image you just put on your device.
Once it is installed, you can reboot and it should be working in the app.
Lastly, if you want better sound, you'll want
ViPER4ANDROiD
Most (if not all) of this information came from this post.
Go to Settings > General > Developer Options
Scroll down to the "Media Category" and select "Use AwesomePlayer (deprecated)" as Viper won't work with NuPlayer
Download SELinux Mode Changer OFFICIAL | MIRROR
Install it
Open it and grant it Root Permissions
Select Permissive Mode
Download this version of ViPER4ANDROiD | MIRRIR
Reboot into Recovery and Install the ViPER4ANDROiD zip file
Once it's done, you can reboot
Open the ViPER4ANDROiD app
It will ask you to install/update the driver
It should continue with no problems and you should have better sound
And you're done! That's everything I know thus far. There are no custom ROMs yet but I want to attempt on working on one(although I've never developed or ported a ROM before) as soon as I get all the information on how to do so . Be sure to thank the Original Posters/Developers and donate to them if you have the means as they put a lot of time and effort into bringing you the best experience possible.
PLEASE PLEASE PLEASE let me know if I forgot something or if there is a type and I will fix it right away!
Click to expand...
Click to collapse
Recovery error 1003
Other then that phone is working fine lgk7 k330. How do I fix this ?

johnsmith1987 said:
Recovery error 1003
Other then that phone is working fine lgk7 k330. How do I fix this ?
Click to expand...
Click to collapse
Try installing this official version of TWRP with the TWRP app. Or using this command in terminal
Code:
dd if='/path/to/TWRP/image' of='/dev/block/bootdevice/by-name/recovery'
Also, if that doesn't work. It's most likely because you didn't unlock the bootloader. Go to "Step Nine: Unlocking The Bootloader" on this thread http://forum.xda-developers.com/general/general/ref-metro-pcs-lg-k7-lgms330-t3362555

Billybobjoe13245 said:
Try installing this official version of TWRP with the TWRP app. Or using this command in terminal
Also, if that doesn't work. It's most likely because you didn't unlock the bootloader. Go to "Step Nine: Unlocking The Bootloader" on this thread http://forum.xda-developers.com/general/general/ref-metro-pcs-lg-k7-lgms330-t3362555
Click to expand...
Click to collapse
Ill try again
I have oem unlock checked

Damaged recovery, unable to ADB debugging, bootloop

[HELP] [URGENT]
//this is the story, skip if you prefer
so i was updating my cm 12.1 rom to rr 7.1 rom
everything was fine, no real mess just bad flash so i decided to reflash the rom (dunno why i did that actually, its just my tradition). Aaaaand the ROM went flawlessly
next step is install supersu, i checked that the rom is pre-rooted so i think its easier to get supersu via playstore. Installing supersu went flawlessly (again) and i rebooted ma phone.
//then everything starts to f***ed up
my phone bootlooped (not a big deal actually, done with this sh** all the time)
like a casual day, reflash my phone. but i cant go to recovery mode its stuck at logo i think that supersu binary damaged ma recovery.img (again not a big deal but i started to worry) i connect my phone to my pc, summon my adb, and hope the best, but my devices not listed there. then i remembered i forgot to turn on usb debugging on setting oh crap!
so here is my question:
is it possible to turn on usb debugging via pc or something else? if so how.
is it possible to use adb feature without my phone being turned on its usb debugging?
is it possible to repair my recovery <== i mean reflash beside using adb. if so how :crying:
and the last one, beside my phone not listed on adb device list. it wont showed or recognized in my pc (do i need something else beside usb and adb driver?)
any help will be appreciated :good:
this is my only phone so i put my hands on you guys, you're the superhero here
if i dont have any solution, my only way is send this phone to service centre :crying:
some info:
devices : lenovo a6k plus
old rom : cm 12.1 by ED300
new rom: rr nougat v5.8.0 (i dont remember who made this rom, sorry. by the way i found the rom somewhere in xda)
supersu ver: newest per 21 Feb 2k17 (playstore)
my pc: win 8 64x <== dunno if this info useful though
old recovey: twrp (forget the version, but im pretty sure the recovery made by russian developer and it has chicken logo during startup)
battery level when i discovered i cant go to recovery mode: somewhat near 16% <== maybe helpful
if you really care to help me just tell me what do you know, i would appreciate that really, i meant that because this phone is the only way i can contact all of my super important buddy for my business.
Thanks anyway, regards Tom

Well take out the battery and return it hold volum down + power button now you should be able to use fastboot commands go to the folder where you have your adb and fastboot there paste a recovery img file you want to use.Open cmd and type fastboot flash recovery nameofyourimg.img
And now you should be able to use recovery.If not try qfil debricking method that you can find on forum.Best of luck if somthing isnt clear enough feel free to PM me.Also download new recoveries that are now officialy developed

Thanks for replying JovanSijacki
unfortunate enough, i have done that and still dope and nope.
usually i can find my device in windows device manager named android with yellow triangle, but this one is different, my computer wont recognize my phone.
will try debricking method instead, thank you dude :smile:

Thank you for those who care to reply, friend of mine who are expert developer told me how to fix this. AS LONG AS YOU ABLE TO GET INTO FASTBOOT MODE YOU ARE SAFE. Im going to make separate thread to share the tutorial *insert smiley emoji*

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