OK, so I am at a loss. I have installed Android Studio, SDK Manager and updated everything I can think of, plus everything that any developer on the web says should be updated. I have checked that the drivers are updated, but every time I try to sideload the latest OTA for my Nexus 6P I get the message "error: no devices/emulators found."
I have done the following:
a) USB debugging is enabled under Developer Options on the device
b) When I execute "adb devices" it shows the device
c) When I execute "adb reboot recovery" it reboots into In recovery
d) I then choose "select update from adb" on the device
e) And then try to execute "adb sideload angler-ota-nrd90u-ffef6b27.zip" only to be given the message that its loading and then "error" no devices/emulator found"
I have searched the web and tried all of the "fixes" and still cannot get the OTA to load, currently tried about 10 times and all have ended up needing to just reboot the system. Does anyone out there have any ideas of the problem and a solution? I have seen several forums that show others with the same issue, but none seem to verify if they have been able to correct the problem. Currently updated to Nougat through the beta program, but my devices shows that I am on NRD90M, which according to the Nexus Files for Developers is for the "ryu" for Pixel C?
Really would like to update the OS to the latest security patch prior to the October date, can anyone help?
There are different drivers for Fastboot and Recovery modes. Once your phone is in Recovery, execute "adb devices", if the phone is not listed there, go to Device Manager in Windows and install the driver.
Plug and Un-plug phone from computer after below step:
c) When I execute "adb reboot recovery" it reboots into In recovery
Faced the same issue earlier. Above thing worked for me.
I finally found a solution, had to do a lot of research but basically I needed to wipe the cache partition. Here is the site that shows you what to do.
https://productforums.google.com/forum/#!topic/nexus/hdrNONCCoNE
Currently my device is updating and is at about 75%! Success!!!
AP_Nex said:
Plug and Un-plug phone from computer after below step:
c) When I execute "adb reboot recovery" it reboots into In recovery
Faced the same issue earlier. Above thing worked for me.
Click to expand...
Click to collapse
This is exactly what worked for me. Happened twice and this fixed it twice.
Related
I am hoping someone can give me some pointers on what to look at... I have two Macs where I have encountered this problem. When in recovery, I type
Code:
adb devices
into the terminal and I get no devices found. When my Nexus 6p is booted into full OS mode I can see the device serial number reported, and I can even issue
Code:
adb reboot recovery
commands.
Any ideas what needs to happen to get the device to work properly in recovery mode with adb? I've gone through several of the tutorials and haven't found any smoking guns. I do NOT have adb in my path, but I do change to that folder and run ./adb to execute.
Some background
Both Macs run OS X 10.11, El Capitan
The Nexus 6p is on 6.0.1, MMB29Q, stock recovery and ROM, not rooted
ADB/Fastboot were installed via the Google Android SDK
Idk how different it is, but I use OSX 10.10.5. I type: ./adb or ./fastboot before commands. With the phone in the bootloader, do you have an issue when you run:
./fastboot devices
Sent from my Nexus 5X using Tapatalk
I used both on my Macbook Pro last night on 10.11.
When you plug the phone in, is it being recognized by the OS? (Or, if you have Android File Transfer installed, does it pop open immediately?)
Follow this tutorial, it will fix your ills.
http://forum.xda-developers.com/showthread.php?t=1917237
gewecht said:
I am hoping someone can give me some pointers on what to look at... I have two Macs where I have encountered this problem. When in recovery, I type
Code:
adb devices
into the terminal and I get no devices found. When my Nexus 6p is booted into full OS mode I can see the device serial number reported, and I can even issue
Code:
adb reboot recovery
commands.
Any ideas what needs to happen to get the device to work properly in recovery mode with adb? I've gone through several of the tutorials and haven't found any smoking guns. I do NOT have adb in my path, but I do change to that folder and run ./adb to execute.
Some background
Both Macs run OS X 10.11, El Capitan
The Nexus 6p is on 6.0.1, MMB29Q, stock recovery and ROM, not rooted
ADB/Fastboot were installed via the Google Android SDK
Click to expand...
Click to collapse
See here.
And here for issues with El Cap.
Thanks for the pointer... However, the problem persists.
I ran the installer after disabling System Integrity Protection (done in Recovery) and rebooted into OS X
I was able to detect the Nexus when the Android OS was running, but not in recovery (same behavior).
I rebooted to recovery and re-enabled System Integrity Protection. Rebooted again. No change in behavior.
So I'm really not what else I could or should be looking at.
BTW, it looks like the only benefit of disabling SIP is allowing the installation of the files into /usr/local/bin. Once it is installed I'm thinking you can re-enable SIP.
Any other thoughts?
uicnren said:
See here.
And here for issues with El Cap.
Click to expand...
Click to collapse
gewecht said:
Thanks for the pointer... However, the problem persists.
I ran the installer after disabling System Integrity Protection (done in Recovery) and rebooted into OS X
I was able to detect the Nexus when the Android OS was running, but not in recovery (same behavior).
I rebooted to recovery and re-enabled System Integrity Protection. Rebooted again. No change in behavior.
So I'm really not what else I could or should be looking at.
BTW, it looks like the only benefit of disabling SIP is allowing the installation of the files into /usr/local/bin. Once it is installed I'm thinking you can re-enable SIP.
Any other thoughts?
Click to expand...
Click to collapse
I did some further digging... When the Nexus is booted into Android I can see the device (identified as "Nexus 6p") in the USB chain in OS X's "System Information" tool. In the bootloader screen, OS X shows "Android" and fastboot does detect the device.
However, when I've rebooted into recovery I cannot see anything connected - not a device in recovery, not a Nexus 6p. Nothing!
gewecht said:
I did some further digging... When the Nexus is booted into Android I can see the device (identified as "Nexus 6p") in the USB chain in OS X's "System Information" tool. In the bootloader screen, OS X shows "Android" and fastboot does detect the device.
However, when I've rebooted into recovery I cannot see anything connected - not a device in recovery, not a Nexus 6p. Nothing!
Click to expand...
Click to collapse
Mind if I ask, what are you trying to do in recovery?
have you tried unplugging and replugging the usb type c while you were on adb/recovery screen? i had the same problem but unplug and replug worked for me.
bluwavemarshall said:
have you tried unplugging and replugging the usb type c while you were on adb/recovery screen? i had the same problem but unplug and replug worked for me.
Click to expand...
Click to collapse
I finally figured out what was going on.
When in Recovery mode, I could never see the Nexus 6p attached to the OS X machine. However, on a hunch, I enabled the sideload ZIP with ADB option (this is stock recovery), and suddenly I was able to see the 6p in OS X System Information, and detect it via "adb devices".
Not sure if this is expected behavior or not, but it seems that there is a portion of the USB interface in stock recovery that only loads on this device once you have enabled the sideload feature in recovery.
Thanks to everyone for the suggestions.
gewecht said:
I finally figured out what was going on.
When in Recovery mode, I could never see the Nexus 6p attached to the OS X machine. However, on a hunch, I enabled the sideload ZIP with ADB option (this is stock recovery), and suddenly I was able to see the 6p in OS X System Information, and detect it via "adb devices".
Not sure if this is expected behavior or not, but it seems that there is a portion of the USB interface in stock recovery that only loads on this device once you have enabled the sideload feature in recovery.
Thanks to everyone for the suggestions.
Click to expand...
Click to collapse
ADB works in OS mode, while USB debugging is enabled. Where stock recovery is concerned, only sideload mode will be available, since it doesn't require ADB access for anything else.
EDIT: And yes. It is expected behaviour of the stock recovery.
Glad you figured it out! Cool
I had the same problem, how did you "enable the sideload ZIP with ADB option "?
I'm having the same issue on my Pixel. How did you "enabled the sideload ZIP with ADB option (this is stock recovery)"??
---------- Post added at 11:54 PM ---------- Previous post was at 11:50 PM ----------
How do I "enabled the sideload ZIP with ADB option"?
gewecht said:
I finally figured out what was going on.
When in Recovery mode, I could never see the Nexus 6p attached to the OS X machine. However, on a hunch, I enabled the sideload ZIP with ADB option (this is stock recovery), and suddenly I was able to see the 6p in OS X System Information, and detect it via "adb devices".
Not sure if this is expected behavior or not, but it seems that there is a portion of the USB interface in stock recovery that only loads on this device once you have enabled the sideload feature in recovery.
Thanks to everyone for the suggestions.
Click to expand...
Click to collapse
I've checked other threads but other similar threads were able to get the phone detected in Device Manager so...
I went to factory reset my old Nexus 4 after using it whilst my LG G4 was being repaired. Instead of wiping the data, I accidentally wiped the entire phone, OS included. I wasn't paying attention to what i was doing due to working at the same time and as a result the phone now only boots into TWRP and fastboot mode, but nothing else.
I tried to connect it to my windows 10 laptop so I could flash a new ROM but my laptop can't find the nexus 4 at all. Not when in recovery or when in fastboot.
Opening device manager shows that it is not there at all. There is no ACER usb device driver, nothing that resembles the nexus 4 at all. I've attached an image showing what device manager shows when the nexus 4 is connected and in recovery mode.
As you can see, there are no drivers I can uninstall. I have installed the google USB drivers from Android SDK manager. Still doesn't show. ADB doesn't work either.
I have tried multiple USB cables and every USB port. The phone charges when using an AC adaptor and charges when connected to the laptop. I can't try a different computer because I do not have access to one. Frankly I'm at a loss as to what to do.
When my nexus 4 was previously unable to connect I was able to see the device and just had to uninstall/reinstall/update drivers to get it working. This time, I can't seem to do anything. My LG G4 connects fine and without issue.
Anyone able to help?
The only way to really tell if it is a software or hardware issue would be to try another computer with Win7.
You may be able to flash a custom ROM with a OTG drive as well.
I had the same problem. When using adb and fastboot I get errors about like "error: device '(null)' not found".
Youtube video with id t0pV2pSw2N0 (sorry I am not yet allowed to post external urls) was helpfull and now I can see Android Composite ADB Interface again in the device manager. I still can not use commands adb and fastboot with exception of adb sideload. Unfortunately I have not yet succeeded to flash an image succesfully with sideload.
first try 2 remove any current drivers that are installed.
then u should experiment with different drivers.
the SkipSoft ToolKit have a huge selection, try each one of them (one of them should work).
begin with the ULTIMATE drivers and Adb/Fastboot Installer and if it don't work use the toolkit drivers.
https://skipsoft.net/download-page/
For me it turned out that MTP was enabled by default. After each restart MTP was enabled again. Now I have disabled MTP and my device is found by normal adb command.
Steps:
1) Start your device in twrp recovery mode
2) In main menu go to mount and tap "Disable MTP"
3) In main menu go to advanced -> adb sideload. Wipe caches and slide to start sideload
4) On your pc go to the command shell
5) Start "adb sideload <image_name.zip>" (replace image_name.zip with a valid image). It does not matter whether this fails or succeeds. Only thing important is that adb connects to your device.
6) Start "adb shell getprop persist.sys.usb.config". As result you will see the actual setting of the USB configuration your device when starting up. In my case it responded with "mtp,adb".
7) Start "adb shell setprop persist.sys.usb.config adb" to enable only "adb" configuration
8) Repeat step 6 to check result
9) Restart your device in recovery mode
10) Start "adb devices" to check if your device is now listed.
i_need_some_help said:
For me it turned out that MTP was enabled by default. After each restart MTP was enabled again. Now I have disabled MTP and my device is found by normal adb command.
Steps:
1) Start your device in twrp recovery mode
2) In main menu go to mount and tap "Disable MTP"
3) In main menu go to advanced -> adb sideload. Wipe caches and slide to start sideload
4) On your pc go to the command shell
5) Start "adb sideload <image_name.zip>" (replace image_name.zip with a valid image). It does not matter whether this fails or succeeds. Only thing important is that adb connects to your device.
6) Start "adb shell getprop persist.sys.usb.config". As result you will see the actual setting of the USB configuration your device when starting up. In my case it responded with "mtp,adb".
7) Start "adb shell setprop persist.sys.usb.config adb" to enable only "adb" configuration
8) Repeat step 6 to check result
9) Restart your device in recovery mode
10) Start "adb devices" to check if your device is now listed.
Click to expand...
Click to collapse
Thanks, I will give this a try!
elad.g said:
first try 2 remove any current drivers that are installed.
then u should experiment with different drivers.
the SkipSoft ToolKit have a huge selection, try each one of them (one of them should work).
begin with the ULTIMATE drivers and Adb/Fastboot Installer and if it don't work use the toolkit drivers.
https://skipsoft.net/download-page/
Click to expand...
Click to collapse
I tried removing all USB drivers and then using the toolkit and tried installing each driver. None of them allowed my PC to detect the nexus 4. As you can see in the attachment, nothing in device manager remotely resembling my nexus 4. This is after uninstalling and reinstalling and also updateing the LG G4 drivers (it makes no difference).
i_need_some_help said:
I had the same problem. When using adb and fastboot I get errors about like "error: device '(null)' not found".
Youtube video with id t0pV2pSw2N0 (sorry I am not yet allowed to post external urls) was helpfull and now I can see Android Composite ADB Interface again in the device manager. I still can not use commands adb and fastboot with exception of adb sideload. Unfortunately I have not yet succeeded to flash an image succesfully with sideload.
Click to expand...
Click to collapse
Alas, this did not work.
audit13 said:
The only way to really tell if it is a software or hardware issue would be to try another computer with Win7.
You may be able to flash a custom ROM with a OTG drive as well.
Click to expand...
Click to collapse
Unfortunately I don't have access to any other PC for this purpose. I can't connect download software or connect USB devices to the PCs at work due to security. I tried an OTG drive but TWRP wouldn't let me mount it, apparently OTG is not enabled by default for the nexus 4.
I've tried all 3 USB ports, several different cables but no luck. I guess that's it for this nexus 4 then?
If the phone is not booted into its ROM, ADB commands won't work. You need to use "fastboot devices" with the phone in bootloader mode.
You android device will reboot in several different boot modes (fastboot, recovery, normal). For each of these boot modes a separate device drive might be installed on your Windows. So check the device drive after each change of boot mode. If needed uninstall and reinstall the correct device driver.
I have seen a lot of people using unofficial and third-party methods to root, which can result in a lot of adverse circumstances to say the least.
So I'm presenting a complete noob-friendly guide to rooting.
Prerequisites:
1. A computer ( I'm using Windows 10 but any OS would do)
2. A USB cable
3. Basic computer know-how
Part 1 (Getting computer ready)
Download sdk tools (adb and fastboot) from here
Note that in the entire guide I'm using official products.
So in Windows, download the zip and extract it in any folder.
Now download latest twrp recovery from here
The lastest version as of 7th August, 2017 is 3.1.
The downloaded file will be named as twrp-x.x.x-0-x3.img.
Now rename this as recovery.img (this will make our work easier)
Now move that file to platform-tools folder which we extracted earlier.
Also, I suggest downloading Intel USB drivers for Android from here
Part 2 (Getting Phone Ready)
Unlocking bootloader didn't format my phone but taking a backup is still important.
Now go to Settings<About Phone and click on Build until it says "You have become a developer"
Now back to main settings menu and find "Developer Options". And turn USB debugging on.
Download magisk install.zip, unistall.zip ans apk from here
Now connect your phone to PC via USB cable.
Step 3 (Rooting!!)
Now open platform-tools folder and press Shift+ right click.
Select "open command prompt here".
Now a terminal will open.
Type
Code:
adb devices
Now you will get a prompt on your phone. Accept it.
Now type
Code:
adb reboot bootloader
Your phone will automatically reboot and fastboot will come up.
Now type
Code:
fastboot oem unlock
[Alert! If you get <waiting for device> right click on start menu, select the unrecognized device and install Intel driver in it. Google for detailed instruction]
The process will start and you will get something like
(Okay ....)
(Okay....)
And type prompt. Now type
Code:
fastboot flash recovery recovery.img
Flashing will start.
When you get type prompt again, type
Code:
fastboot reboot
And when the screen switches off, hold power up+power button.
(
Code:
fastboot reboot emergency
should work but it's effect was same as
Code:
fastboot reboot
If you get something like red state... verification failed... Then it's a good news.
Wait a few seconds and then twrp will launch. I suggest swiping on the first screen
[because letv is almost dead and we can't expect any updates. Plus my bootloader was relocked in my first attempt when I didn't swipe.]
(I suggest wiping dalvik cache and cache)
Now you can just reboot your phone normally.
Now install magisk apk.
Now reboot again to recovery. (Easiest way is Update app>tree dots menu> reboot to recovery)
When twrp starts, go to install> download and find magisk zip. Swipe to install.
Reboot and you have a fully rooted phone!!
Will it work with Le1s eco x509
Will the given method work with le 1s eco x509
Yes it will!
Im stuck in <waiting for any device>. I've installed the Intel drivers , what do you mean by select unrecognized device and install the Intel driver in it?
deepu_ said:
Im stuck in <waiting for any device>. I've installed the Intel drivers , what do you mean by select unrecognized device and install the Intel driver in it?
Click to expand...
Click to collapse
Intel driver will not work try downloading drivers from skyneel for our phone
deepu_ said:
Im stuck in <waiting for any device>. I've installed the Intel drivers , what do you mean by select unrecognized device and install the Intel driver in it?
Click to expand...
Click to collapse
Intel drivers worked for my leeco le 1s. Ideally, Intel drivers should work for all devices.
I'll make a tutorial with screenshots on setting up the drivers whenever I get time.
i cant find "open command prompt here" with shift+ Right click in platform-tools folder
junaidshaik96 said:
i cant find "open command prompt here" with shift+ Right click in platform-tools folder
Click to expand...
Click to collapse
Make sure the directory is writable .
stealthinator16 said:
I have seen a lot of people using unofficial and third-party methods to root, which can result in a lot of adverse circumstances to say the least.
So I'm presenting a complete noob-friendly guide to rooting.
Prerequisites:
1. A computer ( I'm using Windows 10 but any OS would do)
2. A USB cable
3. Basic computer know-how
Part 1 (Getting computer ready)
Download sdk tools (adb and fastboot) from here
Note that in the entire guide I'm using official products.
So in Windows, download the zip and extract it in any folder.
Now download latest twrp recovery from here
The lastest version as of 7th August, 2017 is 3.1.
The downloaded file will be named as twrp-x.x.x-0-x3.img.
Now rename this as recovery.img (this will make our work easier)
Now move that file to platform-tools folder which we extracted earlier.
Also, I suggest downloading Intel USB drivers for Android from here
Part 2 (Getting Phone Ready)
Unlocking bootloader didn't format my phone but taking a backup is still important.
Now go to Settings<About Phone and click on Build until it says "You have become a developer"
Now back to main settings menu and find "Developer Options". And turn USB debugging on.
Download magisk install.zip, unistall.zip ans apk from here
Now connect your phone to PC via USB cable.
Step 3 (Rooting!!)
Now open platform-tools folder and press Shift+ right click.
Select "open command prompt here".
Now a terminal will open.
Type
Code:
adb devices
Now you will get a prompt on your phone. Accept it.
Now type
Code:
adb reboot bootloader
Your phone will automatically reboot and fastboot will come up.
Now type
Code:
fastboot oem unlock
[Alert! If you get <waiting for device> right click on start menu, select the unrecognized device and install Intel driver in it. Google for detailed instruction]
The process will start and you will get something like
(Okay ....)
(Okay....)
And type prompt. Now type
Code:
fastboot flash recovery recovery.img
Flashing will start.
When you get type prompt again, type
Code:
fastboot reboot
And when the screen switches off, hold power up+power button.
(
Code:
fastboot reboot emergency
should work but it's effect was same as
Code:
fastboot reboot
If you get something like red state... verification failed... Then it's a good news.
Wait a few seconds and then twrp will launch. I suggest swiping on the first screen
[because letv is almost dead and we can't expect any updates. Plus my bootloader was relocked in my first attempt when I didn't swipe.]
(I suggest wiping dalvik cache and cache)
Now you can just reboot your phone normally.
Now install magisk apk.
Now reboot again to recovery. (Easiest way is Update app>tree dots menu> reboot to recovery)
When twrp starts, go to install> download and find magisk zip. Swipe to install.
Reboot and you have a fully rooted phone!!
Click to expand...
Click to collapse
It works perfectly on x507, thanks bro
Orange State
stealthinator16 said:
I have seen a lot of people using unofficial and third-party methods to root, which can result in a lot of adverse circumstances to say the least.
So I'm presenting a complete noob-friendly guide to rooting.
Prerequisites:
1. A computer ( I'm using Windows 10 but any OS would do)
2. A USB cable
3. Basic computer know-how
Part 1 (Getting computer ready)
Download sdk tools (adb and fastboot) from here
Note that in the entire guide I'm using official products.
So in Windows, download the zip and extract it in any folder.
Now download latest twrp recovery from here
The lastest version as of 7th August, 2017 is 3.1.
The downloaded file will be named as twrp-x.x.x-0-x3.img.
Now rename this as recovery.img (this will make our work easier)
Now move that file to platform-tools folder which we extracted earlier.
Also, I suggest downloading Intel USB drivers for Android from here
Part 2 (Getting Phone Ready)
Unlocking bootloader didn't format my phone but taking a backup is still important.
Now go to Settings<About Phone and click on Build until it says "You have become a developer"
Now back to main settings menu and find "Developer Options". And turn USB debugging on.
Download magisk install.zip, unistall.zip ans apk from here
Now connect your phone to PC via USB cable.
Step 3 (Rooting!!)
Now open platform-tools folder and press Shift+ right click.
Select "open command prompt here".
Now a terminal will open.
Type
Code:
adb devices
Now you will get a prompt on your phone. Accept it.
Now type
Code:
adb reboot bootloader
Your phone will automatically reboot and fastboot will come up.
Now type
Code:
fastboot oem unlock
[Alert! If you get <waiting for device> right click on start menu, select the unrecognized device and install Intel driver in it. Google for detailed instruction]
The process will start and you will get something like
(Okay ....)
(Okay....)
And type prompt. Now type
Code:
fastboot flash recovery recovery.img
Flashing will start.
When you get type prompt again, type
Code:
fastboot reboot
And when the screen switches off, hold power up+power button.
(
Code:
fastboot reboot emergency
should work but it's effect was same as
Code:
fastboot reboot
If you get something like red state... verification failed... Then it's a good news.
Wait a few seconds and then twrp will launch. I suggest swiping on the first screen
[because letv is almost dead and we can't expect any updates. Plus my bootloader was relocked in my first attempt when I didn't swipe.]
(I suggest wiping dalvik cache and cache)
Now you can just reboot your phone normally.
Now install magisk apk.
Now reboot again to recovery. (Easiest way is Update app>tree dots menu> reboot to recovery)
When twrp starts, go to install> download and find magisk zip. Swipe to install.
Reboot and you have a fully rooted phone!!
Click to expand...
Click to collapse
There was a prompt for TWRP update and Magisk Update.
After it has started showing Orange State instead of Red State.
The phone got rebooted and all installed apps were deleted.
Xposed got uninstalled.
Playstore, Googlemaps got unistalled.
Camera is working.
Calling is working.
Now it shows Orange State.
Is it safe.
Can we bring it to red state?
As per this link
https://www.androidauthority.com/verified-boot-warnings-in-android-6-0-marshmallow-650368/
Orange warning: Your device is in an “unlocked” state. This means that your operating system can’t be checked to make sure that it’s safe to use.
Red warning: The operating system on your device has been changed or corrupted and is not safe to use. The device may not work properly and could expose your data to corruption and security risks.
Orange State seems to be a better state than red.
eighty9sid said:
There was a prompt for TWRP update and Magisk Update.
After it has started showing Orange State instead of Red State.
The phone got rebooted and all installed apps were deleted.
Xposed got uninstalled.
Playstore, Googlemaps got unistalled.
Camera is working.
Calling is working.
Now it shows Orange State.
Is it safe.
Can we bring it to red state?
As per this link
https://www.androidauthority.com/verified-boot-warnings-in-android-6-0-marshmallow-650368/
Orange warning: Your device is in an “unlocked” state. This means that your operating system can’t be checked to make sure that it’s safe to use.
Red warning: The operating system on your device has been changed or corrupted and is not safe to use. The device may not work properly and could expose your data to corruption and security risks.
Orange State seems to be a better state than red.
Click to expand...
Click to collapse
I too got orange state when I had to reroot my device after it got bricked, but there was no issue, everything worked perfectly.
Hi l used this very step by step guides but sadly l got stuck at the :-
Alert! If you get <waiting for device> right click on start menu, select the unrecognized device and install Intel driver in it. Google for detailed instruction]
The process will start and you will get something like
(Okay ....)
(Okay....)
Here l select the unrecognized device and install the Intel drivers but it stuck at the "Okay,,,,Okay" prompt. Meaning that l didn't get this okay prompts and it keeps me on waiting the whole day.
Secondly, till this command l stop it and power down the phone, so after l power back on and try opening the "Application" folder, then it's not working anymore, it shuts down itself.
Please help!!
Valambok said:
Hi l used this very step by step guides but sadly l got stuck at the :-
Alert! If you get <waiting for device> right click on start menu, select the unrecognized device and install Intel driver in it. Google for detailed instruction]
The process will start and you will get something like
(Okay ....)
(Okay....)
Here l select the unrecognized device and install the Intel drivers but it stuck at the "Okay,,,,Okay" prompt. Meaning that l didn't get this okay prompts and it keeps me on waiting the whole day.
Secondly, till this command l stop it and power down the phone, so after l power back on and try opening the "Application" folder, then it's not working anymore, it shuts down itself.
Please help!!
Click to expand...
Click to collapse
Don't power off your phone. Post a screenshot of what exact problem you face with driver installation.
Phone Dead
Hi, after completing this step by step guides my Le 1s can't boot to normal anymore, even if I try booting up system from twrp also it doesn't help, I cant even power off now. So, please please help me out again on how to get back to a normal phone. Thanks in advance.
N.B: My phone shows Orange state
Hi,
I just bought Mi A1.
Now, I wanted to install oreo.
So I was trying to root and install twrp.
Now I'm no expert, I just follow the provided steps and have been successful with past devices.
Note :
1) Developer enabled
2) oem unlocking enabled
3) usb debugging enabled
So I'm using this https://forum.xda-developers.com/mi...l-one-driversunlocktwrpfactory-t3695256/page2
But, there are two issues :
1) When I click on Reboot in fastboot/bootloader mode , it shows this in command prompt : http://prntscr.com/i2sn1o
and in the app, it automatically disconnects from the device http://prntscr.com/i2sncw
2) While this is happening and I leave my device, it automatically goes out from fastboot to power off charging mode.
I tried on another pc too, and followed the steps according to video, still no luck.
And I tried manual methods too, like https://www.youtube.com/watch?v=tRcYUMBgvaI
no luck there either.
Please help.
your adb driver is not installed correctly i guess, happened to me too.
try "adb devices" and will show no devices, if this happen, is the adb driver issue.
this fixed for me.
https://forum.xda-developers.com/showthread.php?p=75163858#post75163858
riccetto80 said:
your adb driver is not installed correctly i guess, happened to me too.
try "adb devices" and will show no devices, if this happen, is the adb driver issue.
this fixed for me.
https://forum.xda-developers.com/showthread.php?p=75163858#post75163858
Click to expand...
Click to collapse
I don't know if there is issue with driver. Because during installation there was no error.
Also, when I command "adb devices" it shows me a device as number.
So it is able to connect to the device then right?
You must install adb drivers AND fastboot drivers separately. I always had to install them manually via device manager. If your phone reboots from fastboot mode automatically, I'm 99% sure that you do not have drivers installed correctly.
_mysiak_ said:
You must install adb drivers AND fastboot drivers separately. I always had to install them manually via device manager. If your phone reboots from fastboot mode automatically, I'm 99% sure that you do not have drivers installed correctly.
Click to expand...
Click to collapse
Hmmmmm. Ok, I'll do that then. Thanks buddy. I'll try again and reply back asap.!!
Hi all,
I used "adb sideload" method to update my S10+ (AUT) to oneui beta 2. Now I'd like to update to beta 3 but when in recovery "adb devices" doesn't see my device anymore so I cannot sideload. When I reboot to system, "adb devices" shows my device without problem. I'm using stock usb cable.
Any help greatly appreciated.
EDIT: I was trying on OSX so I checked on Windows 10 and the result was the same.
EDIT2: Ok, so I went back to Pie 9 with ODIN. After that, ADB in recovery mode is back to normal. I used "adb sideload" to install beta 2, all fine, boots fine. But when going back to recovery, I get errors and device is not visible with "adb devices" once I choose the ADB update method.
This message on the phone when entering recovery mode:
#Reboot Recovery Cause is [BL:Recovery Mode Set by keys]#
E:[libfs_mgr]Unable to disable quotas on /dev/block/platform/13d60000.ufs/by-name/userdata because /system/bin/tune2fs is missing
E:[libfs_mgr]Failed trying to run /system/bin/e2fsck
Supported API:3
And then upon choosing ADB update mode:
# MANUAL MODE v1.0.0 #
Now send the package you want to apply
o the device with "adb sideload filename..."
EDIT3 : I cleared cache partition and factory reset. Now the errors are gone when entering recovery but phone still not visible with "adb devices" after entering adb update mode.
EDIT4: Ended up reinstalling only recovery from latest pie through ODIN as adb sideload as that one worked to sideload pie -> beta 2 but alas "adb devices" doesn't recognize my device. Conclusion, once updated to beta 2, I cannot use adb sideload to install beta 3. Any help appreciated
I have the same issue as you do on the S10+, except my recovery was corrupted from the beginning, on stock pie ADB sideload couldn't load due to missing usb node and configfs file.
I flashed multiple times with ODIN and it didn't bring ADB back. Luckily I had an old SD card laying around, so I have been able to flash each beta .zip from that. I've been checking ADB at each beta version, and as far as I can tell, my ADB keeps throwing the same error as yours...I'm not sure if this is a Samsung beta issue, or if our phones are just special.
Hopefully, you can continue to install the betas using an SD card.
I had the same error whem trying to flash the beta 3 update, but i solved it aplying the update.zip from a SD Card and all worked. Like the above post.