Database Users

Nexus S ICS Problems Driver

prejudice to any forum.
I state that I'm an Italian who speaks no English, he writes, so forgive me for possible misunderstandings, but I'm posting the translation running google.
So are the owner of the Nexus 9023's version and then I wanted to try ICS via the Tools Cescomn I first unlocked the bootloader then root permissions and then I put a rom ics moddata atrraverso the recovery that I have changed as the guide told me. Then again, I want to change rom and then I decide to put the rom 4.0.3 Stock. So attraverlo the usb cable connected to the device I transfer the file ZD3PyN0t.zip from about 160MB. Reboot the device into fastboot recvovery I access the run and wipe and then install the rom. I was faced with the device locked with the recovery (after logging in and selecting the recovery fastboot I get black screen and then after a while you start the device) so everything is ok nothing anormale.Il problem is that there is to recognize the device in windows (both x32 and win7 win7 x64 win xp) I did the test with a nexus s aggiornatosi via ota to ics and then he immediately recognized the driver I've tried are good. Windows tells me unknown device unknown device or manually by selecting the driver. If you check the details of the device exactly match that of my friend who received ICS by ota.
What can I do?

try install google driver first
download it from here android sdk
this is the instruction
http://developer.android.com/sdk/win-usb.html

Done and redone.
facts of the problem occurs with my device, with that of a friend of mine (who has received ics via ota) no problem installing everything perfectly.
Putting it in download mode I recognized the same.
someone give me a tip?

Go to windows, manage devices, search for your phone, driver, update driver, select manually, choose android device and point it to the driver files. If it still does not work, i say you reflash your rom..
Sent from my Nexus S using XDA

Lazer Bear said:
Go to windows, manage devices, search for your phone, driver, update driver, select manually, choose android device and point it to the driver files. If it still does not work, i say you reflash your rom..
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
I tried many times to install the driver manually and do not go.
Now maybe I understand the problem .. a few days ago I got the ota update to 4.0.4 ics, the nexus has downloaded and installed.
The recovery tells me it's always locked, but after you press recovery from fastboot you press vol + + power and the recovery appears.
Turning the menu will not find anywhere the written MPT.
How can I fix?
The CWM does not make me install.
give me help.
thanks

[Q] Nexus 7 (2012) unlocked, but unrooted: waiting for device

I had an unlocked and rooted Nexus 7 (2012) with Android 4.2. After on OTA-Update I have an unlocked but _rooted_ Nexus 7. I read a lot about "waiting for device", but can't get it work anymore to connect. The device is reset and contains a fresh install without any added data.
I tried to follow http://forum.xda-developers.com/showpost.php?p=44179882
Step 2: Reboot the Nexus 7 into fastboot mode using the combination of volume up, volume down and power buttons
Click to expand...
Click to collapse
I can't get into fastboot with 3 buttons, but with Power and Vol- I see:
Product-Name - tilapia
Variant - tilapia
HU Version - PR
Bootloader Version - 4.23
Baseband Version - 1231_0.18.0_0409
Serial Number - ....
Signing - not signed yet
Lock state - unlocked
Maybe I am doing something wrong then, when I try to flash.
I see start, when I press the power button the N7 starts
When I change to recovery mode, I see "waiting for device" (USB debugging is on, the cable worked to unlock it)
Since I have an unlocked device, I tried only from Ubuntu 12.04 as root:
Code:
~# fastboot-linux flash recovery CF-Auto-Root-tilapia-nakasig-nexus7.img
Before I followed http://forum.xda-developers.com/showpost.php?p=44179882 I flashed recovery-clockwork-6.0.0.6-grouper.img
I could also install SuperSU 1.51, but root doesn't work and I found no way to install an updated SuperSU 1.51
BTW, I didn't know, that the grouper.img is the wrong one for my 3G device, UMTS worked fine with 4.2

