Database Info

Access ADB without Debug mode?

Is there a way I can use ADB without setting debug mode on my phone? I am unable to startup the phone to switch to debug mode. When I start up the phone it goes to the google logo screen and stops there.
I am able to go into fastboot mode however. I have adb installed and all the drivers set.
I can see the phone in my device manager, but when I open up cmd prompt and type in adb devices it says it does not see anything.
Any help would be greatly appreciated!

ADB is only for when the phone is booted up. In your case you will need to work with fastboot
Sent from my Nexus S 4G using xda premium

sj_martin said:
Is there a way I can use ADB without setting debug mode on my phone? I am unable to startup the phone to switch to debug mode. When I start up the phone it goes to the google logo screen and stops there.
I am able to go into fastboot mode however. I have adb installed and all the drivers set.
I can see the phone in my device manager, but when I open up cmd prompt and type in adb devices it says it does not see anything.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
What are you trying to use ADB to do? You can run ADB in recovery, but if you are unable to startup the phone, I don't know anything you could do with ADB to fix it.

Rem3Dy said:
ADB is only for when the phone is booted up. In your case you will need to work with fastboot
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yes as stated all I can do is go into the fastboot screen. It sounds like that I cannot use adb in fastboot?
What options do I have to recover data in fastboot if i do not have adb?
Thanks.

derekwilkinson said:
What are you trying to use ADB to do? You can run ADB in recovery, but if you are unable to startup the phone, I don't know anything you could do with ADB to fix it.
Click to expand...
Click to collapse
I wanted to use ADB to extract some files on the sandisk internal hd. I cannot boot up the phone anymore but it still turns on (but freezes at the google logo).
I also cannot go into recovery as when I try it also stalls at the google logo screen.

sj_martin said:
Yes as stated all I can do is go into the fastboot screen. It sounds like that I cannot use adb in fastboot?
What options do I have to recover data in fastboot if i do not have adb?
Thanks.
Click to expand...
Click to collapse
Yes. Adb will Not work in fastboot. Fastboot flash commands will work.

sj_martin said:
I wanted to use ADB to extract some files on the sandisk internal hd. I cannot boot up the phone anymore but it still turns on (but freezes at the google logo).
I also cannot go into recovery as when I try it also stalls at the google logo screen.
Click to expand...
Click to collapse
Is your bootloader unlocked? If so, flash a new recovery image and do a nandroid backup
Sent from my Nexus S 4G

If recovery doesn't work u have 2 options from fastboot to try to get into recovery:
1) fastboot flash recovery recovery.img
2) fastboot boot recovery recovery.img
All u need is a cwr recovery image. And the files on ur PC to use fastboot.
1) flashes a new recovery
2) just boots up the new recovery without flashing it
Sent from my Nexus S using xda premium

