Database Info

[Q] Cant get to recovery mode

Hello,
I'm trying to get the timeshift video mod working on my Z1 C6603, android version 4.2.2. The last step is to install the mod via recovery mode, which I can't boot to. I've tried the power + volume button method but it boots the phone into safe mode. Any ideas how I could get to recovery mode?

varsketis said:
Hello,
I'm trying to get the timeshift video mod working on my Z1 C6603, android version 4.2.2. The last step is to install the mod via recovery mode, which I can't boot to. I've tried the power + volume button method but it boots the phone into safe mode. Any ideas how I could get to recovery mode?
Click to expand...
Click to collapse
Yes, no problem!
If you're rooted (which I expect that you probably are), just open up (or download and install if you need to) Terminal Emulator and execute this command:
Code:
su
reboot recovery
Alternatively, if you don't have/don't want Terminal Emulator, if you connect your device to your PC via ADB, this command will get you into recovery mode, too:
Code:
adb shell
reboot recovery
Hope this helps! :good:

ИΘΘK¡€ said:
Yes, no problem!
If you're rooted (which I expect that you probably are), just open up (or download and install if you need to) Terminal Emulator and execute this command:
Code:
su
reboot recovery
Alternatively, if you don't have/don't want Terminal Emulator, if you connect your device to your PC via ADB, this command will get you into recovery mode, too:
Code:
adb shell
reboot recovery
Hope this helps! :good:
Click to expand...
Click to collapse
Thanks for your help.
Yes, the phone is rooted.
Terminal Emulator only rebooted the phone after a long pause and ADB tool says "operation not permitted". It's a work phone so it might have theft protection which blocks me from accessing recovery mode. Anything else I could try?

Try
adb reboot recovery

varsketis said:
Thanks for your help.
Yes, the phone is rooted.
Terminal Emulator only rebooted the phone after a long pause and ADB tool says "operation not permitted". It's a work phone so it might have theft protection which blocks me from accessing recovery mode. Anything else I could try?
Click to expand...
Click to collapse
Try:
Code:
adb shell
su
reboot recovery

root-expert said:
Try:
Code:
adb shell
su
reboot recovery
Click to expand...
Click to collapse
Hi,
Phone gets rebooted normally after doing this. Maybe it needs to get a custom recovery installed?

varsketis said:
Hi,
Phone gets rebooted normally after doing this. Maybe it needs to get a custom recovery installed?
Click to expand...
Click to collapse
When you type "su" does it changes the $ symbol to # ?
If you have # means that you have root access if not you don't have...

