Database Users

How to unlock bootloader if I have no access to Android GUI?

Hi guys,
a week ago my ZUK Z1 started to bootloop without any evident reason.
I found it in this state picking it up from my pocket, so I guessed it was due to some random reboot that occasionally happened to it.
So, stating that:
- I'm with original stock CyanogenOS,
- I never rooted, or even accessed to the recovery menu prior to this event,
- I'm perfectly able now to communicate and send commands to device via adb or in fastboot mode,
problem is that I did NOT enable "USB debugging" and I did NOT OEM unlock when I had the chance to reach Developer options menu through the Android GUI (now I'm blocked by bootloop), resulting in an obvious "no unlocked device" error message each time I try to flash or write system partitions.
The output from "fastboot oem get-info" confirms this status.
I'm operating from a shell with adiministrator's grant in Windows 8.
No luck with "fastboot oem unlock", "fastboot flashing unlock_critical" or "adb root".
I used also "-i 0x2b4c" (vendor code) option in my commands.
Then, my question for you:
is there still a way to unlock bootloader in order to recover with CyanogenOS stock image, in this condition?
I saw there's a "debuggable" image on Cyanogen site, but I've no hint on how to use it and if it could help me.
Maybe ZUK has to provide to me an unlock key: I read on this forum that OnePlus and Huawei have similar option.
Thanks a lot in advance for any hint and suggestion you can give to me.

---------- Post added at 05:43 PM ---------- Previous post was at 05:43 PM ----------
[/COLOR]
dalviking said:
Hi guys,
a week ago my ZUK Z1 started to bootloop without any evident reason.
I found it in this state picking it up from my pocket, so I guessed it was due to some random reboot that occasionally happened to it.
So, stating that:
- I'm with original stock CyanogenOS,
- I never rooted, or even accessed to the recovery menu prior to this event,
- I'm perfectly able now to communicate and send commands to device via adb or in fastboot mode,
problem is that I did NOT enable "USB debugging" and I did NOT OEM unlock when I had the chance to reach Developer options menu through the Android GUI (now I'm blocked by bootloop), resulting in an obvious "no unlocked device" error message each time I try to flash or write system partitions.
The output from "fastboot oem get-info" confirms this status.
I'm operating from a shell with adiministrator's grant in Windows 8.
No luck with "fastboot oem unlock", "fastboot flashing unlock_critical" or "adb root".
I used also "-i 0x2b4c" (vendor code) option in my commands.
Then, my question for you:
is there still a way to unlock bootloader in order to recover with CyanogenOS stock image, in this condition?
I saw there's a "debuggable" image on Cyanogen site, but I've no hint on how to use it and if it could help me.
Maybe ZUK has to provide to me an unlock key: I read on this forum that OnePlus and Huawei have similar option.
Thanks a lot in advance for any hint and suggestion you can give to me.
Click to expand...
Click to collapse
Sideload the official stock rom with zuk z1 tool. That s how i managed to un-brick my zuk. Download the stock rom , cm-12.1-YOG4PAS3OH-ham-signed.zip from this page https://cyngn.com/support. Use the toolkit provided here : http://forum.xda-developers.com/zuk-...alpha-t3235964 to sideload the rom. Wait until the phone restarts and thats it. You must also install adb and fastboot and have adb driver installed.I used the shenqi adb composite driver, but i guess the universal adb driver can work too. I had the same problem. Stuck in bootloop with USB debugging not enabled and bootloader locked.
Or you can try to fastboot the stock rom with the command provided in this useful tool.

Extentho said:
---------- Post added at 05:43 PM ---------- Previous post was at 05:43 PM ----------
[/COLOR]
Sideload the official stock rom with zuk z1 tool. That s how i managed to un-brick my zuk. Download the stock rom , cm-12.1-YOG4PAS3OH-ham-signed.zip from this page https://cyngn.com/support. Use the toolkit provided here : http://forum.xda-developers.com/zuk-...alpha-t3235964 to sideload the rom. Wait until the phone restarts and thats it. You must also install adb and fastboot and have adb driver installed.I used the shenqi adb composite driver, but i guess the universal adb driver can work too. I had the same problem. Stuck in bootloop with USB debugging not enabled and bootloader locked.
Or you can try to fastboot the stock rom with the command provided in this useful tool.
Click to expand...
Click to collapse
Thanks a lot Extentho for your feedback.
I've already tried your fair suggestion: unfortunately, I'm stuck at the end of sideloading the signed .zip.
In fact, I see on screen logs that it's applying the update "unconditionally" (that sounds good), but nevertheless, when finished it returns "xfer: 1.00x" on PC shell and in recovery menu, on device.
Now, either if I reboot or power down and boot it again, the result is the same: still bootloop-ing.
Of course, at any other attempts leveraging on administrative privilege, it says that "device is locked", including those done through the shell tool.
Some excerpts from my last launched commands:
c:\_APP\CM>adb devices
List of devices attached
51f8941d sideload
c:\_APP\CM>adb shell
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb root
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb usb
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: closed
c:\_APP\CM>adb kill-server
c:\_APP\CM>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
51f8941d sideload
c:\_APP\CM>adb sideload cm-12.1-YOG4PAS3OH-ham-signed.zip
Total xfer: 1.00x

You must have the phone in sideload mode. There is an option to sideload in recovery menu.
Then use the command to sideload from the toolkit. The stock rom must pe renamed sideload and placed on desktop.
If the phone communicates in any way with pc, there is still hope. When you start the sideload process from pc, the phone should show an animation showing the flashing process. Post some pictures from where you are stuck, so i can make an idea about what is going on

my zuk z1 stuck to bootloop,
and android debugging is disabled.
phone can not detecting in fastboot mode.
please help.

Extentho said:
You must have the phone in sideload mode. There is an option to sideload in recovery menu.
Then use the command to sideload from the toolkit. The stock rom must pe renamed sideload and placed on desktop.
If the phone communicates in any way with pc, there is still hope. When you start the sideload process from pc, the phone should show an animation showing the flashing process. Post some pictures from where you are stuck, so i can make an idea about what is going on
Click to expand...
Click to collapse
I've tried also with the toolkit, but it's heavy bugged (also in 5.4 version) and, after all, it gets the exact same problem like me (not surprising, it launches my same commands ).
There's no useful image or snapshot I can share, because I see the animated green android logo moving its antennas on my device, while logs below saying that it's verifying package and then it's unconditionally overwriting system partition.
It seems all so normal and plain.
At the end of the process, no "installation complete" message, but simply I get back to recovery menu (where I started from).
In other attempts, I also wiped cache and user data, prior to rebooting, just to test if it was going to change something, but no luck.
The phone reboots, the "Cyanogen" logo starts to glow for 7/8 times and then... bzzzz, short vibration and all over again (i.e. bootloop).
I tried with an older official signed .zip from Cyanogen OS (cm-12.1-YOG4PAS3AJ-ham-signed, instead of newer cm-12.1-YOG4PAS3OH-ham-signed), but even worst, it fails at "verify package" step, aborting procedure.
MD5 signatures triple-checked each time versus source.
I saw some threads where it seems possible to change the bit, on system image, controlling developer option, to manually post-enable unlocking, but it's suitable only for Nexus or OnePlus One. No instructions for ZUK Z1.
Or maybe do I need a "donor" sharing a stock .zip with this option yet enabled?
Bootloop would be still there, but I possibly could enable to "flash", "boot" and "shell" vs the device, giving me much more options to try.
One last doubt anyway. If I press "Volume Down" + "Power" button at boot, I get into a menu like this:
http: // postimg.org/image/s5badiefh/ (remove extra spaces).
Viewing other examples posted on forums, I noted that at least the "Factory reset" is missing.
Could it be an hint for anything useful?

dalviking said:
I've tried also with the toolkit, but it's heavy bugged (also in 5.4 version) and, after all, it gets the exact same problem like me (not surprising, it launches my same commands ).
There's no useful image or snapshot I can share, because I see the animated green android logo moving its antennas on my device, while logs below saying that it's verifying package and then it's unconditionally overwriting system partition.
It seems all so normal and plain.
At the end of the process, no "installation complete" message, but simply I get back to recovery menu (where I started from).
In other attempts, I also wiped cache and user data, prior to rebooting, just to test if it was going to change something, but no luck.
The phone reboots, the "Cyanogen" logo starts to glow for 7/8 times and then... bzzzz, short vibration and all over again (i.e. bootloop).
I tried with an older official signed .zip from Cyanogen OS (cm-12.1-YOG4PAS3AJ-ham-signed, instead of newer cm-12.1-YOG4PAS3OH-ham-signed), but even worst, it fails at "verify package" step, aborting procedure.
MD5 signatures triple-checked each time versus source.
I saw some threads where it seems possible to change the bit, on system image, controlling developer option, to manually post-enable unlocking, but it's suitable only for Nexus or OnePlus One. No instructions for ZUK Z1.
Or maybe do I need a "donor" sharing a stock .zip with this option yet enabled?
Bootloop would be still there, but I possibly could enable to "flash", "boot" and "shell" vs the device, giving me much more options to try.
One last doubt anyway. If I press "Volume Down" + "Power" button at boot, I get into a menu like this:
http: // postimg.org/image/s5badiefh/ (remove extra spaces).
Viewing other examples posted on forums, I noted that at least the "Factory reset" is missing.
Could it be an hint for anything useful?
Click to expand...
Click to collapse
For me, this method worked exactly as described, booting into stock rom correctly.
now, if you mentioned it in the picture, there is another option. so, i ve noticed too this menu. There is an app called QPST wich can help you. Follow this thread: http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257 .
So when you enter in QFIL, connect the phone to computer and boot with volume down+ power into this menu from your picture. The Qfil app should detect some ports. You must choose the 9008 one, from what i have read.
Anyway, for me this method, didn t work because the pc couldn t detect the right port, only the zuk tookit did it for me.
You read the thread i suggested, and try that method, it may work for you.

Extentho said:
For me, this method worked exactly as described, booting into stock rom correctly.
now, if you mentioned it in the picture, there is another option. so, i ve noticed too this menu. There is an app called QPST wich can help you. Follow this thread: http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257 .
So when you enter in QFIL, connect the phone to computer and boot with volume down+ power into this menu from your picture. The Qfil app should detect some ports. You must choose the 9008 one, from what i have read.
Anyway, for me this method, didn t work because the pc couldn t detect the right port, only the zuk tookit did it for me.
You read the thread i suggested, and try that method, it may work for you.
Click to expand...
Click to collapse
Thanks again Extentho.
I saw QPST trick, but it's not catching right port and/or not getting right permission to stop phone from re-booting.
I think that adb/toolkit method should work also for me. I made attempts with other official ROMs: I noticed that for the older ones, the result is a bit different. They get stuck in a "black screen + notify led lighted in blue" state, rather than bootlooping.
Maybe erasing system partitions is needed, but I'm very reluctant to such dangerous way, without expertised advice.
Weirdest thing is that I did anything to get this situation, I just found my device in this mess.
Of course ZUK official support is well silent at my requests.

dalviking said:
Thanks again Extentho.
I saw QPST trick, but it's not catching right port and/or not getting right permission to stop phone from re-booting.
I think that adb/toolkit method should work also for me. I made attempts with other official ROMs: I noticed that for the older ones, the result is a bit different. They get stuck in a "black screen + notify led lighted in blue" state, rather than bootlooping.
Maybe erasing system partitions is needed, but I'm very reluctant to such dangerous way, without expertised advice.
Weirdest thing is that I did anything to get this situation, I just found my device in this mess.
Of course ZUK official support is well silent at my requests.
Click to expand...
Click to collapse
Try to post some pics about the troubles you encounter. If we receive a solution, this may be helpful for all of us in the future. Now, exactly, what can you acces on phone(recovery, fastboot, )?
Also, check varios threads from other phones with the same problems(one plus one, lg , htc) ,etc. Find a solved situation like yours, and we may adapt that solution to you

Hi guys,
Just to close this topic.
I was finally able to install the ZUI ROM through the QFIL program.
It's a little bit tricky, due to the fact that it is strongly suggested:
- to use a Windows 7 machine started without Signature Enforcement enabled;
- to start QFIL (admin mode) and be prepared with all needed files loaded in its GUI;
- to power off the phone, then, while pressing volume up button, inserting the USB cable, attached (better if) on a 2.0 port to PC;
- to be fast pressing "Download" button on QFIL program.
After that, I unlocked the bootloader and performed a lot of alternative recovery process.
So, I installed on the device:
- ZUI ROM
- Cyanogen OS convert from ZUI ROM
- Cyanogen OS last updated ROM
- CyanogenMod 12.1 last nightly ROM
- CyanogenMod 13.0 last nightly ROM
and the winner is...
...
...
...
... none of the above.
Each time the very same behaviour: bootloop. So, my last conclusion is: hardware failure (I guess wi-fi module).
I give up.
But for anyone searching a safe way to unlock a bootloader without accessing to developer options: the QFIL method works like a charm (once installed properly).
Thanks for support.

Messed my zuk z1
I tried to flash stock room in my zuk z1 , I downloaded Qualcomm file for the ROM and installed the required in my laptop,I wiped all data in my phone using TWRP .though my power button is not working I used tool kit to reboot my phone by connecting into fast boot mode,here comes the prob by mistake I entered the wrong command which locks my bootloader .I don't know what to do...help me.....

Root Solution for Honor ShotX/7i

Hey everyone, think its a bit sad that we dont got our own phone section since ShotX/7i and the regular 7 doesnt share the same cpu architecture so forgive me for cluttering down but just wanted to try and help our fellow honor comrades
The files to do this is taken from the chinese huawei forum (http://club.huawei.com/thread-5761110-1-1.html) and thus I take no credit for the files, im merely making a english guide with chinese files to hopefully spur some development.
The root itself was made for Honor 7i which is the asian market version (I believe?) but ShotX is the same phone but for international market (with LTE 800Mhz band, not sure if there are any other differences) and root was performed and confirmed working by me on my ShotX with Lollipop 5.1.1/B130 firmware so no guarantes if it will work on other firmwares. Im also not responsible if you brick your phone or it catches on fire etc.
First you need to unlock your bootloader
and to do so you will first need to turn on the "allow bootloader oem unlock" so enter settings, about phone, and then press build number 10 times to activate "developer mode".
Go back one step into main settings and the open developer settings, find and enable "allow bootloader oem unlock" (if you have fingerprint or any other code activated then it will ask you for that code) and while you are in here make sure to click "enable usb debugging" aswell.
You will also need a bootloader unlock code from huaweis site by filling out the necessary information on this page http://emui.huawei.com/en/plugin.php?id=unlock&mod=detail
Product model: HUAWEI ATH-UL01 (settings->about phone->model number)
Product serial number: EGQ7Nxxxxxxxxxxx (settings->about phone->Status->Serial number)
Product IMEI: xxxxxxxxxxxxxxx (*#06# IMEI1 or settings->about phone->Status->IMEI1)
Product ID: xxxxxxxx (*#*#1357946#*#*)
So once youve got the code, make sure to write it down on a safe place, next you need adb toolkit. May I recommend Minimal ADB? http://forum.xda-developers.com/showthread.php?t=2317790
Now when you´ve come this far, remember that as soon as you unlock your bootloader, the phone will factory reset and you will loose any data and settings made unless you make a backup before
Insert usb data cable into pc and phone, open command prompt and be in your adb installation directory.
Start with typing "adb devices" to see if your phone is detected and make sure to check on your phone when it asks for permission that you allow your pc. I was running windows 10 x64 when I rooted my phone and I didnt need any driver but your mileage may vary if on w7 or w8. Remember to use "adb kill-server" if you experience issues when trying to connect phone with adb.
If phone is detected then you should get something like
Code:
EGQ7Nxxxxxxxxxxx device
Then all is good and you can type
adb reboot bootloader
Now to check if phone still is with us you type
fastboot devices and you should see something like
Code:
8b0dd496 fastboot
If you are still with us then type fastboot oem unlock xxxxxxxxxxxxxxxx where the xxxx´es represent your bootloader unlock code which you should have retrieved earlier from huaweis site.
To confirm that your bootloader is unlocked, simply type fastboot oem get-bootinfo and you should see
Code:
(bootloader) Bootloader Lock State: UNLOCKED
Congrats! Now youre ready to root the phone
If you recently unlocked bootloader then you need to activate developer settings again and turn on usb debugging aswell.
Download the files below
https://mega.nz/#!BsQiiYpL!xVwbyHTRsVGFsO6LpJacxP64gFrOlCNTRHTI1-vdLLw TWRP install program
https://mega.nz/#!9hQi2I7A!JX121sJ2vChMuxrx1puxf-L1rP9LSPaJW-JnqvEAzIg Root
Put the EMUI3.1 Android 5.1 ROOT补丁（不要双清不要解压.zip file somewhere on your phones memory storage where you can find it.
Unzip the 荣耀7i TWRP recovery.zip and open it up and then you press the second button which says TWRP REC and it should flash twrp. Power off phone and then press vol+ and power where you keep pressing vol+ but let go off power as soon as screen is lit and you should be in recovery in a bit. If you still got the default huawei recovery then redo the procedure (I pressed TWRP REC at first but didnt see any twrp installed so I then just pressed REC just to be disapointed again but 3rd time with TWRP REC it worked so not sure what goes on but just so you know if you also fail to get TWRP installed)
Once youre in twrp you will be greeted with chinese again but buttons are located on same spots so just compare it to a english twrp image https://en.wikipedia.org/wiki/TWRP#/media/File:TWRP_2.7.0.0.png
Just press top left button and select the root file you should have putted on your phone earlier and flash it, when its done just hold the physical power button to reset incase you´re unsure of the reboot button and you should be good to go
Grats on your rooted phone, after some cleanup (possible with root) this phone is flying like never before
Some highly recommended root apps
Rom toolbox lite, so you can flash roms/mods without knowing your way in the chinese twrp and uninstall apps etc
https://play.google.com/store/apps/details?id=com.jrummy.liberty.toolbox&hl=sv
Kernel adiutor, great for getting a bit more performance out of the phone by tweaking cpu and gpu speed
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=sv
And lastly the great snapdragon camera which is pretty fast and nice to use which you need to flash in twrp (or with rom toolbox)
http://forum.xda-developers.com/showpost.php?p=64410821&postcount=44
Its for one+ x but it works as expected for our ShotX/7i aswell (Obvisually dont use this if youre on a regular Honor 7 device since it doesnt have snapdragon processor)

thank you very much , I'll be trying my XShot

Theres a translated twrp now for those that wants
http://forum.xda-developers.com/honor-7/development/unsupported-twrp-honor-7i-shotx-t3323072

-help twrp bootloop
hey i rooted my shot x and worked fine, but then i did a factory reset and now its on twrp bootloop. any ideas to fix this? do you have a rom for this phone? because im trying to donwload one but its slow as f**
I think if i install a rom with twrp it will work but not sure
help pls
TY!

lucaspsara said:
hey i rooted my shot x and worked fine, but then i did a factory reset and now its on twrp bootloop. any ideas to fix this? do you have a rom for this phone? because im trying to donwload one but its slow as f**
I think if i install a rom with twrp it will work but not sure
help pls
TY!
Click to expand...
Click to collapse
Sorry, sold my shot x as there was so little dev interest. The only moderate source of files for it was on the chinese huawei forums :/

something changed? still no intrested by developers?

Please help me. Honor ShotX flash tool firmware.
ATH-UL01-C185B310
Android version 6.0.1 firmware.
Please help me.

Did u root your shotx?

tndb said:
Sorry, sold my shot x as there was so little dev interest. The only moderate source of files for it was on the chinese huawei forums :/
Click to expand...
Click to collapse
Did you tried russian forums? 4pda or others, often they have good devs there for some devices,which are not supported here on XDA.

Anyone who can't get to bootloader unlock site after login. Follow this [GUIDE] :
https://forum.xda-developers.com/ge...nor-bootloader-unlock-code-t3441130?nocache=1
This helped me. Hope you also get the help.
Credits to : Thor

Is there any solution for ShotX with android 6.0?

Please upload android 6.0.1 rooted room

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

Huawei P9 Lite stuck on bootloop, can't enter recovery mode

Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken

There are few different versions of P9 Lite, look at the back of the phone to the bottom to see the numbers beside VSN and let us know.
1) Also when the phone is turned off plug in the usb to a computer or charging adapter
2) Hold down volume up & power
3) Let go of the power button when you feel the buzz while still holding the volume up button
4) Download latest version & recovery.
5) Go to Settings>Developer Options>USB Debugging On
5B) If you don't see Developer Options in settings, then go to Settings>About Phone>Build Number & ( tap the Build Number untill it unlocks)
6) Update us on the status, hope it works out.

