Related
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
wbexpress said:
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
Click to expand...
Click to collapse
If you have a T-Mobile device you are able to root etc. Make sure you have usb debugging enabled, and tick enable oem unlock in developer options. I presume you have a driver issue. Just go ahead and reinstall the drivers and try again.
markbencze said:
If you have a T-Mobile device you are able to root etc. Make sure you have usb debugging enabled, and tick enable oem unlock in developer options. I presume you have a driver issue. Just go ahead and reinstall the drivers and try again.
Click to expand...
Click to collapse
Hi Mark. Which drivers? I have literally tried to use 5 or 6 different ways of installing drivers: device manager/Nexus Root Toolkit/the full Android SDK/KlicKit/adb setup 1.4.3 and maybe two others. Do you know a source that I am missing? Why would my phone out of all of the thousands sold NOT have proper drivers installed? This makes no sense. Weird thing is I can get to the bootloader screen using the adb reboot bootloader command.
wbexpress said:
Hi Mark. Which drivers? I have literally tried to use 5 or 6 different ways of installing drivers: device manager/Nexus Root Toolkit/the full Android SDK/KlicKit/adb setup 1.4.3 and maybe two others. Do you know a source that I am missing? Why would my phone out of all of the thousands sold NOT have proper drivers installed? This makes no sense. Weird thing is I can get to the bootloader screen using the adb reboot bootloader command.
Click to expand...
Click to collapse
Can I ask what commands your running when you're rebooted into boot loader/fastboot?
I'd say to try the LG drivers first and if not go with the Samsung ones. They're relatively universal.
Im also having problems. Ive installed every driver from samsung lg google and universal drivers and still nothing. I can get adb to reconize the device and reboot my device. I type in fastboot oem unlock and it stays on waiting on device
markbencze said:
Can I ask what commands your running when you're rebooted into boot loader/fastboot?
I'd say to try the LG drivers first and if not go with the Samsung ones. They're relatively universal.
Click to expand...
Click to collapse
Sure. Usually I am able to get into the bootloader(if adb devices recognized what's going on) where I get the LG logo and the words on the top left say "Welcome to Fastboot Mode". I put in adb reboot bootloader, which does get me there. Then, I put in fastboot oem unlock and that's when it hangs on waiting for device.
dillonorden said:
Im also having problems. Ive installed every driver from samsung lg google and universal drivers and still nothing. I can get adb to reconize the device and reboot my device. I type in fastboot oem unlock and it stays on waiting on device
Click to expand...
Click to collapse
Exactly. I guess the "misery loves company" thing is operative here. If you do figure it out, PM me, I will do the same.
what does it say when you type "fastboot devices"?
I am 100% certain you have either a driver issue which you should look into in your device/driver manager on your pc. there's likely something broken (common problem). Or you do not have usb debugging/enable oem unlock checked. I'm leaning towards a driver issue. It is also possible that if what you say is true and have installed too many drivers that something is conflicting.
markbencze said:
what does it say when you type "fastboot devices"?
I am 100% certain you have either a driver issue which you should look into in your device/driver manager on your pc. there's likely something broken (common problem). Or you do not have usb debugging/enable oem unlock checked. I'm leaning towards a driver issue. It is also possible that if what you say is true and have installed too many drivers that something is conflicting.
Click to expand...
Click to collapse
Progress!!! I was able to use Tech Know to unlock the bootloader. Now, if I can get the phone to behave enough to install twrp and root I will be good. But, KlicKit is not doing it, still hanging. And, when I type fastboot devices it just opens up another prompt and sits.
Edit: And, I am able to use fastboot reboot to reboot from the bootloader, but I get an error message when I try KlicKit, but it goes away too quickly to read what it says. OK, so now that I have an unlocked bootloader, do you have a recommendation of what method to use to install twrp and to root. (I have renamed the twrp file to "twrp.img" and I have both SU 2.46 and 2.52 on my external sd).
wbexpress said:
Progress!!! I was able to use Tech Know to unlock the bootloader. Now, if I can get the phone to behave enough to install twrp and root I will be good. But, KlicKit is not doing it, still hanging. And, when I type fastboot devices it just opens up another prompt and sits.
Edit: And, I am able to use fastboot reboot to reboot from the bootloader, but I get an error message when I try KlicKit, but it goes away too quickly to read what it says. OK, so now that I have an unlocked bootloader, do you have a recommendation of what method to use to install twrp and to root. (I have renamed the twrp file to "twrp.img" and I have both SU 2.46 and 2.52 on my external sd).
Click to expand...
Click to collapse
Just follow the instructions in the "how to root..." thread. it goes step by step and I believe there is a video tutorial as well. You'll need to do a quick search for this.
wbexpress said:
Ok, this is getting very frustrating. I've been rooting phones since the day the G1 came out, and having gotten a v10 yesterday and tried to root it, all of a sudden I have become stupid. I have tried every type of method om this board to attempt unlocking the bootloader, rooting, and installing TWRP. I've even tried the Nexus Root Toolkit and the I-Root/V-Root methods, both on the phone and from the PC. Even though I "sometimes" am able to type "adb devices" and actually get the device #, many times, both when trying to get into bootloader mode or as with both KlicKit and NRT, it more often than not hangs at "waiting for device". Is there anybody that has had a similar type of difficulty that has figured out how to make this happen? I took it out of the box and started to do my thing, so I am assuming it has a locked bootloader? This should not be so difficult to accomplish. Any insights would be appreciated.
Click to expand...
Click to collapse
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
duecebravo said:
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
Click to expand...
Click to collapse
Hi Duece, thanks for that. I am ok up to where I actually try to root, meaning, I am fine with getting into the bootloader. When I type "fastboot devices" it does give me the model # and the word fastboot next to it. The bootloader is now definitely unlocked. It's the next steps (twrp/root) that I get stuck. When I use KlicKit, it does do something for a second and then it just closes. Have you successfully installed twrp and rooted? That's where I'm jammed up. Thanks...
Edit: although I have the twrp.img file on my ext sd, and I renamed it "twrp.img" and typed that command in when in the bootloader, but it says "error: cannot open twrp.img".
wbexpress said:
Hi Duece, thanks for that. I am ok up to where I actually try to root, meaning, I am fine with getting into the bootloader. When I type "fastboot devices" it does give me the model # and the word fastboot next to it. The bootloader is now definitely unlocked. It's the next steps (twrp/root) that I get stuck. When I use KlicKit, it does do something for a second and then it just closes. Have you successfully installed twrp and rooted? That's where I'm jammed up. Thanks...
Edit: although I have the twrp.img file on my ext sd, and I renamed it "twrp.img" and typed that command in when in the bootloader, but it says "error: cannot open twrp.img".
Click to expand...
Click to collapse
put the twrp.img in the same folder with fastboot, flash recovery by using
Code:
fastboot flash recovery twrp.img
After twrp flash ,shutdown/ restart to factory rest mode and go for 2x "yes". if entering TWRP fine, then flash a supersu 4.52 zip from sd
I am using 2.8.x twrp working fine
jkyoho said:
put the twrp.img in the same folder with fastboot, flash recovery by using
Code:
fastboot flash recovery twrp.img
After twrp flash ,shutdown/ restart to factory rest mode and go for 2x "yes". if entering TWRP fine, then flash a supersu 4.52 zip from sd
I am using 2.8.x twrp working fine
Click to expand...
Click to collapse
Aah, that would make sense. However, I did a search in Root Explorer and nothing came back with "fastboot". Do you know where the most likely place would be?
wbexpress said:
Aah, that would make sense. However, I did a search in Root Explorer and nothing came back with "fastboot". Do you know where the most likely place would be?
Click to expand...
Click to collapse
So which step did you go through?
Do you have your twrp recovery working now?
fastboot is a platform tool from google. You should have it downloaded to computer(Win) and use it with CMD(command prompt)
https://www.youtube.com/watch?v=PPLwFGxLQA4
This is a good sample of how ppl unlcok BL and root v10
duecebravo said:
I literally figured this out 2 hours ago. It is a Driver issue but reinstalling a .exe will not work. This is what you have to do!(did this on Windows 7)
Boot up fastboot and plug into your pc.
Go into "device manager"
While in fastBoot your phone should be listed in "other devices" simply titled "Android".
You have to re select the Driver your self , do not choose for it to automatically search.
Look under the "Android devices" tab and if you have the LG drivers you should see something like "LG adb interface blah blah"
Choose that driver and fastBoot should work.
Try "fastBoot devices" in cmd it should finally recognize.
I've also heard success from selecting any "adb interface" driver
I think I'm gonna make my own thread and YouTube video to break this down further. I've also been and adroid user since the g1 and. I hate being asked "are you sure u ticked usb debugging?"
Click to expand...
Click to collapse
Lorddyyy ive been trying this crap all day i have the same driver issue but it won't let me select the one i want it just says there are no drivers available in this folder! GRRRRR
---------- Post added at 08:37 PM ---------- Previous post was at 08:00 PM ----------
omg i think i got it! http://forum.xda-developers.com/lg-v10/help/phone-adb-fastboot-t3247732 went here and did what duece said above but choose choose from a list!> then i hit select all devices> the box said populating but i just clicked install from disk and changed it to the unzipped file folder that had the driver in it until i found this file android_winusb and selected it!> then low abd behold the box populated with the driver info and it became a samsung adb device! finalllyyyyyy!!!!!!!!!!! i'm so happy Ive been trying to root this damn thing all day!
jkyoho said:
So which step did you go through?
Do you have your twrp recovery working now?
fastboot is a platform tool from google. You should have it downloaded to computer(Win) and use it with CMD(command prompt)
https://www.youtube.com/watch?v=PPLwFGxLQA4
This is a good sample of how ppl unlcok BL and root v10
Click to expand...
Click to collapse
No good. typed adb reboot bootloader, it went right there. Then typed fastboot flash recovery twrp-2.8.7.1-h901.img, it gives an error message: cannot flash twrp-2.8.7.1-h901.img. Typed fastboot reboot, went right back. The video's great, but if the commands don't take, it 's moot. If anybody figured this out (same issue), please let me know how. This is taking forever.
wbexpress said:
No good. typed adb reboot bootloader, it went right there. Then typed fastboot flash recovery twrp-2.8.7.1-h901.img, it gives an error message: cannot flash twrp-2.8.7.1-h901.img. Typed fastboot reboot, went right back. The video's great, but if the commands don't take, it 's moot. If anybody figured this out (same issue), please let me know how. This is taking forever.
Click to expand...
Click to collapse
are you sure your bootloader unlocked? and the code you typing match the recovery file name?
jkyoho said:
are you sure your bootloader unlocked? and the code you typing match the recovery file name?
Click to expand...
Click to collapse
Positive. The code I am putting in is twrp-2.8.7.1-h901.img. That's what most things I've read say to do. The other thing I have been thinking about is that KlicKit is supposed to have everything pre-loaded, and even it won't do it. KlicKit gets me into fastboot, then something really quick happens and the command prompt screen closes. What driver system do you use? I've installed a number of them, then deleted them as well, just to try to make sure there are no conflicts. However, I now have two devices in device manager: "android device.lge mobile adb interface" and "portable devices/v10. Does one need to go, maybe?
Power off your phone , hold volumn down and connect usb to PC.
Do you see "LOCK STATE - UNLOCKED" ?
if yes, type "fastboot.exe flash recovery twrp-2.8.7.1-h901.img "
I need to find a way to root my lg-h901 asap. The ways i found doesnt seem to work. When i do the adb command to unlock my bootloader it says waiting on devices and never continues on and i need root so i can use a call recording app due to legal issues. Any suggestions or ideas will be greatly appreciated
dillonorden said:
I need to find a way to root my lg-h901 asap. The ways i found doesnt seem to work. When i do the adb command to unlock my bootloader it says waiting on devices and never continues on and i need root so i can use a call recording app due to legal issues. Any suggestions or ideas will be greatly appreciated
Click to expand...
Click to collapse
There are call recording apps on playstore. Along with the rooting is so simple I did it the same day I got my v10 T-Mobile variant
dillonorden said:
I need to find a way to root my lg-h901 asap. The ways i found doesnt seem to work. When i do the adb command to unlock my bootloader it says waiting on devices and never continues on and i need root so i can use a call recording app due to legal issues. Any suggestions or ideas will be greatly appreciated
Click to expand...
Click to collapse
First things first, you don't need root to record your phone calls. Like Wadamean said, there are call recording apps in the play store. I personally use "Call Recorder ACR", but you can use whatever you prefer. Most call recorders won't require root access.
As for rooting, if you type the adb command and it says that it's waiting for your device, the most likely cause is that you do not have the proper drivers installed on your computer. An easy way to check this would be to type the command "adb devices" and make sure that your V10 appears under "List of devices attached". If you don't see your h901 device listed, your computer doesn't know that the V10 is connected, and it'll be difficult for your computer to issue commands to a device it can't see
Follow each step in this guide. That doesn't mean click this link, skip to the downloads, and then proceed to root like you've always done. It means click this link, READ THE POST, then once you have finished reading it, read it again to make sure you didn't miss anything. It will guide you through setting up adb with a universal driver. It will also guide you through doing things like enabling USB Debugging, which is required for issuing adb commands.
http://forum.xda-developers.com/tmobile-lg-v10/general/guide-how-to-root-lg-v10-easy-t3274699
If you are still having issues after reading this guide and FOLLOWING THE INSTRUCTIONS, post there to let them know where you're getting stuck at and someone will help you out.
Appreciate the advice i thought call recording was a root only feature so i do apologize for that inconvience guys
As far as rooting my computer does reconize the device ive ran the adb command to check and it did list it and i still got stuck. Ive installed the universal drivers so that may be where i messed up. Thank you for the link im going to try again tonight bc i want root
dillonorden said:
Appreciate the advice i thought call recording was a root only feature so i do apologize for that inconvience guys
As far as rooting my computer does reconize the device ive ran the adb command to check and it did list it and i still got stuck. Ive installed the universal drivers so that may be where i messed up. Thank you for the link im going to try again tonight bc i want root
Click to expand...
Click to collapse
No worries, that's why we're here :good:
If you can see your V10 listed on the ADB devices list, then something else is up. Make sure that USB Debugging and OEM Unlock are checked in Developer Options... What command are you getting stuck at?
Both options are checked in developers options. Ill type the oem unlock command and it reads waiting on device
dillonorden said:
Both options are checked in developers options. Ill type the oem unlock command and it reads waiting on device
Click to expand...
Click to collapse
Ahh, sounds like you aren't in fastboot mode. Make sure that your USB connection type is set to PTP rather than MTP or charge only. Before you issue ANY other adb commands, run "adb devices" and make sure that you see your v10. It should read something like this:
List of devices attached
LGH901blahblah device
Click to expand...
Click to collapse
See it on the list? Good. You should be able to run "adb reboot bootloader". At this stage, your phone should reboot to a mostly dark screen. Once in the bootloader, you should be able to run "fastboot oem unlock". Be forewarned that it can take a few minutes. If you see "waiting on device," you're either not in the right mode (your phone won't acknowledge fastboot commands if it's not in Bootloader mode) or the drivers on your computer are screwy and need to be reinstalled. If you can issue adb commands but not fastboot ones, you probably need additional drivers - more info here: http://android.stackexchange.com/questions/46142/fastboot-doesnt-see-device
This should get you started in the right direction, feel free to PM or post in the guide if you're still having trouble. :good:
ok so i followed the guide, reinstalled the LG drivers. and re setup the ADB system wide. I put my phone in usb ptp and ran command ADB devices. It listed my device, so i ran the ADB reboot bootloader and it rebooted. the screen i get is the LG boot screen but in the top left corner it shows fastboot mode and list the commands to unlock the bootloader. I run command fastboot oem unlock and I get the same waiting on device and waited an hour and got nothing. I even tried unplugging it restarting command prompt held the vol down button when i plugged my device back in to make it boot into FASTBOOT mode. i run the command fastboot oem unlock and still get nothing.
What am I doing wrong? I follow the guide to the very T and still get nothing. Could I possibly get someone to make a file with everything done and flash it using Odin? Im not new to this and dont understand why this V10 H901 is giving me so much trouble. Ive rooted a Motorola OG droid, Droid 2, Bionic, Samsung Note 2, 3 and Grand Prime and never had this much trouble. I really enjoy having root privileges but this is getting ridiculous but I also refuse to give up. If anyone can help me I would much appreciate it. Also Thanks to the ones who have tried helping me so far, this is why I enjoy XDA so much
ok i believe my device isnt being reconized while in fastboot mode. I tried going into fastboot mode by plugging my device in a PC while it was off and holding the Vol Down button and when I go into command prompt and run command fastboot devices nothing shows up. I really need to root this device so any help is appreciated
ok confirmed at 0130 hrs I am loosing connection in fastboot mode... What is the issue?
dillonorden said:
ok i believe my device isnt being reconized while in fastboot mode. I tried going into fastboot mode by plugging my device in a PC while it was off and holding the Vol Down button and when I go into command prompt and run command fastboot devices nothing shows up. I really need to root this device so any help is appreciated
ok confirmed at 0130 hrs I am loosing connection in fastboot mode... What is the issue?
Click to expand...
Click to collapse
Are you the administrator of the pc? What OS are you using?
I am administrator and im using windows 7 so i dont see where im having an issue at
I bricked my opx I was able to bring it to life but the ****ty recovery doesn't let me flash anything so I am stuck no OS and boot loader locked and my computer isn't recognizing the dam thing I have installed SDK tools and google USB drivers but for some reason I am not able to get the Dan thing to connect right when I try via adb sideload it starts then the phone says fail...... Please help I am love this device and brand but I am getting really mad I am about a week in to trying to fix this but no luck I am using windows 10 also
Sorry to say, but you gotta follow this thread.
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus X
Since you may ignore the other thread you started or it may get deleted I'll copypasta here:
We can try to unlock the bootloader as it is now, but that doesn't usually work unless you checked "OEM Bootloader Unlock" in the system settings before the device was bricked. Hindsight is 20/20 but as a word of advice for the future, never ever mess with a device unless you know the bootloader is unlocked or have made it possible to unlock it later without the OS. It also doesn't void the warranty on OnePlus devices to do so.
So first things first, the recovery will normally only flash the stock ROM as provided by OnePlus. You can download that file from here: http://downloads.oneplus.net/2016-04...xygenOS_2.2.1/. For future reference, when the bootloader on a device is locked the bootloader will not boot any software that isn't complete stock. If you try and change the OS or Recovery and it's not stock, the bootloader will not load it. This goes for any Android device.
If ADB sideload is working for you but hasn't been installing on the device (as-in, it sends the file but the device fails to install it) then you should be able to just sideload the zip file. It'll be slow though since it's about 780megs. If it doesn't send it then you can try using the ADB "push" command which is like copy and paste. You "push" the file from your computer to a folder on the device (you can see what folders are available using "adb shell" and then navigating with CD "change directory" and LS "list". If you can't find the sdcard you may have to mount it). Once again, it'll push slowly but once it does you should be able to install it from the internal memory.
If that works and it boots, go to Settings -> About Phone and tap the Build Number until it says you've enabled developer settings. Go to Settings -> Development and turn on "OEM Unlocking". Power the phone down. Hold the Power key and Volume Down until it shows the OnePlus logo and "Fastboot". I believe if you have the Android SDK you have the Fastboot program (it's commandline like ADB). Open CMD or Powershell and as long as it's the only device plugged into the computer you should be able to simply type "Fastboot oem unlock" and it will unlock the bootloader. Once again, it doesn't void your warranty.
I bricked my opx I was able to bring it to life but the ****ty recovery doesn't let me flash anything so I am stuck no OS and boot loader locked and my computer isn't recognizing the dam thing I have installed SDK tools and google USB drivers but for some reason I am not able to get the Dan thing to connect right when I try via adb sideload it starts then the phone says fail...... Please help I am love this device and brand but I am getting really mad I am about a week in to trying to fix this but no luck I am using windows 10 also
We can try to unlock the bootloader as it is now, but that doesn't usually work unless you checked "OEM Bootloader Unlock" in the system settings before the device was bricked. Hindsight is 20/20 but as a word of advice for the future, never ever mess with a device unless you know the bootloader is unlocked or have made it possible to unlock it later without the OS. It also doesn't void the warranty on OnePlus devices to do so.
So first things first, the recovery will normally only flash the stock ROM as provided by OnePlus. You can download that file from here: http://downloads.oneplus.net/2016-04-02/opx/OnePlus_X_OxygenOS_2.2.1/. For future reference, when the bootloader on a device is locked the bootloader will not boot any software that isn't complete stock. If you try and change the OS or Recovery and it's not stock, the bootloader will not load it. This goes for any Android device.
If ADB sideload is working for you but hasn't been installing on the device (as-in, it sends the file but the device fails to install it) then you should be able to just sideload the zip file. It'll be slow though since it's about 780megs. If it doesn't send it then you can try using the ADB "push" command which is like copy and paste. You "push" the file from your computer to a folder on the device (you can see what folders are available using "adb shell" and then navigating with CD "change directory" and LS "list". If you can't find the sdcard you may have to mount it). Once again, it'll push slowly but once it does you should be able to install it from the internal memory.
If that works and it boots, go to Settings -> About Phone and tap the Build Number until it says you've enabled developer settings. Go to Settings -> Development and turn on "OEM Unlocking". Power the phone down. Hold the Power key and Volume Down until it shows the OnePlus logo and "Fastboot". I believe if you have the Android SDK you have the Fastboot program (it's commandline like ADB). Open CMD or Powershell and as long as it's the only device plugged into the computer you should be able to simply type "Fastboot oem unlock" and it will unlock the bootloader. Once again, it doesn't void your warranty.
Hello,
I have a Straight Talk ZTE Majesty Pro LTE [Z799VL]. It runs Android 6.0.1. This phone occasionally installs apps and has an annoying app called AppFinder. I have tried to root this phone with KingoRoot and KingRoot. So, I need help figuring out if this thing is even rootable. I would get a more accessible phone, but I'm short on money. I know this is short on information, but I'd be willing to help in any way I can.
Any help would be greatly appreciated.
Boop.
I'm fairly certain this phone was released recently. Maybe it's just too soon.
I have this same phone and am having the same problem finding info on how to root it. Keeping a hopeful eye on this thread
Any news for ZTE Majesty PRO unlock?
My friend just brought it from USA to Europe and he want to use it in normal way
Any news?
Any news?
Zte z799vl -
I have this phone and have tried many types to root it with no luck.
same here looking for root
Root
I've tried SRS King Kingo 360root etc... And many others and nothin so far. Any luck from anyone else?? Even temp root??
ZTE majesty pro z799vl tracfone
The OP is running Android 6 but I have the Straight Talk boxed ZTE Majesty Pro and it runs 7.1.1 out of the box.
There is a thread called Universal Method with a file and instructions but my Android device is the only PC I own so I haven't given it a try. The post has a Windows and a Linux method.
ChernobylBloodwolf said:
Hello,
I have a Straight Talk ZTE Majesty Pro LTE [Z799VL]. It runs Android 6.0.1. This phone occasionally installs apps and has an annoying app called AppFinder. I have tried to root this phone with KingoRoot and KingRoot. So, I need help figuring out if this thing is even rootable. I would get a more accessible phone, but I'm short on money. I know this is short on information, but I'd be willing to help in any way I can.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you unlocked the bootloader?
I recently upgraded to an Android 7.1.1 ZTE Majesty™ Pro Plus LTE (Z899VL) from TracFone,, and was rather dismayed to find out that it has an unremovable Facebook app (among other rubbish that I don't want/don't use).
I've never rooted a device before, and I know that this thread's a little old, but would anyone be willing to post a very-newbie-friendly step-by-step tutorial/walkthrough for rooting this phone (assuming it's possible)?
I have Developer Options enabled, and I can easily unlock the bootloader if that's required. I just want to get rid of these useless (for me) System Apps.
Oh, also: I don't have Linux, so… if it's possible, perhaps the rooting method could work using a Windows 7 PC?
need fastboot to unlock the bootloader. to the best of my knowledge, which aint much. but i can not find access to any kind of dl mode let alone fastboot.
Kizul said:
I recently upgraded to an Android 7.1.1 ZTE Majesty™ Pro Plus LTE (Z799VL) from TracFone,, and was rather dismayed to find out that it has an unremovable Facebook app (among other rubbish that I don't want/don't use).
I've never rooted a device before, and I know that this thread's a little old, but would anyone be willing to post a very-newbie-friendly step-by-step tutorial/walkthrough for rooting this phone (assuming it's possible)?
I have Developer Options enabled, and I can easily unlock the bootloader if that's required. I just want to get rid of these useless (for me) System Apps.
Oh, also: I don't have Linux, so… if it's possible, perhaps the rooting method could work using a Windows 7 PC?
Click to expand...
Click to collapse
UNLOCKING BOOTLOADER:
Download Koush Universal adb driver from koushikdutta.com and adb setup.
Install the driver first and install adb after that.
Type n and press Enter when adb setup asks for installing drivers.
After the installation, run command prompt as administrator.
Open File explorer, and navigate to C:\adb
Please take backup of your data before proceeding further.
In C:\adb press Shift+right click and select Open Command Window here.
Enable USB debugging on your phone and connect your phone to pc using USB cable.
Type "adb devices" without quotation marks and press enter.
If it shows some device to be connected, only then proceed further.
Type "adb reboot bootloader" and press enter.
Phone will boot into fastboot mode.
Type "fastboot devices" and press enter.
If it shows some device to be connected, only then proceed further.
Type "fastboot oem unlock" and press enter.
On the phone screen, the phone will ask for confirmation to unlock bootloader.
Once fastboot shows "Success" or "Done" or something else signifying that the command was successful, type "fastboot reboot" and press enter.
Your phone will reboot normally.
Congrats, you have successfully unlocked bootloader.
ROOTING:
1. For Kingoroot:
Download and install Kingoroot for PC.
Enable USB debugging on your phone and connect your phone to PC using USB cable.
Open Kingoroot.
Connect your pc to internet.
Kingoroot will detect your phone automatically and in a few seconds the root button will come up, click it and wait until the process completes.
Your phone may reboot several times during the process.
Congrats, you have a rooted phone now.
2. For Dr Fone:
Download and install Dr Fone on your PC.
Enable USB debugging on your phone.
Open Dr Fone and select Root option.
Connect your phone to your PC with USB cable.
Dr Fone will detect your phone in a few minutes.
Click "Root" button and wait.
Congrats, you have a rooted phone now.
Augustoandro said:
UNLOCKING BOOTLOADER:
Download Koush Universal adb driver from koushikdutta.com and adb setup.
Install the driver first and install adb after that.
Type n and press Enter when adb setup asks for installing drivers.
After the installation, run command prompt as administrator.
Open File explorer, and navigate to C:\adb
Please take backup of your data before proceeding further.
In C:\adb press Shift+right click and select Open Command Window here.
Enable USB debugging on your phone and connect your phone to pc using USB cable.
Type "adb devices" without quotation marks and press enter.
If it shows some device to be connected, only then proceed further.
Type "adb reboot bootloader" and press enter.
Phone will boot into fastboot mode.
Type "fastboot devices" and press enter.
If it shows some device to be connected, only then proceed further.
Type "fastboot oem unlock" and press enter.
On the phone screen, the phone will ask for confirmation to unlock bootloader.
Once fastboot shows "Success" or "Done" or something else signifying that the command was successful, type "fastboot reboot" and press enter.
Your phone will reboot normally.
Congrats, you have successfully unlocked bootloader.
Click to expand...
Click to collapse
Well, I finally managed to get my 899VL (it's not a 799VL as I'd thought — sorry) to show up as an ADB device; it accepts commands from the ADB program… except that when I execute "adb reboot bootloader", it just reboots my phone.
The ZTE logo shows, then the TracFone logo, and then Android boots as normal. It's as though I simply used the "Restart" option on my phone itself.
Due to this, I can't use "fastboot" commands, because it doesn't seem to enter Fastboot at all.
I do have both the OEM unlocking and USB debugging options turned ON. My only guess as to what's going wrong is that it's TracFone's fault. (Alas, I have no proof…)
Is there anything else that I can do to try and unlock the bootloader? Or is this phone a lost cause?
Kizul said:
Well, I finally managed to get my 899VL (it's not a 799VL as I'd thought — sorry) to show up as an ADB device; it accepts commands from the ADB program… except that when I execute "adb reboot bootloader", it just reboots my phone.
The ZTE logo shows, then the TracFone logo, and then Android boots as normal. It's as though I simply used the "Restart" option on my phone itself.
Due to this, I can't use "fastboot" commands, because it doesn't seem to enter Fastboot at all.
I do have both the OEM unlocking and USB debugging options turned ON. My only guess as to what's going wrong is that it's TracFone's fault. (Alas, I have no proof…)
Is there anything else that I can do to try and unlock the bootloader? Or is this phone a lost cause?
Click to expand...
Click to collapse
Well, I don't know about any other method to unlock boot loader.
BTW, in case of some phones, turning on the "OEM Unlock" button in Developer Options unlocks the bootloader automatically, so maybe, just check whether your bootloader is locked or not.
Both Didn't work
Augustoandro said:
UNLOCKING BOOTLOADER:
Download Koush Universal adb driver from koushikdutta.com and adb setup.
Install the driver first and install adb after that.
Type n and press Enter when adb setup asks for installing drivers.
After the installation, run command prompt as administrator.
Open File explorer, and navigate to C:\adb
Please take backup of your data before proceeding further.
In C:\adb press Shift+right click and select Open Command Window here.
Enable USB debugging on your phone and connect your phone to pc using USB cable.
Type "adb devices" without quotation marks and press enter.
If it shows some device to be connected, only then proceed further.
Type "adb reboot bootloader" and press enter.
Phone will boot into fastboot mode.
Type "fastboot devices" and press enter.
If it shows some device to be connected, only then proceed further.
Type "fastboot oem unlock" and press enter.
On the phone screen, the phone will ask for confirmation to unlock bootloader.
Once fastboot shows "Success" or "Done" or something else signifying that the command was successful, type "fastboot reboot" and press enter.
Your phone will reboot normally.
Congrats, you have successfully unlocked bootloader.
ROOTING:
1. For Kingoroot:
Download and install Kingoroot for PC.
Enable USB debugging on your phone and connect your phone to PC using USB cable.
Open Kingoroot.
Connect your pc to internet.
Kingoroot will detect your phone automatically and in a few seconds the root button will come up, click it and wait until the process completes.
Your phone may reboot several times during the process.
Congrats, you have a rooted phone now.
2. For Dr Fone:
Download and install Dr Fone on your PC.
Enable USB debugging on your phone.
Open Dr Fone and select Root option.
Connect your phone to your PC with USB cable.
Dr Fone will detect your phone in a few minutes.
Click "Root" button and wait.
Congrats, you have a rooted phone now.
Click to expand...
Click to collapse
I tried using both the wasy for the first one the device not going to fastboot mode it just restarts for "adb reboot bootloader".
i tried KingoRoot, Dr Fone but it didn't work.
Did you unlock the ZTE Majesty Pro Z799VL with this method???
drona91 said:
I tried using both the wasy for the first one the device not going to fastboot mode it just restarts for "adb reboot bootloader".
i tried KingoRoot, Dr Fone but it didn't work.
Did you unlock the ZTE Majesty Pro Z799VL with this method???
Click to expand...
Click to collapse
No, these are general instructions which work for most phones.
Z799vl Help USB tethering