Database Develop

lollipop update

i was updating my s advance with CyanogenMod 12.1 [26/11/15].........currently i have 4.1 jellybean indian version ddlup8 with root access ........... whenever i went for recovery i install cwm 6.8 it installs for little time only. please tell where i am wrong i want to install 5.1 lollipop on my device, i follow these steps but installation always gets cancel .......
1. i ve rooted my devive
2. i installed recovery cwm
3. i back up my data
4. wipe data
5. wipe cache
6. wipe dalchvik cache
7 then i install cyanogenMOd 11 ( buit it doesnt install)
so i tried directly installing cyanogenMOd 12 with cwm but does work
so please tell me what is the problem and what step should i follow.
I want to install CyanogenMod 12.1 [26/11/15] but error comes like:
apply parsed perms : isetfilecon of /system/lost+
not supported on transport endpoint
set metedata recursive:
E:Error in /sdcard/cm12.1_
(status 7)
installation aborted

Try using TWRP instead of CWM

Patil.sid101 said:
i was updating my s advance with CyanogenMod 12.1 [26/11/15].........currently i have 4.1 jellybean indian version ddlup8 with root access ........... whenever i went for recovery i install cwm 6.8 it installs for little time only. please tell where i am wrong i want to install 5.1 lollipop on my device, i follow these steps but installation always gets cancel .......
1. i ve rooted my devive
2. i installed recovery cwm
3. i back up my data
4. wipe data
5. wipe cache
6. wipe dalchvik cache
7 then i install cyanogenMOd 11 ( buit it doesnt install)
so i tried directly installing cyanogenMOd 12 with cwm but does work
so please tell me what is the problem and what step should i follow.
I want to install CyanogenMod 12.1 [26/11/15] but error comes like:
apply parsed perms : isetfilecon of /system/lost+
not supported on transport endpoint
set metedata recursive:
E:Error in /sdcard/cm12.1_
(status 7)
installation aborted
Click to expand...
Click to collapse
Extract boot.img from cm12.1 zip file
Flash boot.IMG
Reboot recovery
Flash cm12.1 zip file followed by GAPPS
Voilà.. All done

Or you can install this modded CyanogenMod 12.1 with integrated gapps, works on old cwm too: https://www.dropbox.com/s/v41kau37sxyct7i/CM12.1.zip?dl=1

Patlcs said:
Extract boot.img from cm12.1 zip file
Flash boot.IMG
Reboot recovery
Flash cm12.1 zip file followed by GAPPS
Voilà.. All done
Click to expand...
Click to collapse
how to flash boot.img please explain in detail.
currently i have flashed 4.12 stock rom and root.zip
but twrp recovery is not installing and cwm recovery is not working
please help me to update

Patil.sid101 said:
how to flash boot.img please explain in detail.
currently i have flashed 4.12 stock rom and root.zip
but twrp recovery is not installing and cwm recovery is not working
please help me to update
Click to expand...
Click to collapse
you can try to use the temporary CWM recovery to flash the boot.img file.
as i said earlier, extract the boot.img file from the rom file and then flash it via the recovery.

I am faceing the same problem
Patlcs said:
you can try to use the temporary CWM recovery to flash the boot.img file.
as i said earlier, extract the boot.img file from the rom file and then flash it via the recovery.
Click to expand...
Click to collapse
Hi
I am faceing the same problem. Can u Explain in Details how to use CWM recovery to flash the boot.img file ?

souravsadvanced said:
Hi
I am faceing the same problem. Can u Explain in Details how to use CWM recovery to flash the boot.img file ?
Click to expand...
Click to collapse
Wow i didnt think that i would reply to something i said 2 years ago xD
Hmm i am a bit rusty now as i upgraded to the s7 and now note 8 where i have not rooted or installed custom roms for a while so try it at your own risk.
If i recall correctly, you need to extract the boot.img file from cm12.1 using 7zip or winrar on your pc
Then there should be another thread for a temporary cwm recovery. Download the file and flash it when u are in recovery mode.
After flashing that temp cwm file, it should boot into it automatically and then flash cm11 followed by gapps

