Develop Bugs

Xperia S LT26I- nAOSProm_b26 Cannot Flash Gapps in TWRP

Gapps not Installing
Hi,
I installed custom rom nAOSProm_b26 with TWRP 2.8.5 on my Xperia S LT26i and now am having a problem.
The problem is that its not showing Play Store. I searched and found maybe its due to Gapps. I tried many packages of Gapps.zip but not successful. Also its saying the kernel does not have support SELINUX in start.
Please Help me in this regard will be very thankful as am new to this field and don't know much about this
Thanking in Advance...!!!

haris05 said:
Hi,
I installed custom rom nAOSProm_b26 with TWRP 2.8.5 on my Xperia S LT26i and now am having a problem.
The problem is that its not showing Play Store. I searched and found maybe its due to Gapps. I tried many packages of Gapps.zip but not successful. Also its saying the kernel does not have support SELINUX in start.
Please Help me in this regard will be very thankful as am new to this field and don't know much about this
Thanking in Advance...!!!
Click to expand...
Click to collapse
You need to flash gapps after flashing a ROM. Since You are on nAOSP b26, Your android version is 5.1 . Search for gapps package which works with 5.1 and the flash them via recovery. Also as for Your error, I would recommend a clean flash by following the instructions by the developer.

Mirhawk said:
You need to flash gapps after flashing a ROM. Since You are on nAOSP b26, Your android version is 5.1 . Search for gapps package which works with 5.1 and the flash them via recovery. Also as for Your error, I would recommend a clean flash by following the instructions by the developer.
Click to expand...
Click to collapse
I download Gapps for 5.1 but issue is I can install nAOSProm_b26 using TWRP 2.8.5 but cannot install it using TWRP 2.8.7.
On other hand I can install Gapps usinng TWRP 2.8.7 but cannot install it using TWRP 2.8.5
So many complex things are going on with me
One more thing I want to know that what do you mean by flash it via recovery. Is it boot.img in the ROM.zip file?
I followed the instructions but each time I failed Do not know why
Can you please help me further in this regard?

You have to say clearly step by step what you have did to flash the ROM or gapps.then only some1 can help you

same problem here!
i can flash gapps but the problem is after the boot and android upgrade all google apps pop up for unfortunately stopped and setup wizard also..

haris05 said:
I download Gapps for 5.1 but issue is I can install nAOSProm_b26 using TWRP 2.8.5 but cannot install it using TWRP 2.8.7.
On other hand I can install Gapps usinng TWRP 2.8.7 but cannot install it using TWRP 2.8.5
So many complex things are going on with me
One more thing I want to know that what do you mean by flash it via recovery. Is it boot.img in the ROM.zip file?
I followed the instructions but each time I failed Do not know why
Can you please help me further in this regard?
Click to expand...
Click to collapse
See, b25 onwards different mode has been followed in the nAOSP ROM. For that, You need to flash the recovery from the ROM.zip. Then flash the boot.img from the b26 zip via bootloader, and then flash the ROM. Are You following this sequence?
Also it doesn't matter what TWRP version You are using to flash gapps. You can always change the TWRP version. So flash the the TWRP with which ever TWRP version it gets flashed with, then change the TWRP if You want to, and then flash the gapps.
Flash it via recovery means flash it via TWRP. TWRP, CWM, Philz, these all are recoveries used to flash flashable zips via it.
The one You took example of, boot.img, is generally the kernel, which needs to be flashed via bootloader mode.
Also, I would recommend these gapps, they always worked for Me.
bojz said:
same problem here!
i can flash gapps but the problem is after the boot and android upgrade all google apps pop up for unfortunately stopped and setup wizard also..
Click to expand...
Click to collapse
Try the gapps I linked above.

Mirhawk is always a life saver for all new Comer's.

Mirhawk said:
Try the gapps I linked above.
Click to expand...
Click to collapse
thanks but still got no luck

nageswarswain said:
Mirhawk is always a life saver for all new Comer's.
Click to expand...
Click to collapse
Just helping out in whatever I can.
bojz said:
thanks but still got no luck
Click to expand...
Click to collapse
That is weird, Can You tell what problem You are facing? Mention the error text if You can. Also, You can try these TK Gapps.

Mirhawk said:
That is weird, Can You tell what problem You are facing? Mention the error text if You can. Also, You can try these TK Gapps.
Click to expand...
Click to collapse
already tried tha gapps also still the samw problem.
all google application was error popping out "unfortunately (google maps, google+ ,etc..) has stopped
then i already reset it in the (setting-application-all) but the setup wizard was not fixed and still popping out and i cannot get on the home screen.

