I am unable to get into recovery of any type on my Xoom. When I try to get into recovery I get the Android with an exclamation point. I've tried factory reset; I've followed instructions for CWM recovery, etc. I just can't get past the damn Android with the exclamation point (inside a yellow triangle). Can anyone help?
BTW, there are no programs or data on the internal storage of the Xoom.
Use ADB to unlock your device again and push the recovery image again. Then try to boot into recovery.
Ok, I unlocked the Xoom and it rebooted. After the Xoom rebooted, I ran adb reboot bootloader and the Xoom went into fastboot. Now what command do I use to push the recovery image? From the platform-tools directory if tried: "adb fastboot push recovery recovery.img and nothing happened." I then tried "adb fastboot flash recovery recovery.img" without success. Help!
sddenizen said:
Ok, I unlocked the Xoom and it rebooted. After the Xoom rebooted, I ran adb reboot bootloader and the Xoom went into fastboot. Now what command do I use to push the recovery image? From the platform-tools directory if tried: "adb fastboot push recovery recovery.img and nothing happened." I then tried "adb fastboot flash recovery recovery.img" without success. Help!
Click to expand...
Click to collapse
Assuming your in the directory with the recovery.img as well:
Code:
fastboot flash recovery recovery.img
(no adb, no push)
Do the following plz with this recovery image. I assume you already have android sdk installed and adb on your laptop.
To download:
• Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
Steps:
1. Power off your XOOM device.
2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
3. Connect Xoom to your computer via USB.
4. Open a ‘Command Prompt’ or ‘Terminal’ window on your computer in your sdk/tools folder.
5. unlock your xoom and flash the recovery image. The recovery image should be in your current working directory where you have command line navigated to: Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6.img
fastboot reboot adb reboot recovery
Now, you have your device unlocked and recovery installed. I prefer this recovery than others. Give it a try.
Sent from my MZ601 using Tapatalk 2
Thanks, that worked and I'm back in operation with the Xoom. I really appreciate the support this forum provides.
I am happy I could help, and happier you are back to xoom operations without issues
Unlock, reboot and issue resolved!!! Cheers
can i flash custom roms to my nexus I9023 using odin?
if i lost the recovery what should i do?
please help.
You can't use Odin with a Nexus S. Reflash your recovery using fastboot.
nexussgeek said:
can i flash custom roms to my nexus I9023 using odin?
if i lost the recovery what should i do?
please help.
Click to expand...
Click to collapse
Fastboot is much better then ODIN - If you loose access to recovery, you'd still be able to access fastboot/adb and then you can easily flash custom recovery using adb.If you have lost recovery then install pdanet on your computer.(It will also install Nexus S USB Drivers) then put your phone into fastboot mode by holding down both Volume Up and Power buttons together. When you are in fastboot mode connect your phone to your PC using USB cable.Download ADB and recovery you want to flash put it in your C:/recovery (Put adb and recovery image in this folder)
Then open cmd and type
1)CD C:/recovery
2)fastboot flash recovery recoveryname.img (replace recoveryname with actual file name of the recovery image).
2nd command will flash recovery to your phone and then you'd be able to access recovery.
Wow, you learn something every day. Never heard of anyone doing that before.
Thanks
Android-Junky said:
Fastboot is much better then ODIN - If you loose access to recovery, you'd still be able to access fastboot/adb and then you can easily flash custom recovery using adb.If you have lost recovery then install pdanet on your computer.(It will also install Nexus S USB Drivers) then put your phone into fastboot mode by holding down both Volume Up and Power buttons together. When you are in fastboot mode connect your phone to your PC using USB cable.Download ADB and recovery you want to flash put it in your C:/recovery (Put adb and recovery image in this folder)
Then open cmd and type
1)CD C:/recovery
2)fastboot flash recovery recoveryname.img (replace recoveryname with actual file name of the recovery image).
2nd command will flash recovery to your phone and then you'd be able to access recovery.
Click to expand...
Click to collapse
thanks
Can someone help me with a LENOVO TAB 3 TB3-850M stock rom or custom rom that i can flash ? I cannot find anywhere. Installed TWRP and file system got messed up, needed to repartition . Or a TB3-850F, they are pretty much the same
tzmst said:
Can someone help me with a LENOVO TAB 3 TB3-850M stock rom or custom rom that i can flash ? I cannot find anywhere. Installed TWRP and file system got messed up, needed to repartition . Or a TB3-850F, they are pretty much the same
Click to expand...
Click to collapse
Here is a link to my TB3-850F Stock Firmware Images. (/system, /boot, /recovery, /logo). You will need an unlocked bootloader, Minimal ADB & Fastboot v1.4 installed on your PC, proper USB Device Drivers, and the ability to boot into fastboot mode (or recovery mode, and boot into fastboot mode from there). Once you have downloaded my firmware images and are in fastboot mode, open a command window in your adb/fastboot directory with your Tab 3 properly connected to your PC. Type "fastboot devices" - if you are properly connected to your PC with the requisite drivers, the command window will return with your device serial number under "Connected Devices." Once you have ensured a proper connection, execute these commands to install the stock firmware:
fastboot oem fb_mode_set
fastboot flash system system.img
(At this point, because the system.img is a 3GB file, fastboot will automatically condense the file into a series of "sparsechunk" images, which fastboot will flash to your device in series until completed. Note, this process can take a few minutes so be patient. Also, ensure you are using the minimal adb & fastboot from my link (v1.4 or newer) to ensure proper sparsechunk conversion)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash logo logo.img
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
You should now be restored to pure stock firmware condition. Note: this stock firmware is for the Lenovo Tab 3 8"/TB3-850F and has not been tried on the TB3-850M variant. You flash these images at your own risk. Good luck.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
Updated Stock 6.0 ROM posted. Force encryption and dm-verity disabled. TWRP flashable zip.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-t3617594
I am having issues booting into my unofficial TWRP installation on my Moto g stylus 5g after attempting to install an unofficial modded LineageOS image.
My problem: I try to boot into TWRP through the command line on my computer using
Code:
fastboot boot twrp-boot.img
, but my new phone disconnects from my computer before the command can finish. Though TWRP is already installed and I can access it by entering recovery mode without my phone needing to be connected to my computer, the touchscreen on the installation does not work. The touchscreen only works if I use the
Code:
fastboot boot twrp-boot.img
command.
My drivers are the latest version: 33.0.3.
I unlocked the bootloader. To do this, I:
Tapped on the build number to become a developer.
Enabled OEM unlocking and USB debugging.
Unlocked my bootloader.
I installed TWRP recovery. To to this, I:
Downloaded the unofficial TWRP image linked in the first paragraph, as well as the Magisk ZIP.
Ran
Code:
fastboot boot twrp-boot.img
while in bootloader.
Copied the image and the Magisk ZIP from my computer to my phone.
Installed TWRP using "Install Recovery Ramdisk".
Installed Magisk.
I attempted to install LineageOS. To do this, I:
Downloaded OTA ZIP, copy partitions ZIP, and boot image from the LineageOS thread linked in the first paragraph.
Flash booted the boot image.
Selected ADB Sideload mode in Lineage recovery.
Ran
Code:
adb sideload copy-partitions-20210323_1922.zip
and
Code:
adb sideload LineageOS-Modded-19.1-Osaka-V2-OTA.zip
on my computer.
I attempted to re-access TWRP recovery, after Lineage recovery seemed to replace it. To do this, I:
Ran
Code:
fastboot boot twrp-boot.img
while in bootloader.
Installed TWRP using a different method than the previous installation (maybe "Install using this image") because I couldn't copy the installation files to my phone as my phone was no longer writable.
After I rebooted I could no longer use the touchscreen to navigate TWRP. That is, until I figured out
Code:
fastboot boot twrp-boot.img
worked. But after I attempted to enter ADB Sideload mode using TWRP and install one of the ZIP files I needed to install for LineageOS (
Code:
copy-partitions-20210323_1922.zip
), my phone began periodically turning black and disconnecting from my computer, again.
It had been turning black, disconnecting, then turning back on and reconnecting on a regular interval while I was trying to unlock the bootloader. I almost made a post about it. When I tried one more time, just to get the error message I could copy and paste, the command I had been trying to run ran fast enough and it worked. What I had done differently that time was I ran the command right away, without running
Code:
fastboot devices
.
After a while the phone stopped disconnecting periodically. After I installed one ZIP, it started again.
How can I get my phone to stop periodically disconnecting from my computer? How can I access TWRP again?
sharkstalk said:
I am having issues booting into my unofficial TWRP installation on my Moto g stylus 5g after attempting to install an unofficial modded LineageOS image.
My problem: I try to boot into TWRP through the command line on my computer using
Code:
fastboot boot twrp-boot.img
, but my new phone disconnects from my computer before the command can finish. Though TWRP is already installed and I can access it by entering recovery mode without my phone needing to be connected to my computer, the touchscreen on the installation does not work. The touchscreen only works if I use the
Code:
fastboot boot twrp-boot.img
command.
My drivers are the latest version: 33.0.3.
I unlocked the bootloader. To do this, I:
Tapped on the build number to become a developer.
Enabled OEM unlocking and USB debugging.
Unlocked my bootloader.
I installed TWRP recovery. To to this, I:
Downloaded the unofficial TWRP image linked in the first paragraph, as well as the Magisk ZIP.
Ran
Code:
fastboot boot twrp-boot.img
while in bootloader.
Copied the image and the Magisk ZIP from my computer to my phone.
Installed TWRP using "Install Recovery Ramdisk".
Installed Magisk.
I attempted to install LineageOS. To do this, I:
Downloaded OTA ZIP, copy partitions ZIP, and boot image from the LineageOS thread linked in the first paragraph.
Flash booted the boot image.
Selected ADB Sideload mode in Lineage recovery.
Ran
Code:
adb sideload copy-partitions-20210323_1922.zip
and
Code:
adb sideload LineageOS-Modded-19.1-Osaka-V2-OTA.zip
on my computer.
I attempted to re-access TWRP recovery, after Lineage recovery seemed to replace it. To do this, I:
Ran
Code:
fastboot boot twrp-boot.img
while in bootloader.
Installed TWRP using a different method than the previous installation (maybe "Install using this image") because I couldn't copy the installation files to my phone as my phone was no longer writable.
After I rebooted I could no longer use the touchscreen to navigate TWRP. That is, until I figured out
Code:
fastboot boot twrp-boot.img
worked. But after I attempted to enter ADB Sideload mode using TWRP and install one of the ZIP files I needed to install for LineageOS (
Code:
copy-partitions-20210323_1922.zip
), my phone began periodically turning black and disconnecting from my computer, again.
It had been turning black, disconnecting, then turning back on and reconnecting on a regular interval while I was trying to unlock the bootloader. I almost made a post about it. When I tried one more time, just to get the error message I could copy and paste, the command I had been trying to run ran fast enough and it worked. What I had done differently that time was I ran the command right away, without running
Code:
fastboot devices
.
After a while the phone stopped disconnecting periodically. After I installed one ZIP, it started again.
How can I get my phone to stop periodically disconnecting from my computer? How can I access TWRP again?
Click to expand...
Click to collapse
First of all, the command that you tried to use is not even the correct command for fastboot booting TWRP(unless your TWRP file is named "twrp-boot.img" and if the file is stored in your fastboot folder on PC). The correct command is:
fastboot boot twrp.img
The command you typed isn't even an actual command, that I know of. The command you typed is trying to tell fastboot to tell TWRP to boot a boot.img, which, makes no sense at all and isn't how it is done.
There is:
fastboot boot twrp.img
And
fastboot boot boot.img
As far as I know, there is no such thing as:
fastboot boot twrp-boot.img
The way fastboot commands typically work is:
fastboot <what you want fastboot to do> <what you want it to do it to>
In your case, you want to use fastboot command, so, you type: fastboot
You want it to boot a .img, so, you follow that with: boot
You want it to boot a twrp.img, so, you follow that with: twrp.img
If you put that all together in one command, you get:
fastboot boot twrp.img
This command is typically used to boot(not flash) a live TWRP session on devices that have locked bootloader because they can't actually flash TWRP "onto" their device with a locked bootloader. This command would probably actually boot your twrp.img if it is stored in your fastboot folder on PC and if the file is actually named "twrp.img"(you can rename it to "twrp.img" if it isn't). But, it wouldn't be booting the TWRP that is installed in the recovery partition on your device, it would be booting a live TWRP directly from the TWRP file in your fastboot folder. In other words, it boots on your device "from" your PC "onto" the device without flashing it, instead of booting on your device from the recovery partition on your device.
If you wanted to flash the twrp.img, the command would be:
fastboot flash recovery twrp.img
Fastboot followed by what you want fastboot to do(flash recovery) followed by what you want it to do it to(twrp.img).
But, all of that is beside the point because you say you already have TWRP installed. If you already have TWRP installed on your device, you don't need to use the "fastboot boot twrp.img" command line. You should be using adb, with this adb command:
adb reboot recovery
This adb command that I posted is used to boot into TWRP on devices that already have it installed. It is also used to boot into stock recovery if stock recovery installed. In other words, it boots yo whatever recovery you have.
Hopefully, you understood all of that without my wording confusing you.
Droidriven said:
First of all, the command that you tried to use is not even the correct command for fastboot booting TWRP(unless your TWRP file is named "twrp-boot.img" and if the file is stored in your fastboot folder on PC). The correct command is:
fastboot boot twrp.img
The command you typed isn't even an actual command, that I know of. The command you typed is trying to tell fastboot to tell TWRP to boot a boot.img, which, makes no sense at all and isn't how it is done.
There is:
fastboot boot twrp.img
And
fastboot boot boot.img
As far as I know, there is no such thing as:
fastboot boot twrp-boot.img
The way fastboot commands typically work is:
fastboot <what you want fastboot to do> <what you want it to do it to>
In your case, you want to use fastboot command, so, you type: fastboot
You want it to boot a .img, so, you follow that with: boot
You want it to boot a twrp.img, so, you follow that with: twrp.img
If you put that all together in one command, you get:
fastboot boot twrp.img
This command is typically used to boot(not flash) a live TWRP session on devices that have locked bootloader because they can't actually flash TWRP "onto" their device with a locked bootloader. This command would probably actually boot your twrp.img if it is stored in your fastboot folder on PC and if the file is actually named "twrp.img"(you can rename it to "twrp.img" if it isn't). But, it wouldn't be booting the TWRP that is installed in the recovery partition on your device, it would be booting a live TWRP directly from the TWRP file in your fastboot folder. In other words, it boots on your device "from" your PC "onto" the device without flashing it, instead of booting on your device from the recovery partition on your device.
If you wanted to flash the twrp.img, the command would be:
fastboot flash recovery twrp.img
Fastboot followed by what you want fastboot to do(flash recovery) followed by what you want it to do it to(twrp.img).
But, all of that is beside the point because you say you already have TWRP installed. If you already have TWRP installed on your device, you don't need to use the "fastboot boot twrp.img" command line. You should be using adb, with this adb command:
adb reboot recovery
This adb command that I posted is used to boot into TWRP on devices that already have it installed. It is also used to boot into stock recovery if stock recovery installed. In other words, it boots yo whatever recovery you have.
Hopefully, you understood all of that without my wording confusing you.
Click to expand...
Click to collapse
Hello. Thank you for responding. "twrp-boot.img" is just the name of the file on my computer. I changed it to "twrp.img".
I know I don't have to boot a live TWRP session from an image when it is already installed. However, whenever I try to use the TWRP I already installed, I cannot press anything becaue the touchsceen doesn't work. When I boot from live, that touchscreen works. It would be good to know how to fix the touchscreen on the installed version, but I'm willing to make do with booting from live if that is possible.
When I use "fastboot boot twrp.img" after renaming the file (it gave me a "no such file or directory" error before renaming the file), I still have the problem where it loads for a few seconds, then my device does black and disconnects from my computer, then soon goes bright and reconnects to my computer. This is what this looks like in the command line:
fastboot boot twrp.img
Sending 'boot.img' (98304 KB) FAILED (Status read failed (No such device))
fastboot: error: Command failed
Now it is not as though my device was never connected. I can use "fastboot devices" to verify it is connected when the screen isn't black. Also, the output looks different when my phone isn't connected at all:
fastboot boot twrp.img
< waiting for any device >
In one instace, the phone is connected and then disconnects. In the other instance, it is never connected.
My phone disconnects from and reconnects to my computer periodically. That is, roughly every 33-34 seonds. It reconnects quickly without my input (roughly every 4.5 seconds). I used a stopwatch to make sure of this.
Spoiler: Stopwatch Times
Connected (in seconds): 29.22, 34.11, 33.84, 34.03, 34.02, 33.75, 34.04, 34.05, 33.73, 33.93, 33.73
Disconnected: 4.28, 4.45, 4.50, 4.53, 4.51, 4.50, 4.48, 4.80, 4.50, 4.80, 4.60
I tested using "fastboot boot twrp.img" at the beginning of a connected interval. The command ran for the whole 33-34 seconds before the phone disconnected and it gave me that same error. I don't think that command took so long to execute when my phone wasn't turning black periodically. I can run other commands like "fastboot devices".
When my phone isn't connected to my computer, it doesn't turn black every 33-34 seconds.
Entering "adb reboot recovery" produces this error:
adb reboot recovery
error: no devices/emulators found
"adb devices" shows no devices attached. That has always been the case when running adb commands in the bootloader. I can run them when my phone is turned on normally (there is no OS so I can't do that now).
Thank you for your advice. Do you know anything about the phone disconnecting?
sharkstalk said:
Hello. Thank you for responding. "twrp-boot.img" is just the name of the file on my computer. I changed it to "twrp.img".
I know I don't have to boot a live TWRP session from an image when it is already installed. However, whenever I try to use the TWRP I already installed, I cannot press anything becaue the touchsceen doesn't work. When I boot from live, that touchscreen works. It would be good to know how to fix the touchscreen on the installed version, but I'm willing to make do with booting from live if that is possible.
When I use "fastboot boot twrp.img" after renaming the file (it gave me a "no such file or directory" error before renaming the file), I still have the problem where it loads for a few seconds, then my device does black and disconnects from my computer, then soon goes bright and reconnects to my computer. This is what this looks like in the command line:
fastboot boot twrp.img
Sending 'boot.img' (98304 KB) FAILED (Status read failed (No such device))
fastboot: error: Command failed
Now it is not as though my device was never connected. I can use "fastboot devices" to verify it is connected when the screen isn't black. Also, the output looks different when my phone isn't connected at all:
fastboot boot twrp.img
< waiting for any device >
In one instace, the phone is connected and then disconnects. In the other instance, it is never connected.
My phone disconnects from and reconnects to my computer periodically. That is, roughly every 33-34 seonds. It reconnects quickly without my input (roughly every 4.5 seconds). I used a stopwatch to make sure of this.
Spoiler: Stopwatch Times
Connected (in seconds): 29.22, 34.11, 33.84, 34.03, 34.02, 33.75, 34.04, 34.05, 33.73, 33.93, 33.73
Disconnected: 4.28, 4.45, 4.50, 4.53, 4.51, 4.50, 4.48, 4.80, 4.50, 4.80, 4.60
I tested using "fastboot boot twrp.img" at the beginning of a connected interval. The command ran for the whole 33-34 seconds before the phone disconnected and it gave me that same error. I don't think that command took so long to execute when my phone wasn't turning black periodically. I can run other commands like "fastboot devices".
When my phone isn't connected to my computer, it doesn't turn black every 33-34 seconds.
Entering "adb reboot recovery" produces this error:
adb reboot recovery
error: no devices/emulators found
"adb devices" shows no devices attached. That has always been the case when running adb commands in the bootloader. I can run them when my phone is turned on normally (there is no OS so I can't do that now).
Thank you for your advice. Do you know anything about the phone disconnecting?
Click to expand...
Click to collapse
Try this, type:
fastboot devices
Then type:
fastboot reboot recovery
Or
If your device has a bootloader mode, try this, type:
fastboot devices
When it returns the serial number, type:
fastboot reboot bootloader
If you have a bootloader mode/menu, it should boot to that, then either select "reboot recovery" or type:
adb reboot recovery
Or
fastboot reboot recovery
ADB may or may not work in bootloader mode, if you have it.
Are you certain that your bootloader is unlocked and are you certain that you correctly flashed TWRP recovery to the correct partition and that the TWRP.img that you flashed onto the device is an actual TWRP recovery .img and not some kind of modified boot.img? I ask this because in your post above, you typed:
fastboot boot twrp.img
Then it returned
"sending "boot.img"(98304 KB) Failed"
This implies that you are using a boot.img, not a recovery.img/twrp.img. I think your file may be some kind of boot.img to be used in association with something to do with flashing/using TWRP or a boot.ing for your device that is meant to be flashed via TWRP(TWRP can flash .img files)
You can also try booting into your one-touch working TWRP, then, connect a USB hub to your android device and connect a mouse and keyboard, it should natively support the mouse and keyboard, you can use the mouse and keyboard to work inside TWRP to make selections.
Droidriven said:
Try this, type:
fastboot devices
Then type:
fastboot reboot recovery
Or
If your device has a bootloader mode, try this, type:
fastboot devices
When it returns the serial number, type:
fastboot reboot bootloader
If you have a bootloader mode/menu, it should boot to that, then either select "reboot recovery" or type:
adb reboot recovery
Or
fastboot reboot recovery
ADB may or may not work in bootloader mode, if you have it.
Are you certain that your bootloader is unlocked and are you certain that you correctly flashed TWRP recovery to the correct partition and that the TWRP.img that you flashed onto the device is an actual TWRP recovery .img and not some kind of modified boot.img? I ask this because in your post above, you typed:
fastboot boot twrp.img
Then it returned
"sending "boot.img"(98304 KB) Failed"
This implies that you are using a boot.img, not a recovery.img/twrp.img. I think your file may be some kind of boot.img to be used in association with something to do with flashing/using TWRP or a boot.ing for your device that is meant to be flashed via TWRP(TWRP can flash .img files)
You can also try booting into your one-touch working TWRP, then, connect a USB hub to your android device and connect a mouse and keyboard, it should natively support the mouse and keyboard, you can use the mouse and keyboard to work inside TWRP to make selections.
Click to expand...
Click to collapse
Thank you. I tried doing "fastboot devices" then "fastboot reboot recovery" and "fastboot devices" worked and returned a serial number but "fastboot reboot recovery" kept running until the screen turned black and the phone disconnected from my computer. The same thing happened when I tried "fastboot devices" then "fastboot reboot bootloader".
I remember unlocking it by using I code I got from the phone to get another code I got from the Motorola website. It says "flashing_unlocked" on the screen when it hadn't before. I'm pretty sure I unlocked it unless it's supposed to say something else. I've seen another Motorola that just said "unlocked" but it wasn't the same exact device.
I am not certain I flashed TWRP to the correct partition.
I will try connecting a mouse and keyboard so I can use TWRP.