Luxferro said:
If recovery doesn't work u have 2 options from fastboot to try to get into recovery:
1) fastboot flash recovery recovery.img
2) fastboot boot recovery recovery.img
All u need is a cwr recovery image. And the files on ur PC to use fastboot.
1) flashes a new recovery
2) just boots up the new recovery without flashing it
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
my understanding is that i need the have the device visible in command prompt via adb to do any of this which is the issue i'm trying to solve. once i can get my computer to see the phone via adb i think i'm home free to extract all the data i need.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Another interesting note (i don't know if this will help me at all) is that if I boot up into download mode (holding both vol buttons when plugging in the usb cord) it gets stuck at the "unlock bootloader?" screen but in windows under the device manager instead of showing it as an android device with adb it is now under the usb controllers as "samsung usb composite device".
If I could get this thing to mount to my computer that would be fantastic and I could just drag and drop files out of the phone.
Any ideas?

If you flash clockwork recovery, you can boot into recovery and then use cwm to mount USB storage.
Sent from my Nexus S using XDA App

If I flash clockwork I need to unlock the bootloader, if I unlock the bootloader I have to wipe all my data.
So by nature of getting clockwork on the phone is useless to me since i'll have no data to backup by that stage =/

I do have access to fastboot now and is recognized via command prompt; is there a way to extract data via fastboot?

sj_martin said:
I do have access to fastboot now and is recognized via command prompt; is there a way to extract data via fastboot?
Click to expand...
Click to collapse
No and its rather preferred you not start two threads about the same issue.
Sent from my Nexus S MV from the XDA Premium app.

help me
can i use adb to change build.prop...
i hav changed build.prop and aftrr i reboot it ends with a boot loop.
i hav to change the build.prop .so does adb help me to do that .

mfmohamedbilal said:
can i use adb to change build.prop...
i hav changed build.prop and aftrr i reboot it ends with a boot loop.
i hav to change the build.prop .so does adb help me to do that .
Click to expand...
Click to collapse
Yes you can, boot to recovery and use adb to overwrite existing and put the original build.prop back in place

[Q] Nexus S w/ CM 7.1.0 (no load & no recovery)

Can anyone help me with this Ive got a Nexus S, with the latest stable vers. of Cyanogen (update-cm-7.1.0-NS-signed) and ClockworkMod as the recovery image. Was working great then all of a sudden the phone will not load past the "Google" unlocked padlock image OR go into recovery mode. I can get into the bootloader alright (vol+ key & power button) and it confirms that the phone's still "UNLOCKED". All I get, on the screen, when I try to get into ClockworkMod is "Google" and the unlocked padlock image.
Can't even get into the SD card when I hook the phone up to my PC. Tried flashing CWM says that its sent and written but still wont load.
Any ideas how I can at least get into recovery mode? Once i'm in, in theory (if there's nothing terminal, hardware-wise) I can wipe the phone, mount the sd card, put a fresh vers. of CyanogenMod on it and start again.

Wrong section.

Soooooo moved.
Obligatory YOU MORON BLAH BLAH RABBLE RABBLE!!!!
....
Seriously though, what version of the Nexus S do you have? Just want to rule out any ID10T erros first. Second what CMW did you flash via fastboot? Thridly what was your fastboot command?

ackte11 said:
Can anyone help me with this Ive got a Nexus S, with the latest stable vers. of Cyanogen (update-cm-7.1.0-NS-signed) and ClockworkMod as the recovery image. Was working great then all of a sudden the phone will not load past the "Google" unlocked padlock image OR go into recovery mode. I can get into the bootloader alright (vol+ key & power button) and it confirms that the phone's still "UNLOCKED". All I get, on the screen, when I try to get into ClockworkMod is "Google" and the unlocked padlock image.
Can't even get into the SD card when I hook the phone up to my PC. Tried flashing CWM says that its sent and written but still wont load.
Any ideas how I can at least get into recovery mode? Once i'm in, in theory (if there's nothing terminal, hardware-wise) I can wipe the phone, mount the sd card, put a fresh vers. of CyanogenMod on it and start again.
Click to expand...
Click to collapse
How did you root it?
You just need to use fastboot to flash CWM & a new rom
Example for the rom:
fastboot update ROMFILENAME.ZIP -w
For more info on fastboot
http://wiki.cyanogenmod.com/wiki/Fastboot
Edit: There, got you the Cyanogenmod page. It's a step by step guide. Skip the bootloader unlocking section. Do all the rest.
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide

slimdizzy said:
Soooooo moved.
Obligatory YOU MORON BLAH BLAH RABBLE RABBLE!!!!
....
Seriously though, what version of the Nexus S do you have? Just want to rule out any ID10T erros first. Second what CMW did you flash via fastboot? Thridly what was your fastboot command?
Click to expand...
Click to collapse
sorry bout posting in the wrong section. But Ive got the GT-I9020 version, Second I tried to flash versions 3.0.2.4-crespo, 4.0.0.2-crespo, and 5.0.2.0. Nothing responded.
$ fastboot flash recovery recovery-clockwork-4.0.0.2-crespo.img

ackte11 said:
sorry bout posting in the wrong section. But Ive got the GT-I9020 version, Second I tried to flash versions 3.0.2.4-crespo, 4.0.0.2-crespo, and 5.0.2.0. Nothing responded.
$ fastboot flash recovery recovery-clockwork-4.0.0.2-crespo.img
Click to expand...
Click to collapse
Do you have a working adb setup on your computer?
Put your device in fastboot mode ( VOL up + power button)
Make sure it's properly connected and interfacing with adb (you can type "adb devices" and you should see your device in the list)
If you don't see any string of characters after typing adb devices, then you don't have a working adb setup. You need either a standalone adb or the android SDK.

