Develop Bugs

[Q] Need Assistance, I brick my Galaxy Nexus

Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!

So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?

cbs2002 said:
Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
Click to expand...
Click to collapse
The key piece of information for your symptom is in this line:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
The other lines do help provide background as to the other modes such as recovery and download working properly, which indicates the issue is not *serious*.
The symptom you state, where the device does not boot past the boot logo, usually means the device is not able to boot the kernel or boot past the kernel. The boot logo appears while the kernel is being loaded on the device. Generally, after the boot logo and kernel finish loading a boot animation appears which indicates the kernel has usually handed off to the Android OS to continue booting.
My approach would be to load a completely stock ROM in order to restore a working kernel and ROM to the device. I generally perform this step as a baseline to get everything back in working order.
In many instances the ROM is dependent on the kernel. Your situation requires at least a kernel to be loaded and in order to prevent any further issues, it would be best to load a ROM dependent on the kernel being loaded.
A simple way would be to grab the stock factory images from Google's site and load those back onto the device.
Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode.
Hope that helps!

Since you're rooted I'm going to assume you have ADB and the necessary drivers installed.
1.) Download a ROM. It doesn't have to be stock, you can choose any of the ROMs from the development section for your device. Most of the ROMs are packaged with a kernel already.
2.) Save this ROM file to the same folder where you have ADB installed.
3.) Boot your phone into CWM recovery and plug it into your computer.
4.) Use ADB to push the ROM zip file to your phone (/data/media). For example:
Code:
c:\gnex\>adb push rom.zip /data/media/rom.zip
5.) Use CWM to wipe data, cache, and davlik-cache
6.) Install zip from sdcard and flash the rom.zip.

RMarkwald said:
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
Click to expand...
Click to collapse
1. I am using GSM
2. Whenever I turn on my mobile, the 'Google' and 'Unlock' logo appears and then freeze, with no more respond at all
* I definitely mess up some system files, but don't know how to restore it because my PC do not recognize my mobile.
Thanks

I am seeing more and more of these threads about "bricked" nexus's is this an issue with how new the phone is or people not following instructions properly as they are too eager to root their phones?
All else fails flash back to stock and count yourself lucky.

To silow,
Thanks for your advice, but fail
1. I put adb.exe, adbwinapi.dll and fastboot.exe (3 files) under my PC C drive (i.e. C
2. I also put a stock Rom (rename as rom.zip) under C drive (i.e. C
3. Boot phone into CWM recovery and plug it into computer.
4. Use cmd command and type c:\gnex\>adb push rom.zip /data/media/rom.zip
5. It fails , It say "Access Denied" (in Chinese, but I translate it into English here)
6. How do I use ADB (it is a ADB.exe file, When I double click it, it only flash up a few page very fast and nothing happen)
Please assist!

To Joeykrim,
I agree that
"Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode."
But how? (according to my symptoms)

The command I gave you was just an example. I didn't spell out the exact details because I thought that you would know how to do it considering you rooted the phone.
If you put the adb.exe and AdbWinApi.dll file in your C: drive, make sure you copy the ROM file to your C: drive too. In the follow example I'm going to use "ROM.zip" but use the name of the ROM file that you downloaded. Also I am assuming you are on Windows XP.
1.) Boot your phone into CWM recovery and then plug it in.
2.) Go to your Start Menu and choose Run. Then type in "cmd" without quotes and hit enter to open a command prompt.
3.) Enter:
Code:
cd c:\
4.) Enter the following to make sure ADB can see your phone:
Code:
adb devices
You should see something similiar to this to confirm ADB can see your device:
List of devices attached
019B756F0C018012 device
5.) Enter the following command to copy the ROM file to your phone. Remember to replace ROM.zip with whatever the name of the ROM file is:
Code:
adb push ROM.zip /data/media/ROM.zip
6.) Use CWM to wipe data, cache, and davlik-cache
7.) Install zip from sdcard and flash the rom.zip.

