OEM unlocking and USB Debugging enabled.
ADB never finds the phone in my windows 10 install no matter what drivers I force it to use. - Tried USB 2 and 3.
Fastboot does find it if I manually start it in fastboot mode, but it can't do anything to it
Fails to write when doing oem unlock
Just sits there if I tell it to write the recovery image.
Phone functions fine, I just want root and a 3rd party rom to be rid of any built in spyware.
Any ideas? any way to root it without flashing then I can just have the twrp app flash it?
Nevermind, found a way around it. This dialpad command made it work
Personmans said:
Hope this will help someone with trouble getting ADB/Fastboot to work. I assume you have a similar environment to me: Windows 10, with working ADB drivers on another device (LG G4 in my case)
Set up LeMax2 in developer mode and enable USB debugging as usual.
Plug in usb and dial *#*#76937#*#* check the box that says "Enable AT Port"
The device should immediately give you the approval message for USB debugging.
Note: This will not stick after a reboot.
Once I had this working, I did an adb reboot recovery, but fastboot still did not work. With the device connected and at the stock recovery screen, I had to open device manager, delete the LeMax device, and allow it to detect again. Finally it appeared in fastboot devices and I was able to flash recovery.
Click to expand...
Click to collapse
Related
Hey guys , anyone have a way to enable usb debugging via fastboot ?
Flashing something may do it ?
Leonardo_f said:
Hey guys , anyone have a way to enable usb debugging via fastboot ?
Flashing something may do it ?
Click to expand...
Click to collapse
i also need to find out because i cant even get into my phone due to bootloop issues...i bought my HTC MyTouch 4G from someone & been trying to fix my bootloop, every forum says to make sure "usb debugging" is enabled but i have no idea if it is or if it isnt
also when i use "adb devices" in cmd nothing shows up under list of devices...i just hope there is a command in adb or fastboot to enable/disable usb debugging
GarciaGotti said:
i also need to find out because i cant even get into my phone due to bootloop issues...i bought my HTC MyTouch 4G from someone & been trying to fix my bootloop, every forum says to make sure "usb debugging" is enabled but i have no idea if it is or if it isnt
also when i use "adb devices" in cmd nothing shows up under list of devices...i just hope there is a command in adb or fastboot to enable/disable usb debugging
Click to expand...
Click to collapse
I don't know whether you can enable USB debugging through fastboot ... i'll leave that to the experts.
However you can see your devices when connected to a PC in fastboot mode!
just run ...
fastboot devices
khajoor said:
However you can see your devices when connected to a PC in fastboot mode!
just run ...
fastboot devices
Click to expand...
Click to collapse
yeah i got that part, but when i try to flash or write anything to the device using fastboot i get nothing but errors so im guessing usb debugging must not be enabled
I'm sorry to say, you cannot enable USB Debugging through fastboot.
Hit the thanks button if i helped answer your question
Those errors have nothing to do with USB debugging. Your bootloader might not be unlocked so the flashing commands aren't working, or you're using wrong commands. USB debugging is at the ROM level and is for enabling adb while booted into the ROM. At the bootloader level, only fastboot commands work if the bootloader is unlocked. adb does not work. You need a custom recovery like CWM/TWRP for adb to work, and this recovery has to be flashed via 'fastboot flash recovery <recovery name>.img' on an unlocked bootloader.
Sent from my Nexus 7 using xda premium
Hello,
I'm also interested on this topic. My screen is broken, but the phone is working. I can boot and I feel the phone working and recognising my finger to unlock. However, because I'm stupid and I didn't have the "USB debugging ON" I can't access my files via ADB or any recovery software.
However, I can boot on fastboot and I see my device on "fastboot devides". Can I do something to access my files from there? I don't know... maybe unlock bootloader and flash any kind of TRWP with full adb or something like that.
THanks ¡
lotuxete said:
Hello,
I'm also interested on this topic. My screen is broken, but the phone is working. I can boot and I feel the phone working and recognising my finger to unlock. However, because I'm stupid and I didn't have the "USB debugging ON" I can't access my files via ADB or any recovery software.
However, I can boot on fastboot and I see my device on "fastboot devides". Can I do something to access my files from there? I don't know... maybe unlock bootloader and flash any kind of TRWP with full adb or something like that.
THanks ¡
Click to expand...
Click to collapse
As its name implies, Fastboot operates on device's bootloader and not on device's Android files as ADB does.
BTW: You always can access the user-data stored in Android's file system if USB-MTP mode got enabled on Android device.
jwoegerbauer said:
As its name implies, Fastboot operates on device's bootloader and not on device's Android files as ADB does.
BTW: You always can access the user-data stored in Android's file system if USB-MTP mode got enabled on Android device.
Click to expand...
Click to collapse
True, I can see my Xiaomi on "Windows Explorer", but it's an empty folder because I can't select MTP mode instead of "only charge" mode that it's launched by default.
What if I flash a TWRP recovery (I'll need to open bootloader first) and then from TRWP I try adb?
It must be a solution... if profesional people can do it so we do.
Thanks.
I bricked my opx I was able to bring it to life but the ****ty recovery doesn't let me flash anything so I am stuck no OS and boot loader locked and my computer isn't recognizing the dam thing I have installed SDK tools and google USB drivers but for some reason I am not able to get the Dan thing to connect right when I try via adb sideload it starts then the phone says fail...... Please help I am love this device and brand but I am getting really mad I am about a week in to trying to fix this but no luck I am using windows 10 also
We can try to unlock the bootloader as it is now, but that doesn't usually work unless you checked "OEM Bootloader Unlock" in the system settings before the device was bricked. Hindsight is 20/20 but as a word of advice for the future, never ever mess with a device unless you know the bootloader is unlocked or have made it possible to unlock it later without the OS. It also doesn't void the warranty on OnePlus devices to do so.
So first things first, the recovery will normally only flash the stock ROM as provided by OnePlus. You can download that file from here: http://downloads.oneplus.net/2016-04-02/opx/OnePlus_X_OxygenOS_2.2.1/. For future reference, when the bootloader on a device is locked the bootloader will not boot any software that isn't complete stock. If you try and change the OS or Recovery and it's not stock, the bootloader will not load it. This goes for any Android device.
If ADB sideload is working for you but hasn't been installing on the device (as-in, it sends the file but the device fails to install it) then you should be able to just sideload the zip file. It'll be slow though since it's about 780megs. If it doesn't send it then you can try using the ADB "push" command which is like copy and paste. You "push" the file from your computer to a folder on the device (you can see what folders are available using "adb shell" and then navigating with CD "change directory" and LS "list". If you can't find the sdcard you may have to mount it). Once again, it'll push slowly but once it does you should be able to install it from the internal memory.
If that works and it boots, go to Settings -> About Phone and tap the Build Number until it says you've enabled developer settings. Go to Settings -> Development and turn on "OEM Unlocking". Power the phone down. Hold the Power key and Volume Down until it shows the OnePlus logo and "Fastboot". I believe if you have the Android SDK you have the Fastboot program (it's commandline like ADB). Open CMD or Powershell and as long as it's the only device plugged into the computer you should be able to simply type "Fastboot oem unlock" and it will unlock the bootloader. Once again, it doesn't void your warranty.
I'm trying to flash TWRP, i've got ADB and i've got the Universal ADB Drivers. The device is properly detected when in EUI and my Device ID is displayed correctly when I type 'adb devices', however when I reboot into fastboot and type 'fastboot devices', nothing is listed and cannot continue.
Which drivers do I use? What is it that I need to continue?
Thanks!
Edit: Nevermind, connected it into my linux machine and got it to work easier (lol winBLOWS amirite) and finally got it to recognize the device in fastboot mode. I kept rebooting and failing to get into TWRP. I found somewhere else that before doing 'fastboot reboot' that you should hold VOL UP so you can immediately boot into twrp and make it permanent, which ended up working for me. Freedom!
ItsJono said:
I'm trying to flash TWRP, i've got ADB and i've got the Universal ADB Drivers. The device is properly detected when in EUI and my Device ID is displayed correctly when I type 'adb devices', however when I reboot into fastboot and type 'fastboot devices', nothing is listed and cannot continue.
Which drivers do I use? What is it that I need to continue?
Thanks!
Edit: Nevermind, connected it into my linux machine and got it to work easier (lol winBLOWS amirite) and finally got it to recognize the device in fastboot mode. I kept rebooting and failing to get into TWRP. I found somewhere else that before doing 'fastboot reboot' that you should hold VOL UP so you can immediately boot into twrp and make it permanent, which ended up working for me. Freedom!
Click to expand...
Click to collapse
I believe you need to configure in the developers options that you don't want to have the recovery overwritten on reboot. What also seems to work is to boot into the TWRP from the command line via 'fastboot boot <recovery-file-name>'
I have the exact same problem. I have installed all drivers and adb, but as soon as i am into fastboot and my device doesnt show up in the command line. If i want to install the recovery the command line just says <waiting for device> and nothing happend.
I already enabled the "Enable AT Port" Settings (http://forum.le.com/in/index.php?threads/le-max-2-x820-qpst-not-working.14820/) but i think this is not permanent turned on on my phone, because i have to repeat this step after every reboot.
Anybody got some tips?
Edit: Also booting directly into TWRP doesnt work, 'fastboot boot <recovery-file-name>' just ends up in <waiting for device>..
If you're using Win 8 or Win 10 you should turn off the driver singing verification before installing usb drivers for device.
In your case one of the drivers was blocked from installing and the systom does not see the device after it switches in fastboot/recovery mode.
I am not allowed to post urls, so google this: How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
RovnyiK said:
If you're using Win 8 or Win 10 you should turn off the driver singing verification before installing usb drivers for device.
In your case one of the drivers was blocked from installing and the systom does not see the device after it switches in fastboot/recovery mode.
I am not allowed to post urls, so google this: How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
Click to expand...
Click to collapse
Thanks for this Hint! Didnt know this
Nevertheless, no improvement so far. I Unistalled every driver and installed them again, but the PC doesnt recognize the phone when its in fastboot mode
Kampfgans said:
Thanks for this Hint! Didnt know this
Nevertheless, no improvement so far. I Unistalled every driver and installed them again, but the PC doesnt recognize the phone when its in fastboot mode
Click to expand...
Click to collapse
There is a chance, that your computer has installed the WRONG driver for the fastboot mode, so find any related to the phone entries in Device Manager when the phone is connected in fastboot mode, and if it is not "Android Phone/Android ADB Interface" -> remove them with remove driver checkbox checked. Optionally, if nothing changes -> try to manually pick the device driver to Android ADB Interface
RovnyiK said:
There is a chance, that your computer has installed the WRONG driver for the fastboot mode, so find any related to the phone entries in Device Manager when the phone is connected in fastboot mode, and if it is not "Android Phone/Android ADB Interface" -> remove them with remove driver checkbox checked. Optionally, if nothing changes -> try to manually pick the device driver to Android ADB Interface
Click to expand...
Click to collapse
I tried it now with the fifth computer and after a few strange error messages, it "succesfully" installed TWRP.
BUT: There is no TWRP installed on my phone. I followed every tip which i found how to exit the fastboot mode (pressing Vol+ & Power / Removing USB Cable / Tried TeamSpains Automatic Installer).
What is wrong with this phone ? - I think i will oben a new thread, thanks for your help!
Kampfgans said:
I tried it now with the fifth computer and after a few strange error messages, it "succesfully" installed TWRP.
BUT: There is no TWRP installed on my phone. I followed every tip which i found how to exit the fastboot mode (pressing Vol+ & Power / Removing USB Cable / Tried TeamSpains Automatic Installer).
What is wrong with this phone ? - I think i will oben a new thread, thanks for your help!
Click to expand...
Click to collapse
Kampfgans: Klingt irgendwo zwischen lustig und richtig bedrohlich...
Lots of ROMs (including most CM variants) like to "automatically 'recover'" recoveries, that is they overwrite the recovery partition with a copy of the "original" every time you reboot.
I seem to remember that my first attempt to overwrite the stock recovery using "fastboot flash recovery <twrp-image-name>" also didn't succeed in making TWRP "stick".
Within the CM13 which I installed next (over the stock v15) there is a developer option to control that, but in this case I simply used a trick, which seems to bypass the recovery overwrite: I told the phone to boot the TWRP recovery over USB after flashing.
It went like this:
fastboot flash recovery <name-and-path-of-TWRP-recovery> //puts the TWRP image on the recovery partition
fastboot boot <name-and-path-of-TWRP-recovery> //bypasses the recovery overwrite logic of either the bootloader or whereever it hides
That booted TWRP over USB and allowed me to install CM13.
There I disabled recovery overwrite in the deveoper's options and I've never had issues with TWRP disappearing since.
Actually you should in theory be able to leave the stock recovery in place and still use TWRP by booting it over USB on the fastboot command line.
I install drivers and USB but when trying to go to fast boot I receive "waiting for device"
My K7 is T-Mobile LG-K330, Android 5.1.1, kernel 3.10.49, Build LMY47V, vers K33010j
I have searched and tried many root guides. All end the same way. This isn't new for me as I have rooted and installed mod roms on several phones and a tablet.
The main problem seems to the phone will not show as connected to the root tools. I have triple checked the developer mode ena and usb debugging ena and tried OEM unlock both ways.
I have the latest (as of today from XDA, minadb and kingroot (PC)). Both are installed on my Win10Pro comp.
The phone USB drivers must be in place as I can plug in the usb and the K7 comes up in the This PC list and I have access to the folders. I must be missing something.
adb devices -l
daemon starts but no devices are listed
fastboot devices
none listed
kingroot
all is well up to the point where it tries to "connect" it just fiddles in circles
I waited 15 min and Xed out.
This may be related: I cannot boot to the recovery screen. No matter how I hold the power and up volume I always get the T-Mobile screen and android.
Has anyone seen this or have any suggestions?
Happy Trails
I had similar problems with my K7.
I had to download a different minimal ADB / Fastboot tool from http://forum.frandroid.com/topic/246460-root-and-recovery/ .
Once the bootloader was rebooted the phone had on-screen instructions.
Use this https://forum.xda-developers.com/lg-k7/how-to/t-mobile-lg-k7-thread-t3481844 and the site above for instruction.
Put your recovery twrp-image-3.img and the SuperSU.zip on a micro sd and insert it in your phone before you start.
Also put the twrp-image-3.img in the ADB program folder on your computer.
Once the bootloader is unlocked, instead of typing: fastboot flash recovery twrp-image-3.img .
Type: fastboot boot recovery twrp-image-3.img or fastboot boot twrp-image-3.img (I don't remember) (only one will work).
Then once in twrp install the recovery ( twrp-image-3.img ) and then the SuperSU.zip from the SD card.
Also make sure you check the box and allow your computer permission to connect to your phone when you first connect them, after you enable usb debugging on you phone.
Good Luck.
I have Samsung Galaxy Tab S2 that I attempted to root earlier today. I used Odin and CF auto root method. Everything appeared to go fine, until it restarted itself after it was done. When it booted back up, the WiFi was not working. When I turn it on, it is simply stuck on "Turning on...." and nothing happens.
Problem 2: When I connect the tablet to a computer via USB cable, it does not recognize it. I'll hear a chime, so it detects it, but it does not show up in the file explorer. The tablet is set for a MTP USB configuration.
I tried a factory reset, but that did nothing.
I'm not sure what to do now. I do have a micro SD card, so I'm able to move it back and forth from the tablet to my PC to install APKs and other files. I'd like to try flashing a custom ROM to see if that fixes it, but now I'm not rooted. I used the SD card to install a couple of the one click root apps, but they were either unsuccessful, or require an internet connection to use.
I don't know if it's possible to actually install a custom ROM on a device that doesn't have internet access and can't use a USB cable.
If anyone has suggestions as to either of my problems, I'd love to hear it, because as of now I can't do anything with my tablet.
You can try to:
wipe data/cache from recovery and reboot it again to see if the wifi error still exists, or you can flash it again.
You can get and use adb/fastboot, if you haven't already, and check if fastboot (execute fastboot devices in cmd) recognizes your device after the chime sound. If you're lucky and your device is displayed, you can flash it again. All the best!
daphr said:
You can try to:
wipe data/cache from recovery and reboot it again to see if the wifi error still exists, or you can flash it again.
You can get and use adb/fastboot, if you haven't already, and check if fastboot (execute fastboot devices in cmd) recognizes your device after the chime sound. If you're lucky and your device is displayed, you can flash it again. All the best!
Click to expand...
Click to collapse
Thanks. Executing "fastboot devices" returns an empty list, however "ADB devices" returns some sort of serial number with "offline" next to it.
edit: I've been running adb kill-server and adb-start server commands, followed by adb devices, and that will switch the device status from "offline" to "unauthorized". I'm not sure how to fix that. I navigated to my .android folder on my PC and deleted the adbkey file but that didn't help.
In developer settings Enable USB debugging, revoke current USB debug authorizations and allow your PC's fingerprint. You can also enable OEM unlock in case you plan to play with the bootloader and custom ROMs.
Next in cmd after plugging the device in, check if it gets detected: adb devices
If you get the list you've mentioned, execute: adb reboot bootloader
This should boot your device into the fastboot mode where you have full access to your phone, so be careful what you're doing.
If you need more info on fastboot and adb, check out the forums.
Good luck!
daphr said:
In developer settings Enable USB debugging, revoke current USB debug authorizations and allow your PC's fingerprint. You can also enable OEM unlock in case you plan to play with the bootloader and custom ROMs.
Next in cmd after plugging the device in, check if it gets detected: adb devices
If you get the list you've mentioned, execute: adb reboot bootloader
This should boot your device into the fastboot mode where you have full access to your phone, so be careful what you're doing.
If you need more info on fastboot and adb, check out the forums.
Good luck!
Click to expand...
Click to collapse
Unfortunately it's still showing the device as "unauthorized". I've toggled developer options and USB debugging on and, and repeatedly tried "Revoke USB debugging authorizations" but it hasn't help. I can't execute the adb reboot bootloader command while it's unauthorized.
febtober said:
Unfortunately it's still showing the device as "unauthorized". I've toggled developer options and USB debugging on and, and repeatedly tried "Revoke USB debugging authorizations" but it hasn't help. I can't execute the adb reboot bootloader command while it's unauthorized.
Click to expand...
Click to collapse
Have you been asked for a new computer ID to accept after revoking old ones and plugging the device in again?
As long as you don't add new fingerprint of your computer to the device, your device will be unauthorized.
febtober said:
Unfortunately it's still showing the device as "unauthorized". I've toggled developer options and USB debugging on and, and repeatedly tried "Revoke USB debugging authorizations" but it hasn't help. I can't execute the adb reboot bootloader command while it's unauthorized.
Click to expand...
Click to collapse
You need to restock your tablet via odin (to put modem back aka Wifi)
After you restock Install Twrp and install magisk to root, instead of cf-root like you did (this will not breaking the safety net or knox even the modem)
(Note:before install magisk backup your "BOOT" via TWRP)