polobunny said:
How did you root it?
You just need to use fastboot to flash CWM & a new rom
Example for the rom:
fastboot update ROMFILENAME.ZIP -w
For more info on fastboot
---wiki.cyanogenmod.com/wiki/Fastboot
Edit: There, got you the Cyanogenmod page. It's a step by step guide. Skip the bootloader unlocking section. Do all the rest ---.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide
Click to expand...
Click to collapse
tried that and got these results
$ fastboot update update-cm-7.1.0-NS-signed.zip -w
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt

I have the android sdk but after "adb devices" its saying command not found

ackte11 said:
I have the android sdk but after "adb devices" its saying command not found
Click to expand...
Click to collapse
on a mac? also what about "fastboot devices"?

Linux Ubuntu 11.04 and Windows 7 "fastboot devices" recognizes it and shows the serial number. adb on windows runs the command but just comes up blank

ackte11 said:
Linux Ubuntu 11.04 and Windows 7 "fastboot devices" recognizes it and shows the serial number. adb on windows runs the command but just comes up blank
Click to expand...
Click to collapse
Alright. Try to flash CWM recovery first, as stated in the Cyanogenmod guide. Then once that's done, boot back into CWM and flash CM7.

Did that and it says that everything goes through, move down to recovery and it just loops the "google" padlock screen

ackte11 said:
Did that and it says that everything goes through, move down to recovery and it just loops the "google" padlock screen
Click to expand...
Click to collapse
Ah okay, maybe a corrupted boot.img
Download the full 2.3.6 rom for your model
i9020a
i9020t/i9023
You can get the model in fastboot mode at the top if you're unsure of which you own.
Extract the ZIP contents and grab hold of boot.img. Flash this boot.img using fastboot
Example: fastboot flash boot boot.img
Once that is done, reboot to fastboot and flash CWM. Then from CWM flash superuser and whichever ROM you want.

polobunny said:
Ah okay, maybe a corrupted boot.img
Download the full 2.3.6 rom for your model
i9020a
i9020t/i9023
You can get the model in fastboot mode at the top if you're unsure of which you own.
Extract the ZIP contents and grab hold of boot.img. Flash this boot.img using fastboot
Example: fastboot flash boot boot.img
Once that is done, reboot to fastboot and flash CWM. Then from CWM flash superuser and whichever ROM you want.
Click to expand...
Click to collapse
Nothings working. flashed the boot then CWM still cant get into recovery. Just right back to the "google" page

I am not sure if this works on the nexus s but give it a try.
Instead of flashing the recovery try and boot it. Change the command to fastboot boot recovery .....instead of flash.

albundy2010 said:
I am not sure if this works on the nexus s but give it a try.
Instead of flashing the recovery try and boot it. Change the command to fastboot boot recovery .....instead of flash.
Click to expand...
Click to collapse
still no go.

i am having the exact same problem, my computer can see my phone, but nothing is working. anyone have any input??? it seems like i can not write to certain parts of the sd card, it says, FAILED (remote: Write Fail)
trying to run an update. see how the image says it was copied over correctly? ive also tried ereasing it as well..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No boot or recovery img

This post specifically helped me.
http://forum.xda-developers.com/showpost.php?p=19531979&postcount=30
just rename the file "install-recovery.sh" which is in the /etc folder. You can only access it with a root file manager (rootexplorer $4 on the market)
make sure your new file is not ending with .sh
It appears that this file keeps writing stock recovery to your phone. Once you erase it, flash CWM recovery and then flash your rom. Hope it helps.

Nice catch. Didn't even think about it getting rewritten every boot.
Sent from my Nexus S using xda premium

[Q] Bootloop - no recovery - no system - reset tamper flag - RMA