To Silow,
You have been very helpful, but I fail.
"You should see something similiar to this to confirm ADB can see your device:
List of devices attached"
There is NO device number shown after the phrase 'List of devices attached'
To recap:
a) Phone is already plugged in my PC, under the Clockworkmod Recovery 5.5.0.2
b) adb.exe and AdbWinApi.dll file are under C: drive directly
c) Also type cmd in 'Run', a black Dos window shown C:\windows\system32\cmd.exe
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Pls don't give up on me!
: )

you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot (edit: wrong!)

Sounds like your ADB USB drivers are not correctly installed. While the phone is under CWM, when you plug it in is your computer attempting to install drivers for a new device?
Download these bare ADB Interface drivers.ADB USB Drivers
Go into Device Manager on your computer and check the device list for any unknown devices or "?" devices. If you need to update those drivers by pointing them to the drivers you downloaded and extracted from that link above.
When the ADB Interface drivers are correctly installed you should see Android Phone listed under under your Device Manager when it's plugged in with CWM recovery loaded.
---------- Post added at 02:36 PM ---------- Previous post was at 02:35 PM ----------
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.

silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
edit: i did appear to have one missing driver, my mistake. it was listed in device manager as "unknown - full"
its funny cause i never had to use adb from cwm before, never noticed

cbs2002 said:
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Click to expand...
Click to collapse
This symptom generally occurs from not having loaded the drivers for the hardware. As with the majority of hardware devices when being connected to a Windows machine, the drivers need to be loaded. Sometimes these are automatically loaded and other times they have to be manual loaded.
As an alternative and for future reference, the android-sdk package contains general USB drives which usually work for Google Nexus devices.
Generally, as this providers a *cleaner* install, best practice as recommended by Google is to download the whole android-sdk .zip and then from the installer download/install the pieces needed, such as platform-tools (containing adb) and USB drivers as opposed to extracting out the adb.exe and .dll file and installing manually.
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
Agreed. To add greater clarification so there is no confusion: adb can't be used from the bootloader.
The /sbin/adbd daemon on the device is only loaded while in normal android boot mode or in recovery mode as called by the init.rc (or on some older devices, recovery.rc) file in the boot process.
Bootloader mode will only work with fastboot while it is in fastboot usb mode.
On some devices, the bootloader has a separate menu for fastboot and on other devices, the fastboot mode is directly entered when entering the bootloader.
Hope that helps clarify!

To silow (and all other helpers)
1. I fail
2. The ADB USB drivers in my PC should be fine as in Device Manager , I can see Android Phone with Android Composite ADB Interface. (No exclamation mark)
3. On the other hand, whenever I plug my mobile into PC, I can see "Unknown-Full"
4. In DOS, when I first type "adb devices" it shows
* daemon not running. starting it now on port 5037*
*daemon started successfully *
List of devices attached
(but NO device number shown!)
5. When I enter adb devices second time, it shows
List of devices attached (No device number shown)
Thank you so much , but it is Hong Kong time (my place) at 0511 am , I didn't sleep all night and I am very tired.
If you don't mind (especially big helper Silow), please give me email so that I capture screen picture and show you in detail (hope it may help)
my email is
[email protected]
I need to sleep now, I will check my email and see you guys or come back this Forum later (several hours later, as I really need some sleep right now)
Pls don't give up on me as this is an expensive mobile. I think the hardware is fine, just need to figure out a way to unbrick it.
Thanks, and see you!

What you need to do is right click on "Unknown-Full" and click on "Update Driver...". Then choose "Install from a list or specific location". Make sure "Search for the best driver in these locations." is checked and "Include this location in the search:" is check. Click on the Browse button and browse to where you extracted the driver files from the link I posted above. Click Next and this should install the correct drivers for you. Afterwards try "adb devices" again to see if ADB now reconizes your device.

To Silow,
Fail.
1. Already installed the drivers you gave me (and there is no 'Exclamation' Mark) in Device manager
2. Situation is the same , Cannot recognize my mobile (i.e. no Device No. after entering adb devices)
3. "List of devices attached" shown in DOS video but without any number.
No other method?
My mobile is really 'bricked' to death?

