Related
So I just bought this tab. And stupidly upgraded to JB right away (not a big fan with first impression) and was following the 3 step guide for recovery and root on JB. Starting on step 3
When I reboot into bootloader from advanced, or manually (power + V down, then V down to navigate to USB sign, V Up to confirm (already unlocked bootloader of cource)
In the top left corner where the words are, the last line says "starting fastboot mode" or something like that, but nothing just stuck in the bootloader screen with 4 options RCK, ANDROID, FASTBOOT, AND WIPE DATA. Untilled I hold power to reboot.
Tried several times. What am I doing wrong?
trevor7428 said:
So I just bought this tab. And stupidly upgraded to JB right away (not a big fan with first impression) and was following the 3 step guide for recovery and root on JB. Starting on step 3
When I reboot into bootloader from advanced, or manually (power + V down, then V down to navigate to USB sign, V Up to confirm (already unlocked bootloader of cource)
In the top left corner where the words are, the last line says "starting fastboot mode" or something like that, but nothing just stuck in the bootloader screen with 4 options RCK, ANDROID, FASTBOOT, AND WIPE DATA. Untilled I hold power to reboot.
Tried several times. What am I doing wrong?
Click to expand...
Click to collapse
Hi,
you are doing everything fine....
It just stays there when "starting fastboot mode" appears!
Now you can open a terminal on your pc.
When you enter "fastboot devices" (without quotes), a number will appear so you know the device will be recognized when you want to flash recovery. Just like "adb devices".
Do you have to enter fastboot devices first to flash recovery threw adb?
Cause last night after it said starting fastboot (when I thought it was stuck)
I extracted the twrp Jb recovery from same post. To the same folder as adb.exe and fastboot.exe (named the folder fastboot on the C drive) shift + right click on fastboot folder - open in command prompt
fastboot -i 0x0b05 flash recovery tf300t-jb.blob
The responded was like can't complete command. File or folder doesn't exist (or something like that, will try again when I get home with the exact response)
And tried extract to a folder named, recovery1 on my c drive
C:\recovery1: fastboot -i 0x0b05 flash recovery tf300t-jb.blob
Still with the same response
Thank you for the help
trevor7428 said:
Do you have to enter fastboot devices first to flash recovery threw adb?
Cause last night after it said starting fastboot (when I thought it was stuck)
I extracted the twrp Jb recovery from same post. To the same folder as adb.exe and fastboot.exe (named the folder fastboot on the C drive) shift + right click on fastboot folder - open in command prompt
fastboot -i 0x0b05 flash recovery tf300t-jb.blob
The responded was like can't complete command. File or folder doesn't exist (or something like that, will try again when I get home with the exact response)
And tried extract to a folder named, recovery1 on my c drive
C:\recovery1: fastboot -i 0x0b05 flash recovery tf300t-jb.blob
Still with the same response
Thank you for the help
Click to expand...
Click to collapse
Try fastboot -i 0x0b05 flash recovery C:\recovery1\tf300t-jb.blob
Thank you so much, that did the trick
I'm supposedly on fastboot mode. on the One x, I can run a command to confirm I'm connected but unsure what to do using the infinity since the fastboot commands is a different.
I ran this command "fastboot -i 0x0b05 flash staging ebtblob.bin" (part of nvflash steps) and it's stuck at "waiting for device".
When connected to my windows laptop, it says "ASUS Android composite ADB interface" in device manager when booted normally. And it says "AsUS Android bootloader interface" when I'm supposedly in fastboot.
thanks
mrjayviper said:
I'm supposedly on fastboot mode. on the One x, I can run a command to confirm I'm connected but unsure what to do using the infinity since the fastboot commands is a different.
I ran this command "fastboot -i 0x0b05 flash staging ebtblob.bin" (part of nvflash steps) and it's stuck at "waiting for device".
thanks
Click to expand...
Click to collapse
"fastboot devices" should show something. With the old bootloader, maybe just "???????? - device" - with a newer one, an actual serial number.
"fastboot continue" should continue booting Android, that would be a sign that the protocol basically works.
_that said:
"fastboot devices" should show something. With the old bootloader, maybe just "???????? - device" - with a newer one, an actual serial number.
"fastboot continue" should continue booting Android, that would be a sign that the protocol basically works.
Click to expand...
Click to collapse
just says waiting for device.
tried:
1. fastboot continue
2. fastboot -i 0x0b05 continue
3. the nvflash command above
4. fasboot reboot
5. fastboot -i 0x0b05 reboot
I was on 4.0.3 ICS before unlocking and I suppose still on 4.0.3 just unlocked. thanks!
My tf 700t is stop in a restarting loop until the battery is finished.... i have tried booting into recovery but the logo of the recovery TwRP apear and the tablet restarts itself to that point ,until the battery is dead.
Any sugestions?
the tablet is rooted and i was on KatKiss rom on the moment of the crash for about 5 months.
Try this:
http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my Nexus 5X using Tapatalk
I'm having the exact same issue.
I can occasionally get into the bootloader, but when I try to get into TWRP it will show the logo page and will immediately restarts.
Following the link you sent, I tried the adb devices prompt, but it showed up blank. Do I need to be in TWRP for adb to work? When I try to get into TWRP it just restarts.
Not sure what my options are when the only screen I can get into is the fastboot.
wldtravel26 said:
I'm having the exact same issue.
I can occasionally get into the bootloader, but when I try to get into TWRP it will show the logo page and will immediately restarts.
Following the link you sent, I tried the adb devices prompt, but it showed up blank. Do I need to be in TWRP for adb to work? When I try to get into TWRP it just restarts.
Not sure what my options are when the only screen I can get into is the fastboot.
Click to expand...
Click to collapse
If you can get into fastboot yours is a very different situation. But let me answer your questions first.
The linked method works if you have adb access in TWRP - however briely. Even if TWRP loops you should have adb access at some point (open Device Manager and watch for changes).
If TWRP is just bootlooping very quickly you may be out of luck but I have seen cases where a little window of adb access and careful timing of the commands let people push the file to internal and insmod it. But that depends on the nature of the bootloop, the skill of the user and persistence.
Now, if you have fastboot access you don't need any of that. In fastboot you have a pretty powerful tool to wipe and format partitions, flash the Asus blob if all fails, but you quite a few options....
If you can get "only occasionally" into the bootloader I would not wait much longer but perform a full wipe of the major partitions and flash the Asus system blob, returning the tablet to stock basically and giving you a fresh start.
We call it a @Buster99
Download the latest Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95u/8/
Extract it twice and copy the blob into your fastboot directory.
Issue these commands in fastboot one by one:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Good luck!
Thanks Berndblb. I downloaded the Asus firmware and was able to get the blob file.
But I'm fine with totally starting over and trying Buster99, but I'm still unable to get the ADB to see the device.
I've gone through the beginners guide to root and flashing a custom rom again, but I still can't see the device when I type in "fastboot devices".
If you have any advice or a guide on what I need to do get where I can use ADB to erase everything and start over again.
i cant do anything the tablet starts - shows asus logo-go to TWRP logo screen - restarts (all in 32 seconds). Any other sugestion? if i dismantle the tablet ? or anithing else?
Thank You
wldtravel26 said:
Thanks Berndblb. I downloaded the Asus firmware and was able to get the blob file.
But I'm fine with totally starting over and trying Buster99, but I'm still unable to get the ADB to see the device.
I've gone through the beginners guide to root and flashing a custom rom again, but I still can't see the device when I type in "fastboot devices".
If you have any advice or a guide on what I need to do get where I can use ADB to erase everything and start over again.
Click to expand...
Click to collapse
Either you do not have the correct driver installed or your usb cable is not original but a cheap "charge only" knockoff or try a different usb port or you are not open the cmd prompt from the fastboot directory or your usb port is busted.....
I don't know how to troubleshoot that from here....
Please search the TF700 forum or google "fastboot driver problems". That problem is so common, I really do not know what to add to advice that's out there a hundred times over....
---------- Post added at 04:29 PM ---------- Previous post was at 04:25 PM ----------
mallasorte2000 said:
i cant do anything the tablet starts - shows asus logo-go to TWRP logo screen - restarts (all in 32 seconds). Any other sugestion? if i dismantle the tablet ? or anithing else?
Thank You
Click to expand...
Click to collapse
You can always install a new r used mainboard, but that's the only reason to open it up....
Sorry man, if you do not have adb while the recovery is looping or starting up and you cannot get into fastboot, there's nothing you can do.....
Except for the really crazy and desperate "throw away reason" stuff of course. Like stuffing the tablet into the freezer in an airtight bag for 30 min, then try to boot it......
Thanks Berndblb, I was able to get through the Buster 99 instructions above.
Per the last step I would have expected the tablet to reboot, but that did not happen.
When I restarted it I got the following error when I tried to load Andriod "unrecoverable bootloader error".
I used the following file from the Asus website US_epaduser10_6_1_14_10_UpdateLauncher, based on the fact that my bootloader shows the tablet as "US_epad-10.6.1.14.10-20130801". Hopefully I used the right file for the blob file.
I've attached what I have from adb for the system flash blob and reboot. I tried to screen shoot it in a better format, but that didn't work.
Hopefully someone will be able to take a look and direct me in the right way to get this working again.
C:\adb>fastboot devices
015d2a5086641a19 fastboot
C:\adb>fastboot - i 0x0B05 flash system blob
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\adb>fastboot - i 0x0b05 reboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
wldtravel26 said:
Thanks Berndblb, I was able to get through the Buster 99 instructions above.
Per the last step I would have expected the tablet to reboot, but that did not happen.
When I restarted it I got the following error when I tried to load Andriod "unrecoverable bootloader error".
I used the following file from the Asus website US_epaduser10_6_1_14_10_UpdateLauncher, based on the fact that my bootloader shows the tablet as "US_epad-10.6.1.14.10-20130801". Hopefully I used the right file for the blob file.
I've attached what I have from adb for the system flash blob and reboot. I tried to screen shoot it in a better format, but that didn't work.
Hopefully someone will be able to take a look and direct me in the right way to get this working again.
Click to expand...
Click to collapse
You used the correct file but I see a mistake in your command.
You put a space between the dash and the "i" in your command: fastboot - i 0x0B05 which is a command fastboot does not understand so it shows you the help file so to speak.
It is supposed to be fastboot -i 0x0B05.
See the difference?
Try it again and welcome to the world of the command line
A thousand thanks Berndblb. I was able to get it flashed and it back to the original firmware. Thought for a while, it was a total loss, so your advise was a big help.
On another note, I was having this issue with multiple custom roms, which leads me to believe it a hardware issue.
If I press on the screen too hard or lift it in a different angle, it will freeze up and try to reboot.
I was just able to get past the initial setup, but once I lifted the tablet up again, it did the same thing and froze.
I had basically been stuck, just using the tablet for strictly steaming purposes and leaving in on a table.
If anyone has had similar issues or has any insight let me know.
My wife is asking for a new Ipad if we can't get it to work properly, I'm still trying to convince her to stick with Android but this tablet isn't helping my case.
wldtravel26 said:
A thousand thanks Berndblb. I was able to get it flashed and it back to the original firmware. Thought for a while, it was a total loss, so your advise was a big help.
On another note, I was having this issue with multiple custom roms, which leads me to believe it a hardware issue.
If I press on the screen too hard or lift it in a different angle, it will freeze up and try to reboot.
I was just able to get past the initial setup, but once I lifted the tablet up again, it did the same thing and froze.
I had basically been stuck, just using the tablet for strictly steaming purposes and leaving in on a table.
If anyone has had similar issues or has any insight let me know.
My wife is asking for a new Ipad if we can't get it to work properly, I'm still trying to convince her to stick with Android but this tablet isn't helping my case.
Click to expand...
Click to collapse
damn i feel so used
grats on getting it to work again.
in regard to the troubles you are still having: is it in the Keydock or without, also a possibility that the display has an issue with the digitizer and shortens out.
cheers
Buster
I typically use it without the dock. Haven't put it in the dock in a while. Yea I was thinking the same thing where maybe something is loose inside.
Short of changing out the whole digitizer, do you know of any trouble shooting I can do if I open it up? If it keeps doing this, the tablet itself isn't worth using often. I did have a gumdrop case on it most of the time. I've got a toddler, so wanted maximum protection for it. Maybe it overheated or something?
Check out some tear down videos on YouTube and iFixit, then open it up and check all connectors you can get your hands or tools on. It does sound as if you gave a connection shorting out.
Sent from my Nexus 5X using Tapatalk
berndblb said:
If you can get into fastboot yours is a very different situation. But let me answer your questions first.
The linked method works if you have adb access in TWRP - however briely. Even if TWRP loops you should have adb access at some point (open Device Manager and watch for changes).
If TWRP is just bootlooping very quickly you may be out of luck but I have seen cases where a little window of adb access and careful timing of the commands let people push the file to internal and insmod it. But that depends on the nature of the bootloop, the skill of the user and persistence.
Now, if you have fastboot access you don't need any of that. In fastboot you have a pretty powerful tool to wipe and format partitions, flash the Asus blob if all fails, but you quite a few options....
If you can get "only occasionally" into the bootloader I would not wait much longer but perform a full wipe of the major partitions and flash the Asus system blob, returning the tablet to stock basically and giving you a fresh start.
We call it a @Buster99
Download the latest Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95u/8/
Extract it twice and copy the blob into your fastboot directory.
Issue these commands in fastboot one by one:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Good luck!
Click to expand...
Click to collapse
I also got into a bootloop situation and was unable to connect via adb (adb usb gave me "error: device not found") but fastboot was ok. So I tried the @Buster99 rescue. Unfortunately it failed at the flash system blob step. It gave "FAILED (data transfer failure (unknown error))...".
It's been too long since I used adb and fastboot. Lately my TF700T had become erratic, unstable and experiencing sudden reboots so I wanted to format data and do clean re-install of KatshMallow #29. I also had discovered that the digitizer had developed a blind-spot, actually more of a whole blind column of about a quarter inch wide, giving me problems swiping a TWRP button to unlock the screen. So, I went to change TWRP's screen timeout setting (TWRP 2.8.4.0 Kang) to max when suddenly it rebooted into a system bootloop. Going to TWRP would go to bootloop again at the TWRP splash screen.
Alas, I must have forgotten to set the USB debug mode after the last flashing as I am now locked out of adb. That's how I got into this unfortunate situation.
Any ideas, short of replacing TF700T's mb? Looks like this is the end of a long journey with my TF700T! :crying:
Kraka said:
I also got into a bootloop situation and was unable to connect via adb (adb usb gave me "error: device not found") but fastboot was ok. So I tried the @Buster99 rescue. Unfortunately it failed at the flash system blob step. It gave "FAILED (data transfer failure (unknown error))...".
It's been too long since I used adb and fastboot. Lately my TF700T had become erratic, unstable and experiencing sudden reboots so I wanted to format data and do clean re-install of KatshMallow #29. I also had discovered that the digitizer had developed a blind-spot, actually more of a whole blind column of about a quarter inch wide, giving me problems swiping a TWRP button to unlock the screen. So, I went to change TWRP's screen timeout setting (TWRP 2.8.4.0 Kang) to max when suddenly it rebooted into a system bootloop. Going to TWRP would go to bootloop again at the TWRP splash screen.
Alas, I must have forgotten to set the USB debug mode after the last flashing as I am now locked out of adb. That's how I got into this unfortunate situation.
Any ideas, short of replacing TF700T's mb? Looks like this is the end of a long journey with my TF700T! :crying:
Click to expand...
Click to collapse
Did you ever get it fixed? I'm in the same situation. Can't enter recovery or fastboot. Well, I entered fastboot once, chose recovery, now it boot loops straight to recovery. This sucks. Tablet worked fine for months.
If you can't boot into fastboot and you do not have adb access when in recovery, you're done. Nothing left to do.
You did not mention if you are unlocked. With a locked bootloader you can't do anything even if you have adb in recovery or if you could boot to fastboot. Sorry
It is unlocked and rooted. I see something showing up in Device Manager, only it says Google Nexus ADB interface. I can also enter the other mode with Power and Vol Up. This mode holds, however, not sure if I can do much from there.
Now I got TWRP screen stuck, so at least it's not looping. But adb commands don't produce any effect.
xxhaimbondxx said:
It is unlocked and rooted. I see something showing up in Device Manager, only it says Google Nexus ADB interface. I can also enter the other mode with Power and Vol Up. This mode holds, however, not sure if I can do much from there.
Click to expand...
Click to collapse
What do you mean? APX? No, that does not help you
xxhaimbondxx said:
Now I got TWRP screen stuck, so at least it's not looping. But adb commands don't produce any effect.
Click to expand...
Click to collapse
With TWRP booted, do you see the adb recovery interface in device manager and what do you get with "adb devices"? Do you have the drivers installed?
berndblb said:
With TWRP booted, do you see the adb recovery interface in device manager and what do you get with "adb devices"? Do you have the drivers installed?
Click to expand...
Click to collapse
This is the only thing I see in Device Manager: Google Nexus ADB interface. I installed the Universal Drivers.
When I type adb devices, I get nothing.
Well, this one time I got this:
adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
It's very, very, unfortunate that this happened so early in the life of my new Pixel 2. Here's what I did:
fastboot oem unlock
Device erases and boots normally, power off and boot into bootloader using volume and power.
Flash Android 8.1 beta using flash-all.bat
<Device is stuck in bootloader>
Flash factory Android 8.0 image, same thing
Try "fastboot --set-active=a" followed by "fastboot continue" and "fastboot --set-active b" followed by "fastboot continue", neither worked.
Try entering recovery or download mode from bootloader, neither worked.
I contacted Google support, and they didn't have any suggestions other than an RMA, so a new device should be on the way soon. Given the comments in this thread about using the wrong version of fastboot, I'll point out that I do have the latest version of platform-tools, and my fastboot version is:
Code:
C:\>fastboot --version
fastboot version 3db08f2c6889-android
Installed as C:\android-platform-tools\fastboot.exe
Anyone else have this experience? (I hope not.)
Edit: Okay, thanks to this post, I learned that I flash-all.bat, which uses "fastboot -w update image-*.zip", leads to this condition. However, flashing each img file in the zip archive individually gets the device back to health. Phew.
can you share the .bat file please?
I didn't use a bat script to recover the device, I typed each "fastboot flash <partition> <partition>.img" command by hand. Not the most efficient, but I wasn't expecting to do this more than once.
It's possible you had a bad download, did you attempt to redownload the stock image?
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.