[ROM] OxygenOS Open Beta 9 (Nougat) Update and Installation!!

Hi everyone,
We appreciate everyone’s feedback from the OxygenOS Open Beta 8. With your help, we have optimized and improved several key areas.
The changes include:
Added Expanded Screenshots
Shelf Design Optimizations
General UI Optimizations
DPI Optimizations
Battery Performance Optimizations
Stability and Performance Optimizations
General bug fixes
Please visit the download page here:
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_9/
If you’ve already flashed a previous Open Beta build, you will receive this update via OTA. If you haven’t, you will need to flash this build by ADB sideload. Your data may transfer, but there is always a possibility of losing personal data, so be sure to backup all of your important data before flashing this build. As stated before, once you flash the Open Beta, you’ll continue getting Open Beta OTAs.
Please follow the link below for the UI/UX experience survey. We’d really appreciate a few minutes of your time, as it will help us make OxygenOS even better. One last thing: this is a limited program, so we may disable this download link once we receive enough feedback.
- Feedback on UI/UX: https://goo.gl/forms/hEqMPq9U9QNrxvhc2
Note: If you flash this Open Beta build, you’ll receive Open Beta OTAs (but not official OTAs). You’ll need to manually (clean) flash back to our official builds to continue receiving official OTAs. Rolling back to official OxygenOS versions require wiping data and cache.
Thank you for your patience and as always, we look forward to hearing your continued feedback in the bug reporting forum here: https://forums.oneplus.net/feedback/.
Thank you for helping us build a better OxygenOS.
Never settle.

Installation Methods
Before we start:This method is only for the OnePlus 3
Follow the steps correctly otherwise you may brick your device. I am not responsible for any damage to your device, please ensure that your device is at least 60% charged to prevent the accidental shutdown in-between the update process.
Downloads:
Beta 9 Full Zip Official Download
Compatible Stock Recovery
********************* For Stock Non Rooted Users with Stock Recovery *****************
1. Download the appropriate OTA/Full Zip from above link and place it in the root folder.
2. Navigate to Settings > System Updates > Settings Icon > Local Upgrade & Select the OTA File
3. Once selected system would prompt upgrade now
4. Select upgrade now and system would reboot in stock recovery and flash the OTA
5. The installer would itself flash the OTA and reboot the device.
The Device will reboot and your OnePlus 3 is now running on the latest OxygenOS firmware & OS.
PS: The first boot may take some time so keep calm and wait for it to boot.
* After flash is successful go back to recovery and a wipe of cache is recommended.
* If in any case flash is unsuccessful the system would prompt you to download the full 1.4GB zip. So download that and follow the same process as above.
************************ For Rooted Users with TWRP Recovery ************************
Download Beta 9 Full Zip
1. Download the Beta 9 Full Zip on your phone internal memory.
2. Download the Latest SuperSU SR5
4. Reboot To TWRP (Modified 28) & Take a Nandroid of your existing ROM
5. Go to Wipe > Advance Wipe > Select Dalvik & Cache & Swipe to Wipe
6. Install Menu > Select Beta 9 Rom Zip > Swipe to Flash
7. Wipe Dalvik & Cache
8. Flash SuperSU to maintain root
9. Reboot System and Enjoy the Beta 9 Update
* Do not flash Xposed as not compatible with 7.0 builds yet
If you come from a custom rom, i recommend a clean flash and make sure you use the modified TWRP 3.0.2-1.28 as the official one is incompatible with the CB firmware yet.
PS: The first boot may take some time so keep calm and wait for it to boot and the system would boot twice due to flash of supersu so keep calm
PS: Rooted users may either flash the full Beta 9 Zip or they need to flash the previous full zip beta 8 first to overwrite system partition followed by the relevant Beta 9 OTA zip for a successful flash else just the OTA flash would fail with error 7 in TWRP