To Silow and all,
Something important
1. When choose 'install zip from sd card' under CWM, a list of old folder names remains
(e..g gameloft, DCIM, Pictures, etc). That means almost all old files, folders are STILL in my mobile!
2. I have already use the funcion 'Wipe data/factory reset', 'wipe cache partition', ' Wipe Dalvik Cache'
Perhaps my CWM has problem?

What happens when you update drivers for Unknown-Full?
Boot into fastboot and see if your computer recognizes the phone by checking device manager. The key here is to get your computer to see the phone either in fastboot or CWM.
Perhaps try another cable, USB port, or new computer.
The goal is to get Android Phone ADB Composite Interface to show up in device manager either in Fastboot or CWM. Without that done you cannot use Fastboot to flash nor ADB to push a zip file to the phone.
Sent from my Galaxy Nexus using XDA App

[Q] MTP USB Device: ADB lists no devices

Hi guys.
The phone is Xperia S.
I have installed CWM and wiped all partitions (except for sdcard) in order to prepare the phone for CM12.1 install.
Now I understand that my CWM version is outdated (5.5.0.4) and I need to install TWRP (which I had had installed before).
The problem is that when I plug in the phone, Windows registers it as MTP USB Device and I cannot uninstall/change drivers. adb devices lists no devices and I cannot do anything with the phone now.
Also, I have twrp.img on sdcard, but I'm not sure how to install it from CWM. When I was running TWRP before, adb was working fine.
So, I guess my problem can be fixed in two ways:
Install TWRP from CWM. I have twrp.img on sdcard, but CWM won't let me install it, I can't see it listed in file list.
Uninstall/change drivers for "MTP USB Device" so that adb works again.
Any help would be appreciated, as I cannot install anything on my phone now, and all I have is a CWM recovery on it.

Witchunter said:
Hi guys.
The phone is Xperia S.
I have installed CWM and wiped all partitions (except for sdcard) in order to prepare the phone for CM12.1 install.
Now I understand that my CWM version is outdated (5.5.0.4) and I need to install TWRP (which I had had installed before).
The problem is that when I plug in the phone, Windows registers it as MTP USB Device and I cannot uninstall/change drivers. adb devices lists no devices and I cannot do anything with the phone now.
Also, I have twrp.img on sdcard, but I'm not sure how to install it from CWM. When I was running TWRP before, adb was working fine.
So, I guess my problem can be fixed in two ways:
Install TWRP from CWM. I have twrp.img on sdcard, but CWM won't let me install it, I can't see it listed in file list.
Uninstall/change drivers for "MTP USB Device" so that adb works again.
Any help would be appreciated, as I cannot install anything on my phone now, and all I have is a CWM recovery on it.
Click to expand...
Click to collapse
The MTP is fine, You don't need to uninstall it. Try following the method from here to flash the ROM.

Mirhawk said:
The MTP is fine, You don't need to uninstall it. Try following the method from here to flash the ROM.
Click to expand...
Click to collapse
Thanks for the suggestion.
When I turn off the phone, press and hold UP button and then connect the phone to PC, the blue light lights up as it should. However, after ~10 seconds, blue light goes away and the phone goes to CWM recovery.
Therefore, I'm unable to execute adb commands during this short time period.
How to prevent CWM from starting up while in fastboot mode?

Witchunter said:
Thanks for the suggestion.
When I turn off the phone, press and hold UP button and then connect the phone to PC, the blue light lights up as it should. However, after ~10 seconds, blue light goes away and the phone goes to CWM recovery.
Therefore, I'm unable to execute adb commands during this short time period.
How to prevent CWM from starting up while in fastboot mode?
Click to expand...
Click to collapse
Then Your fastboot drivers are not installed.
Disconnect Your phone from PC.
Open command prompt and run this command:
Code:
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
and then open device manager, Choose View, Show Hidden Devices. Then uninstall any device with Xperia S and/or android in it. Then install the flashtool, fastboot, and every Xperia S related drivers from drivers pack in flashtool. I see that You use Windows 8/8.1, hence You need to follow a different method to install drivers. You can find that method here. Then follow the method I mentioned before.