Hi guys,
my N5 is broken and i want to RMA ... It bootloops at the Google Logo, I can enter Fastboot, but NOT the recovery.
I managed to flash stock via fastboot and I locked the Bootloader.
After that I tried to reset the Tamper Flag with osm0sis' BootUnlocker zip ... well, ya need recovery for that. I tried to boot twrp with
Code:
fastboot boot recovery
but that returns "cannot load 'recovery': No such file or directory".
flashing the recovery works well ... but it doesn't boot into recovery, its bootlooping here to, even if you select recovery mode in fastboot.
So, any ideas how to do that now ?
thanks in advance !
EDIT
AWWW ..... after re-reading my post, I realized the command was wrong ..... its just boot ... not boot recovery ....jeeez
But anyway, even that results in a Bootloop .... so no way to access anything else but fastboot.

momsi said:
Hi guys,
my N5 is broken and i want to RMA ... It bootloops at the Google Logo, I can enter Fastboot, but NOT the recovery.
I managed to flash stock via fastboot and I locked the Bootloader.
After that I tried to reset the Tamper Flag with osm0sis' BootUnlocker zip ... well, ya need recovery for that. I tried to boot twrp with
Code:
fastboot boot recovery
but that returns "cannot load 'recovery': No such file or directory".
flashing the recovery works well ... but it doesn't boot into recovery, its bootlooping here to, even if you select recovery mode in fastboot.
So, any ideas how to do that now ?
thanks in advance !
Click to expand...
Click to collapse
it wont boot into recovery. boot into bootloader, then recovery, if no recovery, flash a recovery. btw, dont boot a recovery, flash it. if you run the script to boot it, itll only boot once. you need to fastboot flash recovery recoveryname.img
edit.. i noticed that you are booting a recovery. booting it only works for a one time use. dont boot it, flash it.
fastboot flash recovery recoveryname.img
Click to expand...
Click to collapse

fastboot boot recovery boots the phone to a recovery image on your PC.
So like fastboot flash...
fastboot boot path\to\recovery.img
Sent from my Nexus 5 using Tapatalk

I know that booting it is only one time use, I did that on purpose. But it didn't work either, see edit in OP.

momsi said:
I know that booting it is only one time use, I did that on purpose. But it didn't work either, see edit in OP.
Click to expand...
Click to collapse
the boot command is wrong as well. its fastboot boot recovery recoveryname.img
and the recovery file has to be in the same folder on your desktop as fastboot.

simms22 said:
the boot command is wrong as well. its fastboot boot recovery recoveryname.img
and the recovery file has to be in the same folder on your desktop as fastboot.
Click to expand...
Click to collapse
fastboot boot doesn't need you to identify a NAND partition as you're loading it into memory.
fastboot boot recovery.img is the command if your recovery is called recovery.img
The recovery file can be in any directory.
If you haven't installed fastboot correctly, you need to open the command prompt in (or change directory TO) the directory where fastboot.exe is. The easiest way to deal with this is as you say, drop the recovery image there, but you can also just prefix the recovery.img with the path if its anywhere else
However best practice would be to install fastboot correctly by manually adding it to environment variables or using the 15 second installer (or even dropping fastboot.exe in an existing environment variable path such as c:\windows\system32) at which point you can run fastboot no matter what directory command prompt is running in.
I cover most of the above in my "adb and fastboot. What is it?" Sticky thread in my signature
Anyway, sorry OP, I think you're stuck.
Sent from my Nexus 5 using Tapatalk

rootSU said:
fastboot boot doesn't need you to identify a NAND partition as you're loading it into memory.
fastboot boot recovery.img is the command if your recovery is called recovery.img
The recovery file can be in any directory.
If you haven't installed fastboot correctly, you need to open the command prompt in (or change directory TO) the directory where fastboot.exe is. The easiest way to deal with this is as you say, drop the recovery image there, but you can also just prefix the recovery.img with the path if its anywhere else
However best practice would be to install fastboot correctly by manually adding it to environment variables or using the 15 second installer (or even dropping fastboot.exe in an existing environment variable path such as c:\windows\system32) at which point you can run fastboot no matter what directory command prompt is running in.
I cover most of the above in my "adb and fastboot. What is it?" Sticky thread in my signature
Anyway, sorry OP, I think you're stuck.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
hmm.. ive always used fastboot boot recovery recoveryname.img, and never an issue.

simms22 said:
hmm.. ive always used fastboot boot recovery recoveryname.img, and never an issue.
Click to expand...
Click to collapse
Are you sure? It *shouldn't* work and certainly doesn't for me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