GloryNation said:
There are few different versions of P9 Lite, look at the back of the phone to the bottom to see the numbers beside VSN and let us know.
1) Also when the phone is turned off plug in the usb to a computer or charging adapter
2) Hold down volume up & power
3) Let go of the power button when you feel the buzz while still holding the volume up button
4) Download latest version & recovery.
5) Go to Settings>Developer Options>USB Debugging On
5B) If you don't see Developer Options in settings, then go to Settings>About Phone>Build Number & ( tap the Build Number untill it unlocks)
6) Update us on the status, hope it works out.
Click to expand...
Click to collapse
tried to enter recovery, still not work. can't go to developer options because phone is stuck on logo, can't power off. couldn't find any solution that works anywhere, been searching for more than 6 hours, still no use. phone model is VNS-L21 forgot to mention earlier

What exactly were you doing before this happened and does your computer recognize your phone when plugged in at all.
Try holding volume up & down together & plug phone in when it reboots on you, & report back with what you see. If anything at all.

GloryNation said:
What exactly were you doing before this happened and does your computer recognize your phone when plugged in at all.
Try holding volume up & down together & plug phone in when it reboots on you, & report back with what you see. If anything at all.
Click to expand...
Click to collapse
I tried to install nougat update, computer recognizes it only in fastboot. holding volume buttons haven't changed anything still no progress. the thing is i had installed nougat a moth or so ago and it worked fine, then rolled back to marshmallow and now this. i'm pretty sure i tried to install correct package, because it was the same i had installed earlier