I was on TWRP (modded) and rooted. Installed the update (OTA) and now my phone just reboots to TWRP no matter what I do (I have even made a factory reset and reinstalled Beta8)

salomaoa said:
I was on TWRP (modded) and rooted. Installed the update (OTA) and now my phone just reboots to TWRP no matter what I do (I have even made a factory reset and reinstalled Beta8)
Click to expand...
Click to collapse
You can't install the ota update on TWRP recovery. You need the stock one.
Try reflashing TWRP recovery via fastboot and then flash open beta 9(not the ota)

salomaoa said:
I was on TWRP (modded) and rooted. Installed the update (OTA) and now my phone just reboots to TWRP no matter what I do (I have even made a factory reset and reinstalled Beta8)
Click to expand...
Click to collapse
Download the recovery at the bottom of the page.
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_9/
Copy it onto your phone with the this Open Beta 9 package.
Start up TWRP, format /dalvik, /cache, /system, /data.
Flash the Open Beta and clean the caches if asked.
Flash the original recovery from TWRP as recovery image, and restart your phone afterwards.
Your phone may boot into the new recovery, then show "Update failed", then do another restart, but after that mine was working.

Does all partitions support f2fs?

smk513 said:
Does all partitions support f2fs?
Click to expand...
Click to collapse
AFAIK, only data partition is f2fs

Sun90 said:
AFAIK, only data partition is f2fs
Click to expand...
Click to collapse
I wonder if the new version is possible...
Thank you for your response.

flashing with twrp will result in recovery booting loop. after downloading ota simply reboot to recovery, download oneolusrecovery from ob9 page. transfer it to phone. select install image in twrp, select reocover, flash as recovery and reboot to recovery. itll show updating.. takes about 20mins

Will modified twrp also not work?

Really? The modified twrp doesnt work? I,ve read the thread in oneplus forum and some are saying it worked for them. :/
Edit: anyways, im on modified twrp, rooted, beta 8, can i dirty flash beta 9?

jfodra said:
Really? The modified twrp doesnt work? I,ve read the thread in oneplus forum and some are saying it worked for them. :/
Click to expand...
Click to collapse
It works. I flashed the full zip with it.
Edit:
Yes you can dirty flash. Everything is working as expected.

jfodra said:
Really? The modified twrp doesnt work? I,ve read the thread in oneplus forum and some are saying it worked for them. :/
Click to expand...
Click to collapse
It will work with full zips !! It won't work it ota updates
As simple as this

Dirty flashed over OB8, everything working fine!
Edit:
Using Modified TWRP

Dirty flashed over OB8, so far no issue's.
Did flash TWRP img after update in TWRP (just to be sure), first boot took a while tho.
Anyone tried supersu?

I have this from yesterday. I was on 3.2.8 from OnePlus site, dated 12.05.16.
Clean flash with TWRP 3.0.2-1.28, thanks to eng_stk. Flash the rom & SuperSU SR5 (if you want root). Refalsh recovery 3.0.2-1.28. Reboot to recovery. If it not works reflash recovery.
Then reboot to system.
I did not flash any mods. All it's ok.

t181 said:
It works. I flashed the full zip with it.
Edit:
Yes you can dirty flash. Everything is working as expected.
Click to expand...
Click to collapse
Oh okay thanks. So is it the same as before? Flash beta 9, flash twrp again, then flash sr5 then reboot?
Edit: Nvrmind, flashed it already and d*mn. It does feel smoother than beta 8. ???

Can it be flashed over modded Open Beta 8 ?

M3ntoR said:
Can it be flashed over modded Open Beta 8 ?
Click to expand...
Click to collapse
Yep. Just make sure to have the full update and not the OTA one. Also, just in case make sure you have the TWRP img and super-su on your phone's memory to be able to flash them again

Any mirror for this? Full zip is downloading really slow and I've already stucked on twrp after OTA Need to dirty flash the full zip, but it is going to dowload around Christmas with that speed...

Stuck in bootloop after Xposed install [Magisk][Exposed][Recovery]