rootSU said:
Are you sure? It *shouldn't* work and certainly doesn't for me.
Click to expand...
Click to collapse
you are right

Ah ok
Sent from my Nexus 5 using Tapatalk

Try fastboot format recovery then flash it again.
Sent from my Nexus 5 using XDA Free mobile app

Atomix86 said:
Try fastboot format recovery then flash it again.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
did that ... didn't work....

Didn't work as in the format failed, or the recovery flash failed?
Sent from my Nexus 5 using XDA Free mobile app

I didn't see it mentioned but, have you tried a different alternative recovery? I speak from experience at one point after rooting, my phone would not launch the stock recovery. I then tried to use CWM (it's what I was familiar with) and it wouldn't boot either. I then went to TWRP and it did work.
Is it maybe possible the recovery image you have is corrupted or incomplete? Possible maybe you have the wrong one you're trying to flash and boot? I once mistakenly flashed my tablet with the recovery for my phone. Fixed that issue but it drove me nuts for a few hours wondering why it wasn't working.

Didnt work as in it stuck in the same bootloop again ...
no luck with other recoverys or other ..tried several
i only can enter fastboot

Bootloop

Bootloop
Hi there, i was on cm7, than i found this rom "Desire XS version 1.1" and I decided to install it, after aroma installation, I rebooted it and now i'm in bootloop and i can't access to hboot, what should I do?

Hi, I assume you are s-on with unlock bootloader? If yes, then enter fastboot(if my memory serves me right, hold vol down and power on). The instructions can be found here. I assume u have already wipe/format and flash the rom, so the next thing to do is flash the boot.img in fastboot, found in the link, step 4.

Thank you for your reply, but i think that i can't access to fastboot

evilken9555 said:
Thank you for your reply, but i think that i can't access to fastboot
Click to expand...
Click to collapse
pull the battery out for a min then put back in, u should be able to boot into bootloader then select fastboot in the menu

Got an update :
Both of the suggestions didn't work, so i've tried to connect my phone to a PC and tried to use adb to access into fastboot mode, once I've got into fastboot I've tried to install the stock firmware through ruu, but I get an error : USB error
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

#Fear said:
Hi, I assume you are s-on with unlock bootloader? If yes, then enter fastboot(if my memory serves me right, hold vol down and power on). The instructions can be found here. I assume u have already wipe/format and flash the rom, so the next thing to do is flash the boot.img in fastboot, found in the link, step 4.
Click to expand...
Click to collapse
i can't find boot.img :|
edit: i've found the boot.img, now the problem is that when i connect my phone to the pc when it is in fastboot mode, after a bit a notification with a yellow exclamation mark appears and says "Usb device not recognized", i have windows 8.1, could it be the problem?

evilken9555 said:
i can't find boot.img :|
edit: i've found the boot.img, now the problem is that when i connect my phone to the pc when it is in fastboot mode, after a bit a notification with a yellow exclamation mark appears and says "Usb device not recognized", i have windows 8.1, could it be the problem?
Click to expand...
Click to collapse
the ruu wont work coz ur bootloader is "unlocked". u need to relock it then run the ruu. and yes windows 8 is a problem with fastboot, theres a few guides here on xda how to use fastboot with windows 8. so either find a way to get fastboot working then flash custom rom in recovery then flash the boot.img via fastboot or relock the bootloader (ul need fastboot commands working for that too) and then run ur ruu. either way, get fastboot working first.

jmcclue said:
the ruu wont work coz ur bootloader is "unlocked". u need to relock it then run the ruu. and yes windows 8 is a problem with fastboot, theres a few guides here on xda how to use fastboot with windows 8. so either find a way to get fastboot working then flash custom rom in recovery then flash the boot.img via fastboot or relock the bootloader (ul need fastboot commands working for that too) and then run ur ruu. either way, get fastboot working first.
Click to expand...
Click to collapse
thank you for your support guys, i'll try this in the afternoon =).
I wanted to thank you so much guys, thank you for your help and kindess, i've finally installed the original sense rom =).
Have a good day!

stuck on boot loader - no fastboot - linux

