Hi good people of the internet,
I recently brough a brand new ZTE Blade Vec 4G and i wanted to replace the Android OS that came with the device before i start using it, but i hit a snag when trying to run the shell commands via USB.
I have been trying via my Ubuntu machine, but i also tried allitle in Windows, but i got the same result there.
So far ive been following this list (could not post the links, but its via the main "Installing Ubuntu for Devices" page:
Unlock the Android device
To install Ubuntu, you must first “unlock” the Android device bootloader.
Warning: Unlocking deletes all data from the device, including apps and other data. You may want to create a backup first.
You must first have enabled USB Debugging in the Android OS.
Boot the device into the Android bootloader:
$ adb reboot bootloader
Tip: When the device is booted into the bootloader the screen displays the green Android robot lying on its back with its front panel open and a highlighted Start menu item.
Verify the device is connected to your Ubuntu Desktop as follows:
$ fastboot devices
025d138e2f521413 fastboot
Unlock the device as follows:
$ sudo fastboot oem unlock
Accept the terms of unlocking displayed on the Android device.
Reboot the device to Android as follows:
$ fastboot reboot
Complete the first use Android setup steps, entering minimal information: Android and its data is about to be deleted during the Ubuntu install.
Click to expand...
Click to collapse
Ive only made it to highlighted point, but when i hit "sudo fastboot oem unlock" it just stops on < waiting for device >, and when i try to find the device i cant see it when in "Android system recovery mode".
Any help would be great as ive spent near 5 hours trying to do this now
I don't think it's possible to unlock the bootloader on your device yet. From what I've read, even the adb reboot bootloader method does not actually get you into fastboot mode. Replacing the OS with Ubuntu will not be an option because of this as well as other reasons.
es0tericcha0s said:
I don't think it's possible to unlock the bootloader on your device yet. From what I've read, even the adb reboot bootloader method does not actually get you into fastboot mode. Replacing the OS with Ubuntu will not be an option because of this as well as other reasons.
Click to expand...
Click to collapse
Thank you for the reply. So how can i remove Android at all then? would it be better to try something like CyanogenMod or MIUI? I have also been looking at Firefox OS, but if i cant remove Android, then i cant really do much at all..
Just saw this thread:
http://forum.xda-developers.com/general/help/soshphone-4g-zte-blade-vec-root-t2810210/page1
Guess i just need to make do with the unrooted Android for now..
Pretty much stuck for awhile. There might never be an option for it. Many phones never get the chance to have different OSes or even custom versions of Android. Hopefully that's not the case, but it's not uncommon.
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 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.
I've looked up guides but apparently it's really hard to root the Blu advance 5.0? MY Moto g died recently and I had Lineage OS custom rom. I've rooted moto g and that was super easy, but this looks really difficult to do and I'm afraid to brick my phone that I'm just about to get, and I really want to get more external memory because I think it has like no memory. I also really want to root my phone and I know unlocking the bootloader and installing the custom recovery (twrp) is the only way to do so. So can anyone help a guy out?
Advancedsoda said:
I've looked up guides but apparently it's really hard to root the Blu advance 5.0? MY Moto g died recently and I had Lineage OS custom rom. I've rooted moto g and that was super easy, but this looks really difficult to do and I'm afraid to brick my phone that I'm just about to get, and I really want to get more external memory because I think it has like no memory. I also really want to root my phone and I know unlocking the bootloader and installing the custom recovery (twrp) is the only way to do so. So can anyone help a guy out?
Click to expand...
Click to collapse
Backup ur data before proceeding further.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
U can now use Kingoroot or any other tool for rooting.
Hey all i dont know what the deal is but ive got an lg g5 that just will not boot to the bootloader. I've tried factory resetting it and all the methods to get to bootloader just reboots the phone fully. Adb reboot booloader, key combos, nothing seems to work. Any ideas??
First, connect your smartphone with your PC; plug in the USB cord in order to establish the connection.
On your computer access the Android SDK folder.
From there open a command prompt window: press and hold the Shift keyboard key while right clicking on any blank space.
Next, in the cmd window type “adb reboot bootloader” and wait while the bootloader mode is displayed on your smartphone
That's basically what I did and worked first time..make sure the adb and fastboot package is installed and open the command window from that folder
russy23 said:
First, connect your smartphone with your PC; plug in the USB cord in order to establish the connection.
On your computer access the Android SDK folder.
From there open a command prompt window: press and hold the Shift keyboard key while right clicking on any blank space.
Next, in the cmd window type “adb reboot bootloader” and wait while the bootloader mode is displayed on your smartphone
That's basically what I did and worked first time..make sure the adb and fastboot package is installed and open the command window from that folder
Click to expand...
Click to collapse
Did all that.. I mean I've flashed custom recoveries and roms to other phones before and never really had a problem i couldn't google..this has me stumped. It simply refuses to even access the bootloader.
If it helps it was a koodo phone and is running the latest official patch from lg on nougat. The only thing i could find online was that sprint supposedly removed all access to the bootloader on theirs, but i cant find any real info on that either. It reboots when i send the adb reboot bootloader but its like fastboot just isn't there..?? It reboots right back to the android home screen. Ive tried all possible key combos as well... Ugh
Which model is it..mines the h850
Ive got the h831
I think I've sort of answered my own question. From browsing the forums it appears the Canadian variant has the bootloader locked down and inaccessible, which would explain a lot..lol.. I really hate when this kind of thing is done to the consumer...ugh. Back to xiaomi i guess lol
bproulx said:
... has the bootloader locked down and inaccessible, which would explain a lot..lol.. I really hate when this kind of thing is done to the consumer...ugh. Back to xiaomi i guess lol
Click to expand...
Click to collapse
Interesting - my xianomi hat an locked bootloader and i had to ask for permission (for the phone I bought!) to unlock the bootloader.
LG is also locked, but the unlocking procedure is way easier.
logg.sar said:
Interesting - my xianomi hat an locked bootloader and i had to ask for permission (for the phone I bought!) to unlock the bootloader.
LG is also locked, but the unlocking procedure is way easier.
Click to expand...
Click to collapse
Unless you're from Canada apparently ..lol