Did you download a adb tool on your computer that have the 'fastboot.exe' file? If so open that folder,
Have the mouse curser hover in that folder, hold down shift & right click the mouse
Open command prompt
Connect phone as is in fastboot mode
Type adb devices & press enter
Type adb continue & press enter

Hi,
I have the same issue as ellanyx.
my phone can only be stucked while booting or if I connect my phone to a computer, I'm able to boot it in fastboot.
as ellanyx, I didn't enable usb-debug nor OEM unlock option...
so when I'm in fastboot, I type the command "fastboot oem unlock xxxxxx" (hopefully the different data needed are the correct ones mentioned on the box of the phone) I get this error message:
C:\Users\Dieu\Downloads\SRKToolHuawei-STABLE-V1.3-20160619>fastboot oem unlock xxxxx
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
and off course the other options like "fastboot flash recovery recovery.img "... doesn't work.
I can't use the adb commands neither.
when I type the commande, as mentioned above, "adb devices" or "adb continue", nothing works.
So I'm a bit desesperate
do you have any solution for this kind of issue?
thanks

Dude, so the last firmware on your phone was MM or N? If it was MM you should put stock firmware appropriate for your model in dload folder on SD card and put volume+volume-power, and thats it. If you stack on N,....then I dont know because dload method doesnt work with N, or maybe works if you can find stock firmware with recovery for N.
Regards

