Hello , I had my mini rooted and with recovery TWRP but is is disappeared , I can not get it open not by phisical keys nor through ADB commands , I tried to install it again with ADB but no succes , I have also tried to do a factory reset but it also does not work , it reboots as always , no changes at all , I have tried tuliptool but it doesnt work also , any idea please ???
TWRP recovery disappeared? That's new.
What about fastboot boot twrp.img
Replace twrp.img with the location of the twrp image on your PC. You need debugging mode on and unlocked bootloader for that to work.
Also have you tried flashing it again?
XDHx86 said:
TWRP recovery disappeared? That's new.
What about fastboot boot twrp.img
Replace twrp.img with the location of the twrp image on your PC. You need debugging mode on and unlocked bootloader for that to work.
Also have you tried flashing it again?
Click to expand...
Click to collapse
Hello , I can not start TWRP , instead system reboots with physical keys or ADB commands , I can not flash , through ADB ,"ADB Devices" list the phone but with any other command I only get "waiting for device "
Rafaru said:
Hello , I can not start TWRP , instead system reboots with physical keys or ADB commands , I can not flash , through ADB ,"ADB Devices" list the phone but with any other command I only get "waiting for device "
Click to expand...
Click to collapse
That's a driver problem, you can your device driver from here.
Device driver may be different from driver installed upon connecting the device, or the driver installed from the internet through windows device manager.
XDHx86 said:
That's a driver problem, you can your device driver from here.
Device driver may be different from driver installed upon connecting the device, or the driver installed from the internet through windows device manager.
Click to expand...
Click to collapse
Thanks , I will try and see
Hello XDHx86 , I have installed drivers , adb devices recognizes the phone but "fastboot boot recovery.img" states "waiting for device" , trying "adb reboot bootloader" phone system is restarted normally , seems no TWRP at all , just like using physical keys , but it was installed as i have used it many times
Edit: I have just checked device manager and on Android Device folder appear "Android ADB Interface" - "Android Bootloader Interface" and "Android Composite ADB Interface" , on all of them in properties appears "Device can not be started Code 10 "
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have also tried a factory reset from settings but device just reboots with no changes
Rafaru said:
Hello XDHx86 , I have installed drivers , adb devices recognizes the phone but "fastboot boot recovery.img" states "waiting for device" , trying "adb reboot bootloader" phone system is restarted normally , seems no TWRP at all , just like using physical keys , but it was installed as i have used it many times
Edit: I have just checked device manager and on Android Device folder appear "Android ADB Interface" - "Android Bootloader Interface" and "Android Composite ADB Interface" , on all of them in properties appears "Device can not be started Code 10 "
View attachment 5252773
Click to expand...
Click to collapse
That command only works in fastboot mode, you need to use adb reboot bootloader first.
On a side note the command for checking devices in fastboot is fastboot devices
Rafaru said:
I have also tried a factory reset from settings but device just reboots with no changes
Click to expand...
Click to collapse
I don't know why you thought factory reset would restore recovery, you just wiped the device and lost root access if you had it.
XDHx86 said:
That command only works in fastboot mode, you need to use adb reboot bootloader first.
On a side note the command for checking devices in fastboot is fastboot devices
I don't know why you thought factory reset would restore recovery, you just wiped the device and lost root access if you had it.
Click to expand...
Click to collapse
Hi , yes I know but with adb reboot bootloader phone just boots to system does not get fastboot mode , I tried factory reset just to start all over , root , recovery and so on . but it does not work , nothing is wiped it just reboots with all data , apps....nothing is erased
Rafaru said:
Hi , yes I know but with adb reboot bootloader phone just boots to system does not get fastboot mode , I tried factory reset just to start all over , root , recovery and so on . but it does not work , nothing is wiped it just reboots with all data , apps....nothing is erased
Click to expand...
Click to collapse
Have you checked if your bootloader is unlocked?
XDHx86 said:
Have you checked if your bootloader is unlocked?
Click to expand...
Click to collapse
As far as I know it was unlocked when I bought it , at least I was told so , I have never checked myself , do not know how to
Rafaru said:
As far as I know it was unlocked when I bought it , at least I was told so , I have never checked myself , do not know how to
Click to expand...
Click to collapse
I don't think you have unlocked bootloader, but first check the driver and USB cable.
If everything seems fine then follow this thread to check bootloader status and unlock it then flashing TWRP. Or directly flashing it if your bootloader is already unlocked.
XDHx86 said:
I don't think you have unlocked bootloader, but first check the driver and USB cable.
If everything seems fine then follow this thread to check bootloader status and unlock it then flashing TWRP. Or directly flashing it if your bootloader is already unlocked.
Click to expand...
Click to collapse
I have already tried but zadig does not recognize the device , I guess it is/was open as I had TWRP and I have changed in the past the ROM , now I have Lineage 16 , I also had Lineage 14 , AOSP , I reinstalled drivers as you told me and cable is the original from ZTE and I have used it in the past to flash from this same PC , never had problems before , I guess I did something wrong and phone seems "blocked" as does not respond to ADB nor Factory reset , pc does bot recognize it , will keep trying , thansk anyway for your help
Rafaru said:
I have already tried but zadig does not recognize the device , I guess it is/was open as I had TWRP and I have changed in the past the ROM , now I have Lineage 16 , I also had Lineage 14 , AOSP , I reinstalled drivers as you told me and cable is the original from ZTE and I have used it in the past to flash from this same PC , never had problems before , I guess I did something wrong and phone seems "blocked" as does not respond to ADB nor Factory reset , pc does bot recognize it , will keep trying , thansk anyway for your help
Click to expand...
Click to collapse
How can't the tool recognize the device?
Check for the following:
Are you sure the device is in EDL mode? It should display nothing, but only a black screen and no vibrations or any indicators. Try manually rebooting to EDL mode (Volume Up + Volume Down + Power), or adb reboot edl and you should see QHSUSB_BULK unknown device or something similar in windows device manager.
Are you sure you installed the correct driver? EDL mode requires different driver than the device driver. You can get that from here. You may want to boot into test mode to install the driver properly.
Original cable can also get faulty it's in essence still a cable. Try a different cable, or get an EDL cable they're cheap.
XDHx86 said:
How can't the tool recognize the device?
Check for the following:
Are you sure the device is in EDL mode? It should display nothing, but only a black screen and no vibrations or any indicators. Try manually rebooting to EDL mode (Volume Up + Volume Down + Power), or adb reboot edl and you should see QHSUSB_BULK unknown device or something similar in windows device manager.
Are you sure you installed the correct driver? EDL mode requires different driver than the device driver. You can get that from here. You may want to boot into test mode to install the driver properly.
Original cable can also get faulty it's in essence still a cable. Try a different cable, or get an EDL cable they're cheap.
Click to expand...
Click to collapse
I have tried again , I wrote adb reboot edl , device did as you said , black screen and no sound , vibrations , I can see QHSUSB_BULK in device manager , now I ran zadig that says 0 devices found , as per tuliptool thread it should detect it and install WINUSB driver but that is not happenning , on CMD I write command as tuliptool read boot but system says tuliptool is not recognized as internal or external command .......sorry I guess is me doing something wrong
EDIT: I have managed to do at last , it says Device Unlocked : yes Device tampered : no
Rafaru said:
I have tried again , I wrote adb reboot edl , device did as you said , black screen and no sound , vibrations , I can see QHSUSB_BULK in device manager , now I ran zadig that says 0 devices found , as per tuliptool thread it should detect it and install WINUSB driver but that is not happenning , on CMD I write command as tuliptool read boot but system says tuliptool is not recognized as internal or external command .......sorry I guess is me doing something wrong
Click to expand...
Click to collapse
Manually installing the driver should do the trick. I already provided the link, and as I said: "You may have to boot the PC into test mode to install the driver properly"
XDHx86 said:
Manually installing the driver should do the trick. I already provided the link, and as I said: "You may have to boot the PC into test mode to install the driver properly"
Click to expand...
Click to collapse
it is working now , I have already confirmed that bootloader is unlocked , could you let me please know how to write TWRP please ?? tuliptool-win64.exe write recovery "filename" ?? I have tried this but says "Sending programmer...Failed to send programmer: Unknown error"
EDIT: At last I did it , TWRP installed and working , phone fully erased to start installing apps and so on , many thanks for your help
XDHx86 said:
That's a driver problem, you can your device driver from here.
Device driver may be different from driver installed upon connecting the device, or the driver installed from the internet through windows device manager.
Click to expand...
Click to collapse
Hey I'm having a similar issue. Fastboot wont work. You mentioned a driver problem. Im on linux and installed adb and fastboot. Im pretty sure i did it correctly. adb works fine, fastboot not. In the stock recovery was no option for fastboot neither in twrp. Is it possible that fastboot is disabled or not available on my device (Axon 7 mini B2017G)
Wave1982 said:
Hey I'm having a similar issue. Fastboot wont work. You mentioned a driver problem. Im on linux and installed adb and fastboot. Im pretty sure i did it correctly. adb works fine, fastboot not. In the stock recovery was no option for fastboot neither in twrp. Is it possible that fastboot is disabled or not available on my device (Axon 7 mini B2017G)
Click to expand...
Click to collapse
No, your device fastboot isn't disabled, unless stated so by your carrier. Like Verizon almost all of their devices are perma-locked.
Did you check the device driver itself? You can get your device driver from this link. You can install it automatically or if it doesn't work try installing it manually. Don't forget to restart your PC.
If it still doesn't work then it may be cable connection issues, try a different cable.
If it still however doesn't work, then I don't know what may be the cause of the issue. Although you can always count on XDA forums for such issues, here's an article on how to unlock your specific device's bootloader.
Related
Hey guys,
I was hoping you might help me as I was struggling to find an answer through google search.
After using the ZUK Z1 (Cyanogen OS 12.1 with the latest update), a few days ago the phone suddenly restarted and entered an endless restart loop
I've tried wiping the data, the cache and the user files.
I've tried applying the latest CyanogenOS zip for the Z1 either through sideload or locally from the device.
Nothing worked and I'm becoming very frustrated
I thought that maybe if I could wipe the system partition and then apply the COS zip than maybe it would work.
Does anybody have any ideas?
Thanks in advance,
Yoav.
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-z1/development/win-zuk-z1-toolkit-0-1-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 too.
Can you tell me what exactly did you do?
As far as I can see nothing works for me with the toolkit...
Did you use a mac or windows?
I checked that the driver is recognized (ShenQI), also tried manually using fastboot commands to unlock the bootloader and flashing images, but since my device is bricked I am unable to allow OEM unlock from inside Android
Update:
So I came across a discussion in this forum about bringing a bricked ZUK back to life
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
Done that, seem to be successful, however the phone won't turn on and the QPST Configuration tool shows that the device is stuck in download mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone has any idea what that means? Does that mean that it is a hardware failure?
yoavk said:
Can you tell me what exactly did you do?
As far as I can see nothing works for me with the toolkit...
Did you use a mac or windows?
I checked that the driver is recognized (ShenQI), also tried manually using fastboot commands to unlock the bootloader and flashing images, but since my device is bricked I am unable to allow OEM unlock from inside Android
Update:
So I came across a discussion in this forum about bringing a bricked ZUK back to life
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
Done that, seem to be successful, however the phone won't turn on and the QPST Configuration tool shows that the device is stuck in download mode.
Does anyone has any idea what that means? Does that mean that it is a hardware failure?
Click to expand...
Click to collapse
Ok, so first, don t panic. If you re able to acces recovery and fastboot mode, there is a strong hope. I have Windows 7 on my PC, btw.
I tried the qpst tool to flash the stock, but i couldn t. That is why i turned to the Zuk Tool Kit, which did the trick for me.
To use this tool, FIRST OF ALL YOU MUST INSTALL ADB AND FASTBOOT. you can find varius tutorials about this on te interent. I provide you some, too:
http://forum.xda-developers.com/showthread.php?t=2588979
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
It was hard for me too to understand what is going on at first, but i did some research on the topic, and i got it.
After you installed adb, you can check if it is instaled by running the command "adb version" in CMD:
You should recieve something like this if it is installed.
After you installed fastboot and adb, install the Zuk Toolkit following the steps provided in the thread of Lenvo Zuk toolkit. Download cygwin, open cygwin terminal and drag start.sh from zuk toolkit folder into terminal window, press Enter, and you will have the menu open like this:
Here, just naviagte by writing the number corresponding to the menu you want to access and hitting enter.
Under "6. Do some basic ADB and Fastboot commands.
" coomands, you will have this menu:
Do note that [fASTBOOT] marked commands will work only when your phone is in fastboot mode. To acces your fast boot mode of your phone, just select "reboot to bootloader" option from recovery menu.
Once you managed to reach this state, you can put your phone in fastboot mode, and try the command "10. [Fastboot] Reflash to stock using a manually downloaded factory image."....
IF this doesn t work, try to flash the stock rom via sideload option from recovery menu of your phone. To do this, you must chose the sideload option from recovery menu. Download the stock signed rom from here https://cyngn.com/support(NOT THE FASTBOOT ONE, JUST THE SIGNED ONE.) Rename your stock rom zip file you just downloaded "sideload" and place it on desktop. Then use THE command "4. [ADB] Sideload a zip file.
" from zuk toolkit to flash the rom. Also you must have the phone connected to pc with the USB-c cable during the whole process, of course. If it works, your phone will show the animation of flashing procees on its screen. Wait until the phone stops, chose wipe dalvik and reboot.
Use the snipping tool or PrtSc to take screen images from where you are stuck or you don t know what to do, and post them here.
Well, the QPST method seemed to have worked (as indicated by the QFIN tool).
However, it seems that the bootloop is back, when I am only able to boot into the ZUI recovery without any option of fastboot.
Edit:
Here is a pic of the Recovery (there is no option of adb sideload)
http: //s10.postimg. org/flaa11g3d/IMG_20160120_121012.jpg
Here is the fastboot
http: //s22.postimg. org/rgz4rt3a9/IMG_20160120_122555.jpg
And this is what i get when I try to use fastboot commands
C:\ WINDOWS\ system32> fastboot -i 0x2b4c oem device-info
< waiting for device >
Click to expand...
Click to collapse
All devices are discovered correctly in device manager
http: //s30.postimg. org/g8m1taywx/Capture.jpg
yoavk said:
Well, the QPST method seemed to have worked (as indicated by the QFIN tool).
However, it seems that the bootloop is back, when I am only able to boot into the ZUI recovery without any option of fastboot.
Edit:
Here is a pic of the Recovery (there is no option of adb sideload)
http: //s10.postimg. org/flaa11g3d/IMG_20160120_121012.jpg
Here is the fastboot
http: //s22.postimg. org/rgz4rt3a9/IMG_20160120_122555.jpg
And this is what i get when I try to use fastboot commands
All devices are discovered correctly in device manager
http: //s30.postimg. org/g8m1taywx/Capture.jpg
Click to expand...
Click to collapse
You have the ZUI version?? Because this does not seem to be the stock recovery of cyanogen. At least, i have the option to sideload in my recovery.
When you chose the install Update pacakge option, what options are displayed on your phone?
Also, if u installed qpst, you shoudl have in your PC a program callled QFIL, which is the flasher tool for all lenovos including ZUK. You must flash the zui stock rom using qfil. Read this thread for more info and downloads: http://forum.xda-developers.com/zuk...ui-version-t3265741/post64865607#post64865607
Also, here is a thread of a guy who had pretty much the same problem as you and managed to flash the stoc using QFIL : http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257
Extentho said:
You have the ZUI version?? Because this does not seem to be the stock recovery of cyanogen. At least, i have the option to sideload in my recovery.
Click to expand...
Click to collapse
Yeah, it was cyanogen and with QFIN I flashed stock ZUI in hopes that it will the bootloop.
I contacted coolicool, which is from where I bought the device.
I will send the device to them. I hope that they'll be able to find the problem.
yoavk said:
Yeah, it was cyanogen and with QFIN I flashed stock ZUI in hopes that it will the bootloop.
I contacted coolicool, which is from where I bought the device.
I will send the device to them. I hope that they'll be able to find the problem.
Click to expand...
Click to collapse
I think you could try un-bricking it by yourself. It is not that hard. But if those guys from coolicool will change your phone, that s ok too. Blease be advised that rooting voids warranty...soo
Lucky me I didn't have the chance to do it
I didn't even have the chance to unlock the bootloader
Does anyone here have any experience with the guys over at coolicool?
i flashed coldbird's zip for capacitive touch on the fingerprint sensor. got into an endless restart loop after that. to every option, the toolkit replies command not found.
eg: ./xposeduninstallbootloop.sh: line 128: adb: command not found
followed by whatever option was ordered, that has been done successfully but can see no change.
Try this
https://forum.xda-developers.com/zuk-z1/help/boot-loop-cyanogen-logo-t3666056
Easy bro easy, the steps that you are following are a bit confusing, aren't they?
Please tell me the current status of your phone. I might be able to help.
Hi guys I tried to root my LeTV 1 Pro but it didn't worked.
My phone keeps rebooting in fastboot ( I see the penguin 10-15sec and it reboot again and again) or it stays alight with the penguin.
Computer doesn't recognize it.
Thanks.
Try and plug it to your computer then keep power and wol down pressed for like 15 sec: now fastboot should stick and device shouldn't reboot, so you can flash a recovery (TWRP?) and start over with a new ROM.
Thank you for your reply,
It still doesn't work, penguin stays on screen but it's not recognized by computer ( before the brick it was)
I'm not very experienced in rooting btw.
Edit : The recovery.bat in the file X1_X800_TWRP_Recovery2.8.7.0 says "Complete! The device is ready to reboot into Recovery." which I do but it keeps reboot with the pinguin on.
I recieved my phone today and it just wont stay in fastboot mode. I can do anything I want but it just keeps rebooting before I can flash anything. Any suggestions on how I should keep the Phone in Fastboot mode?
You need to install drivers. After that it will not reboot anymore. That worked for me atleast.
What kind of drivers do I need? Please link them to me I have tried a lot of drivers. The thing is that the phone also does not stay in Fastboot mode when not plugged into the PC.
It's my topic for my problem so don't ask questions for you on it please u_u
zamul said:
It's my topic for my problem so don't ask questions for you on it please u_u
Click to expand...
Click to collapse
The reason I got on here is because my problem seems kinda similar to yours. I'm sorry to bother you. I was just in search of help.
DatNoob said:
The reason I got on here is because my problem seems kinda similar to yours. I'm sorry to bother you. I was just in search of help.
Click to expand...
Click to collapse
Zamul don't be mean. He just asked for help as you did...
I have downloaded drivers (I think) from https://twrp.me/devices/letvle1pro.html where I also get twrp 3.0.2.0
Btw if you are using Windows you can open Device Manager and there you will see your device and what drivers it has installed (you can always use update drivers function, maybe that will help too).
Here is a little guide how I managed to get twrp:
Just download it (drivers and intall them) (and download twrp also). Place twrp file to the folder where you have your adb installed.
In phone settings go to developer menu (first you need to unlock it) and you need to switch on usb debugging.
Connect phone to the pc via usb.
Open command prompt in your adb folder and type Adb devices (if you have drivers installed corectly you will se your devices connected under some code).
Then just write Adb reboot booloader and phone will restart to the recovery.
Type into the comand prompt: fastboot flash recovery name***.img (where the name is the file name of twrp you have downloaded- just a tip: rename it so it is easier to remember for example to twrp. Then the command will look like: fastboot flash recovery twrp.img)
If succesful, write fastboot reboot and that is all.
Btw for me it did not work first time. I had to load twrp for second time and when I wrote fastboot reboot then I immediately pressed volume up so It went directly to twrp recovery.
Hope it helps. Cheers
I have this problem
Hello
I have your problem have you solve this?
Thanks
Hi guys. I have a problem! My letv x800 CN boots to TWRP but doesn't start the system (EUI logo loading all the time) I don't know how to transfer ROM into the phone in order to flash it. I installed all the drivers and PC recognize it. PLEASE HELP!!!
Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
arnab8820 said:
Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
Click to expand...
Click to collapse
Try qfil method
JovanSijacki said:
Try qfil method
Click to expand...
Click to collapse
Can you give the link please..... please note the phone is no longer detected in pc
arnab8820 said:
Can you give the link please..... please note the phone is no longer detected in pc
Click to expand...
Click to collapse
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
I already have installed the drivers. Still not detected. Even the device manager does not show a device is connected
sasukay said:
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
Click to expand...
Click to collapse
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
arnab8820 said:
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
Click to expand...
Click to collapse
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
sasukay said:
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
Click to expand...
Click to collapse
There is only one pcb in it. Changing the cable does not make a difference
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
arnab8820 said:
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
Click to expand...
Click to collapse
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful, type in
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
arnab8820 said:
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
Click to expand...
Click to collapse
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also try
Code:
fastboot boot recovery.img
Sometimes only this works which temporarily boots into the custom recovery.
sasukay said:
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also try
Sometimes only this works which temporarily boots into the custom recovery.
Click to expand...
Click to collapse
Ok friend i will post the results tonight
sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Tried the above method but no luck it gives an error: "unknown command or device is lock".
arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
sasukay said:
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
Click to expand...
Click to collapse
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
arnab8820 said:
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
Click to expand...
Click to collapse
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
sasukay said:
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
Click to expand...
Click to collapse
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
arnab8820 said:
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
Click to expand...
Click to collapse
Try fastboot oem unlock
arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
I think you are missing something (maybe).
The command is "fastboot flash recovery recovery.img"
If the recovery files name is twrp.img then command will be "fastboot flash recovery twrp.img".
So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Edit: I solved my issue by downloader the stock B08 system on my S5 and then i placed it in the external sd. Then i put the SD back into the Axon and installed the system. After i had installed the system and booted into the OS i could enter adb with my device being recognized and after that i flashed twrp by using ADB.
I have a new problem though and that is that i can't install the 3.1.0.0. twrp. it only boots into black screen when i enter recovery. I can use the 3.0.4.0. version though.
You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?
senny22 said:
So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Click to expand...
Click to collapse
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?
nonamesl said:
You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?
Click to expand...
Click to collapse
Correct. It simply reboots.
Yup, i tried installing the B29 stock system on my G model and so i suppose i had the wrong bootstack becasue this is where my problems started.
I get to the stock android recovery.
raystef66 said:
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?
Click to expand...
Click to collapse
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.
senny22 said:
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.
Click to expand...
Click to collapse
You should see your phone as QUSB_BULK. Installed the ZADIG drivers ? That may cure the problem.
After that, imo, it is important you can reboot edl and flash TWRP recovery again AND when it recounts, you pull usb.
Normally you will have replaced recovery , reboot ok and you can enter TWRP and fastboot also.
ps : sometimes it is also advisable to go to ADB RECOVERY directly and do the processes.
ps2 : when TWRP backup, you can always put it on SD via other phone and in TWRP restore. Normaly you're good to go then...
Try the Marshall London Bootloader Interface driver maybe?
nonamesl said:
Try the Marshall London Bootloader Interface driver maybe?
Click to expand...
Click to collapse
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?
senny22 said:
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?
Click to expand...
Click to collapse
Installing the driver and using it for the phone (device manager -> change driver manually (or something of the sort)) worked for me, but it could differ. Let me know. You don't have to uninstall other drivers just use that specific one for your phone by switching the driver manually via device manager.
So I tried to root my Xiaomi mi 9t again (1st time was a success on MIUI 10), now I'm on MIUI 11.0.6.0 and I can't use ADB since it won't show on fastboot.
However, I can see my device when I'm not in fastboot...
OEM is UNLOCKED
USB DEBUGGING is ON
I have tried basically all options available.. reinstalling drivers and trying different USB ports and cables.
Device manager won't show "Android ADB interface" while in fastboot
The way I tried to root was this thread https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
Razexay said:
So I tried to root my Xiaomi mi 9t again (1st time was a success on MIUI 10), now I'm on MIUI 11.0.6.0 and I can't use ADB since it won't show on fastboot.
However, I can see my device when I'm not in fastboot...
OEM is UNLOCKED
USB DEBUGGING is ON
I have tried basically all options available.. reinstalling drivers and trying different USB ports and cables.
Device manager won't show "Android ADB interface" while in fastboot
The way I tried to root was this thread https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
Click to expand...
Click to collapse
You cannot use ADB commands in Fastboot, only fastboot commands
For ADB commands, you must be booted to Android
Please distinguish ADB and fastboot
In system, for ADB, try:
>> adb devices
In Fastboot, try:
>> fastboot devices
If everything is ok, both will respond with your device ID (same you also see in the folder name when making TWRP backup)
zgfg said:
You cannot use ADB commands in Fastboot, only fastboot commands
For ADB commands, you must be booted to Android
Please distinguish ADB and fastboot
In system, for ADB, try:
>> adb devices
In Fastboot, try:
>> fastboot devices
If everything is ok, both will respond with your device ID (same you also see in the folder name when making TWRP backup)
Click to expand...
Click to collapse
It didn't work with fastboot commands either, didn't know that there was a difference, so didn't point that out. But yea.. no luck with fastboot commands.
Razexay said:
It didn't work with fastboot commands either, didn't know that there was a difference, so didn't point that out. But yea.. no luck with fastboot commands.
Click to expand...
Click to collapse
Which ADB/Fastboot tool have you installed? Tried Mini ADB & Fastboot?
https://drive.google.com/file/d/1mOBkqL92MF7s7rhkX2cD7i7dSD6_sd-K/view?usp=drivesdk
If you're sure that you have the needed drivers installed and tried different usb ports/cables ADB and Fastboot should work.
When you are booted to Android, connected to PC and enter "adb devices" take a look on your mobile, there should appear a prompt to allow usb debugging. Only if you agree adb (when booted to Android) and fastboot (in fastboot mode as @zgfg posted) will work.
Razexay said:
So I tried to root my Xiaomi mi 9t again (1st time was a success on MIUI 10), now I'm on MIUI 11.0.6.0 and I can't use ADB since it won't show on fastboot.
However, I can see my device when I'm not in fastboot...
OEM is UNLOCKED
USB DEBUGGING is ON
I have tried basically all options available.. reinstalling drivers and trying different USB ports and cables.
Device manager won't show "Android ADB interface" while in fastboot
The way I tried to root was this thread https://forum.xda-developers.com/mi-9t/how-to/guide-easiest-to-root-twrp-t4000209
Click to expand...
Click to collapse
The same issue happened to me once. I installed 'Mi Unlock' tool from here (https://c.mi.com/thread-2262302-1-0.html), and that tool installed the necessary drivers. On the top right of the Mi Unlock interface, there's the settings icon, and that has the option to install the drivers. After rebooting, the Device Manager showed ADB interface. Try it.
On another occasion, 'MiFlash' tool (https://c.mi.com/thread-1857937-1-0.html) helped to install the necessary drivers in the same way to solve the issue.
I faced this issue and redownloaded the adb tools to a separate location and it worked.
I faced this issue and just used another USB cable.
mchtt said:
I faced this issue and just used another USB cable.
Click to expand...
Click to collapse
I tried 4 different cables, nothing worked.
Thanks for the suggestion
Wolfcity said:
Which ADB/Fastboot tool have you installed? Tried Mini ADB & Fastboot?
https://drive.google.com/file/d/1mOBkqL92MF7s7rhkX2cD7i7dSD6_sd-K/view?usp=drivesdk
If you're sure that you have the needed drivers installed and tried different usb ports/cables ADB and Fastboot should work.
When you are booted to Android, connected to PC and enter "adb devices" take a look on your mobile, there should appear a prompt to allow usb debugging. Only if you agree adb (when booted to Android) and fastboot (in fastboot mode as @zgfg posted) will work.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried many different tools.
I even tried to install ADB to different location.
Also tried 4 different cables on all 3 ports i have 2xUSB3.0 1xUSB2.0
Razexay said:
View attachment 5072073
View attachment 5072075
I have tried many different tools.
I even tried to install ADB to different location.
Also tried 4 different cables on all 3 ports i have 2xUSB3.0 1xUSB2.0
Click to expand...
Click to collapse
Try this
- Extract the attached zip.
- Connect the device to PC while in fastboot.
- On Device Manager, right click on the place where the 'Android ADB interface' shown without drivers installed.
- Click Update Driver Software > Browse my computer for driver software
- Browse to the extracted folder (tick 'Include subfolders').
- Click Next.
- Reboot the PC and check the Device Manager
Stillness said:
Try this
- Extract the attached zip.
- Connect the device to PC while in fastboot.
- On Device Manager, right click on the place where the 'Android ADB interface' shown without drivers installed.
- Click Update Driver Software > Browse my computer for driver software
- Browse to the extracted folder (tick 'Include subfolders').
- Click Next.
- Reboot the PC and check the Device Manager
Click to expand...
Click to collapse
It says that I already have the latest drivers.
Stillness said:
Try this
- Extract the attached zip.
- Connect the device to PC while in fastboot.
- On Device Manager, right click on the place where the 'Android ADB interface' shown without drivers installed.
- Click Update Driver Software > Browse my computer for driver software
- Browse to the extracted folder (tick 'Include subfolders').
- Click Next.
- Reboot the PC and check the Device Manager
Click to expand...
Click to collapse
The problem is that my phone won't be seen in Device Manager if its in fastboot mode.
Razexay said:
The problem is that my phone won't be seen in Device Manager if its in fastboot mode.
Click to expand...
Click to collapse
Perhaps something went wrong in the root procedure. May be the only option is to flash the ROM again via fastboot, install TWRP and root by Magisk zip.
Stillness said:
Perhaps something went wrong in the root procedure. May be the only option is to flash the ROM again via fastboot, install TWRP and root by Magisk zip.
Click to expand...
Click to collapse
So i should Flash .tgz fastboot rom with miflash?
Razexay said:
So i should Flash .tgz fastboot rom with miflash?
Click to expand...
Click to collapse
Yes. Most of the time that solves such issues.
- Here is a MiFlash guide: https://c.mi.com/thread-1857937-1-0.html
- Latest MiFlash download: https://cdn.alsgp0.fds.api.mi-img.com/micomm/MiFlash2020-3-14-0.rar
- After that flash TWRP recovery (steps mentioned there): https://forum.xda-developers.com/mi-9t/development/recovery-unofficial-twrp-xiaomi-redmi-t3960726
- Boot to TWRP and flash latest Magisk zip from it: https://github.com/topjohnwu/Magisk/releases
Stillness said:
Yes. Most of the time that solves such issues.
- Here is a MiFlash guide: https://c.mi.com/thread-1857937-1-0.html
- Latest MiFlash download: https://cdn.alsgp0.fds.api.mi-img.com/micomm/MiFlash2020-3-14-0.rar
- After that flash TWRP recovery (steps mentioned there): https://forum.xda-developers.com/mi-9t/development/recovery-unofficial-twrp-xiaomi-redmi-t3960726
- Boot to TWRP and flash latest Magisk zip from it: https://github.com/topjohnwu/Magisk/releases
Click to expand...
Click to collapse
If my device should be in Fastboot then it won't work, because miflash won't show my device while in fastboot.
So i tried to flash it while phone was on but nothing happens
Razexay said:
If my device should be in Fastboot then it won't work, because miflash won't show my device while in fastboot.
So i tried to flash it while phone was on but nothing happens View attachment 5072303
Click to expand...
Click to collapse
No, you can't flash from MiFlash while the device is on.
I haven't done this as I always use either TWRP or fastboot for updates but might I suggest updating MIUI from OTA. I think, it will download the necessary file to the device, and then you can go to the stock recovery and flash the update. Some other user here may have a better input on this.
Stillness said:
No, you can't flash from MiFlash while the device is on.
I haven't done this as I always use either TWRP or fastboot for updates but might I suggest updating MIUI from OTP. I think, it will download the necessary file to the device, and then you can go to the stock recovery and flash the update. Some other user here may have a better input on this.
Click to expand...
Click to collapse
How do i update MIUI from OTP?
I did a V12 update using "choose custom update package" since i did not have a auto update available.
Razexay said:
How do i update MIUI from OTP?
I did a V12 update using "choose custom update package" since i did not have a auto update available.
Click to expand...
Click to collapse
What MIUI version you are currently on?
Stillness said:
No, you can't flash from MiFlash while the device is on.
I haven't done this as I always use either TWRP or fastboot for updates but might I suggest updating MIUI from OTP. I think, it will download the necessary file to the device, and then you can go to the stock recovery and flash the update. Some other user here may have a better input on this.
Click to expand...
Click to collapse
What's OTP ? do you mean OTA ?
I got the exact same problem as the OP. I can't get a device (it doesn't show anything in windows neither in linux) when in fastboot. I think it's related to a MIUI rom global/EAE mismatch with the real usb chips in the phone and it screws any possibility to flash anything but authorized MIUI OTA updates. The 12 update apparently changed something : before that, fastboot device was just unrecognized (00/00 for device/vendor), and after that there nothing at all, nada, not even unrecognized device.