So, I have updated lineageOs through TWRP.
I wipe dalvik, system and cache.
I flash latest rom and reflash Gapps then magisk but then it's bootloop.
I'm using lineageOs before, but I want to update it to latest rom and this is happening.
I tried many ways like flash lazyflasher etc. but no use, the problem is still happen.
So I have my phone unrooted now.
Please, help me to solve this problem, how can I root my phone? I'm still noob at this things.
PS:
lineageOs version : 15.1-20180611-NIGHTLY-mido
pandip said:
So, I have updated lineageOs through TWRP.
I wipe dalvik, system and cache.
I flash latest rom and reflash Gapps then magisk but then it's bootloop.
I'm using lineageOs before, but I want to update it to latest rom and this is happening.
I tried many ways like flash lazyflasher etc. but no use, the problem is still happen.
So I have my phone unrooted now.
Please, help me to solve this problem, how can I root my phone? I'm still noob at this things.
Click to expand...
Click to collapse
You would be really helpful if you were more specific about which version of lineage you flashed!
David_#27 said:
You would be really helpful if you were more specific about which version of lineage you flashed!
Click to expand...
Click to collapse
lineageOs version : 15.1-20180611-NIGHTLY-mido.
I download it from it's official site.
pandip said:
lineageOs version : 15.1-20180611-NIGHTLY-mido.
I download it from it's official site.
Click to expand...
Click to collapse
From here: https://download.lineageos.org/mido, right?
pandip said:
So, I have updated lineageOs through TWRP.
I wipe dalvik, system and cache.
I flash latest rom and reflash Gapps then magisk but then it's bootloop.
I'm using lineageOs before, but I want to update it to latest rom and this is happening.
I tried many ways like flash lazyflasher etc. but no use, the problem is still happen.
So I have my phone unrooted now.
Please, help me to solve this problem, how can I root my phone? I'm still noob at this things.
PS:
lineageOs version : 15.1-20180611-NIGHTLY-mido
Click to expand...
Click to collapse
You need a special TWRP for Treble if you want to flash Magisk. It's all linked and discussed in the LineageOS thread.
Also, when coming from an old or unofficial LineageOS build, you need to do a full wipe (System, Data, Cache, Dalvik and Vendor).
David_#27 said:
From here: https://download.lineageos.org/mido, right?
Click to expand...
Click to collapse
yea it's from there, it's an official site, isn't it ?
Noter2017 said:
You need a special TWRP for Treble if you want to flash Magisk. It's all linked and discussed in the LineageOS thread.
Also, when coming from an old or unofficial LineageOS build, you need to do a full wipe (System, Data, Cache, Dalvik and Vendor).
Click to expand...
Click to collapse
I did a full wipe even it's an official lineageOs but the problem is still exist.
I reflash all stuff like gsi vendor mido treble, gapps, kernel and boom, the problem is stand still.
pandip said:
yea it's from there, it's an official site, isn't it ?
Click to expand...
Click to collapse
Yes exactly! After downloading the ROM and flashing it from recovery you will notice that it is treble rom(apart from the message: "patching system image unconditionally..." You will also see a message: "Patching vendor image...")! So you need two things to download:
1) Custom TWRP for treble ROMs.
2) Custom Magisk for treble ROMs.
David_#27 said:
Yes exactly! After downloading the ROM and flashing it from recovery you will notice that it is treble rom(apart from the message: "patching system image unconditionally..." You will also see a message: "Patching vendor image...")! So you need two things to download:
1) Custom TWRP for treble ROMs.
2) Custom Magisk for treble ROMs.
Click to expand...
Click to collapse
I just download magisk custom from the lineageOs's thread and flash it then it's succesfully installed a.k.a. no bootlooping anymore.
Maybe I should reads the threads carefully before execute next time.
Wow thanks a lot man, you helped me.
Same problem
Hi there, I'm having the same bootloop problem. Could you show me the thread you got the magisk from?
So first of all I would really recommend you to grab this TWRP: https://sourceforge.net/projects/orangefox/files/mido/ (all credits go to orangefox developers and you can find them here: https://forum.xda-developers.com/re.../recovery-orangefox-recovery-project-t3775933)
Download the latest R7 zip because it supports now all kinds of roms (treble, non-treble and Android P!)
Now go and download the magisk from here: https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
First rom then gapps custom kernel(optional) last flash magisk. If you encounter any issues with magisk then wipe everything flash rom gapps and kernel if u want boot your phone to system reboot to recovery and flash magisk.
Related
Is Samsung Galaxy S5 G900T a KLTE handset? cannot seem to find anything related to T-mobile S5
nht48823 said:
Is Samsung Galaxy S5 G900T a KLTE handset? cannot seem to find anything related to T-mobile S5
Click to expand...
Click to collapse
Yes it is
from my Samsung Galaxy S5 SM-G900T on AT&T, Android 5.1.1 DOB1 with Resurrection Remix ROM v5.5.6
jt1998 said:
Yes it is
from my Samsung Galaxy S5 SM-G900T on AT&T, Android 5.1.1 DOB1 with Resurrection Remix ROM v5.5.6
Click to expand...
Click to collapse
I'm trying to flash cyanogenmod from twrp but getting error 7 , can't flash over incompatible system data. I'm on t mobile sm-g900t and downloaded the latest klte snapshot...
Help please.
Dorsant said:
I'm trying to flash cyanogenmod from twrp but getting error 7 , can't flash over incompatible system data. I'm on t mobile sm-g900t and downloaded the latest klte snapshot...
Help please.
Click to expand...
Click to collapse
Trying to flash cm 12 rom right? It's a zip? Checked md5 to ensure good download?
I'd update to latest twrp 3.0 first. Make a backup of current rom/setup.
Are you trying clean or dirty flash?
Sent from my SM-G900T using Tapatalk
jt1998 said:
Trying to flash cm 12 rom right? It's a zip? Checked md5 to ensure good download?
I'd update to latest twrp 3.0 first. Make a backup of current rom/setup.
Are you trying clean or dirty flash?
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply. Not sure how to check if md5 download was good, but there were no interruptions so I believe it was.
And what is clean vs dirty flash? I downloaded the only "snapshot" version that was on the klte downloads page directly to my phone. Rebooted into twrp recovery, selected zip file, swipe to flash. Then I get the error. Looks like file name says CM 12.1-20115007....
Snapshot is a stable build right? This is my first custom ROM so I wanted to start with a stable build.
Thanks
Dorsant said:
And what is clean vs dirty flash?
Click to expand...
Click to collapse
Make a backup, then wipe system, data, cache, and dalvik before flashing the ROM. It helps prevent bugs
Dorsant said:
Thanks for the reply. Not sure how to check if md5 download was good, but there were no interruptions so I believe it was.
And what is clean vs dirty flash? I downloaded the only "snapshot" version that was on the klte downloads page directly to my phone. Rebooted into twrp recovery, selected zip file, swipe to flash. Then I get the error. Looks like file name says CM 12.1-20115007....
Snapshot is a stable build right? This is my first custom ROM so I wanted to start with a stable build.
Thanks
Click to expand...
Click to collapse
This is the Cm 12.1 ROM I'd use for your device https://download.cyanogenmod.org/get/jenkins/129251/cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte.zip
You'll need an android 5.0 lollipop gapps also which allows you to use your ROM with google apps, play store functionality, etc. This is the one I'd use for your device. https://basketbuild.com/filedl/devs...gapps-modular-micro-5.1.1-20150927-signed.zip
Once both are downloaded onto your phone storage, make sure you backup 1st in TWRP so if anything goes wrong you're ok.
Clean flash means you're wiping system, data, dalvik, and cache before installing new ROM/Gapps - always reccommended if you're coming from stock touchwiz a different non CM rom.
Dirty flash means you only wipe dalvik and cache typically b/c you're just updating your current ROM with a newer version of same ROM so no need to wipe data/system but it is the first thing to evaluate if your device has errors like force closures, bugginess, etc.
Also, after you've wiped your device and now are ready to install your ROM and gapps, do both zip installs in one step. so add the ROM, then add another zip which will be your gapps, then swipe to flash having 2 zips in your queue. Then when all is done, reboot and let your device install. Sign in setup your accounts and profit.
Let me know how it goes ok! Hit thanks for me please!!
jt1998 said:
This is the Cm 12.1 ROM I'd use for your device https://download.cyanogenmod.org/get/jenkins/129251/cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte.zip
You'll need an android 5.0 lollipop gapps also which allows you to use your ROM with google apps, play store functionality, etc. This is the one I'd use for your device. https://basketbuild.com/filedl/devs...gapps-modular-micro-5.1.1-20150927-signed.zip
Once both are downloaded onto your phone storage, make sure you backup 1st in TWRP so if anything goes wrong you're ok.
Clean flash means you're wiping system, data, dalvik, and cache before installing new ROM/Gapps - always reccommended if you're coming from stock touchwiz a different non CM rom.
Dirty flash means you only wipe dalvik and cache typically b/c you're just updating your current ROM with a newer version of same ROM so no need to wipe data/system but it is the first thing to evaluate if your device has errors like force closures, bugginess, etc.
Also, after you've wiped your device and now are ready to install your ROM and gapps, do both zip installs in one step. so add the ROM, then add another zip which will be your gapps, then swipe to flash having 2 zips in your queue. Then when all is done, reboot and let your device install. Sign in setup your accounts and profit.
Let me know how it goes ok! Hit thanks for me please!!
Click to expand...
Click to collapse
Perfect! Great explanation, worked perfectly!
Dorsant said:
Snapshot is a stable build right? This is my first custom ROM so I wanted to start with a stable build.
Click to expand...
Click to collapse
there's little reason to use an old & insecure version at this point, i've ONLY used a few nightlies, the bugs were usually minor & you can get the fixes pretty much as soon as they come out rather than waiting months
deep sleep battery use & the camera app are greatly improved in CM13
http://www.cmxlog.com/13/klte/ changelogs
I did a factory reset on my phone and it just booted up in to twrp recovery mode and I cant get in out of it. Its stuck on it I even tried installing a custom rom to make sure i didnt delete everything somehow. Nothing is working I rooted my phone yestarday im still new to this stuff. Anyone have any ideas on how I can fix this?
Dileter said:
I did a factory reset on my phone and it just booted up in to twrp recovery mode and I cant get in out of it. Its stuck on it I even tried installing a custom rom to make sure i didnt delete everything somehow. Nothing is working I rooted my phone yestarday im still new to this stuff. Anyone have any ideas on how I can fix this?
Click to expand...
Click to collapse
I had this issue, too once. Can't recap what exactly fixed it, but I flashed TWRP again (think that didn't fix it) and then dirty flashed a ROM (in this case the same, which was already on the phone). If I remember correctly it worked after the later only. Might have also had to flash superSU. No data should be deleted if you just dirty flash (but do make a backup, should be no problem, since you are stuck in recovery anyway [emoji12]).
What ROM did you try to flash? You're rooted?
DidierMoulin said:
I had this issue, too once. Can't recap what exactly fixed it, but I flashed TWRP again (think that didn't fix it) and then dirty flashed a ROM (in this case the same, which was already on the phone). If I remember correctly it worked after the later only. Might have also had to flash superSU. No data should be deleted if you just dirty flash (but do make a backup, should be no problem, since you are stuck in recovery anyway [emoji12]).
What ROM did you try to flash? You're rooted?
Click to expand...
Click to collapse
Yes I am rooted and I tried flashing this ROM http://forum.xda-developers.com/lg-g5/development/unofficial-cyanogenmod-14-1-lg-g5-h850-t3494001
DidierMoulin said:
I had this issue, too once. Can't recap what exactly fixed it, but I flashed TWRP again (think that didn't fix it) and then dirty flashed a ROM (in this case the same, which was already on the phone). If I remember correctly it worked after the later only. Might have also had to flash superSU. No data should be deleted if you just dirty flash (but do make a backup, should be no problem, since you are stuck in recovery anyway [emoji12]).
What ROM did you try to flash? You're rooted?
Click to expand...
Click to collapse
I also dont really care if I lose photos or anything I already got all of them saved on my pc before I even started rooting the damn thing. I do need to ask tho how do you dirty flash and Do i just flash twrp normally since im already in it or ??? As I said im rlly new to this
TWRP can be flashed just from inside TWRP itself. Dirty flash means not do a factory reset before flashing.
Sorry that I can't remember what fixed it, but you can get out of it, 'cause I did, too...
Just wipe cache and dalvik/art cache then install separately TWRP, ROM, GAPPS, SUPERSU again and reboot after each install step to see of you reboot to TWRP again. That's what I did.
I use latest AICP ROM (http://forum.xda-developers.com/showthread.php?p=69699770) but that shouldn't matter.
Hope it helps.
DidierMoulin said:
TWRP can be flashed just from inside TWRP itself. Dirty flash means not do a factory reset before flashing.
Sorry that I can't remember what fixed it, but you can get out of it, 'cause I did, too...
Just wipe cache and dalvik/art cache then install separately TWRP, ROM, GAPPS, SUPERSU again and reboot after each install step to see of you reboot to TWRP again. That's what I did.
I use latest AICP ROM (http://forum.xda-developers.com/showthread.php?p=69699770) but that shouldn't matter.
Hope it helps.
Click to expand...
Click to collapse
Okay thanks a lot I will see if Any of it helps.
Please report.
DidierMoulin said:
Please report.
Click to expand...
Click to collapse
UPDATE I fixed it I just downgraded to the 2nd to lates version of twrp and it booted normally. Now I regret flashing the pixel one XDD If you have any idea for a good custom rom tell me Thanks for the help it actually helped a lot gave me the idea to downgrade the twrp recovery.
What you mean by pixel one xxd?
DidierMoulin said:
What you mean by pixel one xxd?
Click to expand...
Click to collapse
Its a 7.1.1 android rom from the google pixel
Dileter said:
Its a 7.1.1 android rom from the google pixel
Click to expand...
Click to collapse
Wait you were trying to flash recovery for a pixel device on your g5?
What TWRP build did you flash when you said you downgraded? 3.0.2-1 or 3.0.2-0 ? What is the date on the TWRP build?
Pphish20 said:
Wait you were trying to flash recovery for a pixel device on your g5?
What TWRP build did you flash when you said you downgraded? 3.0.2-1 or 3.0.2-0 ? What is the date on the TWRP build?
Click to expand...
Click to collapse
What he asked [emoji32]
It's happened to me too! Like three times lol. Just use UpperCut / LG UP to flash the latest nougat rom. That will fix the issue. You will need to re-root after that. There are instructions in this forum that tell how to do all of that. Good luck
Well and don't flash a ROM which is not for your device...
So here is my situation: I have a 3GB kenzo model with 6.3.24 EU ROM and ZCX TWRP 3.0.0-0. Of course bootloader in unlocked. Since the TWRP is pretty old, I updated it to RedWolf V3.1.
What I did:
Wipe: Dalvik/System/Data/Cache
Install Beta 7.9.22 or Stable 8.5.6.0 Kenzo firmware (tried with both)
Install RR image: RR-N-v5.8.5-20170924-kenzo-Final.zip
Install open gapps ARM64 7.1 (or not)
Wipe caches (also tried without wiping it)
Reboot
Bootloop
I know the first boot can take some time, so I let it run for 30+ minutes, still, only bootloop happened. Tried it a couple times, changing firmware, wiping caches at the end, ditching gapps etc. Images checked for md5 checksum on the phone, they are not corrupted. I was able to restore the EU ROM, but I really want to try out ResurrectionRemix. What could possibly the problem be?
Same here...i flash all nougat rom and got bootloop..now i stay in mm only...:C
Reflash newest stock image, than hack the emmc bootloader of it and try again
reemar said:
Reflash newest stock image, than hack the emmc bootloader of it and try again
Click to expand...
Click to collapse
So you mean to flash the latest stock ROM, won't it remove TWRP and lock the bootloader? And how to "hack" the emmc bootloader? Sorry, I'm a newbie
Just wait for at least 15 minutes after flashing
DdroidTHEGAMER said:
Just wait for at least 15 minutes after flashing
Click to expand...
Click to collapse
What do you mean, wait in TWRP for 15 minutes or when booting up the OS? As I said, I waited for 30+ minutes while it booted up.
Try installing ROM without flashing the firmware
Minions007 said:
Try installing ROM without flashing the firmware
Click to expand...
Click to collapse
That was the first thing I did (I didn't know a firmware was needed so I only flashed the RR ROM). Same bootloop
You could try to format data partition. Then wipe system,data,cache,dalvik cache and internal partition. After that Copy actually firmware, rom and opengapps arm64 pico in internal memory (Download all files again. Maybe archiv was damaged). Then flash firmware, rom, gapps and do wipe Cache/dalvik and reboot. Then report.
SpeRator said:
You could try to format data partition. Then wipe system,data,cache,dalvik cache and internal partition. After that Copy actually firmware, rom and opengapps arm64 pico in internal memory (Download all files again. Maybe archiv was damaged). Then flash firmware, rom, gapps and do wipe Cache/dalvik and reboot. Then report.
Click to expand...
Click to collapse
Did it, same result. Wiped everything, copied zips to internal storage, flashed from there and boom, bootloop
Hmm strange. You could test a good modified rom of rr.
Try this Rom:
https://www.androidfilehost.com/?fid=673791459329049490
And these Gapps:
https://www.androidfilehost.com/?fid=673791459329049438
If it all not Work, you have to flash actually official Rom to restore all with edl.
I have the exact same problem. Cant flash any ROM without getting bootloop. The bootloop though isnt a standard one, i think. I get the logo of the ROM and the phone starts to give Tiny vibrations in regular periods of time. I also left the phone for a long time hoping it'll eventualy boot. No luck. Tried flashing stock ROM with miflashtool and edl. Didnt help as well. I wonder if it could be the fault of any previous roms i had installed.
Twrp:
-are you sure you are not in read mode? Change to writemode.
-All relevant partitions mounted?
SpeRator said:
Twrp:
-are you sure you are not in read mode? Change to writemode.
-All relevant partitions mounted?
Click to expand...
Click to collapse
Changed to writemode.. default options selected in the mounts screen.
unable to flash any Nougat roms- stuck in boot animation.
is it because the bootloader was unlocked unofficially via lollipop fastboot ROM 7.1.8??
All right, got it working.
I flashed the latest official MIUI ROM with the official flashing tool with the option "clear all". Then I had to open the bootloader again, then flash TWRP, then flash RR, and it works! Looks like something was wrong with the previous installation, the clearing everything did the job.
Were your bootloader unlocked officially?
aldhi said:
Were your bootloader unlocked officially?
Click to expand...
Click to collapse
Unlocked Unofficially via this method https://www.youtube.com/watch?v=2FmaCdnLi58
tonyrulez said:
So here is my situation: I have a 3GB kenzo model with 6.3.24 EU ROM and ZCX TWRP 3.0.0-0. Of course bootloader in unlocked. Since the TWRP is pretty old, I updated it to RedWolf V3.1.
What I did:
Wipe: Dalvik/System/Data/Cache
Install Beta 7.9.22 or Stable 8.5.6.0 Kenzo firmware (tried with both)
Install RR image: RR-N-v5.8.5-20170924-kenzo-Final.zip
Install open gapps ARM64 7.1 (or not)
Wipe caches (also tried without wiping it)
Reboot
Bootloop
I know the first boot can take some time, so I let it run for 30+ minutes, still, only bootloop happened. Tried it a couple times, changing firmware, wiping caches at the end, ditching gapps etc. Images checked for md5 checksum on the phone, they are not corrupted. I was able to restore the EU ROM, but I really want to try out ResurrectionRemix. What could possibly the problem be?
Click to expand...
Click to collapse
Backup all of your data from internal storage and flash latest fastboot developer ROM and setup it. This will fix all issues regarding ROMs, zips, bootloops and firmware and any other. After that flash latest ZCX recovery as RedWolf recovery causes problems for flashing ROMs and zips as per my experiance. Then simply flash RR and gapps and boot and wait for 15 minutes and till then don't restart device.
I am using the kenzo version with 3gb ram.
I am currently on resurrection remix rom 6.1 and am updating the rom via dirty flashing it. I thought about rooting the rom via magisk flash and was thinking if the device can be updated after rooting it. If yes then how?
I don't understand the question if you are asking about if you can update with magisk, yes you can, I think you have to reflash magisk after updating the rom.
Tatoh said:
I don't understand the question if you are asking about if you can update with magisk, yes you can, I think you have to reflash magisk after updating the rom.
Click to expand...
Click to collapse
Sry.
I am talking about updating my rom. Can i update it once i have rooted it? Cause i read magisk does some changes in the boot sector and i don't want that while updating my rom(via dirty flashing) causing it to bootloop.
Varun Sharda said:
Sry.
I am talking about updating my rom. Can i update it once i have rooted it? Cause i read magisk does some changes in the boot sector and i don't want that while updating my rom(via dirty flashing) causing it to bootloop.
Click to expand...
Click to collapse
yes, you can update your ROM without any problems after root it's with magisk, don't worry it's won't cause bootloop or anything, if you want to update ROM , just flash ROM , gapps , wipe cache and dalvik cache then reboot.
Zasnizas said:
yes, you can update your ROM without any problems after root it's with magisk, don't worry it's won't cause bootloop or anything, if you want to update ROM , just flash ROM , gapps , wipe cache and dalvik cache then reboot.
Click to expand...
Click to collapse
Thanks you very much
Varun Sharda said:
Thanks you very much
Click to expand...
Click to collapse
one more things I forgot to tell you , you don't need to reflash magisk after flashing update rom coz twrp will automatically flash magisk after flashing rom. however you need to flash magisk again if you make a clean flash .
Can someone enlighten me how to dirty flash a custom rom? I mean I did it before but it was back in gingerbread days. Now that we use magisk, can someone give me the exact steps to do?
BenParz said:
Can someone enlighten me how to dirty flash a custom rom? I mean I did it before but it was back in gingerbread days. Now that we use magisk, can someone give me the exact steps to do?
Click to expand...
Click to collapse
Just flash the rom, and wipe cache thats it. But be sure ur using the same rom not another one
BenParz said:
Can someone enlighten me how to dirty flash a custom rom? I mean I did it before but it was back in gingerbread days. Now that we use magisk, can someone give me the exact steps to do?
Click to expand...
Click to collapse
wipe system,davik and cache. then dirty flash. remember not to wipe "system" if you flash OTA .zip
Okay, I have Additional questions :
1. Do I have to disable magisk modules or outright uninstall it before flashing?
2. Do I have to mount system and vendor in twrp again?
3. Do I need to install magisk again after dirty flashing?
4. Do I have to flash DFE again?
BenParz said:
Okay, I have Additional questions :
1. Do I have to disable magisk modules or outright uninstall it before flashing?
2. Do I have to mount system and vendor in twrp again?
3. Do I need to install magisk again after dirty flashing?
4. Do I have to flash DFE again?
Click to expand...
Click to collapse
1. Not necessary (unless you are using a module which may cause bootloop)
2. I never did.
3. Most of the times when dirty flashing the same ROM, twrp flashes Magisk (and GApps) automatically (atleast in my case). If it doesn't flash automatically, then you can flash it manually in order to make it certain.
4. Like I always said, flashing DFE is not necessary if you use the TWRP that supports decryption without actually decrypting your device permanently. Infact, I never suggest anyone to use a decrypted device if using it for financial purpose.
Rowdyy Ronnie said:
1. Not necessary (unless you are using a module which may cause bootloop)
2. I never did.
3. Most of the times when dirty flashing the same ROM, twrp flashes Magisk (and GApps) automatically (atleast in my case). If it doesn't flash automatically, then you can flash it manually in order to make it certain.
4. Like I always said, flashing DFE is not necessary if you use the TWRP that supports decryption without actually decrypting your device permanently. Infact, I never suggest anyone to use a decrypted device if using it for financial purpose.
Click to expand...
Click to collapse
Omg, thanks for answering my questions mate, much appreciated!
Depends, but if you are switching from a different ROM then dirty flash will most likely brick your device or cause a lot of errors and it should never be done. But if it is from the same ROM, like going from older PE to new one, then all you do is flash the newer one with the older version already installed. But it is recommended you clean flash because from my experience, dirty flash always caused errors like lag and crashing. Just use Migrate(available on Play store) and use it to backup apps. A lot of these custom ROMs are still early and in BETA so it is recommended you clean flash.
As for DFE, it is optional. Only problem is you will have to use TWRP with SD card support or one that has a working decryption so that you can flash files through the recovery . You can use apps like flashify to flash if you dont want to your device decrypted. If you got any questions you can ask me.
itscooltime said:
Depends, but if you are switching from a different ROM then dirty flash will most likely brick your device or cause a lot of errors and it should never be done. But if it is from the same ROM, like going from older PE to new one, then all you do is flash the newer one with the older version already installed. But it is recommended you clean flash because from my experience, dirty flash always caused errors like lag and crashing. Just use Migrate(available on Play store) and use it to backup apps. A lot of these custom ROMs are still early and in BETA so it is recommended you clean flash.
As for DFE, it is optional. Only problem is you will have to use TWRP with SD card support or one that has a working decryption so that you can flash files through the recovery . You can use apps like flashify to flash if you dont want to your device decrypted. If you got any questions you can ask me.
Click to expand...
Click to collapse
Actually I've got one.
I want to dirty flash a ROM (just an updated version of the same one) but I dont know how i can place a file into my phone's internal storage through TWRP without formatting de data (full wipe). My phone is not recognized by my PC on TWRP mode unless I make a full wipe.
Can you guys assist?
I have a question I'm using a custom rom with gapps, but the custom rom update that is available does not have gapps if I flash the non-gapp version on my gapp version will it cause problems?
gersomfcomiano said:
Actually I've got one.
I want to dirty flash a ROM (just an updated version of the same one) but I dont know how i can place a file into my phone's internal storage through TWRP without formatting de data (full wipe). My phone is not recognized by my PC on TWRP mode unless I make a full wipe.
Can you guys assist?
Click to expand...
Click to collapse
G3's typically have sd card storage available. athat's where I put all my roms, gapp's, other stuff which I have no trouble flashing from TWRP. Beyond that you must seek one more learned than I.
Nfury00701 said:
wipe system,davik and cache. then dirty flash. remember not to wipe "system" if you flash OTA .zip
Click to expand...
Click to collapse
in this case all data & apps will be lost ?
gajanan57 said:
in this case all data & apps will be lost ?
Click to expand...
Click to collapse
You're right. That user is wrong. Do NOT wipe system if you are dirty flashing. Otherwise you are just doing a normal flashing, not updating your rom.
fede01_8 said:
You're right. That user is wrong. Do NOT wipe system if you are dirty flashing. Otherwise you are just doing a normal flashing, not updating your rom.
Click to expand...
Click to collapse
I'd say no.
Android System partition is mounted as readonly after boot and won't be modified anymore then (unless you modify system files with adb/TWRP and mounted system partition).
Your during Android usage installed apps are stored in Data partition.
However you have to reflash gapps and magisk in case you installed them with TWRP/adb.