Related
Hi
When I start up the boot loader or hit start, it just goes into recovery mode
When I turn my phone off normally and start it up, it just goes into recovery mode
I have an unlocked phone that's rather new, and I can't start it up
Thanks for the help
RingPvP said:
Hi
When I start up the boot loader or hit start, it just goes into recovery mode
When I turn my phone off normally and start it up, it just goes into recovery mode
I have an unlocked phone that's rather new, and I can't start it up
Thanks for the help
Click to expand...
Click to collapse
Running stock rom and stock kernel? Or custom rom kernel? Twrp recovery? Any other info
Sent from my Nexus 5X using Tapatalk
The_Automator said:
Running stock rom and stock kernel? Or custom rom kernel? Twrp recovery? Any other info
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I did *fastboot flash boot twrp.img. I mean't to flash it, but I was thinking twrp.img when trying to use boot.img
I couldn't undo it, and I knew I damaged my phone from this, but if there is a possible chance to fix it I am in even if I loose my data.
I was pretty sure this was the reason my Nexus 5x doesn't work, but I did nothing else other then that. Thanks for the help
RingPvP said:
I did *fastboot flash boot twrp.img. I mean't to flash it, but I was thinking twrp.img when trying to use boot.img
I couldn't undo it, and I knew I damaged my phone from this, but if there is a possible chance to fix it I am in even if I loose my data.
I was pretty sure this was the reason my Nexus 5x doesn't work, but I did nothing else other then that. Thanks for the help
Click to expand...
Click to collapse
So you can not boot to bootloader but can boot straight into twrp? But you can't flash the boot image from twrp because you cant use fastboot commands in twrp correct? maybe try this thread dedicated to unbricking phones
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Sent from my Nexus 5X using Tapatalk
The_Automator said:
So you can not boot to bootloader but can boot straight into twrp? But you can't flash the boot image from twrp because you cant use fastboot commands in twrp correct? maybe try this thread dedicated to unbricking phones
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
No no no, I can boot into the bootloader. When I turn on my phone normally, it goes into recovery mode or in twrp. When I load the bootloader and start, it also goes into twrp.
I am pretty sure I can still fastboot commands in twrp, so that's good.
Sorry that I didn't add that, but I hope you know what the problem is because I really want my phone back.
RingPvP said:
No no no, I can boot into the bootloader. When I turn on my phone normally, it goes into recovery mode or in twrp. When I load the bootloader and start, it also goes into twrp.
I am pretty sure I can still fastboot commands in twrp, so that's good.
Sorry that I didn't add that, but I hope you know what the problem is because I really want my phone back.
Click to expand...
Click to collapse
To be clear recovery mode is the same as twrp and you can not use fastboot commands within TWRP you can use adb shell commands (im less familiar with these). You can not flash stock images from twrp only aftermarket roms, kernels, zips etc. Factory images are flashed from the bootloader using fastboot.
But if you can boot into the bootloader and use fastboot (verify by typing fastboot devices)
Download chainfires modified boot image (select bullhead for the Nexus 5X)
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
extract the file so you have the .img file
Verify that your fastboot commands work fastboot devices (should always work from bootloader)
place chainfires image in the same folder as your fastboot exe.
fastboot flash boot boot.img
this should over write the boot image.
You could also just download the factory google image
https://developers.google.com/android/nexus/images?hl=en
Latest bullhead image ends with M. Extract the tar and place the extracted content in your (fastboot/adb folder) on your computer and just double click the flash-all.bat (note this will erase all data and give you a clean phone)
leave your phone until it says press any key to exit.
The_Automator said:
If you can boot into bootloader than the simplest thing to do is to download the nexus 5x image from googles factory image site. Extract that zip into your fastboot folder and double click flash all.bat. This will restore youre ur phone to factory defaults on the latest factory image. Alternatively you can just extract the boot image and use fastboot flash boot boot.img (but for this method youd have to download the factory image you already have installed which is why googlea self installer (flash-all.bat) would be easier
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I just flashed all.bat double clicking it, and it said finished. I turned on my phone already on bootloader, and it went back to twrp. I might have set my fastboot folder wrong, but the location is
C:\Program Files (x86)\Android\android-sdk\bullhead-mda89e if that helps.
Sorry if I am taking to much of your time away, but you've helped me a lot already
RingPvP said:
I just flashed all.bat double clicking it, and it said finished. I turned on my phone already on bootloader, and it went back to twrp. I might have set my fastboot folder wrong, but the location is
C:\Program Files (x86)\Android\android-sdk\bullhead-mda89e if that helps.
Sorry if I am taking to much of your time away, but you've helped me a lot already
Click to expand...
Click to collapse
usually the folder you would want to place the image into is the platform tools folder and you would want to place the files in the directory (not a sub directory) and the mda89e is the first release the newest release from google is
6.0.0 (MDB08M) Link f5233f827a44f99e26722e349f3c9445 5867cc27a23257a47688fe180ec272f1152ddde2
But within the factory image there should be a zip called something like image-bullhead-MDB08M.zip open that zip and extract just the boot.img to your platform tools folder. Then you should be able to use
fastboot flash boot boot.img
RingPvP said:
I just flashed all.bat double clicking it, and it said finished. I turned on my phone already on bootloader, and it went back to twrp. I might have set my fastboot folder wrong, but the location is
C:\Program Files (x86)\Android\android-sdk\bullhead-mda89e if that helps.
Sorry if I am taking to much of your time away, but you've helped me a lot already
Click to expand...
Click to collapse
In your case, it should be: C:\Program Files (x86)\Android\android-sdk\platform-tools\bullhead-mda89e
In this folder your should see fastboot.exe
The_Automator said:
To be clear recovery mode is the same as twrp and you can not use fastboot commands within TWRP you can use adb shell commands (im less familiar with these). You can not flash stock images from twrp only aftermarket roms, kernels, zips etc. Factory images are flashed from the bootloader using fastboot.
But if you can boot into the bootloader and use fastboot (verify by typing fastboot devices)
Download chainfires modified boot image (select bullhead for the Nexus 5X)
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
extract the file so you have the .img file
Verify that your fastboot commands work fastboot devices (should always work from bootloader)
place chainfires image in the same folder as your fastboot exe.
fastboot flash boot boot.img
this should over write the boot image.
You could also just download the factory google image
https://developers.google.com/android/nexus/images?hl=en
Latest bullhead image ends with M. Extract the tar and place the extracted content in your (fastboot/adb folder) on your computer and just double click the flash-all.bat (note this will erase all data and give you a clean phone)
leave your phone until it says press any key to exit.
Click to expand...
Click to collapse
I don't know what to say, but thank you so much! I literally had a heart attack when it happened. You deserve more than a thanks for this .
RingPvP said:
I don't know what to say, but thank you so much! I literally had a heart attack when it happened. You deserve more than a thanks for this .
Click to expand...
Click to collapse
Happy to help glad you got your phone sorted
Sent from my Nexus 5X using Tapatalk
Hello,
I've unlocked the bootloader and installed twrp..
First thing that was strange was that after I've put the .zip file to the internal memory, and booted back to twrp, the files were not there.. after that I've rebooted the phone, it asked me for a password (I've had no password after I've unlocked the bootloader)...
I've puted the Linage OS and Gapps on the external sd card..
Went to recovery again tried to flash the linage OS, got some error, like step 1 step 2.. and then error, tried to reboot into system.. now it only boots into fastboot.. I can get it to the EDL.. However cant flash twrp.. I get the error - mdp image is corrupted..
So I'm stuck! Don't know what to do anymore..
Any help is much appreciated.
Bucika said:
Hello,
I've unlocked the bootloader and installed twrp..
First thing that was strange was that after I've put the .zip file to the internal memory, and booted back to twrp, the files were not there.. after that I've rebooted the phone, it asked me for a password (I've had no password after I've unlocked the bootloader)...
I've puted the Linage OS and Gapps on the external sd card..
Went to recovery again tried to flash the linage OS, got some error, like step 1 step 2.. and then error, tried to reboot into system.. now it only boots into fastboot.. I can get it to the EDL.. However cant flash twrp.. I get the error - mdp image is corrupted..
So I'm stuck! Don't know what to do anymore..
Any help is much appreciated.
Click to expand...
Click to collapse
For me the problem was that I didn´t formatted DATA!
did you?
anykill said:
For me the problem was that I didn´t formatted DATA!
did you?
Click to expand...
Click to collapse
Damn, no I didn't! But I can't boot into twrp anymore.. just fastboot..
fastboot.exe boot .\twrp-daisy-3.3.0-0-offain.img
adb.exe push .\lineage-16.0-20190601-UNOFFICIAL-daisy.zip sdcard
adb.exe push .\ForcedEncryptionDisablerDaisy.zip sdcard <------ you need to flash this too
adb.exe push .\open_gapps-arm64-9.0-micro-20190601.zip sdcard
in twrp flash lineage (not gapps) than, reboot to fastboot
fastboot.exe boot twrp...
flash gapps
done
or go here!
https://github.com/tkchn/daisyinstall/blob/master/README.md
anykill said:
fastboot.exe boot twrp...
adb.exe push lineage.... /sdcard
adb.exe push gapps.... /sdcard
in twrp flash lineage (not gapps) than, reboot to fastboot
fastboot.exe boot twrp...
flash gapps
done
Click to expand...
Click to collapse
Yeah, it was that easy..
If I try to boot twrp I get the error, that mdpt image is corrupted and it doesn't boot..
Bucika said:
Yeah, it was that easy..
If I try to boot twrp I get the error, that mdpt image is corrupted and it doesn't boot..
Click to expand...
Click to collapse
Oh... maybe you need to do the EDL...
I had to do this one time when I flashed wrong image...
anykill said:
Oh... maybe you need to do the EDL...
I had to do this one time when I flashed wrong image...
Click to expand...
Click to collapse
< waiting for device > is all I get when I boot into EDL..
Bucika said:
< waiting for device > is all I get when I boot into EDL..
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=HTRLumtgqOM
However I do believe that the phone is not totally bricked, as I can boot into EDL and into Fastboot, but there is no system, no recovery.. And when I try to flash anything all I get is mdpt image is corrupted.. And If I try to flash anything from EDL it just says < waiting for device >
No..
I can get into the EDL by typing fastboot oem edl.. and computer recognize the device as Qualcom HS-USB QDloader 9008... I just can't find a way to flash anything..
Bucika said:
Yeah, it was that easy..
If I try to boot twrp I get the error, that mdpt image is corrupted and it doesn't boot..
Click to expand...
Click to collapse
try this
New TWRP 3.3.1-0 update:
Bootable: https://androidfilehost.com/?fid=6006931924117887098
Flashable: https://androidfilehost.com/?fid=6006931924117887097
Same thing.. Corrupted mdtp..
Bucika said:
Same thing.. Corrupted mdtp..
Click to expand...
Click to collapse
you tried the Miflash?
https://www.xiaomiflash.com/
and the stock firmware
https://bigota.d.miui.com/V10.0.8.0.PDLMIXM/miui_DAISYGlobal_V10.0.8.0.PDLMIXM_29324cbe1b_9.0.zip
Bucika said:
Same thing.. Corrupted mdtp..
Click to expand...
Click to collapse
Try to flash version 9.6.4.0. using the QFIL utility (QPST). maybe she will help
Bucika said:
Hello,
I've unlocked the bootloader and installed twrp..
First thing that was strange was that after I've put the .zip file to the internal memory, and booted back to twrp, the files were not there.. after that I've rebooted the phone, it asked me for a password (I've had no password after I've unlocked the bootloader)...
I've puted the Linage OS and Gapps on the external sd card..
Went to recovery again tried to flash the linage OS, got some error, like step 1 step 2.. and then error, tried to reboot into system.. now it only boots into fastboot.. I can get it to the EDL.. However cant flash twrp.. I get the error - mdp image is corrupted..
So I'm stuck! Don't know what to do anymore..
Any help is much appreciated.
Click to expand...
Click to collapse
Bro just stay in fastboot and flash the official stock firmware. Extract it on your computer and run FLASH ALL.
https://en.miui.com/getrom-354.html?m=yes&mobile=2
Btw- make sure you have charge over 50%
I don't recommend to use mi flash tool in that situation.
Download the fastboot rom and adb to the same folder and run the flash_all.bat.
What it will do it delete the partitions and remake them what mi flash tool don't do, after that your phone will be back to stock.
I played with this phone a lot and I even got the system is now destroyed message and also deleted my imei, if I did recovered from that so I know what I'm saying?
MAKE SURE TO NOT RUN THE FLASH_ALL_LOCK.BAT IF YOU DO WITHOUT TESTING IF YOUR SYSTEM BOOT FINE YOU COULD BRICK YOUR PHONE FOREVER!!!
OP did any of these methods work?
I had the exactly same problem when I first got to flashing on my A2 Lite. Download the newest Fastboot image, extract it with 7zip and run the flash_all.bat, <b>NOT THE FLASH_ALL_LOCK.BAT<b/>. This will recover everything. After that you can proceed normal installing. Also use unofficial TWRP by offain instead of the official one.
The exact installing instructions can be found here: https://github.com/tkchn/daisyinstall
Use only this installation guide, except for the disable encryption part: don't flash the disableencyption.zip directly after TWRP on Slot A, but instead install it after the GApps and leave out Magisk. This will automatically install Magisk 16.7 on your phone, but you can upgrade that after a successful boot. If you will try to flash the def.zip on the Slot A, it will give an error and your phone will encrypt the data on the first boot.
Noam5651 said:
I don't recommend to use mi flash tool in that situation.
Download the fastboot rom and adb to the same folder and run the flash_all.bat.
What it will do it delete the partitions and remake them what mi flash tool don't do, after that your phone will be back to stock.
I played with this phone a lot and I even got the system is now destroyed message and also deleted my imei, if I did recovered from that so I know what I'm saying
MAKE SURE TO NOT RUN THE FLASH_ALL_LOCK.BAT IF YOU DO WITHOUT TESTING IF YOUR SYSTEM BOOT FINE YOU COULD BRICK YOUR PHONE FOREVER!!!
Click to expand...
Click to collapse
thanks a lot , it work for my Mi a2 Lite which previously had an error message "device unable to boot Error - mdtp image is corrupted"
now normal again
i found the souliton man do you still need help? i had exact same problem
Hello everyone,
I have managed to forget my pattern. :crying: I'm on a Pixel 1 and on Android 10 Beta 4. The problem is I have my bitcoin wallet on that device, which is the reason why I cannot factory reset it.
The problem is I cannot reach the device via Google Find, even though it's connected to my WiFi. I also tried putting in a simcard - this didn't help either. Next problem is, I cannot access it via ADB, only via fastboot in bootloader mode.
Any ideas what else I could try? I'm starting to give up...
Best regards
snOwjAwk said:
Hello everyone,
I have managed to forget my pattern. :crying: I'm on a Pixel 1 and on Android 10 Beta 4. The problem is I have my bitcoin wallet on that device, which is the reason why I cannot factory reset it.
The problem is I cannot reach the device via Google Find, even though it's connected to my WiFi. I also tried putting in a simcard - this didn't help either. Next problem is, I cannot access it via ADB, only via fastboot in bootloader mode.
Any ideas what else I could try? I'm starting to give up...
Best regards
Click to expand...
Click to collapse
if you have twrp installed without encryption then its possible to remove that
look here something like this
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
zfk110 said:
if you have twrp installed without encryption then its possible to remove that
look here something like this
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
Click to expand...
Click to collapse
I tried to install twrp but ran into this error (on mac):
booting...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (Undefined error: 0))
EDIT:
Tried it from a windows pc now, got another error:
creating boot image...
creating boot image - 11765760 bytes
Sending 'boot.img' (11490 KB) OKAY [ 0.495s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
You don't install TWRP. you boot into it via fastboot and from there you can then choose to flash a zip file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
Phalanx7621 said:
You don't install TWRP. you boot into it via fastboot and from there you can then choose to flash a zip file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
Click to expand...
Click to collapse
Thats what I did actually. I typed in Fastboot Boot twrp.img and that was the outcome
snOwjAwk said:
Thats what I did actually. I typed in Fastboot Boot twrp.img and that was the outcome
Click to expand...
Click to collapse
You have to have TWRP installed before hand, if not then you wont able to do it. since OEM unlock needs to be on
read here more
https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
also Im going to PM get it touch with that guy and see if he can help you out
zfk110 said:
You have to have TWRP installed before hand, if not then you wont able to do it. since OEM unlock needs to be on
read here more
https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
also Im going to PM get it touch with that guy and see if he can help you out
Click to expand...
Click to collapse
Bootloader is unlocked! That's why im curious why it doesnt work...
snOwjAwk said:
Bootloader is unlocked! That's why im curious why it doesnt work...
Click to expand...
Click to collapse
if its unlocked then you should able to install twrp without any issues,
follow him
You don't install TWRP. you boot into it via fastboot first and from there you can then choose to flash a img file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
copy that TWRP.img in the same adb folder, also its saying too many links that mean you have more than one USB devices connected, just take all of them off and only have your phone connected to it
zfk110 said:
if its unlocked then you should able to install twrp without any issues,
follow him
You don't install TWRP. you boot into it via fastboot first and from there you can then choose to flash a img file which will permanently flash TWRP until a custom ROM is flashed then you have to reflash it. The command to boot into TWRP is fastboot boot *name of TWRP file*.img
It will then boot into TWRP . For convenience sake, I always rename my TWRP file TWRP.img
copy that TWRP.img in the same adb folder, also its saying too many links that mean you have more than one USB devices connected, just take all of them off and only have your phone connected to it
Click to expand...
Click to collapse
That's what I did... And there was no other USB device connected other than the pixel. Fastboot devices also only showed my device
Is there a way i can recover my data ? I need to recover my kid's graduation pictures. I will pay for help if I need too.
I was rooted and using 11.2.4.4.LE15AA. I uninstalled Magisk then i tried updating to 11.2.5.5 via ota , it kept saying install failed i need to reboot and now I'm stuck in fastboot.
edit: and now it doesn't turn off.
Im a flipping idiot.
Thanks in advance.
https://mega.nz/file/7YQj3SIR#5yDfje2mVgPVRdZi-gYrDRvvQE2hx_DYD00vicZH8Fo
This is a zip from one of the top 3 pinned threads on this OP9P forum that has stock and patched boot.img from your 4.4AA build..(if thats what ur phone is still on). U may be able to download the zip, put on ur pc, extract it, then open cmd and fastboot boot (then drag the stock boot.img to the command prompt u typed in) and hit enter.. It may work to get u back booted unrooted...
Shooter7889 said:
https://mega.nz/file/7YQj3SIR#5yDfje2mVgPVRdZi-gYrDRvvQE2hx_DYD00vicZH8Fo
This is a zip from one of the top 3 pinned threads on this OP9P forum that has stock and patched boot.img from your 4.4AA build..(if thats what ur phone is still on). U may be able to download the zip, put on ur pc, extract it, then open cmd and fastboot boot (then drag the stock boot.img to the command prompt u typed in) and hit enter.. It may work to get u back booted unrooted...
Click to expand...
Click to collapse
Crap that didn't work. I'm so beyond screwed. I wonder IF and when TWRP comes out if I will be able to decrypt then.
Try flashing 4.4 or 5.5 full OTA via fastboot/fastbootd. If you are gonna try the 5.5 then you gotta use EU/India.
TWRP at this point is a pipe dream. Decrypt doesn't even work for A10 on OP and Android is moving faster than TWRP can keep up.
craznazn said:
Try flashing 4.4 or 5.5 full OTA via fastboot/fastbootd. If you are gonna try the 5.5 then you gotta use EU/India.
TWRP at this point is a pipe dream. Decrypt doesn't even work for A10 on OP and Android is moving faster than TWRP can keep up.
Click to expand...
Click to collapse
Is that where i flash all the individual .imgs with fastboot? or just system.img
Individual
In case this comes from magisk modules, just try to reboot in safe mode:
Safe Mode
1. Hold power until it goes off
2. Boot and wait for the bootloader warning
3. Hold vol up and down until boot animation
4. Once it's booted just reboot again and you're done
Now on boot all magisk modules are disabled
Other option, have you try to flash your original boot!
craznazn said:
Individual
Click to expand...
Click to collapse
I get this for several of the img files.
FAILED (remote: Flashing is not allowed for Critical Partitions
But I'm able to get to recovery now, with this error
boot reason fs_mgr_mount_all
Fastbootd for critical partitions (not fastboot)
I wiped it.
close the thread.
Oh too bad i had your solution, as ihad the same problem last week.
For anyone else in this situation you have to flash the stock boot img to opposite partition. Then boot to that partition. Get your data off at that point before you do anything else. Then try to re-root
On an older phone I used TWRP recovery. That has a brilliant option to create system backups.
How to do that in the LineageOs recovery?
I want to clone one phone to another identical phone. I hope that can be done by creating a backup on phone 1 and install it from recovery on the other. Hopefully including the OS (with all the setting that take hours of fiddling about), apps and data.
Just use twrp..?
PhotonIce said:
Just use twrp..?
Click to expand...
Click to collapse
But fom what I understand the TWRP-backup is only the system, not the apps and data.
In the install instructions for lineageOs, the lineageOs recovery is used. So I followed the instructions exactly. Just surprised there is no backup option.
carsten888 said:
But fom what I understand the TWRP-backup is only the system, not the apps and data.
In the install instructions for lineageOs, the lineageOs recovery is used. So I followed the instructions exactly. Just surprised there is no backup option.
Click to expand...
Click to collapse
Obliviously no, twrp backup include everything. I use twrp and when I have to install new lineage os update I boot lineage recovery from fastboot and keep internal recovery as twrp
carsten888 said:
But fom what I understand the TWRP-backup is only the system, not the apps and data.
In the install instructions for lineageOs, the lineageOs recovery is used. So I followed the instructions exactly. Just surprised there is no backup option.
Click to expand...
Click to collapse
Use twrp backup and select all the partitions. It'll back up everything.
Apps and settings are located in the data partition and other files/data is located in the internal storage partition. boot is the kernel, recovery is the recovery and system in the system image.
If you know what you're doing you could even install a fresh copy of lineage onto another phone and just restore the data and internal storage partitions, and still receive an exact copy of the phone you backup up from while using less space in the backup.
... An additional question. I apologize if my n00b question should be something I already know. However, I briefly had twrp on my device and then I flashed lineageOS and magisk on slot b and of course it switched to boot from slot b. Since then, I have not been able to access twrp as it is located on slot a. When I boot into recovery, it brings me automatically to lineageOS recovery. How would I access twrp once again?
Paul_Neocube said:
... An additional question. I apologize if my n00b question should be something I already know. However, I briefly had twrp on my device and then I flashed lineageOS and magisk on slot b and of course it switched to boot from slot b. Since then, I have not been able to access twrp as it is located on slot a. When I boot into recovery, it brings me automatically to lineageOS recovery. How would I access twrp once again?
Click to expand...
Click to collapse
Not sure what you mean by slot A and B, but just try flashing twrp again, it should override lineage recovery.
PhotonIce said:
Not sure what you mean by slot A and B, but just try flashing twrp again, it should override lineage recovery.
Click to expand...
Click to collapse
On my device there are two slots... A and B. Like two separate partitions that van have software installed to. When I installed my rom I first installed twrp to slot a and then my Tom to slot b which is what runs now when I power on my device. I can't install twrp to the slot my os is on as I would have issues with the os recovery that is on that slot.
Skorpion96 said:
Obliviously no, twrp backup include everything. I use twrp and when I have to install new lineage os update I boot lineage recovery from fastboot and keep internal recovery as twrp
Click to expand...
Click to collapse
Could you please explain (or link to instructions) how did you manage to have two different recoveries (TWRP and LOS) in the same phone? I would've thought that was not possible.
zogoibi said:
Could you please explain (or link to instructions) how did you manage to have two different recoveries (TWRP and LOS) in the same phone? I would've thought that was not possible.
Click to expand...
Click to collapse
It's not. He keeps LineageOS recovery on the phone, and when he wants to use TWRP, he connects the phone to his computer via USB and runs fastboot boot twrp.img from the command line. This reboots the phone and loads TWRP into memory without flashing it to the phone.
@MJPollard Wow!! That's a very intersting trick! thanks a lot. I'll take that down as it seems darn useful. Just one question: the "alternative" recovery .img file should be in my computer, or previously copied to the phone?
zogoibi said:
@MJPollard Wow!! That's a very intersting trick! thanks a lot. I'll take that down as it seems darn useful. Just one question: the "alternative" recovery .img file should be in my computer, or previously copied to the phone?
Click to expand...
Click to collapse
actually i done the reverse, i have twrp installed and when i want to run lineage recovery i boot it with fastboot boot "recovery.img"
Thanks. Yes, I've realized that. Still, my question remains unanswered: In order to boot via fastboot, should the alternative recovery's .img file reside in the computer or in the phone? I presume the former, but I'm not sure.
zogoibi said:
Thanks. Yes, I've realized that. Still, my question remains unanswered: In order to boot via fastboot, should the alternative recovery's .img file reside in the computer or in the phone? I presume the former, but I'm not sure.
Click to expand...
Click to collapse
You ever flashed TWRP via cmd (adb) on a pc? It's the same thing but you use fastboot flash rather than fastboot boot. When you flash twrp on phone, you put the recovery.img file in your adb folder, if I'm not mistaken. The same thing goes for booting an .img file (it goes in the adb directory/folder in your pc).
zogoibi said:
Thanks. Yes, I've realized that. Still, my question remains unanswered: In order to boot via fastboot, should the alternative recovery's .img file reside in the computer or in the phone? I presume the former, but I'm not sure.
Click to expand...
Click to collapse
The alternate recovery should remain on the computer. It can be in the same folder as adb and fastboot for easy access (it doesn't need to be there, it's just easier that way). That way, all you need to do is reboot the device into fastboot mode, connect it to the computer via USB, and run fastboot boot twrp.img (or whatever it's named). The original recovery will remain untouched on the phone while the alternate recovery runs in memory.
MJPollard said:
That way, all you need to do is reboot the device into fastboot mode, connect it to the computer via USB, and run fastboot boot twrp.img (or whatever it's named). The original recovery will remain untouched on the phone while the alternate recovery runs in memory.
Click to expand...
Click to collapse
Thank you. I know this question is a bit off topic, but when I try to run that command (with the phone in fastboot mode), it fails:
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.611s]
booting...
FAILED (remote: Unrecognized command boot)
Do you have an idea of why is that? My device's recovery is LOS's, and the recovery I try to run from the computer is TWRP.
zogoibi said:
Thank you. I know this question is a bit off topic, but when I try to run that command (with the phone in fastboot mode), it fails:
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.611s]
booting...
FAILED (remote: Unrecognized command boot)
Do you have an idea of why is that? My device's recovery is LOS's, and the recovery I try to run from the computer is TWRP.
Click to expand...
Click to collapse
Try fastboot boot recovery twrp.img. I don't normally do this so I might have misremembered it. If it works, I'll edit my post so that others don't get confused.
Nope, it didn't work. The first command you told me is the correct one (I've checked that on the fastboot manual), but it fails on my device. Maybe there is some incompatibility between LOS recovery's fastboot mode and the TWRP I am trying to run. I won't insist, as this is not the thread for such an issue. I will try to find some information somewhere else. Thank you all the same for trying to help!
zogoibi said:
Nope, it didn't work. The first command you told me is the correct one (I've checked that on the fastboot manual), but it fails on my device. Maybe there is some incompatibility between LOS recovery's fastboot mode and the TWRP I am trying to run. I won't insist, as this is not the thread for such an issue. I will try to find some information somewhere else. Thank you all the same for trying to help!
Click to expand...
Click to collapse
have you found a solution for this? I m also having same trouble lineage os 20. I wanna use TWRP to make backup of whole rom.
agamemnonn said:
have you found a solution for this? I m also having same trouble lineage os 20. I wanna use TWRP to make backup of whole rom.
Click to expand...
Click to collapse
I found out that it's not possible. LOS Recovery's fastboot mode has that command disabled.