Related
I have finally been able to unlock my TF300T!!!!! But now I'm trying install TWRP or CWM so I can root and I'm having a few problems...
I've been trying this guide ( http://forum.xda-developers.com/showthread.php?t=1845377 ) and I'm stuck on Part 3 step 3.
The command prompt is reading :
C:\tf300tsoftware>adb reboot bootloader
error: device not found
Then when I just plug in the tablet I can transfer any files from my pc to the table, but it will not read anything on the command prompt. Any help would be great. I've re-installed the drivers, and re-installed all of the software many times but I'm just at a loss.
Thanks again.
bwillie said:
C:\tf300tsoftware>adb reboot bootloader
error: device not found
Then when I just plug in the tablet [...]
Thanks again.
Click to expand...
Click to collapse
This sounds like you are trying to run adb, before plugging in your tablet?
Using adb generally requires your tablet to be plugged into the USB port of your PC.
Anyhow, another way to get into the boot loader is to hold the volume-down key, while switching on the tablet.
Hope that helps.
Sent from my TF300T using XDA Premium HD app
bwillie said:
I have finally been able to unlock my TF300T!!!!! But now I'm trying install TWRP or CWM so I can root and I'm having a few problems...
I've been trying this guide ( http://forum.xda-developers.com/showthread.php?t=1845377 ) and I'm stuck on Part 3 step 3.
The command prompt is reading :
C:\tf300tsoftware>adb reboot bootloader
error: device not found
Then when I just plug in the tablet I can transfer any files from my pc to the table, but it will not read anything on the command prompt. Any help would be great. I've re-installed the drivers, and re-installed all of the software many times but I'm just at a loss.
Thanks again.
Click to expand...
Click to collapse
Need to know if you have the proper device drivers. You can transfer files from PC to tablet because that uses different drivers.
What happens when you type 'fastboot devices'?
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
bwillie said:
I have finally been able to unlock my TF300T!!!!! But now I'm trying install TWRP or CWM so I can root and I'm having a few problems...
I've been trying this guide ( http://forum.xda-developers.com/showthread.php?t=1845377 ) and I'm stuck on Part 3 step 3.
The command prompt is reading :
C:\tf300tsoftware>adb reboot bootloader
error: device not found
Then when I just plug in the tablet I can transfer any files from my pc to the table, but it will not read anything on the command prompt. Any help would be great. I've re-installed the drivers, and re-installed all of the software many times but I'm just at a loss.
Thanks again.
Click to expand...
Click to collapse
You can accomplish part 3 step 3 without adb. Power tablet off. Power on by holding power and down volume till you see the bootloader menu, release both power button and down volume. Now continue with part 3 step 4.
Good Luck!
xxboarderxx said:
Need to know if you have the proper device drivers. You can transfer files from PC to tablet because that uses different drivers.
What happens when you type 'fastboot devices'?
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
I am having the same problem. I connect the tablet and it seems to connect fine (MTP) but adb doesn't see it. When I enter the command above it just returns the next line with no results.
I loaded the Asus sync from their website which doesn't seem to have made much difference either.
MG
moregadget said:
I am having the same problem. I connect the tablet and it seems to connect fine (MTP) but adb doesn't see it. When I enter the command above it just returns the next line with no results.
I loaded the Asus sync from their website which doesn't seem to have made much difference either.
MG
Click to expand...
Click to collapse
Got USB debugging turned on?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Hi All,
It has been a time that I unlocked my TF700t then followed the CM10 documentation to install 10.0 using CWM.
Recently I wanted to upgrade to 10.1 but it didn't work and ended with my tablet rebooting undefinitely.
I reverted then to install back the ASUS stock Rom from their website :
- I downloaded the file
- unzipped it (since it contains another zip)
- put it on a micro SD
- Booted into CWM
- installed the zip
I ended with a working tablet on the stock rom JB 4.1 but know I wanted to try again CM but I cannot access recovery anymore. I can access the bootloader but when I select RCK I get the droid laying on his back with the warning sign.
I thought I would need to flash another recovery (TWRP or other) using fastboot but now when I plug the tablet to my PC it keeps telling me that the device is not recognized. I tried to install the USB driver but it doesn't get detected.
Can anyone please help ? The tablet is working but I am afraid that it has lost some of its capabilities.
Thanks
Nacef
nacef_l said:
Hi All,
It has been a time that I unlocked my TF700t then followed the CM10 documentation to install 10.0 using CWM.
Recently I wanted to upgrade to 10.1 but it didn't work and ended with my tablet rebooting undefinitely.
I reverted then to install back the ASUS stock Rom from their website :
- I downloaded the file
- unzipped it (since it contains another zip)
- put it on a micro SD
- Booted into CWM
- installed the zip
I ended with a working tablet on the stock rom JB 4.1 but know I wanted to try again CM but I cannot access recovery anymore. I can access the bootloader but when I select RCK I get the droid laying on his back with the warning sign.
I thought I would need to flash another recovery (TWRP or other) using fastboot but now when I plug the tablet to my PC it keeps telling me that the device is not recognized. I tried to install the USB driver but it doesn't get detected.
Can anyone please help ? The tablet is working but I am afraid that it has lost some of its capabilities.
Thanks
Nacef
Click to expand...
Click to collapse
Go to your system setting and select storage. Click the 3 dots in the upper right corner and tick the box which is Media device (MTP).. Good luck..
LetMeKnow said:
Go to your system setting and select storage. Click the 3 dots in the upper right corner and tick the box which is Media device (MTP).. Good luck..
Click to expand...
Click to collapse
I just tried that but it did not work, windows is still displaying USB device not recognized.
nacef_l said:
I just tried that but it did not work, windows is still displaying USB device not recognized.
Click to expand...
Click to collapse
What Windows version are you running?
You may have to uninstall the drivers for your MTP device before installing new ones as well as disabling Windows to automatically install drivers for a new device, then manually point it to the Universal Naked Drivers folder.
Or downlaod Android SDK tool ad through it the Platform Tools and USB drivers.
BTW: When you flashed the stock firmware you lost your custom recovery. That's why you see the dead Droid - it's the stock recovery.
If you can't get fastboot to work you can use Motochopper to root your JB 4.1 stock firmware and then GooManager to install the latest TWRP recovery.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
I have tested it on WinXP, Win7, Ubuntu and another box with Win XP. Always same thing the device is not recognized.
When I try to update the driver and point it manually to the naked drivers it cannot detect them.
I guess that even for running Motochopper I will need to get USB working to be able to root my device.
Any help please ? I am stuck with a sluggish stock mod that buries the perfs of my device.
nacef_l said:
I have tested it on WinXP, Win7, Ubuntu and another box with Win XP. Always same thing the device is not recognized.
When I try to update the driver and point it manually to the naked drivers it cannot detect them.
I guess that even for running Motochopper I will need to get USB working to be able to root my device.
Any help please ? I am stuck with a sluggish stock mod that buries the perfs of my device.
Click to expand...
Click to collapse
You do have USB debugging enabled in the Developer settings, do you?
Sent from my DROID4 using Tapatalk 2
berndblb said:
You do have USB debugging enabled in the Developer settings, do you?
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
Yes checked and double checked that
nacef_l said:
Yes checked and double checked that
Click to expand...
Click to collapse
Then it's a driver problem and it's solvable. What do you see in Device Manager under Portable Devices with your tablet connected? Did you uninstall the driver and re-install it?
Did you try to install Asus Sync (which should give you compatible drivers for the TF700)?
So many driver problems lately... there's got to be a pattern to it, but what it may be beats me :what:
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
Then it's a driver problem and it's solvable. What do you see in Device Manager under Portable Devices with your tablet connected? Did you uninstall the driver and re-install it?
Did you try to install Asus Sync (which should give you compatible drivers for the TF700)?
So many driver problems lately... there's got to be a pattern to it, but what it may be beats me :what:
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
In the Device Manager I have nothing under Portable Devices, but under USB devices it appears an Unrecognized USB Device and a bubble notifying about an unrecognized USB device keeps popping in the task bar. Even after installing ASUS Sync it is not detected.
nacef_l said:
In the Device Manager I have nothing under Portable Devices, but under USB devices it appears an Unrecognized USB Device and a bubble notifying about an unrecognized USB device keeps popping in the task bar. Even after installing ASUS Sync it is not detected.
Click to expand...
Click to collapse
You don't connect your tablet to the PC through the dock USB port, do you?? Just had that in another thread....
If you connect the tablet directly, I'm stumped. No idea why it's not recognized...
Sent from my DROID4 using Tapatalk 2
berndblb said:
You don't connect your tablet to the PC through the dock USB port, do you?? Just had that in another thread....
If you connect the tablet directly, I'm stumped. No idea why it's not recognized...
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
I don't have a dock and I am connecting directly with the cable. I have just reflashed it to stock rom again hoping it resolves itself but nothing.
It's driving me crazy. The stock rom is really sluggish and I want to flash it to CM
Sounds like a windows driver issue to me. You need to force windows to use the right usb drivers. You normally do this by upgrading thenm in device manager. You may have a borked windows installation to fix as well..
Try the ones I have attached.
sbdags said:
Sounds like a windows driver issue to me. You need to force windows to use the right usb drivers. You normally do this by upgrading thenm in device manager. You may have a borked windows installation to fix as well..
Try the ones I have attached.
Click to expand...
Click to collapse
I have tried different windows installations with the different drivers that you provided me, still nothing. It seems to me that the device is not even sending proper ids to the system. Can it be caused by a damaged cable ?
Sent from my iPhone using Tapatalk - now Free
Had the same problem.I fixed it by uninstalling the faulty usb device. Then disconnected the usb cable. Reconnected. And the drivers installed.
nacef_l said:
I have tried different windows installations with the different drivers that you provided me, still nothing. It seems to me that the device is not even sending proper ids to the system. Can it be caused by a damaged cable ?
Click to expand...
Click to collapse
Im having the same problem and after one day of research I could not find a solution. I bought a use TF700 with a standard andriod on it, no mod, not unlocked, no root. When I connect it to the pc I get the same error, meaning just a USB Device showing up. Tried different PC's with different types of OS, no success.
Did you manage to fix the problem ? I would really appreciate some help because now I can't use that tablet in debug mode to test my android applications and that's all I bought it for. By the way, is there a adb tool that works wireless and doesn't neet root access or can I get root access without connecting my pad to my pc ?
Thanks for the help !
Well did you install adb fastboot drivers on the PCs you tried? Did you try it under Linux? Do you have the original Asus cable you connect it with?
adb over network is an option under Developer Options in Omni and Omni based roms - at least the LP roms. I don't think you can get that with an app you install. Probably needs to be baked into the kernel.
berndblb said:
Well did you install adb fastboot drivers on the PCs you tried? Did you try it under Linux? Do you have the original Asus cable you connect it with?
adb over network is an option under Developer Options in Omni and Omni based roms - at least the LP roms. I don't think you can get that with an app you install. Probably needs to be baked into the kernel.
Click to expand...
Click to collapse
First of all thanks a lot for your response, didn't think anyone would still react on that post because it's quite old. Yes I did install adb fastboot drivers, the device only shows up in the usb section saying usb device not recognized. I tried nearly every driver I found, installed the Andriod SDK, the Asus Sync Tool, the naked drivers... then removed them all (including the hidden ones) and installed just the adb fastboot -> no success. I have not tried it on linux, but on windows 7, 8 and 10. Android version is 4.2.1 and Build is 10.6.1.14.10. I now unlocked it using the apk provided by asus (version 7 , 8 did not work). Still for rooting I need pc connection, so I ordered a new cable today (cable is original Asus though).
I installed the Rom Manager and that tells me the ClockworkMod Recovery and TWRP are already installed. I also tried that recovery (power + vol) and got the same result as nacef meaning " I can access the bootloader but when I select RCK I get the droid laying on his back with the warning sign." Thing is, I don't know what the previews owner did, so it might be the reason he sold the Tablet. Can I get anywhere form that Bootloader ? Maybe boot as a Superuser and then use wireless adb to root the device ?
Thanks a lot for your help, Im feeling that I have wasted the money and the only way to get rid of that feeling is to fix the problem
Grab the Puppy Linux live CD from here: http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
It has adb fastboot already installed. If you don't get a connection with that one the problem would be tablet side, not Windows related.
I booted using that Puppy Linux and followed the Guide but no success. After entering "adb devices" I get the output "list of adb devices attached" and than a blank space. So I tried booting in fastboot like you described in your guide and entered "fastboot devices" but that also gives me nothing. Fastboot works though (as it's already included in that image) so I tried a bunch of other fastboot commands but that just results in "waiting for the device".
I don't know what to do now, it has something to do with the tablet itself. Im waiting for the new cable but don't think thats gonna change anything.
You are not trying to do this through the dock port, right? You are connecting the tablet directly to the PC?
The only answer I have left is either a broken cable or one of the pins in the port is bent or broken. Get a magnifying glass and check them out.
Phone: Droid Razr HD XT926, locked bootloader, was rooted, not sure now
Issue: OTAs had not worked for awhile, but I wanted to go to KitKat. So, I tried to use Matt's 1.41 utility. I may not have had the most up-to-date Motorola USB drivers when I started. The update did not work. Now, I just get the "Motorola Logo and Dual Core Technology text", but phone then goes black. I am able to get to AP fastboot screen, but all attempts to re-try Matt's 1.41 utility, or the House of Moto 4.1, or RSD Lite 6.2.4 are unsuccessful. All of them show <waiting for device>.
Any ideas why I can't get past <waiting for device>?
Fastboot screen:
Device is LOCKED. Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Boot menu selected
Assuming you've updated the drivers at this point, are using the stock usb cord and following all the details in the op to a T? Might try another USB port...
grnsl2 said:
Assuming you've updated the drivers at this point, are using the stock usb cord and following all the details in the op to a T? Might try another USB port...
Click to expand...
Click to collapse
You are correct on those assumptions except the stock usb cord. The cord I am using was fine when I first started my adventure. USB debugging was on and plugging in the phone+cord caused PC to recognize the phone. But, now my PC does not even flinch when I plug the phone+cord into the USB port. Should the PC be flinching (recognizing the phone) when all are plugged in? If it is not, any recommended tricks to encourage PC and phone to play nice together?
I have tried two different ports. I will check documentation and verify they are 2.0. I will also see about finding a motorola OEM cable just to rule that out.
Thanks for the response!
Additional info:
- Motorola USB drivers I used (USB Driver.6.4.0.2014-10-24): [droidrzr website] /index.php/topic/57858-motorola-tools-rsd-lite-usb-driver/
I used to do a lot of flashing from various laptops to different phones with mixed results. Certainly strange when sometimes one works and the other does not. Hard to pinpoint why with so many variables. In your situation, working at one point then bam...
grnsl2 said:
I used to do a lot of flashing from various laptops to different phones with mixed results. Certainly strange when sometimes one works and the other does not. Hard to pinpoint why with so many variables. In your situation, working at one point then bam...
Click to expand...
Click to collapse
Update: Decided to give it another shot today. Went back to original cord (when I had success prior to bad flash). Booted to fastboot. Plugged into USB port. Today, my PC decided to try and recognize it! Windows failed once trying to find drivers for "Fastboot VANQUISH S". So, I decided to disconnect and try again. This time, drivers found! Fastboot screen changed to include the "usb connected" message below the "Fastboot Reason: Boot menu selected" message.
Using House Of Moto, I was able to successfully flash 4.4.2 183.46.10. Phone is charging up now in preparation for rooting and unlocking.
Good news there!
Warning: This will delete all your data. You'll also see a large warning every time you turn on the device (attached), this disappears in less than a second.
Turn on developer mode
Turn on OEM unlock and USB debugging
Install LG drivers
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
Type adb devices and authorize your computer on the phone
Type adb reboot bootloader
Type fastboot devices and make sure your phone shows up
Type fastboot oem unlock
Type fastboot getvar all
Should say (bootloader) unlocked:yes
Type fastboot reboot
What's the purpose for an Unlock bootloader?
bhagiratha said:
What's the purpose for an Unlock bootloader?
Click to expand...
Click to collapse
It's the first step to rooting. If you plan to root, wiping your data now may be preferable.
bhagiratha said:
What's the purpose for an Unlock bootloader?
Click to expand...
Click to collapse
At this point, nothing. It's a prelude to rooting.
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
heldc said:
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
Click to expand...
Click to collapse
Try fastboot devices and reinserting the usb cable. Doesn't make sense that adb sees it but fastboot does not unless it's a different driver. I think fastboot driver differs actually so do that driver too.
Ubuntu
heldc said:
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
Click to expand...
Click to collapse
You can also load Ubuntu on a flash drive and boot your computer from the flash drive. Then run the commands.
https://www.ubuntu.com/
Cheers
heldc said:
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
Click to expand...
Click to collapse
First be on your c:\
Type in adb devices
If your phones serial comes up type in..
Adb reboot bootloader
Then
Fastboot oem unlock
ADB reboot bootloader boots straight into the OS on AT&T v20 :crying:
cordell12 said:
ADB reboot bootloader boots straight into the OS on AT&T v20 :crying:
Click to expand...
Click to collapse
Do you guys have the oem unlock option at least?
Also what helped me was downloading android studio with the sdk.. It installs android drivers which were necessary for me at least to get past the waiting for device message, windows located the drivers on my c drive and boom... Unlocked Bootloader.. Just saying
Sent from my LG-H918 using XDA-Developers mobile app
wing_addict_usa said:
Do you guys have the oem unlock option at least?
Click to expand...
Click to collapse
yup, even warns us that certain things won't work if we enable it. adb works just fine too
cordell12 said:
yup, even warns us that certain things won't work if we enable it. adb works just fine too
Click to expand...
Click to collapse
Yeah I am really curious if there may still be a way to unlock the bootloader with out AT&T variant. I wish I kept my phone on the Download Mode when I had gotten into it because I wanted to see if by any chance that might actually get fastboot to read the phone..
I'm curious if there's anyone with a T-Mobile variant that has their bootloader unlocked and wants to view their debug logs (specifically last_log/last_kmsg). As I was looking through mine and tried to boot into bootloader these lines were the only things I saw that might have interested me at all. I'm just curious on what the values are on their phone.
Code:
last_log
[ 0.711419] ro.boot.flash.locked=1
[ 0.711784] ro.bootloader=unknown
[ 0.711817] ro.oem_unlock_supported=1
last_kmsg
<6>[ 1.077087 / 01-01 00:00:01.069][3] [70] SW3800_Authentication [vendor code: 1]
<6>[ 1.077120 / 01-01 00:00:01.069][3] [110] set_dload_mode: download_mode:0
wing_addict_usa said:
It's the first step to rooting. If you plan to root, wiping your data now may be preferable.
Click to expand...
Click to collapse
It's quite possible the process of rooting will wipe the phone anyway.
twistedvip said:
Yeah I am really curious if there may still be a way to unlock the bootloader with out AT&T variant. I wish I kept my phone on the Download Mode when I had gotten into it because I wanted to see if by any chance that might actually get fastboot to read the phone..
I'm curious if there's anyone with a T-Mobile variant that has their bootloader unlocked and wants to view their debug logs (specifically last_log/last_kmsg). As I was looking through mine and tried to boot into bootloader these lines were the only things I saw that might have interested me at all. I'm just curious on what the values are on their phone.
Click to expand...
Click to collapse
power device off, hold volume up and keep it down and plug in USB cord while it's connected to PC. I tried fastboot from download mode though. the logs do look interesting, wonder what a T-MOBILE device says
Double0EK said:
First be on your c:\
Type in adb devices
If your phones serial comes up type in..
Adb reboot bootloader
Then
Fastboot oem unlock
Click to expand...
Click to collapse
Yup, I did that. And then I get an error. Well, not an error, just a lack of response. fastboot devices returns nothing. I'm currently downloading the full sdk, on the theory that perhaps it's a problem with the installation of 'minimal adb and fastboot' I have.
---------- Post added at 08:07 PM ---------- Previous post was at 07:36 PM ----------
manufan721 said:
Also what helped me was downloading android studio with the sdk.. It installs android drivers which were necessary for me at least to get past the waiting for device message, windows located the drivers on my c drive and boom... Unlocked Bootloader.. Just saying
Sent from my LG-H918 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you do anything specific after installing Android Studio to get it to install the drivers? Cos I've installed Android Studio, but am still having the same problem-fastboot devices returns nothing, and fastboot oem unlock hangs on <waiting for device>. I went into device manager and had it search the entire C: for drivers for the android bootloader interface, and it gave the same 'already up to date drivers' message as before I installed Android Studio.
EDIT- Even after installing the Google usb driver, no luck. Giving up for the weekend.
I'm a newbie, may I know have to fastboot from download mode?
having same issue just hangs at Fastboot oem unlock if anybody can help thanks in advance
twistedvip said:
Yeah I am really curious if there may still be a way to unlock the bootloader with out AT&T variant. I wish I kept my phone on the Download Mode when I had gotten into it because I wanted to see if by any chance that might actually get fastboot to read the phone..
I'm curious if there's anyone with a T-Mobile variant that has their bootloader unlocked and wants to view their debug logs (specifically last_log/last_kmsg). As I was looking through mine and tried to boot into bootloader these lines were the only things I saw that might have interested me at all. I'm just curious on what the values are on their phone.
Code:
last_log
[ 0.711419] ro.boot.flash.locked=1
[ 0.711784] ro.bootloader=unknown
[ 0.711817] ro.oem_unlock_supported=1
last_kmsg
<6>[ 1.077087 / 01-01 00:00:01.069][3] [70] SW3800_Authentication [vendor code: 1]
<6>[ 1.077120 / 01-01 00:00:01.069][3] [110] set_dload_mode: download_mode:0
Click to expand...
Click to collapse
[ 0.711817] ro.oem_unlock_supported=1 1=YES
did some digging into last_kmsg while trying to boot into bootloader (AT&T device) and found a reason it may not be allowing it.
http://forum.xda-developers.com/showthread.php?t=2708466
Its a start :good:
of course we need root in order to dd anything
LG issued a new driver update for the v20. Driver version is 4.1.1+. You can get the driver from the website.
Hi
My phone is international NXT-L29
I was on Ephemeral B180 rom but i decided to upgrade it to get emui 4.1
I flashed back stock b180 rom, and after I flashed stock b321 rom
ROM works great but i would like to get root and twrp back again, but everytime I try to go through fastboot i get this screen on picture.
I logged into my dc unlocker again and followed the procedures (manufacture mode, unlocking,...) and dc unloccker tool informs that the phone was unlocked...but no, when I do adb reboot bootloader i still get the same message on the picture.
I saw other suggestions here on XDA, i confirm oem unlock is activated on developer options...i made factory reset and then "vol+- power" (with or without phone connected to PC) but i dont't get any option to unlock bootloader. I always arrive to a menu saying that the phone is looking for upgrade and tries until 5% is reached... (if I keep waiting it does not fisplat error message, only waits and waits and after a while it reboots normally (i don't have any dload folder either on phone or sd card)
Any suggestion to solve this is highly appreciated
many thanks
Try to get ur unlock code from huawei website maybe this can help.
Did you run the bootloader unlock command with your unlock code again?
Ephemera said:
Did you run the bootloader unlock command with your unlock code again?
Click to expand...
Click to collapse
the only command my phone accept is adb reboot bootloader
Then i get the screen of picture that I posted, which says that it is a cold reboot (?)
Whem I reach this point it doens not respond to anything else taht I type on Command line (I type fastboot oem unlock (and the code) but on pc screen i read 'ewaiting device' and nothing happens on phone
gm007 said:
Try to get ur unlock code from huawei website maybe this can help.
Click to expand...
Click to collapse
I retrived my code from DC Unlocker (it has an option to read bootload code) but the problem is thar when I get de Fastboot&Rescue Mode the phone does not react to any command i can type on PC
Can I replace the stock boot.img that comes inside the UPDATE.APP file byone decrypted boot image of same rom?
If that would be possible then flashing this "modified" UPDATE.APP would solve the problem?
Many Thanks
pasil.pt said:
I retrived my code from DC Unlocker (it has an option to read bootload code) but the problem is thar when I get de Fastboot&Rescue Mode the phone does not react to any command i can type on PC
Click to expand...
Click to collapse
Hi pasil.pt,
try to update the fastboot mode driver
http://forum.xda-developers.com/showpost.php?p=69382774&postcount=202
grofock said:
Hi pasil.pt,
try to update the fastboot mode driver
http://forum.xda-developers.com/showpost.php?p=69382774&postcount=202
Click to expand...
Click to collapse
I don't see any kedacom usb device folder...
Check if the device isnfound by the computer. Restart in fastboot mode then on your computer type "fastboot devices" you should get a device and its serial. If you're not getting anything its a driver issue.
Ephemera said:
Check if the device isnfound by the computer. Restart in fastboot mode then on your computer type "fastboot devices" you should get a device and its serial. If you're not getting anything its a driver issue.
Click to expand...
Click to collapse
I did not try the command fastboot devices, but as per the new picture attached when I run adb devices the computer finds my phone
the problem is, then, when next i run 'adb reboot bootloader'...the device goes into fastboot&rescue mode and the device is not recognized by computer anymore
pasil.pt said:
I did not try the command fastboot devices, but as per the new picture attached when I run adb devices the computer finds my phone
the problem is, then, when next i run 'adb reboot bootloader'...the device goes into fastboot&rescue mode and the device is not recognized by computer anymore
Click to expand...
Click to collapse
Open control panel when your phone is in this state (it's fastboot mode) and you should see the folder I talked about.
It seems drivers issue, i hate windows 10
Try different usb port,and try to remove the drivers and install them again.
Make sure no usb device connected to any other ports.
grofock said:
Open control panel when your phone is in this state (it's fastboot mode) and you should see the folder I talked about.
Click to expand...
Click to collapse
YES!!!!!!
many thanks to you. grofock, and to ephemera, and XDA
At last i got it done. (Huawei are so tricky compared to samsung...but at least they do not explode
gm007 said:
It seems drivers issue, i hate windows 10
Try different usb port,and try to remove the drivers and install them again.
Make sure no usb device connected to any other ports.
Click to expand...
Click to collapse
You were probably right because i recently changed PC and aeverytime w10 upgrades I pray...
Have the the same problem, but didn't find the solution. Try different laptops and different cables. Windows can't recognise my Mate 8 L29 after B320 update cause of the wrong descriptor.
timasan said:
Have the the same problem, but didn't find the solution. Try different laptops and different cables. Windows can't recognise my Mate 8 L29 after B320 update cause of the wrong descriptor.
Click to expand...
Click to collapse
try grofock's hints about control panel and Device manager on windows....
pasil.pt said:
try grofock's hints about control panel and Device manager on windows....
Click to expand...
Click to collapse
I try it on four different PCs and still error 43 "wrong descriptor".
timasan said:
I try it on four different PCs and still error 43 "wrong descriptor".
Click to expand...
Click to collapse
Maybe explain more what you did,what are you trying to do and which tools you used.
gm007 said:
Maybe explain more what you did,what are you trying to do and which tools you used.
Click to expand...
Click to collapse
I'm trying to install drivers for Mate 8. I did it on different PC with Win 10 and 7. With different cables. Try to change or delete drivers for USB hub and etc. In fastboot mode and normal with usb debug and w/o.
timasan said:
I'm trying to install drivers for Mate 8. I did it on different PC with Win 10 and 7. With different cables. Try to change or delete drivers for USB hub and etc. In fastboot mode and normal with usb debug and w/o.
Click to expand...
Click to collapse
Did you install hisuite it has all the drivers and make sure to enable allow hisuite to use hdb in phone settings under security.