Related
Anyone else have this problem?
numus said:
Anyone else have this problem?
Click to expand...
Click to collapse
So is fastboot the problem or are you trying to boot to recovery through the bootloader. I would use ADB instead of fastboot. But if what you're asking is that you want to boot to recovery from the bootloader, just connect your USB cable to your computer and then select recovery in the bootloader.
CharliesTheMan said:
So is fastboot the problem or are you trying to boot to recovery through the bootloader. I would use ADB instead of fastboot. But if what you're asking is that you want to boot to recovery from the bootloader, just connect your USB cable to your computer and then select recovery in the bootloader.
Click to expand...
Click to collapse
Pretty sure it is fastboot... You use the volume rocker to select recovery and hit the power button... It shows the Bootscreen but doesn't go any further than that.
Edit: it says in red FASTBOOT MODE.. When i select recovery it goes tot he google screen (witht he unlock icon) and doesn't go any further than that.
numus said:
Anyone else have this problem?
Click to expand...
Click to collapse
I'm having trouble too. I have it plugged in to my laptop. When I select "Recovery" and press Power, it just reboots, and then boots into Android.
No recovery.
So I'm gonna try TWRP..
i had the same issue this is what i did
download new recovery h**p://goo.im/devs/OpenRecovery/grouper/openrecovery-twrp-2.2.1.4-grouper.img
then in fastboot
fastboot erase recovery
fastboot flash recovery name_of_recovery.img
wait 15 seconds
unplug usb cable
then use volume keys to boot in to recovery
hope this helps
so any solution at the same screen, same problem.
dj_denims said:
i had the same issue this is what i did
download new recovery h**p://goo.im/devs/OpenRecovery/grouper/openrecovery-twrp-2.2.1.4-grouper.img
then in fastboot
fastboot erase recovery
fastboot flash recovery name_of_recovery.img
wait 15 seconds
unplug usb cable
then use volume keys to boot in to recovery
hope this helps
Click to expand...
Click to collapse
You want to be in the bootloader mode and select recovery. The trick is that to do that, you have to have your Asus USB cable connected to a live usb port when you do it, and it usually works if recovery isn't damaged.
And you can also use Wug's toolkit on the computer, or if you can boot the tablet, you can use goo manager to reboot to recovery, or the Trinity kernel app, or your rom's advanced power menu.
With the USB cable attached from the computer to tablet, here's what I did:
- Went to bootloader
- Did "fastboot erase recovery"
- Did "fastboot flash recovery IMG"
- Then boot to recovery manually from the device itself via volume buttons and Power
Hasn't failed me yet when trying out different recoveries. There was some issue a while back where you had to have the USB cable hooked to your computer and Nexus 7 in order to get to recovery. Not sure if the bug still exists, but it may be worth trying with the cable in.
Also you probably have to have an unlocked bootloader (lock at bottom of Google boot screen).
dj_denims said:
i had the same issue this is what i did
download new recovery h**p://goo.im/devs/OpenRecovery/grouper/openrecovery-twrp-2.2.1.4-grouper.img
then in fastboot
fastboot erase recovery
fastboot flash recovery name_of_recovery.img
wait 15 seconds
unplug usb cable
then use volume keys to boot in to recovery
hope this helps
Click to expand...
Click to collapse
Thanks for that.
That worked for me
Does the USB port you're plugged into need to be a computer with the fastboot drivers already installed? My unit freezes up in bootloader every time I plug in any live USB cable, whether it's a computer or not. My recovery is fine, but with the bootloader constantly freezing I'm not able to install the N7 drivers on my computer, let alone input any fastboot commands. And no, I don't have access to the computer with the drivers already installed sadly.
Sent from my SGH-T989 using xda premium
Turn it off plug USB lead into PC/laptop and nexus hold volume up and down and turn it on, or it also works via my otg cable in my s3 also, its a bug..
Sent from my Nexus 7 using Tapatalk 2
a stupid bug.buoght yesterday,rooted and unlocked.downloaded 10 roms,all kernels,and now that i'm ok to begin test i tried without luck to enter recovery from fastboot (i didn't know this fact)but my cable was inserted on pc usb port...and strange it doesn't work.yestrerday via fastboot i flashed twrp recovery that i love and use also on mine gnexs.i'm on stock rom yet,and without "reboot to recovery" option in powermenu.i reflashed twrp,cwm touch (in fastboot manually)then the same but with a rootkit,no luck.i began to think i have a problem in my device and i don't know how to do because it's a secondary bug for assistance i think..and i read this post.don't even tried commands in few posts ago,already did same things an hour ago.i installed quickboot frm playstore and now i can boot on TWRP.use this for today,when i begin to test roms i'll have the powermenu option!
Sad this,i'm a bit anxious of this bug,because i soft brick gnex every 2\3 days,always trying things and stuff,kernel with modifications by me etc,and i often have to go in cwm via devices off and fastboot before...i see that my tab attacched at pc don't enter recovery from fastboot mode..and it's a problem for me.hope someone discover where is this bug and find a workaround\fix fro that.
cheers
sert00 said:
a stupid bug.buoght yesterday,rooted and unlocked.downloaded 10 roms,all kernels,and now that i'm ok to begin test i tried without luck to enter recovery from fastboot (i didn't know this fact)but my cable was inserted on pc usb port...and strange it doesn't work.yestrerday via fastboot i flashed twrp recovery that i love and use also on mine gnexs.i'm on stock rom yet,and without "reboot to recovery" option in powermenu.i reflashed twrp,cwm touch (in fastboot manually)then the same but with a rootkit,no luck.i began to think i have a problem in my device and i don't know how to do because it's a secondary bug for assistance i think..and i read this post.don't even tried commands in few posts ago,already did same things an hour ago.i installed quickboot frm playstore and now i can boot on TWRP.use this for today,when i begin to test roms i'll have the powermenu option!
Sad this,i'm a bit anxious of this bug,because i soft brick gnex every 2\3 days,always trying things and stuff,kernel with modifications by me etc,and i often have to go in cwm via devices off and fastboot before...i see that my tab attacched at pc don't enter recovery from fastboot mode..and it's a problem for me.hope someone discover where is this bug and find a workaround\fix fro that.
cheers
Click to expand...
Click to collapse
Paragraphs dude? Or at the very least, proper spacing.
On stock rooted rom, flash latest TWRP recovery. openrecovery-twrp-2.2.2.0-grouper.img
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.2.2.0-grouper.img
Then install Rom Toolbox. Use the "Rebooter" to Reboot recovery, and you should have no issues.
..
mvmacd said:
Paragraphs dude? Or at the very least, proper spacing.
On stock rooted rom, flash latest TWRP recovery. openrecovery-twrp-2.2.2.0-grouper.img
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.2.2.0-grouper.img
Then install Rom Toolbox. Use the "Rebooter" to Reboot recovery, and you should have no issues.
Click to expand...
Click to collapse
I did this and I still can't boot into recovery. The only way I can boot into recovery is if I use the fastboot command. The rom toolbox does not work for me.
similar problem
I have somewhat similar problem. Well, actually the problem is not very uncommon the way it looks, but usual solutions do not work.
Basically I have erased my old rom (rebooted to recovery from aokp menu) and erased my rom. I've tried mounting the device from the recovery mode, but it was not recognised on my PC. I assumed that this was an Win8 issue.
Once I've rebooted, I could no logger boot to recovery (after selecting recovery all I got was google logo). I've thought of flashing recovery via fastboot, but bootloader seams to freeze with usb cable in (no matter the cable) and resetting does not help (the way it helped others). Also I cannot fastboot at that time either as PC (neither win8 nor win7 machine can see the device).
Any ideas would be appreciated.
When the bootloader freezes with the usb cable plugged into a PC, it is a driver issue. Uninstall and reinstall the drivers. I have experienced this on a win7 x64 system.
It isn't a driver issue as the same thing happens when connecting to a charger and not the PC.
It happens on mine as well.
Well it wouldn't crash with wall charger if it was a PC driver issue.
In either case, I've actually figured out what's the problem. It seems that usb connector is not very reliable. If the it usb connection is poor, the bootloader crashes. To avoid this issue you have to bend the cable towards the screen to ensure the proper connection. It load that way just fine.
Edit: or not... probably bending just removed the connection completely...
Edit2: did not figure out what was the problem, but after playing around some more, the phone has popped up in computer manager and I was able to continue from there. After flashing the recovery (twm -> cwm), the bootloader un-froze as well.
I can't get into the bootloader/fastboot mode, is there something wrong?
Note I am now on stock 4.4 (including stock recovery/kernel etc.) but previously i had custom recovery and same error.
- tried rebooting into bootloader from recovery when I had philz and/or TWRP - would just boot into the OS
- tried power + button up (i.e. reverse of booting into recovery) - same, boots into OS
- tried quick boot root app - same, boots into OS
WTF
Not hugely concerned since I could get into recovery lol but why is it I can't get into bootloader/fastboot mode? What if the OS is broken and I need to ADB something?
Note I rooted/TWRP/PHilzed and went custom for awhile, then I made my own zip using below thread and a full kdz and flashed back to stock including recovery/kernel/baseband (I wanted to go back to 100% stock).
http://forum.xda-developers.com/showthread.php?p=52207783#post52207783
Thanks
Isn't the bootloader locked on the G2? Coming from a Nexus phone, I was also looking for the option but read it wasn't currently possible to unlock it.
I know we're BL locked, I meant fastboot or download mode or whatever the mode is where you can use adb commands and/or fastboot flash recovery recovery.img if I never need to manually fix recovery for example.
wintermute000 said:
I know we're BL locked, I meant fastboot or download mode or whatever the mode is where you can use adb commands and/or fastboot flash recovery recovery.img if I never need to manually fix recovery for example.
Click to expand...
Click to collapse
You can use ADB by enabling USB debugging in developer options.
Download mode can be enabled by turning the phone off, pushing power+Volume Up and then plugging in your phone to your PC with a USB cable - I've used this twice already to recover from experimenting with recoveries and ROMs (by going back to stock following instructions here: http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/)
GenghisKhan67 said:
You can use ADB by enabling USB debugging in developer options.
Download mode can be enabled by turning the phone off, pushing power+Volume Up and then plugging in your phone to your PC with a USB cable - I've used this twice already to recover from experimenting with recoveries and ROMs (by going back to stock following instructions here: http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/)
Click to expand...
Click to collapse
also i've found the phone won't boot in to recovery if it's on mains charge (via button combo not adb/in rom apps or APM)
GenghisKhan67 said:
You can use ADB by enabling USB debugging in developer options.
Download mode can be enabled by turning the phone off, pushing power+Volume Up and then plugging in your phone to your PC with a USB cable - I've used this twice already to recover from experimenting with recoveries and ROMs (by going back to stock following instructions here: http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/)
Click to expand...
Click to collapse
Thanks, the plugging in USB cable is probably the bit I'm missing!
I know I can use ADB with USB debugging, I'm asking the question if I need to recover from softbrick and can't get into OS
Hi.
Recently I decided to flash lineage os 15.1 on my MiA1
For that I have downgrade to Android nougat.
After downgrading I booted my device.
After setting up device I booted device in fastboot mode to follow further steps like flashing TWRP and all but the problem is my device goes in fastboot mode and it is not identified by abd and after that it is automatically getting restarted and is not holding in fastboot mode.
Please help??
Odd issue. What are you using to flash? If you are using XiaoMiFlash.exe, you'll want to try the (THIS WILL REMOVE ALL YOUR DATA) "clean all" option. Please note that this removes all your data.
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
MrUsamahh said:
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
Click to expand...
Click to collapse
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
oreo27 said:
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
Click to expand...
Click to collapse
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
MrUsamahh said:
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
Click to expand...
Click to collapse
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
oreo27 said:
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
Click to expand...
Click to collapse
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
MrUsamahh said:
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
Click to expand...
Click to collapse
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
oreo27 said:
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
Click to expand...
Click to collapse
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
MrUsamahh said:
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
Click to expand...
Click to collapse
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
oreo27 said:
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
Click to expand...
Click to collapse
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
MrUsamahh said:
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
Click to expand...
Click to collapse
Yup. I just tested it out. It looks like you're right.
oreo27 said:
Yup. I just tested it out. It looks like you're right.
Click to expand...
Click to collapse
So do you know how can I help myself out?
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Mizuru said:
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Click to expand...
Click to collapse
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
MrUsamahh said:
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
Click to expand...
Click to collapse
Your device doesn't get detected in your CMD prompt when it's in fastboot AND you type "fastboot devices"?
If it doesnt then you might have flashed something incorrectly.
Also, make sure to have your android drivers up to date in your pc. It's very, very likely that you don't have them installed on your PC, or they are outdated. See this: https://developer.android.com/studio/run/oem-usb.html
And this: https://developer.android.com/studio/releases/platform-tools.html
I have faced this issue. Yesterday i dirty flashed a custom rom. but i forgot how to dirty flash. i just simply flashed the rom and restarted the phone. it was mandatory to flash custom recovery and gapps after flashing a rom dirtily or normally. but i didn't. After the reboot completed, i remembered that i didn't flashed the twrp and gapps. So, i go back recovery mod, guessed i could flash twrp now. But i didn't see any custom recovery on my phone. But the phone boots, and i can use the phone. Still, i'm on that phone, while i'm typing this comment. i didn't lost my data cause i flashed dirtily. But the problem is, as i didn't flashed gapps or magisk (for root access), now i can't use google apps like, play store, and more. As i don't have root access on my phone so, i can't run flasify, to flash custom recovery. neither i can run other apps that need root. As i didn't flash custom recovery, now i can't flash gapps, magisk and whatever that needs a custom recovery.
I told some rom porter about the matter. They told me to flash stock rom. So, i was trying to flash stock rom. but flashing stock rom requires a fastboot mode. But my fastboot logo doesn't appear and it's blank. I told this to a rom porter. But he said, He doesn't know about that and he can't help.
Hi guys,
i managed to f*ck up.
I had a running LOS 15.1 build until today where it bootloops .
THe thing is that I am not able to access the storage for saving files or using ADB for flashing stock.
adb does not recognize my device since I didnt enable USB Debugging. What do I do now?
I need to boot to twrp at least or flash a stock image but I can't connect my phone..
what do I do?
PLease helpe, its urgent!!
Ragonexus said:
Hi guys,
i managed to f*ck up.
I had a running LOS 15.1 build until today where it bootloops .
THe thing is that I am not able to access the storage for saving files or using ADB for flashing stock.
adb does not recognize my device since I didnt enable USB Debugging. What do I do now?
I need to boot to twrp at least or flash a stock image but I can't connect my phone..
what do I do?
PLease helpe, its urgent!!
Click to expand...
Click to collapse
Power down your device, and power it back on. Just after vibrate press vol - that will take you to fastboot mode.
I have screwed up on every possible way and fastboot saved me every damn time!!!
Just get the timing right , go to fastboot , connect miflash -> flash stock image.
Anantha47 said:
Power down your device, and power it back on. Just after vibrate press vol - that will take you to fastboot mode.
I have screwed up on every possible way and fastboot saved me every damn time!!!
Just get the timing right , go to fastboot , connect miflash -> flash stock image.
Click to expand...
Click to collapse
Already tried MiFlash in Fastboot mode, but it doesnt seem to recognize my device, although I'm pretty sure I have the right adb drivers installed on my Windows 10 machine. MAybe I gotta reinstall them, but I'm not sure which are 100 percent right.
Thanks!!
Hi. I have an LG v20 H990ds. I used a non-genuine usb-c cable which messed up its usb-c port. Ever since then, phone started bootlooping. Despite replacing the usb-c cable, phone is on bootloop. I think the firmware flashing can resolve the issue.
But the phone doesnt stay in download mode for more than 3-4 seconds as it keeps bootlooping. When it is in download mode, my computer doesn't detect it or get a trigger that the phone is connected in device manager.
But when I enter into fastboot, I can install fastboot drivers just fine and able to use fastboot commands. I would have flashed boot.img and system.img using fastboot but it shows the device is 'locked'. Since I cant use 'fastboot oem unlock' as the developer options of the phone software was not enabled, I have come here for seeking help.
Can I bypass the developer options and unlock in fastboot? Can I use EDL mode? Or Qualcomm tools? What are my options? I am really not sure why its bootlooping despite getting usb c port fixed. I will really appreciate if someone can help please. The only way the device can work is if it bypasses the 'lock' checks in fastboot. So a patch or something that can bypass the fastboot can help. Or if I can unlock bootloader n fastboot without using android OS.