bojz said:
already tried tha gapps also still the samw problem.
all google application was error popping out "unfortunately (google maps, google+ ,etc..) has stopped
then i already reset it in the (setting-application-all) but the setup wizard was not fixed and still popping out and i cannot get on the home screen.
Click to expand...
Click to collapse
Have u followed the procedure I sent you by message

Mirhawk said:
See, b25 onwards different mode has been followed in the nAOSP ROM. For that, You need to flash the recovery from the ROM.zip. Then flash the boot.img from the b26 zip via bootloader, and then flash the ROM. Are You following this sequence?
Also it doesn't matter what TWRP version You are using to flash gapps. You can always change the TWRP version. So flash the the TWRP with which ever TWRP version it gets flashed with, then change the TWRP if You want to, and then flash the gapps.
Flash it via recovery means flash it via TWRP. TWRP, CWM, Philz, these all are recoveries used to flash flashable zips via it.
The one You took example of, boot.img, is generally the kernel, which needs to be flashed via bootloader mode.
Also, I would recommend these gapps, they always worked for Me.
Try the gapps I linked above.
Click to expand...
Click to collapse
I guess am skipping one step of recovery.... gonna try that.

I did flash by using recovery and now I am successful in installing gapps using TWRP 2.8.5.
Now the other issue am facing and that is of unknown IMEI
after flashing 4-5 times the issue resolved but now am facing issue "Unfortunately Setup Wizard has stopped" and it is not letting me do anything with my phone
Any Suggestion what should I do now

bojz said:
same problem here!
i can flash gapps but the problem is after the boot and android upgrade all google apps pop up for unfortunately stopped and setup wizard also..
Click to expand...
Click to collapse
exactly the same problem I am facing

bojz said:
already tried tha gapps also still the samw problem.
all google application was error popping out "unfortunately (google maps, google+ ,etc..) has stopped
then i already reset it in the (setting-application-all) but the setup wizard was not fixed and still popping out and i cannot get on the home screen.
Click to expand...
Click to collapse
The same thing exactly
Got Any solution to that?

haris05 said:
The same thing exactly
Got Any solution to that?
Click to expand...
Click to collapse
Can You use the b25b version? It is what I'm on now and it works just fine for Me. There are no major updates in b26 as it is.

only in this nAOSP b26 rom im facing this problem "system wizard has stopped" after installing gapps. but i tried other rom then i dont have any problem.

Mirhawk said:
Can You use the b25b version? It is what I'm on now and it works just fine for Me. There are no major updates in b26 as it is.
Click to expand...
Click to collapse
Let me try this now

Mirhawk said:
Can You use the b25b version? It is what I'm on now and it works just fine for Me. There are no major updates in b26 as it is.
Click to expand...
Click to collapse
Cannot flash using this ROM. Its giving error on installing

These Steps am Following:
1) Connected Phone on flashboot mode (By Pressing VolUp+Power Key and connecting the cable and it shows blue LED)
2) Flashed with recovery.img file in nAOSProm_b26 using flashtool (Fastboot mode)
3) Flashed with boot.img file in nAOSProm_b26 using flashtool (Fastboot mode)
4) flashed with TWRP 2.8.5 using flashtool (Fastboot mode)
5) disconnected cable and open bootloader then flashed using nAOSProm.zip file
6) wipe cache and dalvik (also treid by wiping cache/dalvik/data and other option I forgot (total 4))
7) flashed using pa_Gapps (as only this Gapps are flashed on my phone, others are giving errors)
same I followed for b25b but its giving error on 5th step mentioned above.
So what wrong am doing

SM-T700 Bootloop after flash of customrom, again and again

