After LineageOS OTA Update (30.5.2019) stuck in fastboot - Xiaomi Poco F1 Questions & Answers

Hi,
I was running:
Unlocked, TRWP and magisk on most actual version, beryllium-9.5.6-9.0-vendor-firmware, lineage-16.0-20190506-nightly-beryllium-signed
Today I started an OTA Lineage Update, but my Poco is now stuck in fastboot mode!
When I start minaml adb and type "fastboot continue", Lineage OS will boot normally. The TRWP-App Icon disappeared, but I can still start the TRWP-App via Google Play.
I copied all zips necessary for a clean new install onto my SD-Card, but I cannot boot into TRWP Recovery any more!
I downloaded the All in one tool, it connects: ADB device Ready. But I just don't know what to do for a clean new install.
Please help a newbie, I don't want to brick my Poco any further. I found a few threads that OTA Updates do not work that reliable, but I haven't figured out a solution.
Best regards

If I understand correctly, the Lineage OTA Update wiped the recovery Partition with TRWP?
That would explain why I cannot boot anymore to recovery.
As I remember I have been using OTA Updates in the past working fine. How should I update Lineage in the future? Always clean install? And how to backup all my data then, nandroid?
Should I now use the All in one tool to Flash TRWP again to recovery? How? Use "Recovery Flasher and Root" -> TRWP and check "Root after flash"?

Andi900rr said:
If I understand correctly, the Lineage OTA Update wiped the recovery Partition with TRWP?
That would explain why I cannot boot anymore to recovery.
As I remember I have been using OTA Updates in the past working fine. How should I update Lineage in the future? Always clean install? And how to backup all my data then, nandroid?
Should I now use the All in one tool to Flash TRWP again to recovery? How? Use "Recovery Flasher and Root" -> TRWP and check "Root after flash"?
Click to expand...
Click to collapse
Get the TWRP recovery image on to your pc, together with vendor/firmware zip for at least 2019-05-23. fastboot boot [TWRP recovery img] to boot the recovery, copy the vendor/firmware file over with adb, flash it with TWRP and reboot. If all goes well, great. If it doesn't, well...

Hi, I am unsure what you refer to by "TWRP recovery image", do you refer to "twrp-3.3.0-0-beryllium.img" or to some kind of backup image?
I have the "beryllium-9.5.23-9.0-vendor-firmware.img" on both, sd-card and PC now. I just do not know how to flash TWRP with the All in one tool, either by
Recovery -> Recovery Flasher and Root -> select recovery -> twrp-3.3.0-0-beryllium.img [and check the box "Root after Flash"]
or
Miscellaneous -> Advanced Options -> fastboot flash recovery twrp-3.3.0-0-beryllium.img
I just guess the first Option (Recovery)

Andi900rr said:
Hi, I am unsure what you refer to by "TWRP recovery image", do you refer to "twrp-3.3.0-0-beryllium.img" or to some kind of backup image?
I have the "beryllium-9.5.23-9.0-vendor-firmware.img" on both, sd-card and PC now. I just do not know how to flash TWRP with the All in one tool, either by
Recovery -> Recovery Flasher and Root -> select recovery -> twrp-3.3.0-0-beryllium.img [and check the box "Root after Flash"]
or
Miscellaneous -> Advanced Options -> fastboot flash recovery twrp-3.3.0-0-beryllium.img
I just guess the first Option (Recovery)
Click to expand...
Click to collapse
twrp-3.3.0-0-beryllium.img is what I was referring to. Boot it with the command I gave. The vendor-firmware is a zip file, not an img file. You need to flash that after booting TWRP.
Sent from my POCO F1 using XDA Labs

yes, vendor is of course zip not img.
Thank you for helping me!
I was using the all in one tool to Flash TWRP again with the Checkbox "root" activated, booted recovery and went though a whole new clean install, device is running fine again.
I am Kind of afraid to touch the OTA update Option ever again. Seems that when updating via OTA, one Need to still checkout compatibility of all other zips and TWRP Version etc.
So the effort is the same to do a clean install with all updated.

Related

Help needed.

