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.
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
Hi guys,
I wiped everything by mistake in TWRP 2.8.4.0 and now I'm puzzled... I did a FULL (yeah....) wipe before flashing a custom ROM, but then, everything was gone, of course.
I still have access to TWRP ; the bootloader is unlocked ; was on JB 4.2 .
So I tried to put a Rom back into the memory of the Tab, but :
1/ TWRP won't mount my SD card with a ROM on it... Does anyone have an idea why?
2/ adb doesn't recognize the device... but "fastboot devices" does! So I have access to all the fastboot commands.. Sadly, it doesn't flash any .zip.
So I'm guessing I have to solve the SD card problem OR flash a system.img with flashboot...?
I don't know what to do. I read that an older version of TWRP might mount my SDcard, but I'm quite scared to try and flash another recovery, since I'm not sure it will not definitely brick the thing.
Thanks for any answer
dandystrion said:
Hi guys,
I wiped everything by mistake in TWRP 2.8.4.0 and now I'm puzzled... I did a FULL (yeah....) wipe before flashing a custom ROM, but then, everything was gone, of course.
I still have access to TWRP ; the bootloader is unlocked ; was on JB 4.2 .
So I tried to put a Rom back into the memory of the Tab, but :
1/ TWRP won't mount my SD card with a ROM on it... Does anyone have an idea why?
2/ adb doesn't recognize the device... but "fastboot devices" does! So I have access to all the fastboot commands.. Sadly, it doesn't flash any .zip.
So I'm guessing I have to solve the SD card problem OR flash a system.img with flashboot...?
I don't know what to do. I read that an older version of TWRP might mount my SDcard, but I'm quite scared to try and flash another recovery, since I'm not sure it will not definitely brick the thing.
Thanks for any answer
Click to expand...
Click to collapse
Use MTP to get said file onto the tablet ??
Or install the drivers to enable adb ??
Thx Josh
lj50036 said:
Use MTP to get said file onto the tablet ??
Or install the drivers to enable adb ??
Thx Josh
Click to expand...
Click to collapse
Thanks for the reply
But the drivers are already installed, that's why I don't get why adb doesn't work.
as for the MTP, I can't get to it, since there is no ROM installed on the tab anymore : when I switch it on, it stays stuck on the ASUS logo, but is not detected by the computer.
Do you know where I could get an image of a stock firmware to flash with fastboot? or another way to push a file?
dandystrion said:
Thanks for the reply
But the drivers are already installed, that's why I don't get why adb doesn't work.
as for the MTP, I can't get to it, since there is no ROM installed on the tab anymore : when I switch it on, it stays stuck on the ASUS logo, but is not detected by the computer.
Do you know where I could get an image of a stock firmware to flash with fastboot? or another way to push a file?
Click to expand...
Click to collapse
MTP from with in TWRP has nothing to do with the ROM ?
Thx Josh
lj50036 said:
MTP from with in TWRP has nothing to do with the ROM ?
Thx Josh
Click to expand...
Click to collapse
Oh, ok sorry, I didn't understand.
Then what is the MTP on TWRP? Is it in " Advanced"/"File Manager"? Cause then I don't know how to use it...
dandystrion said:
Oh, ok sorry, I didn't understand.
Then what is the MTP on TWRP? Is it in " Advanced"/"File Manager"? Cause then I don't know how to use it...
Click to expand...
Click to collapse
Nope you should be able to plug it into a PC and move files to it drag and drop the zip ....
But you should still have adb working, it is a must have when messing with android ...
If you would like to look into this more drop me a hangouts at [email protected]
Thx Josh
Hi dandystrion,
Sorry i cant give an answer, but MTP should be activated per default at twrp and you should have your device as a drive on PC.
I'm intessted on how did you flash twrp on an unlocked bootloader? I fighting with my tf700 since October to unlock my bootloader to install CyanogenMod. I did a lots of tickets and RMA, which didn't helps.
Can you give me a link or a short explanation how I can flash twrp?
Thanks
schlombie said:
Hi dandystrion,
Sorry i cant give an answer, but MTP should be activated per default at twrp and you should have your device as a drive on PC.
I'm intessted on how did you flash twrp on an unlocked bootloader? I fighting with my tf700 since October to unlock my bootloader to install CyanogenMod. I did a lots of tickets and RMA, which didn't helps.
Can you give me a link or a short explanation how I can flash twrp?
Thanks
Click to expand...
Click to collapse
I unlocked the bootloader with the Transformer Toolkit v3.2.0 (I can't post a link since I'm a new member, but google it up, you'll find easily) and flashed TWRP 2.8.4 with fastboot without any problem. Hope it will work out for you.
lj50036 said:
Nope you should be able to plug it into a PC and move files to it drag and drop the zip ....
But you should still have adb working, it is a must have when messing with android ...
If you would like to look into this more drop me a hangouts at [email protected]
Thx Josh
Click to expand...
Click to collapse
Thanks man.
Well the PC does not see the tablet. I'm quite sure of my drivers since adb worked fine until I messed up (the drivers were installed through the latest version of Asus Pad Pc Suite)... I tried a adb sideload too : no connection.
I'll be glad to get some help.
Tried a thrid, empty brand new sdcard, and it did the trick.
Still don't know why adb wouldn't work, but now it's fine, so... :fingers-crossed:
Thanks for the help
I have checked it. But it is based on the Asus Unlock Tool, which doesn't work for me in the past!
Thanks
While recently trying to update my opo running cm11 I clicked install update but then it rebooted and just went to a black screen and did nothing. I rebooted it but it hadn't installed. I found my boot loader was locked and i had no recovery at all installed does anyone know how to fix this.
tom_clegg said:
While recently trying to update my opo running cm11 I clicked install update but then it rebooted and just went to a black screen and did nothing. I rebooted it but it hadn't installed. I found my boot loader was locked and i had no recovery at all installed does anyone know how to fix this.
Click to expand...
Click to collapse
Use fastboot & ADB guide for beginners. Download all required files so your PC can Connect to OPO VIA USB from PC. What PC OS do u use? Windows or Linux. Watch how to unlock boot loader, root, & install recovery tool or Return to stock OnePlus one YouTube video. Easiest start. Your phone will be OK. U need to down load drivers so u can use your PC to talk to your phone - pass instruction & activate 1+1 options. Install CM 11 or whatever ROM u want to use, as well as, 1+1 tools u may have lost is Recovery Tool.
Fstop said:
Use fastboot & ADB guide for beginners. Download all required files so your PC can Connect to OPO VIA USB from PC. What PC OS do u use? Windows or Linux. Watch how to unlock boot loader, root, & install recovery tool or Return to stock OnePlus one YouTube video. Easiest start. Your phone will be OK. U need to down load drivers so u can use your PC to talk to your phone - pass instruction & activate 1+1 options. Install CM 11 or whatever ROM u want to use, as well as, 1+1 tools u may have lost is Recovery Tool.
Click to expand...
Click to collapse
I use a mac and i tried to use a recovery tool however it says boot loader needed to be unlocked which mine wasn't and it wouldn't unlock because i had no recovery at all.
tom_clegg said:
I use a mac and i tried to use a recovery tool however it says boot loader needed to be unlocked which mine wasn't and it wouldn't unlock because i had no recovery at all.
Click to expand...
Click to collapse
You don't need a recovery to unlock the bootloader. Just boot it into fastboot mode, connect it to your Mac, and type 'fastboot oem-unlock' on the Terminal. Be careful, though, because you WILL lose ALL of your data!
Sent from my LG-V500 using Tapatalk
GXGOW said:
You don't need a recovery to unlock the bootloader. Just boot it into fastboot mode, connect it to your Mac, and type 'fastboot oem-unlock' on the Terminal. Be careful, though, because you WILL lose ALL of your data!
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
where do i find the files for mac with fast boot adb etc.
tom_clegg said:
I use a mac and i tried to use a recovery tool however it says boot loader needed to be unlocked which mine wasn't and it wouldn't unlock because i had no recovery at all.
Click to expand...
Click to collapse
Hmmm no recovery? When u hold down volume + power ?
Did u find the fastboot & adb tools for Mac?
What happens when u hold volume key up + power button at same time after turning device off?
What happens if u $fastboot devices -
Can u issue cmd "$fastboot oem unlock"
Know its frustrating but have to keep trying till u get in. Just have the rom files unzipped on your Mac ready to flash 1+1 when u get in. Its how I did it. When I wasn't able to but into recovery. Get on fastboot go thru OEM unlock, then flash 1+1. Follow the install script manually. Open script w plain text reader & just issue cmds following script. I don't trust scripts I + automation to get things unstuck.
tom_clegg said:
where do i find the files for mac with fast boot adb etc.
Click to expand...
Click to collapse
Use Google, there are plenty of guides available online. Once you have fastboot working the best thing to do is to flash the stock images with fastboot. I have detailed instructions in section 8a of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Please note that fastboot commands are slightly different on a Mac but you'll see that when you view a guide on how to set it up and use it.
Heisenberg said:
Use Google, there are plenty of guides available online. Once you have fastboot working the best thing to do is to flash the stock images with fastboot. I have detailed instructions in section 8a of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Please note that fastboot commands are slightly different on a Mac but you'll see that when you view a guide on how to set it up and use it.
Click to expand...
Click to collapse
would u be able to do a short one for mac that would help a lot with the commands
tom_clegg said:
would u be able to do a short one for mac that would help a lot with the commands
Click to expand...
Click to collapse
There's no point in duplicating my guide when all that's needed are a couple of extra characters prefixing each fastboot command.
Heisenberg said:
There's no point in duplicating my guide when all that's needed are a couple of extra characters prefixing each fastboot command.
Click to expand...
Click to collapse
is it just ./ then the command?
can i message you somehow maybe so it is quicker
tom_clegg said:
is it just ./ then the command?
can i message you somehow maybe so it is quicker
Click to expand...
Click to collapse
Dude, in the time it's taken you to ask these questions here you could have already found the answers online and completed the task. I'm here to help people but I'm not about spoon feeding, it doesn't benefit you in any way.
Heisenberg said:
Dude, in the time it's taken you to ask these questions here you could have already found the answers online and completed the task. I'm here to help people but I'm not about spoon feeding, it doesn't benefit you in any way.
Click to expand...
Click to collapse
fine then
tom_clegg said:
would u be able to do a short one for mac that would help a lot with the commands
Click to expand...
Click to collapse
at the point where i do fastboot oem unlock it reboots but stays at the boot screen.
tom_clegg said:
fine then
Click to expand...
Click to collapse
Don't get an attitude because I'm trying to help you help yourself.
tom_clegg said:
at the point where i do fastboot oem unlock it reboots but stays at the boot screen.
Click to expand...
Click to collapse
Issue the Mac equivalent of this command:
Code:
fastboot oem device-info
What does it return?
Heisenberg said:
Don't get an attitude because I'm trying to help you help yourself.
Issue the Mac equivalent of this command:
Code:
fastboot oem device-info
What does it return?
Click to expand...
Click to collapse
I type fastboot oem unlock and it is meant to reboot into android but however it stays stuck on the boot screen
tom_clegg said:
I type fastboot oem unlock and it is meant to reboot into android but however it stays stuck on the boot screen
Click to expand...
Click to collapse
That isn't what I asked you, if you want help you need to answer the questions that you're asked.
Heisenberg said:
That isn't what I asked you, if you want help you need to answer the questions that you're asked.
Click to expand...
Click to collapse
it says device tampered true
unlocked false
charge screen enabled false
tom_clegg said:
it says device tampered true
unlocked false
charge screen enabled false
Click to expand...
Click to collapse
Ok, try the unlock command again. What recovery did you previously have installed?
Heisenberg said:
Ok, try the unlock command again. What recovery did you previously have installed?
Click to expand...
Click to collapse
still the same thing sorry just stuck on boot screen.
i would have been able to do it its just this which i wasn't sure about :/
tom_clegg said:
still the same thing sorry just stuck on boot screen.
i would have been able to do it its just this which i wasn't sure about :/
Click to expand...
Click to collapse
You definitely can't boot into recovery? Most times not being able to get into recovery it's a case of user error. Hold volume down, then hold power (so you're holding them together), when you see the OnePlus boot logo let go of power but keep holding volume down until you reach recovery.
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
my pixel two screen died.. google backup restore joke service failed to restore sms or app setting to new phone. i need to grab that data from the old phone but cant see or use the screen, phone is not rooted and adb debugging not enabled. and i am not much more than a novice ahhhhhh!
The same happened to me. Try using vysor in pc. It shows your Mobile screen on pc. It worked for me. You dont need to install vysor n your mobile. Pc verion will auto install it on your device.
itsfaiez said:
The same happened to me. Try using vysor in pc. It shows your Mobile screen on pc. It worked for me. You dont need to install vysor n your mobile. Pc verion will auto install it on your device.
Click to expand...
Click to collapse
I tried vysor but it says ADB debugging has to be enabled
frankygoes said:
I tried vysor but it says ADB debugging has to be enabled
Click to expand...
Click to collapse
do you have recovery installed
itsfaiez said:
do you have recovery installed
Click to expand...
Click to collapse
yes. phone was rooted then got unrooted with ota upgrade to 11
frankygoes said:
yes. phone was rooted then got unrooted with ota upgrade to 11
Click to expand...
Click to collapse
is oem unlocked. if unlocked boot to download mode and install twrp for ur device boot into twrp i will givee access to your files
itsfaiez said:
is oem unlocked. if unlocked boot to download mode and install twrp for ur device boot into twrp i will givee access to your files
Click to expand...
Click to collapse
i cant see anything. so how would i boot into twrp?
or if anyone have the same model try to change the screen and use it and then return it
frankygoes said:
i cant see anything. so how would i boot into twrp?
Click to expand...
Click to collapse
shutdown device ( power + volume down).
power button + volume up WILL BOOT TO RECOVERY
did it work
you said boot to download or recovery?
frankygoes said:
you said boot to download or recovery?
Click to expand...
Click to collapse
if you have twrp intsalled boot to recovery it will give ccess to ur files
thanks for the help but im not sure if I had twrp after all . no matter what i can't get past the adb device "unauthorized" state. turns out the pixel2 is unique in not supporting usb-c to hdmi - thanks Google. i tried unified toolkit and vysor. next thing i might try is a hammer and send the pulverized phone back to Google.
frankygoes said:
thanks for the help but im not sure if I had twrp after all . no matter what i can't get past the adb device "unauthorized" state. turns out the pixel2 is unique in not supporting usb-c to hdmi - thanks Google. i tried unified toolkit and vysor. next thing i might try is a hammer and send the pulverized phone back to Google.
Click to expand...
Click to collapse
ok