Develop Bugs

How to flash official nougat without wiping internal storage?

Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks

I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!

Edit : Nougat running on my op3.

abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?

To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!

anshulajain said:
I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!
Click to expand...
Click to collapse
I don't have any issues with ext4, infact i do feel ext4 is more stable than f2fs so file system is my last concern. Thanks for your method, but then how did u root again? Installing nougat is fine but what after that? I have read that you can't use modified twrp without formatting internal memory first, as it'll show you the pin issue. Let me know how do you propose a safe method to achieve root.
Renosh said:
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?
Click to expand...
Click to collapse
Yes i am encrypted, rooted, stock OOS 3.2.8 + Franco kernel. Official TWRP(not modified). I am using ext4, never used f2fs at all. The time to backup data and then to restore it all back is the reason formatting is not an "preferred" option for me. I can do it, but i would have to wait until i find enough time to do the whole process. I am in a full time job, so i hope you would understand.
Puddi_Puddin said:
To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!
Click to expand...
Click to collapse
Well this again defeats the purpose of my original question, but thanks mate. I would definitely read the guide if decide to switch to f2fs.

@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.

I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0

Puddi_Puddin said:
@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.
Click to expand...
Click to collapse
Thanks a lot for informing me mate. I really don't want to decrypt my storage as of now. I guess flashing stock recovery is the only solution now. Will hope someone would pick up the twrp and update it.

anshulajain said:
I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0
Click to expand...
Click to collapse
Seems like stock recovery is the best way as of now. Seems like I'll have to love without root until someone updates twrp to support encrypted storage.

I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.

abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...

Zielony360 said:
I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.
Click to expand...
Click to collapse
That i already knew mate. But i WANT my storage to remain encrypted. And that's the issue with modified TWRP. You can't enter into recovery on that if your storage is encrypted.
kpmohamedhussain said:
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...
Click to expand...
Click to collapse
Again, "You can't enter into recovery on modified TWRP if your storage is encrypted." So i won't be able to enter into twrp in the first place, let alone flash anything.

abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.

Go to twrp. Press backup. Select only data. Save to PC youre backup for safety..
3.2.8 it's Android 6, 4.0 it's Android 7. Some apps might not work from base to base.
If you want to change to F2FS it will format youre phone, wipe phone full internal memory. If you want to change it back to ext4, same.
Clean flash, full wipe it's always better.

dmoses1969 said:
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.
Click to expand...
Click to collapse
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.

anshulajain said:
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.
Click to expand...
Click to collapse
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.

abhibnl said:
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.
Click to expand...
Click to collapse
I dont know. I found this on Oneplus forum. May be worth trying. Just not 100% sure.....

Thanks! Will try and let you know

abhibnl said:
Thanks! Will try and let you know
Click to expand...
Click to collapse
Well, I tried something, waiting on it to finishing booting and see how it went.
I flashed twrp-3.0.2-1.28-oneplus3p version,
Flashed the OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip inside TWRP,
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip right after flashing OTA zip.
Its rebooting and says Android is upgrading. Fingers crossed.
EDIT: Its booted and I am on Nougat, didnt lose my data and phone is still encrypted!
Edit: Ended up having issues with settings app locking up. So, I went a different route and its all working great now.
Downloaded the stock recovery image and renamed it to recovery.img
Make sure after you rename it its not named recovery.img.img, If you have show file extensions enabled on your pc you should already see the file extension.
Rebooted to bootloader - adb flash recovery recovery.img
Using the volume keys and power button selected - reboot recovery.
Now in stock recovery - flashed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
After rom is done flashing, went right back into bootloader. Did not let my phone reboot to start the OS.
Renamed twrp-3.0.2-1.28-oneplus3p.img to recovery.img
adb flash recovery recover.img
Powered off phone and Manually boot it into recovery by holding Power + Volume Down button.
Phone booted into TWRP
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip
Wiped cache / dalvik
Rebooted system from TWRP and waited. System is really smooth now, no issues yet. Been playing with it for awhile now.
During the booting up process it might take a minute and it will reboot twice. Dont get nervous like I did thinking it was going to start bootlooping. It booted just fine. I read in a nother thread that SuperSU is what causes it to boot twice.
So......Now I have OOS 4.0 Nougat, Rooted, Encrypted and everything seems to be working fine.