Helo friends, I am new to redmi note 3 (sd). I officially unlocked the boot loader. I updated my device to 7.3.2 using miflash. I tried to install TWRP. I flashed the TWRP img and modified img. I tried to enter TWRP by pressing vol+ & power button. BUT no recovery was found . Simply Phone with cable image is showing in display. I followed all the steps carefully. I tried Cofface version and also the latest one.
Somebody please guide me step by step procedure to install TWRP. Somebody have the proper modified image for 7.3.2??? If yes means please give me the link.
In 7.1.8 i was able to get the TWRP. Is there any way to update to miui 7.3.2 by TWRP from 7.1.8
MIUI overwrites your recovery, disable it with the ALKA recovery, which can be found in Santosh's thread.
Here is what I did, to make TWRP workable, and it's very easy, no pc needed.
1. Install flashify
2. Install twrp with flashify but do not reboot yet
3. copy alka twrp to your phone
4. when it's done reboot your phone in flashify (right corner, reboot to recovery)
5. make system r/w (you will lose ota but screw it..., no other way to make twrp permanent on the phone)
6. flash alka update
7. reboot in twrp -> system
8. TWRP will give you a pop-up which tells you that you would like to disable the stock recovery, and just simply allow it to do it.
9. boom, done
Thanks bro!!!!!!!
Now i got both root and recovery on 7.3.2
balazs312 said:
MIUI overwrites your recovery, disable it with the ALKA recovery, which can be found in Santosh's thread.
Here is what I did, to make TWRP workable, and it's very easy, no pc needed.
1. Install flashify
2. Install twrp with flashify but do not reboot yet
3. copy alka twrp to your phone
4. when it's done reboot your phone in flashify (right corner, reboot to recovery)
5. make system r/w (you will lose ota but screw it..., no other way to make twrp permanent on the phone)
6. flash alka update
7. reboot in twrp -> system
8. TWRP will give you a pop-up which tells you that you would like to disable the stock recovery, and just simply allow it to do it.
9. boom, done
Click to expand...
Click to collapse
as for me the app freezes when I try to install twrp leaving me with a recovery-less phone help!
pandyajoe said:
Helo friends, I am new to redmi note 3 (sd). I officially unlocked the boot loader. I updated my device to 7.3.2 using miflash. I tried to install TWRP. I flashed the TWRP img and modified img. I tried to enter TWRP by pressing vol+ & power button. BUT no recovery was found . Simply Phone with cable image is showing in display. I followed all the steps carefully. I tried Cofface version and also the latest one.
Somebody please guide me step by step procedure to install TWRP. Somebody have the proper modified image for 7.3.2??? If yes means please give me the link.
In 7.1.8 i was able to get the TWRP. Is there any way to update to miui 7.3.2 by TWRP from 7.1.8
Click to expand...
Click to collapse
Tried to used this the latest from miui forum, redmi note 3 pro Snapdragon version: http://en.miui.com/thread-296053-1-1.html
Sent from my Redmi Note 3 using XDA-Developers mobile app

Rooting officially unlocked Redmi note 3 kenzo

in every forum ,about rooting rn3 pro i got only that i have to flash cracked boot.img or ubp zip after flashing supersu.zip.are they outdated.cant we do direct flash supersu zip directly using alka/cofface recovery or i have to use diseable verify option in recovery advanced menu.very messy please help me
Camlin3 said:
in every forum ,about rooting rn3 pro i got only that i have to flash cracked boot.img or ubp zip after flashing supersu.zip.are they outdated.cant we do direct flash supersu zip directly using alka/cofface recovery or i have to use diseable verify option in recovery advanced menu.very messy please help me
Click to expand...
Click to collapse
Simple steps:
1. Go in fastboot mode.
2. Flash official twrp.
3. Boot in recovery.
4. Flash supersu zip.
5. Reboot your phone.
And yeah, allow modification to system partition when asked in recovery. The only downside of the official recovery is that it will be replaced by the stock recovery on boot. No prob, you can flash it again. No need to flash custom cooked boot image or something.
To keep recovery forever:
In system partition, there will be a file next to build.prop, named something like recovery-boot-bak or something, delete it and then flash twrp and this time it will stay.
Archit9169 said:
Simple steps:
1. Go in fastboot mode.
2. Flash official twrp.
3. Boot in recovery.
4. Flash supersu zip.
5. Reboot your phone.
And yeah, allow modification to system partition when asked in recovery. The only downside of the official recovery is that it will be replaced by the stock recovery on boot. No prob, you can flash it again. No need to flash custom cooked boot image or something.
To keep recovery forever:
In system partition, there will be a file next to build.prop, named something like recovery-boot-bak or something, delete it and then flash twrp and this time it will stay.
Click to expand...
Click to collapse
After flashing for ex. Resurrection Remix (or any other custom rom) the device asks whether it should leave an old recovery or not. Flashing official miui zip doesn't touch the recovery at all.
So it's not necessary to delete any files (regarding my experience).
Sent from Note 3, Xiaomi Redmi Note 3.

