My rooted Axon 7 (A2017U) does not show the boot partition in TWRP when backing up or restoring a backup that previously showed the boot partition. Here is what I did prior to the problem:
1. Manually updated stock rom to B32 using DrakenFX procedures, which includes flashing bootstack. (I made a backup after the upgrade of boot, data, and system - as usual.)
2. When I restored AICP nandroid, boot was shown along with data and system. Phone operated normally, but would not flash OTA upgrade - error 7. (Attempted to flash a previous version that I had flashed before with the same error 7.)
3. Rather than unzipping the rom and deleting the asserts line, I flashed the universal boot image from LineageOS and was able to OTA without issue, but when I ran the TWRP backup, boot did not show and only system and data backed up.
4. Restored the stock nandroid, boot did not show.
My phone is operating normally, but I find it disconcerting to have made an unintended change and would appreciate any help in correcting my error.
Thanks in advance.
Hi have you fixed your problem or not?
William Guo said:
Hi have you fixed your problem or not?
Click to expand...
Click to collapse
No, still waiting for assistance.
Reflash TWRP. I had partitions missing and there was a weird version of TWRP installed for unknown reasons. Reflashing the latest TWRP fixed my problem.
JKSurf said:
Reflash TWRP. I had partitions missing and there was a weird version of TWRP installed for unknown reasons. Reflashing the latest TWRP fixed my problem.
Click to expand...
Click to collapse
That worked. Thank you very much. Weird how that happened.
Just as a matter of interest, I just did a clean install of AICP, which required installation of universal bootstack, and found that TWRP version had been replaced with an old version that did not show boot partition when doing nandroid. Reflashed current build image and boot file was visible.
Keep the latest .img on TWRP, and when you flash the universal bootstack, flash the TWRP .img after. I've asked over at the LOS thread if they could update the TWRP version on the bootstack and nobody answered lol
Should we use the one from twrps official website? I'm having the same issue but I can't remember changing my recovery.
jojofreddy said:
Should we use the one from twrps official website? I'm having the same issue but I can't remember changing my recovery.
Click to expand...
Click to collapse
You don't change your recovery, the universal bootstack zip does
It's the same whether you use the zip from TWRP's official website or raystef66's download center really
Related
Hi, I have a essential phone running Oreo 8.1, just recently I have rooted the phone with magisk v16 an twrp 3.2.1, I successfully flashed it with twrp but after the flash whenever I want to get into twrp it just freezes up on the mount data screen and I have to force reboot it, does anyone know a solution to this problem
Make sure you're following the exact steps from this post. Every step is crucial (except #3, because you have to disable your screen lock before booting twrp.
You shouldn't have to manually mount anything in TWRP either. The magisk installer might give you an error about mounting system but it doesn't seem to make any difference.
[QRCODE][/QRCODE]
yellk20 said:
Hi, I have a essential phone running Oreo 8.1, just recently I have rooted the phone with magisk v16 an twrp 3.2.1, I successfully flashed it with twrp but after the flash whenever I want to get into twrp it just freezes up on the mount data screen and I have to force reboot it, does anyone know a solution to this problem
Click to expand...
Click to collapse
You cannot have TWRP installed with 8.x.
TWRP is not compatible.
You must flash the original boot image, then install magisk.
TWRP cannot remain.
You will boot loop.
Please read the instructions on rooting carefully.
Ok thank you
Why can't TWRP replace recovery instead of boot?
RawSlugs said:
Why can't TWRP replace recovery instead of boot?
Click to expand...
Click to collapse
No one has created a bit image with TWRP as the recovery.
Sent from my PH-1 using XDA Labs
RawSlugs said:
Why can't TWRP replace recovery instead of boot?
Click to expand...
Click to collapse
Because the partition layout of the Essential does not have a recovery partition.
Recovery is contained in the boot image.
So to have TWRP resident/permanent, the boot image must be patched.
It has been done for 7.x, but sense 8.x is still beta, there is no official TWRP for Oreo.
Once Oreo is final, I expect we will get a TWRP that works.
The current limitation, means you can't flash without a computer handy.
I am currently using a OnePlus 5 which used to run on a stock based rom, xxxNoLimits v3.1
Since the dev ended the support I wanted to revert back to pure OOS, so I downlaoded the newest 5.1.5 zip and followed the instructions using the newest blu_spark twrp recovery but right after pressing the "flash" button I kept getting error 7, so I download the zip from a mirror link and I have also tried the newest version of codeworkx twrp, still error 7. Then I tried flashing the original stock recovery in order to flash the zip but it instantly threw me back to the zip selection menu, flashing the zip via adb sideload kept quitting at exactly 47%. At this point I was pretty frustrated, I flashed twrp codeworkx again and wiped EVERYTHING, which includes the system, data, cache, dalvik partitions and then I also did a format on the data partition, the point was that now I would have a clean phone only running twrp and I thought I could easily flash the newest zip now without any problems, NOPE, still error 7!!! Now I am stuck here, the stock recovery doesnt let me flash anything and I've tried 4 different versions of twrp recoverys and every single one gives me the same error, I even dug up an older version of OOS, I think it which I had running for a few weeks without any probles so I knew that the zip was not corrupted but same error
Now I had given up and wanted to restore the backup I did just in case anything goes wrong, well, restoring the backup fails when it tries to restore the data partition, so I unchecked everything except system, system image and recovery but it didnt work, now I am sitting here with my phone telling me that there's no OS installed. any advice?
Use Unbrick Tool and Restore
Hey,
You can Flash your Mobile using the Unbrick tool at - https://androidfilehost.com/?w=files&flid=204903
Use the Latest file which I guess comes with OOS 5.1.3 - https://androidfilehost.com/?fid=962339331458999196
If you try to Go to Open Beta ROM First Flash Open Beta 12--> Open Beta 13 --> Open Beta 17
freaky2xd said:
I am currently using a OnePlus 5 which used to run on a stock based rom, xxxNoLimits v3.1
Since the dev ended the support I wanted to revert back to pure OOS, so I downlaoded the newest 5.1.5 zip and followed the instructions using the newest blu_spark twrp recovery but right after pressing the "flash" button I kept getting error 7, so I download the zip from a mirror link and I have also tried the newest version of codeworkx twrp, still error 7. Then I tried flashing the original stock recovery in order to flash the zip but it instantly threw me back to the zip selection menu, flashing the zip via adb sideload kept quitting at exactly 47%. At this point I was pretty frustrated, I flashed twrp codeworkx again and wiped EVERYTHING, which includes the system, data, cache, dalvik partitions and then I also did a format on the data partition, the point was that now I would have a clean phone only running twrp and I thought I could easily flash the newest zip now without any problems, NOPE, still error 7!!! Now I am stuck here, the stock recovery doesnt let me flash anything and I've tried 4 different versions of twrp recoverys and every single one gives me the same error, I even dug up an older version of OOS, I think it which I had running for a few weeks without any probles so I knew that the zip was not corrupted but same error
Now I had given up and wanted to restore the backup I did just in case anything goes wrong, well, restoring the backup fails when it tries to restore the data partition, so I unchecked everything except system, system image and recovery but it didnt work, now I am sitting here with my phone telling me that there's no OS installed. any advice?
Click to expand...
Click to collapse
Flashing newest oos doesn't always work l have had this sometime l have had to go back 3 oos versions then flash them in order to flash the latest release.
freaky2xd said:
I am currently using a OnePlus 5 which used to run on a stock based rom, xxxNoLimits v3.1
Since the dev ended the support I wanted to revert back to pure OOS, so I downlaoded the newest 5.1.5 zip and followed the instructions using the newest blu_spark twrp recovery but right after pressing the "flash" button I kept getting error 7, so I download the zip from a mirror link and I have also tried the newest version of codeworkx twrp, still error 7. Then I tried flashing the original stock recovery in order to flash the zip but it instantly threw me back to the zip selection menu, flashing the zip via adb sideload kept quitting at exactly 47%. At this point I was pretty frustrated, I flashed twrp codeworkx again and wiped EVERYTHING, which includes the system, data, cache, dalvik partitions and then I also did a format on the data partition, the point was that now I would have a clean phone only running twrp and I thought I could easily flash the newest zip now without any problems, NOPE, still error 7!!! Now I am stuck here, the stock recovery doesnt let me flash anything and I've tried 4 different versions of twrp recoverys and every single one gives me the same error, I even dug up an older version of OOS, I think it which I had running for a few weeks without any probles so I knew that the zip was not corrupted but same error
Now I had given up and wanted to restore the backup I did just in case anything goes wrong, well, restoring the backup fails when it tries to restore the data partition, so I unchecked everything except system, system image and recovery but it didnt work, now I am sitting here with my phone telling me that there's no OS installed. any advice?
Click to expand...
Click to collapse
Hi ! Do you have some news about it ? I have the same issue since Monday...
I've tried like anything i've found and even more, but nothing did the job ...
The only way to have my OP5 working is downgrade to an old version running Android 7.1.1
hey guys, so i used twrp to flash a OTA then flashed twrp again and rebooted and when i went to flash magisk i was just shown a list of all random numbers/letters. i booted into bootloader flashed twrp img, booted into recovery and all my files were there once again but i still cant get into the OS, can anyone please help?
why is flashing so complicated these days? even the recovery works different. the last time i rooted (4 years ago maybe) you could use twrp to make a backup and it was done simple as that (i did this on the oneplus 6t about 4 weeks ago and got the issue with my storage just being a list of numbers and letters and had to find a way to fully wipe and re install OOS) and the same for flashing, i could just flash something and it was fine, no issues.
Do you have an OTG adapter and pendrive? You can copy the full OTA zip, TWRP zip and Magisk zip on to that and flash from TWRP using that. Your internal storage is encrypted and you won't be able to access it until you can reboot OOS fully. If that didn't work, you may have to do a factory reset/wipe (including internal data) to get the phone to boot again. You will obviously lose any unbacked data.
Which version of TWRP are you using? Which version of OOS are you using? Most likely you just don't have the correct version, and you updated to the latest version OOS with the new security patch and it no longer can decrypt it.
Have you tried TWRP 3.3.1-7 from here? If you boot the .img file from fastboot, can you decrypt your data?
Most likely you just need to flash Magisk, and you will be fine. For updates, it's always as you did, flash the full OTA update, TWRP installer, reboot to recovery, Magisk. It is recommended to uninstall Magisk, however I usually don't do that personally. Official Instructions here. You just have to make sure you are using the correct version of TWRP, otherwise you can run into encryption issues, as you found out when there are updates.
OhioYJ said:
Which version of TWRP are you using? Which version of OOS are you using? Most likely you just don't have the correct version, and you updated to the latest version OOS with the new security patch and it no longer can decrypt it.
Have you tried TWRP 3.3.1-7 from here? If you boot the .img file from fastboot, can you decrypt your data?
Most likely you just need to flash Magisk, and you will be fine. For updates, it's always as you did, flash the full OTA update, TWRP installer, reboot to recovery, Magisk. It is recommended to uninstall Magisk, however I usually don't do that personally. Official Instructions here. You just have to make sure you are using the correct version of TWRP, otherwise you can run into encryption issues, as you found out when there are updates.
Click to expand...
Click to collapse
Latest twrp and latest full OOS OTA. If I fastboot the twrp. Img I can see all my data again. I've fixed it now, I flashed the twrp. Img in fastboot then rebooted system and it worked
Hi Guys,
yesterday the new update came out, great.
I of course immediately pulled the zip (source) and installed it with TWRP (source).
So far no problems.
After a while I realized that I no longer had root because the apps stopped working.
When I wanted to boot into the TWRP to reinstall Magisk, I unfortunately found that it was no longer available, but only stock recovery.
Well, I thought to myself and tried to reinstall TWRP (method-twrp-3.3.1-2-davinci-fix), which was fatal, because my cell phone only booted into the Fastboot.
Then I got my cell phone, set up again with the Fastboot method.
Now I'm back to 11.0.4.0 but unfortunately without TWRP and root.
Can someone please describe how I can get TWRP and root again on Android 10?
I am thankful for every help !!!
Same thing happening to me, no matter what I do, stock recovery keeps overwriting TWRP
Oh dear, that doesn't sound good.
I hope there will be a solution to the problem soon.
I don't want to do without TWRP and root.
I wanted to try it according to these instructions "https://miui.blog/redmi-k20/twrp-mi-9t-redmi-k20-vbmeta-mauronofrio/". But don't trust me, I'm afraid that it won't work and I can start all over again.
Flash official TWRP this morning with fastboot commands without problem.
1. reboot in fastboot mode
2. Flash recovery with this command "fastboot flash recovery yourrecovery.img"
3. Reboot in recovery with this command "fastboot boot yourrecovery.img"
Any problems here.
The fact that twrp is lost when flashing official rom (even thought twrp itself) is normal. You just have to reboot into bootloader and flash twrp again and it will be back.
Your problem here is that you are using an old and unofficial twrp build, that has problems on newer roms. Flash official twrp and you'll be fine
houbaba said:
Flash official TWRP this morning with fastboot commands without problem.
1. reboot in fastboot mode
2. Flash recovery with this command "fastboot flash recovery yourrecovery.img"
3. Reboot in recovery with this command "fastboot boot yourrecovery.img"
Any problems here.
Click to expand...
Click to collapse
Can u share the twrp file, im unnable to flash the one i have without causing a bootloop
hounter17 said:
Can u share the twrp file, im unnable to flash the one i have without causing a bootloop
Click to expand...
Click to collapse
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html
RedNas74 said:
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html
Click to expand...
Click to collapse
Oh sorry it works? I read somewhere that the original causes also bootloops :good:
Found something on a Russian website.
Обновление TWRP Recovery от LR.Team для устройств на Android 10
Does anyone dare to test this?
Here is the link to the TWRP for our Mi9t
> TWRP-3.3.1-1109-DX (полный комплект для установки) <
Check it out...
I finally got it
I did the following.
"V11.0.4.0.QFJEUXM" flashed in the TWRP and booted into the system, TWRP will be overwritten.
Now flashed TWRP "twrp-3.3.1-0-davinci.img" in Fastboot and booted into Recovery (TWRP).
To be on the safe side, I had the cell phone booted again into the TWRP in the TWRP.
Then I flashed Magisk "Magisk-v20.3.zip".
Booted cell phone into the system and everything works.
frank808 said:
I finally got it
I did the following.
"V11.0.4.0.QFJEUXM" flashed in the TWRP and booted into the system, TWRP will be overwritten.
Now flashed TWRP "twrp-3.3.1-0-davinci.img" in Fastboot and booted into Recovery (TWRP).
To be on the safe side, I had the cell phone booted again into the TWRP in the TWRP.
Then I flashed Magisk "Magisk-v20.3.zip".
Booted cell phone into the system and everything works.
Click to expand...
Click to collapse
Where did you get the twrp file from?
You can use OrangeFox Recovery if you want a TWRP that can survive after flashing MIUI ROMs or updates :
https://forum.xda-developers.com/mi-9t/development/official-orangefox-recovery-project-t4037899
RedNas74 said:
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html
Click to expand...
Click to collapse
Ok, I am on global 11.0.4.0 (QFJMIXM) and I used this latest twrp-3.3.1-0-davinci.img and I can confirm its working without bootloop.
ShiningScias said:
You can use OrangeFox Recovery if you want a TWRP that can survive after flashing MIUI ROMs or updates :
https://forum.xda-developers.com/mi-9t/development/official-orangefox-recovery-project-t4037899
Click to expand...
Click to collapse
To install TWRP, is it neccesary to wipe Data (or something else)?
And if Data must be wiped, does it mean that Data will no more be encrypted as originally by MIUI?
I have 11.0.4.0, rooted by Magisk (Magisk installed simply by patching and flashing boot.img, did not need TWRP for, did not wipe Data, etc) and I possibly want to have TWRP but don't want to loose encryption of Data, Widewine L1 and so
zgfg said:
To install TWRP, is it neccesary to wipe Data (or something else)?
And if Data must be wiped, does it mean that Data will no more be encrypted as originally by MIUI?
I have 11.0.4.0, rooted by Magisk (Magisk installed simply by patching and flashing boot.img, did not need TWRP for, did not wipe Data, etc) and I possibly want to have TWRP but don't want to loose encryption of Data, Widewine L1 and so
Click to expand...
Click to collapse
You don't need to wipe anything to install a custom Recovery (like TWRP).
TWRP can handle ROM encryption, you just need to install a correct TWRP, and version, for your current MIUI / Android version.
A custom Recovery doesn't change Widevine level.
And TWRP is useful in case of bootloop (because of an installed Magisk module, by example) or if you want to easily reinstall Magisk after ROM update.
RedNas74 said:
Download from the official twrp site here: https://twrp.me/xiaomi/xiaomimi9t.html
Click to expand...
Click to collapse
Micdu70 said:
You don't need to wipe anything to install a custom Recovery (like TWRP).
TWRP can handle ROM encryption, you just need to install a correct TWRP, and version, for your current MIUI / Android version.
Click to expand...
Click to collapse
Ok thanks, so starting from v11.0.4.0 QFJEUXM, rooted by Magisk (did not wipe Data or so, just patched and flashed boot img), is it ok just to flash (from Fastboot) twrp-3.3.1-0-davinci.img, downloaded from the official site https://twrp.me/davinci/twrp-3.3.1-0-davinci.img
Maybe I could test first by
fastboot boot twrp-3.3.1-0-davinci.img
zgfg said:
Ok thanks, so starting from v11.0.4.0 QFJEUXM, rooted by Magisk (did not wipe Data or so, just patched and flashed boot img), is it ok just to flash (from Fastboot) twrp-3.3.1-0-davinci.img, downloaded from the official site https://twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
Yes, it should work.
But I prefer OrangeFox Recovery.
zgfg said:
so starting from v11.0.4.0 QFJEUXM, rooted by Magisk (did not wipe Data or so, just patched and flashed boot img), is it ok just to flash (from Fastboot) twrp-3.3.1-0-davinci.img, downloaded from the official site https://twrp.me/davinci/twrp-3.3.1-0-davinci.img
Maybe I could test first by
fastboot boot twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
Micdu70 said:
Yes, it should work.
But I prefer OrangeFox Recovery.
Click to expand...
Click to collapse
Something is fishy. IMO, if that official TWRP is really ok for 11.0.4.0, then it should correctly boot by:
fastboot boot twrp-3.3.1-0-davinci.img
But phone rebooted into the dark.
TG, I didn't really flash with, so by long pressing Pow it rebooted to system.
Tried again, no avail
Edit:
Tried the same fastboot boot with
twrp-3.3.1-12-davinci-mauronofrio.img and also OrangeFox-R10.1_1-Stable-davinci.img (obtained by unzipping OrangeFox), but it also reboots to dark and I have to long press Pow to reboot to system
frank808 said:
Hi Guys,
yesterday the new update came out, great.
I of course immediately pulled the zip (source) and installed it with TWRP (source).
So far no problems.
After a while I realized that I no longer had root because the apps stopped working.
When I wanted to boot into the TWRP to reinstall Magisk, I unfortunately found that it was no longer available, but only stock recovery.
Well, I thought to myself and tried to reinstall TWRP (method-twrp-3.3.1-2-davinci-fix), which was fatal, because my cell phone only booted into the Fastboot.
Then I got my cell phone, set up again with the Fastboot method.
Now I'm back to 11.0.4.0 but unfortunately without TWRP and root.
Can someone please describe how I can get TWRP and root again on Android 10?
I am thankful for every help !!!
Click to expand...
Click to collapse
You can install twrp by All In One tool
You can find its thread here itself
I took the official TWRP. " Link "
Flashed in fastboat and then booted the phone with a key combination in TWRP.
With the Fastboot command it didn't work for me either, the cell phone remained black ...
I was wondering if there is alternative option for Oneplus 6T/fajita recovery, like OrangeFox, RedFox, or other recoveries beside TWRP. TWRP doesn't work to restore on OP6T after backup. If I try to restore from previous backup, I will always end up in a continuous boot loop :'( and to resolve is issue, I have to flash the original ROM again but that affects some of my apps, so I have to check each app and reinstall them. In general TWRP doesn't work well on OP6T like other phones, and I couldn't find any alternative recovery options, and I wish someone is working on this.
Please let me know, even if there is beta or unofficial version that works with full ROM Backup and restore.
Thank you
FYI- I tried TWRP on different Pie custom Roms and OOS9 but the result is always the same, endless boot loop.
Nothing exists
You just taking a wrong steps while restoring. I've already done a two or three successful restores
Just backup these partitions:
1. Boot
2.System image
3.Vendor image
4.Data
romixer said:
You just taking a wrong steps while restoring. I've already done a two or three successful restores
Just backup these partitions:
1. Boot
2.System image
3.Vendor image
4.Data
Click to expand...
Click to collapse
I tried in that order and it doesn't work. I always end up in the boot-loop.
I even tried the following steps.
1. Boot to twrp recovery after full backup
2.Restore System image only
3.Reboot to twrp recovery
4.Restore Vendor image only
5.Reboot to twrp recovery again
6.Restore Data only
7.Restart
=>End result is the same, boot-loop.
I think TWRP is only good to flash zip files on Oneplus 6T .
duckduck2020 said:
I tried in that order and it doesn't work. I always end up in the boot-loop.
I even tried the following steps.
1. Boot to twrp recovery after full backup
2.Restore System image only
3.Reboot to twrp recovery
4.Restore Vendor image only
5.Reboot to twrp recovery again
6.Restore Data only
7.Restart
=>End result is the same, boot-loop.
I think TWRP is only good to flash zip files on Oneplus 6T .
Click to expand...
Click to collapse
You must be doing something wrong, perhaps using the wrong outdated version? The latest "unofficial" version posted here works, I can personally attest to that, but the older "official" version available on the TWRP site doesn't. It's outdated, and only works with Oreo and older ROMs.
There were issues with the "unofficial" TWRP and "Q" up until a couple of months ago that required the flashing of an additional file to get it to work properly, because of encryption errors, but even during that time period it was still working as expected on Pie.
Double check what you're doing, as you are making a mistake somewhere. The problem isn't with TWRP.
Link to the OP in the TWRP developer's thread here.