Need help to root Redmi note 5 pro on Miui 11

How to root Redmi note 5 pro on Miui 11 ... please help

Rdxinha said:
How to root Redmi note 5 pro on Miui 11 ... please help
Click to expand...
Click to collapse
If you custom recovery then flash magisk file using your custom recovery this will work i guess

mohitmb0211 said:
If you custom recovery then flash magisk file using your custom recovery this will work i guess
Click to expand...
Click to collapse
question. flashing recovery need to wipe data? or i can flash twrp without wiping?

nicoodc said:
question. flashing recovery need to wipe data? or i can flash twrp without wiping?
Click to expand...
Click to collapse
It'll work without wiping data. I have tried it and i faced no problem.

mohitmb0211 said:
It'll work without wiping data. I have tried it and i faced no problem.
Click to expand...
Click to collapse
I hope you can help me, I'm having similar problems too. I boot into TWRP, but the new Android 9 updates, I think, have everything encrypted. So rooting my Redmi Note 5 Pro has been really puzzling me all day. Because of the encryption, I can't access the internal storage where Magisk or SuperSU .img should be, unless I wipe all data, which removes the .imgs. Following the advice of some other threads, I have tried rebooting TWRP from itself and then flashing a TWRP.img to flash but I can't find it anywhere either. I tried adb sideloading and adb pushing but I can't get my computer to detect my phone when its in recovery. Thought I'd ask here before making my own thread

Gdsad0 said:
I hope you can help me, I'm having similar problems too. I boot into TWRP, but the new Android 9 updates, I think, have everything encrypted. So rooting my Redmi Note 5 Pro has been really puzzling me all day. Because of the encryption, I can't access the internal storage where Magisk or SuperSU .img should be, unless I wipe all data, which removes the .imgs. Following the advice of some other threads, I have tried rebooting TWRP from itself and then flashing a TWRP.img to flash but I can't find it anywhere either. I tried adb sideloading and adb pushing but I can't get my computer to detect my phone when its in recovery. Thought I'd ask here before making my own thread
Click to expand...
Click to collapse
Change your recovery to orangefox recovery and encryption doesn't bother much just take your data backup and factory reset your phone.hope so it'll work.

mohitmb0211 said:
Change your recovery to orangefox recovery and encryption doesn't bother much just take your data backup and factory reset your phone.hope so it'll work.
Click to expand...
Click to collapse
Thanks, I ended up just getting an SD card and flashing with that

Gdsad0 said:
Thanks, I ended up just getting an SD card and flashing with that
Click to expand...
Click to collapse
Glad to help you .

Device turns off randomly after root

Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?

cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom

niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..

cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me

Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!

If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.

Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?

Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!

cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.

Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange

cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.

cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.

Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.

cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.

Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!

cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display

the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!

cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.

the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do

cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.

[Solved] Wifi , bluetooth and Mobile hotspot not working after installing lineage os 17.1

Hello,
I installed lineage os 17.1 but my wifi, bluetooth and hotspot are not working. In "About Phone" section, it is showing both wifi and bluetooth mac address as unavailable.
I also reflashed stock rom, but now, same issue is happening there. So I reflashed lineage os 17.1. Please help me!!!!.
@sunnyraj84348

gurbir3178 said:
Hello,
I installed lineage os 17.1 but my wifi, bluetooth and hotspot are not working. In "About Phone" section, it is showing both wifi and bluetooth mac address as unavailable.
I also reflashed stock rom, but now, same issue is happening there. So I reflashed lineage os 17.1. Please help me!!!!.
@sunnyraj84348
Click to expand...
Click to collapse
Try flashing another kernel

venu dinesh said:
Try flashing another kernel
Click to expand...
Click to collapse
Can you please give me a link to any tutorial?

