*update*
So now I can't access recovery nor fastboot. Any ideas how to fix that?
*original post*
So, I was dicking around with this zenfone 5 aaaaand I managed to get it stuck in bootloop. Being the epitome of calmness I panicked and screwed up more. Anyway, here's the brass tacks.
The phone is bricked, I can still access droidboot but that's it. I can flash fastboot.img and recovery.img, but can't find device when trying to adb sideload the rom, because I didn't install the adb drivers earlier. The way I see it, I can't flash new roms till I somehow magically able to install adb drivers without being able to boot into the phone and turn on usb debugging.
So, I need help. Is there some way I can still somehow shove adb drivers into this?
Click to expand...
Click to collapse
After a bit of googling, I found out that TWRP has mount feature and I flashed that through fastboot. And then I mounted the phone and managed to install adb driver that way. Then to install the rom I got from asus site, I flashed the fastboot and recovery image that corresponds to the rom, aaaaaaaaaand now I lost droidboot for some reason. Every attempt to boot goes to recovery, so I can't adb sideload anything now. But I got recovery, so yay?
I forgot the question. How do I proceed from this? (My current condition= Nothing is working except recovery)
Go to http://forum.xda-developers.com/showthread.php?p=64331311
INSTALL ADB DRIVERS
yasin0005 said:
Go to http://forum.xda-developers.com/showthread.php?p=64331311
INSTALL ADB DRIVERS
Click to expand...
Click to collapse
Yeah I did that. It's just that, now it's stuck at "Asus, in search of incredible". No droidboot, no recovery.
install intel driver !!
Related
Hi, these days I adb sideloaded android 4.3 on my Nexus 4. adb worked like a charm at this time. Now I wanted to root my phone (til now the phone was on stock recovery), but since 4.3 the device is not recognized by adb anymore when in stock recovery mode. So something changed during the update and i can´t communicate with my device anymore in recovery. I know that there is a similar thread on this topic, but my computer runs Archlinux 64-bit, therefore I started this new topic.
I would be happy if you could help me rooting my device.
You need to flash a new recovery in fastboot mode first, then flash the SU package
EddyOS said:
You need to flash a new recovery in fastboot mode first, then flash the SU package
Click to expand...
Click to collapse
Thank you for your answer. The problem is that the bootloader is still locked, so I wanted to open it with adb first.
If you unlock it and flash a custom recovery straight away before rebooting you shouldn't lose any data
But thats the problem, I can´t open the bootloader because adb doesn´t recognize my device when it is in recovery mode, but only when booting it up normally. So I can´t open the bootloader and flash a custom recovery.
EDIT: I was able to open the bootloader with fastboot instead of adb. Everthing went fine and I`m rooted now. Thank you for your help.
p53se said:
But thats the problem, I can´t open the bootloader because adb doesn´t recognize my device when it is in recovery mode, but only when booting it up normally. So I can´t open the bootloader and flash a custom recovery.
EDIT: I was able to open the bootloader with fastboot instead of adb. Everthing went fine and I`m rooted now. Thank you for your help.
Click to expand...
Click to collapse
That's what I said in the first place, you can only unlock using fastboot
I've found a driver that works fine for me on another XDA thread...
download.clockworkmod.com/test/UniversalAdbDriverSetup6 .msi
I'm on win8 and i was having the same trouble with ADB in recovery, after installing these, no problem!
Thank you for your answer. I´m sorry for the misunderstanding, but everything works like a charm now.
I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!
There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Added:
If you can't find a patched version, flash cwm or philz recovery with fastboot, adb is working on both of those. You just need a rrcovery image and do
"fastboot flash recovery <recovery-file>.img"
In fastboot mode.
let's try it out!
nvan7891 said:
There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Click to expand...
Click to collapse
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!
alkkade said:
I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!
Click to expand...
Click to collapse
i dont know how to fix your problem but i know how u can change the devices not found
install on your computer pdanet driver.
p.s.
i ****ed up my phone as well today i publish a post i will be thankfull if look on my problem.thanks.
alkkade said:
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!
Click to expand...
Click to collapse
See the edit to my first response. Fastboot is done in fastboot mode, not recovery, so you should be good. You just need the basic .img file of cwm or philz recovery.
If you are on win 7 try this:
http://adbdriver.com/downloads/
(Adb driver installer)
Run it when you turn adb sideload on in G2 and connect it to PC.
If it fails you still can go buy somewhere USB OTG cable (few bucks) and flash ROM from usb stick like me.
It appears that accessing fastboot pn the lg g2 is not so simple. Sorta like samsung phone deal, where a manufacturer download is used instead. From what I gather, recovery might need to be wiped to access fastboot, which you could do from terminal in twrp, but thats risky. Apparently, a lot of people have gotten stuck in fastboot mode. Best bet would be to reflash stock firmware through lg download mode. Also see this thread for a method to return to stock firmware:
http://forum.xda-developers.com/showthread.php?t=2432476
Once you are back to stock, just reroot and flash revovery, etc.
downloadmode should still work. go back to any kdz for your version
also source and versions post next time
So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Edit: I solved my issue by downloader the stock B08 system on my S5 and then i placed it in the external sd. Then i put the SD back into the Axon and installed the system. After i had installed the system and booted into the OS i could enter adb with my device being recognized and after that i flashed twrp by using ADB.
I have a new problem though and that is that i can't install the 3.1.0.0. twrp. it only boots into black screen when i enter recovery. I can use the 3.0.4.0. version though.
You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?
senny22 said:
So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Click to expand...
Click to collapse
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?
nonamesl said:
You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?
Click to expand...
Click to collapse
Correct. It simply reboots.
Yup, i tried installing the B29 stock system on my G model and so i suppose i had the wrong bootstack becasue this is where my problems started.
I get to the stock android recovery.
raystef66 said:
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?
Click to expand...
Click to collapse
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.
senny22 said:
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.
Click to expand...
Click to collapse
You should see your phone as QUSB_BULK. Installed the ZADIG drivers ? That may cure the problem.
After that, imo, it is important you can reboot edl and flash TWRP recovery again AND when it recounts, you pull usb.
Normally you will have replaced recovery , reboot ok and you can enter TWRP and fastboot also.
ps : sometimes it is also advisable to go to ADB RECOVERY directly and do the processes.
ps2 : when TWRP backup, you can always put it on SD via other phone and in TWRP restore. Normaly you're good to go then...
Try the Marshall London Bootloader Interface driver maybe?
nonamesl said:
Try the Marshall London Bootloader Interface driver maybe?
Click to expand...
Click to collapse
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?
senny22 said:
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?
Click to expand...
Click to collapse
Installing the driver and using it for the phone (device manager -> change driver manually (or something of the sort)) worked for me, but it could differ. Let me know. You don't have to uninstall other drivers just use that specific one for your phone by switching the driver manually via device manager.
I was installing a magisk module when the phone bootlooped, I tried to use fastboot but adb wont recongize it, does anyone know what to do
yellk20 said:
I was installing a magisk module when the phone bootlooped, I tried to use fastboot but adb wont recongize it, does anyone know what to do
Click to expand...
Click to collapse
You're getting you tools messed up...
For fastboot you need to be in the bootloader (vol- and pwr)
rignfool said:
You're getting you tools messed up...
For fastboot you need to be in the bootloader (vol- and pwr)
Click to expand...
Click to collapse
yeah im in the bootloader, my computer will recongize that there is something in fastboot, but adb wont recongize so i cant flash anything
yellk20 said:
yeah im in the bootloader, my computer will recongize that there is something in fastboot, but adb wont recongize so i cant flash anything
Click to expand...
Click to collapse
From fastboot... You could
1) flash the stock kernel, reboot to recovery, and factory reset
2) flash TWRP to boot, reboot to recovery, use adb to push whatever you want to /sdcard/, then flash that
3) download either from the BTS thread or from Essential, a back to stock fastboot flashable
If none of those sound good...
Fastboot flash the stock kernel, reboot to recovery, and sideloadable an OTA from the Essential website...
yellk20 said:
I was installing a magisk module when the phone bootlooped, I tried to use fastboot but adb wont recongize it, does anyone know what to do
Click to expand...
Click to collapse
Update, i sideloaded a image and that seemed to work, but fastboot still wont be recongized
Thank you, but I got it figured out and I re rooted and I installed twrp just in case something goes wrong
I am following this guide here to root oneplus 6t (european variant), 9.0.5 Android:
https://www.xda-developers.com/onepl...otloader-root/
bootloader is unlocked and I can see there is a positive connection between phone and PC by checking the output on adb devices and fastboot devices. both work as intended.
the problem is that when I try to adb sideload, it says that I need version 1.0.32. so this means I cannot flash the custom recovery.
any tips? been looking online for quite some time now and cannot figure out what to do anymore. where can I find this 1.0.32 adb version?
I am a long time user on nexus 5 and just bought this phone, want to root it aswell. (note: this does not mean I have high level of knowledge on these types of hacks, just wanted to have this clear.)
Are you trying to boot or to flash the recovery from adb ? If you're trying to install the recovery from adb it wont work, on a/b devices the recovery is part of the boot image wich needs to be patched, boot twrp.img and then get the bluespark twrp zip and flash it.
nikexv2 said:
Are you trying to boot or to flash the recovery from adb ? If you're trying to install the recovery from adb it wont work, on a/b devices the recovery is part of the boot image wich needs to be patched, boot twrp.img and then get the bluespark twrp zip and flash it.
Click to expand...
Click to collapse
I can start the twrp, the problem is when I go into adb sideload and try to flash it. on pc is says "error" and on the phone it says I need to get adb 1.0.32. I am trying to flash that bluespark recovery with no luck.
cesar.maranhao said:
I can start the twrp, the problem is when I go into adb sideload and try to flash it. on pc is says "error" and on the phone it says I need to get adb 1.0.32. I am trying to flash that bluespark recovery with no luck.
Click to expand...
Click to collapse
You need to flash the zip from within the recovery that you booted using adb, not sideload it.
I already tried that, copied the files to the phone but when I try to access them through the bootable trwp, I cannot access them.
cesar.maranhao said:
I already tried that, copied the files to the phone but when I try to access them through the bootable trwp, I cannot access them.
Click to expand...
Click to collapse
wrong twrp used. you correct twrp and it will work. like this twrp https://forum.xda-developers.com/on...covery-theme-blacked-twrp-acuicultor-t3847752 or https://forum.xda-developers.com/devdb/project/?id=27466#downloads the choice is yours alone to make.
you are asking for help with 6t in the 6 form. whats wrong with this? you should be at this link https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482