Related
Or the distributed boot / system / data (rom) for restoration?
I figured to HTCDEV unlock to allow fastboot to write to recovery
and then fastboot boot twrp to backup whats there before overlaying it.
why not try it?
https://forum.xda-developers.com/showthread.php?t=2798853
fuzzynco said:
Or the distributed boot / system / data (rom) for restoration?
I figured to HTCDEV unlock to allow fastboot to write to recovery
and then fastboot boot twrp to backup whats there before overlaying it.
Click to expand...
Click to collapse
Yes.
Captain_Throwback said:
One thing to note is that you CAN fastboot boot TWRP on this device, so if you don't want to overwrite stock recovery, you don't have to
Click to expand...
Click to collapse
Just make sure to do that from the bootloader menu, not the download mode. Download didn't work for me, command line in Windows was stuck on booting and the download mode said finished flashing, that's it. Once rebooted to the bootloader menu everything was fine. That's how I backed my original recovery as well. You'll probably need to unlock the bootloader on htcdev first though, at least that's what I did.
BolecDST said:
Just make sure to do that from the bootloader menu, not the download mode. Download didn't work for me, command line in Windows was stuck on booting and the download mode said finished flashing, that's it. Once rebooted to the bootloader menu everything was fine. That's how I backed my original recovery as well. You'll probably need to unlock the bootloader on htcdev first though, at least that's what I did.
Click to expand...
Click to collapse
Yes, I figured that, (htcdev.com bootloader unlock).
Thanks for the pointer, I really don't know which mode is for what ...
I think bootloader mode is for direct fastboot flashing
fastboot flash <partition> <file>
or fastboot boot <file>
and download mode & RUU mode is for things packaged
like an RUU. fastboot flash zip <file>
fastboot oem <--->
fuzzynco said:
Yes, I figured that, (htcdev.com bootloader unlock).
Thanks for the pointer, I really don't know which mode is for what ...
I think bootloader mode is for direct fastboot flashing
fastboot flash <partition> <file>
or fastboot boot <file>
and download mode & RUU mode is for things packaged
like an RUU. fastboot flash zip <file>
fastboot oem <--->
Click to expand...
Click to collapse
Recovery is to be flashed in download mode as has been on the HTC 10 the case. In fact download mode can be viewed at as fastboot mode of the phone.
Sent from my htc_pmeuhl using XDA Labs
Left a note here.
My first-batch U11 can be booted to twrp with "fastboot boot twrp-blahblah.img" under bootloader menu (I wish I didn't remember it wrong)
But it can't be done after it came back from repair (no power issue with unknown reason), which motherboard had been replaced and updated to Oreo already.
Anyway, it seems that stock-recovery backup is not required since there's reliable source of stock-recovery which inside the OTA file.
whenever i try to go into recovery mode, it takes me to the default one even after i flashed twrp. my bootloader is unlocked and i flashed twrp several times. even when i use the command prompt from fastboot mode it still takes me to the default recovery. any ideas to what's wrong?
Asafbzm said:
whenever i try to go into recovery mode, it takes me to the default one even after i flashed twrp. my bootloader is unlocked and i flashed twrp several times. even when i use the command prompt from fastboot mode it still takes me to the default recovery. any ideas to what's wrong?
Click to expand...
Click to collapse
This could be a solution or a workaround:
"Hello i just had a personal experience with my Asus zenfone selfie Z00T Stock recovery kept replacing TWRP. (Boot loader already unlocked)
This is how i got around it i downloaded the latest TWRP for my device and placed directly in minimal adb and fastboot app folder then i renamed it to recovery .
then i put my device in fastboot mode using the buttons on the phone and After i ran minimal adb and fastboot app as admin then i typed fastboot flash recovery recovery.img
once done i then i typed fastboot boot recovery.img. and my phone booted to twrp recovery then i selected reboot recovery directly on my phone and to finish reboot system (still in twrp) that's it.
(OEM commands to boot from fastboot to recovery do not work on some devices )
it only worked for me eventually because i downloaded the latest TWRP from the official TWRP website.
The idea is to flash the custom recovery and then booting from the custom recovery.img that you just used to flash (the one still on the pc) using minimal adb and fastboot app.
IT may not work on all devices as the commands may change from one device to another but the idea stays the same. (example for nexus fastboot -c "lge.kcal=0|0|0|x" boot recovery.img)
I hope this will help some people out."
sill not booting into twrp
Tiqqy said:
This could be a solution or a workaround:
"Hello i just had a personal experience with my Asus zenfone selfie Z00T Stock recovery kept replacing TWRP. (Boot loader already unlocked)
This is how i got around it i downloaded the latest TWRP for my device and placed directly in minimal adb and fastboot app folder then i renamed it to recovery .
then i put my device in fastboot mode using the buttons on the phone and After i ran minimal adb and fastboot app as admin then i typed fastboot flash recovery recovery.img
once done i then i typed fastboot boot recovery.img. and my phone booted to twrp recovery then i selected reboot recovery directly on my phone and to finish reboot system (still in twrp) that's it.
(OEM commands to boot from fastboot to recovery do not work on some devices )
it only worked for me eventually because i downloaded the latest TWRP from the official TWRP website.
The idea is to flash the custom recovery and then booting from the custom recovery.img that you just used to flash (the one still on the pc) using minimal adb and fastboot app.
IT may not work on all devices as the commands may change from one device to another but the idea stays the same. (example for nexus fastboot -c "lge.kcal=0|0|0|x" boot recovery.img)
I hope this will help some people out."
Click to expand...
Click to collapse
i've just tried this but the 'fastboot boot recovery' command just turn the phone back on from fastboot. thanks anyways!
Tiqqy said:
This could be a solution or a workaround:
"Hello i just had a personal experience with my Asus zenfone selfie Z00T Stock recovery kept replacing TWRP. (Boot loader already unlocked)
This is how i got around it i downloaded the latest TWRP for my device and placed directly in minimal adb and fastboot app folder then i renamed it to recovery .
then i put my device in fastboot mode using the buttons on the phone and After i ran minimal adb and fastboot app as admin then i typed fastboot flash recovery recovery.img
once done i then i typed fastboot boot recovery.img. and my phone booted to twrp recovery then i selected reboot recovery directly on my phone and to finish reboot system (still in twrp) that's it.
(OEM commands to boot from fastboot to recovery do not work on some devices )
it only worked for me eventually because i downloaded the latest TWRP from the official TWRP website.
The idea is to flash the custom recovery and then booting from the custom recovery.img that you just used to flash (the one still on the pc) using minimal adb and fastboot app.
IT may not work on all devices as the commands may change from one device to another but the idea stays the same. (example for nexus fastboot -c "lge.kcal=0|0|0|x" boot recovery.img)
I hope this will help some people out."
Click to expand...
Click to collapse
Work for me. Thanks buddy
This works, thumb up
Asafbzm said:
i've just tried this but the 'fastboot boot recovery' command just turn the phone back on from fastboot. thanks anyways!
Click to expand...
Click to collapse
i have suffered with the same problem for hours until i decided to come here and look for related article , it actually worked and made me wonder that it wasn't that hard to fix it , i just rebooted fastboot and flashed twrp and in the end typed 'fastboot reboot recovery.img
that solved my suffering within 5 seconds. thank you for sharing the knowledge
Tiqqy said:
This could be a solution or a workaround:
"Hello i just had a personal experience with my Asus zenfone selfie Z00T Stock recovery kept replacing TWRP. (Boot loader already unlocked)
This is how i got around it i downloaded the latest TWRP for my device and placed directly in minimal adb and fastboot app folder then i renamed it to recovery .
then i put my device in fastboot mode using the buttons on the phone and After i ran minimal adb and fastboot app as admin then i typed fastboot flash recovery recovery.img
once done i then i typed fastboot boot recovery.img. and my phone booted to twrp recovery then i selected reboot recovery directly on my phone and to finish reboot system (still in twrp) that's it.
(OEM commands to boot from fastboot to recovery do not work on some devices )
it only worked for me eventually because i downloaded the latest TWRP from the official TWRP website.
The idea is to flash the custom recovery and then booting from the custom recovery.img that you just used to flash (the one still on the pc) using minimal adb and fastboot app.
IT may not work on all devices as the commands may change from one device to another but the idea stays the same. (example for nexus fastboot -c "lge.kcal=0|0|0|x" boot recovery.img)
I hope this will help some people out."
Click to expand...
Click to collapse
I had the same issue on Poco F1 and this worked for me as well! Pleasant surprise. First result on google was this article and it worked, 2 minutes work.
Lamantin001 said:
I had the same issue on Poco F1 and this worked for me as well! Pleasant surprise. First result on google was this article and it worked, 2 minutes work.
Click to expand...
Click to collapse
Okay, I was a bit too early with that. The next time I turned off the phone and tried booting to recovery (Vol up+pwr), I got booted into factory recovery (mi-recovery 3.0) :/
Lamantin001 said:
Okay, I was a bit too early with that. The next time I turned off the phone and tried booting to recovery (Vol up+pwr), I got booted into factory recovery (mi-recovery 3.0) :/
Click to expand...
Click to collapse
Update:
I found the solution. I followed the steps in this article:
How can I keep MIUI from overwrite TWRP with stock recovery after a ROM flash?
I'm on fw Global 9.6.6.0. (Bought the phone 'bogus' unlocked with "fake" 9.6.4.0, bricked it while trying to restore chinese fw and re-lock bootloader using miflash - I'm not doing that again brought it back to life using the steps from...
forum.xda-developers.com
Asafbzm said:
whenever i try to go into recovery mode, it takes me to the default one even after i flashed twrp. my bootloader is unlocked and i flashed twrp several times. even when i use the command prompt from fastboot mode it still takes me to the default recovery. any ideas to what's wrong?
Click to expand...
Click to collapse
Try this:
when you are in fastboot mode type:
Code:
fastboot boot recovery.img
This command will boot your phone to twrp. Install twrp .zip file (there are 2 options when installing .img or .zip)
after this go to ADB/Sideload - This is in Advanced section
Then swipe to start a sideload. Now on your pc type:
Code:
adb sideload recovery.zip
This worked for me. I hope this works for you too
Could anyone please help with a guide for rooting Nokia 3 and flashing TWRP that works for Android 9.0?
Thanks.
It's very easy if you have the bootloader already unlocked.
1.- Download magisk apk from github
2.- Install and download the zip
3.- Move the zip to a sd card
4.- Flash twrp using Sp Flash Tools
5.- Boot into recovery and flash magisk zip
That's all
I tried yesterday
Zhowlx said:
It's very easy if you have the bootloader already unlocked.
1.- Download magisk apk from github
2.- Install and download the zip
3.- Move the zip to a sd card
4.- Flash twrp using Sp Flash Tools
5.- Boot into recovery and flash magisk zip
That's all
I tried yesterday
Click to expand...
Click to collapse
Thank you for your answer.
What if you don't have your bootloader unlocked ? Do you just need to check the "Unlock Bootloader" switch in the developers options ? Thank you
Soupape50 said:
Thank you for your answer.
What if you don't have your bootloader unlocked ? Do you just need to check the "Unlock Bootloader" switch in the developers options ? Thank you
Click to expand...
Click to collapse
The only way Is unlocking the bootloader
Just follow this steps and it's done
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
Zhowlx said:
The only way Is unlocking the bootloader
Just follow this steps and it's done
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
Click to expand...
Click to collapse
Thank you really much for your answer, but I don't think this tutorial works on android Pie :/
unfortunately not, I downgrade the android version to nougat and from there I did the whole process, then updated to oreo and then to android p
Zhowlx said:
It's very easy if you have the bootloader already unlocked.
1.- Download magisk apk from github
2.- Install and download the zip
3.- Move the zip to a sd card
4.- Flash twrp using Sp Flash Tools
5.- Boot into recovery and flash magisk zip
That's all
I tried yesterday
Click to expand...
Click to collapse
have tried it?
Zhowlx said:
It's very easy if you have the bootloader already unlocked.
1.- Download magisk apk from github
2.- Install and download the zip
3.- Move the zip to a sd card
4.- Flash twrp using Sp Flash Tools
5.- Boot into recovery and flash magisk zip
That's all
I tried yesterday
Click to expand...
Click to collapse
Can you give more details like what zip ? what apk ( magisk or magisk manager)? How to boot into recovery? (Samsung is easier to boot than nokia so i dont know how to)
Zhowlx said:
unfortunately not, I downgrade the android version to nougat and from there I did the whole process, then updated to oreo and then to android p
Click to expand...
Click to collapse
Hey. How to downgrade nokia 3 from pie to nogaut ? I want to root my device
before you do this just remember this wipes your phone
you can unlock your nokia 3 on 9.0 just make sure bootloader is unlocked in dev settings and boot into fastboot.
then run the following commands
fastboot -i 0x2e04 oem key [MD5-key]
fastboot flashing unlock_critical
fastboot flash boot [path to whatever you're flashing e.g. magisk]
then run
fastboot reboot
and your phone will be rooted and the bootloader unlocked
NulledRoot said:
before you do this just remember this wipes your phone
you can unlock your nokia 3 on 9.0 just make sure bootloader is unlocked in dev settings and boot into fastboot.
then run the following commands
fastboot -i 0x2e04 oem key [MD5-key]
fastboot flashing unlock_critical
fastboot flash boot [path to whatever you're flashing e.g. magisk]
then run
fastboot reboot
and your phone will be rooted and the bootloader unlocked
Click to expand...
Click to collapse
How can I remove the orange state?
I mean, currently, if I lock the bootloader again, I get a red state.
and I can only skip it, if I connect it to the usb.
and start normally, without any status warning, if it is connected to the usb
djxpro said:
How can I remove the orange state?
I mean, currently, if I lock the bootloader again, I get a red state.
and I can only skip it, if I connect it to the usb.
and start normally, without any status warning, if it is connected to the usb
Click to expand...
Click to collapse
perhaps flash an unmodified boot image?
NulledRoot said:
perhaps flash an unmodified boot image?
Click to expand...
Click to collapse
that implies then that I could not root it.
****
I guess I'll keep the orange state.
NulledRoot said:
fastboot -i 0x2e04 oem key [MD5-key]
Click to expand...
Click to collapse
>>>>fastboot: unknown option -- i
TA-1032, android 9 (00W_5_120_SP02), OEM unlocking in dev.opt. enabled.
NOWAY!
ORANGE STATE (^_^)
fastboot oem key [md5 KEY]
fastboot flashing unlock
fastboot reboot
NulledRoot said:
before you do this just remember this wipes your phone
you can unlock your nokia 3 on 9.0 just make sure bootloader is unlocked in dev settings and boot into fastboot.
then run the following commands
fastboot -i 0x2e04 oem key [MD5-key]
fastboot flashing unlock_critical
fastboot flash boot [path to whatever you're flashing e.g. magisk]
then run
fastboot reboot
and your phone will be rooted and the bootloader unlocked[/QUOTE
How to get MD5-key ?
Click to expand...
Click to collapse
Hasnain77 said:
NulledRoot said:
before you do this just remember this wipes your phone
you can unlock your nokia 3 on 9.0 just make sure bootloader is unlocked in dev settings and boot into fastboot.
then run the following commands
fastboot -i 0x2e04 oem key [MD5-key]
fastboot flashing unlock_critical
fastboot flash boot [path to whatever you're flashing e.g. magisk]
then run
fastboot reboot
and your phone will be rooted and the bootloader unlocked[/QUOTE
How to get MD5-key ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
you need your SN from your phone and put it on the web that is in the thread
Click to expand...
Click to collapse
NulledRoot said:
before you do this just remember this wipes your phone
you can unlock your nokia 3 on 9.0 just make sure bootloader is unlocked in dev settings and boot into fastboot.
then run the following commands
fastboot -i 0x2e04 oem key [MD5-key]
fastboot flashing unlock_critical
fastboot flash boot [path to whatever you're flashing e.g. magisk]
then run
fastboot reboot
and your phone will be rooted and the bootloader unlocked
Click to expand...
Click to collapse
I am in very trouble to rooting my Nokia 3 ta-1032 pie... Pls help me how to unlock bootloader and flash twrp and root on nokia 3 pie security patch 5 October 2019:crying::crying:help me plz
aditya#777 said:
I am in very trouble to rooting my Nokia 3 ta-1032 pie... Pls help me how to unlock bootloader and flash twrp and root on nokia 3 pie security patch 5 October 2019:crying::crying:help me plz
Click to expand...
Click to collapse
get the twrp recovery image file from unofficialtwrp.com/nokia-3-root-twrp-3-2-3 ....
rename the file to recovery.img and put the file in adb directory.....also put the magisk.zip file in the sd card (don't put it in the internal memory)
then get into fastboot mode....then enter the following commands....
fastboot oem key [md5 hash]
fastboot flashing unlock
fastboot flash recovery recovery.img
fastboot reboot
while rebooting, instantly press vol up+power to go into recovery mode( dont let the phone to boot normally or you will have to flash twrp again and your phone might be in orange state but ignore that)....if it shows "no command" press the same buttons at the same time to get into recovery mode.....then install the magisk.zip and reboot....then install magisk.apk and you are done.... tried and tested on nokia 3 ta- 1032 android pie just today and it worked...
mech59 said:
get the twrp recovery image file from unofficialtwrp.com/nokia-3-root-twrp-3-2-3 ....
rename the file to recovery.img and put the file in adb directory.....also put the magisk.zip file in the sd card (don't put it in the internal memory)
then get into fastboot mode....then enter the following commands....
fastboot oem key [md5 hash]
fastboot flashing unlock
fastboot flash recovery recovery.img
fastboot reboot
while rebooting, instantly press vol up+power to go into recovery mode( dont let the phone to boot normally or you will have to flash twrp again and your phone might be in orange state but ignore that)....if it shows "no command" press the same buttons at the same time to get into recovery mode.....then install the magisk.zip and reboot....then install magisk.apk and you are done.... tried and tested on nokia 3 ta- 1032 android pie just today and it worked...
Click to expand...
Click to collapse
can you confirm that this method to root the phone is still working right now with the latest updates of nokia 3?
freaks211 said:
can you confirm that this method to root the phone is still working right now with the latest updates of nokia 3?
Click to expand...
Click to collapse
Don't do it !!! After rooting TA-1032 Pie 9, camera does not work !!!
Hier is what I did:
$ adb devices
$ adb reboot bootloader
$ fastboot devices
$ echo -n "NE1GXXXXXXXXXXXX" | md5sum | tr a-z A-Z | awk '{print $1}'
$ fastboot oem key YOUR-KEY
# the first time did not accepted
$ fastboot -i 0x2e04 oem key YOUR-KEY
$ fastboot oem key YOUR-KEY
$ fastboot flashing unlock
$ fastboot reboot
# Installed magisk v23.apk
$ fastboot flash boot magisk_patched-23000_7R099.img
$ fastboot reboot
I can confirm that this works on Nokia3 TA-1032, but the problem is the camera.
All you get is green background, if anyone knows hot to fix the green
background, please let me/us know.
Thank you,
I've got a BIG problem with my new Pixel 5. I've successfully rooted it and had it operating for a day.
I then decided to boot into recovery mode just to see what the new stock recovery looks like (I used to use TWRP.).
BIG MISTAKE!
All I got was the error icon that I've seen in the past meaning that no recovery image is available. OK, so I try to just try to do a simple reboot. I'm taken back to the same place.
Now I try to reload Android. No luck! I'm stuck on:
"Device product is 'unknown'"
Update requires 'bramble'.
HELP!!!!
In the file android-info.txt, what would happen if I patched the line
require board=bramble
to
require board=unknown
Did you figure this out? I'm facing the same issue with my Pixel 5.
Edit: I figured it out. If you are having an issue with the 'flash-all.bat' command like we were, you just need to manually push the individual files and it should boot you back up into stock.
Run these commands:
1. fastboot flash bootloader <bootloader image file>
2. fastboot reboot-bootloader
3. fastboot flash radio <radio image file>.img
4. fastboot reboot-bootloader
5. fastboot update <image zip file>.zip
6. fastboot reboot
All of the reboot-bootloader commands may be redundant but it worked for me. It booted me into stock, verified I was unrooted with Root Checker, then proceeded to reboot back into the bootloader and 'fastboot flashing lock' to re-lock my bootloader and wipe the device.
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.