Mirhawk said:
Then Your fastboot drivers are not installed.
Disconnect Your phone from PC.
Open command prompt and run this command:
Code:
SET DEVMGR_SHOW_NONPRESENT_DEVICES=1
and then open device manager, Choose View, Show Hidden Devices. Then uninstall any device with Xperia S and/or android in it. Then install the flashtool, fastboot, and every Xperia S related drivers from drivers pack in flashtool. I see that You use Windows 8/8.1, hence You need to follow a different method to install drivers. You can find that method here. Then follow the method I mentioned before.
Click to expand...
Click to collapse
While waiting for your answer, I found the video detailing instructions to install drivers on Windows 8.1 x64:
Nonetheless, thank you for your answer, now I can continue to try to install CM12.1.

Huawei Watch Update 1.4 is here!

Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you are connected to your charging dock.
Make sure you are running the latest update LCB43B.
I did all this on Win 10.
1. Just be fully stock including recovery. Refer to Skin1980's guide here to return to stock if you used his previous kernel or did any other mods like TWRP or root. (http://forum.xda-developers.com/huawei-watch/general/guide-return-to-stock-huawei-watch-t3219596)
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339) (People have reported PDANET drivers are working if the naked drivers do not work for them and are somewhat easier to install.)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip and make sure its located inside the root directory of your adb installation.
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Don't forget to hit the thanks button! I appreciate it!

Thank you. Can you please create a step by step guide for idiots like me, who have never used adb etc..?

hey when i try to go to recovery and do the "adb devices within stock recovery.. i see this
c:\android\hwatch> adb reboot bootloader
c:\android\hwatch>adb devices
list of devices attached
c:\android\hwatch>
even though when i was on the main menu of the watch before rebooting to recovery and all that
list of devices attached
FFS7N15B06003222 device
i go to bootloder reboot recovery adb devices... get nothing in there

chachin said:
hey when i try to go to recovery and do the "adb devices within stock recovery.. i see this
c:\android\hwatch> adb reboot bootloader
c:\android\hwatch>adb devices
list of devices attached
c:\android\hwatch>
even though when i was on the main menu of the watch before rebooting to recovery and all that
list of devices attached
FFS7N15B06003222 device
i go to bootloder reboot recovery adb devices... get nothing in there
Click to expand...
Click to collapse
I updated OP check the steps again. adb commands won't work in bootloader. Once in recovery swipe down and select apply update from adb then issue the "adb sideload update.zip" command.

so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>

chachin said:
so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>
Click to expand...
Click to collapse
Make sure the update file is inside your root adb directory on your hard drive.

chachin said:
so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>
Click to expand...
Click to collapse
It looks like your device is still not visible to adb. Make sure you don't have any other devices connected like a phone with debugging turned on also. And you do need to be in recovery with it awaiting the sideload update.zip command. You seemed to be in the correct place.

Mine got pushed to me, I just have to charge it
Sent from my VS990 using Tapatalk

xceebeex said:
Mine got pushed to me, I just have to charge it
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
YAY! Always the best way to go. Where are u located?

RngrYogi said:
Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
1. Just be fully stock including recovery.
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Click to expand...
Click to collapse
But... the phone must be connected on the pc? I can't detect the watch with adb devices..

I was wondering why I couldn't boot to the recovery directly so thanks a ton for the help! Also dayum, the speaker sure is quite loud for a smartwatch!
To the person above no, you do not need to have the phone to your pc connected for it to work.

got it installed like it so far, to me the speaker sounds alot better then the one in the gear s

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you dear XDA members for your advice on how to adb sideload
Sent from my LG-H815 using Tapatalk

Tried installing the naked drivers in the link but that fails, any suggestions?

str8spir said:
Thank you dear XDA members for your advice on how to adb sideload
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Very glad we could help! Just wanted everyone to be as happy as I was when I saw the file drop!

RngrYogi said:
Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
1. Just be fully stock including recovery.
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Click to expand...
Click to collapse
Thanks worked flawlessly...

ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost

chachin said:
ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost
Click to expand...
Click to collapse
Let me test mine and see if it is visible while waiting on the adb sideload update.zip command

No luck for me installing these drivers