@varsketis, yes, a custom recovery should resolve your problem. I'd recommend either ClockworkMod or TWRP (TeamWin Recovery Project).
@root-expert, if varsketis didn't have root, when he executed these commands:
Code:
su
reboot recovery
-OR-
Code:
adb shell
su
reboot recovery
...he would have gotten an "Access denied" error. However, since he was able to get his device to reboot in some way or another using the shell, it means that he does have a root shell (#) usable.

Android 10 ADB

Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
I'm trying to disable some apps through ADB but when the

Cj214 said:
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
I'm trying to disable some apps through ADB but when the
Click to expand...
Click to collapse
You can't see the device while on fastboot mode of you type adb devices.
You need to make sure debugging is on in the developer preferences.

ADB appears to be working just fine for me.

When using adb make sure you have debugging enabled and grant the popup on screen

adb is not fastboot. You can use adb on twrp or booted system. Fastboot is on bootloader mode.

Also need to make sure that the proper USB drivers on the computer are installed/updated.

Cj214 said:
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
Click to expand...
Click to collapse
This is working exactly as intended, and not exclusive to Android 10, but rather has been the case as long as I can remember (Jelly Bean? KitKat? Maybe much earlier?):
adb: Only works when booted to OS or in TWRP. Debugging required to be toggle on in phone settings. Does not work in bootloader-fastboot mode.
fastboot: Only works in bootloader-fastboot mode. Debugging is not required to be toggled on.

D:\OnePlus3\Fastboot>adb sideload stock7.zip
opening 'stock7.zip'...
connecting...
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Thats what adb gives to me...

Bringer1 said:
D:\OnePlus3\Fastboot>adb sideload stock7.zip
opening 'stock7.zip'...
connecting...
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Thats what adb gives to me...
Click to expand...
Click to collapse
Sounds like another adb server is still running. What does adb kill-server and then trying again do

a second adb server was running.
TNX

Can I mount system rw using adb enabled recovery img from the following link:
https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865

Cant get ADB in recovery mode, but works in live mode, and so does fastboot

On my Rooted Pixel 4a, I can use:
Fastboot - I flashed the latest update firmware as well as the rooted boot image
ADB Over WiFi - This is the most comnon way I connect for ADB
ADB While the Android OS is running
What I cannoit get woirking is ADB while in recovery mode,
If I go to recovery and connect via a high quality cable, I can see the device with
Code:
adb devices
C:\Java\x86\Android\android-sdk\platform-tools>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
091????????490 rescue
Click to expand...
Click to collapse
But none of the below works
Code:
>adb shell
error: closed
>adb connect 091XXXXXXXX490
cannot resolve host '091XXXXXXXX490' and port 5555: No such host is known. (11001)
>adv shell 091XXXXXXXX490
error: closed
What am I doing wrong? how can I connect in recovery?

Stock recovery?

WillisD said:
Stock recovery?
Click to expand...
Click to collapse
Yes.

DiamondJohn said:
What I cannoit get woirking is ADB while in recovery mode
Click to expand...
Click to collapse
I always thought that adb from recovery was a TWRP thing?
I did adb reboot recovery. My phone has an Android on its back, with "No command" on the screen.
Code:
$ adb devices
List of devices attached
xxx unauthorized
$ adb shell
adb: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
I got the same thing booting to recovery by holding Vol down at boot.
Booting to rescue (another option on the boot menu) got me the same thing on my screen and the same symptom you saw.
Code:
$ adb devices
List of devices attached
xxx rescue
$ adb shell
error: closed
Are you sure this is supposed to work with the stock recovery?

a1291762 said:
Are you sure this is supposed to work with the stock recovery?
Click to expand...
Click to collapse
Actually no, i guess it was an assumption, and the response to adb devices, gave me further hope.
However,, it does respnod to ADB. As is seen, it provides a list of devices. But, maybe one can't shell out while in stock recpvery. Which goves me an idea, maybe we can send commands from the command window in windows/linux. eg adb shell ls But it wouldn't make sense that it would allow root, which negates what I wanted to be able to do in the first place. ie recovery from a bootloop by selectively editing the data partition. in my previous case, it was to disable a single magisk module.

DiamondJohn said:
It wouldn't make sense that it would allow root, which negates what I wanted to be able to do in the first place. ie recovery from a bootloop by selectively editing the data partition. in my previous case, it was to disable a single magisk module.
Click to expand...
Click to collapse
Yeah, it certainly seems to be speaking adb...
I didn't think to try...but maybe adb push and pull work?

Cannot adb boot bootloader. Stuck on boot logo

Hi,
I am using a bootloader unlocked Surface Duo on Android 11 with ‘adb devices authorized’ and all permissions allow from developer menu.
However, when I type:
‘adb reboot bootloader’ my phone reboots and gets stuck on the Windows boot logo infinitely.
I am successfully able to enter recovery and fastbootD (fastbootd) using:
‘adb reboot recovery’ lands up in android icon
‘adb reboot fastboot’ shows menu with fastbootd and adb sideload.
If I type adb devices in the recovery, it prompts unauthorized error.
If I sideload ota update from fastbootd> adb sideload, it partially completes (94%) with unrecognized command error.
I am on non-rooted Surface Duo.
I have tried removing adb keys and reallowing from RSA several times.
I have tested different machines, Windows, Mac and Linux yet no success.
I cannot push Twrp or any boot.img file.
My goal is to be able to push a boot.img file or a twrp.img but i am unable to perform it due to lack of access to the bootloader.
Any suggestions?

anuragkanase said:
Hi,
I am using a bootloader unlocked Surface Duo on Android 11 with ‘adb devices authorized’ and all permissions allow from developer menu.
However, when I type:
‘adb reboot bootloader’ my phone reboots and gets stuck on the Windows boot logo infinitely.
I am successfully able to enter recovery and fastbootD (fastbootd) using:
‘adb reboot recovery’ lands up in android icon
‘adb reboot fastboot’ shows menu with fastbootd and adb sideload.
If I type adb devices in the recovery, it prompts unauthorized error.
If I sideload ota update from fastbootd> adb sideload, it partially completes (94%) with unrecognized command error.
I am on non-rooted Surface Duo.
I have tried removing adb keys and reallowing from RSA several times.
I have tested different machines, Windows, Mac and Linux yet no success.
I cannot push Twrp or any boot.img file.
My goal is to be able to push a boot.img file or a twrp.img but i am unable to perform it due to lack of access to the bootloader.
Any suggestions?
Click to expand...
Click to collapse
If you can access fastboot mode, try flashing the boot.img via fastboot. Place a copy of your boot.img in your fastboot folder on PC and rename the file to "boot.img". Then flash the boot.img via fastboot using the following command:
fastboot flash boot boot.img

Enable USB Debugging in Recovery Mode

Hi,
during the update the phone got stuck, daughter restarted couple of times but it always got to the 76%, hang there and then restarted itself in the endless loop.
I've tried the the hard reset (Power+VolUP) and it got to the screen saying "No Command". Then I pressed the same combo again to get to the bootloader and tried the wipe / reset. During that process I got the error message "E: Can't send SPI message. Try again" and then it said it was successful, but rebooting did nothing, got stuck in the restart loop.
So I've done the research and wanted to to upload the OTA update, have done that but that didn't do anything.
So I've found some articles on how to upload the stock rom/image but I'm unable to do so as sending adb commands is disabled due to the phone being LOCKED. I've learned that the USB debugging needs to be enabled, however I'm unable to get into the OS to set it up, so found this article:
How to enable USB Debugging in Android using recovery mode?
One million questions, Is it possible to Enable USB Debugging in Android Using Recovery Mode or any other technique? Well, the answer is Yes! It is now
www.isrgrajan.com
which outlines the following steps (in summary):
Download the Stock ROM for your device- Google it, I am dam sure you can find it. [DONE]
Download SuperSU from UPDATE-SuperSU-v1.65.zip [DONE][looks pretty old though]
Steps to Enable USB Debugging Using Recovery Mode
Unzip the stock ROM. [DONE]
Within the extracted folder, you will find the system.img well extract it too using Ext4 Unpacker [DONE but plenty of folder are empty, but eventually plentu of APK along]
Also, extract the Update-SuperSU.v1.65.zip file. [DONE, again, looks pretty old]
Now open the folder where you have extracted the system.img files [DONE]
Grab any .apk file from this folder and change the extension from .apk to .zip [PROBLEM: the apks are all over the shop. Which APK shall I pick up?]
And Copy the RSA Certificated to the Update-SuperSU.v1.65 folder (delete previous files if exist) [PROBLEM: unable to find any "RSA Certificated" like files once I open ANY apk]
Also, copy the build.prop to the system folder located within Update-SuperSU.v1.65 folder [BLOCKED by previous step]
Locate the update-script file within this folder and edit it using Notepad++ [BLOCKED by previous step]
You need to update the build.prop file after adding the following line at the bottom [BLOCKED by previous step]
persist.service.adb.enable=1
Next step is updating SQLite Database [WHERE would I do this step?]
Which can be done by adding the following code to the update-script file
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "UPDATE global SET value=1 WHERE name='adb_enabled'"
What would I do then? How to actually apply the changes back to the phone?
Does anyone know of better / latest step by step process of enabling / unlocking the device or is my device now completely and unrepairably bricked?
Thank you.

Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com

jwoegerbauer said:
https://gist.github.com/varhub/7b9555cdd1e5ad785ffde2300fcfd0bd
Click to expand...
Click to collapse
For a while (since when, I don't know) persistent properties are not shared as individual files in /data/property.
They are all packed inside /data/property/persistent_properties.
Try setprop instead.

jwoegerbauer said:
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Click to expand...
Click to collapse
will give it a go. thank you.

jwoegerbauer said:
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Click to expand...
Click to collapse
I've tried the steps but I'm crashing on sending any commands to the device. While I'm in the recovery, I see the following details and options:
```
Android Recovery
google/blueline/blueline
12/SP1A.210812.016.B2/8602260
user/release-keys
Use volume up/down and power
Warning: Previous installation has failed. Your device may fail to boot if you reboot or power off now
- Reboot system now
- Reboot to bootloader
- Enter Fastboot
- Apply Update from ADB
- Apply update from SD card
- Wipe data/factory reset
- Mount /system
- View recovery logs
- Run Graphics Test
- Run Locale Test
- Power Off
```
where I run the adb command:
`adb shell mount data` I get the `adb.exe: no devices/emulators found`.
when I go to the `Apply update from ADB` and run the command above I get `error: closed`.
Basically I'm unable to run any adb commands as of the first message, and the only place I can it's from within the update. I've noticed that while in the 'Update via ADB', then in the Win Device Manager I can see that the driver is changed to `Android Composite ADB Interface` and only now it's accepting very limited commands. `adb devices` command generates: `<device id number>: sideload`.
When in the fastboot, it switches to `Android Bootloader Interface` in the DEvice manager.
When in recovery, the device is disconnected from the computer. (is not listed in the device manager)
any thoughts. thanks
Note: that phone was never rooted.
Bootloader looks like this at the moment:
```
Fastboot Mode
Product revision: blueline MP1.0(ROW)
Bootloader version: b1c1-0.4-7617406
Basebandversion...
serial number:
secure booth: PRODUCTION
NOS Production: yes
DRAM: 4GB
Device State: Locked
Boot slot: a
```

vajnorcan said:
I've tried the steps but I'm crashing on sending any commands to the device. While I'm in the recovery, I see the following details and options:
```
Android Recovery
google/blueline/blueline
12/SP1A.210812.016.B2/8602260
user/release-keys
Use volume up/down and power
Warning: Previous installation has failed. Your device may fail to boot if you reboot or power off now
- Reboot system now
- Reboot to bootloader
- Enter Fastboot
- Apply Update from ADB
- Apply update from SD card
- Wipe data/factory reset
- Mount /system
- View recovery logs
- Run Graphics Test
- Run Locale Test
- Power Off
```
where I run the adb command:
`adb shell mount data` I get the `adb.exe: no devices/emulators found`.
when I go to the `Apply update from ADB` and run the command above I get `error: closed`.
Basically I'm unable to run any adb commands as of the first message, and the only place I can it's from within the update. I've noticed that while in the 'Update via ADB', then in the Win Device Manager I can see that the driver is changed to `Android Composite ADB Interface` and only now it's accepting very limited commands. `adb devices` command generates: `<device id number>: sideload`.
When in the fastboot, it switches to `Android Bootloader Interface` in the DEvice manager.
When in recovery, the device is disconnected from the computer. (is not listed in the device manager)
any thoughts. thanks
Note: that phone was never rooted.
Bootloader looks like this at the moment:
```
Fastboot Mode
Product revision: blueline MP1.0(ROW)
Bootloader version: b1c1-0.4-7617406
Basebandversion...
serial number:
secure booth: PRODUCTION
NOS Production: yes
DRAM: 4GB
Device State: Locked
Boot slot: a
```
Click to expand...
Click to collapse
On my pixel3, /dev/block/dm-4 is mounted to /data. Try "adb shell mount /dev/block/dm-4 /data".
The instructions you are following are very old, and likely obsolete. SuperSu is also obsolete. Try to find a newer method.

dcarvil said:
On my pixel3, /dev/block/dm-4 is mounted to /data. Try "adb shell mount /dev/block/dm-4 /data".
The instructions you are following are very old, and likely obsolete. SuperSu is also obsolete. Try to find a newer method.
Click to expand...
Click to collapse
the issue is I'm unable to run that command `adb shell mount...` with the `no devices/emulator found` message. I believe it's because the device is not even listed in the device manager (windows) when in recovery mode. When in the update mode, then it's listed in the DM. See my post above, I've updated it few times. Thanks
Btw on that link if you check the posts there are newer ones (1.5y back) claiming it works so might actually work

If you're unable to sideload the OTA via PC, I don't think there's any other option besides paying for a repair, or replacing the device. A locked bootloader definitely makes recovery a lot harder.

V0latyle said:
If you're unable to sideload the OTA via PC, I don't think there's any other option besides paying for a repair, or replacing the device. A locked bootloader definitely makes recovery a lot harder.
Click to expand...
Click to collapse
I'm able to sideload the OTA, but restart goes into start being stuck and back and forth but never gets any further than the first google load screen

vajnorcan said:
I'm able to sideload the OTA, but restart goes into start being stuck and back and forth but never gets any further than the first google load screen
Click to expand...
Click to collapse
Were you using adb/fastboot before this happened? Was the device recognised then? If not, are you sure you have the right drivers?

AlexKarimov said:
Were you using adb/fastboot before this happened? Was the device recognised then? If not, are you sure you have the right drivers?
Click to expand...
Click to collapse
I've used the adb to upload the ota and that went, according the message ok, but the system won't start up. Device is recognized only when I choose the "Apply update from ADB" option in recovery mode. The moment I choose it, it shows up as a device in device manager and "adb devices" lists it ok. In fastboot mode it does list it in device manager, but "adb devices" doesn't list it.
It's the latest driver

vajnorcan said:
I've used the adb to upload the ota and that went, according the message ok, but the system won't start up. Device is recognized only when I choose the "Apply update from ADB" option in recovery mode. The moment I choose it, it shows up as a device in device manager and "adb devices" lists it ok. In fastboot mode it does list it in device manager, but "adb devices" doesn't list it.
It's the latest driver
Click to expand...
Click to collapse
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website

AlexKarimov said:
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website
Click to expand...
Click to collapse
This requires OEM Unlocking to be enabled so it won't be much help here.
Rescue Mode might work though.
@vajnorcan try this:
Boot to bootloader and select Rescue Mode using the volume buttons, then press Power to enter it.
On your PC, go to pixelrepair.withgoogle.com and connect the USB cable to your device. Select your carrier or select "Other" if device is unlocked.
I don't know whether this will actually work...I haven't heard of anyone using this tool to successfully recover.

AlexKarimov said:
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website
Click to expand...
Click to collapse
'fastboot devices' is reading the device, which is good. but trying the online flash tool fails due to the device being locked. :/

V0latyle said:
This requires OEM Unlocking to be enabled so it won't be much help here.
Rescue Mode might work though.
@vajnorcan try this:
Boot to bootloader and select Rescue Mode using the volume buttons, then press Power to enter it.
On your PC, go to pixelrepair.withgoogle.com and connect the USB cable to your device. Select your carrier or select "Other" if device is unlocked.
I don't know whether this will actually work...I haven't heard of anyone using this tool to successfully recover.
Click to expand...
Click to collapse
The google tool has found and connected to the device, but it ends up in an error (on the device) and saying "disconnected", looked promising, but not for long. thanks.