Unfortunately I can't update with the 3 button update otherwise it would indeed solvemy problem.

pyromana said:
Unfortunately I can't update with the 3 button update otherwise it would indeed solvemy problem.
Click to expand...
Click to collapse
Probably you didnt have correct Oeminfo for MM if dload method didnt work....Try to conect phone with Toolkit and follow procedure for flashing oeminfo and custombin, after that flash stock recovrry and b161 via dload metod. You will find it on forum here.
Regards

the procedure from SRK toolkit?
would it be possible to provide it? because I can't unlock the OEM and I didn't tick the USB debug think.

Maybe problem with the ps not phone so u can not connect with adb
Try with different pc you must have flash oem with fast boot without enable adb from phone if u in fastboot

I can only boot my phone in fastboot (vol- + power) and not in recovery (vol+ + power).
also when using the SRK toolkit, the first screen tells me to be sure that the usb debugging is enable, which I haven't done...
if I'm not mistaken, fastboot is to use the fastboot command and recovery the adb commands
the connection with fastboot works on my computer, the link is made. however when I type the command to unlock the OEM, I get an error stating that the command is not allowed.
when I use the SRK toolkit, with the different questions, he tries to connect the phone with adb and waiting.... waiting...
is there a command to reboot in recovery but from fastboot? in the otherway around it exists but it doesn't seem that from fastboot to recovery it exists.
thanks.