chachin said:
ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost
Click to expand...
Click to collapse
C:\ADB>adb devices
List of devices attached
MQB7N15914000616 sideload
This is what I see while in sideload mode inside recovery. Not sure why its not working for you.:crying:

ADB not working - returns "unauthorized"

As title says, I cannot use adb: "adb devices" returns "UNAUTHORIZED" if I launch command with phone plugged in and in android environment.
If I try in bootloader mode, download mode or recovery mode it returns "list of attached device" like it is empty list and cant see phone.
Phone is M9 ViperOneM9 4.3.0 firmware 3.35.401.12 recovery TWRP 3.0.0.0.
I am using a Win 10 PC where ADB command is perfectly working with my other M9 (ViperOneM9 4.2.1 same firmware as above, TRWP 2.8.7.1).
I read various posts and the problem seems to be the phone not showing the prompt to accept RSA key.
Yes, I am with USB debug ON and install from unknow sources ON (this last is useless but I say the same).
I think to have tried most of everything people suggest in different posts:
- updated and reinstalled android sdk
- deleted adbkey and adbkey.pub in my %user%/.android folder (then it recreates files but still no prompt on phone)
- tried different versions of HTC drivers on PC
- tried different versions of adb (1.0.31, 1.0.32 and also a pre 1.0.30 I dont remember exactly which one)
- tried installing Minimal ADB and Fastboot [4-27-16] http://forum.xda-developers.com/show....php?t=2317790
- wiped everything from TWRP recovery under "advanced" button and reinstalled rom with wipe during aroma installer
- looking in the phone in "system/data/misc/adb" for adb keys files but my folder is empty (checked on my other fully working M9 and that folder is empty too)
- toggled USB debugging on/off rebooting phone and PC
I also tried setting up a virtual machine with Windows 7 but I am not able to install drivers for the phone (yellow triangle in device manager).
Set up a virtual machine with Debian 8.4.0, installed android-tools-sdk, updated last version and "adb devices" here return OFFLINE
What can i do? It is like 7 hour I am trying but nothing is working.
Any help is greatly appreciated.
Thanks everyone

I'm sure that first time using and, a window requesting to authorize your PC pops up on the phone. Have you ever seen this window and authorized the PC. If not you could toggle of USB debugging in developer options, restart phone, toggle debugging on.
Then I'd deactivate display standby, connect phone to PC, in CAD type: adb kill-server and after this adb devices. When the window pops up on your phone agree to it and allshould be fine.
Sent from my HTC One M9 using XDA Labs

Same here
I have the same problem, and also try many way.
Finally I have to flash another rom to solve it.
Have you solved on this Viper rom?

ok, I found a stupid solution.
Because adb is ok on another rom, so I copy this file.
/data/adb/adb_key
Restore it after flash Viper, and I finale can use adb debugging on Viper ROM.

adb device offline
:good::good::good:
aseeme555076 said:
ok, I found a stupid solution.
Because adb is ok on another rom, so I copy this file.
/data/adb/adb_key
Restore it after flash Viper, and I finale can use adb debugging on Viper ROM.
Click to expand...
Click to collapse
Copy adb_keys from another device to /data/misc/adb/adb_keys and setting permissions to 0640 for system:shell works for me, too.

bsdroid said:
setting permissions to 0640
Click to expand...
Click to collapse
THANKYOU!