Device is stuck in bootloop after I installed Xposed framework module from magisk manager .
I've tried uninstalling magisk , but the uninstall package terminates with error .
Then I flashed stock boot.img , it is booting but I cannot disable the module as magisk isn't installed.
Is there a way I can removed magisk's files / uninstall magisk modules manually from twrp .
Thanks !
(If there is some more relevant place for this thread , please let me know I'll post this there.)
Edit: Fixed it!

you will have to reflash entire system.img + boot.img again with proper wiping.

I never got xposed working on R6 stock.. (i got it magically working on GSI tho) I really want Xposed tho.. :/

TanRayCz said:
I never got xposed working on R6 stock.. (i got it magically working on GSI tho) I really want Xposed tho.. :/
Click to expand...
Click to collapse
which gsi image & twrp you are using? I flashed rr gsi-nosu-vanilla but it keeps bootloop.

abkdmn said:
which gsi image & twrp you are using? I flashed rr gsi-nosu-vanilla but it keeps bootloop.
Click to expand...
Click to collapse
LOS Treble. Call/SMS issues though. LR Team TWRP.

TanRayCz said:
LOS Treble. Call/SMS issues though. LR Team TWRP.
Click to expand...
Click to collapse
i tried flashing the los (15.1 arm A only) gsi image, stuck at bootloop.
how can u succeed?

Michaelw7 said:
i tried flashing the los (15.1 arm A only) gsi image, stuck at bootloop.
how can u succeed?
Click to expand...
Click to collapse
If youll get into bootloop i suggest you trying to wipe system and data partitions from fastboot (important), then flash stock ROM and then flash the GSI. This most of the time worked for me as clear GSI flash. So steps may not be necessary.

TanRayCz said:
If youll get into bootloop i suggest you trying to wipe system and data partitions from fastboot (important), then flash stock ROM and then flash the GSI. This most of the time worked for me as clear GSI flash. So steps may not be necessary.
Click to expand...
Click to collapse
thank u for the help. i will try it

TanRayCz said:
If youll get into bootloop i suggest you trying to wipe system and data partitions from fastboot (important), then flash stock ROM and then flash the GSI. This most of the time worked for me as clear GSI flash. So steps may not be necessary.
Click to expand...
Click to collapse
[official] miui 10 recovery & fastboot ROM
tried wipe system and data partition from fastboot.
and then flash stock rom (from [official] miui 10 recovery & fastboot ROM thread in kernel sub forum), and then instal the gsi image los 15.1.
still bootloop. idk what i did wrong. still no clue

Michaelw7 said:
[official] miui 10 recovery & fastboot ROM
tried wipe system and data partition from fastboot.
and then flash stock rom (from [official] miui 10 recovery & fastboot ROM thread in kernel sub forum), and then instal the gsi image los 15.1.
still bootloop. idk what i did wrong. still no clue
Click to expand...
Click to collapse
Try to flash stock kernel/boot.img or remove Magisk trough uninstaller. This magically helped me one time

TanRayCz said:
Try to flash stock kernel/boot.img or remove Magisk trough uninstaller. This magically helped me one time
Click to expand...
Click to collapse
where can ai get the stock kernel file?

Michaelw7 said:
where can ai get the stock kernel file?
Click to expand...
Click to collapse
You can restore boot.img by installing Magisk uninstaller update ( it's available on Magisk thread I think) , or download a fastboot update for your device to get stock boot.img

Michaelw7 said:
where can ai get the stock kernel file?
Click to expand...
Click to collapse
You can extract it from firmware ZIP

Michaelw7 said:
where can ai get the stock kernel file?
Click to expand...
Click to collapse
go to this site. (not promoting it or something) https://extract.me paste this link [ http://bigota.d.miui.com/V10.0.1.0....FH_20180919.0000.00_8.1_global_794ccbbe18.tgz ] wait a few second then you will see all files from this archive, download what you want from it. It will save you a lot of time to download entire archive. Trust me.

GUIDE How to Instal GSI ROM- Havoc-OS-v4.X-Official Android 11 On Redmi 8

Here I bring to you the official Havoc-os 4.X ROM Android 11 and fully functional on Redmi 8
The intention of this post is to make a step-by-step tutorial on the installation of this excellent GSI ROM on Redmi 8 and give assistance in the installation process
All the development credits for this wonderful ROM go to the Havoc team
@Ruturaj Kadam
@jhenrique09
@SKULSHADY
Remember I am not a developer, if you are presenting any bugs let us know and you can contact the Havoc team on Telegram
I am not responsible for any damage caused to your device by not following the steps or negligence at the time of this process, All the steps were carried out and tested on my personal device and are confirmed, My device Redmi 8 3/32, the version that i tested Havoc-OS-v4.5-20210208-Official-arm64-ab.img.xz
Bugs
videos recorded with the default camera do not play
Update: Install the NGCam_7.4.104-v1.8-fix.apk Once the application is installed open it take a photo close the application, this will create a folder in the SD called Gcam, inside the Gcam folder create a folder and call it Config7 and inside this place the XML file Redmi 8 GCam 7.4.104.314953318 G_Modder.xml restart the application and you're done
the only bugs that have is slow motion record not work for now
Automatic brightness does not work
Update: to fix the automatic brightness on your device, after installing the ROM, put in the folder SYSTEM-OVERLAY the treble-overlay-xiaomi-redmi 8.apk and set the permission for the apk on 644 ( use root explorer ) and reboot ..... problem solved
the necessary files are at the end of the tutorial
Steps
Note: I did the installation coming from Mui 12.EU, and there was no problem in the installation process or in the boot process
If you come from Miui12 .EU or any other GSI Rom go to step 4, if you come from the Rom stock follow the this steps
1- First make a backup of all the necessary information in case something goes wrong you can easily recover, Charge the battery at least 80%
All your data will be deleted during the process
2- Unlock the Bootloader if you have not already done it or do not know how to, follow this post: http://en.miui.com/unlock/
3- Install a custon recovery, if you dont know how to, follow this post: https://c.mi.com/thread-2850424-1-0.html
4- Make wipe only to Cache, Dalvik, System, Data and Internal SD
5- Format data,( if it doesn't format the data you will have bootloop) then Reboot into Recovery
6- Copy all the files to the phone (Havoc-OS-v4.X-20200522-Official-arm64-ab.img you can find it by unpacking the zip), Magisk,Magisk Path Fix, Permisiver, Certification Patch.zip, opengapp (recommended nano or pico)
7- Install system image to system partition (on TWRP go to install-Install image-System) .
8- Flash Permisiver v5 (on TWRP go to install selec permisver_v5.zip)
9- Resize system partition to flash opengapps (on TWRP go to Wipe-Advanced Wipe-Select System on the list-Repair or Change File System-Resize)
To Root
once you have installed an resized the system
10- Flash the Magisk path fix (on TWRP go to install selec MagiskA11_PATH_fix.zip)
11- Flash Magisk (on TWRP go to install selec Magisk-v23.0.zip)
12- Flash Opengapps
1-Flash Certification Patch
1 - Make a wipe to Cache and Dalvik
1- Reboot
The boot process takes 5 to 10 minutes the first boot, in case of any problem in any of the stages you can reinstall Miui version fastboot with Mi flash tool and start again
Download link Rom image:
arm64-ab • Havoc-OS
Havoc-OS Downloads
download.havoc-os.com
OpenGapss Android 11: https://sourceforge.net/projects/opengapps/files/arm64/test/20210130/
Magisk:
Download Magisk Manager Latest Version 26.1 For Android 2023
Magisk Manager is an app which helps users to root their phone. With the help of Magisk you can run banking apps and also pass SafetyNet tests.
magiskmanager.com

Hey !
I have a stupid question. Do you upload the GSI ROM and the other files on a SD card or on the internal storage ? I was searching this guide on the morning but I was wondering about that...
Thanks for your answer

letouvetpierre said:
Hey !
I have a stupid question. Do you upload the GSI ROM and the other files on a SD card or on the internal storage ? I was searching this guide on the morning but I was wondering about that...
Thanks for your answer
Click to expand...
Click to collapse
Don't mind it, I haven't read all the article....

letouvetpierre said:
Hey !
I have a stupid question. Do you upload the GSI ROM and the other files on a SD card or on the internal storage ? I was searching this guide on the morning but I was wondering about that...
Thanks for your answer
Click to expand...
Click to collapse
You can place it in either of the two, as long as you can access the storage where you placed them from the recovery

D
letouvetpierre said:
Don't mind it, I haven't read all the article....
Click to expand...
Click to collapse
Dont worry

Darth Inferno said:
You can place it in either of the two, as long as you can access the storage where you placed them from the recovery
Click to expand...
Click to collapse
Okay thanks I think I will try this in the few days. Thanks for your guide !

Hey ! Do we need to flash a vbmeta image for Havocon boot ?
Is there any bugs when you install Havoc with TWRP ? 'cuz i'm a little bit experimented with TWRP but i'm shy with GSI...
Thanks for the answer

UPDATE :
I bricked my phone. When i arrived to the step 5 and i rebooted into fastboot (i would reboot into recovery...)
So, what can I do ? I installed MiFlashTool to unbrick my phone, if it can...
I tried to reboot from fastboot to twrp and this is what happened :
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.141s]
booting...
FAILED (remote: unknown reason)
finished. total time: 2.771s
Thanks...

letouvetpierre said:
UPDATE :
I bricked my phone. When i arrived to the step 5 and i rebooted into fastboot (i would reboot into recovery...)
So, what can I do ? I installed MiFlashTool to unbrick my phone, if it can...
I tried to reboot from fastboot to twrp and this is what happened :
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.141s]
booting...
FAILED (remote: unknown reason)
finished. total time: 2.771s
Thanks...
Click to expand...
Click to collapse
Hi, I need to know some things to help you, what ROM did you have before flashing Havoc? do you have the bootloader unlocked? When did you use My flashtool, what method did you use?

letouvetpierre said:
Hey ! Do we need to flash a vbmeta image for Havocon boot ?
Is there any bugs when you install Havoc with TWRP ? 'cuz i'm a little bit experimented with TWRP but i'm shy with GSI...
Thanks for the answer
Click to expand...
Click to collapse
In my particular case it was not necessary to flash vbmmeta as I comment in the OP I come from Miui12.eu, but it is necessary to avoid problems whatever the ROM you have before installing Havoc is to have the latest version of TWRP and have configured a lock pattern security in ROM access and in the flashing process I didn´t have problems

Hey!
I was on the stock ROM when i started to flash HavocOs.
I unbricked my phone with the MIUnlockTool V2 and my phone's still alive.
I booted on TWRP with fastboot boot TWRP.img 'cuz I can't boot to TWRP with volume up and power...
How can I flash HavocOs in the good way ?
I have Redmi 8 3/32 like you...

letouvetpierre said:
Hey!
I was on the stock ROM when i started to flash HavocOs.
I unbricked my phone with the MIUnlockTool V2 and my phone's still alive.
I booted on TWRP with fastboot boot TWRP.img 'cuz I can't boot to TWRP with volume up and power...
How can I flash HavocOs in the good way ?
I have Redmi 8 3/32 like you...
Click to expand...
Click to collapse
Ok the first thing is that you have the bootloader unlocked, if it is that way regardless of the stock version of the rom you have when installing twrp you must install magisk to ensure that the Recovery remains fixed in this link is a tutorial on how to install it, that tutorial was made by me and approved by Xiaomi https://c.mi.com/thread-2850424-1-0.html ,
install the latest version of TWRP and as it says in the tutorial then flash magisk, once you have everything ready install miui 12.eu do not do many settings except create a blocking pattern when starting the rom this is used by TWRP to be able to decrypt the internal memory
All ready do the steps as indicated in this tutorial (If you come from Miui12 .EU or any other GSI Rom go to step 4)
If for some reason you have a problem, use MI flashtool to return to the stock rom, but make sure to use the snapdragon method, select MIflash and when opening the screen at the bottom select clean all, this will prevent you from blocking the bootloader and you can start again without problems (note when selecting clean all at the end it will give you an error for not being able to block the bootloader and the device will restart, do not worry it will restart normally without problems)

Darth Inferno said:
Ok the first thing is that you have the bootloader unlocked, if it is that way regardless of the stock version of the rom you have when installing twrp you must install magisk to ensure that the Recovery remains fixed in this link is a tutorial on how to install it, that tutorial was made by me and approved by Xiaomi https://c.mi.com/thread-2850424-1-0.html ,
install the latest version of TWRP and as it says in the tutorial then flash magisk, once you have everything ready install miui 12.eu do not do many settings except create a blocking pattern when starting the rom this is used by TWRP to be able to decrypt the internal memory
All ready do the steps as indicated in this tutorial (If you come from Miui12 .EU or any other GSI Rom go to step 4)
If for some reason you have a problem, use MI flashtool to return to the stock rom, but make sure to use the snapdragon method, select MIflash and when opening the screen at the bottom select clean all, this will prevent you from blocking the bootloader and you can start again without problems (note when selecting clean all at the end it will give you an error for not being able to block the bootloader and the device will restart, do not worry it will restart normally without problems)
Click to expand...
Click to collapse
Hey!
I thought about something this afternoon : if I flash HavocOS with adb and fastboot, we also haven't any problems with TWRP installation ! But the problem is that I haven't found any wiki to do that and i won't transform my phone to a beta tester....
Thanks a lot for your help but I think i will wait until a custom rom of LineageOs or HavocOs...

Hi . I am currently running havoc is 3.12 on my device I tried multiple times to flash this ROM without any success. Is not installing open gapps a problem ? Anyways when I flash this rom without flashing the certification patch I get a no os installed warning before rebooting from orange fox recovery but when I flash the certification I no longer get this message. Etherway I am getting stuck on a bootloop . How can I solve this issue? I did all the steps correctly wiping the correct partitions and formating data . Edit I wiped cache and dalvik after the bootloop without any success .

Dragonnuu said:
Hi . I am currently running havoc is 3.12 on my device I tried multiple times to flash this ROM without any success. Is not installing open gapps a problem ? Anyways when I flash this rom without flashing the certification patch I get a no os installed warning before rebooting from orange fox recovery but when I flash the certification I no longer get this message. Etherway I am getting stuck on a bootloop . How can I solve this issue? I did all the steps correctly wiping the correct partitions and formating data . Edit I wiped cache and dalvik after the bootloop without any success .
Click to expand...
Click to collapse
Hey !
I had the same bug before installing the v3.12 version.
I think it goes from the Permissiver v5. I think we should flash it to have the Havoc v4.
I'll test later if I have the time to do this and I'll inform you about the possibilities.
Hope I can help.

letouvetpierre said:
Hey !
I had the same bug before installing the v3.12 version.
I think it goes from the Permissiver v5. I think we should flash it to have the Havoc v4.
I'll test later if I have the time to do this and I'll inform you about the possibilities.
Hope I can hel
Click to expand...
Click to collapse

Thanks for replying and trying to help but last night I managed to get havoc 4.1 is installed by flashing lineage first (using another guide from this category). I will try again to get havoc 4.1 working without flashing lineage as soon as posible because I am curious .

Used online available guides bit still not able to install magisk on Hovoc 4.1
Anyone succeeded?

mwaseem851 said:
Used online available guides bit still not able to install magisk on Hovoc 4.1
Anyone succeeded?
Click to expand...
Click to collapse
Magisk doesn't work on Android 11

letouvetpierre said:
Magisk doesn't work on Android 11
Click to expand...
Click to collapse
Finally managed to flash Magisk on Havoc 4.1 with the help of youtuberking (telegram and YouTube).
How: just flash Magisk path fix before magisk and it's good to go.

Could please somebody build a working TWRP build for me?

I need somebody to build me a working
TWRP build for the SM-A305N (Korea).
Every TWRP in XDA doesn't seem to work in my device, probably because they aren't for the A305N.
A week before, I finally found a 3.3.1 version TWRP build that works in my phone so I flashed it via odin, flashed magisk.zip, and rebooted successfully.
but after flashed an optimization file I found that the build doesn't support decrypting files, and it can't read the internal storage even though my device reboots into system normally and the files are all right in the file manager (files are shown as random characters in twrp)
Please, could somebody make a working TWRP build for A305N?
+Q. Can a Disable-dm verity file brick my device?

I made a password as a security lock system on my phone, but when I booted to twrp it didn't ask for a password. (Also with PIN)
Also, when I typed
"twrp decrypt MyPassword"
(MyPassword is the password I put on my device)
TWRP said that decrypting files wasn't installed on this build of TWRP.

sycall2847 said:
I need somebody to build me a working
TWRP build for the SM-A305N (Korea).
Every TWRP in XDA doesn't seem to work in my device, probably because they aren't for the A305N.
A week before, I finally found a 3.3.1 version TWRP build that works in my phone so I flashed it via odin, flashed magisk.zip, and rebooted successfully.
but after flashed an optimization file I found that the build doesn't support decrypting files, and it can't read the internal storage even though my device reboots into system normally and the files are all right in the file manager (files are shown as random characters in twrp)
Please, could somebody make a working TWRP build for A305N?
+Q. Can a Disable-dm verity file brick my device?
Click to expand...
Click to collapse
Hi
Download twrp 3.3.1.0.tar and flash with odin
Then download twrp 3.4.0.img or 3.5.1.img and install by twrp
And remember mount system

Could you plz explain steps more specifically

DOES THIS REALLY WORK ON MY GALAXY A30? Thanks bro

Yes. Work for me

sycall2847 said:
Could you plz explain steps more specifically
Click to expand...
Click to collapse
1. Download twrp 3.3.1.0.tar
2. Flash this file with odin ( get help with google)
3.turn off your phone
4.hold power and volume up keys for going to twrp
5.go to mount and tick system
6. Install twrp 3.4.0.img from install on twrp
Reboot recovery and you see twrp 3.4 installed on your phone

OK thanks Umm.. TWRP 3.3.1 is already flashed in my device (It cant read internal storage). Should I first flash the stock recovery img with odin before flashing 3.3.1 again ir should I just flash the 3.3.1 again?

Mozaffar1994 said:
1. Download twrp 3.3.1.0.tar
2. Flash this file with odin ( get help with google)
3.turn off your phone
4.hold power and volume up keys for going to twrp
5.go to mount and tick system
6. Install twrp 3.4.0.img from install on twrp
Reboot recovery and you see twrp 3.4 installed on your phone
Click to expand...
Click to collapse
After rebooting to TWRP 3.4, What should I do next? Should I flash the magisk zip?

Can I just flash the TWRP 3.4 file by flashify or TWRP official app? Will current TWRP be replaced with it?

sycall2847 said:
Can I just flash the TWRP 3.4 file by flashify or TWRP official app? Will current TWRP be replaced with it?
Click to expand...
Click to collapse
If work ,do it

If what works??

sycall2847 said:
If what
Click to expand...
Click to collapse
I installed as I said before.
I do not know of other methods.
Sorry

Mozaffar1994 said:
1. Download twrp 3.3.1.0.tar
2. Flash this file with odin ( get help with google)
3.turn off your phone
4.hold power and volume up keys for going to twrp
5.go to mount and tick system
6. Install twrp 3.4.0.img from install on twrp
Reboot recovery and you see twrp 3.4 installed on your phone
Click to expand...
Click to collapse
This is how i installed TWRP on my A305F