try using nexus root toolkit. I had rooted prior to 4.3. when I updated, i just had to press one button to reroot(if you didn't use nexus root toolkit to begin with then you may need to go thru the driver setup)

Xanthius Balaraw said:
try using nexus root toolkit. I had rooted prior to 4.3. when I updated, i just had to press one button to reroot(if you didn't use nexus root toolkit to begin with then you may need to go thru the driver setup)
Click to expand...
Click to collapse
I will try it, also I hoped to use Linux.
http://www.wugfresh.com/nrt/
Configure your drivers if you haven’t already using the driver guide (If you aren’t sure use Step 3 of the driver guide to test your drivers).
Click to expand...
Click to collapse
Where do I get the drivers? Couldn't find a link there.
Edit: Since I have to go to a Windows PC, I downloaded the windows-programm only on my linux pc, it looks like the drivers are included in Nexus Root Toolkit: http://www.youtube.com/watch?v=iQhyerPfGes

I tried a lot with Windows XP 32bit and Windows 7 bit, but always I got "adb device was not found", but I saw a popup on the windows desktop with the Nexus after I attached the USB-cable. With Win7 I tried drivers 1-3, with XP driver 1.
With Linux something works:
Code:
adb devices
List of devices attached
<serial no> device
Code:
fastboot devices
<serial no> fastboot
Code:
~# fastboot flash recovery cf-auto-root-tilapia-nakasig-nexus7_92bf3da522bbb6e86725fe3290f391cc.zip
sending 'recovery' (6900 KB)...
OKAY [ 0.802s]
writing 'recovery'...
OKAY [ 0.332s]
finished. total time: 1.134s
But how can I install supersu? I don't know how to get the menu, where I can install zip-files.

lg-optimus said:
Where do I get the drivers? Couldn't find a link there.
Click to expand...
Click to collapse
There is a button in nrt to download and install drivers also to test to make sure they are working.

This forum is for the new 2013 Nexus 7 named Flo. You stated you have the 2012 verson...might want to go to the 2012 Nexus 7 forum here for advice.
On the 2013 Nexus 7 I use the volume button in bootloader/fastboot mode to switch to recovery, then select it with the power button to boot into the recovery you just flashed to the device. From there you can install Supersu (if you have downloaded the Supersu zip file to your device before hand).

geckocavemen said:
This forum is for the new 2013 Nexus 7 named Flo. You stated you have the 2012 verson...might want to go to the 2012 Nexus 7 forum here for advice.
Click to expand...
Click to collapse
This Guy ^

Oh, I am sorry to be in the wrong forum. What I found out in the menatime, that the stock-recovery is flashed everytime after a reboot, so there is no menu to flash zip-files after a new start.

lg-optimus said:
Oh, I am sorry to be in the wrong forum. What I found out in the menatime, that the stock-recovery is flashed everytime after a reboot, so there is no menu to flash zip-files after a new start.
Click to expand...
Click to collapse
I know it was in the wrong forum and all, but found something odd. I had a lot of trouble due to the same thing, waiting for device when trying fastboot. Just in case anyone arrives here: When you see the screen with the Start on top and FASTBOOT MODE in small red letters with the product specs, you're exactly where you should, no need to choose any option.
In my case, the fastbood mode doesn't work from linux (Kubuntu 13.10). It's just not detected, it makes no usb plugged sound, no icon on the tray...nothing. After some headaches just decided to boot to windows and try again. Fastboot mode, exactly as described, plug it to USB, and there you go, the "bop-beep" sound of usb plugged. I knew then it was gonna work on Windows.

Wrong forum *and* necro posting. Fantastic.
Sent from my Nexus 7 (2013) running 4.4

limbonik said:
Wrong forum *and* necro posting. Fantastic.
Sent from my Nexus 7 (2013) running 4.4
Click to expand...
Click to collapse
Thanks for your contibutive post. However I got there through google searches, that kept directing me to this thread. I imagined more people would get there searching for answers not finding them. By the way, the thread is from august, not so old.

install PDAnet on your device .. follow procedure of installation carefully ( should be installed on both pc and phone ) and when it was installed .when u enter your bootloader your phone will be recognize by your pc and wait for device will gone .
the method tested by me and took me one month two years ago to find .. on my g nexus first try to unlock .
PDAnet isntall drivers and everything you need to use adB commands ... if it helped give me thanks and let me know by pm .
PDA links
http://junefabrics.com/android/downloadold.php

[Q] I have a broken N7.

*** Returned my N7 (2012) as faulty and swapped with a 2013. Thread Ended. ***
I've been having trouble with my N7 (2012) for a while now.. Ever since the 4.3 update.. Slow response, hangs, and so on.
The latest 4.3 update would not install. Just a lying down droid with '!'.
My tablet was rooted using Wugfresh toolkit and was perfect before 4.3.
So i thought i'd go back to the start and use the toolkit to go back to root and flash stock+unroot.
Went through all instructions, it got to the part where it says ' You tablet will now reboot a few times. Please wait.'
Waited for 30 mins and nothing..
Now got a tablet with the google name and the unlock symbol. Options available are start, bootloader, recovery, off
All bring back to same screen.. Bootloader option displays -
Fastboot mode
PRODUCT NAME - tilapia
VARIANT = tilapia
HW VERSION - PR
BOOTLOADER VERSION - 4.13
BASEBAND VERSION - 1231_0.18.0_0409
SERIAL NUMBER - 015d88ffa8540a1c
SIGNING - not defined yet
LOCK STATE - UNLOCKED
During the flash boot to stock it wiped all directories etc so I now have an empty tablet..
Any ideas what I can do now? I would prefer to go back to stock 4.2 if possible... but if not, any help would be nice...

filking said:
I've been having trouble with my N7 (2012) for a while now.. Ever since the 4.3 update.. Slow response, hangs, and so on.
The latest 4.3 update would not install. Just a lying down droid with '!'.
My tablet was rooted using Wugfresh toolkit and was perfect before 4.3.
So i thought i'd go back to the start and use the toolkit to go back to root and flash stock+unroot.
Went through all instructions, it got to the part where it says ' You tablet will now reboot a few times. Please wait.'
Waited for 30 mins and nothing..
Now got a tablet with the google name and the unlock symbol. Options available are start, bootloader, recovery, off
All bring back to same screen.. Bootloader option displays -
Fastboot mode
PRODUCT NAME - tilapia
VARIANT = tilapia
HW VERSION - PR
BOOTLOADER VERSION - 4.13
BASEBAND VERSION - 1231_0.18.0_0409
SERIAL NUMBER - 015d88ffa8540a1c
SIGNING - not defined yet
LOCK STATE - UNLOCKED
During the flash boot to stock it wiped all directories etc so I now have an empty tablet..
Any ideas what I can do now? I would prefer to go back to stock 4.2 if possible... but if not, any help would be nice...
Click to expand...
Click to collapse
Hi, filking...
I have no experience with toolkits, so I can only advise you to download the Factory Image for your 'tilapia'/'nakasig' Nexus 7, and fastboot flash it.
Using fastboot isn't that difficult, and I'm at a loss to understand why toolkits have become so popular, when fastboot is so easy to use. Maybe people don't like command line interfaces...??
Anyway, there's a thread here which explains it all in detail.
Good luck.
Rgrds,
Ged.

Hi, thanks for the reply.
I think, in the world it is now, everyone is used to menus/mouse clicks to perform functions.
Anyway, I have read that thread already and my problem is when I get to the commands. All 'adb' commands don't work.
'adb devices' shows nothing.
I've tried in bootloader mode and recovery mode... All show a droid lying down. Fastboot mode shows the above message. Rest show, 'boot failed'
Help.....

filking said:
Hi, thanks for the reply.
I think, in the world it is now, everyone is used to menus/mouse clicks to perform functions.
Anyway, I have read that thread already and my problem is when I get to the commands. All 'adb' commands don't work.
'adb devices' shows nothing.
I've tried in bootloader mode and recovery mode... All show a droid lying down. Fastboot mode shows the above message. Rest show, 'boot failed'
Help.....
Click to expand...
Click to collapse
You don't need ADB to flash a stock image. ADB only works with a fully booted Android tablet. Indeed, if you have no bootable OS on your tablet, ADB is redundant and will not work.
You need to use fastboot...
What do you see when you type fastboot devices? (whilst the N7 is booted into the bootloader).
Rgrds,
Ged.

An update....
I went through wugs full driver setup part and deleted existing drivers. Installed the drivers again...
The device is detected on my PC.. But, seeing as it is stuck on the bootloader screen and I can't get into the system to turn on debugging, no adb commands work.
Device is listed as an 'unknown' android device when plugged in..
Seen a few other posts similar, but a lot say, 'it's ok, i've fixed it' without saying how.
anyone?

sorry, our posts must've been at same time..
Fastboot devices shows
015d88ffa8540a0c fastboot
*EDIT* Looks like i've misread the instructions in the post linked to above...
It got to the part where is said 'type in adb devices'... I read that, it didn't work, and I stopped.
BUT, I was already in bootloader mode, so didn't need that bit..
My error. (it's been a hot day!!! is that a good enough excuse.)
Continuing with the fastboot commands now... I'll update how it goes..
Thanks for replies.....

Update. All resolved.
I tried with the 4.3 img, but for some reason, it went through all the steps correctly. fastboot reboot resulted in the bootloader screen again.
Weird I thought, so I downloaded the 4.2.2 img and tried that and it worked perfectly..
Many thanks all who did, and it's a reminder to all. Re-read instructions..
:highfive::good:

HP slate 7 Extreme root tutorial plz!

Hey, I just bought a Hp slate 7 extreme and love it but i want to root my tablet. It was rooted using Vroot when my tab is 4.2.2. Now problem is someone or something has triggered the update to 4.3 and now i lost the root access. Tried using Vroot, onesuperclick and even the supertool by Tom but to no avail. There also towelroot but it make my tablet hanged and if i force close, it restarts the tab.
Also heard so much bad thing about 4.4.2 so i rather not up my os. Plz help me in my situation. I have check other threads and couldn't find a solution for this (at least for 4.3) would love a youtube video tutorial.
thank you

Sazz said:
Hey, I just bought a Hp slate 7 extreme and love it but i want to root my tablet. It was rooted using Vroot when my tab is 4.2.2. Now problem is someone or something has triggered the update to 4.3 and now i lost the root access. Tried using Vroot, onesuperclick and even the supertool by Tom but to no avail. There also towelroot but it make my tablet hanged and if i force close, it restarts the tab.
Also heard so much bad thing about 4.4.2 so i rather not up my os. Plz help me in my situation. I have check other threads and couldn't find a solution for this (at least for 4.3) would love a youtube video tutorial.
thank you
Click to expand...
Click to collapse
For starters this is the wrong Forum Thead to post in, it should be in the Q&A Forum.
Second you didn't use search as if you got here : http://forum.xda-developers.com/showthread.php?t=2541784 it will tell you with clear instructions on how to root the TegraTab.
Please insure that your threads are in the right place. I mean no disrespect but XDA have rules for a reason.

Ahh my bad, I'll try and be more careful. Now, I have read that link there already and it doesn't work. Also now my situation has worsen in that it got updated to 4.4.2.......I still tried all other methods, Vroot, towelroot, supertool etc . Tried to do the manual fastboot also doesn't work, impact or see no device so stuck over there. Has anyone found a way to root?

If Impactor does not find your device fastboot mode, try another USB port. If that doesn't work, try another computer if possible.
Also, make sure that you are running Impactor as administrator by right-clicking the application and pressing "Run as administrator".

Edit: this is a different device

I did try other computers and still no avail, even with admin access. Also HP slate 7 extreme is basically a Tegra note 7 not different device. Just few minor changes. If only the fastboot work, i probably be rooted by now. Is there a way to back 4.2.2? like put the recovery 4.2.2 in sd and recover from the loader? would it brick my device? Also i found out about towelroot modstring, is there a specific modstring for hp 7 extreme? would like to try it.
thank you

Sazz said:
I did try other computers and still no avail, even with admin access. Also HP slate 7 extreme is basically a Tegra note 7 not different device. Just few minor changes. If only the fastboot work, i probably be rooted by now. Is there a way to back 4.2.2? like put the recovery 4.2.2 in sd and recover from the loader? would it brick my device? Also i found out about towelroot modstring, is there a specific modstring for hp 7 extreme? would like to try it.
thank you
Click to expand...
Click to collapse
In this case unlock bootloader
Flash TWRP and check if it works, if so flash supersu

Hey shaky, thank you for replying. he boot loader is still lock. When device off , I press power n vol up to get into this menu which has fastboot protocol, selected it but nothing happens, then check for driver in impactor, no device detected. So can't use Tom's supertool to unlock bootloader. Also did the command prompt, say fastboot not recognize internal or external etc....
There also a recovery kernel, which leads to a recovery menu that can open zip files, think I can do just flash twrp ?
Thanks

Sazz said:
Hey shaky, thank you for replying. he boot loader is still lock. When device off , I press power n vol up to get into this menu which has fastboot protocol, selected it but nothing happens, then check for driver in impactor, no device detected. So can't use Tom's supertool to unlock bootloader. Also did the command prompt, say fastboot not recognize internal or external etc....
There also a recovery kernel, which leads to a recovery menu that can open zip files, think I can do just flash twrp ?
Thanks
Click to expand...
Click to collapse
Install the drivers when the menu shows up, don't select anything at all.

Sazz said:
Hey shaky, thank you for replying. he boot loader is still lock. When device off , I press power n vol up to get into this menu which has fastboot protocol, selected it but nothing happens, then check for driver in impactor, no device detected. So can't use Tom's supertool to unlock bootloader. Also did the command prompt, say fastboot not recognize internal or external etc....
There also a recovery kernel, which leads to a recovery menu that can open zip files, think I can do just flash twrp ?
Thanks
Click to expand...
Click to collapse
Install fastboot drivers then go to your boot loader menu and type
Fastboot flash recovery twrplocation.IMG, this will flash twrp then boot into twrp (recoverykernel) install SuperSU

Thanks for replying. I did all that was suggested and nothing has changed. Problem is that impactor won't detect my device and won't install driver.
Took these pics to show what i'm seeing (left to right)
1) First pic is when tab is off, I power and vol up to get that menu,
2) Second pic impactor can't detect anything.
3) Third pic is if i select Recovery Kernel, a No command show, did power and Vol up to get this recovery menu