Thaoldwise said:
As title says, I cannot use adb: "adb devices" returns "UNAUTHORIZED" if I launch command with phone plugged in and in android environment.
If I try in bootloader mode, download mode or recovery mode it returns "list of attached device" like it is empty list and cant see phone.
Phone is M9 ViperOneM9 4.3.0 firmware 3.35.401.12 recovery TWRP 3.0.0.0.
I am using a Win 10 PC where ADB command is perfectly working with my other M9 (ViperOneM9 4.2.1 same firmware as above, TRWP 2.8.7.1).
I read various posts and the problem seems to be the phone not showing the prompt to accept RSA key.
Yes, I am with USB debug ON and install from unknow sources ON (this last is useless but I say the same).
I think to have tried most of everything people suggest in different posts:
- updated and reinstalled android sdk
- deleted adbkey and adbkey.pub in my %user%/.android folder (then it recreates files but still no prompt on phone)
- tried different versions of HTC drivers on PC
- tried different versions of adb (1.0.31, 1.0.32 and also a pre 1.0.30 I dont remember exactly which one)
- tried installing Minimal ADB and Fastboot [4-27-16] http://forum.xda-developers.com/show....php?t=2317790
- wiped everything from TWRP recovery under "advanced" button and reinstalled rom with wipe during aroma installer
- looking in the phone in "system/data/misc/adb" for adb keys files but my folder is empty (checked on my other fully working M9 and that folder is empty too)
- toggled USB debugging on/off rebooting phone and PC
I also tried setting up a virtual machine with Windows 7 but I am not able to install drivers for the phone (yellow triangle in device manager).
Set up a virtual machine with Debian 8.4.0, installed android-tools-sdk, updated last version and "adb devices" here return OFFLINE
What can i do? It is like 7 hour I am trying but nothing is working.
Any help is greatly appreciated.
Thanks everyone
Click to expand...
Click to collapse
Install this driver manually from the device manager, the phone must be connected to the computer https://yadi.sk/d/TVkbNcXv3KP7mQ

[ROM][UNOFFICIAL] LineageOS 18.1 for Nexus 6P (angler)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Important Info:
To flash this rom you need TWRP 3.3.1.0 or newer.
Make sure you have the vendor, radio, & bootloader img's installed, from the stock oreo 8.1 OPM7.181205.001 Dec 2018 factory image.
They can be extracted from the factory image on google's site here. Or you can use the ones linked below that I already extracted:
vendor, radio, bootloader img's: https://androidfilehost.com/?w=files&flid=286833
The vendor img is flashable with twrp or fastboot. For the radio and bootloader img, use fastboot.
Instructions:
If updating from an unofficial lineage-18.1 build, follow the steps below:
If you don't already have them installed, flash the newest vendor, radio, and bootloader img's linked above.
Boot into TWRP.
Flash the ROM zip.
Reboot & enjoy.
NOTE: if you previously flashed gapps and/or the su addon, there's no need to flash them again. They will be automatically re-installed during rom zip installation.
If coming from a different ROM:
If you don't already have them installed, flash the newest vendor, radio, and bootloader img's linked above. also make sure you have the newest twrp, linked above.
Boot into TWRP.
Wipe system & data & cache partitions.
Format data.
Flash rom & GApps & su zips (GApps & su zips are optional).
Reboot & enjoy.
For more info or more detailed instructions, visit our wiki here.
Downloads:
Builds:
AndroidFileHost
Google Drive
Reporting Bugs:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Source Code:
Device Tree
Kernel Tree
Vendor Tree

Known issues
Constant System UI crashes.
Regular hiccups/freezes.
Broken Camera.
Bluetooth connectivity may vary.
Wi-Fi Hotspot.

Peripherals
FBE Recovery: TWRP
FBE Recovery (4 Core): TWRP
BLOD Patch (4 Core): boot.img

Pixelboot never fails to amaze us welcome lineage 18.1!

On the download sites there is just a file called
lineage-18.0-20200929-UNOFFICIAL-angler.zip
No LineageOS 18.1! Or what do I miss here?

After flashing lineage-18.0-20200929-UNOFFICIAL-angler, adb always reports device offline:
E:\>adb devices
List of devices attached
84D7Q15A12345678 offline
Even though I can see the following warning message at lock screen
USB debugging connected
Tap to turn off USB debugging
When booting to bootloader, fastboot doesn't report any device.
Recovery is wiped out. That is, I can no longer boot into recovery.
After booting into OS, when setting the usb connection to file transfer, PC cannot recognize my phone.
Any suggestion?

2ndLeaf said:
After flashing lineage-18.0-20200929-UNOFFICIAL-angler, adb always reports device offline:
E:\>adb devices
List of devices attached
84D7Q15A12345678 offline
Even though I can see the following warning message at lock screen
USB debugging connected
Tap to turn off USB debugging
When booting to bootloader, fastboot doesn't report any device.
Recovery is wiped out. That is, I can no longer boot into recovery.
After booting into OS, when setting the usb connection to file transfer, PC cannot recognize my phone.
Any suggestion?
Click to expand...
Click to collapse
I am having same problem. Any suggestion ?