Alexxxx1 said:
Dude, so the last firmware on your phone was MM or N? If it was MM you should put stock firmware appropriate for your model in dload folder on SD card and put volume+volume-power, and thats it. If you stack on N,....then I dont know because dload method doesnt work with N, or maybe works if you can find stock firmware with recovery for N.
Regards
Click to expand...
Click to collapse
dload method works on N. I downgraded my phone from unofficial N update back to official MM update using this method yesterday. You just have to enable OEM at developer options on settings.

It looks like people can't be bothered to read the 1st post properly before they reply.
HE CAN NOT BOOT TO ANDROID SO HE CAN NOT ENABLE OEM OR ACTIVATE USB DEBUGGING!!!!
What he CAN do, is go into eRecovery and Fastboot.
With that in mind, I would suggest using the dload method through fastboot.
Also, make sure it is Huawei SRK Tools 2.0 that is used, as it actually asks if you are in debug mode or fastboot.
Note that there is a few bugs in SRK 2.0:
The TWRP recovery file has the wrong filename in the package, so it WILL fail unless you name it correctly.
Also, when trying to root, do NOT use the "P9 Lite" method as that WILL fail too. Use the "P9/P9 Plus" method.
I am trying to set up a complete guide that can restore the phone when it is stuck in fastboot, however I apparently went a step too far...