Hallo everybody, greetings from germany.
I would need some support from you guys on a bootloop case for the sm-t700. I searched my ass off in google and xda but could not find a solution.
So now after hours of trying it myself I like to ask for help.
In the following I will describe what I have done to come to this point including everything I installed etc.
The stock rom was lollipop 5.0.2 and already installed.
- usb debug mode on
- flashed via odin v.3.10.7 supersu "cf-autoroot-twrp-t700.tar"
- forgot to install busybox and rootchecker for verifying root.
- backup of IMEI/EMFS (data is now on pc)
- in recovery backup of Boot.img
- wipe data/cache/dalwik/system in one go
- flashed "Euphoria-OS-1.1-klimtwifi-UNOFFICIAL-20150812.zip"
"open_gapps-arm-5.1-pico-20151013.zip"
"SkyHigh_SM-T700_kernel_TW-LL_v2.0.zip"
- rebooted and waited up to 15 - 20 min. Stopped waiting after that.
the regular samsung logo while booting shows up in intervalls from 5 to 10 minutes.
Next I wanted to do it better by installing busybox and cheking for root, because
I thought first that this could be the main cause for the bootloop.
- downloadmode
- flashed succesfully "T700XXU1BOE5_T700DBT1BOD1_HOME.tar.md5" via odin v.3.10.7 to get to stockrom again
- usb debug mode on
- downloadmode
- flashed via odin v.3.10.7 supersu "cf-autoroot-twrp-t700.tar"
- verifyied it with rootvalidator
- installed busybox
- deleted all knox stuff
- installed twrp app to get to v.2.8.7.0
- recoverymode
- backup of everything
- wipe data/cache/dalwik/system
- flashed "Euphoria-OS-1.1-klimtwifi-UNOFFICIAL-20150812.zip"
"open_gapps-arm-5.1-pico-20151013.zip"
"SkyHigh_SM-T700_kernel_TW-LL_v2.0.zip"
- rebooted and waited up to 15 - 20 min. Stopped waiting after that.
the regular samsung logo while booting shows up in intervalls again from 5 to 10 minutes.
Next I went into recovery and restored everything as before the flash of the customrom.
This happens in the same way with blisspop and liquidsmooth roms.
Hope anyone knows something.

Youve flashed an aosp rom , but attempting to boot with a stock based kernel.
Its never advisable to multi flash. Flash after each successful boot.
You need to flash the kernel provided in that thread or flash the whole rom again.
Also make sure your bootloader is up to date.
Tbh I'd wipe and start again.

ashyx said:
Youve flashed an aosp rom , but attempting to boot with a stock based kernel.
Its never advisable to multi flash. Flash after each successful boot.
Click to expand...
Click to collapse
By "multi flash" do you mean the install procedure in twrp that automates the installation procedure? (add zip)
And how am I able to flash after each successful boot if there is nothing to boot left after wipe?
ashyx said:
You need to flash the kernel provided in that thread or flash the whole rom again.
Click to expand...
Click to collapse
I thought this Kernel would be great. So you do not recommend me to use it?
I will look up the roms now and the kernel they use.
ashyx said:
Also make sure your bootloader is up to date.
Tbh I'd wipe and start again.
Click to expand...
Click to collapse
How do I do this or if already up to date where do I can look it up?

According to your post you flashed rom, gapps and kernel in one go.
Any one of those could have caused a bootloop or hang.
As for SkyHigh kernel, it is a great kernel but probably not suitable for an aosp rom as it's built from stock sources intended for stock roms.
Use the kernel provided.
To update the bootloader flash the latest firmware or pull it out and flash it separately.

Okay I will do the following now.
First find the appropiate Kernel if Skyhigh is a nogo. sadly.
Then flash in recovery at first the kernel of the rom. boot. recovery, flash the customrom + gapps. Right?
And before all that flash a new bootloader.
Further, is there a Kernel beside the one of the roms that you would recommend me?

Just wipe data and cache in recovery then flash just the rom. It probably already has the kernel.
Don't flash gapps just reboot after flashing the rom.

ashyx said:
Just wipe data and cache in recovery then flash just the rom. It probably already has the kernel.
Don't flash gapps just reboot after flashing the rom.
Click to expand...
Click to collapse
Okay worked well.
Left out the kernel because I could not find any custom ones.
Now I have euphoria on it and want to change between blisspop and liquidsmooth until I have the one I like most.
It is kinda hard to get the difference. I just know that euphoria and liquid are faster, smoother?
Thanks a lot without your input I would still be searching for an answer.
Happy day to you.

skyhigh and iron kernel are mean for touchwiz. Its not mean for cyanogen/aosp/aokp.
currently there is no one cook a custom kernel for cyanogen/aosp/aokp rom. so we stuck with the kernel that come with the rom.

Kernels :
https://www.androidfilehost.com/?w=files&flid=37193

Okay, did not know about this kernel.could you give me some info about the "deathly signed"?
My browser here is not loading the xda thread where I found people talking about it.

Failed install of Android 7.1.2 - boot stuck on "Android"