After flashing lineage-18.0-20200929-UNOFFICIAL-angler, adb always reports device offline:
E:\>adb devices
List of devices attached
84D7Q15A12345678 offline
Even though I can see the following warning message at lock screen
USB debugging connected
Tap to turn off USB debugging
When booting to bootloader, fastboot doesn't report any device.
Recovery is wiped out. That is, I can no longer boot into recovery.
After booting into OS, when setting the usb connection to file transfer, PC cannot recognize my phone.
Any suggestion?
Click to expand...
Click to collapse
Reboot to bootloader. Connect the phone to pc, uninstall the driver in case of recognition, if not choose update driver. Once it pops up, select manually the adb bootloader interface driver. Open adb and do fastboot devices, it should appear. Also, switch usb port.

xxJMarian said:
Reboot to bootloader. Connect the phone to pc, uninstall the driver in case of recognition, if not choose update driver. Once it pops up, select manually the adb bootloader interface driver. Open adb and do fastboot devices, it should appear. Also, switch usb port.
Click to expand...
Click to collapse
Thanks for your suggestion. I check the device manager. My Windows PC already has nexus-6p driver installed. I try to upgrade it. Windows reports I already have the latest driver. The same usb port works for my other android phones. Only the nexus 6p doesn't work (it worked well before I upgraded to lineage-18.0-20200929-UNOFFICIAL-angler .)
BTW, I am able to copy files to my phone. Is there any way to reflash my phone to a different image by sideloading a program on phone? I try to sideload the play store app but the app always crashes.

2ndLeaf said:
Thanks for your suggestion. I check the device manager. My Windows PC already has nexus-6p driver installed. I try to upgrade it. Windows reports I already have the latest driver. The same usb port works for my other android phones. Only the nexus 6p doesn't work (it worked well before I upgraded to lineage-18.0-20200929-UNOFFICIAL-angler .)
BTW, I am able to copy files to my phone. Is there any way to reflash my phone to a different image by sideloading a program on phone? I try to sideload the play store app but the app always crashes.
Click to expand...
Click to collapse
Doesn't matter if it used to work or work for other phones... do the process... sometimes it doesn't recognize the proper driver... the easy test is... go to fastboot and connect the phone to the pc if you inspect the device manager and your phone is not listed as "Bootloader interface" then it will never be recognized on fastboot... is that simple... That's why you have to manually select it, to force windows use the driver you are selecting.
I know this process because it happened to other of my phones... i had to manually select the driver so it appear on fastboot and be able to flash through it

xxJMarian said:
Doesn't matter if it used to work or work for other phones... do the process... sometimes it doesn't recognize the proper driver... the easy test is... go to fastboot and connect the phone to the pc if you inspect the device manager and your phone is not listed as "Bootloader interface" then it will never be recognized on fastboot... is that simple... That's why you have to manually select it, to force windows use the driver you are selecting.
I know this process because it happened to other of my phones... i had to manually select the driver so it appear on fastboot and be able to flash through it
Click to expand...
Click to collapse
Thanks again for your reply. I can see Nexus 6P in device manager (see attached). Does that mean I already have proper driver installed? If not, could you point me to a wiki that I can follow to update the driver? I follow the link below to set up adb. It doesn't mention about driver:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
I downloaded the USB driver from the following site. But windows refuses to update the driver claiming I already have the latest.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com

I find this thread: https://forum.xda-developers.com/t/...sb-driver-installer-tool-for-windows.3999445/
I was able to enable the ADB interface. But "adb devices" still shows nexus 6p is offline.

2ndLeaf said:
I was able to enable the ADB interface. But "adb devices" still shows nexus 6p is offline.
Click to expand...
Click to collapse
That's a Known issue in this rom. Reflash stock images and then flash your desired Custom rom