Can't install TWRP

Hi,
there is something wrong with my Xperia Tablet Z. After upgrading from CyanogenMod 11 to CyanogenMod 12 a few Mouth ago the Custom Recovery i've installed before was replaced with CyanogenMod-Recovery. Because CM doesn't work very well i downgraded to Stock-ROM using Flashtool. Because i couldn't find a Way to root Firmware 4.2.x and higher i downgraded to 4.1.2 and rooted with towelroot. The Bootloader is unlocked (checked with *#*#7378423#*#*).
But when i try to install TWRP it failed. This is the error with Fastboot
Code:
fastboot flash recovery twrp.img
fastboot flash recovery twrp.img
sending 'recovery' (10688 KB)...
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.359s
All drivers are installed. I've tried this on Ubuntu 16.04 and Windows 7 with installed Flashtool and also with installed ADB Installer (https://forum.xda-developers.com/showthread.php?p=48915118#post48915118). I tried it with three usb cables and different usb ports.
It also doesn't work with TWRP Manager (https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=de) and the Official TWRP App (https://play.google.com/store/apps/details?id=me.twrp.twrpapp&hl=de). TWRP Manager show me this error
Code:
Flashing recovery was unsuccessful. Either you already have thos recovery installed or another error has occuured. Would you like to attempt to recovery now?
When i try to reboot the App freeze.
The Official TWRP App seems to install the recovery ("was successfully installed"), but i can't reboot into recovery with VOL+ (also tried VOL-). The Table starts normally.
Maybe there is something wrong with my Tablet now? Is there any other Way to flash a Recovery or to flash a Custom-Rom or a pre-rooted Stock-Rom? As i said before i can't root it with a Firmware higher 4.1.x. Update with the internal Update fuction also failed. So at the moment i can use [email protected] or a higher Version without root.
@PiereMallao
Sony devices, in particular, tabz don't have separate recovery partition. So you need to flash kernel with built-in recovery (see crDroid, RR, LA firmware threads), or you have to flash TWRP to FOTA partition.
Hi,
after some years with my pollux_windy left untouched, I decided I'd install my first custom ROM. But I'm having serious trouble to do so, and it seems unsolvable to me after hours of despair (I've been trying for almost 10 hours now).
I was on Lollipop (firmware .222), first unlocked my bootloader, then rooted my tablet (using kingroot). Then I tried to install twrp, and the only way I managed to do this was through this "TabZ-lockeddualrecovery2.8.26" thing. Only, I couldn't manage to flash anything, ended up bricking my tablet.
I then flashed a stock 5.0.2 ROM (.454), retried installing twrp via the same method, and although I manage to access twrp, I get the same error each time I want to flash a new ROM (tried CM/LineageOS 14.1 and ResurrectionRemix v5.7.0), which is : "E: error executing updater binary in zip [insert name of the .zip]".
If I hear Rootk1t correctly, I should flash a kernel with a built-in recovery first... But, doing some research, it looks like you need a working recovery in the first place to flash a custom kernel.
I'm completely lost in this... How can I get that damn recovery to work, and/or get a custom ROM ?
Edit : Alright, with a good 3 hours-long night and a lucky shot, I managed to install LineageOS ! I used twrp recovery (from the dualrecovery thingy-thing) to wipe clean the device, then tried to install the ROM. It gave me the same error message about updating binary. So I rebooted the device into fastboot (couldn't access the recovery anyway... not sure if it's normal), flashed the "boot.img" from the ROM using Flashtool, then rebooted again the device. On the bootlogo, I tried to enter recovery with Vol-, and it worked. i then flashed with ease the ROM. Maybe it will help somebody !
Hapaxx said:
If I hear Rootk1t correctly, I should flash a kernel with a built-in recovery first... But, doing some research, it looks like you need a working recovery in the first place to flash a custom kernel.
Click to expand...
Click to collapse
yep, one just need to
fastboot flash boot boot.img
Click to expand...
Click to collapse
enter recovery and flash firmware zip, gapps, etc from it.
Root works now, but i can't install TWRP 3.0.2.0 (but XZDualRecovery works).
Sony devices, in particular, tabz don't have separate recovery partition. So you need to flash kernel with built-in recovery (see crDroid, RR, LA firmware threads), or you have to flash TWRP to FOTA partition.
Click to expand...
Click to collapse
Hapaxx said:
So I rebooted the device into fastboot (...), flashed the "boot.img" from the ROM using Flashtool, then rebooted again the device.
Click to expand...
Click to collapse
If i understand correct Hapaxx flashed the boot.img form the LineageOS 14.1 Image? I don't want to install a Custom-ROM. crDroid is for Nexus. Where can i download a Kernel with build-in Recovery for tabz? or can i use the same crDroid also for tabz?
how can i flash the recovery to fota? can i do this with the same *.img or do i need an other image?
i just unlocked my bootloader and i dont know what else to do, i would like to install lineage 14.1 but i dont know what path to follow, i also hit the whole command not allowed thing, and what Hapaxx said, i'm unable to understand, could someone give a clear set of commands to follow? please? what to do in order so i dont brick my tablet.
Hi PiereMallao,
i have the same Odyssey behind me! Sony Xperia Tablet Z SGP321 LTE (16GB)
1. First check Bootloader unlocked with Flashtools 0.9.18.6. Check!
2. Install SGP321_10.1.1.A.1.307_Unbranded.ftf with Flashtools 0.9.18.6. Check!
3. Developertools on. USB-Debugging on. unknown sources on. Check!
4. Root with Doomlord_Rootkit_v18.rar. Check!
5. Check with App "Root-Checker" in Google PlayStore. Check!
6. And now I try to install TWRP for 3 days !
First try with TabZ-lockeddualrecovery2.8.26-RELEASE.combined.zip its ok, but i come only once after the installation in the recovery mode. Afterwards I have it with Vol+ or Vol- tried. It always starts the normal system.
7. With Fastboot -
Code:
fastboot flash recovery twrp.img
fastboot flash recovery twrp.img
target didn't report max-download-size
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.359s
How can i check Bootloader unlock ? In Android Tablet Z i didnt have a keyboard to put in the hex-code *#*#7378423#*#* ?
In Flashtools i checked Bootloader unlock so i have no idea at this Point.
What can I do ?
sorry, i have so solution for this problem. i have given up. theonly way i know to ceck the bl is unlocked or not is flashtool.
I'm having issues with this as well. Trying to install LineageOS 14.1, I can initially get twrp onto the tablet, flash LineageOS 14.1.. boot into it, set up (it is recommended to reboot the tablet once before flashing gapps) ...however, rebooting wipes twrp out. I'm not used to this FOTA thing (first i've ever heard of it) so not sure how to get twrp to 'stick' and not get wiped out
I got it installed this weekend. First secret was fastboot TWRP to boot, not recovery:
Fastboot flash boot twrp-------.img
Make sure you have the right TWRP image.
Then boot into recovery and TWRP comes up.
Flash lineage and gapps.
See:
https://forum.xda-developers.com/xp...de-tutorial-sony-xperia-tablet-z-lte-t3392831
bowguy said:
I got it installed this weekend.
Click to expand...
Click to collapse
I'm a little confused about part 14.
Download app from Play Store : Recovery Manager for Xperia. (done)
Chose FOTAkernel -> Backup. (this makes the app unresponsive for me so i skipped it for now)
Then TWRP -> Download. (done)
then the rest of the steps are confusing. b/c following that guide twrp is already on there (flashed via fastboot), and so why am i replacing the fastboot flashed twrp with the twrp just downloaded in the above step?
and what does the fotakernel have to do with all this? am i suppose to replace the fotakernel with the twrp image downloaded above?
the steps in that guide need more detailed elaboration
x000x said:
I'm a little confused about part 14.
Download app from Play Store : Recovery Manager for Xperia. (done)
Chose FOTAkernel -> Backup. (this makes the app unresponsive for me so i skipped it for now)
Then TWRP -> Download. (done)
then the rest of the steps are confusing. b/c following that guide twrp is already on there (flashed via fastboot), and so why am i replacing the fastboot flashed twrp with the twrp just downloaded in the above step?
and what does the fotakernel have to do with all this? am i suppose to replace the fotakernel with the twrp image downloaded above?
the steps in that guide need more detailed elaboration
Click to expand...
Click to collapse
I never did step 14. Looks straight forward. You should ask this question on that thread
bowguy said:
I never did step 14. Looks straight forward. You should ask this question on that thread
Click to expand...
Click to collapse
Have you rebooted and tried to get back into twrp after you installed the rom? I did the first few steps of the guide a few days back, but every time after flashing the rom it would wipe twrp. I think the only way to get twrp to 'stick' permanently is to complete all the steps
x000x said:
Have you rebooted and tried to get back into twrp after you installed the rom? I did the first few steps of the guide a few days back, but every time after flashing the rom it would wipe twrp. I think the only way to get twrp to 'stick' permanently is to complete all the steps
Click to expand...
Click to collapse
After installing twrp via fastboot per the directions, then reboot into recovery I had few problems. The only issues I had are solved by installing the ROM first - not gapps. Boot and run setup. Then boot recovery and install gapps.
I never had issues with twrp after installing. Power off, power on and rock volume up/volume down until you are in recovery
bowguy said:
After installing twrp via fastboot per the directions, then reboot into recovery I had few problems. The only issues I had are solved by installing the ROM first - not gapps. Boot and run setup. Then boot recovery and install gapps.
I never had issues with twrp after installing. Power off, power on and rock volume up/volume down until you are in recovery
Click to expand...
Click to collapse
Are you using twrp-3.0.2-0-pollux_windy?
x000x said:
Are you using twrp-3.0.2-0-pollux_windy?
Click to expand...
Click to collapse
Yes.
I never bothered with step 14 in the guide. It works fine as is.
P.S.
As per my post on the guide referenced, I installed Rashr and flashed TWRP that way. Seemed to work perfectly. TWRP now shows 3.0.2 which is correct version. No change to system boot. Nice app
Rootk1t said:
@PiereMallao
Sony devices, in particular, tabz don't have separate recovery partition. So you need to flash kernel with built-in recovery (see crDroid, RR, LA firmware threads), or you have to flash TWRP to FOTA partition.
Click to expand...
Click to collapse
Bro please give me link to twrp latest for sgp321 m going to unlock bootloader using" flash tool" is it ok
Please tell me how to flash recovary too
Is it ok if i root my tab after unlocking bootloader using king root ajnd flash using flashify
Is ressuraction remex stableto use tell me bugs
?
i had equal problem
FAILED (remote: Command not allowed)
i also have the same problem with my huawei chc u23 gplay mini bricked no recovery please help

Some root questions

I want to root my poco f1 ....
But i have some questions regarding it
1. Will my data be format while rooting and installing twrp
2. How i will get ota update
3. Will installing ota update also format my data?
1. Your whole internal data needs to be wiped... To flash the force decryption enabler at first...
Even while installing twrp via fastboot.. Your data will be formated
2. You will get updates... But not via ota.... Yes you will get to download the updateds in some roms... But you need to dirty flash them.
3. While dirty flashing.... Formatting data is not required.
roxor101 said:
1. Your whole internal data needs to be wiped... To flash the force decryption enabler at first...
Even while installing twrp via fastboot.. Your data will be formated
2. You will get updates... But not via ota.... Yes you will get to download the updateds in some roms... But you need to dirty flash them.
3. While dirty flashing.... Formatting data is not required.
Click to expand...
Click to collapse
Does the twrp with working decryption also need to format my data?
You can root your device in two ways.
First, with twrp (OTA won't work afterwards)
Second, without twrp (OTA will work)
First method, unlock the bootloader (device will be wiped)>Grab the twrp with working decryption>Boot your device into fastboot and type fastboot flash recovery twrp.img (or whatever the recovery image name is)>Now type fastboot boot twrp.img (or whatever the recovery image name is)>Once booted into twrp, swipe to allow modification>Now download Magisk installer and copy into the device>Flash it?Reboot to system>Profit.
N.B. After flashing twrp, make sure to first boot into twrp before booting into system or else device will restore stock recovery. If you need to update in future, just grab the twrp flashable update package and flash it. That's it. No need for OTA.
Second method, this will also require an unlocked bootloader. Once the bootloader is unlocked, get the stock boot image of your current software (e.g. if you are on miui 10 with October security patch, make sure to grab the stock boot image for miui 10 october). Now install Magisk manager apk in your device. Now open magisk manager and go to install. You will find an option for patching stock boot image. Click on it and select the stock boot image. Magisk will patch the boot image and will place it in your internal memory. Now boot into fastboot mode and type fastboot boot patched_boot.img (or whatever the name is). Once device is booted into system, go to Magisk and click on Install>Direct install (recommended).Magisk will get flashed by itself and reboot. Once rebooted, go to Magisk manager and check. If you do everything correctly, you are rooted.
N.B. When you get an OTA update, open Magisk and go to Unsinatll and click on "Complete uninstall". It will uninstall magisk and revert your stock boot image back. Note that, if you play witgh system partition like modifying build.prop or change host file or bootanimantion or any such thing, you won't be able to get any further OTA update. In that case, you need to flash the complete fastboot rom through MiFlash tool.
For more information, please go to Magisk thread or search online.

Help how to do the Root on the Xiaomi Mi 8 device with the MIUI Global Stable!!

Hi everyone, I am recently registered on this site. from some days I have the desire to do the Root on the miui global stable, it is consequently on my beloved Xiaomi Mi 8, the problem is: when the device is turned off I turn on the device pressing it under volume key + ignition key at the same time to enter in recovery mode, the latter makes me enter in "Official" mode, in the sense that it does not let me enter twrp mode where there are install, settngs, advacend options, backup ... but in the official one with only 3 buttons: wipe , connect to mi account ... So I thought of flashing the twrp via fastboot, I finally entered it, but the problem is that when I go to Install, to install the root, I can't do that, because characters (alphanumeric) appear long and randomly, so I can't identify which folder I put the Magisk on, it appears in both folders and subfolders. somewhere I read to install a zip file called LazyFlasher, to avoid possible blocking at startup, in fact I try before installing this zip file, with various combinations (first rom, then magisk, both rom and magisk, first magisk then rom , first rom that gate at the end the cache then magisk) but all fail, so I am forced to flash through fastboot with the tool I flash, because at every start it always took me back to twrp without the possibility of moving, it seems that the touch does not respond at the user's commands. So I know that this LazyFlasher file causes me to "bypass" this problem, give me confirmation ??. Thank you. PS: so far I haven't managed to install the Magisk root yet, can you give me a hand, maybe the twrp has some problems? or is my device not compatible with this version of twrp ??, I tell you that in the past with the miui global beta it didn't give me this problem. Thank you all
Have you even unlocked your bootloader? If not look for the official Xiaomi tool, it's the only way how you are able to flash twrp and root your phone.
altae said:
Have you even unlocked your bootloader? If not look for the official Xiaomi tool, it's the only way how you are able to flash twrp and root your phone.
Click to expand...
Click to collapse
Thanks for the reply, I solved everything, unlocked BL, installed twrp (no stock) and installed root. but I have a problem, when I installed the root, every time I want to restart the device for a series of reasons (slowness, delete cache, rest ...) it starts in twrp not in the system, so I have to delete everything it's starting again. I heard that the LazyFlasher file makes it possible to remedy this problem, essentially it allows you to bypass the security of android to avoid bootloap, and I hope it also corrects this problem (which when I reboot the device, I want to install a zip file, I it always starts in twrp), but during the flash of this zip (LazyFlasher) I get an error: the Updater process ended with error: 1 Error installing zip '/sdcard/lazyflasher-no-verify-opt-encrypt.zip. Thanks a lot. PS: but this file, lazyflasher should be mounted on an SD card to work ?? I don't have it on my device
Paoloqu24 said:
Thanks for the reply, I solved everything, unlocked BL, installed twrp (no stock) and installed root. but I have a problem, when I installed the root, every time I want to restart the device for a series of reasons (slowness, delete cache, rest ...) it starts in twrp not in the system, so I have to delete everything it's starting again. I heard that the LazyFlasher file makes it possible to remedy this problem, essentially it allows you to bypass the security of android to avoid bootloap, and I hope it also corrects this problem (which when I reboot the device, I want to install a zip file, I it always starts in twrp), but during the flash of this zip (LazyFlasher) I get an error: the Updater process ended with error: 1 Error installing zip '/sdcard/lazyflasher-no-verify-opt-encrypt.zip. Thanks a lot. PS: but this file, lazyflasher should be mounted on an SD card to work ?? I don't have it on my device
Click to expand...
Click to collapse
Flash a DM-Verity No-Encryption ZIP to remove encryption and disable the Verity check. OR if you want to keep encryption and root -flash a 3rd party Kernel like MiPa or Sphinx after Magisk.
Agimax said:
Flash a DM-Verity No-Encryption ZIP to remove encryption and disable the Verity check. OR if you want to keep encryption and root -flash a 3rd party Kernel like MiPa or Sphinx after Magisk.
Click to expand...
Click to collapse
thank you. in the past I flamed DM-Verity No-Encryption ZIP to remove encryption and disable Verity checking. in fact after immediately this zip I put magisk. at the access of the dispay I saw a magisk icon, so it means root installed successfully. but the problem is: when I reboot the device to clear the cache ... or install a module on the magisk, it always starts in twrp, so I have to start all over again. there is a way to keep cryptography and root, without any booting going into twrp but into the system. thank you
Paoloqu24 said:
thank you. in the past I flamed DM-Verity No-Encryption ZIP to remove encryption and disable Verity checking. in fact after immediately this zip I put magisk. at the access of the dispay I saw a magisk icon, so it means root installed successfully. but the problem is: when I reboot the device to clear the cache ... or install a module on the magisk, it always starts in twrp, so I have to start all over again. there is a way to keep cryptography and root, without any booting going into twrp but into the system. thank you
Click to expand...
Click to collapse
You shouldn't have these problems:
Flash ROM and Keep Encryption:
Flash TWRP
Boot into TWRP and flash MIUI ROM
Flash TWRP again (select flash image, then select recovery partition, then select recovery file)
Flash DM-Verity ZIP here-->: DM-Verity (Make sure 'DM-Verity' file is the ONLY thing the file is named. The filename triggers what is installed during flash)
Flash MAGISK
Flash 3rd Party Kernel (I prefer MiPa or Sphinx found in other threads)
Reboot and enjoy!
Flash ROM and REMOVE Encryption: (Keeps Stock Kernel)
Flash TWRP
Boot into TWRP and flash MIUI ROM
Flash TWRP again (select flash image, then select recovery partition, then select recovery file)
Flash DM-Verity ZIP here-->: DM-Verity (Make sure 'verity' AND 'forceencryp' is in the file name. The filename triggers what is installed during flash)
Reboot and enjoy!
If you have problems with any of them, you might need to format internal storage first (where you have to answer 'yes' in TWRP)
/.
As far as I understand, you are having problems while booting into TWRP. You should boot into TWRP right after flashing it, and boot into OS once again and reboot to recovery. It should work. If you see the stock recovery, keep flashing TWRP. If you want to temporarily flash it, use "fastboot boot TWRP.img" command.
The War Profiteer said:
As far as I understand, you can't boot into TWRP. You should boot into TWRP right after flashing it, and boot into OS once again and reboot to recovery. It should work. If you see the stock recovery, keep flashing TWRP. If you want to temporarily flash it, use "fastboot boot TWRP.img" command.
Click to expand...
Click to collapse
No problems booting into TWRP.
You can use "fastboot.exe flash recovery twrp.img"
Then reboot phone and hold volume-up+power. When booting until TWRP appears. If you miss it and it tries to boot it will overwrite it. But I've never had issues otherwise.
Agimax said:
You shouldn't have these problems:
Flash ROM and Keep Encryption:
Flash TWRP
Boot into TWRP and flash MIUI ROM
Flash TWRP again (select flash image, then select recovery partition, then select recovery file)
Flash DM-Verity ZIP here-->: DM-Verity (Make sure 'DM-Verity' file is the ONLY thing the file is named. The filename triggers what is installed during flash)
Flash MAGISK
Flash 3rd Party Kernel (I prefer MiPa or Sphinx found in other threads)
Reboot and enjoy!
Flash ROM and REMOVE Encryption: (Keeps Stock Kernel)
Flash TWRP
Boot into TWRP and flash MIUI ROM
Flash TWRP again (select flash image, then select recovery partition, then select recovery file)
Flash DM-Verity ZIP here-->: DM-Verity (Make sure 'verity' AND 'forceencryp' is in the file name. The filename triggers what is installed during flash)
Reboot and enjoy!
If you have problems with any of them, you might need to format internal storage first (where you have to answer 'yes' in TWRP)
/.
Click to expand...
Click to collapse
Thanks for the reply. I will choose the first option, I replace the stock kernel with sphinx kerne, so I get more functionality, battery life, performance, fluidity ... also the developer has mentioned us, if any desired functionality is missing in this kernel, it is possible ask the developer to add us. so I choose the first option, I have some questions before replacing the stock kernel: 1) is it possible to restore the kernel stock, in case of problem, if yes, where can I get the kernel for Mi 8? 2) if in the future there will be a new update of sphinx kerne, how do I understand if a new update has been released? will you notify me ?? 3) are you sure that after these steps, upon restarting the phone, I will find the root installed ?, if I would like to restart the device, it will not boot in twrp but in the system, because I replaced the stock kernel, the same thing is also valid for the magisk modules, zip files ... 4) the last fundamental thing, will I receive updates via OTA ?? if not, is there a way to install future updates (I would like to try the latest magisk version, 19.3) ?. 5) it is safe if I install update via ota, it does not start in twrp, but system. 6) the steps to do are, flash twrp custom via fastboot, I choose to delete the memory, restart twrp, copy the files (MIUI global stable, sphinx kernel, dm-verify), flash rom, flash dm-verify, flash magisk, flash kernel, device reboot, all right. Thanks a lot for the questions
Agimax said:
You shouldn't have these problems:
Flash ROM and Keep Encryption:
Flash TWRP
Boot into TWRP and flash MIUI ROM
Flash TWRP again (select flash image, then select recovery partition, then select recovery file)
Flash DM-Verity ZIP here-->: DM-Verity (Make sure 'DM-Verity' file is the ONLY thing the file is named. The filename triggers what is installed during flash)
Flash MAGISK
Flash 3rd Party Kernel (I prefer MiPa or Sphinx found in other threads)
Reboot and enjoy!
Flash ROM and REMOVE Encryption: (Keeps Stock Kernel)
Flash TWRP
Boot into TWRP and flash MIUI ROM
Flash TWRP again (select flash image, then select recovery partition, then select recovery file)
Flash DM-Verity ZIP here-->: DM-Verity (Make sure 'verity' AND 'forceencryp' is in the file name. The filename triggers what is installed during flash)
Reboot and enjoy!
If you have problems with any of them, you might need to format internal storage first (where you have to answer 'yes' in TWRP)
/.
Click to expand...
Click to collapse
I get an error during the installation of sphinx: the Updater process ended with error: 1 Error installing zip '/sdcard/sphinx.zip
Agimax said:
You shouldn't have these problems:
Flash ROM and Keep Encryption:
Flash TWRP
Boot into TWRP and flash MIUI ROM
Flash TWRP again (select flash image, then select recovery partition, then select recovery file)
Flash DM-Verity ZIP here-->: DM-Verity (Make sure 'DM-Verity' file is the ONLY thing the file is named. The filename triggers what is installed during flash)
Flash MAGISK
Flash 3rd Party Kernel (I prefer MiPa or Sphinx found in other threads)
Reboot and enjoy!
Flash ROM and REMOVE Encryption: (Keeps Stock Kernel)
Flash TWRP
Boot into TWRP and flash MIUI ROM
Flash TWRP again (select flash image, then select recovery partition, then select recovery file)
Flash DM-Verity ZIP here-->: DM-Verity (Make sure 'verity' AND 'forceencryp' is in the file name. The filename triggers what is installed during flash)
Reboot and enjoy!
If you have problems with any of them, you might need to format internal storage first (where you have to answer 'yes' in TWRP)
/.
Click to expand...
Click to collapse
both methods don't work, the first one gives me error when I install kernel, the second one on startup gives me a lot of error
I managed to install the root, doing the following steps: flash twrp via fastboot, copy the files to the internal memory, install rom files, install magisk files, install dm-verify, then reboot, and it works perfectly. but I have some problems: when I reboot the device, it starts in twrp not in the system, and therefore I am forced to do it again. help me !! kernel replacement gives me error, both
Paoloqu24 said:
I managed to install the root, doing the following steps: flash twrp via fastboot, copy the files to the internal memory, install rom files, install magisk files, install dm-verify, then reboot, and it works perfectly. but I have some problems: when I reboot the device, it starts in twrp not in the system, and therefore I am forced to do it again. help me !! kernel replacement gives me error, both
Click to expand...
Click to collapse
You should not have errors flashing a kernel. Maybe you should flash all partition images from fastboot. Or maybe wrong recovery? What version are you using?
Agimax said:
You should not have errors flashing a kernel. Maybe you should flash all partition images from fastboot. Or maybe wrong recovery? What version are you using?
Click to expand...
Click to collapse
the kernel is: Sphinx-v2.9
Paoloqu24 said:
the kernel is: Sphinx-v2.9
Click to expand...
Click to collapse
I mean what version of recovery. You should use this one (v3.3.1) or newer: https://www.androidfilehost.com/?fid=3556969557455275724
It's from this thread: https://forum.xda-developers.com/mi-8/development/recovery-unofficial-twrp-recovery-t3893823
Agimax said:
I mean what version of recovery. You should use this one (v3.3.1) or newer: https://www.androidfilehost.com/?fid=3556969557455275724
It's from this thread: https://forum.xda-developers.com/mi-8/development/recovery-unofficial-twrp-recovery-t3893823
Click to expand...
Click to collapse
TWRP 3.3.1.1 https://eu.dl.twrp.me/dipper/
I followed in this guide "https://clk.ink/7q4SUR" but instead of installing Disable_Dm-Verity_FEC_v1.1.zip I downloaded Disable_Dm-Verity_ForceEncrypt_09.02.2018.zip, is it the same ?, also I saw that, when I go inside the magisk, and I click on uninstall> restore image, a warning appears "there is no original boot image", I also executed this command in powershell "fastboot getvar current-slot" but I get a "GetVar Variable Not found" error. I don't know how to solve. thank you

Categories

Resources