Related
Hi, I've got a Nexus S 4g. I recently tried to flash it with the stock Jelly Bean image from Google's developer page - developers.google.com/android/nexus/images. While I was running flash-all.sh, the flash appeared to finish, and my terminal just said <waiting for device>. The device does boot up, and is functional, however, I can't get this thing to connect to any of my PCs via USB.
I've plugged it into my 12.10 Ubuntu laptop, and run lsusb. The device isn't listed at all, so adb doesn't work. I've also booted the phone into fastboot, and lsusb still doesn't list it (so fastboot devices doesn't list anything either). I've also plugged it into my Arch box, and tried the same steps with the same results. Before I flashed the phone, I was able to debug just fine on both machines.
Has anyone seen this behavior before? Is there any way to fix it? I've spent a bunch of time searching around for this problem, and haven't seen much. Thanks.
Well, crap. It looks like I flashed the wrong image to my phone. I've got a Nexus S 4G (d720), and it appears I flashed the i9020 image. That's what has probably caused my issue. Does anyone know if there's any way to recover from this?
Rephrase: Do you have unlocked bootloader?
Do you have adb and fastboot drivers installed?
Do you have debugging enabled in devoper settings?
kwibis said:
Rephrase: Do you have unlocked bootloader?
Do you have adb and fastboot drivers installed?
Do you have debugging enabled in devoper settings?
Click to expand...
Click to collapse
no need to have debbuging mode on
kwibis said:
Rephrase: Do you have unlocked bootloader?
Click to expand...
Click to collapse
Yes
kwibis said:
Do you have adb and fastboot drivers installed?
Click to expand...
Click to collapse
Yes
kwibis said:
Do you have debugging enabled in devoper settings?
Click to expand...
Click to collapse
Yes
The problem is that I flashed the wrong image to my device. I'm pretty sure it's hosed. The phone works fine - it boots up, I can get on wifi, but I just can't connect via USB. The image I flashed must have different USB drivers than what my device has. It looks like I'm stuck with it, or I will see if someone can "unbrick" it, and flash the proper image to it.
Well since you have unlocked bootloader I guess you have custom recovery and are rooted as well. You can download a custom rom, safe your app data with titanium backup, factory reset and wipe cache in recovery and flash proper rom. Then the drivers should work again and you can flash the correct image if wanted.
Sent from my Nexus S
The situation : I am unlocked with Clean Rom installed. I cannot get in recovery or fastboot but the tablet will boot to CleanRom
What I am thinking about doing is installing the ASUS Transformer Pad Infinity TF700T Firmware: V10.4.4.25 (for US SKU version only). It is my impression that the Firmware will reinstall the bootloader etc. Then reloading CleanRom.
Will this work?
RLGL said:
The situation : I am unlocked with Clean Rom installed. I cannot get in recovery or fastboot but the tablet will boot to CleanRom
What I am thinking about doing is installing the ASUS Transformer Pad Infinity TF700T Firmware: V10.4.4.25 (for US SKU version only). It is my impression that the Firmware will reinstall the bootloader etc. Then reloading CleanRom.
Will this work?
Click to expand...
Click to collapse
How would you install the firmware without recovery?
What happens when you try to get to the bootloader menu? (turn off, hold volume-down while switching on)
_that said:
How would you install the firmware without recovery?
What happens when you try to get to the bootloader menu? (turn off, hold volume-down while switching on)
Click to expand...
Click to collapse
Does that not install from the PC?
I can get to the menu, make a selection then is just hangs and doesn't load anything else.
RLGL said:
Does that not install from the PC?
I can get to the menu, make a selection then is just hangs and doesn't load anything else.
Click to expand...
Click to collapse
What do you select? RCK, Android, or USB? Caution: Don't select "wipe data" under any circumstances until your recovery is known to be good or you will hard brick your tablet.
_that said:
What do you select? RCK, Android, or USB? Caution: Don't select "wipe data" under any circumstances until your recovery is known to be good or you will hard brick your tablet.
Click to expand...
Click to collapse
Finally I am back where I was yesterday. I can now boot to recovery fastboot works BUT sideload does not work with either TWRP or CWM (device not seen) . I have Super SU installed Should I switch to Super user?
Any other ideas?
RLGL said:
Finally I am back where I was yesterday. I can now boot to recovery fastboot works BUT sideload does not work with either TWRP or CWM (device not seen) . I have Super SU installed Should I switch to Super user?
Any other ideas?
Click to expand...
Click to collapse
Looks like a problem with your PC/driver setup. SuperSU/Superuser has no effect in the recovery.
_that said:
Looks like a problem with your PC/driver setup. SuperSU/Superuser has no effect in the recovery.
Click to expand...
Click to collapse
so what is the missing link? The device when booted is seen by the PC ADB devices returns the S/N. My SDK is updated.
Sideload works with my DNA but with the tablet The return is "error device not found"
RLGL said:
so what is the missing link? The device when booted is seen by the PC ADB devices returns the S/N. My SDK is updated.
Sideload works with my DNA but with the tablet The return is "error device not found"
Click to expand...
Click to collapse
Which version of TWRP is installed?
Does "adb devices" work while the tablet is in recovery?
What does "lsusb" say (if you are using Linux) or Windows Device Manager? It may be that the recovery is using a different USB device ID than Android.
Which version of TWRP is installed?
2.4.3.0
Does "adb devices" work while the tablet is in recovery?
No
What does "lsusb" say (if you are using Linux) or Windows Device Manager? It may be that the recovery is using a different USB device ID than Android.
Asus Android Composite ADB Interface
RLGL said:
Asus Android Composite ADB Interface
Click to expand...
Click to collapse
I don't know much about the Windows USB drivers and how they decide which devices to drive - other than that it doesn't work for everyone. Is this the same device displayed as when you are running real Android? Also compare the detailed properties of the device when running recovery and Android.
Alternatively, try booting a live linux environment, obtain the adb binary from somewhere, and try it under Linux.
_that said:
I don't know much about the Windows USB drivers and how they decide which devices to drive - other than that it doesn't work for everyone. Is this the same device displayed as when you are running real Android? Also compare the detailed properties of the device when running recovery and Android.
Alternatively, try booting a live linux environment, obtain the adb binary from somewhere, and try it under Linux.
Click to expand...
Click to collapse
I don't do linux. I will try a different recovery version from TWRP. When the device is connected while in recovery the computer makes a different sound for connecting, as if there is something wrong with the recovery usb identifier
RLGL said:
I don't do linux. I will try a different recovery version from TWRP. When the device is connected while in recovery the computer makes a different sound for connecting, as if there is something wrong with the recovery usb identifier
Click to expand...
Click to collapse
I am down to a driver issue. Other than the driver that comes in the Asus sync software what else is there. My SDK is up to date.
I was given my friends tablet to try and fix for him. Basically the recovery (TWRP 2.5.0.0) cannot mount any partitions at all (and asks for a password for some reason - can be bypassed with the cancel button). The tablet will boot straight into the recovery mentioning that no OS is installed. I have attempted to boot into fastboot to flash an older version of the recovery (which I've read up on a few websites that say it will fix the mounting problem) however while pressing VOL DOWN and POWER it will boot up to the ASUS logo and no message appears about fastboot in the top-left. I'm out of ideas now and the only way I'll be able to fix this (from what I know) is either by flashing the ASUS firmware or an older version of TWRP via fastboot. Has anyone got any ideas on how I can fix this? Thanks.
EDIT: May be of reference https://github.com/TeamWin/Team-Win-Recovery-Project/issues/138
EDIT 2: I have finally solved the problem! I have quoted the important parts below in case anyone else has the same problem.
Basically I had some problems with the drivers the whole time on Windows 8. So what I did was disabled driver signature enforcement in Windows 8 (I think it re-enables after some time). I downloaded the drivers from this post and followed this other post , specifically this part:
jpasher said:
Making Windows recognize the TF300T
You will need to add the hardware IDs for the TF300T in the driver to make it recognize the ADB interface
Open the file android_winusb.inf in the naked drivers directory.
Look for the section titled [Google.NTx86] (for 32-bit systems) or [Google.NTamd64] (for 64-bit systems)
Add the following lines to make it recognize the TF300T hardware (it doesn't matter where, but I put it after the existing entries for the TF201 APX interface)
Code:
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C81&REV_0232&MI_01
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C81&MI_01
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C83&REV_0232
%AsusTransformerADBInterface% = USB_Install, USB\VID_0B05&PID_4C83
After the information is added, you should be able to install the drivers as usual for the device. If for some reason the device is still not recognized, you'll need to find its hardware IDs and add those to the file.
Click to expand...
Click to collapse
Then I booted up the tablet and connected to my computer. The drivers finally worked! I went into command prompt and typed "adb devices" and the device was there! Then I typed "adb reboot bootloader" and I got into the bootloader.
I had to look for the SKU too and since I couldn't find it cause I couldn't boot into Android it was in really small text in the bootloader at the top. Unfortunately after trying to flash the firmware in the bootloader it would not write over the system every time. So I followed this post instead: http://forum.xda-developers.com/showpost.php?p=49164067&postcount=167
After following the procedure it finally worked! Thanks cmendonc2 and everyone for your help, my friend is happy!
firtvid20 said:
I was given my friends tablet to try and fix for him. Basically the recovery (TWRP 2.5.0.0) cannot mount any partitions at all (and asks for a password for some reason - can be bypassed with the cancel button). The tablet will boot straight into the recovery mentioning that no OS is installed. I have attempted to boot into fastboot to flash an older version of the recovery (which I've read up on a few websites that say it will fix the mounting problem) however while pressing VOL DOWN and POWER it will boot up to the ASUS logo and no message appears about fastboot in the top-left. I'm out of ideas now and the only way I'll be able to fix this (from what I know) is either by flashing the ASUS firmware or an older version of TWRP via fastboot. Has anyone got any ideas on how I can fix this? Thanks.
EDIT: May be of reference https://github.com/TeamWin/Team-Win-Recovery-Project/issues/138
Click to expand...
Click to collapse
What bootloader is it on? It is on the top left corner of the screen wneh you enter the recovery menu in the bootloader.
cmendonc2 said:
What bootloader is it on? It is on the top left corner of the screen wneh you enter the recovery menu in the bootloader.
Click to expand...
Click to collapse
It doesn't say in TWRP recovery. When I boot the device straight up in the top-left corner it saw device is unlocked. However holding VOL DOWN does nothing and the tablet boots straight into TWRP
firtvid20 said:
It doesn't say in TWRP recovery. When I boot the device straight up in the top-left corner it saw device is unlocked. However holding VOL DOWN does nothing and the tablet boots straight into TWRP
Click to expand...
Click to collapse
You can still use fastboot in TWRP, but you will need to find the bootloader in order to figure out which recovery to flash over TWRP. There should be a fastboot command to find out.
cmendonc2 said:
You can still use fastboot in TWRP, but you will need to find the bootloader in order to figure out which recovery to flash over TWRP. There should be a fastboot command to find out.
Click to expand...
Click to collapse
Okay that's good to know. I am still unfortunately not able to get into fastboot. So I'll have to figure out what version the bootloader is before flash the firmware over.
Okay I got access to APX mode (useless from my understanding since my friends has no backups via nvflash), the bootloader while the recovery is loaded (although the driver isn't working for the bootloader), but I CANNOT GET INTO THE BOOTLOADER VIA VOLUME DOWN + POWER. Please help, somebody!
Here's a video explaining my problem.
firtvid20 said:
Here's a video explaining my problem.
Click to expand...
Click to collapse
Have you tried pressing the reset pin, then going into TWRP and going into ADB mode.
Then type ADB reboot bootloader and then try getting into fastboot by pressing volume down.
cmendonc2 said:
Have you tried pressing the reset pin, then going into TWRP and going into ADB mode.
Then type ADB reboot bootloader and then try getting into fastboot by pressing volume down.
Click to expand...
Click to collapse
Hmm I'll give that a go. Is ADB already on when I'm in TWRP? Otherwise how do I get into ADB mode?
firtvid20 said:
Hmm I'll give that a go. Is ADB already on when I'm in TWRP? Otherwise how do I get into ADB mode?
Click to expand...
Click to collapse
Its an option somewhere in TWRP called "ADB sideload".
cmendonc2 said:
Its an option somewhere in TWRP called "ADB sideload".
Click to expand...
Click to collapse
I tried it out but I get the the message "ADB Sideload Complete" and below it a message in red" Failed". I have it plugged into the computer and I didn't hear a connection sound.
I have also looked in Device Manager and there is the Transformer with no driver loaded with it. Further searching using the device information gave me this link: http://binarydb.com/driver/ASUS-Android-Bootloader-Interface-208738.html
EDIT: Found a driver on softpedia and installed it: http://drivers.softpedia.com/get/Ot...iver-4004-for-Vista-Windows-7-Windows-8.shtml Doesn't look like it's working though.
firtvid20 said:
I tried it out but I get the the message "ADB Sideload Complete" and below it a message in red" Failed". I have it plugged into the computer and I didn't hear a connection sound.
I have also looked in Device Manager and there is the Transformer with no driver loaded with it. Further searching using the device information gave me this link: http://binarydb.com/driver/ASUS-Android-Bootloader-Interface-208738.html
EDIT: Found a driver on softpedia and installed it: http://drivers.softpedia.com/get/Ot...iver-4004-for-Vista-Windows-7-Windows-8.shtml Doesn't look like it's working though.
Click to expand...
Click to collapse
While the ADB is attempting to connect, reinstall the naked drivers. If you are on Windows 8, use test mode.
cmendonc2 said:
While the ADB is attempting to connect, reinstall the naked drivers. If you are on Windows 8, use test mode.
Click to expand...
Click to collapse
Sorry, what is test mode? I am on Windows 8.
firtvid20 said:
Sorry, what is test mode? I am on Windows 8.
Click to expand...
Click to collapse
This should help: http://www.wugfresh.com/faq/8/
cmendonc2 said:
This should help: http://www.wugfresh.com/faq/8/
Click to expand...
Click to collapse
Hi cmendonc. I have already disabled driver signature enforcement. I have installed the drivers however I don't think I've had luck with them unfortunately.
firtvid20 said:
Hi cmendonc. I have already disabled driver signature enforcement. I have installed the drivers however I don't think I've had luck with them unfortunately.
Click to expand...
Click to collapse
Hmm. Try using a different USB cable ( if u have it) or a different USB port.
cmendonc2 said:
Hmm. Try using a different USB cable ( if u have it) or a different USB port.
Click to expand...
Click to collapse
I tried out both USB 2.0 and 3.0 ports on my computer but I still have the failed message come up. Any ideas still?
firtvid20 said:
I tried out both USB 2.0 and 3.0 ports on my computer but I still have the failed message come up. Any ideas still?
Click to expand...
Click to collapse
I vaguely remember someone posting that he succeeded to use adb/fastboot by installing a VirtualBox with Linux. You might have to search for the details.
Sent from my TF300T using Tapatalk
cmendonc2 said:
Hmm. Try using a different USB cable ( if u have it) or a different USB port.
Click to expand...
Click to collapse
Just an update. I got it working!! I did the following on this post to the universal drivers and then tried installing them on Windows 8. After booting my tablet to TWRP and plugging it in to my computer ADB works! I can reboot into fastboot now. Now I either have the option of flashing a JB compatible recovery or flashing the Asus firmware...
Since I'm not able to boot into Android would anyone be able to tell me what is the SKU on the picture below? So I can flash the correct firmware.
EDIT: Found it in the bootloader in small text. -.- It was the "WW" version.
Hello,
I just broke my nexus 5 screen but the device is still working. I'd like to retrieve some files from my phone before buying a new one, like pictures or SMS for example.
Here is what I can do :
- Boot in fastboot mode
- Flash a custom recovery (ex : TWRP)
Here is what is not working :
- Device is not recognized in Windows file folder, then I suppose that MTP is not enabled
- no developer mode enabled
- no USB debugging mode enabled
- Then ADB is not working
By the way, the device is not unlocked and not rooted.
I tried to flash and boot into TWRP mode but I don't know how to "drive" it from my computer as the device screen is not working.
Could somebody help me please ?
pilipe75 said:
Hello,
I just broke my nexus 5 screen but the device is still working. I'd like to retrieve some files from my phone before buying a new one, like pictures or SMS for example.
Here is what I can do :
- Boot in fastboot mode
- Flash a custom recovery (ex : TWRP)
Here is what is not working :
- Device is not recognized in Windows file folder, then I suppose that MTP is not enabled
- no developer mode enabled
- no USB debugging mode enabled
- Then ADB is not working
By the way, the device is not unlocked and not rooted.
I tried to flash and boot into TWRP mode but I don't know how to "drive" it from my computer as the device screen is not working.
Could somebody help me please ?
Click to expand...
Click to collapse
Then i suppose there is nothing you can do if almost nothing works and adb doesn`t recognise your phone, good luck mate
BTW next time enable google foto`s backup.
gee2012 said:
Then i suppose there is nothing you can do if almost nothing works and adb doesn`t recognise your phone, good luck mate
Click to expand...
Click to collapse
Using ADB would have been to easy
There is nothing I can do with a custom recovery ? or a modified boot ?
pilipe75 said:
Using ADB would have been to easy
There is nothing I can do with a custom recovery ? or a modified boot ?
Click to expand...
Click to collapse
You can`t, the bootloader is locked so you can`t flash custom stuff like a recovery. And even then you couldn`t know what buttons you`ld press if you can`t see what you`re doing.
gee2012 said:
You can`t, the bootloader is locked so you can`t flash custom stuff like a recovery.
Click to expand...
Click to collapse
I can unlock and root it, but I guess that it'll erase everything, right ?
pilipe75 said:
I can unlock and root it, but I guess that it'll erase everything, right ?
Click to expand...
Click to collapse
Unlocking the device wipes the device, so this kills the whole purpouse of your question. Might as well do nothing and get the phone repaired or buy a another one.
gee2012 said:
Unlocking the device wipes the device, so this kills the whole purpouse of your question. Might as well do nothing and get the phone repaired or buy a another one.
Click to expand...
Click to collapse
ok thanks for your help I'm still opened to news ideas if somebody is able to do miracles.
It's Christmas after all
pilipe75 said:
Here is what I can do :
- Flash a custom recovery (ex : TWRP)
By the way, the device is not unlocked and not rooted.
Click to expand...
Click to collapse
if bl is not unlocked... you won't be able to flash a custom recovery to use ADB to pull files.. so.. you're done here.
I maybe found a solution but I need a specific apk.
I may use the sideload mode to push and install a ROM or an apk. The best would be to push/install an apk from sideload mode, and this apk would automatically launch itself at device startup and will activate USB debugging mode which will allow me to fully use adb.
What do you think about that ? Would you know an apk which would do that ?
Or secondary option, push a specific ROM with USB debugging enabled by default. But I'm afraid that it could erase all my data.
Have you tried a TV out adapter?
rootSU said:
Have you tried a TV out adapter?
Click to expand...
Click to collapse
Great idea but i don't have any and, above all i'm afraid that the touch screen is not working either, so i'm not sure if it could really help
pilipe75 said:
Great idea but i don't have any and, above all i'm afraid that the touch screen is not working either, so i'm not sure if it could really help
Click to expand...
Click to collapse
Well I guess you're a bit stuck unfortunately.
Can you try ubuntu.
download a live cd version and boot into ubuntu or maybe a smaller version of linux (i know ubuntu works)
once booted into ubuntu plug in the phone.
usually linux can read the file system even when windows can't
You can't flash anything unsigned with stock recovery.
a hammerhead wrote this.
qnc said:
Can you try ubuntu.
download a live cd version and boot into ubuntu or maybe a smaller version of linux (i know ubuntu works)
once booted into ubuntu plug in the phone.
usually linux can read the file system even when windows can't
Click to expand...
Click to collapse
It's not working
pilipe75 said:
It's not working
Click to expand...
Click to collapse
We don't even know if your phone boots up... Does it ring when you call it?
rootSU said:
We don't even know if your phone boots up... Does it ring when you call it?
Click to expand...
Click to collapse
Yes it does. And it's responding in fastboot and sideload mode. So the phone is working, it's just the screen which ia dead.
The only way is to install a custom recovery. There is no other way. However as you said, unlocking the bootloader will erase everything.
pilipe75 said:
Yes it does. And it's responding in fastboot and sideload mode. So the phone is working, it's just the screen which ia dead.
Click to expand...
Click to collapse
... But your bootloader is locked and you think you have stock recovery and MTP mode doesn't work?
pilipe75 said:
Yes it does. And it's responding in fastboot and sideload mode. So the phone is working, it's just the screen which ia dead.
Click to expand...
Click to collapse
sorry that did not work.
when connected to ubuntu and you type "fastboot devices" do you get a response?
If so ubuntu can not browse file system in fastboot mode, you need to reboot back to the OS.
type fastboot reboot and when the phone reboots try to browse the file system.
hello guys
how do i root this phone please.
none of the google searched guides seem to work.
1. i've unlocked the bootloader using the asus app
2. i have adb installed on my pc
3. i've enabled usb debug mode on phone and allowing installation unknown apps
4. i've installed magisk v23 by downloading from github and just installing the apk file normally
5. i've downloaded a 2.9gb zip file from asus for androind 11 firmware onto phone and pc (but its a zip file that extracts a bin file, no image file)
my problem seems to be i don't know how to CREATE AND PATCH an image file or install twrp and install image file that way.
Could someone help, there doesn't seem to be any guides for rooting in this phones forum.
Look in the twrp thread: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/
after twrp you can flash the magisk.zip
Seosam said:
Look in the twrp thread: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/
after twrp you can flash the magisk.zip
Click to expand...
Click to collapse
i keep getting era waiting for device when i want to flash the phoben with twrp.
adb reboot bootloader (works and i enter the recovery menu start, bootloader, recovery, power off etc)
fastboot flash recovery_a twrp.img (when i type this cmd power shell just says waiting for device)
i have universal drivers installed and android sdk installed. not sure why it isn't recognising the phone?
When my phone is switched on normally, cmd recognises it, when i use adb devices. but as soon as i reboot into recovery mode using cmd "adb reboot bootloader" it stops recognising the phone on the list of devices using the cmd "adb devices"
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Seosam said:
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Click to expand...
Click to collapse
no answer from phone when in fastboot mode.
but i do get a reply in cmd when phone is switched on normally.
I'll try with another cable, but if it responds to adb when in normal mode. doesn't it mean it's not a cable issue but a software driver issue?
Seosam said:
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Click to expand...
Click to collapse
seems when i do adb reboot bootloader it goes into what i thought was called fastboot. It even says fastboot.
but in that mode my phone isn't recognised by cmd when type adb devices, it doesn't come up.
it has 4 options reboot system now, botloader, enter recovery, reboot to bootloader, power off.
if i then select enter recovery. it enters a smaller text screen with lots of small blue writing. when inside that screen (recovery mode) cmd seems to recognise my device.
but it says it is unauthorized. this is in recovery mode.
i'm not sure why it says it is unauthorized. i've authorised my pc to control the phone through the fingerprint, when the message popped up.
but i can't push the twrp.img file through because of this.
since cmd doesn't seem to recognise phone in fastboot mode.
and cmd doesn't seem to have authorisation in recovery mode.
any ideas?
is it possible to root using adb sideload or install twrp using adb sideload?
articoceanic said:
seems when i do adb reboot bootloader it goes into what i thought was called fastboot. It even says fastboot.
but in that mode my phone isn't recognised by cmd when type adb devices, it doesn't come up.
it has 4 options reboot system now, botloader, enter recovery, reboot to bootloader, power off.
if i then select enter recovery. it enters a smaller text screen with lots of small blue writing. when inside that screen (recovery mode) cmd seems to recognise my device.
but it says it is unauthorized. this is in recovery mode.
i'm not sure why it says it is unauthorized. i've authorised my pc to control the phone through the fingerprint, when the message popped up.
but i can't push the twrp.img file through because of this.
since cmd doesn't seem to recognise phone in fastboot mode.
and cmd doesn't seem to have authorisation in recovery mode.
any ideas?
Click to expand...
Click to collapse
Thats the right mode.
Does the phone at normal start show that the bootloader is unlocked?
Your debugging mode is turned on in developer settings?
A sideload isn`t possible I think.
Seosam said:
Thats the right mode.
Does the phone at normal start show that the bootloader is unlocked?
Your debugging mode is turned on in developer settings?
A sideload isn`t possible I think.
Click to expand...
Click to collapse
yes, shows bootloader is unlocked when i start the phone.
usb debugging mode is turned on.
i think for some reason in fastboot mode the device driver is not recognised in windows. have googled seems it was a very old problem that happned on phones 6 years ago. nut i haven't found anything recent to solve same error.
articoceanic said:
yes, shows bootloader is unlocked when i start the phone.
usb debugging mode is turned on.
i think for some reason in fastboot mode the device driver is not recognised in windows. have googled seems it was a very old problem that happned on phones 6 years ago. nut i haven't found anything recent to solve same error.
Click to expand...
Click to collapse
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
i think its definitely a driver issue. windows 10 seems to be overriding the drivers and installing wrong ones. and won't let me install right ones.
haven't tried in a different pc. will need to get hold of one and try.
Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
dont'know what happened. but weirdly i used usb 2.0 as you said and the driver listed on page 2 of this link got recognised.
[RECOVERY][OFFICIAL] TWRP for ASUS ZenFone 7 Series
*** Disclaimer *** All flashing is done at your own risk! While nothing from this thread should break your device, don't come back here blaming anyone if it does! Introduction Team Win Recovery Project 3.x, or twrp3 for short, is a custom...
forum.xda-developers.com
all this time windows 10 wouldn't let me install it. kept saying the drivers i already had was the best ones. but weirdly this time it did.
thanks friend. i think i have root access now. magisk keeps asking me to install the app tho. not sure why. i have version 23.0 installed.
but when i opne magisk it shows install icons for magisk and an unknown App. both listed as version 23.0.
Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
last question friend, thanks for all your help.
where do i download apps like ad block plus adaway minmingaurd etc.
magisk dowsn't seem to have an option for that.
articoceanic said:
last question friend, thanks for all your help.
where do i download apps like ad block plus adaway minmingaurd etc.
magisk dowsn't seem to have an option for that.
Click to expand...
Click to collapse
how solve com.asus.service keep stopping after install twrp? android 11 stock rom please answer
decade 1 said:
how solve com.asus.service keep stopping after install twrp? android 11 stock rom please answer
Click to expand...
Click to collapse
I'm not sure.
i only managed to root it by following the instructions here years ago.
maybe try updating the asus apps in play store? or ask some of the other people here who know more than me. or disable the asus apps. i don't use them.
sorry i couldn't help more
articoceanic said:
I'm not sure.
i only managed to root it by following the instructions here years ago.
maybe try updating the asus apps in play store? or ask some of the other people here who know more than me. or disable the asus apps. i don't use them.
sorry i couldn't help more
Click to expand...
Click to collapse
I try factory reset normal again I hope no recurrence