2ndLeaf said:
I find this thread: https://forum.xda-developers.com/t/...sb-driver-installer-tool-for-windows.3999445/
I was able to enable the ADB interface. But "adb devices" still shows nexus 6p is offline.
View attachment 5217521
Click to expand...
Click to collapse
This is what you should see if you are in bootloader.
If you are in bootloader, windows shows the proper driver like in the image and you type fastboot devices, the device will show up and you will be able to reflash twrp if you want or do whatever

2ndLeaf said:
I downloaded the USB driver from the following site. But windows refuses to update the driver claiming I already have the latest.
Click to expand...
Click to collapse
The steps are... you boot into bootloader, connect the phone to pc. Select the device on device manager and click properties and then drivers. Then select update drive and select the option that says something like "choose manually", then select the other option that appears, says something like "choose from list" once you click that it will present to you a list of drivers and you manually select the bootloder interface driver. After doing that, it will work. Open adb, type fastboot devices and it will appear.

xxJMarian said:
The steps are... you boot into bootloader, connect the phone to pc. Select the device on device manager and click properties and then drivers. Then select update drive and select the option that says something like "choose manually", then select the other option that appears, says something like "choose from list" once you click that it will present to you a list of drivers and you manually select the bootloder interface driver. After doing that, it will work. Open adb, type fastboot devices and it will appear.
Click to expand...
Click to collapse
Thanks for the detail instruction. I am able to recover my nexus 6p. Hooray!!!

I had t
2ndLeaf said:
After flashing lineage-18.0-20200929-UNOFFICIAL-angler, adb always reports device offline:
E:\>adb devices
List of devices attached
84D7Q15A12345678 offline
Even though I can see the following warning message at lock screen
USB debugging connected
Tap to turn off USB debugging
When booting to bootloader, fastboot doesn't report any device.
Recovery is wiped out. That is, I can no longer boot into recovery.
After booting into OS, when setting the usb connection to file transfer, PC cannot recognize my phone.
Any suggestio
Click to expand...
Click to collapse
2ndLeaf said:
After flashing lineage-18.0-20200929-UNOFFICIAL-angler, adb always reports device offline:
E:\>adb devices
List of devices attached
84D7Q15A12345678 offline
Even though I can see the following warning message at lock screen
USB debugging connected
Tap to turn off USB debugging
When booting to bootloader, fastboot doesn't report any device.
Recovery is wiped out. That is, I can no longer boot into recovery.
After booting into OS, when setting the usb connection to file transfer, PC cannot recognize my phone.
Any suggestion?
Click to expand...
Click to collapse
I had the same issue and I really need help

I had t
2ndLeaf said:
After flashing lineage-18.0-20200929-UNOFFICIAL-angler, adb always reports device offline:
E:\>adb devices
List of devices attached
84D7Q15A12345678 offline
Even though I can see the following warning message at lock screen
USB debugging connected
Tap to turn off USB debugging
When booting to bootloader, fastboot doesn't report any device.
Recovery is wiped out. That is, I can no longer boot into recovery.
After booting into OS, when setting the usb connection to file transfer, PC cannot recognize my phone.
Any suggestio
Click to expand...
Click to collapse
2ndLeaf said:
After flashing lineage-18.0-20200929-UNOFFICIAL-angler, adb always reports device offline:
E:\>adb devices
List of devices attached
84D7Q15A12345678 offline
Even though I can see the following warning message at lock screen
USB debugging connected
Tap to turn off USB debugging
When booting to bootloader, fastboot doesn't report any device.
Recovery is wiped out. That is, I can no longer boot into recovery.
After booting into OS, when setting the usb connection to file transfer, PC cannot recognize my phone.
Any suggestion?
Click to expand...
Click to collapse
I had the same issue and I really need h
PixelBoot said:
Known issues
Constant System UI crashes.
Regular hiccups/freezes.
Broken Camera.
Bluetooth connectivity may vary.
Wi-Fi Hotspot.
Click to expand...
Click to collapse
Can't play videos

2ndLeaf said:
Thanks for the detail instruction. I am able to recover my nexus 6p. Hooray!!!
Click to expand...
Click to collapse
I flashed the lineage 18 on my nexus 6p without flashing gaps, device's offline recovery mode wiped I really need help

Thanks alot for android 11. but why it's stops?