Can someone confirm the order for flashing ROM, kernel, and Gapps? Do I perform all the factory reset/wipe/format steps prior to flashing anything, and do I need to reboot between any of the steps? Is it really necessary to perform multiple wipes (i.e. factory reset x3) and/or use the CleanWIPE script?
I'm used to a factory reset and a flash of just the ROM, but I'm reading through the CarbonROM thread and seeing the suggestions for custom kernel, separate Gapps, and "hoops" regarding data/GPS that have me second-guessing my noobish knowledge.
I am S-OFF and currently running Tachyon 1.1 with some minor problems. I attribute these to using CWM Touch recovery and not formatting internal SD/emmc prior to first (and only) 4.3 ROM. I plan to switch to TWRP 2.6.3 prior to flashing another ROM per all the high praise.
esmith818 said:
Can someone confirm the order for flashing ROM, kernel, and Gapps? Do I perform all the factory reset/wipe/format steps prior to flashing anything, and do I need to reboot between any of the steps? Is it really necessary to perform multiple wipes (i.e. factory reset x3) and/or use the CleanWIPE script?
I'm used to a factory reset and a flash of just the ROM, but I'm reading through the CarbonROM thread and seeing the suggestions for custom kernel, separate Gapps, and "hoops" regarding data/GPS that have me second-guessing my noobish knowledge.
I am S-OFF and currently running Tachyon 1.1 with some minor problems. I attribute these to using CWM Touch recovery and not formatting internal SD/emmc prior to first (and only) 4.3 ROM. I plan to switch to TWRP 2.6.3 prior to flashing another ROM per all the high praise.
Click to expand...
Click to collapse
If you are S-OFF, I would recommend this procedure (assuming TWRP 2.6.3.0 is installed)
1) Backup current ROM
2) Flash CleanWipe script of choice
2.5) [OPTIONAL] Format /boot partition (Some people say do this, others say never do. I do it everytime and never had any issues)
3) Flash ROM
4) Flash recommended Gapps (official full or unofficial Core as recommened by ROM dev)
5) Reboot
If you are going for a custom kernel that is not included in the ROM, make sure the ROM boots and comes up problem free BEFORE you flash it.
This is what I have been doing for some time, it always works... no extra steps or anything else. I have never had the internal storage problems or anything else. If you do have the internal storage issue, just format it in TWRP and you should be good to go.
acejavelin said:
2.5) [OPTIONAL] Format /boot partition (Some people say do this, others say never do. I do it everytime and never had any issues)
Click to expand...
Click to collapse
Where do you do this in TWRP 2.6.3.0? I do not see an option for /boot in Advanced Wipe.
esmith818 said:
Where do you do this in TWRP 2.6.3.0? I do not see an option for /boot in Advanced Wipe.
Click to expand...
Click to collapse
Hmm... Apparently its gone now, just skip that part I guess. The more I think about it, the more I am pretty sure I haven't done that since I used Amon Ra. Just Cleanwipe and flash.
Sent from my Nexus 4 using xda app-developers app
esmith818 said:
Where do you do this in TWRP 2.6.3.0? I do not see an option for /boot in Advanced Wipe.
Click to expand...
Click to collapse
If internal is acting funny and camera says it doesnt work after you flash the rom and everything you'll have to go into advanced settings and partition internal sd card and emmc...and also wipe it afterwards...also just to be safe format internal sd to defaults on pc afterwards
Related
When I first got my Optimus V it'd been, and still is, my first android phone. I jumped in ass first and followed a guide to put Clockwork Recovery and aospcmod on my phone. I've been reading up on Bumblebee and Xionia recovery and want to try that out.
The only problem that I am faced with is I don't know how to change recoveries, how to wipe, backup, and install a new rom & kernel. Any help, much appreciated.
FatalIll said:
When I first got my Optimus V it'd been, and still is, my first android phone. I jumped in ass first and followed a guide to put Clockwork Recovery and aospcmod on my phone. I've been reading up on Bumblebee and Xionia recovery and want to try that out.
The only problem that I am faced with is I don't know how to change recoveries, how to wipe, backup, and install a new rom & kernel. Any help, much appreciated.
Click to expand...
Click to collapse
afaik you can flash the new recovery in recovery
all the wiping is done in recovery. there should a an option to wipe data, dalvik cache, etc.
theres an option to make a nand backup in recovery too but remember that backups from one recovery are probably not compatible with another recovery.
your rom should have specific instructions on how to flash it, but this is the general scope:
download the file (on your phone, or on your computer and then transfer it to your phone)
place it in at the root of your sdcard (directory /sdcard)
boot into recovery and wipe data, dalvik cache, etc
flash rom (it comes with a kernel, you can flash your own kernel later)
done (first boot might take a while, dont worry)
of course as i said, this is kinda the general thing. check the instructions for your rom
Just curious about whether I am wiping and flashing correctly.
I currently have TWRP 2.2.2.0 installed.
I am presently on the Viper sense based rom for the HOX+. I assume I must be wiping and flashing correctly as the rom works!!
Wipe cache, wipe davlik cache, factory reset and system? Then flash rom?
Doing this, does it completely remove the previous rom, audio drivers etc so that I have a clean slate so to speak for flashing the new rom?
That's what I'm after, wiping the previous rom completely, drivers, everything so that I can flash an aosp based rom.
Thanks.
First off, I would advice you to flash the latest version of TWRP before doing anything. Now, having said that, yeah, essentially press all buttons in the wipe Menu (I frankly don't know if the "Format" button would be overkill). However, be aware that in doing so, you're going to wipe all the data in the partition, including any zip files you may want to flash afterwards. If you end up doing this, you're going to need to sideload the rom into your phone in order for you to be able to install it.
You only lose stuff in data by wiping data partition
Sent from my HTC One X+ using Tapatalk 2
If he is wanting to use the Viper rom it is best to flash the version that is on the Viper thread. This has some minor changes in it to allow the install of OTA's and zip files from the hub.
If he uses the latest version it may cause issues trying to install OTA's.
Lloir said:
You only lose stuff in data by wiping data partition
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Exactly, so long as he doesn't touch the data partition he should loose nothing. I did recommend the whole "Nuke it" approach because of the whole "Clean Slate" thing the OP wanted though...
Nuke it? Wipe everything, including data partition then sideload a rom?
Thanks.
maritimesbob said:
Nuke it? Wipe everything, including data partition then sideload a rom?
Thanks.
Click to expand...
Click to collapse
Yeah, although it's not necessary most of the times, at least that's what I personally do when I want a 100% clean install (Short of re-locking the bootloader and running a RUU of course).
maritimesbob said:
Nuke it? Wipe everything, including data partition then sideload a rom?
Thanks.
Click to expand...
Click to collapse
While installing Viper you can choose to wipe the phone for a clean installation. So basically it's not necessary to do anything than install recovery for Viper and then install Viper ROM and choose the correct option in AROMA installer...
Which recovery is the most hassle-free for the verizon GS4?
My current issue:
I currently have TWRP 2.5.0.2 installed (via goomanager) when I intially rooted my phone -- still on stock, haven't updated to ME7 but looking to finally flash a ROM this week.
Reading through threads, I am picking up bits and pieces of people soft bricking their phone due to a wipe done with TWRP, requiring an ODIN flash to get the phone to boot. Is this a problem only with TWRP 2.6, or with all versions?
What are the advantages/disadvantages to TWRP and CWM.
Thanks for you help
They both essentially do the same thing. It comes down to personal preference in my opinion. Alot of people say twrp is easier to use but like you I have read about the bootloop issues associated with it. And i really dont like the look of twrp either. Now me I like cwm. I have been using it for over 2 years on 4 different devices and have never had a single problem.
Sent from my SCH-I545 using Tapatalk 2
TWRP v2.5.0.2 seems more stable than the current 6.2 version. The 2.5.02 works perfectly far as I know. TWRP seems most recommended, but they both do the same job very well.
hexitnow said:
Now me I like cwm. I have been using it for over 2 years on 4 different devices and have never had a single problem.
Click to expand...
Click to collapse
Mmm Hmm! I like me some CWM!
I use twrp 2.5.0.2. CWM's menu layout is garbage.
sent from my Verizon Galaxy s4
Philz CWM supports extFAT and reports the correct date/time.
Sent from my Nexus 7 using Tapatalk 2
With TWRP 2.5.0.2 I was able to corrupt my data partition by formatting it. Over and over again this happened. When you format it (the one where you have to type "yes") screws things up pretty bad. At first formatting it again would fix it but then it got to the point where rebooting my phone would result in it getting stuck at the logo. When I went into recovery it would ask me for a password to access /DATA. If you do not format DATA you might not have a problem. I don't do it often but the first time you do things could eventually require ODIN and starting over.
I have been using the PhilZ recovery (modified CWM) and its been working great. It has a feature where you can "Wipe to flash new ROM". It will get things clean for a new flash pretty good.
That being said I like how TWRP is laid out better, with larger buttons, and especially doing flashes of multiple ZIPs is more efficient. But in the end I went with the one that was more stable. I might give TWRP a try again and just stay away from the hard wipe. Things have been stable enough where I have not had to do that for a while.
For a long time I used CWM. However once I made the move to TWRP I never looked back. Now with that said I use 2.5.0.2 as I have read many issues with 2.6 and 2.5.0.2 has been perfect for me.
Not knocking CWM but I've had no issues with exFat and twrp 2.5.0.2.
I've used TWRP to flash several ROMs, to make backups, restore backups, etc. etc. etc. and have never had any problem with any version.
As far as CWM, it's also always worked perfectly for me but I find TWRP slightly easier to use.
Thanks everyone who replied!
Quite a mix bag of results -- but most people say the TWRP works fine. Diaftia -- the issues you ran into are exactly what I have read and really don't want to deal with them.
To all who use TWRP as the recovery -- what are the steps you use to CLEAN flash a new rom (ME7 based). One reply I read in a thread somewhere said don't use TWRP to upgrade to a ME7 based ROM as it causes those hang-ups that diaftia explained. Are there any don't do's --i.e. wipe data? etc.
I will probably flash this weekend -- still shopping around for the ROM that suits me the best.
Thanks again so much everyone -- really appreciate the feedback,
-thebeen
thebeen said:
Thanks everyone who replied!
Quite a mix bag of results -- but most people say the TWRP works fine. Diaftia -- the issues you ran into are exactly what I have read and really don't want to deal with them.
To all who use TWRP as the recovery -- what are the steps you use to CLEAN flash a new rom (ME7 based). One reply I read in a thread somewhere said don't use TWRP to upgrade to a ME7 based ROM as it causes those hang-ups that diaftia explained. Are there any don't do's --i.e. wipe data? etc.
I will probably flash this weekend -- still shopping around for the ROM that suits me the best.
Thanks again so much everyone -- really appreciate the feedback,
-thebeen
Click to expand...
Click to collapse
Im on twrp 2.5.0.2 and just flashed a stock root me7. Flashed with twrp and everything is working smoothly. But i should add that just prior to this I used a factory image and went back to mdk so my partitions would be formatted. Then immediately got root and installed twrp 2.5.0.2 and flashed the mE7 rom.
Also I find the file manager in twrp a valuable tool I just couldn't give up.
Sent from my SCH-I545 using xda app-developers app
I've been using cwm since my ogdroid. I used it on thunderbolt. I had to use twrp on the bionic. Twrp was easy to use but I jumped back to cwm on the sg4. I just really like how cwm manages. I personally don't see need to have multi roms loaded. Cwm assures I do proper install of each new rom I use I feel.
ghostrigger on to the next show
I had used TWRP and been fine for 3 roms, then the 4th rom installation soft-bricked my phone. It would boot the first time, but you could not restart it. I wiped several times and resinstalled, verifying MD5's and using multiple versions... same problem each time. Finally, I had to figure out how to use ADB again (I'd forgotten years ago) and I installed CWM and started again from scratch. Each mod install has been flawless, save for me forgetting that the power button is now where the volume rockers used to be on the Rezound a few times. I soft bricked with TWRP and CWM fixed it, so that's where my current loyalty goes.
thanks everyone for the replies. I ended up going to homebase and using PhilZ touch CWM and worked flawlessly. Don't think i'll be going to the TWRP bandwagon for a while.
Thanks! Hope this thread helps any future users on their decision
-thebeen
If new users see this and are reading, it seems most of the devs for this phone are using TWRP 2.5.0.2. Those guys flash way more than even the average crack flasher. If that seems to be their go to recovery must be something to it. The others are probably fine too. Some times it comes down to preference. I've seen posts for all the recoveries good and bad. That being said, it was also asked what are the steps for flashing with TWRP.
Here goes.
For TouchWiz and AOSP 4.2.2 roms
1. Factory Reset under wipe, then tap advanced and check the boxes beside system, Data, Cache, and davlik. Do both of these x3.
2. Flashed ROM and gapps (if not included with the ROM.)
3. Reboot system.
For AOSP 4.3 ROM.
1. Factory Reset under wipe, then tap advanced and check the boxes beside system, Data, Cache, and davlik. Do both of these x3.
2. Flashed ROM and gapps (if not included with the ROM.)
3. Wipe Davlik and cache.
4. Reboot into Recovery.
5.Wipe Davlik and cache under advanced.
6. Reboot system.
In addition follow any additional instructions from the OP for the ROM your flashing. They are mostly the same but you should always read to be sure.
I've had 100% success with the above.
Dubsy if you see this maybe you could post your process for flashing with TWRP. Might be different, simpler, or better. You would be flashing way more than me.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
If new users see this and are reading, it seems most of the devs for this phone are using TWRP 2.5.0.2. Those guys flash way more than even the average crack flasher. If that seems to be their go to recovery must be something to it. The others are probably fine too. Some times it comes down to preference. I've seen posts for all the recoveries good and bad. That being said, it was also asked what are the steps for flashing with TWRP.
Here goes.
For TouchWiz and AOSP 4.2.2 roms
1. Factory Reset under wipe, then tap advanced and check the boxes beside system, Data, Cache, and davlik. Do both of these x3.
2. Flashed ROM and gapps (if not included with the ROM.)
3. Reboot system.
For AOSP 4.3 ROM.
1. Factory Reset under wipe, then tap advanced and check the boxes beside system, Data, Cache, and davlik. Do both of these x3.
2. Flashed ROM and gapps (if not included with the ROM.)
3. Wipe Davlik and cache.
4. Reboot into Recovery.
5.Wipe Davlik and cache under advanced.
6. Reboot system.
In addition follow any additional instructions from the OP for the ROM your flashing. They are mostly the same but you should always read to be sure.
I've had 100% success with the above.
Dubsy if you see this maybe you could post your process for flashing with TWRP. Might be different, simpler, or better. You would be flashing way more than me.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Im not a dev, but I do make my own mods and personal roms and ive used every recovery possible, in fact Ive made my own zip of every recovery after loki flashing and put them in my sd for a rainy day (think I even posted most of them somewhere recently) . I use twrp because of the file manager and terminal (mainly terminal though). Most issues I can fix in recovery by either setting permissions for or removing/moving apks (also doable in terminal >>adb>>chmod 755/644 etc,etc). Terminal with adb gives you the ability to do almost everything. That and i like to see the logs of what's happenin'. Ive never had an issue a using exfat either after formating using linux.
Fwiw my method is:
1. Format system
2. Flash rom
3. Wipe/format cache and dalvik
4. Fix permissions (if rom contains custom kernel)
5. Reboot
tetakpatak said:
Please quote my post and copy&paste whole text into some help thread for your phone, it is better idea as we are now getting off topic here. I'll try to help you there.
Format /system is done in recovery mode under "mount and storage" then after that you can restore your nandroid if it is done with the same recovery you use now. If you're on PhilZ 6, it usually can restore also CWM 6 backups.
Click to expand...
Click to collapse
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Click to expand...
Click to collapse
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
tetakpatak said:
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
Click to expand...
Click to collapse
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it? .
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it?
Click to expand...
Click to collapse
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
tetakpatak said:
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
Click to expand...
Click to collapse
Thanks for helping, but I ended up downloading the stock rom and flashing it. Everything was normal. Then I installed cm10.2 so everything's great now. Thanks!
Sent from my Nexus 4 using xda app-developers app
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
tetakpatak said:
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
Click to expand...
Click to collapse
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Sent from my Nexus 4 using xda app-developers app
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
keithross39 said:
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
Click to expand...
Click to collapse
6.0.4.5 is compatible? I think so ......
Sent from my Nexus 4 using xda app-developers app
I've always read....not.....
In any case, probably best not to risk it......
6.0.4.7 is DEFINITELY KK compatible.... and it'd take a couple of seconds to flash.........
Sent from my Infected KitKat bar.....
AndroidReborn said:
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Click to expand...
Click to collapse
Yes, mate, CWM 6.0.4.5 is capable of flashing KitKat.
It is usually always the same:
download your ROM zip and compatible Gapps
check in the phone (or PC) if the zips are corrupted through download (if they open after clicking them, they are fine)
move the zips to the folder you will flash it from (if you use PC to flash zips with ADB sideload, put them in the sdk/platform-tools folder)
make nandroid backup of your presently used ROM
wipe data/factory reset
wipe cache
wipe dalvik cache (advanced)
format /system (under mount and storage)
flash ROM.zip
flash Gapps
reboot
It is in general always good to read in the development thread of the ROM you attend to flash in the opening post which Gapps are recommended, or if there is some unusual order of flashing (sometimes, developers recommend reboot system after flashing ROM, and after that going to recovery and flash Gapps zip.
Some KitKat ROMs struggle with root access by using Superuser, so SuperSU should be flashed. If SuperSU app from Play Store gives errors by updating binary, you should uninstall SuperSU app then, find in the Chainfire's thread the compatible UPDATE-SuperSu.zip (version for your phone), flash its zip in the recovery, install SuperSU app, update binary (either "normal" or "through CWM/TWRP")
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.