Related
Newb here -- I'm running Cyanogen 4.0.4.
I want to try some themes, but wanted to know in advance how I would go about un-installing them if they cause problems.
How would I revert to the base cyanogen state?
I'd like to avoid having to re-flash cyanogen and/or wiping phone.
Thanks!
Don't wipe/flash.
Just apply the cyanogen rom again.
It's that easy? Will my apps/data stay intact on the phone or will that erase it when the ROM is re-flashed?
yes it is just that easy the theme is just modded picture files in the rom. so if you replace the files your apps and data airn't effected. its the same as flashing and updated version of the rom
I am not sure how installing a new custom ROM and kernel affects my device (R900x), but I already have root and unlocked the bootloader. Will I lose any of my data (music, contacts, etc.) if I flash DooM's Kernel and the FTS rom? And how should I backup data (preferably through CWM), even if installing a new kernel/ROM doesn't wipe everything?
The main reason I am doing this is because I constantly get software update reminders and I have to shut off my wifi/data in order to stop getting notified, because it will no longer let me click the "Remind Me Later" option.
Make a backup anyways
You wont lose data for kernel
but for Custom ROMS to be 100% functional i reccomend you make a backup and WIPE DATA
Thank you.
I also need help flashing FrAsErTag's FTS ROM. Can someone confirm these steps?
Backup data.
Flash UK-Generic firmware.
Factory reset data.
Get root. (Do I need to unlock bootloader and get root again after flashing the generic FW?)
Flash DooM's kernel.
Flash FTS ROM.
Run CDMA, Facebook, and gapps patches (CWR).
Restore data.
just do what the instructions tell you in his first post.
Well I'm not sure how to do it exactly, but I think I'm going to see if I can flash the full 2.3.3 update manually with FlashTool before I do anything else. I have an unlocked bootloader though, will manually flashing the update brick my phone? Thanks again for your help.
Hi guys!
A few days ago I bought the notes 2. He installed the rom DME6 with the modem DMF1.
I would like to know how to install a custom ROM safely without corrupting the IMEI!
Thanks!
You can safely use this tool to backup/restore your EFS (which contains your IMEI) before flashing anything. You should have a rooted phone if doing so.
You can also use this APK form the Play Store to backup your EFS partition.
After backing up your EFS, you can proceed with the custom ROM installation as usual. If you get your EFS corrupted, you can easily restore it now.
To find out more about rooting, EFS and flashing, read this.
I hope this helps!
Currently I'm using a OnePlus 3 on 6.0.1 (OOS 3.1.1) but I would like to update to Oreo (OOS 5.0). How do I do this when my device is rooted?
I've downloaded the latest OS off the oneplus website. Is it as simple as uninstalling SuperSU and then flashing the latest OS through recovery?
I also have TWRP recovery and Xposed installed.
Would appreciate any help.
Just flash the new OS in recovery, no need to unroot as it will get overwritten anyways. You'll need to root again after updating, of course.
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
Just flash the new OS in recovery, no need to unroot as it will get overwritten anyways. You'll need to root again after updating, of course.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
The full zip of oxygen OS will overwrite the TWRP recovery with the stock one?
I can update with the zip in the recovery and root whenever i want or i have to do this at the same time?
Explorer23 said:
Just flash the new OS in recovery, no need to unroot as it will get overwritten anyways. You'll need to root again after updating, of course.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
It's as easy as that? It's not a problem that I have xposed installed or anything?
What should I wipe before I install the new OS?
Sorry for all the questions, newbie here.
@Edo 91
I'm not sure about overwriting recovery, it's been a long time since I've used OOS (currently on PA, before than on LOS). If I remember correctly the recovery should stay if you DON'T boot into system right after flashing. So, flash the ROM, reboot into recovery first, then boot into system. Can't say if anything changed with Oreo, but that's how I remember it from Nougat and Marshmallow. You can however flash recovery again right after ROM, just to be sure.
You can root later down the road, no need to do everything at once.
@scalliant
Generally yes, it as easy as that. Xposed and root methods modify system partition - and that gets overwritten when you flash new ROM. That's why those modifications have to be flashed again after every update (some custom ROMs are exception, but rest assured the stock one will nuke all mods).
Anyways, we're talking about Android version upgrade here and not just a minor system update, so I'd recommend a clean installation (but you can try dirty first and then do a clean one in case you experience issues).
First of all, make a full nandroid backup (check everything except "system image" in TWRP). Copy all of your media content (pictures, videos, music ... whatever you don't wanna lose) to another device - better safe than sorry. Optionally, backup apps with Titanium or something similar.
To do it clean: wipe /system, /data and /cache. That means losing all apps and settings, but you'll keep stuff that was stored on the phone. After successfully booting into system you can restore app backups or install them and set up everything again.
To do it dirty: wipe just /system and /cache. You'll lose just system settings, but will keep apps and everything else. Less hassle, but higher chance of something going south.
Explorer23 said:
@Edo 91
To do it clean: wipe /system, /data and /cache. That means losing all apps and settings, but you'll keep stuff that was stored on the phone. After successfully booting into system you can restore app backups or install them and set up everything again.
Click to expand...
Click to collapse
I thought you loose everything when you do a clean install. So photos and files are preserved using this method? I assume text messages will be lost?
shobuddy said:
I thought you loose everything when you do a clean install. So photos and files are preserved using this method? I assume text messages will be lost?
Click to expand...
Click to collapse
Media is on a (virtually) separate partition and is preserved unless while internal storage is formated. Still, it's never a bad idea to have a backup.
Yes, text messages are lost if not backed up. There are many apps that do that (and can be set to upload to cloud regularly).
Sent from my OnePlus 3 using Tapatalk
CHANGED: You must flash the dm-verity.zip on ROM install to use the backup/restore feature of TWRP. It won't work if /data is encrypted. I jumped the gun when making this thread.
EDIT2: I had also flashed dm-verity on install so /data wasn't encrypted.
Which Dm Verity did you use which version??
Does this mean even today with the latest versions of twrp and magisk you cant restore the backups made of an encrypted phone? I just got a new Moto G7 Power and got it setup with those two things and made a backup - havnt tried restoring yet. Does your solution of flashing the dm-verify.zip thing mean the phone will be unencryped then? Because I cant have that, I rather not have backups. What about the old "adb backup" type command line does that still work?
I've had my phone since the day they were available at metro and I can't and don't even try to backup or restore anything anymore. On roms it always has broken lockscreen where you cannot secure phone. Because of this I stay encrypted and setup my **** all over again when I change roms.
flash713 said:
I've had my phone since the day they were available at metro and I can't and don't even try to backup or restore anything anymore. On roms it always has broken lockscreen where you cannot secure phone. Because of this I stay encrypted and setup my **** all over again when I change roms.
Click to expand...
Click to collapse
I see, too bad it's a nice function to backup/restore I guess I'll just backup my important data individually and try not to mess up my Rom.
TaZeR369 said:
I see, too bad it's a nice function to backup/restore I guess I'll just backup my important data individually and try not to mess up my Rom.
Click to expand...
Click to collapse
Check this out. I haven't used it yet but I'm about to try it. Join «Migrate - Custom ROM Migration Tool» on Telegram: https://t.me/migrateApp
https://forum.xda-developers.com/android/apps-games/app-migrate-custom-rom-migration-tool-t3862763
There's a new add-on for it on telegram link
TaZeR369 said:
I see, too bad it's a nice function to backup/restore I guess I'll just backup my important data individually and try not to mess up my Rom.
Click to expand...
Click to collapse
Me too. I haven't a bit of luck with encrypted stock restores. I was told it would work if you don't restore /data, but when I made a backup without /data, it failed to restore. I HAVE been able to restore unencrypted customs though. I only backed up system, data, and boot when I succeeded. It's been a while. I think you have to wait a long time for the 1st boot after the restore, as if it were rebuilding ART or something. Haven't had any luck stopping stock from encrypting either. I hate not messing up my ROM. Boring.....
Perhaps I am missing a critical detail, but I just successfully restored my latest LOS(lineage-17.1-20200524-UNOFFICIAL-ocean) & older CRD(crDroidAndroid-10.0-20200405-ocean-v6.4) backups(*) using TWRP(twrp-installer-3.3.1-2-ocean).
SELinux is NOT enforced, but "Trust"(lulz) claims the phone is encrypted.
My methodology requires installing the same base f/w I used when originally installing the ROM(former newest RETAIL for CRD & newest RETUS for LOS), root, flash copy partitions zip, flash>factory reset>1st boot of the original ROM zip, enable debug, install TWRP, boot into TWRP, wipe all & restore backup(*).
I just restored successfully 2x's on my xt1955-5.
I loaded LOS 10 & 3rds from scratch, made all my settings tweaks & made Titanium b/u(JIC), made TWRP b/u(*) then restored my previous CRD daily install using steps above. Then I repeated the above steps(again) to go back to my new, fresh LOS. It is annoying to have to reload f/w, et al, but def easier than reloading & retweaking the OS & all 3rds from scratch... Titanium fails to restore most settings + other nits.
To restore a backup(*) of a ROM I am currently running, I just boot to TWRP, wipe all & restore.
*: To make the original TWRP backup, I will run it & it will fail. I open the log file and find the last file/folder that "error"ed, delete the offender & re-run backup(boot, data & system). It works for me, no DM-verity flash required.
As always, YMMV.
Edit: PS: The problems seem to be stemming from beta testing the new "Trust"(lulz) framework, on all 10 ROMs(?). Would be nice to get that ironed out. A new Recovery wouldn't hurt, either. AFAIK, these problems exist in OFR, too.
googleverifysux said:
Perhaps I am missing a critical detail, but I just successfully restored my latest LOS(lineage-17.1-20200524-UNOFFICIAL-ocean) & older CRD(crDroidAndroid-10.0-20200405-ocean-v6.4) backups(*) using TWRP(twrp-installer-3.3.1-2-ocean).
SELinux is NOT enforced, but "Trust"(lulz) claims the phone is encrypted.
My methodology requires installing the same base f/w I used when originally installing the ROM(former newest RETAIL for CRD & newest RETUS for LOS), root, flash copy partitions zip, flash>factory reset>1st boot of the original ROM zip, enable debug, install TWRP, boot into TWRP, wipe all & restore backup(*).
I just restored successfully 2x's on my xt1955-5.
I loaded LOS 10 & 3rds from scratch, made all my settings tweaks & made Titanium b/u(JIC), made TWRP b/u(*) then restored my previous CRD daily install using steps above. Then I repeated the above steps(again) to go back to my new, fresh LOS. It is annoying to have to reload f/w, et al, but def easier than reloading & retweaking the OS & all 3rds from scratch... Titanium fails to restore most settings + other nits.
To restore a backup(*) of a ROM I am currently running, I just boot to TWRP, wipe all & restore.
*: To make the original TWRP backup, I will run it & it will fail. I open the log file and find the last file/folder that "error"ed, delete the offender & re-run backup(boot, data & system). It works for me, no DM-verity flash required.
As always, YMMV.
Edit: PS: The problems seem to be stemming from beta testing the new "Trust"(lulz) framework, on all 10 ROMs(?). Would be nice to get that ironed out. A new Recovery wouldn't hurt, either. AFAIK, these problems exist in OFR, too.
Click to expand...
Click to collapse
Have u tried the new 3.5 twrp
Lol...and here it is a couple years later and I'm still searching whether a force-encrypted twrp backup of stock has been figured out how to restore...Pulled up my own thread. Lol.
i miss being able to backup android properly. it made me behave completely differently with my phone. it was a toy instead of just some tool. i'd just install every single rom, kernel modem operating system i could find or i'd just plagiarize the hell out of you guys for sh*ts and giggles and man i loved android so much back then but now its my cell phone. :\ i just liked the colorful language, i wasn't signing anybody else's code.
it's such a tedious thing now, even compared to before and i suppose that's their intention perhaps.