Hi,
following the corresponding lineageos guide i executed from my linux machine
Code:
fastboot flash boot twrp.img
.
rebooting got me to the boot loader. i cannot get into fastboot. (nor anywhere else.)
neither via adb reboot fastboot nor volume down + power.
I cannot recall having experienced this before.
Any help to how I can get into fastboot?
Cheers!

inli said:
Hi,
following the corresponding lineageos guide i executed from my linux machine
Code:
fastboot flash boot twrp.img
.
rebooting got me to the boot loader. i cannot get into fastboot. (nor anywhere else.)
neither via adb reboot fastboot nor volume down + power.
I cannot recall having experienced this before.
Any help to how I can get into fastboot?
Cheers!
Click to expand...
Click to collapse
Fastboot boot TWRP.img

AndroidRooterKev said:
Fastboot boot TWRP.img
Click to expand...
Click to collapse
thanks, but unfortunately, I am not in fastboot mode - that's the problem.

inli said:
Hi,
following the corresponding lineageos guide i executed from my linux machine
Code:
fastboot flash boot twrp.img
.
rebooting got me to the boot loader. i cannot get into fastboot. (nor anywhere else.)
neither via adb reboot fastboot nor volume down + power.
I cannot recall having experienced this before.
Any help to how I can get into fastboot?
Cheers!
Click to expand...
Click to collapse
EDL way work try it.

inli said:
unfortunately, I am not in fastboot mode - that's the problem.
Click to expand...
Click to collapse
Bootloader = fastboot. Run fastboot devices. If you're device shows up, run the command I sent previously.

AndroidRooterKev said:
Bootloader = fastboot. Run fastboot devices. If you're device shows up, run the command I sent previously.
Click to expand...
Click to collapse
hm, ok. but. but
Code:
fastboot devices
(with sudo before) does not give me any device list. (as it should be doing)

superac11 said:
EDL way work try it.
Click to expand...
Click to collapse
On EDL I find eg https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
but the solution there presumes windows. I am on a linux machine.

AndroidRooterKev said:
Bootloader = fastboot. Run fastboot devices. If you're device shows up, run the command I sent previously.
Click to expand...
Click to collapse
the screen I get is the one saying "The boot loader is unlocked"...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

inli said:
the screen I get is the one saying "The boot loader is unlocked"...
Click to expand...
Click to collapse
Ohhh! That's what you meant by "stuck in boot loader". Yeah fastboot won't work there. And you've tried vol down + power multiple times to get to the actual bootloader screen (where you can fastboot)?
Try forcing a shut down (vol up + power) and retry a few times. What were you doing before it got stuck on the boot loader is unlocked screen? You might just need to flash the stock boot.img but you need to try to get to the bootloader screen to run the fastboot command.
If all else fails, you'll have to use the MSM tool (which will wipe everything).
EDIT: Yeah MSM tool requires a windows machine. Not sure how to run it via Linux. Maybe there's a windows emulator out there that can run windows .exe files?

AndroidRooterKev said:
Ohhh! That's what you meant by "stuck in boot loader". Yeah fastboot won't work there. And you've tried vol down + power multiple times to get to the actual bootloader screen (where you can fastboot)?
Click to expand...
Click to collapse
yes, tried multiple times - and, no did not get to the actual bootloader.
AndroidRooterKev said:
What were you doing before it got stuck on the boot loader is unlocked screen? You might just need to flash the stock boot.img but you need to try to get to the bootloader screen to run the fastboot command.
Click to expand...
Click to collapse
i simply executed
Code:
sudo fastboot flash boot 'twrp-3.4.0-0-guacamole.img'
AndroidRooterKev said:
If all else fails, you'll have to use the MSM tool (which will wipe everything).
Click to expand...
Click to collapse
according to https://forum.xda-developers.com/on...to-restore-t4078827/post82210187#post82210187 it seems I need to find a window computer to run this.

inli said:
yes, tried multiple times - and, no did not get to the actual bootloader.
i simply executed
Code:
sudo fastboot flash boot 'twrp-3.4.0-0-guacamole.img'
.
Click to expand...
Click to collapse
That shouldn't have broken the ability to get into the bootloader. Did you have TWRP installed before or was this your first time? Most of the hardware button combos should work regardless of any system/software issues. So vol down + power isn't working, have you tried vol up + power to force a shutdown and retry?