What does the Device Manager show? For instance, when the tablet is in the recovery menu, can you see an unidentified device?
EDIT: What operating system are you running? Are you an administrator? Are you running Impactor as administrator?

In recovery mode, nothing shows up in device manager
In normal tab mode, it show android phone with subset android composite adb interface. Also there a ? MTP

anyone?

Update! : I exchange my tab, now its 4.2.2 and just rooted it with vroot. Voila surprise that towelroot and impactor still not working....
now that its rooted, is there a way to install cmw/twrp? tried the supertool but no luck with impactor so can't fastboot command.
can i just put cmw or twrp in sd and flash it from the android revocery menu?
thanks

Bump....could use some expertise help here
Thank you

From the sound of it you are rooted but not unlocked. So, flashing Roms and things will not work until you do that.
However if I am wrong and you have unlocked the boot loader, go right ahead and flash some ROMs.

I found off another thread that our HP S7E running kitkat can be rooted with towelroot v1. It's a one-click root method. Just download the apk, install and run it, and the tablet will be rooted! Just take note to install supersu from the play store

Root 4.4.2 HP Slate 7 Extreme
See my tutorial here: http://forum.xda-developers.com/nvidia-tegra-note-7/help/root-4-4-2-hp-slate-7-extreme-t2850893

HP Slate 7 Beats Special Edition
Hello new to this thread. Wanted to ask if this root method would work on the HP slate 7 beats special edition, the beats special edition looks very similar to the HP slate 7 extreme, and also the Nvidia Tegar note 7.

