Hi I am Rupesh from India and I have lenovo a3000H and I am using it from past three years and I am bored with it and so I have downloaded cm 5.1.1 from your site.
I have tried a lot to root the device at first I have installed framaroot and after that I have installed superuser app which gave error as their is no su binary installed.
In order to unlock the bootloader I have installed android studio and USB drivers provided by the device vendor. When I connect the tab to Windows 8.1 system I am able to see an entry named lenovo a3000 under portable devices in device manager.
When I issue the command adb devices on command prompt of my pc I am able to see a serial number followed by the word device. When I issue the command adb reboot bootloader instead of entering into fastboot mode my tab is restarting itself after that when I issue the command fastboot devices I am unable to see no output.
Previously I have tried to backup my tab storage from PC using adb and my tab asked for confirmation but no backup was performed.
I think that fastboot is unable to detect the device.
I am unable to root my tab with using PC or without using PC.
Please suggest how to root my tab properly.
Regards,
Rupesh.
Before performing the above I have enabled USB debugging and became developer by tapping 7 times build number in about phone.
Hi All,
Trying to do what should be simple - install TWRP , then omnirom.
Have a new le pro 3, running stock firmware.
have enabled usb debugging, enabled oem unlock.
I can see the le pro 3 in adb devices. I then reboot (adb reboot bootlader).
Phone goes into fastboot. But fastboot devices, or any other command cant see the phone in fastboot mode..
Appreciate any help.. I'm at a loss. Thanks!
Even if ADB show your empty list, when you're at bootloader you can flash TWRP... Look my thread about brick.
Do it with flashing guide... You should also unlock in bootloader mode. And check the status.
For anyone that cares - on a Macbook pro retaina (with windows 10 as VM) - I could only see phone in adb, not fastboot.
installed fastboot for OSX, and ditched the virtual machine, and voila.
So I've just received my axon 7 a2017g. It came with b06 installed. I'm trying to unlock boot loader without success. Can't get to edl mode. In cmd the device is unauthorized though I've enabled oem unlock and sub debugging. Installed the drivers from sub debugging. I have Windows 10 64 bit. I get to recovery with volume up plus power I select to reboot to bootloader with no success. It only restarts. Tried also with b10 and b08.
Any suggestions ?
ItsNewDroid said:
So I've just received my axon 7 a2017g. It came with b06 installed. I'm trying to unlock boot loader without success. Can't get to edl mode. In cmd the device is unauthorized though I've enabled oem unlock and sub debugging. Installed the drivers from sub debugging. I have Windows 10 64 bit. I get to recovery with volume up plus power I select to reboot to bootloader with no success. It only restarts. Tried also with b10 and b08.
Any suggestions ?
Click to expand...
Click to collapse
Why bootloader? Isn't there a way to do it via EDL (from system, do adb reboot edl)? On Controllerboy's guide maybe? Maybe you think that the device doesn't get to EDL because it seems like it's totally powered off. Just try again.
As of fastboot, it was removed on Nougat, not sure if they removed it before though
Choose an username... said:
Why bootloader? Isn't there a way to do it via EDL (from system, do adb reboot edl)? On Controllerboy's guide maybe? Maybe you think that the device doesn't get to EDL because it seems like it's totally powered off. Just try again.
As of fastboot, it was removed on Nougat, not sure if they removed it before though
Click to expand...
Click to collapse
Did not understand you. Where in system to do and reboot?
The phone is turned onand connected the the pc and I've enabled oem unlock and usb debugging.
The device won't boot to edl after I enter adb reboot edl. So I tried in recovery screen to get to the bootloader menu but pressing reboot loader it just restarts
ItsNewDroid said:
Did not understand you. Where in system to do and reboot?
The phone is turned onand connected the the pc and I've enabled oem unlock and usb debugging.
The device won't boot to edl after I enter adb reboot edl. So I tried in recovery screen to get to the bootloader menu but pressing reboot loader it just restarts
Click to expand...
Click to collapse
You have to have adb and fastboot installed. Run "adb reboot edl" from your computer while the phone is on, it should ask you if you want ADB to be allowed to do stuff, then poof. Go to the Device manager and check that there's a Qualcomm HS-USB QDLoader 9008 under Ports (COM&LPT)
Choose an username... said:
You have to have adb and fastboot installed. Run "adb reboot edl" from your computer while the phone is on, it should ask you if you want ADB to be allowed to do stuff, then poof. Go to the Device manager and check that there's a Qualcomm HS-USB QDLoader 9008 under Ports (COM&LPT)
Click to expand...
Click to collapse
Can you direct me where to get the adb and fastboot? I've rooted a lot of phones but this one seems unfriendly
ItsNewDroid said:
Can you direct me where to get the adb and fastboot? I've rooted a lot of phones but this one seems unfriendly
Click to expand...
Click to collapse
You rooted a lot of phones and don't have ADB lol
Search for 15 seconds adb installer
I already have it installed. It says unauthorized when I run adb devices
ItsNewDroid said:
I already have it installed. It says unauthorized when I run adb devices
Click to expand...
Click to collapse
Unplug the phone, turn it off. Hold only the 2 volume buttons (DON'T TOUCH POWER) and insert the USB-C (plugged to the PC in the other end ofc) while holding the two volume buttons. then check device manager
This should get you to EDL
---------- Post added at 12:44 AM ---------- Previous post was at 12:40 AM ----------
ItsNewDroid said:
I already have it installed. It says unauthorized when I run adb devices
Click to expand...
Click to collapse
Okay after you do that last thing you should get to EDL. Download Zadig, uninstall the Qualcomm QDLoader drivers and tick Delete driver software too. Then go to Zadig and install the driver. After that hold the 3 buttons (pwr, vol) until the led flashes or your PC makes a sound, wait 5 seconds, and you'll be able to run axon7tool.exe -r gpt boot recovery
In zadig's post he says they G models should edl only by the command. But I did as you said with the volume buttons. I run axon7tool in command But it says no device found
ItsNewDroid said:
In zadig's post he says they G models should edl only by the command. But I did as you said with the volume buttons. I run axon7tool in command But it says no device found
Click to expand...
Click to collapse
That's extremely weird...
Well I guess there's no harm trying to downgrade to marshmallow B03. Download that ancient ROM from raysteff's download center. I did the whole process there. Maybe you'll get fastboot too
---------- Post added at 01:13 AM ---------- Previous post was at 01:10 AM ----------
ItsNewDroid said:
In zadig's post he says they G models should edl only by the command. But I did as you said with the volume buttons. I run axon7tool in command But it says no device found
Click to expand...
Click to collapse
Thinking about it it's not that weird, I think you're not getting the Zadig part. Did you install the driver through Zadig? How's the device reported aa when on EDL? If you installed the driver properly it should be listed as QUSB_BULK under USB something
Sure I'm not doing something right.
First I did not have Qualcomm drivers installed
I'm in edl with volume buttons and sub. open zadig and install wcid.
From here I did not get it. Hold all buttons vol÷power?
ItsNewDroid said:
I already have it installed. It says unauthorized when I run adb devices
Click to expand...
Click to collapse
Like this ?
"adb devices" command:
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
xxxxx unauthorized
When enabling USB debugging then with USB cable connected, there is a popup in your phone, asking to authorize
your phone (with digital signature etc..). You need then to authorize it. Afterwards, your phone will be recognized
with 'adb devices" output as :
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
xxxxx device
xxxxx is your device id. You must have status "device" and not "unauthorized"
dnlilas said:
Like this ?
"adb devices" command:
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
xxxxx unauthorized
When enabling USB debugging then with USB cable connected, there is a popup in your phone, asking to authorize
your phone (with digital signature etc..). You need then to authorize it. Afterwards, your phone will be recognized
with 'adb devices" output as :
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
xxxxx device
xxxxx is your device id. You must have status "device" and not "unauthorized"
Click to expand...
Click to collapse
Yes I know that a message should popup but it doesn't. What can I do?
I have oconnection options like charging, mpt etc.
Should I choose something perticular?
And why it doesn't reboot to bootloader from recovery menu?
I really think something is wrong with the device.
Where can I find a2017g b03? In every post the link to zte's website that only have b11 and nougat.
Sorry for all the questions as I said this device gives me a hard time.
I've had opo op3 lg g5 le max 2. Non of theme gave me hard time like this one
ItsNewDroid said:
Yes I know that a message should popup but it doesn't. What can I do?
I have oconnection options like charging, mpt etc.
Should I choose something perticular?
And why it doesn't reboot to bootloader from recovery menu?
I really think something is wrong with the device.
Where can I find a2017g b03? In every post the link to zte's website that only have b11 and nougat.
Sorry for all the questions as I said this device gives me a hard time.
I've had opo op3 lg g5 le max 2. Non of theme gave me hard time like this one
Click to expand...
Click to collapse
Please check periodically USB debugging option. I encountered similar problem as your, and before the popup that confirms USB debugging
for the phone, the option is set back to disabled. So maybe you have to check again this option, unplug and replug the phone, choose option MTP,
this should help to have the confirmation popup. Anyhow you must have to reach status "device" which means your phone is able to connect using ADB.
For A2017G B03, it is not necessary, B11 is OK for unlock, TWRP or root using the current guide.
However if you really need it (A2017G B03, B06, B09):
https://forum.xda-developers.com/showpost.php?p=68873485&postcount=3
I suspect that my laptop is causing me trouble as also my g5 will not prompt me with authorization.
I'm gonna use a different laptop without any drivers installed. Can someone tell me all the drivers needed for the a2017g in chronological order so there won't be any conflicts?
In other tutorials they don't mention Qualcomm's driver but in othrrs they are needed.
This phone makes me so frustrated.
So please a step by step from new how to connect to adb on a total new pc. From there I hope I'll manage.
Thanks to all who replied. It's much appreciated.
Here the same problem with an A2017G model. Phone worked with the latest LineageOS, was rooted and got an unlocked bootloader, and with flashing to the the new B04 update phones ends up in a loop.
I can get into the stock recovery and when i choose "reboot system now" i get a screen wich tells you to lock your bootloader.
In recovery a can also choose "apply update from adb" or "apply update from sd card". With the first option i can flash a rom but at 25-30% adb ends up with an error.
With the second option i get a message "Sorry, can`t sdcard upgrade", and tryed several sd cards.
Phone will NOT boot into Android so i can`t change USB debgugging or something.
I can get in EDL mode and after "axon7tool -r gpt boot recovery" in adb the phone reboots with no errors and gets in a loop again. Grrrrr..... Very frustrating with a non working phone!
the_cyberspace said:
Here the same problem with an A2017G model. Phone worked with the latest LineageOS, was rooted and got an unlocked bootloader, and with flashing to the the new B04 update phones ends up in a loop.
I can get into the stock recovery and when i choose "reboot system now" i get a screen wich tells you to lock your bootloader.
In recovery a can also choose "apply update from adb" or "apply update from sd card". With the first option i can flash a rom but at 25-30% adb ends up with an error.
With the second option i get a message "Sorry, can`t sdcard upgrade", and tryed several sd cards.
Phone will NOT boot into Android so i can`t change USB debgugging or something.
I can get in EDL mode and after "axon7tool -r gpt boot recovery" in adb the phone reboots with no errors and gets in a loop again. Grrrrr..... Very frustrating with a non working phone!
Click to expand...
Click to collapse
The command "axon7tool -r gpt boot recovery" only backups your boot and recovery (-r = read, so of course only files *-backup.bin are created inside your PC directory, no change to the phone).
Since you have stock recovery, did you apply the full ROM A2017G-N-B04 (australian) from here:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547 ?
dnlilas said:
Since you have stock recovery, did you apply the full ROM A2017G-N-B04 (australian) from here:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547 ?
Click to expand...
Click to collapse
Yes but get an error in adb: cannot read 'rom.zip'
the_cyberspace said:
Yes but get an error in adb: cannot read 'rom.zip'
Click to expand...
Click to collapse
Did you try installing the ROM zip from inside the stock recovery?
dnlilas said:
Did you try installing the ROM zip from inside the stock recovery?
Click to expand...
Click to collapse
I can choose "apply update from ADB" and "apply update from SD card". When i choose the option from SD card i get a error: "sorry, can`t sdcard upgrade" and when i`m flash the rom in adb: "cannot read 'rom.zip' ".
Hi,
I just bought Mi A1.
Now, I wanted to install oreo.
So I was trying to root and install twrp.
Now I'm no expert, I just follow the provided steps and have been successful with past devices.
Note :
1) Developer enabled
2) oem unlocking enabled
3) usb debugging enabled
So I'm using this https://forum.xda-developers.com/mi...l-one-driversunlocktwrpfactory-t3695256/page2
But, there are two issues :
1) When I click on Reboot in fastboot/bootloader mode , it shows this in command prompt : http://prntscr.com/i2sn1o
and in the app, it automatically disconnects from the device http://prntscr.com/i2sncw
2) While this is happening and I leave my device, it automatically goes out from fastboot to power off charging mode.
I tried on another pc too, and followed the steps according to video, still no luck.
And I tried manual methods too, like https://www.youtube.com/watch?v=tRcYUMBgvaI
no luck there either.
Please help.
your adb driver is not installed correctly i guess, happened to me too.
try "adb devices" and will show no devices, if this happen, is the adb driver issue.
this fixed for me.
https://forum.xda-developers.com/showthread.php?p=75163858#post75163858
riccetto80 said:
your adb driver is not installed correctly i guess, happened to me too.
try "adb devices" and will show no devices, if this happen, is the adb driver issue.
this fixed for me.
https://forum.xda-developers.com/showthread.php?p=75163858#post75163858
Click to expand...
Click to collapse
I don't know if there is issue with driver. Because during installation there was no error.
Also, when I command "adb devices" it shows me a device as number.
So it is able to connect to the device then right?
You must install adb drivers AND fastboot drivers separately. I always had to install them manually via device manager. If your phone reboots from fastboot mode automatically, I'm 99% sure that you do not have drivers installed correctly.
_mysiak_ said:
You must install adb drivers AND fastboot drivers separately. I always had to install them manually via device manager. If your phone reboots from fastboot mode automatically, I'm 99% sure that you do not have drivers installed correctly.
Click to expand...
Click to collapse
Hmmmmm. Ok, I'll do that then. Thanks buddy. I'll try again and reply back asap.!!
Hi,
Despite my best efforts device manager still shows yellow at Android compesite device..
In ADB SHELL MODE it won't list the device on ADB DEVICES Command.
Can someone help me with the right USB / fastboot drivers for Mi A1 for Windows 10 Pro
Managed to get the fastboot working.
vu2pmc said:
Hi,
Despite my best efforts device manager still shows yellow at Android compesite device..
In ADB SHELL MODE it won't list the device on ADB DEVICES Command.
Can someone help me with the right USB / fastboot drivers for Mi A1 for Windows 10 Pro
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2588979
Compatibility mode, run as admin, you can also try with another source of adb files, because I had issues with the one from magisk manager.
Not working for me