i tried to flash a recovery and it didnt work and the phone is stuck in fastboot mode
use this
BUT, before you even do a thing, know that you have to use the files that are meant for your phone (you need the recovery and usb drivers meant for your phone; i believe you can use the other files)
sweetnsour said:
use this
BUT, before you even do a thing, know that you have to use the files that are meant for your phone (you need the recovery and usb drivers meant for your phone; i believe you can use the other files)
Click to expand...
Click to collapse
My phone can't get to emergency mode and stuck in fastboot mode i have rooted my phone and backed up rom rebooted phone and went straight to fastboot mode what do i do
lg optimus c
Yes the tut didn't work for my phone. for some reason its not being recognized by the fastboot shell nor adb shell. I'd assume its completely bricked ? thanks for all the help.
My phone was not recognized by neither fastboot nor adb while in fastboot mode. "adb devices" and "fastboot devices" generated no result. Nevertheless, the following command worked flawlessly
fastboot flash recovery recovery.img
So, it seems that it's not necessary for the phone to show up in adb or fastboot.
Related
Short version - is it possible to copy files from my phone to my PC using fastboot (or perhaps adb)? The cyanogenmod WIKI for fastboot, among others, imply that you can (under the section Examples -> Manual Nandroid Restore it says "Make a Nandroid backup, and copy the folder off your SD card to your desktop."). Sorry I'm not allowed to post the link due to being a new user, but this is what it says:
"Make a Nandroid backup, and copy the folder off your SD card to your desktop.
cd ~/Desktop/path/to/backup/
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot"
If it is possible, is "flash" the correct command to be using? The description of the flash command when you run "fastroot help" implies it writes data to the phone, not from the phone to the PC... Unfortunately almost everything I search for around the flash command is examples showing how to load ROMs etc, I can't seem to find anything else that points to it being used to backup data...
[UPDATE] - From what I understand you can't copy files off the phone using fastboot commands, but can using adb - so a few questions:
- Does anyone know why adb wouldn't see my device (when I run "adb devices") but fastboot does (note that I'm on the fastboot screen)?
- Does adb require debugging mode to be on?
[UPDATE-2] - Still can't get adb working, suspect it's because USB debugging isn't enabled (though not sure how I can check?). I did try using fastboot to erase the /cache partition in case the lockout data was stored in there - but this didn't work unfortunately. Looking likely I'll just have to wipe it with fastboot oem unlock
Long version / background info:
Using a Samsung Nexus S with Android 4.1
The other night someone down the pub decided to try to unlock my phone, and apparently got the pattern wrong so many times it's now requiring me to enter my Google account details.
Fine, I enter the username / pass, only it says they're wrong - I know they're correct because I've just confirmed they are by logging into Gmail. It says they're incorrect so quickly that I suspect it's not even connecting to the web to check. The icons at the top imply there is signal, but it looks as though 3G / data is off, and there's no WiFi icon even though I'm sat next to my wireless router. I can't find any way to re-enable WiFi / 3G without first unlocking the phone - which requires a net connection. So I got into Fastboot Mode and selected Recovery and the device looks as though it's doing something (deleting all user data I assumed), but when it starts up it's exactly the same - which implies the user data hasn't been erased.
Then I installed fastboot, and the drivers for the Nexus S.
When I run "fastboot devices" I can see the phone listed, however bizarrely "adb devices" lists nothing.
"fastboot oem unlock" seems to work (the phone prompts me to confirm I want to give root access & delete all user data). I haven't done this yet as I want to see if I can save my data somehow using adb or fastboot commands.
For adb to work, your phone must be booted and USB debugging enabled. In your current situation, as far as I know, a factory reset is the only option.
The phone is either in ADB mode or in Fastboot mode. It can never be in both ADB and Fastboot at the same time. ADB requires the phone is up and running, Fastboot requires the phone is in bootloader mode. ADB requires debugging turned on.
If you unlock your bootloader, you can boot the phone using fastboot and your own recovery image using "fastboot boot myrecovery.img" (notice, no flash keyword here). Booting your device with this recovery image, you can do whatever you like and the image permits, e.g. running ADB and copying files. You'll need this recovery image, though.
Thanks, I did try fastboot with a recovery image, but it currently doesn't work because I need to unlock the bootloader (which will wipe all data anyway). Sounds like I will need to just wipe it
kuisma said:
The phone is either in ADB mode or in Fastboot mode. It can never be in both ADB and Fastboot at the same time. ADB requires the phone is up and running, Fastboot requires the phone is in bootloader mode. ADB requires debugging turned on.
If you unlock your bootloader, you can boot the phone using fastboot and your own recovery image using "fastboot boot myrecovery.img" (notice, no flash keyword here). Booting your device with this recovery image, you can do whatever you like and the image permits, e.g. running ADB and copying files. You'll need this recovery image, though.
Click to expand...
Click to collapse
Facing same issue.
Is there anyway so I could copy userdata.img to my pc and then delete gesture.key file (I am running Lollipop) with NO USB DEBUGGING ON in Fastboot mode.
I have gone through "unpacking and packing .img files"http://forum.xda-developers.com/galaxy-s2/general/ref-unpacking-repacking-stock-rom-img-t1081239
But it is out of my knowledge range can anyone get through it and explain me the same.
Hi! I am in the same situation... ADB not working, only fastboot... Any way to save my data? Do I need to unlock bootloader to install a stock recovery? Thank you!
Hi - I am in exactly same situation as well. I am using Oneplus 8t. Any help is greatly appreciated. thanks
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Tommyboy77 said:
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Click to expand...
Click to collapse
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
es0tericcha0s said:
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
Click to expand...
Click to collapse
adb devces does not work in clockwork mod either.....what is the easiest way to get this custom rom sent to my internal sd card if the phone wont boot up and os is wiped off the phone? it is an htc one...
adb should work in CWM... You might have to manually load the driver. Even if every driver works when the phone is booted and all, Windows can still have issues finding the right one in recovery. Check in your device manager. If that doesn't work, then you'll have to see if your recovery supports USB OTG and see if you can load like that. If none of that works, you'll have to reload the OS via RUU and start over with root/recovery/etc.
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
C13v3r0n3 said:
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Neither of those things are options for the OP. He can't boot, so he can't mount USB (mounting USB in recovery hasn't worked for most phones since JB where most phones don't support USB mount - only MTP) and he can't sideload because he hasn't been able to get ADB working.
His options now are:
Find out why the adb driver isn't loading so he can just adb commands to push the file or sideload
USB OTG
Return to stock via RUU
I am having trouble rooting my Galaxy J7 Prime sm-j727t
Every Odin version I use with every TWRP tar file I try to use doesn't work. They either Fail or Odin stops responding when I try to load the tar file into the AP.
I've tried just using the CF Auto Root and those fail as well.
Any ideas what the issue is? I've been trying for two days with no success
Is your bootloader unlocked?
Emir Çetin said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
I thought Samsung phones come with bootloader unlocked already??
BramaKnox said:
I thought Samsung phones come with bootloader unlocked already??
Click to expand...
Click to collapse
You can check bootloader with dialer (search it).
Of phone has fastboot mode you can check bootloader with fastboot commands (search it too)
Emir Çetin said:
You can check bootloader with dialer (search it).
Of phone has fastboot mode you can check bootloader with fastboot commands (search it too)
Click to expand...
Click to collapse
When I put the phone in FastBoot mode I have the following options
Reboot System Now
Reboot to Bootloader
Apply update from ADB
Apply Update from SD card
Wide data/factory reset
Wipe Cashe partition
Mount /system
View recovery logs
Run graphics test
Power off
Lacking storage booting
1-Install your phones drivers on your PC.
2-Install adb and fastboot tools. https://www.addictivetips.com/android/download-adb-and-fastboot/
3-Reboot to fastboot.
4-Connect your phone with USB cable.
5-Open command prompt in adb and fastboot folder
6-Type fastboot devices (If you don't see your device there is a problem in drivers or fastboot)
7-Type fastboot oem device-info
You can check your bootloader status in that screen.
Emir Çetin said:
1-Install your phones drivers on your PC.
2-Install adb and fastboot tools. https://www.addictivetips.com/android/download-adb-and-fastboot/
3-Reboot to fastboot.
4-Connect your phone with USB cable.
5-Open command prompt in adb and fastboot folder
6-Type fastboot devices (If you don't see your device there is a problem in drivers or fastboot)
7-Type fastboot oem device-info
You can check your bootloader status in that screen.
Click to expand...
Click to collapse
Am I doing something wrong here ? see attached for screnshot
Emir Çetin said:
1-Install your phones drivers on your PC.
2-Install adb and fastboot tools. https://www.addictivetips.com/android/download-adb-and-fastboot/
3-Reboot to fastboot.
4-Connect your phone with USB cable.
5-Open command prompt in adb and fastboot folder
6-Type fastboot devices (If you don't see your device there is a problem in drivers or fastboot)
7-Type fastboot oem device-info
You can check your bootloader status in that screen.
Click to expand...
Click to collapse
I tried a some other steps. Tried using the video on youtube on a tut. When I get to the oem unlock I just get stuck with a msg sayng "waiting for any device" my device is plugged in, from what I know I have updated the samsung drivers (from previous attempt of other methods) the adb bootloader cmd did put my phone into fastboot mode
(White box, blue arrow point down with a straight line under the point)
(Blue screen with Downloading...)
do not turn off target
What am I missing here?
I tried rooting TWRP 3.2.3. with Odin on the phone again and it still failed
Does anyone else have any more insight to a possible solution?
Have you checked bootloader with dialer?
BramaKnox said:
I am having trouble rooting my Galaxy J7 Prime sm-j727t
Every Odin version I use with every TWRP tar file I try to use doesn't work. They either Fail or Odin stops responding when I try to load the tar file into the AP.
I've tried just using the CF Auto Root and those fail as well.
Any ideas what the issue is? I've been trying for two days with no success
Click to expand...
Click to collapse
Witch android you are?
Hi all,
Just bought yesterday this phone and after doing typical actions like android config (oem, debugging, etc.), installed adb and fastboot. PC recognized command adb devices and shows the phone but when I reboot to fastboot mode, it stucks and the device manager shows unknown android.
Have read all the tips here, forums, youtube, etc. but no way. Tried in 2 different computer with same results. Installed last android studio with sdk manager, same error. Installed oneplus drivers and also the same.
Even I have tried a different cable but no success at all.
This is so frustrating situation, ever more considering that I'm not newbie at this (years ago always changed rom every month and smartphone every 2 months).
Any advice? Format pc? Install other windows in other partition?
Or selling the phone and buying another brand
spamerobaldomero said:
Hi all,
Just bought yesterday this phone and after doing typical actions like android config (oem, debugging, etc.), installed adb and fastboot. PC recognized command adb devices and shows the phone but when I reboot to fastboot mode, it stucks and the device manager shows unknown android.
Have read all the tips here, forums, youtube, etc. but no way. Tried in 2 different computer with same results. Installed last android studio with sdk manager, same error. Installed oneplus drivers and also the same.
Even I have tried a different cable but no success at all.
This is so frustrating situation, ever more considering that I'm not newbie at this (years ago always changed rom every month and smartphone every 2 months).
Any advice? Format pc? Install other windows in other partition?
Or selling the phone and buying another brand
Click to expand...
Click to collapse
Did you select always allow from this computer after enabling debugging and plugging your phone into computer when phone was booted and running(not in recovery or fastboot. Also adb does not work in the bootloader only fastboot commands. Secondly search for the insecure modded stock recovery if you want to do adb access commands in recovery. There is also a fastboot d mode on our phones which look like recovery but you can flash all partions via full fastboot to get to fastboot d your phone has to be on then you type adb reboot fastboot
toolhas4degrees said:
Did you select always allow from this computer after enabling debugging and plugging your phone into computer when phone was booted and running(not in recovery or fastboot. Also adb does not work in the bootloader only fastboot commands. Secondly search for the insecure modded stock recovery if you want to do adb access commands in recovery. There is also a fastboot d mode on our phones which look like recovery but you can flash all partions via full fastboot to get to fastboot d your phone has to be on then you type adb reboot fastboot
Click to expand...
Click to collapse
finally solved!! thanks mate
spamerobaldomero said:
finally solved!! thanks mate
Click to expand...
Click to collapse
No prob
Hello.
Today I updated from the Nord 5G to the Nord 2 5G.
DN2103_11_A.14
I have enabled developer mode, oem unlock and adb debug.
I can't access fastboot properly. And recovery is different from the previous Nord. There is no option to reboot to fastboot.
I use adb reboot-fastboot and I enter a sort of fastboot. It says:
fastboot_unlock_verify ok
The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously.
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Halp?
krugm0f0 said:
Hello.
Today I updated from the Nord 5G to the Nord 2 5G.
DN2103_11_A.14
I have enabled developer mode, oem unlock and adb debug.
I can't access fastboot properly. And recovery is different from the previous Nord. There is no option to reboot to fastboot.
I use adb reboot-fastboot and I enter a sort of fastboot. It says:
fastboot_unlock_verify ok
The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously.
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Halp?
Click to expand...
Click to collapse
Don't own this device but try: "adb reboot bootloader" instead and test fastboot commands from there (don't navigate to Fasboot from bootloader).
krugm0f0 said:
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Click to expand...
Click to collapse
This is normal behaviour with the OPN2 afaik. Your PC can access the USERDATA folder whilst in ADB mode (aka booted normally) and whilst in the recovery bios. Your pc CANNOT access the USERDATA folder when your phone is in fastboot, or at least I've never been able to on my Nord 2.
Your op didn't include what exactly you need help with. Everything you described is exactly intended behaviour. From my understanding your seem to have booted into fastboot mode, then noticed your PC can't access userdata. That's normal, you can still use fastboot commands and your PC is still connected to the phone. Your "My Computer" folder on PC not showing the phone shouldn't be any cause for alarm.
Now I'm starting to guess, because you might have failed to mention; Are you unable to send fastboot commands to your phone when its in fastboot mode?
Are you trying to flash a file?
What's the issue?
Zombnombs said:
This is normal behaviour with the OPN2 afaik. Your PC can access the USERDATA folder whilst in ADB mode (aka booted normally) and whilst in the recovery bios. Your pc CANNOT access the USERDATA folder when your phone is in fastboot, or at least I've never been able to on my Nord 2.
Your op didn't include what exactly you need help with. Everything you described is exactly intended behaviour. From my understanding your seem to have booted into fastboot mode, then noticed your PC can't access userdata. That's normal, you can still use fastboot commands and your PC is still connected to the phone. Your "My Computer" folder on PC not showing the phone shouldn't be any cause for alarm.
Now I'm starting to guess, because you might have failed to mention; Are you unable to send fastboot commands to your phone when its in fastboot mode?
Are you trying to flash a file?
What's the issue?
Click to expand...
Click to collapse
I am unable to send fastboot commands. Is not recognized by "fastboot devices". And this fastboot mode looks nothing like my previous phones. 2, X, 5T and Nord 5G. <waiting for device>
I want to do my "usual routine" with my new phones. Unlock, flash twrp or other recovery, and flash magisk for root.
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
nothing. only recovery mode
vol down+ power =recovery mode
vol up + power = normal boot
I finaly boot into fastboot mode with adb command only (adb reboot bootloader)
With buttons wont work.
But i can't enable Volte/Vowifi (thats why i wanted to boot there).
Can you send adb commands when in recovery mode ?
I'm trying to enable VoLTE too, but adb only detect phone when powered normaly, not when in recovery mode.
i don't know about adb but in fastboot you can.
I can't enable volte/vowifi in fastboot with this commands.
https://androplus.org/wp/wp-content/uploads/2021/08/onr12.jpg
Fastboot commands start with fastboot, those are adb commands.
krugm0f0 said:
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
Click to expand...
Click to collapse
krugm0f0 said:
Hello.
Today I updated from the Nord 5G to the Nord 2 5G.
DN2103_11_A.14
I have enabled developer mode, oem unlock and adb debug.
I can't access fastboot properly. And recovery is different from the previous Nord. There is no option to reboot to fastboot.
I use adb reboot-fastboot and I enter a sort of fastboot. It says:
fastboot_unlock_verify ok
The device is in fastboot mode which is only for debug Android devices. if you want to exit fastboot mode, please long press volume up nad power buttons simultaneously.
Phone is recognized in windows when in adb-mode (normal booted), but does not recognize it when in this new fastboot mode. Just an Android with an exclamation mark on.
Halp?
Click to expand...
Click to collapse
i am having the same issue can any one help
krugm0f0 said:
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
Click to expand...
Click to collapse
pls contact me in 9650930525 in this number and help me how u did it
drkanurag said:
i am having the same issue can any one help
Click to expand...
Click to collapse
pankspoo said:
On Android 12 OnePlus removed fastbootmode so no unlocking nothing.
But how did u booted in fastbootmode on oos 12 i can't understand
Click to expand...
Click to collapse
roldev said:
Downgrade to latest A11. Unlock via fastboot. Do what you want, then. All explained here or/and telegram group. Sorry, don't have time to do step by step guide now. Cheers.
Click to expand...
Click to collapse
Follow this guide to downgrade to A11 https://community.oneplus.com/thread/1596759
Then you should be able to access fastboot.
krugm0f0 said:
After a "full wipe" of ADB and fastboot drivers, I reinstalled and got it working!
Click to expand...
Click to collapse
Could you go into more detail on what you did in the entire process exactly? Did you use the drivers and adb install from the 15 sec installer? Did you simply uninstall them in the Windows Device Manager and click on "update drivers" to find the local drivers from the 15 sec installer? Which ones did you choose? Sorry, these might be dumb questions, but I'm admittedly very stupid when it comes to Windows and drivers in particular.
I did the exact thing I described above but I'm still just getting that message. Additionally, "fastboot devices" won't list anything and "fastboot oem unlock" will wait for the device for eternaty. "adb devices" on the other hand will list my device while not in Fastboot.