Unable to hack Asus Zenfone Laser 2 [ZE550KL - Z00L - Z00LD]

Hi to all.
I landed on XDA because I am not able to hack my Asus Zenfone Laser 2 dual-sim (ZE550KL, which seems to be also called as Z00L or Z00LD... I don't know why... ?!? ). Actually I'm very new on smartphone hacking, so I did my best recently to understand what "rooting", "recovery", "brick" etc mean.
I tried to enter this world because my phone gets gradually very slow as I use it and so I supposed that erasing the pre-installed applications and overclocking it would help, possibly installing a lighter and more performing custom rom. In order to do this I read that in short I have to unlock the boot loader, root the phone and then eventually install a custom rom. In fact I suppose that getting root privileges should already do the job by keeping the original rom, unistall all unwanted apps and eventually overclocking it. Is that correct?
However, the problems I found on my way are the following two:
I've not been able to follow those procedures on Linux. In detail, I'm not able to use "fastboot boot" instruction because it gets stuck on "waiting for any device". The device is listed and allowed when running "adb devices", the boot had been unlocked previously, the phone is in debug mode etc... but the problem is still there despite I've been trying with both the adb package included in the repositries and the one downloaded from the related google page. I've been told it may be a matter of USB drivers, so I also installed the android studio package thinking it would help, but I was wrong. I'm quite confused on this, despite I do hope I can hack my phone using my favourite operating system (I'm a Linux user since 2006). If you do not feel like helping on this then I will try on Windows.
After trying the same procedures on Windows 10, I realised that the Android Usb drivers released by Google did not work. I had to install the proprietary ASUS USB Drivers from the official website and only then I was able to overcome on Windows the same "waiting for any device" I had experienced on Linux. However, the phone "bricks". I suppose this should be the technical term used in this field to tell that the phone gets stuck for hours on the boot animation. I tried several times to reboot it, but each time the same story.
Maybe the problem on Linux is that I do not have the proper Android Device Usb drivers installed. In this case, how to solve the problem taking into account that ASUS only released the drivers for Windows?
RECAP: I have my phone bricked now (Android is unable to reboot, but I can do access both to the Power+VolumeUP menu (by the way, what's the name of this menu? Fast boot?) and the Power+VolumeDOWN menu (by the way, what's the name of this menu? Recovery boot?)
So sorry for the long story.
Hope you can help.
Thanks for your attention and best regards.

Uhm... no replies till now?

i dont know how you get this kind of trouble, maybe try other computer? , im using wondows 10, download small package of of fastboot driver and adb driver, flash twrp using fastboot command. all done. then i make full backup using twrp, next flash magisk .now i have root access, any problem or bootloop i just restore the full backup that work.
---------- Post added at 04:53 PM ---------- Previous post was at 04:22 PM ----------
i see a lot of this zen2 laser got bricked on this general forum , you should read some more if that could help

When I had this device, I remember booting a temporary recovery TWRP and rooted it in that recovery. Then once I got rooted, I installed TWRP app and installed a permanent recovery from within the TWRP app, which needed root of course. Then I got everything working.
You can try booting on a temporary TWRP using fastboot then flash supersu or magisk or whatever rooting client you want. Though, I think you need an unlocked bootloader. I'm sure there's a guide around here somewhere

I'm using a Z00T and just installed LineageOS yesterday using Windows 10, following a guide by Android Authority and LineageOS.
Volume Up + Power = Fastboot
Volume Down + Power = Recovery
Sounds like you can get into Fastboot, so I'm wondering if maybe you can use it to flash the recovery image??? (I'm not a dev in any form; try this at own risk)
I'm assuming you unlocked the bootloader already...
In the directory where all your images are, perhaps try flashing the recovery with the following, where RECOVERY.img is whatever you may have renamed the TWRP image to be:
Code:
fastboot flash recovery RECOVERY.img
After it's finished flashing, turn off the phone, then reboot into recovery mode with Volume Down + Power.