gurbir3178 said:
Can you please give me a link to any tutorial?
Click to expand...
Click to collapse
Note: backup anytype of data in external storage
I AM NOT RESPONSIBLE FOR DAMAGE OF YOUR DEVICE
Wipe all except micro SD card..
Flash rom- gapps(if required)- magisk ( if required) - kernel ( try inferno kernel available in xda redmi 5a forums) reboot.. if you bypassed bootloader flash appender.zip for applying blocks .. use orange fox recovery for best results.. and custom rom work only in nougat firmware

gurbir3178 said:
Can you please give me a link to any tutorial?
Click to expand...
Click to collapse
t.me/Redmi_5a telegram link
Ask any questions there.. answers available soon

venu dinesh said:
Note: backup anytype of data in external storage
I AM NOT RESPONSIBLE FOR DAMAGE OF YOUR DEVICE
Wipe all except micro SD card..
Flash rom- gapps(if required)- magisk ( if required) - kernel ( try inferno kernel available in xda redmi 5a forums) reboot.. if you bypassed bootloader flash appender.zip for applying blocks .. use orange fox recovery for best results.. and custom rom work only in nougat firmware
Click to expand...
Click to collapse
Thanks I will try that. One more qustion. Will that kernel be booted as default? Or like in linux I have to choose kernel?

gurbir3178 said:
Thanks I will try that. One more qustion. Will that kernel be booted as default? Or like in linux I have to choose kernel?
Click to expand...
Click to collapse
It will be booted automatically.. there are many kernel available but u can choose one kernel to flash at once if you want to use another kernel you have to flash the rom again flashing kernel is as like flashing zips.
Do not flash 2 kernel in one rom. You will be held in bootloop

venu dinesh said:
It will be booted automatically.. there are many kernel available but u can choose one kernel to flash at once if you want to use another kernel you have to flash the rom again flashing kernel is as like flashing zips.
Do not flash 2 kernel in one rom. You will be held in bootloop
Click to expand...
Click to collapse
ok thanks.

venu dinesh said:
Note: backup anytype of data in external storage
I AM NOT RESPONSIBLE FOR DAMAGE OF YOUR DEVICE
Wipe all except micro SD card..
Flash rom- gapps(if required)- magisk ( if required) - kernel ( try inferno kernel available in xda redmi 5a forums) reboot.. if you bypassed bootloader flash appender.zip for applying blocks .. use orange fox recovery for best results.. and custom rom work only in nougat firmware
Click to expand...
Click to collapse
No Bro. Its not working. Same problem.

I also face the same problem when I flash lineages is 17.1,so now I am stock miui 11 don't have problems all works fine.I don't know in which way u flash stock ROM,Don't flash via recovery, I never done that ,try to flash it via fastboot tools use fastboot ROM

also face the same problem when I flash lineages is 17.1,so now I am stock miui 11 don't have problems all works fine.I don't know in which way u flash stock ROM,Don't flash via recovery, I never done that ,try to flash it via fastboot tools use fastboot ROM

Lak dj said:
I also face the same problem when I flash lineages is 17.1,so now I am stock miui 11 don't have problems all works fine.I don't know in which way u flash stock ROM,Don't flash via recovery, I never done that ,try to flash it via fastboot tools use fastboot ROM
Click to expand...
Click to collapse

Solution: Flash persist.img from orangefox recovery.
Steps:
1. Boot to Orangefox Recovery.
2. Select persist.img file (Downloaded previously in phone)
3. Select "Persist partition" before swiping.
4. Swipe and then reboot.

gurbir3178 said:
Solution: Flash persist.img from orangefox recovery.
Steps:
1. Boot to Orangefox Recovery.
2. Select persist.img file (Downloaded previously in phone)
3. Select "Persist partition" before swiping.
4. Swipe and then reboot.
Click to expand...
Click to collapse
I have a little confusion, can I get a perfect guideline or a perfect installation method

Lak dj said:
I have a little confusion, can I get a perfect guideline or a perfect installation method
Click to expand...
Click to collapse
Flash latest orange fox recovery first. Then boot into it. and follow the steps. Can you tell your problem in more detail?

gurbir3178 said:
Flash latest orange fox recovery first. Then boot into it. and follow the steps. Can you tell your problem in more detail?
Click to expand...
Click to collapse
Bro I need a clear flashing method

