I have a 2013 Nexus 7 wifi tablet, bootloader locked, with USB debugging disabled. It decided mid-activity that all it would like to do in life is display the "Google" image on the boot up screen.
I can access the bootloader so I tried doing the standard wipe in recovery mode but that did not work.
Investigated Wugfresh's Nexus Root Toolkit. Drivers (Windows 7) are installed but under Step 4 of the Full Driver Configuration guide it is unable to find the device as an ADB device, even though the device does show up on my Device Manager (but only as bootloader interface, not ADB). Tried to use the unlock feature anyway but on the tablet it just gets stuck on the "unlock bootloader" screen after trying to run the unlock tool (choosing "yes" by pressing the up volume button to scroll to the yes option, followed by the power button to select it).
My questions based on this are simple:
1) Can I unlock this device without having USB debugging enabled? If so, how?
2) Can I restore to factory stock settings without having USB debugging enabled (and not using recovery mode on the device itself, as that does not work)? If so, how?
All of the tools I have seen thus far require that USB debugging be enabled on the device. Since I can't actually boot up the device, there is no way to make this happen. I don't really care about any of the data on the device, I just want it to function again to avoid buying a new one.
Stop using a toolkit. Your device will never be recognized by adb when booted into the bootloader.
Unlocking the bootloader is simple if you have the Windows drivers set up correctly. Open command prompt with admin privileges, type 'fastboot oem unlock' and done. This is why I hate toolkits.
nhizzat said:
Stop using a toolkit. Your device will never be recognized by adb when booted into the bootloader.
Unlocking the bootloader is simple if you have the Windows drivers set up correctly. Open command prompt with admin privileges, type 'fastboot oem unlock' and done. This is why I hate toolkits.
Click to expand...
Click to collapse
I believe this also requires that USB Debugging be enabled. I would paste links but the forum prevents me from doing so since I just signed up.
If I am incorrect in thinking that USB Debugging must be enabled for this to work, then please let me know. All I really need is clear instructions on how to hard reset the device without USB debugging enabled. Unlocking just seems to be a prerequisite for that in most of the tutorials I have found so far.
You can flash the device back to stock with wugs without adb. There should be an option you pick under the factory restore button that says "soft bricked" which tells wugs that it needs to go straight fastboot mode instead of trying to restart the tablet with adb.
skrypj said:
You can flash the device back to stock with wugs without adb. There should be an option you pick under the factory restore button that says "soft bricked" which tells wugs that it needs to go straight fastboot mode instead of trying to restart the tablet with adb.
Click to expand...
Click to collapse
Thanks for your reply. I have tried this option without the ADB (but with my computer recognizing the device). Since it did not work I expect the device is well and truly screwed (the recovery mode factory reset also does not work on the tablet itself).
Bugnerd said:
Thanks for your reply. I have tried this option without the ADB (but with my computer recognizing the device). Since it did not work I expect the device is well and truly screwed (the recovery mode factory reset also does not work on the tablet itself).
Click to expand...
Click to collapse
Couple of things:
1. You may also have a driver issue, I was playing with this the other day on both my Nexus 5 and Nexus 7. My nexus 5 worked fine, but later that day when i tried my nexus 7 I had troubles with my PC recognizing the N7 in fastboot mode. It would be fine in ADB and would reboot, but then the computer would freak out when it saw the fastboot device. Sometimes it would kinda work, sometimes the N7 would freeze on the bootloader screen or fail to flash during the process. It even locked my PC at one point. I completely uninstalled(per the Step 1 instructions in Wug's) all Android associated drivers(Samsung, LG, Asus, whatever. Kill them all) on the PC and reinstalled and it solved the issues. It sounds like maybe your PC is failing to flash properly like mine was.
2. Not sure if you tried this yet but; go to Options Menu>Flash Stock Tab>Check "Enable 'Force Flash Mode' . . . " Then try to flash stock + unroot again with the soft-bricked option selected. This basically makes Wug's ignore the check process at the beginning of the flash. I had to do this for both my N5 and N7.
Keep in mind, you will lose EVERYTHING on your N7 if you unroot and flash, including your internal storage.
Yeah, it does not seem to want to do the unroot + flash even with the override of checks. It seems unlocking is really a prerequisite for that tool (according to the text that appears as it proceeds), and unlocking appears to require the USB debugging. If it really can be unlocked without that, then it is not cooperating and just getting stuck on the unlocking screen. I expect it is now a very expensive paperweight.
All of this nonsense just over a year since I bought it, of course.
Try it with another computer, another USB cable...
I'm in the same boat, can't get it to unlock so it's essentially dead now
I've tried original and a G3 usb cord and nothing, front and rear USB ports, just will not unlock, almost to the point of sending it on and paying to get it fixed if possible , will try another computer first
Can you boot manually into fasboot mode and do flashing full stock firmware for ur device..
Bcoz I thinks you don't need usb debugging when on fastboot mode..
if you want to use toolkit, you must setup all driver for ur device first using the toolkit.. but you must do it when ur device is full "working", not when It's just stuck on google image... that's ur main problem now ...
you should try install the driver again on new "fresh" pc ....
Good luck bro... :fingers-crossed:
Did you try to manually unlock it? Boot to the boot loader screen(down volume+power) and the fastboot unlock it using the cmd in windows?
Az-one786 said:
Can you boot manually into fasboot mode and do flashing full stock firmware for ur device..
Bcoz I thinks you don't need usb debugging when on fastboot mode..
if you want to use toolkit, you must setup all driver for ur device first using the toolkit.. but you must do it when ur device is full "working", not when It's just stuck on google image... that's ur main problem now ...
you should try install the driver again on new "fresh" pc ....
Good luck bro... :fingers-crossed:
Click to expand...
Click to collapse
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
I can try the drivers again on another PC, but I have a feeling that won't fix anything.
skrypj said:
Did you try to manually unlock it? Boot to the boot loader screen(down volume+power) and the fastboot unlock it using the cmd in windows?
Click to expand...
Click to collapse
I looked into this a week or so ago and I think I determined that it would also require the USB debugging to be on (at least from the tutorials). Do you have any recommendations of tutorials on this process? Screwing around with this stuff is not really my bag.
Bugnerd said:
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
I can try the drivers again on another PC, but I have a feeling that won't fix anything.
Click to expand...
Click to collapse
Ok.., Your have no choice by now, you'll need to find a working driver for your PC to get recognize your tablet when on fastboot mode..
I've got this issues before when I want to update my tab using toolkit...
My PC can recognized my tab as adb devices, but when it's reboot to check fastboot status it fail to detect my device is on fastboot mode..
But maybe I'm so lucky that day, Moboginie notification has pop-up and it's has searching and found the driver and fix it itself ...
Then i try again and this time it's has no problem at all till now... I still can access my storage using Moboginie but until now window explorer still fail to recognized my N7...
It's so weird isn't it ...
Try Moborobo
Bugnerd said:
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
Click to expand...
Click to collapse
After the recovery screen with "sick" Andy, did it automatically begin to reboot? If not, you know that it's very tricky with the power+vol up button (sometimes I think it's power+both volume buttons that works) to access that screen in recovery (the one past sick Andy). Sometimes I've tried five or six times. I have twrp so I can't check it out right now.
As far as adb/fastboot drivers set up to run any commands, I thought they were required. I'm not certain about USB debugging. It seems you've tried with your device in fastboot and running Cmd (fastboot oem unlock) from your fast boot directory. Do you get a device code when you enter [fastboot devices] while in that directory? If not, your N7 will not accept fastboot commands.
Sent from my Nexus 7 using Tapatalk
Related
Hi all,
Hope someone can help, I have a desire HD that has some issues.
Long story short the phone was acting up and was flashed with a non official ROM. It was working originally but after about a week it started acting up, with apps force closing, phone crashing altogether etc.
I am trying to get the phone back to a state that Vodafone in Australia will be able to warranty the phone in.
The current situation is that when the phone turns on, it'll load straight to the bootloader/hboot. Recovery mode does not work - it dumps you in to fastboot menu and fails to load.
System restore from boot menu does not work either, and there is no rom at all so USB debugging is a no go, and there appears to be no way to flash the ROM.
Any ideas? Any help would be greatly appreciated.
Thanks
Sent from my GT-P7100 using XDA App
Use adb / fastboot to push a new recovery to the phone (I hope you left USB debugging enabled).
Sent from my Ericsson T39m
Sadly no USB debugging doesn't seem to work. Makes the sound that it connects to the computer and that bootloader states its connected by usb however it doesn't seem to phone is connected. Any other ideas?
Sent from my GT-P7100 using XDA App
CrystalCastle said:
Sadly no USB debugging doesn't seem to work. Makes the sound that it connects to the computer and that bootloader states its connected by usb however it doesn't seem to phone is connected. Any other ideas?
Sent from my GT-P7100 using XDA App
Click to expand...
Click to collapse
ooh i tested it in my DHD and don´t works...how can be possible that don´t works adb parameters, but fastboot commander works perfectly??
maybe we have anything that works badly in our PC´s.. i´m in it...
ei crystal!! has you tested with FASTBOOT COMMANDER? if you download it you can flash a new recovery from this tool... its intuitive...
you only must to download the tool
download the recovery (lastest CWM in the DHD android development forum)
put the file in the paragraph that says "RECOVERY:not file set" and then push FLASH IT"".maybe you enjoy...
remember to put your device into boot loader
CrystalCastle said:
Sadly no USB debugging doesn't seem to work. Makes the sound that it connects to the computer and that bootloader states its connected by usb however it doesn't seem to phone is connected. Any other ideas?
Click to expand...
Click to collapse
How did you check to see if adb shell can see the device?
Run an pb98.img from the bootlaoder
Sent from my Motorola Startac running Atari 2600 software!
Mr_JMM said:
How did you check to see if adb shell can see the device?
Click to expand...
Click to collapse
adb get-state
result:
unknown
Code:
adb devices
But this does depend on you having previously ticked USB Debugging option before you had all these problems (no way to check now without being able to boot the phone).
If this fails you may have to try the previous suggestion of putting a PD98IMG on your sdcard then going into fastboot on the phone.
Mr_JMM said:
But this does depend on you having previously ticked USB Debugging option before you had all these problems (no way to check now without being able to boot the phone).
If this fails you may have to try the previous suggestion of putting a PD98IMG on your sdcard then going into fastboot on the phone.
Click to expand...
Click to collapse
Currently there is no Rom on the Phone. Just put PD98IMG.zip on the SD card which seems to be updating. Does it normally take a while to Update all the Sections?
Can take anything from 5 to 20+ minutes.
Seems to be taking ages to even get past [1]. Is that normal? Hasn't done anything. It says "Updating" yet I'm still yet to see it get past "[1] BOOTLOADER"
Just to confirm...
1. Turn phone off
2. Put PD98IMG file onto ROOT of sd card
3. Use vol- and power button to get to Fastboot
4. Scroll and select Bootloader (HBOOT)
(might automatically do last step when you boot phone)
Phone will show a message to say it is looking for the file then unpack it and install.
Mr_JMM said:
Just to confirm...
1. Turn phone off
2. Put PD98IMG file onto ROOT of sd card
3. Use vol- and power button to get to Fastboot
4. Scroll and select Bootloader (HBOOT)
(might automatically do last step when you boot phone)
Phone will show a message to say it is looking for the file then unpack it and install.
Click to expand...
Click to collapse
Confirmed dude. Doesn't seem to be doing much though. It has been stuck on "updating BOOTLOADER". It has trying to update it for more then 30mins now
It has a big list of 12 things it wants to update however it hasn't moved past the first file "BOOTLOADER" in over 30mins.
Did you confirm the MD5HASH of the file before putting it on the card?
Could you put a link to where you got the file from please?
http://forum.xda-developers.com/showthread.php?t=905003
Thank you.
Are you still connected to the PC? If so disconnect and try again.
Did you confirm the MD5HASH?
Have you got another SD card you can try? If not, reformat the current one and put the PD98IMG file on it again and try again.
The Device fails to even turn on now dude. Thanks anyway man
!!!???!!!
Damn. Do you just get the orange flashing light when you try to turn the phone on?
Take out SD Card and try.
If nothing works the bright side is you can send it to HTC and say "I woke up, turned it on and it's dead". Chances are they'll never be able to tell how it happened.
Many people did this when the Clockwork recovery bug bricked loads of phones.
Sorry but stay positive. Always a sliver lining.
Thank you
thanks for your great guidance to get back to recovery. I followed your tips and made it.
thanks a lot once again.
SERGI.3210 said:
ooh i tested it in my DHD and don´t works...how can be possible that don´t works adb parameters, but fastboot commander works perfectly??
maybe we have anything that works badly in our PC´s.. i´m in it...
ei crystal!! has you tested with FASTBOOT COMMANDER? if you download it you can flash a new recovery from this tool... its intuitive...
you only must to download the tool
download the recovery (lastest CWM in the DHD android development forum)
put the file in the paragraph that says "RECOVERY:not file set" and then push FLASH IT"".maybe you enjoy...
remember to put your device into boot loader
Click to expand...
Click to collapse
I have a soft bricked GNex that goes into a bootloop of the "Google" splash logo. I can volume up + down + power and get it into the screen that gives options for recovery mode. However, when I click recovery mode, it takes me to a screen with a dead android with the red triangle sign on it. When I connect the phone to my PC, it is not even registering that a device was plugged in.
Are there any other methods or options I have to attempt to get the phone up and running?
1) thats stock recovery
2) if you want your pc to recognize it, just boot into fastboot and install the universal naked drivers.
Zepius said:
1) thats stock recovery
2) if you want your pc to recognize it, just boot into fastboot and install the universal naked drivers.
Click to expand...
Click to collapse
It's not that my PC doesn't recognize it because I don't have the drivers, I have another GNex and it plugs in just fine. My PC acts as if there was no device plugged in, there is no notification, no unknown device detected, nada. The owner claims there was water damage to the phone so maybe it's hardware bricked?
update: tried a different USB cable and got my PC to recognize the device. Using the toolkit to try and flash stock rom on there. Will keep updated if all goes well
toolkit goes through the whole stock rom flash process but phone is still doing bootloops. any other ideas?
Do it the right way. Follow the sticky on setting up adb and fast boot and put some hair on tour chest. Toolkits are terrible.
063_XOBX said:
Do it the right way. Follow the sticky on setting up adb and fast boot and put some hair on tour chest. Toolkits are terrible.
Click to expand...
Click to collapse
Ok, been following the instructions via this topic: http://forum.xda-developers.com/showthread.php?t=1529058
Have gotten all the way to the part where it's telling me to restart in recovery mode and that's when the dead android with the red warning triangle shows up. I also want to make note that I received the phone in this condition so I'm pretty sure the USB debugging mode has not been enabled.
Hey all. I'm in a bit of a pickle. My Tmobile LG g4 has stopped fast charging. When I plug in any cable, I do NOT get the USB notification which allows me to connect to my PC. Enabling the MTP option in the Dev options still does not allow the device to be connected to the PC to flash back to stock for warranty support.
Is there any way for me to save something to the SD card to reset back to stock? Do I have to connect it back to stock or at least relock the boot loader?
I've tried multiple PC's and multiple cables with no success to get the device connected. When connecting to a PC, I get. The device has malfuntioned on my machine.
ftblstr2319 said:
Hey all. I'm in a bit of a pickle. My Tmobile LG g4 has stopped fast charging. When I plug in any cable, I do NOT get the USB notification which allows me to connect to my PC. Enabling the MTP option in the Dev options still does not allow the device to be connected to the PC to flash back to stock for warranty support.
Is there any way for me to save something to the SD card to reset back to stock? Do I have to connect it back to stock or at least relock the boot loader?
I've tried multiple PC's and multiple cables with no success to get the device connected. When connecting to a PC, I get. The device has malfuntioned on my machine.
Click to expand...
Click to collapse
does it go into download mode.? phone off vol up key and connect usb.?
if you want to remove unlocked bootloader follow this comands
UPDATE:
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Unfortunately, the computer will NOT detect the phone. No computer will. Using a USB cable that came with it , no luck either. Any ideas?
raptorddd said:
does it go into download mode.? phone off vol up key and connect usb.?
if you want to remove unlocked bootloader follow this comands
UPDATE:
I was able to Lock the bootloader.
1. I connected the phone to my PC
2. Powered on the Phone (it took a few tried of pulling the battery and powering on)
3. Check the box for OEM Unlock in Dev. Option
4. Use Minimal ADB and Fastboot and type in
Quote:
adb devicecs
- you should see the phone listed as one of the devices in the command line window
Quote:
adb reboot bootloader
- phone should reboot and you shouold see 3 lines of text on top
Quote:
fastboot oem lock
- nothing will happen on the phone, but on in the commandline it should say that it is done
Quote:
fastboot reboot
Phone reboots and the boot screen does not show the unlocked bootloader message anymore
Click to expand...
Click to collapse
ftblstr2319 said:
Unfortunately, the computer will NOT detect the phone. No computer will. Using a USB cable that came with it , no luck either. Any ideas?
Click to expand...
Click to collapse
so basically theres no comunication with phone. not really. unless you go and exhcnage it to tmobile, so you cant remove bootloader unlocked message either. if you lucky and tmobile doesnt check for it then you may be able to get it exchanged. as it not recognized in any computer ill say its hardware problem. good luck.
Hi,
I'm after some advice, how do I place the Moto G5 in Qualcomm mode or EDL mode.
I have entered the bootloader by holding down and turning the phone on, this allows me to use fastboot.
From there I can scroll down to QCOM, but when I press the power button it boots into the normal system instead of EDL mode.
I have also attempted from within fastboot to use:
fastboot oem edl
fastboot oem qcom-on
fastboot reboot emergency
and
fastboot reboot-edl
Although non of these have been sucessful.
I also have access to an EDL cable, although, when I plug the phone in, then flick the switch 10 seconds later, it does not enter EDL mode, it just charges.
The phone sometimes shows as File Storage Linux USB Gadget in device manager, although it is inaccessible, I have updated the laptop to use the qualcomm drivers, although I don't think it will ever recognise it if I can't put the phone into qualcomm mode to begin with.
Any help would be much appreciated.
What are you actually attempting to do?
This mode is generally used to unbrick a device but you have access to the bootloader/fastboot mode and you wouldn't use edl mode to unbrick this device anyway
It's also used on some device to unlock the bootloader but again you wouldn't do that with this device
So without knowing what you are trying to achieve I can't give you any advice
Technically if you start the phone normally then enable usb debugging in dev options then connect phone to PC and in a terminal window where you have adb set up type
adb reboot edl
Not all devices support this mode though and I've no idea if this one does
TheFixItMan said:
What are you actually attempting to do?
This mode is generally used to unbrick a device but you have access to the bootloader/fastboot mode and you wouldn't use edl mode to unbrick this device anyway
It's also used on some device to unlock the bootloader but again you wouldn't do that with this device
So without knowing what you are trying to achieve I can't give you any advice
Technically if you start the phone normally then enable usb debugging in dev options then connect phone to PC and in a terminal window where you have adb set up type
adb reboot edl
Not all devices support this mode though and I've no idea if this one does
Click to expand...
Click to collapse
Without going into too much detail as to why, there are tools I have access to which can be used to take a full back up of the entire memory block of the phone when it is in Qualcomm mode.
I cannot access adb on the device to use "adb reboot edl" so I am limited to either trying to activate Qualcomm using a button combination or via fastboot, unless you can advise another way.
Any help or a point in the right direction would be much appreciated.
jameswstubbs said:
Without going into too much detail as to why, there are tools I have access to which can be used to take a full back up of the entire memory block of the phone when it is in Qualcomm mode.
I cannot access adb on the device to use "adb reboot edl" so I am limited to either trying to activate Qualcomm using a button combination or via fastboot, unless you can advise another way.
Any help or a point in the right direction would be much appreciated.
Click to expand...
Click to collapse
Sounds dodgy to me - sounds like you're trying to access data from a phone that isn't yours so I won't be helping
TheFixItMan said:
Sounds dodgy to me - sounds like your trying to access data from a phone that isn't yours so I won't be helping
Click to expand...
Click to collapse
It's not dodgy, but I fully understand.
Thank you anyway.
try fastboot -i 0x2b4c oem reboot-edl (it's working for LENOVO ZUK Z1 and ZUK Z2)
You can try (if you can/have the TWRP image) to flash TWRP and in reboot options select EDL.
In case the bootloader isn't unlocked you can also use fastboot boot [TWRP image name] to boot directly into TWRP without flashing and then repeat, go into reboot options and select edl.
Not sure if it works for you, if it does let me know that I have helped!
TheFixItMan said:
Sounds dodgy to me - sounds like you're trying to access data from a phone that isn't yours so I won't be helping
Click to expand...
Click to collapse
I need help too. So, I own a Moto G5s plus sanders. I unlocked its bootloader the day I got it. Didn't keep any backup and rooted it. I Also installed dot os based on android 11. But my 4G Volte connection was finicky. So, I decided to use a Volte zip patch. But, anyways I flashed the zip via TWRP and tried to reboot. But the phone didn't turn on after that. After a few minutes to my shock I understood that I hardbricked my mobile. No button combos, nothing worked. Anyways in my desperation I found a YouTube video showing the use of blankflash to revive a phone and lo and behold I used the procedure to again restore my device. It booted to the fastboot interface. But my happiness was short lived. My baseband was unknown at this point and the bootloader was I dunno downgraded to 0.5 inplace of 2.12. But, more importantly the unlock status was lost. I unlocked it again and all went well. I could even flashed TWRP. but then I realised I couldn't upgrade my bootloader. I couldn’t do anything. It's always gives a "security downgrade", "preflash validation failed" and "permission denied" error. I even tried RSA official rescue tool from Lenovo but even it was unsuccessful. It was never unsuccessful before that. Not even with a unlocked bootloader. I researched for days and tried custom ROMs. I flashed stock images. Nothing brought back my baseband and IMEI. When I type "fastboot oem unlock critical" it gives me permission denied error with a message. "Need OEM signed bootloader." I think the blankflash bootloader is the root of all evil. I need to change it and therefore I need to enter the edl mode. I have tried all adb commands and fastboot commands. The phone reboots okay after those commands but never goes into edl mode whatsoever. I am also ready to do a controlled hardbrick of my device to go into the edl mode so that I can use my device again with a proper bootloader and a properly working fastboot. Please help
So, I flashed Derpfest A12 ROM, It boots fine but gets stuck on "getting your Android 12 Ready" screen with the animation. I can access wifi and visiblity options but not settings. I flashed TWRP from the official website to install the recovery. But now when I reboot and press Volume Down, TWRP is stuck on boot animation. So I thought just reset using fastboot and start again and pressed volume up and power button but it does NOT work. I tried the volume buttons again in the rom [i can change volume in the starting screen] and they are working. I can press volume down and power button to reboot into recovery and it works fine but gets stuck. So, I just want to have access to adb or fastboot to reset this phone but neither seems possible. I Cant enable advanced reboot in the starting screen. Fastboot doesnt work. ADB not recognizing as it is a new rom and havent enabled it [i enabled in the previous rom]. Thanks for you Help in Advance!
P.S. I have tinkered POCO F1 fairly so I am not totally new to this scene!
EDIT: Thanks for all the replies! But I solved the problem, Idk how but i got access to fastboot mode after some tries and reflashed everything and now it works, also I use linux and the adb drivers and fastboot were in repos so it was easy.
hello,
I am a novice and use a translation tool to write to you (sorry if there are errors...).
Ok I already installed roms (but a long time ago on a OnePlus One...
I have an OP5T, I want to install lineage Os 19.1 on it.
I followed the tutorial on the lineage wiki.
I installed ADB and fastboot well, as well as universal adb driver.
I'm on windows 11, it works.
I enabled debug mode
The adb reboot bootloader command works, so the tel is well seen by the pc and the tel restarts in fastboot mode.
Then nothing, no command (oem unlock) works, the computer does not seem to see such after restarting in fastboot mode.
I read some topic on the net that say that the phone must be in "battery charging" mode and not "file transfer". Me to be visible by adb I have to put it in file transfer mode, otherwise it is not seen.
If I put in recharge mode, same thing to do.
Do you have a tip or should I give up?
ezivoco_163 said:
The adb reboot bootloader command works, so the tel is well seen by the pc and the tel restarts in fastboot mode.
Then nothing, no command (oem unlock) works, the computer does not seem to see such after restarting in fastboot mode.
I read some topic on the net that say that the phone must be in "battery charging" mode and not "file transfer". Me to be visible by adb I have to put it in file transfer mode, otherwise it is not seen.
If I put in recharge mode, same thing to do.
Do you have a tip or should I give up?
Click to expand...
Click to collapse
You need to install not just the adb drivers, but the fastboot ones as well, see this guide for example. This driver is the one needed for fastboot.
My devices have always been in file transfer mode btw, I've never heard of it needing to be in charging mode only.
No, you don't have to be in "charging only" vs "data transfer".
Still, those of us who distain to be plebian keep our devices in "charging only" (with ADB on) as MTP is beneath our contempt.
(Actually, the problem is that the USB VID/PID sometimes changes with each mode and that you may not have a driver loaded for ADB only.)
Nimueh said:
You need to install not just the adb drivers, but the fastboot ones as well, see this guide for example. This driver is the one needed for fastboot.
My devices have always been in file transfer mode btw, I've never heard of it needing to be in charging mode only.
Click to expand...
Click to collapse
Renate said:
No, you don't have to be in "charging only" vs "data transfer".
Still, those of us who distain to be plebian keep our devices in "charging only" (with ADB on) as MTP is beneath our contempt.
(Actually, the problem is that the USB VID/PID sometimes changes with each mode and that you may not have a driver loaded for ADB only.)
Click to expand...
Click to collapse
ok thanks, i a going to try this