Database Users

[Fix] Permanent Chinese CWM

Hello
well i also faced this issue,if ur not aware of it then let me explain a liitle.. if you have upgraded to the latest version via OTA then there are some patch files in the system which do this trick.. so in order to get permanent recovery if u flashed it via ur phone with apps like flashify or recovery tools then you need to go to
System and there you will see a file with name Recoveryfromboot.p just delete that file and flash chinese cwm and ur done :]
btw i'll try to build the english cwm as soon as i get some free time.. thanx to burakgon for releasing the kernel sources..

Thanks simmer14, works perfectly after removing that file from system. So that confirms it's not bootloader lock issue. No idea why custom kernels and twrp not working then?

1manshow said:
Thanks simmer14, works perfectly after removing that file from system. So that confirms it's not bootloader lock issue. No idea why custom kernels and twrp not working then?
Click to expand...
Click to collapse
i will build the cwm for our phone but i'm not getting any time to sit in front of my pc :'(
edit :
custum kernels are not working ? did you tried to compile one from the sources ? or the sources are not complete ?

I didn't tried to compile anything, but some guys did here -
http://forum.xda-developers.com/showthread.php?t=2712586
If you want, you can take a look there and contribute in your own way to resolve the issue. Thanks for your efforts so far though.

[RECOVERY][KANG] TWRP 3.0.2 recovery for u8800pro/u8860

Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOGS
Changelogs can be found from TeamWin site TeamWin - TWRP
BUGS:
- No off mode charging, boots straight in to recovery.
INFORMATION:
- Supports the f2fs file system.
2016-05-10
- TWRP version 3.0.2-0
2016-02-06
- TWRP version 3.0.0-1
2015-12-10
- TWRP version 2.8.7.0
2014-10-26
- TWRP version 2.8.1.0
2014-10-15
Today (2014-10-15) I announce a build with F2FS support, today's and upcoming build's will have support for F2FS file system. Read more about F2FS from post #18.
DOWNLOAD:
For u8800pro
Stable:
TWRP_2.8.1.0-20141026-u8800pro.zip
Unstable:
TWRP_3.0.2-0-u8800pro.zip
TWRP_3.0.0-1-u8800pro.zip
TWRP_2.8.7.0-20151210-u8800pro.zip
For u8860
TWRP_2.8.1.0-20141026-u8860.zip
Looking for the u8800 version?
It can be found here: [RECOVERY] TWRP 2.8.1.0 recovery for u8800.
Big thanks to @Dees_Troy, @bigbiff and @Captain_Throwback. Also I want to thank you @desalesouche from his help.

Thanks Lihis and everyone else, I'm glad you are still supporting this device Thumbs up!

CrysisLTU said:
Thanks Lihis and everyone else, I'm glad you are still supporting this device Thumbs up!
Click to expand...
Click to collapse
Thanks and thanks to you and other dev's who was part of this forum, you have made a job which can't be forgotten!

Great. This must be a record. Not so famous device, still getting superb support from devs. Lets see what happens to Android L.

It seems that I must be doing something wrong.
I am using TWRP manager to install the recovery img
choose the downloaded img from the SD card
but when I try to install I get a WARNING that says
1><p> The requested URL /install_command/ was not found on this server. </p>
any idea what I am doing wrong.
obviously rebooting into recovery mode does not work

Greekguy74 said:
It seems that I must be doing something wrong.
I am using TWRP manager to install the recovery img
choose the downloaded img from the SD card
but when I try to install I get a WARNING that says
1><p> The requested URL /install_command/ was not found on this server. </p>
any idea what I am doing wrong.
obviously rebooting into recovery mode does not work
Click to expand...
Click to collapse
I have not never used TWRP manager so I do not have experience with it. I suggest you to use pink screen to replace the recovery.

Lihis said:
I have not never used TWRP manager so I do not have experience with it. I suggest you to use pink screen to replace the recovery.
Click to expand...
Click to collapse
I have access to the pink screen, but it seems it is locked and don't have access to the internal storage.
I suppose I need some custom bootloader for that. Any ideas which is appropriate for the B928 version I am using from Huwaie ?
and once I get access to the internal storage where do I place the new recovery image ?
thanks in advance for all the help.

Greekguy74 said:
I have access to the pink screen, but it seems it is locked and don't have access to the internal storage.
I suppose I need some custom bootloader for that. Any ideas which is appropriate for the B928 version I am using from Huwaie ?
and once I get access to the internal storage where do I place the new recovery image ?
thanks in advance for all the help.
Click to expand...
Click to collapse
Yes, you need unlocked bootloader, take a look in here: Official ICS 4.0.3 V100R001C00B928 with unlock pink screen. When you boot your phone to pink screen the recovery can be found from "image" folder.

Lihis said:
Yes, you need unlocked bootloader, take a look in here: Official ICS 4.0.3 V100R001C00B928 with unlock pink screen. When you boot your phone to pink screen the recovery can be found from "image" folder.
Click to expand...
Click to collapse
I tried those instructions and they don't seem to work.
If I attempt it from the normal recovery screen I get a
Code:
update package;s ext name error
E:ota_pre_update error
Maybe will try to flash everything ie reinstall B928 as well and not just try to unlock the pink screen.
Will keep you posted.

Greekguy74 said:
I tried those instructions and they don't seem to work.
Click to expand...
Click to collapse
What is the error? No, you cannot flash the update.app via recovery.

Lihis said:
What is the error? No, you cannot flash the update.app via recovery.
Click to expand...
Click to collapse
If I try to flash outside the recovery it fails and in dload directory the sd_update.log says
Code:
dload_sd_ram_data_proc->(retry >= DLOAD_RETRY) failed!
I formattted the SD card but that was not the problem.
Interestingly enough if I try to flash with the official Huawei ROMs same thing happens. I am bit at a loss

Greekguy74 said:
If I try to flash outside the recovery it fails and in dload directory the sd_update.log says
Code:
dload_sd_ram_data_proc->(retry >= DLOAD_RETRY) failed!
I formattted the SD card but that was not the problem.
Interestingly enough if I try to flash with the official Huawei ROMs same thing happens. I am bit at a loss
Click to expand...
Click to collapse
In that case unfortunately I can't help you much but you can't flash update.app via recovery, they must be applied via "force update" method which is that dload thing or via stock rom "update" option. You don't have a recovery or a OS now? One thing you can test is to take off the battery and power your phone with USB cable only to apply the update.app, I have heard it helped someone's.
btw, why you didn't unlocked your pink screen in the first place when you upgraded to ICS?

Lihis said:
In that case unfortunately I can't help you much but you can't flash update.app via recovery, they must be applied via "force update" method which is that dload thing or via stock rom "update" option. You don't have a recovery or a OS now? One thing you can test is to take off the battery and power your phone with USB cable only to apply the update.app, I have heard it helped someone's.
btw, why you didn't unlocked your pink screen in the first place when you upgraded to ICS?
Click to expand...
Click to collapse
At the moment my phone works fine with the stock 4.0.3 official android version from Huawei after I managed to replace the bootloader.
I tried without the battery and just the USB cable still no joy.
As for the why I did not unlock it, good question. At the time cyanogenmod was behind ver 4.0.3 for my phone so decided to stick with the official ROM and then to be frank I forgot about it.
I will contact the TWRP manager devs to see if they can fix their app so it applies TWRP without the need for going through the pink screen.

Greekguy74 said:
At the moment my phone works fine with the stock 4.0.3 official android version from Huawei after I managed to replace the bootloader.
I tried without the battery and just the USB cable still no joy.
As for the why I did not unlock it, good question. At the time cyanogenmod was behind ver 4.0.3 for my phone so decided to stick with the official ROM and then to be frank I forgot about it.
I will contact the TWRP manager devs to see if they can fix their app so it applies TWRP without the need for going through the pink screen.
Click to expand...
Click to collapse
Good! Try eg. with RootExplorer to replace the recovery.img. It can be found from /.cust_backup/image

Lihis said:
Good! Try eg. with RootExplorer to replace the recovery.img. It can be found from /.cust_backup/image
Click to expand...
Click to collapse
I did just that and now the phone is in even bigger trouble.
When I boot it it says
Code:
Image signature verify fail!
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one.
You can remove battery for power down.
USB in pink screen mode is not functioning and it seems I cannot flash with any of the official ROMs (which is VERY weird since I did update the phone to 4.0.3 at some point in the past).
:crying:

Greekguy74 said:
I did just that and now the phone is in even bigger trouble.
When I boot it it says
Code:
Image signature verify fail!
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one.
You can remove battery for power down.
USB in pink screen mode is not functioning and it seems I cannot flash with any of the official ROMs (which is VERY weird since I did update the phone to 4.0.3 at some point in the past).
:crying:
Click to expand...
Click to collapse
Ouch.. This is hard situation :/ sometimes I really hate Huawei.. Adb is not accessible in any point? So you can't push files to device?

Lihis said:
Ouch.. This is hard situation :/ sometimes I really hate Huawei.. Adb is not accessible in any point? So you can't push files to device?
Click to expand...
Click to collapse
adb is not accessible but fastboot seems that it is. even though I cannot flash anything since they are locked.

Support for F2FS file system
Added support for F2FS file system.
What is F2FS file system?
F2FS (Flash-Friendly File System) file system is a flash file system initially developed by Samsung Electronics for the Linux operating system kernel (source). Here is some benchmark made with Xperia Z1 [Benchmarks] File System Performance: F2FS vs EXT4.
For now there is no ROM which uses F2FS file system but in future there may be.

Lihis said:
Added support for F2FS file system.
What is F2FS file system?
F2FS (Flash-Friendly File System) file system is a flash file system initially developed by Samsung Electronics for the Linux operating system kernel (source). Here is some benchmark made with Xperia Z1 [Benchmarks] File System Performance: F2FS vs EXT4.
For now there is no ROM which uses F2FS file system but in future there may be.
Click to expand...
Click to collapse
Found one bug with f2fs its fail in restore f2fs system backup data and cache are ok.
If you need you need f2fs backup just backup your current rom
Then rename and replace every "ext4" with f2fs.

mohammad.afaneh said:
Found one bug with f2fs its fail in restore f2fs system backup data and cache are ok.
If you need you need f2fs backup just backup your current rom
Then rename and replace every "ext4" with f2fs.
Click to expand...
Click to collapse
Thanks! Are you working a F2FS enabled rom?

Need help with Android N Preview 2

Hi Guys, i have a little Problem.
i installed the Android N Preview 2, and now i wanna install TWRP-Recovery.
Latest 3.0.2-0 dont work, so i installed the 2.8.7.0 and this works, but i cannot connect in twrp to storage.
so that i can flash the root.zip
i enter the passwort for decrypt data but nothing happends, and after every boot i need to flash twrp again ?
May anybody can help me?
Regards,
Taker

To gain root on N preview 2, use the auto root kit. Just run the .bat file and your good.
http://www.droidviews.com/root-android-n-developer-preview-cf-auto-root/

Taker18 said:
Hi Guys, i have a little Problem.
i installed the Android N Preview 2, and now i wanna install TWRP-Recovery.
Latest 3.0.2-0 dont work, so i installed the 2.8.7.0 and this works, but i cannot connect in twrp to storage.
so that i can flash the root.zip
i enter the passwort for decrypt data but nothing happends, and after every boot i need to flash twrp again ?
May anybody can help me?
Regards,
Taker
Click to expand...
Click to collapse
Encrypted N environment is having issues with TWRP, it either fails to boot into recovery or decryption doesn't work. The best thing you could do here is, decrypt your internal storage entirely.
Once you have decrypted, TWRP will be fully operational, and you can flash the latest SuperSU via recovery itself.
Here is the link: https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
And yeah, you can flash back 3.0.2-0, it will work perfectly after decryption. :highfive:

DJBhardwaj said:
Encrypted N environment is having issues with TWRP, it either fails to boot into recovery or decryption doesn't work. The best thing you could do here is, decrypt your internal storage entirely.
Once you have decrypted, TWRP will be fully operational, and you can flash the latest SuperSU via recovery itself.
Here is the link: https://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
And yeah, you can flash back 3.0.2-0, it will work perfectly after decryption. :highfive:
Click to expand...
Click to collapse
Thanks for your always wick answers, but now i need to go back to 6.0.1, as there are many apps not working on Android N
Now, lets see why beanstalk is not showing sim again, will make an logcat and maybe you can look into it?
Regards,
Taker

Taker18 said:
Thanks for your always wick answers, but now i need to go back to 6.0.1, as there are many apps not working on Android N
Now, lets see why beanstalk is not showing sim again, will make an logcat and maybe you can look into it?
Regards,
Taker
Click to expand...
Click to collapse
You're welcome.Yeah, the apps are currently a concern until the full SDK comes out. Now since Android Studio supports N, we might see app-compatibility issues resolve fast.
Yeah, do give a check. Mind linking me to Beanstalk thread for 6P? I have been out of the development scene since a long time, but yeah, I will surely look at it.

DJBhardwaj said:
You're welcome.Yeah, the apps are currently a concern until the full SDK comes out. Now since Android Studio supports N, we might see app-compatibility issues resolve fast.
Yeah, do give a check. Mind linking me to Beanstalk thread for 6P? I have been out of the development scene since a long time, but yeah, I will surely look at it.
Click to expand...
Click to collapse
check your pm

[RECOVERY] how to install TWRP 3.1.1 on J330F/G/FN

how to install TWRP 3.1.1 on Samsung Galaxy J3 2017
-------------------------------------------------
J330F--OK!
J330G--OK!
J330FN--OK!
-------------------------------------------------
TWRP for j330 3.1.1-1 by Lemlis
-------------------------------------------------
FULL STEPS TO INSTALL TWRP
DO THIS AT YOUR OWN RISK. I AND XDA AND NOT RESPONSIBLE FOR BRICKS. FOLLOW THE STEPS CORRECTLY.
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
NOTE: IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
1-Download TWRP :twrp3.1.1-1_J330.tar
2-Download no-verity-opt-encrypt-5.1.zip and put it on SD, external memory of the phone in any folder
3-Flash twrp3.1.1-1_J330.tar with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
4- For the full work of the recovery need to make the format of the data section.(WIPE-format data-yes) (Warning: all your data and applications on the phone (not the SD card) will be deleted)
5-MANDATORY !!! reboot again in the recovery and install the script no-verity-opt-encrypt-5.1.zip
Congratulations! already quietly go to make backups, sewing firmware and in general anything you like
-------------------------------------------------
Download:
twrp3.1.1-1_J330.tar
twrp3.1.1-1_J330.img
no-verity-opt-encrypt-5.1.zip
-------------------------------------------------
To root with SuperSU:
Download the latest SuperSU by Chainfire,or Magisk
Flash it through TWRP.
Go to [Reboot] -> [System].​--------------
opensource.samsung.com j330f
--------------
Credits:
@ashyx
@AlexVolzsk

...reserved

Succesfully installed to my j330g & enter to recovery but touch screen not working without mouse as mentioned by developer. Must wait for another stable version...aaarghhh need to flash stock rom again:crying::crying: btw thanks to mr developer for their efforts & hopefully can release stable version as soon as possible.

hi from j330fn boot from recvovery twrp but touchscreen dont work .. you can not use it but thanks this way is good

This is great! I'll be even happier when touchscreen is available.

LeeTG3 said:
This is great! I'll be even happier when touchscreen is available.
Click to expand...
Click to collapse
so why is it so unusable

ANDROIDXFOREVER said:
so why is it so unusable
Click to expand...
Click to collapse
You can use this TWRP only with mouse through the OTG cable.
In the near future I will try to fix it

I never said it was unusable. But I don't have an otg cable

LeeTG3 said:
I never said it was unusable. But I don't have an otg cable
Click to expand...
Click to collapse
I followed your advice and I solved you confirm twrp works perfectly on j330fn thanks waiting for update:good:

lemlis said:
TWRP 3.1.1-2 J330 Aroma
-Touch screen does not work! You can only use with the mouse through the OTG cable!
Changes:
-added items in the backup and mount section
-fixed small bugs
-In the Aroma, the mouse does not work, but you can select items using the volume and power buttons
Click to expand...
Click to collapse
Boss, please make touch screen working as well...i know you can do it...tq

@lemlis are twrp and the kernel both built from source?

ashyx said:
@lemlis are twrp and the kernel both built from source?
Click to expand...
Click to collapse
Twrp is ported .kernel is custom build from source.with stok kernel not work mount sd card.

Anual said:
please make touch screen working as well...i know you can do it...tq
Click to expand...
Click to collapse
here is TWRP with working touch screen

lemlis said:
here is TWRP with working touch screen
Click to expand...
Click to collapse
thanks bro from j330fn work perfect :good::good:

lemlis said:
here is TWRP with working touch screen
Click to expand...
Click to collapse
I'm 2 hours late..download link temporary removed hahaha..btw thanks.

I've downloaded twrp you attached here but the extension is .img which odin cannot read this type. I try to convert this image file to .tar and still fail to flash. Any suggestion?

Anual said:
extension is .img which odin cannot read this type. Any suggestion?
Click to expand...
Click to collapse
I aded link to .tar and to .img

Thank you very much bro...it's working???

Anual said:
I'm 2 hours late..download link temporary removed hahaha..btw thanks.
Click to expand...
Click to collapse
It will be back up later on today.
Keep an eye on this thread.
https://forum.xda-developers.com/ga...overy-twrp-3-1-1-1-samsung-galaxy-j3-t3709056

Arggghh i feel something goes wrong with my device intead of succesfull installation. Yes i can flash zip and make nandroid backup. But my device not running properly. I can't adjust screen brightness even camera not functioning. Now i'm waiting for full batery charge to flash stock rom & try to flash twrp once again???

[SOLVED] Phone gets stuck in bootloop if I try to install Magisk ZIP!

From the forum I followed these step to install magisk:
- Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot
- After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally
- After booting up installed Magisk Manager and both Magisk and Magisk manager shows green tick (installed)
But at this stage, whenever I open Magisk, it shows a recommendation to install a ZIP, if I agree to install it, phone gets stuck in recovery again.
If I choose not to install recommended zip and click Install > Direct Install, phone gets stuck in recovery again anyway
Everytime it gets stuck I have to wipe all data and start all over again. Anyone else facing same issue? Any solution?
Really frustrated right now.
My current rom is : DAVINCIIN INDIAN Global_V11.0.2.0
Used latest magisk manager 7.4.0
I have official recovery, not TWRP.
Afraid that flashing TWRP now will brick it for good.
UPDATE: Got the solution here, thanks @pikchu289 !

Twrp up to now is the best way
But check some stuff first
1.unlock the boot loader
2.chech if the magisk zip/img is corrupted or any file
3.does your os support this magisk version
Any way you can flash twrp because many people had already tried it and tested it from installing zips/ROMs/mods etc.. to backup files/data or even fixing some corrupted files that caused boot loops manually
But there are various things that doesn't work usually such as restoring system partition but never worry about this because if any thing failed just use miflash tool to go back to official/stock rom
Edit : I think something's wrong with your magisk version number

I have no idea which rom youre using or why on earth you didn't install TWRP before messing around with the os but some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch

Solve this solution
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389

pikchu289 said:
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
Finally someone with an answer!
Thanks... Will try and see if it works...
UPDATE: IT WORKED!

Aserar said:
I have no idea which rom youre using
Click to expand...
Click to collapse
Maybe I should've used font size 72 while writing the rom I'm using above.
Aserar said:
why on earth you didn't install TWRP before messing around with the os
Click to expand...
Click to collapse
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
Aserar said:
some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch
Click to expand...
Click to collapse
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-

It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
stone_henge said:
Maybe I should've used font size 72 while writing the rom I'm using above.
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-
Click to expand...
Click to collapse

Aserar said:
It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
Click to expand...
Click to collapse
Sorry for being harsh... I understand you actually tried to help. It's actually really frustrating when facing a problem that has no straightforward solution.
Sorry mate.

finally i founded how to fix this issue without formating data of ur device
--just the flash the same the full custom rom or stock rom that u r using currently on . and boom restart. and ur issue fixed

Install a magisk zip without TWRP. TWRP takes too long. Instead use Aodin to flash a rom specific to your device version. Make sure it is not corrupted as well