ellanyx said:
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken[/QUOTE
Do you have TWRP recovery ?
---------- Post added at 09:55 AM ---------- Previous post was at 09:50 AM ----------
ellanyx said:
Hello, I'm new to xda, in fact I registered just to ask for help. My p9 lite got stuck on huawei logo, when i try to turn off the device it just reboots 2 times and then just stays on huawei logo. I can enter fastboot and rescue mode, but i have not enabled usb debugging and oem unlock on the device earlier. To be honest this is my first android device, in the past i used only windows phones, so you could say i'm completely new to this. Any suggestions on how to recover my phone or flash any rom into it? I'd be very glad if someone helped me find the solution to this problem. Not sure if i made a thread in the correct place, direct me if i'm mistaken
Click to expand...
Click to collapse
Boot into fastboot mode and flash a custom recovery by meticulus. Link : meticulus.co.vu
Then whenyou get stuck hold power and vol down button for 2 minutes the phone will reboot and then when it says that your device has been unlocked and cant be trusted then only press vol up key ( dont press power button then). The u get into huawei recovery. From that u should power off the phone. Now get a custom rom by meticulus into your device sd card ( Cyanogenmod 13 is recommended ). Then insert sd card in a powered off phone. Now press vol up and power key and flash gapps and custom rom and you are good to go.
Click to expand...
Click to collapse

So, MY question:
I have tried 4 times to get Nougat installed, but every time I got the SMALL package (1.25gb) which means it is not complete.
I decided to try ONE more time, but think I have made a serious mistake.
I was on B161 and tried to downgrade to B160 without upgrading to Nougat first.
This has caused my phone to be stuck at boot with the message "Your device is booting now..."
I can NOT get into eRecovery or fastboot no matter what I do.
If I just leave the phone, then it discharge very fast, but as soon as I plug it in, it starts up and gets stuck at the same screen again.
Does anyone have ANY idea about how I can get out of this problem?
UPDATE:
I have managed to boot to fastboot while connected to my pc.
The phone is unlocked but FRP is LOCKED, which means I can't flash anything.
I read about using Miracle Loader to remove the FRP lock, but it can't "see" my phone. Maybe I am doing it wrong?

SnowmanDK said:
So, MY question:
I have tried 4 times to get Nougat installed, but every time I got the SMALL package (1.25gb) which means it is not complete.
I decided to try ONE more time, but think I have made a serious mistake.
I was on B161 and tried to downgrade to B160 without upgrading to Nougat first.
This has caused my phone to be stuck at boot with the message "Your device is booting now..."
I can NOT get into eRecovery or fastboot no matter what I do.
If I just leave the phone, then it discharge very fast, but as soon as I plug it in, it starts up and gets stuck at the same screen again.
Does anyone have ANY idea about how I can get out of this problem?
UPDATE:
I have managed to boot to fastboot while connected to my pc.
The phone is unlocked but FRP is LOCKED, which means I can't flash anything.
I read about using Miracle Loader to remove the FRP lock, but it can't "see" my phone. Maybe I am doing it wrong?
Click to expand...
Click to collapse
Try to relock and then unlock the bootloader again. And make sure oem unlocking is enabled in dev options

Arsaam said:
Try to relock and then unlock the bootloader again. And make sure oem unlocking is enabled in dev options
Click to expand...
Click to collapse
Please read my previous post again
I can NOT boot normally. And as FRP is locked, then I can't relock or unlock the bootloader.

SnowmanDK said:
Please read my previous post again
I can NOT boot normally. And as FRP is locked, then I can't relock or unlock the bootloader.
Click to expand...
Click to collapse
Go to fast boot mode and from their try to flash meticulus recovery.
You can also try the adb method as well.
Visit meticulus.co.vu

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