Hey guys, I really need some help here, I'm not good at any of this stuff - my OPO just randomly got stuck on a boot loop, I have never played with the USB debugging or any of that or tried to flash anything else, I was using just stock cyanogen.
I've been reading around and I've downloaded all the drivers but still can't detect the device when I do the Shift + Right Click --> Run CMD "fastboot devices" or "adb devices".
I never enabled options such as the USB debugging or anything else, can someone please help me out? I'm really clueless to all of this stuff.
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
jchen221 said:
Hey guys, I really need some help here, I'm not good at any of this stuff - my OPO just randomly got stuck on a boot loop, I have never played with the USB debugging or any of that or tried to flash anything else, I was using just stock cyanogen.
I've been reading around and I've downloaded all the drivers but still can't detect the device when I do the Shift + Right Click --> Run CMD "fastboot devices" or "adb devices".
I never enabled options such as the USB debugging or anything else, can someone please help me out? I'm really clueless to all of this stuff.
Click to expand...
Click to collapse
joanquro said:
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
Click to expand...
Click to collapse
This, except that's the wrong button combo (power + volume down is for recovery). Use power + volume up to get to fastboot mode and then try the "fastboot devices" command.
Heisenberg said:
This, except that's the wrong button combo (power + volume down is for recovery). Use power + volume up to get to fastboot mode and then try the "fastboot devices" command.
Click to expand...
Click to collapse
I'm sorry for this mistake.
joanquro said:
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
Click to expand...
Click to collapse
Thanks for your advice. This is the big problem I'm having, I've downloaded the SDK slim, and the driver manager and the 15 second installer things and installed all of them but still can't manage to detect my phone on fastboot.
jchen221 said:
Thanks for your advice. This is the big problem I'm having, I've downloaded the SDK slim, and the driver manager and the 15 second installer things and installed all of them but still can't manage to detect my phone on fastboot.
Click to expand...
Click to collapse
What command are you using while in fastboot mode?
Heisenberg said:
What command are you using while in fastboot mode?
Click to expand...
Click to collapse
I'm using both
fastboot devices
adb devices
Fastboot devices comes back with nothing in the CMD box, ADB devices gives a message that says 'Devices:' but there are none listed.
jchen221 said:
I'm using both
fastboot devices
adb devices
Fastboot devices comes back with nothing in the CMD box, ADB devices gives a message that says 'Devices:' but there are none listed.
Click to expand...
Click to collapse
There's no point in using adb commands in fastboot because only fastboot commands work. What drivers do you have installed?
XDA Moderator
Transmitted via Bacon
Heisenberg said:
There's no point in using adb commands in fastboot because only fastboot commands work. What drivers do you have installed?
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
I've looked around for all sorts of drivers, I have the universal ADB, android SDK slim or something, is there a specific one I need?
jchen221 said:
I've looked around for all sorts of drivers, I have the universal ADB, android SDK slim or something, is there a specific one I need?
Click to expand...
Click to collapse
Uninstall whatever drivers you have installed, reboot your PC, install these drivers, reboot your PC, connect your phone, test fastboot (fastboot devices).
Heisenberg said:
Uninstall whatever drivers you have installed, reboot your PC, install , reboot your PC, connect your phone, test fastboot (fastboot devices).
Click to expand...
Click to collapse
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
jchen221 said:
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
Click to expand...
Click to collapse
I can't remember what capabilities the stock recovery has, but if it's there it's worth trying.
jchen221 said:
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
Click to expand...
Click to collapse
Heisenberg said:
I can't remember what capabilities the stock recovery has, but if it's there it's worth trying.
Click to expand...
Click to collapse
I managed to get it to work after resetting a bunch of the options, thanks so much for your help with this (even if I didn't get it to fastboot mode)
I have the same problem.
jchen221 said:
I managed to get it to work after resetting a bunch of the options, thanks so much for your help with this (even if I didn't get it to fastboot mode)
Click to expand...
Click to collapse
Hey bro, I have the same problem. Can you please explain me how did you resolve it? This would be of great help. Thanks.
pavanakshay said:
Hey bro, I have the same problem. Can you please explain me how did you resolve it? This would be of great help. Thanks.
Click to expand...
Click to collapse
for me too bro same problem please help me
---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------
Heisenberg said:
Uninstall whatever drivers you have installed, reboot your PC, install these drivers, reboot your PC, connect your phone, test fastboot (fastboot devices).
Click to expand...
Click to collapse
i too having the same problem bro the driver link is not working please send me the link thankyou in advance
i am also facing the same problem that phone loops into fast boot mode whenever turned on i do totally every kind of drivers softwares and etc like tenorshare but all in vain i guess at last that phone must be enabled usb debuging in order to be detected as a active adb device,i pratically do this stuff by using another phone with enabled debuging and it was an active device andd can be processed further but when i disabled the usb debugging of same phone it was not working with adb interface i hope you understand,,,,but a miracle happenend i removed the battery for about a week and suddenly i pluged and try to turn it on hola it starts from roms boot logo
HELP!!!!! Stuck on bootloop and fastboot not working
i was flashing twrp on infinix s4 withfast boot. after flashing the device is stuck on bootloop. the recovery is not accessible (i press the key combo nothing happens) and fastboot combination is also not working. i tried connecting it with adb cmd and ran the command "adb reboot bootloader" but no device is detected.
ps: the link for drivers is broken
Related
Google doesn't know, so maybe the experts here can help.
I'm trying to unlock the bootloader of my Nexus S 4G.
I installed drivers via PDAnet. USB Debugging is on. Windows detects the device, both when its on in normal mode, and in Fastboot mode. ADB detects the phone when on.
Fastboot won't detect it when in Fastboot mode, though!
ADB won't detect it in Fastboot, either. (But maybe that's normal.)
Why doesn't fastboot see it?
I'm running Win7 x64, if that helps.
Thanks in advance.
pennyfan87 said:
Google doesn't know, so maybe the experts here can help.
I'm trying to unlock the bootloader of my Nexus S 4G.
I installed drivers via PDAnet. USB Debugging is on. Windows detects the device, both when its on in normal mode, and in Fastboot mode. ADB detects the phone when on.
Fastboot won't detect it when in Fastboot mode, though!
ADB won't detect it in Fastboot, either. (But maybe that's normal.)
Why doesn't fastboot see it?
I'm running Win7 x64, if that helps.
Thanks in advance.
Click to expand...
Click to collapse
What happens when you type:
Fastboot devices
?
Sent from my Nexus S using XDA App
matt2053 said:
What happens when you type:
Fastboot devices
?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Nothing shows up. No errors. No devices.
Are you in bootloader mode when you're doing fastboot commands?
zephiK said:
Are you in bootloader mode when you're doing fastboot commands?
Click to expand...
Click to collapse
I'm in "fastboot mode", I think that's what its called.
I get there by holding Vol Up + Power when I turn it on.
pennyfan87 said:
I'm in "fastboot mode", I think that's what its called.
I get there by holding Vol Up + Power when I turn it on.
Click to expand...
Click to collapse
If you have the USB Driver from the SDK installed edit android_winusb.inf and add:
;Nexus S
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20&REV_0100
Go into device manager and tell it to update the driver, hit pick from list, all and have disk. Pick the INF and let it install.
pennyfan87 said:
I'm in "fastboot mode", I think that's what its called.
I get there by holding Vol Up + Power when I turn it on.
Click to expand...
Click to collapse
Search is your friend...
http://forum.xda-developers.com/showthread.php?t=878786
Please read the whole post for instructions...
Are you running command prompt as Administrator?
pennyfan87 said:
Google doesn't know, so maybe the experts here can help.
I'm trying to unlock the bootloader of my Nexus S 4G.
I installed drivers via PDAnet. USB Debugging is on. Windows detects the device, both when its on in normal mode, and in Fastboot mode. ADB detects the phone when on.
Fastboot won't detect it when in Fastboot mode, though!
ADB won't detect it in Fastboot, either. (But maybe that's normal.)
Why doesn't fastboot see it?
I'm running Win7 x64, if that helps.
Thanks in advance.
Click to expand...
Click to collapse
Hi, I had the same problem, I fixed it by giving the command prompt root permissions (I'm using Linux). On Windows, make sure the command prompt is running AS THE ADMINISTRATOR
I'm trying to get into fastboot
reboot while holding vol down
select the USB icon and press vol up
but I am stuck at "Starting Fastboot USB download protocol"
am i doing something wrong?
xdeslitx said:
I'm trying to get into fastboot
reboot while holding vol down
select the USB icon and press vol up
but I am stuck at "Starting Fastboot USB download protocol"
am i doing something wrong?
Click to expand...
Click to collapse
No you are doing it right. THAT IS IS FASTBOOT. If you run the fastboot commands from your pc you will see it working on the pc.
xdeslitx said:
I'm trying to get into fastboot
reboot while holding vol down
select the USB icon and press vol up
but I am stuck at "Starting Fastboot USB download protocol"
am i doing something wrong?
Click to expand...
Click to collapse
sbdags said:
No you are doing it right. THAT IS IS FASTBOOT. If you run the fastboot commands from your pc you will see it working on the pc.
Click to expand...
Click to collapse
The above is correct, you are in fastboot if you see this (similar to download mode on samsung devices for use with ODIN).
Be sure to add path to environmental variables so that you can use fastboot commands at prompt (if in NT (windows) environment)
sbdags said:
No you are doing it right. THAT IS IS FASTBOOT. If you run the fastboot commands from your pc you will see it working on the pc.
Click to expand...
Click to collapse
i tried running the command " fastboot devices" and it doesnt see my tf700
i have all drivers loaded
Poser said:
The above is correct, you are in fastboot if you see this (similar to download mode on samsung devices for use with ODIN).
Be sure to add path to environmental variables so that you can use fastboot commands at prompt (if in NT (windows) environment)
Click to expand...
Click to collapse
i added the path to environmental variables.
Fastboot works fine for me.
Suggest you go over to the nvflash thread and download the windows drivers.
---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------
xdeslitx said:
i tried running the command " fastboot devices" and it doesnt see my tf700
i have all drivers loaded
Click to expand...
Click to collapse
Isn't that adb commands you are trying to run. I.e., adb devices. I think you are confusing fastboot.
What are you trying to do?
sbdags said:
Fastboot works fine for me.
Suggest you go over to the nvflash thread and download the windows drivers.
---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------
Isn't that adb commands you are trying to run. I.e., adb devices. I think you are confusing fastboot.
What are you trying to do?
Click to expand...
Click to collapse
fastboot devices is also a fastboot command from what i understand...i was trying to run that command to see if the computer can even see my tablet in fastboot...which it doesnt.
and i actually did get the drivers from the nvflash thread because that's what i am trying to accomplish
what does your tablet look like when you are in fastboot mode?
because i am doubting the fact that mine is even in that mode...i get the feeling that it gets stuck when trying to load fastboot
xdeslitx said:
fastboot devices is also a fastboot command from what i understand...i was trying to run that command to see if the computer can even see my tablet in fastboot...which it doesnt.
and i actually did get the drivers from the nvflash thread because that's what i am trying to accomplish
what does your tablet look like when you are in fastboot mode?
because i am doubting the fact that mine is even in that mode...i get the feeling that it gets stuck when trying to load fastboot
Click to expand...
Click to collapse
It just says starting Fastboot mode. It never changes from that.
im going to try and uninstall/reinstall the drivers to see if thatll work
finally got it to work...had to reload my drivers
haha so i did the whole nvflash thing but i dont really know how it works
all i know is that itll keep me from bricking my tf700
xdeslitx said:
finally got it to work...had to reload my drivers
haha so i did the whole nvflash thing but i dont really know how it works
all i know is that itll keep me from bricking my tf700
Click to expand...
Click to collapse
You can still brick your device but it's 100% recoverable, at least if it's not a hardware failure. Just make sure to keep your backup files safe.
Pretoriano80 said:
You can still brick your device but it's 100% recoverable, at least if it's not a hardware failure. Just make sure to keep your backup files safe.
Click to expand...
Click to collapse
are there any instructions on how to recover using these files in case of brick?
i didnt see any on the thread under development
xdeslitx said:
are there any instructions on how to recover using these files in case of brick?
i didnt see any on the thread under development
Click to expand...
Click to collapse
There's no guide so far, but i'm sure you would get some help from xda users when needed.
cool thanks for the replies
I'm stuck at fastboot mode with my TF700. Windows XP recognizes my device but the command "fastboot devices" doesn't show up my TF700. I tried to reinstall drivers from univeral naked drivers package 0.7 with success - tried it three times. Bootet up TF700 in fastboot mode but still fastboot doesn't see my device.
Has anyone an idea what I can do? I tried it also in my virtual linux machine without succes. I want to flash new CWM recovery over old TWRP recovery to update to JB and after this to get proprietary files needed to build CM10 from sources.
As I understand, without fastboot, I can't update my bootloader to JB. Not a nice device...
thunderger said:
I'm stuck at fastboot mode with my TF700. Windows XP recognizes my device but the command "fastboot devices" doesn't show up my TF700. I tried to reinstall drivers from univeral naked drivers package 0.7 with success - tried it three times. Bootet up TF700 in fastboot mode but still fastboot doesn't see my device.
Has anyone an idea what I can do? I tried it also in my virtual linux machine without succes. I want to flash new CWM recovery over old TWRP recovery to update to JB and after this to get proprietary files needed to build CM10 from sources.
As I understand, without fastboot, I can't update my bootloader to JB. Not a nice device...
Click to expand...
Click to collapse
Try to use this command to check if fastboot it's working : " fastboot -i 0x0b05 reboot ". If your device reboot after sending that command it means you can use fastboot just fine.
To be honest i've seen many bricks reports from people that tried to only flash the JB bootloader so imo the best way to get the JB bootloader is to flash the official JB firmware, then install the latest TWRP OR CWM recovery via fastboot, use the custom recovery to make a backup of the stock rom. Once you've did all that you can install CM10 just fine but also you will have the opportunity to go back to stock JB in case you need to.
thunderger said:
I'm stuck at fastboot mode with my TF700. Windows XP recognizes my device but the command "fastboot devices" doesn't show up my TF700. I tried to reinstall drivers from univeral naked drivers package 0.7 with success - tried it three times. Bootet up TF700 in fastboot mode but still fastboot doesn't see my device.
Has anyone an idea what I can do? I tried it also in my virtual linux machine without succes. I want to flash new CWM recovery over old TWRP recovery to update to JB and after this to get proprietary files needed to build CM10 from sources.
As I understand, without fastboot, I can't update my bootloader to JB. Not a nice device...
Click to expand...
Click to collapse
Fastboot devices does not work on this device. I've used fastboot to swap recovery images several times and update to the JB bootloader by itself. It definitely works as a whole.
Pretoriano80 said:
Try to use this command to check if fastboot it's working : " fastboot -i 0x0b05 reboot ". If your device reboot after sending that command it means you can use fastboot just fine.
To be honest i've seen many bricks reports from people that tried to only flash the JB bootloader so imo the best way to get the JB bootloader is to flash the official JB firmware, then install the latest TWRP OR CWM recovery via fastboot, use the custom recovery to make a backup of the stock rom. Once you've did all that you can install CM10 just fine but also you will have the opportunity to go back to stock JB in case you need to.
Click to expand...
Click to collapse
I've tried this command many times, and all I ever get is < waiting for device > and nothing else. This is getting annoying as hell. I've tried so many different things, all with the same result. I guess I'll just have to wait until there is an exploit found to root the JB firmware without having to use fastboot, then use TWRP from Goomanager, and hopefully by then there will be a zip of CWM Recovery.
hi guys,
i my shield is stuck on the nvidia logo when booting normally, if it brings up the bootloader, it shows unlocked but hitting continue caused it to freeze on the screen, recovery freezes on nvidia logo and fastboot protocol just brings it back to this screen. i orginally installed twrp and it confirmed successful flash of new os .... on reboot it bricked to its now state, i cant get into twrp or get my pc to see it to install a new copy
anyone got any ideas
thanks
@Fairmax don't click continue, it freezes because there is nothing to continue to, as long as you can enter bootloader your device isn't fully bricked. So, to fix your problem you will have to download official ROM from nvidia's site (https://developer.nvidia.com/shield-open-source find your model and click recovery images).
When you download latest ROM unzip it and follow the textual guide, but, there will be one file missing (i can't remember which one, user data maybe or something like that), don't worry and just continue with the next step. After you flash just reboot to system by holding power button. Good luck !
i cant seem to get it to be recognised by windows all i get is this-- Windows has stopped this device because it has reported problems. (Code 43) A request for the USB device descriptor failed.--
trying to install nvidia usb driver via have disk bring up an error that the file is not usable with x64 system
ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd
Fairmax said:
ok after many driver reinstall iv got device manager to say android adb interface but still not showing on on device list in cmd
Click to expand...
Click to collapse
Which command did you type in?
fpozar said:
Which command did you type in?
Click to expand...
Click to collapse
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:
Fairmax said:
adb devices shows no devices
i tried the 3 different option in the driver install which was android adb, bootloader, and something else and nothing shows in devices. i tried it on my laptop and a different cable and cant get adb to list the device :crying:
Click to expand...
Click to collapse
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...
fpozar said:
Well of course adb devices shows no devices because you are not actually in adb mode, you are in the bootloader mode. Just download minimal fastboot and adb, install it and extract recovery image into the folder where you installed minimal adb and fastboot (you don't need any other drivers).After you did this and your device is in bootloader and connected, click on the path in your fastboot & adb folder and delete everything and type cmd. No need to do adb devices, just proceed with fastboot flash ...
Click to expand...
Click to collapse
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works
Fairmax said:
ah now that makes sence....silly me i dont do this very often . so fastboot saw device and iv uploaded all parts of the recovery image and rebooted but it is still stuck on the nvidia logo, that was the original file so now il try 5.2.0 and see if that works
Click to expand...
Click to collapse
You can also try flashing twrp and then lineageos or something from twrp.
fpozar said:
You can also try flashing twrp and then lineageos or something from twrp.
Click to expand...
Click to collapse
good news after a few hours of trying (usb dropped connection a few times then battery died) it finally works again .....been over 2 years since iv had this shield running after nvidia did the recall , now goto put a different rom on there so it dosnt update and kill itself
Hello I had a similar issue with my k1 tablet and ended up flashing factory images via adb fastboot and all flashed fine. Now my tablet is stuck on the boot screen with the green and white nvidia logo. How long does it take to boot please?
I have same issue too. I can load TWRP and flash the other partitions but TWRP shows un-mountable partitions and even a full stock ROM flash will not allow it to boot. I have a similar issue with a recall tablet. what did you do to fix it?
Hi, I have a OnePlus 6 that was running Pie Beta 3. Yesterday it rebooted on it's own and kept going to qualcomm crash dump mode. At that time, I was able to get into FastBoot but not recovery. I then used the MSMDownload Tool which completed successfully but now it only vibrates with a black/blank screen when I try to turn it on. If I keep holding the power button down, it vibrates every 3 seconds or so. Now I can't get into recovery or fastboot. The only thing I can do is see my phone in device manager by holding down vol+ when connecting it to my laptop.
Any ideas would be appreciated.
Thanks!
Update, now it keeps taking me to fastboot mode every time I turn it on (even while only pressing the power button). I still can't get in Recovery mode.
If you're in fastboot, you already won.
Get TWRP on the start (preferably from eng.stk) > plug in to your PC > fastboot boot twrp.img
You can also find the Stock boot image and run it, see if that helps. fastboot boot <whicheverfile>.img
matteosaeed said:
You can also find the Stock boot image and run it, see if that helps. fastboot boot <whicheverfile>.img
Click to expand...
Click to collapse
I found the stock image but I'm not sure how to put it on the phone with fastboot. Is there a tutorial some where?
I knew to all this stuff.
Thanks in advance!
Patrick
preilly44 said:
I found the stock image but I'm not sure how to put it on the phone with fastboot. Is there a tutorial some where?
I knew to all this stuff.
Thanks in advance!
Patrick
Click to expand...
Click to collapse
It is easy, you do not need to put it on the phone
You'll use this in cmd
fastboot boot (filename).img
Have you used fastboot before ?
matteosaeed said:
It is easy, you do not need to put it on the phone
You'll use this in cmd
fastboot boot (filename).img
Have you used fastboot before ?
Click to expand...
Click to collapse
Unfortunately, I have not used Fastboot before. I did install it with ADB but that's it.
I just connected the phone (device manager shows it's connected) and typed fastboot devices and it doesn't show any. I also tried fastboot boot filename.img and it just sits there "waiting for device" (even though DM shows it connected).
Any help would be appreciated. OnePlus remoted in and used the MSM tool which was successful but it still wouldn't boot so they told me to RMA it which will take about 10 days. I'm hoping to avoid that.
preilly44 said:
Unfortunately, I have not used Fastboot before. I did install it with ADB but that's it.
I just connected the phone (device manager shows it's connected) and typed fastboot devices and it doesn't show any. I also tried fastboot boot filename.img and it just sits there "waiting for device" (even though DM shows it connected).
Any help would be appreciated. OnePlus remoted in and used the MSM tool which was successful but it still wouldn't boot so they told me to RMA it which will take about 10 days. I'm hoping to avoid that.
Click to expand...
Click to collapse
Send me a message. I'll see what I can do.
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