AndroidRooterKev said:
That shouldn't have broken the ability to get into the bootloader. Did you have TWRP installed before or was this your first time? Most of the hardware button combos should work regardless of any system/software issues. So vol down + power isn't working, have you tried vol up + power to force a shutdown and retry?
Click to expand...
Click to collapse
funny, I have been trying now for about 1:30-2h to get into fastboot mode. and 10 sec ago, I got into it. strange. no idea how.
ok, now trying to somehow get into twrp to then perform backup (as originally intended)

oh, no - and now:
I executed
Code:
sudo fastboot boot 'twrp-3.4.0-0-guacamole.img'
Downloading 'boot.img' OKAY [ 0.799s]
booting OKAY [ 0.105s]
Finished. Total time: 0.962s
and then the device rebooted showing me the +1 logo and "fastboot mode". but my computer cannot find it anymore in fasboot mode

inli said:
oh, no - and now:
I executed
Code:
sudo fastboot boot 'twrp-3.4.0-0-guacamole.img'
Downloading 'boot.img' OKAY [ 0.799s]
booting OKAY [ 0.105s]
Finished. Total time: 0.962s
and then the device rebooted showing me the +1 logo and "fastboot mode". but my computer cannot find it anymore in fasboot mode
Click to expand...
Click to collapse
What exact device and software are you running? Have you tried toggling it to "reboot to recovery" on the phone itself? The fastboot command seems to have been successfu so no need to run anymore fastboot commands. Now it's just a matter of getting the phone into recovery. You can even just hold the vol down + power to try and get there.

AndroidRooterKev said:
What exact device and software are you running? Have you tried toggling it to "reboot to recovery" on the phone itself? The fastboot command seems to have been successfu so no need to run anymore fastboot commands. Now it's just a matter of getting the phone into recovery. You can even just hold the vol down + power to try and get there.
Click to expand...
Click to collapse
interesting: when I fastboot boot recovery.img I then get the +1 logo and nothijg works anymore.
if I am in fastboot mode and select "restart bootloader" I get well into fastboot mode. if I select "restart into recovery" I get the "bootloader is unlocked screen".

inli said:
interesting: when I fastboot boot recovery.img I then get the +1 logo and nothijg works anymore.
if I am in fastboot mode and select "restart bootloader" I get well into fastboot mode. if I select "restart into recovery" I get the "bootloader is unlocked screen".
Click to expand...
Click to collapse
Flash the stock boot.img for whatever software you were running.

AndroidRooterKev said:
Flash the stock boot.img for whatever software you were running.
Click to expand...
Click to collapse
yeah, trying this right now. interestingly am now waiting for a few minutes in which lineageos is trying to start - without much success as of yet... i will wait for 10 minutes and then try to reset the whole phone... will keep this thread informed
thank you so far - helped me a lot to note that I am not insane...

aaaah, I figured out
sudo fastboot boot 'twrp-3.3.1-4-guacamole.img' works

hi,
if I may, a brief maybe stupid question: i want to restore
https://oxygenos.oneplus.net/OnePlus7ProOxygen_21.E.26_OTA_026_all_2005192135_8474bf58a0ec4716.zip
websites suggest to run flash all.bat. well, I do not find it anywhere. Do you have an idea where to find it?

inli said:
hi,
if I may, a brief maybe stupid question: i want to restore
https://oxygenos.oneplus.net/OnePlus7ProOxygen_21.E.26_OTA_026_all_2005192135_8474bf58a0ec4716.zip
websites suggest to run flash all.bat. well, I do not find it anywhere. Do you have an idea where to find it?
Click to expand...
Click to collapse
I've never heard of that. But do your research and confirm it works before you do it.
---------- Post added at 01:26 AM ---------- Previous post was at 01:23 AM ----------
inli said:
aaaah, I figured out
sudo fastboot boot 'twrp-3.3.1-4-guacamole.img' works
Click to expand...
Click to collapse
That most likely worked because you're on A9. A10 will not accept that twrp img since it's incompatible.
This is why it's good to mention device/software details of the phone during the creation of an xda post. But glad you got it.