Something Similar happened with my phone and looking for answer
Hi All,
I'm new to this but do some hands on reading these forums. Recently i don't know how but my phone continuously boot into Fast-Boot mode. If I try to push some zip file as mentioned i'm getting error related to partition. "failed to write partition."
Can someone help me out with this.
Thank in advance.
CerealKiIIel said:
Hi to all.
I landed on XDA because I am not able to hack my Asus Zenfone Laser 2 dual-sim (ZE550KL, which seems to be also called as Z00L or Z00LD... I don't know why... ?!? ). Actually I'm very new on smartphone hacking, so I did my best recently to understand what "rooting", "recovery", "brick" etc mean.
I tried to enter this world because my phone gets gradually very slow as I use it and so I supposed that erasing the pre-installed applications and overclocking it would help, possibly installing a lighter and more performing custom rom. In order to do this I read that in short I have to unlock the boot loader, root the phone and then eventually install a custom rom. In fact I suppose that getting root privileges should already do the job by keeping the original rom, unistall all unwanted apps and eventually overclocking it. Is that correct?
However, the problems I found on my way are the following two:
I've not been able to follow those procedures on Linux. In detail, I'm not able to use "fastboot boot" instruction because it gets stuck on "waiting for any device". The device is listed and allowed when running "adb devices", the boot had been unlocked previously, the phone is in debug mode etc... but the problem is still there despite I've been trying with both the adb package included in the repositries and the one downloaded from the related google page. I've been told it may be a matter of USB drivers, so I also installed the android studio package thinking it would help, but I was wrong. I'm quite confused on this, despite I do hope I can hack my phone using my favourite operating system (I'm a Linux user since 2006). If you do not feel like helping on this then I will try on Windows.
After trying the same procedures on Windows 10, I realised that the Android Usb drivers released by Google did not work. I had to install the proprietary ASUS USB Drivers from the official website and only then I was able to overcome on Windows the same "waiting for any device" I had experienced on Linux. However, the phone "bricks". I suppose this should be the technical term used in this field to tell that the phone gets stuck for hours on the boot animation. I tried several times to reboot it, but each time the same story.
Maybe the problem on Linux is that I do not have the proper Android Device Usb drivers installed. In this case, how to solve the problem taking into account that ASUS only released the drivers for Windows?
RECAP: I have my phone bricked now (Android is unable to reboot, but I can do access both to the Power+VolumeUP menu (by the way, what's the name of this menu? Fast boot?) and the Power+VolumeDOWN menu (by the way, what's the name of this menu? Recovery boot?)
So sorry for the long story.
Hope you can help.
Thanks for your attention and best regards.
Click to expand...
Click to collapse

hey I have the same issue im on windows 10 and asus hasn't realeased drivers for asus zenfone laser connectivity so It wont show up no matter what I do, and the windows 7 drivers cant be used.

BlondebigboobsIRL said:
hey I have the same issue im on windows 10 and asus hasn't realeased drivers for asus zenfone laser connectivity so It wont show up no matter what I do, and the windows 7 drivers cant be used.
Click to expand...
Click to collapse
I'm using Z00T and Windows 10. Had no issues using the Android Authority and LineageOS guides.

These guides are great but I don't want to lose my data by formatting my bootlooping device, and the drivers asus gives do not work with windows 10, the adb drivers work fine but the asus drivers do not.