I had CWM Recovery and an older cyanogenmod rom installed and I wanted to upgrade to 7.1.2 from here: https://forum.xda-developers.com/lg.../rom-android-7-0-nougat-20161008-r16-t3476750
I copied the rom to internal memory, rebooted into recovery, selected the rom file to install. It showed some messages about patching, then in a couple of minuted erred with smth like "Erro loki-ifying because of incompatible aboot image".
I then rebooted and now it boots and shows "ANDROID" and is stuck on it - looks like it partially updated the ROM and failed somewhere.
I am not sure what to do now - I tried to boot into recovery (Power off -> Hold Power + Vol down till menu shows) but it doesnt work - it keeps booting onto this stuck boot.
Any ideas?

As I understand it, being an amateur ROM flasher, all those 3rd party ROMs need a TWRP recovery to work. Provided your bootloader is unlocked, I'd flash the stock on via RSDlite, flash TWRP 3.1.1.0 (my best experience), THEN install whatever ROM you like in TWRP. This'll start you from a clean slate and wipe ALL data from the phone. I'm guessing you forgot to wipe dalvik and cache before restarting, to. Someone of more experience may chime in, soon.
Sent from my XT1254 using Tapatalk
Crap. Sorry. Disregard. Thought this was a Droid Turbo thread.

Einsteindks said:
As I understand it, being an amateur ROM flasher, all those 3rd party ROMs need a TWRP recovery to work. Provided your bootloader is unlocked, I'd flash the stock on via RSDlite, flash TWRP 3.1.1.0 (my best experience), THEN install whatever ROM you like in TWRP. This'll start you from a clean slate and wipe ALL data from the phone. I'm guessing you forgot to wipe dalvik and cache before restarting, to. Someone of more experience may chime in, soon.
Click to expand...
Click to collapse
But how do I flash anything if I can't get into recovery?

andreyl79 said:
But how do I flash anything if I can't get into recovery?
Click to expand...
Click to collapse
You missed my edit update. I got confused as to which thread I was replying to.
Sent from my XT1254 using Tapatalk

Einsteindks said:
You missed my edit update. I got confused as to which thread I was replying to.
Click to expand...
Click to collapse
Nevertheless you gave me the idea to try looking for a similar LG recovery tool and I just found one. Flashing stock at the moment - fingers crossed

Ok, I installed LineageOS and it worked fine. Must be an issue with the latest AOSP ROM here

andreyl79 said:
Ok, I installed LineageOS and it worked fine. Must be an issue with the latest AOSP ROM here
Click to expand...
Click to collapse
The reason the flash failed is simply the fact you put the ROM on the internal storage, flashing from there wiped the ROM before it gets written. If you had stored the AOSP on an external SD, it would have worked.
As Lineage is based on AOSP, it should have failed also...

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.

Strange issue encountered first time with Oneplus 7t

After i flashed custom kernel (elemental x) & rebooted device it stuck in fastboot then I flashed stock boot images back (even flashed in both slots) still it's stuck on fastboot screen even deleted magisk module directory via adb still no luck, has somone encountered it before... I really need to get out from this..

Uraniam9 said:
After i flashed custom kernel (elemental x) & rebooted device it stuck in fastboot then I flashed stock boot images back (even flashed in both slots) still it's stuck on fastboot screen even deleted magisk module directory via adb still no luck, has somone encountered it before... I really need to get out from this..
Click to expand...
Click to collapse
I have used Elemental x before and I really never had issues, did you flash it on top of another custom kernel?are you on stock? OB? Are you using stable magisk build? You could try to dirty flash the stock fastboot ROM or just clean flash it. Also what's magisk modules are you using ?

lil_kujo said:
I have used Elemental x before and I really never had issues, did you flash it on top of another custom kernel?are you on stock? OB? Are you using stable magisk build? You could try to dirty flash the stock fastboot ROM or just clean flash it. Also what's magisk modules are you using ?
Click to expand...
Click to collapse
No I flashed it on stock boot images, I was previously using Elementalx and also never had this issue, even flashed another on top of other custom kernel was fine for me, I guess something different is messed up, well i deleted whole magisk module directory via adb, you mean dirty flash full ota via fastboot? Can you confirm it I won't loose any data by dirty flashing all(by flashing all files one by one?).

Uraniam9 said:
No I flashed it on stock boot images, I was previously using Elementalx and also never had this issue, even flashed another on top of other custom kernel was fine for me, I guess something different is messed up, well i deleted whole magisk module directory via adb, you mean dirty flash full ota via fastboot? Can you confirm it I won't loose any data by dirty flashing all(by flashing all files one by one?).
Click to expand...
Click to collapse
I done it and I just did right now you won't lose data if you dirty flash you will lose root, when you first click on flash all it will go get you a message saying erase user data: y or N ,just type N . It will flash all the files again and you will still keep all your apps and data.