Lak dj said:
Bro I need a clear flashing method
Click to expand...
Click to collapse
I don't understand your problem. You can ask more here... t.me/Redmi_5a

gurbir3178 said:
I don't understand your problem. You can ask more here... t.me/Redmi_5a
Click to expand...
Click to collapse
Bro my doubt is when to flash the persist IMG, either while flashing along withthe ROM or after the ROM flashed

Lak dj said:
Bro my doubt is when to flash the persist IMG, either while flashing along withthe ROM or after the ROM flashed
Click to expand...
Click to collapse
after flashing rom.

gurbir3178 said:
after flashing rom.
Click to expand...
Click to collapse
Okay thanks for your help ,I'll try and I will reply if I face any issue,I check the link that u provide I am facing the error "Your not Authorized to Access the Content"

Issues with installing LOS 18.1 microG - maybe encryption?

Hello there,
I tried install the LOS 18.1 fork with microG using TWRP 3.6.2_9-0. Format data / factory reset, install zip, reboot. Everything fine, LOS is starting, setting the system up etc. Next restart straight into recovery which lost its setting. I thought maybe an encryption issue, so I formatted data to EXT2 and back to EXT4. Reboot into TWRP, settings are still fine. Installed LOS an reboot. Same problem: after setting the device up and first restart, straight into TWRP again.
Has anybody an idea what the issue can be? I had the same ginkgo before and never a problem installing Lineage with the standard method.
Thank you all
Flo

FarmerElm said:
I tried install the LOS 18.1 fork with microG using TWRP 3.6.2_9-0. Format data / factory reset, install zip, reboot. Everything fine, LOS is starting, setting the system up etc. Next restart straight into recovery which lost its setting. I thought maybe an encryption issue, so I formatted data to EXT2 and back to EXT4. Reboot into TWRP, settings are still fine. Installed LOS an reboot. Same problem: after setting the device up and first restart, straight into TWRP again.
Has anybody an idea what the issue can be? I had the same ginkgo before and never a problem installing Lineage with the standard method.
Click to expand...
Click to collapse
Do a clean flash
if problem persist change rom

Thank you so much, you are a star! It worked with the first try. I still do not understand why I could flash my previous ginkgo on TWRP without any hassles... but Ofox is defenitly the better experience.

FarmerElm said:
I still do not understand why I could flash my previous ginkgo on TWRP without any hassles
Click to expand...
Click to collapse
some rom have similar encryption key, but when you use a differant (especially A11/12) you will face bootloops ...
FarmerElm said:
... but Ofox is defenitly the better experience.
Click to expand...
Click to collapse
OFox is based on TWRP but have extra options that's why i suggest it
they both flash roms the same way (also backup the same way)
so the problem was the encryption, i don't think it's the recovery

How do you prevend the same issue after an OTA?
After an OTA it went to OrangeFox again --> "storage is encrypted". In OrangeFox I enabled OTA but not "Disable DM-Verity" and "Disable Forced Encryption".

FarmerElm said:
How do you prevend the same issue after an OTA?
After an OTA it went to OrangeFox again --> "storage is encrypted". In OrangeFox I enabled OTA but not "Disable DM-Verity" and "Disable Forced Encryption".
Click to expand...
Click to collapse
Use the DFE i linked in the tutorial
not the one included in Ofox

So you flash that DFE script after every OTA?

use "reply" button so i get a notification
FarmerElm said:
So you flash that DFE script after every OTA?
Click to expand...
Click to collapse
Roms encrypt storage by default
so to stay decrypted you have to flash DFE after the rom/ota

As far as I understood it, using the "disable forced encryption" setting in OrangeFox will not work? I will have to flash DFE after an OTA?

FarmerElm said:
As far as I understood it, using the "disable forced encryption" setting in OrangeFox will not work? I will have to flash DFE after an OTA?
Click to expand...
Click to collapse
i'm not sure if it work or not because it's outdated and i did not test it
i use the one i linked (from the official source)

Then I will do the same. Thank you so much for your advice!