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.
Last night, I tried to flash gapps using goomanager. I must have used the wrong gapp files. Now, I have a problem. When I turn on tablet, an endless loop of mesages including "Unfortunately Setup Wizard has stopped working". Now I cannot access anything; no notifications, no access to settings, etc. Anyone have an idea where I can start to troubleshoot this?
That seems like a lot of work compared to just dirty-flashing the same ROM you were using before the gapps flash.
If you have a Nandroid backup using TWRP, you could just selectively restore the system partition.
OR, just start over by doing a factory reset in the custom recovery and then re-installing a ROM from scratch. (You didn't say whether saving data was of any concern to you.)
bftb0 said:
That seems like a lot of work compared to just dirty-flashing the same ROM you were using before the gapps flash.
If you have a Nandroid backup using TWRP, you could just selectively restore the system partition.
OR, just start over by doing a factory reset in the custom recovery and then re-installing a ROM from scratch. (You didn't say whether saving data was of any concern to you.)
Click to expand...
Click to collapse
Saving data is not important. I should have a backup of the Nandroid. I made one after rooting the tablet. The part that confuses me is how to get to those options? I can get into fastboot mode on the tablet. However, from the methods I've tried, they all say I do not have abd. I cannot access usb debugging. How would I reset to factory settings?
captainNT said:
Saving data is not important. I should have a backup of the Nandroid. I made one after rooting the tablet. The part that confuses me is how to get to those options? I can get into fastboot mode on the tablet. However, from the methods I've tried, they all say I do not have abd. I cannot access usb debugging. How would I reset to factory settings?
Click to expand...
Click to collapse
What custom recovery is on the tablet?
I would think that no matter what installer you used (I'm not familiar with "goo manager"), the ROM file that you downloaded would still be present on your device's /sdcard.
If that is the case, you boot your custom recovery (get the tablet into fastboot mode, and press the vol-down or vol-up button to until "start recovery" shows up, and then press the Power button).
From there perform a factory reset and then flash the ROM on your /sdcard from the custom recovery menu.
Long term you really need to straighten out your driver issues. You can see why, right? Alternatively, the TWRP recovery can mount USB flash drives in order to get files to a blank tablet that still has a working custom recovery - you just need the USB key drive and a working OTG cable.
bftb0 said:
What custom recovery is on the tablet?
I would think that no matter what installer you used (I'm not familiar with "goo manager"), the ROM file that you downloaded would still be present on your device's /sdcard.
If that is the case, you boot your custom recovery (get the tablet into fastboot mode, and press the vol-down or vol-up button to until "start recovery" shows up, and then press the Power button).
From there perform a factory reset and then flash the ROM on your /sdcard from the custom recovery menu.
Long term you really need to straighten out your driver issues. You can see why, right? Alternatively, the TWRP recovery can mount USB flash drives in order to get files to a blank tablet that still has a working custom recovery - you just need the USB key drive and a working OTG cable.
Click to expand...
Click to collapse
New problem now. I think I have no custom recovery installed. When I go into recovery from fastboot mode, it shows the droid with a red exclamation mark. Trying to diagnose that now but I can't access the tablet settings.
captainNT said:
New problem now. I think I have no custom recovery installed. When I go into recovery from fastboot mode, it shows the droid with a red exclamation mark. Trying to diagnose that now but I can't access the tablet settings.
Click to expand...
Click to collapse
That is the stock recovery.
Which means you need to get fastboot working from a PC; you really have no choice any longer. Have a look at the fastboot / unroot sticky thread.
Used a toolkit to get back to stock settings. Good to go. Thank you.
Alright here is my situation. I ran the latest OTA update on the stock rom and the phone started going into
a boot loop. My problem is that I havent performed a recent backup and need to access some files on the
phone. Developer mode is enabled, however I disabled USB debugging prior to running the update. When my
phone reboots, I remove the battery and restart the phone but every once in a while my phone successfully
loads and I am able to punch in my pin to unlock the phone. However, a few seconds later the phone reboots.
I tried to access the phone using ADB but because I dont have USB debugging enabled I dont see any devices
when I run the "adb devices" command. I also tried to acquire a smartphone image using encase forensic, but
yet again, because USB debuggin is not enabled, I am not able to pull data.
I am able to go into recovery mode and I tried to wipe my cache partition, but that did not help.
My questions are:
1. Is there a way for me to access my data files while the phone is stuck in a boot loop and USB debugging is
disabled?
2. Is it possible for me to download the latest update, copy it over to my sdcard and rerun the update from
my sdcard from recovery mode? Could this possibly solve my problem?
3. In a worst case scenario, if I do a factory wipe/reset, will this solve my problem and what is the
likelyhood of recovering my files from the data partition?
Any tips, tricks, advice is greatly appreciated.
tparnet said:
Alright here is my situation. I ran the latest OTA update on the stock rom and the phone started going into
a boot loop. My problem is that I havent performed a recent backup and need to access some files on the
phone. Developer mode is enabled, however I disabled USB debugging prior to running the update. When my
phone reboots, I remove the battery and restart the phone but every once in a while my phone successfully
loads and I am able to punch in my pin to unlock the phone. However, a few seconds later the phone reboots.
I tried to access the phone using ADB but because I dont have USB debugging enabled I dont see any devices
when I run the "adb devices" command. I also tried to acquire a smartphone image using encase forensic, but
yet again, because USB debuggin is not enabled, I am not able to pull data.
I am able to go into recovery mode and I tried to wipe my cache partition, but that did not help.
My questions are:
1. Is there a way for me to access my data files while the phone is stuck in a boot loop and USB debugging is
disabled?
2. Is it possible for me to download the latest update, copy it over to my sdcard and rerun the update from
my sdcard from recovery mode? Could this possibly solve my problem?
3. In a worst case scenario, if I do a factory wipe/reset, will this solve my problem and what is the
likelyhood of recovering my files from the data partition?
Any tips, tricks, advice is greatly appreciated.
Click to expand...
Click to collapse
Boot phone into recovery mode. You can access phone now and make backup or download need files to PC.
svs57 said:
Boot phone into recovery mode. You can access phone now and make backup or download need files to PC.
Click to expand...
Click to collapse
Thanks svs57 for the quick reply.
Would you mind elaborating a bit more? I am an IT guy but by no means a developer. When I boot into recovery is the phone supposed to show up in My Computer via MTP or PTP? The phone is not showing up as a device. Or am I supposed to use adb commands to pull the files down?
When I go into recovery and run the "adb devices" command now I get what appears to be a serial number followed by the word "unauthorized". I rebooted and went into recovery mode again this time tried "apply update from ADB". When I try using either the adb push or adb pull I get "error: closed"
Thanks again for the help.
You have to use latest version of adb. Then you can login to phone via adb and find file you want to backup. Then use "adb pull" to get file to PC.
If you have custom recovery you also can make backup you data using recovery.
Also you can flash the same ROM you have without wipe data.
Rooted my N73G with Clockwork back in 12/12 when I bought it, worked fine for a year and change. Last week it wouldnt boot past the glowy X. Tried resetting cache, Dalvik cache, and factory reset options in Recovery Mode. Nothing
Downloaded the SDK as a couple different tutorials instructed. Tried Skipsoft's toolkit. Why does every bloody recovery tutorial tell you "enable USB Debugging in the Settings menu" when you cant bloody well boot to a working OS???????
Needless to say, everything I try deadends at unable to do whatever because USB Debugging isnt enabled. Now it wont even boot into Recovery Mode, stopping at the bootloader.
Wat do?
aeldergoth said:
Rooted my N73G with Clockwork back in 12/12 when I bought it, worked fine for a year and change. Last week it wouldnt boot past the glowy X. Tried resetting cache, Dalvik cache, and factory reset options in Recovery Mode. Nothing
Downloaded the SDK as a couple different tutorials instructed. Tried Skipsoft's toolkit. Why does every bloody recovery tutorial tell you "enable USB Debugging in the Settings menu" when you cant bloody well boot to a working OS???????
Needless to say, everything I try deadends at unable to do whatever because USB Debugging isnt enabled. Now it wont even boot into Recovery Mode, stopping at the bootloader.
Wat do?
Click to expand...
Click to collapse
BETTER DESCRIPTION....
Rooted my N73G with Clockwork back in 12/12 when I bought it, worked fine for a year and change. Last week it wouldnt boot past the glowy X. Tried resetting cache, Dalvik cache, and factory reset options in Recovery Mode. Nothing
Downloaded the SDK as comminus's tutorial instructed. Installed Java Dev Kit and Android SDK. Got to the command line, but under the right directory when I try "adb devices" it doesnt list my tablet.
Tried Skipsoft's toolkit. Why does every bloody recovery tutorial tell you "enable USB Debugging in the Settings menu" when you cant bloody well boot to a working OS???????
Needless to say, everything I try deadends at unable to do whatever because USB Debugging isnt enabled. Now it wont even boot into Recovery Mode, stopping at the bootloader.
Wat do?
If usb debugging was enabled, one might save the important files from the device before flashing it.
Since you boot into the bootloader, you can flash a factory image. I recommend this guide but all of your data will be gone.
Erovia said:
If usb debugging was enabled, one might save the important files from the device before flashing it.
Since you boot into the bootloader, you can flash a factory image. I recommend this guide but all of your data will be gone.
Click to expand...
Click to collapse
From the linked guide (the one I've been using) "Enable usb debugging on your device (found under Settings > Developer Options)
NOTE: Since Android 4.2 the Developer Options are hidden by default."
How can I enable USB Debugging on a tablet that is bricked? Further, the SDK program doesnt see my tablet connected. I hear a little connection tone in windows when I plug it in, but running adb.exe from the command line and using an "adb devices" command shoes a "List of connected devices" that is empty.
Only the Skipsoft toolkit seems to want to even see my tablet, no matter what USB port I try,
There is no need for adb (it is only used to boot into bootloader). What you will need is the fastboot commands in the "Flashing the Factory Image" part, but be carefull to flash the proper image and to the proper partions.
Erovia said:
There is no need for adb (it is only used to boot into bootloader). What you will need is the fastboot commands in the "Flashing the Factory Image" part, but be carefull to flash the proper image and to the proper partions.
Click to expand...
Click to collapse
Sorted. THanks.
Recently lost the ability to dash charge and use my USB-C jump drive on my OP6T. I've flashed a couple of different ROMS, I updated to OnePlus6TOxygen_34.J.55_OTA_055_all_2107132253_b2cbbb97b4eee.zip, re-flashed another rom, I even swapped out the port with a new replacement I ordered. I'm out of ideas, the port is new so it doesnt need cleaning, USB debugging has been toggled and USB config set to file transfer. Computer doesnt recognize it using the original cable either. I'm leaning towards a software issue but i'm afraid to do too much flashing as I dont have my USB-C to fall back on as backup and would essentially brick the thing if I cant read from the jump drive. Any idead?
Are you able to run fastboot commands from the bootloader or adb commands in recovery?
Or even mount storage in recovery?
SMcC2 said:
Are you able to run fastboot commands from the bootloader or adb commands in recovery?
Or even mount storage in recovery?
Click to expand...
Click to collapse
I'm able to get to get to fastboot, and now I just screwed myself out of TWRP and root by flashing a rom without TWRP. The PC will charge the phone, but wont see it. ADB sees no devices and Shapeshift's recovery doesnt have many options. Basically now i need to flash a recovery image by device only. and that still doesn't solve the connection and slow charge issue
Are you rooted with Magisk?
You should be able to install the twrp.zip from Magisk if so. If not the TWRP app in may work to get it back.
It sounds like you may need to try the MSM tool soon.
root checker says i'm not properly rooted anymore, i've only got the magisk.apk courtesy of google's restore. Looks like the official twrp app will download but not let you flash the img unless rooted. I'm hoping this is a software bug with the oxygen image since i replaced the cable and port and no fix, otherwise i'm gonna have to buy a new device.
and I dont think MSMtool will do anything if the phones not recognized. the all-in-one tool was useless since it didnt see the phone in fastboot
I am able to wirelessly ADB. but as far as i know, there's no way to flash recovery. As soon as i boot to fastboot I obviously lose wifi. any other ideas? i'm not familiar with wireless adb