Database Info

[Q]About rooting and flashing ROM (a noob asks)

i'll try to be brief:
-if i root my phone (s3 mini), will samsung updates cause problems? would you suggest that i also flash the ROM (to smth custom like cyanogenMod)
-does the utility to root the phone provide a full backup of the stock firmware and data? so, if smth goes wrong i can revert back to stock (with my apps and settings. at worst, default factory settings).
-if i flash the ROM, will i lose anything? -say- will i lose proprietary stuff like touchwiz?
-do custom ROMs use the latest android version (that's one of the reasons that i wanna root & flash: to be up to date to latest android version)?
-can custom ROMs update to newer android versions automatically? or do i have to flash again and again everytime there is a new android update?

When I rooted my Galaxy S3 the status of the phone (visible in the preferences/device info) changed to "modified" and I stopped getting updates from Samsung (when checking for updates it said that I had a modified system so I wouldn't be able to get any updates). If you flash a ROM you will indeed loose everything, including Touchwiz, but if you backup your personal data then loosing Touchwiz could be a good thing, at least it was for me. I prefer Cyanogenmod.
Flashing ROMs is frequently done because you actually want to loose all that proprietary bloatware. Custom ROMs also can give you access to the latest Android version right away, wich is a lot faster than waiting months to get last year's version through Samsung. This is one of the main reasons why I decided to flash my phone. I don't use all the "features" that Samsung implements and with Cyanogenmod 10.1 my phone feels faster and has longer battery life.
As for updating, each ROM has different ways of handling it. Cyanogenmod has OTA updates which you can access through your phone "Settings/About phone" section and it will automatically flash them for you.
wtx1033 said:
i'll try to be brief:
-if i root my phone (s3 mini), will samsung updates cause problems? would you suggest that i also flash the ROM (to smth custom like cyanogenMod)
-does the utility to root the phone provide a full backup of the stock firmware and data? so, if smth goes wrong i can revert back to stock (with my apps and settings. at worst, default factory settings).
-if i flash the ROM, will i lose anything? -say- will i lose proprietary stuff like touchwiz?
-do custom ROMs use the latest android version (that's one of the reasons that i wanna root: to be up to date to latest android version)?
-can custom ROMs update to newer android versions automatically? or do i have to flash again and again everytime there is a new android update?
Click to expand...
Click to collapse

hcengar said:
When I rooted my Galaxy S3 the status of the phone (visible in the preferences/device info) changed to "modified" and I stopped getting updates from Samsung (when checking for updates it said that I had a modified system so I wouldn't be able to get any updates). If you flash a ROM you will indeed loose everything, including Touchwiz, but if you backup your personal data then loosing Touchwiz could be a good thing, at least it was for me. I prefer Cyanogenmod.
Flashing ROMs is frequently done because you actually want to loose all that proprietary bloatware. Custom ROMs also can give you access to the latest Android version right away, wich is a lot faster than waiting months to get last year's version through Samsung. This is one of the main reasons why I decided to flash my phone. I don't use all the "features" that Samsung implements and with Cyanogenmod 10.1 my phone feels faster and has longer battery life.
As for updating, each ROM has different ways of handling it. Cyanogenmod has OTA updates which you can access through your phone "Settings/About phone" section and it will automatically flash them for you.
Click to expand...
Click to collapse
thank you
the replies were as i hoped i am gonna root and flash soon.
but i am still looking for a reply to this one:
does the utility to root the phone also provides a full backup of the stock firmware and data? so, if smth goes wrong i can revert back to stock (with my apps and settings. at worst, default factory settings).

wtx1033 said:
thank you
the replies were as i hoped i am gonna root and flash soon.
but i am still looking for a reply to this one:
does the utility to root the phone also provides a full backup of the stock firmware and data? so, if smth goes wrong i can revert back to stock (with my apps and settings. at worst, default factory settings).
Click to expand...
Click to collapse
Yes. You can use clockwork mod (cwm) to backup everything. Its recommended to take your backup using cwm before flashing a custom Rom. So that whenever you want your stock back or something with your new rom goes wrong you can revert back. You can use cwm to restore or use Odin which will make your device like when you bought it. You can restore the data alone using advance restore and your device will be like before flashing custom rom.

haridevil99 said:
Yes. You can use clockwork mod (cwm) to backup everything. Its recommended to take your backup using cwm before flashing a custom Rom. So that whenever you want your stock back or something with your new rom goes wrong you can revert back. You can use cwm to restore or use Odin which will make your device like when you bought it. You can restore the data alone using advance restore and your device will be like before flashing custom rom.
Click to expand...
Click to collapse
i guess, if smth goes bad during rooting i cannot revert back. since for backup one needs to root the device beforehand. is this right?

wtx1033 said:
i guess, if smth goes bad during rooting i cannot revert back. since for backup one needs to root the device beforehand. is this right?
Click to expand...
Click to collapse
I dont think cwm needs root access to take a backup. And you can rely on odin always if you got stock rom. So something goes wrong, Odin to the rescue.. So try taking backup with cwm first then root. Anyway if the root update was made for your device then its very very rare for things to go wrong.

Unlocked Bootloader & Rooted Questions After KitKat

As the title states I'm unlocked & rooted, but have a few questions before I start making changes to the phone.
1. Is there any advantage to using CWM as opposed to the stock recovery? The reason I ask is that the recovery is what caused me hours of trouble upgrading to KitKat. It just would not verify that I had the correct one even after flashing stock back. Is there any real disadvantage to flashing CWM to backup & recover as needed but keeping the stock recovery in other words? Or is there a way to save & flash my stock recovery back later if needed (CWM says that it is irreversible)?
2. Does anyone know a good ad blocker & how to get it running right? I used to use ROM Tool Box & never upgraded it when Google pulled that feature but apparently they shut it down as I still have the option but it won't work.
3. Anyone have a good list of apps that can be frozen/disabled in KitKat?
4. What font do you like? Been using the original Droid font for years but kinda thinking it might be time to switch it up.
Thanks for any advice and opinions you can offer!
It is greatly appreciated!
Sent from my DROID RAZR HD using xda premium

1. Being able to make backups is the big advantage. Stock recovery is basically useless aside from OTA upgrades.
2. AdAway is what I use. It's open source and you can find it in the F-Droid repository at f-droid.org
3. I'm still on CM so I'll let someone else answer this.
4. I never bothered changing fonts either.

Moto G rooted. 4.4.2 upgrade to 4.4.3 how to?

Moto G, currently running 4.4.2 unlocked and rooted with TWRP v2.6.3.0 the firmware is tweaked to my liking with GravityBox. I am also using the Faux123 to over/under clock etc.
Very happy with the performance, features and battery life.
But I am now getting bugged by the Motorola update for 4.4.3
I did try to update and the phone got into a start, reboot loop. So I have restored to my last configuration.
It's been quite sometime since I played with configuring the above and I have gone a bit blank! Can someone please outline the steps that I have to do to complete the upgrade with minimum fuss.
As a side note. I have avoided custom ROMs so far because of all the problems that I was reading about several months ago. But perhaps enough time has elapsed for me to consider going say CM11 now? I would appreciate any comments as to me going down this route. ie. Are all bugs worked out is the Moto G fully functional, does a custom ROM truly provide worthwhile benefits?
Thanks.

I would also like to know this as well as I am currently on 4.4.2 unrooted, but really feel feel like I want to start and get my Moto G rooted and up and running with all the goody's available on the community, but feel like I should wait for the 4.4.3 rollout before I start going through the whole bootloader unlocking, rooting etc.
So I will check back on this post, and thank you to the thread starter as this saves me starting a similar topic.

Rooted 4.4.2 over here as well. Unfortunately I've had no such luck finding a way to update to 4.4.3 while being rooted. I've been through a plethora of guides and suggestions but nothing seems to be working. I'll end up getting an error no matter what I do.
Don't mean to try and hijack your thread, but I've been trying to flash the .zip for the update with both CWM and TWRP but I get an error every time. Anyone have any ideas why? Do I need to configure root-requiring apps beforehand or something?

ugh...same here! Please someone figure this out!

@Kwala Baerr I was hoping for a quick 1,2,3 Guide! I miss posted the question in the General section, then moved it here. I subsequently find a few similar posts in this section. But your message suggests that you may have already tried them which worries me! Anyway I will have a go tomorrow and post here if I get success.
Sent from my Nexus 7 using Tapatalk

@grahamgo oh yea sorry. Well I've tried just about everything. I think I've narrowed down my problem to SoftKeyz messing up my SystemUI.apk so you might still have a chance. Let me know how it goes though!

grahamgo said:
Moto G, currently running 4.4.2 unlocked and rooted with TWRP v2.6.3.0 the firmware is tweaked to my liking with GravityBox. I am also using the Faux123 to over/under clock etc.
Very happy with the performance, features and battery life.
But I am now getting bugged by the Motorola update for 4.4.3
I did try to update and the phone got into a start, reboot loop. So I have restored to my last configuration.
It's been quite sometime since I played with configuring the above and I have gone a bit blank! Can someone please outline the steps that I have to do to complete the upgrade with minimum fuss.
As a side note. I have avoided custom ROMs so far because of all the problems that I was reading about several months ago. But perhaps enough time has elapsed for me to consider going say CM11 now? I would appreciate any comments as to me going down this route. ie. Are all bugs worked out is the Moto G fully functional, does a custom ROM truly provide worthwhile benefits?
Thanks.
Click to expand...
Click to collapse
Put on your phone Us firmware http://forum.xda-developers.com/showthread.php?t=2542219 setup the phone via wifi. Update is about 163mb. After that use Mototool to root the phone and fix the white screen http://forum.xda-developers.com/showthread.php?t=2635706
mabey you can do a beckup of sms https://play.google.com/store/apps/details?id=com.riteshsahu.SMSBackupRestore and https://play.google.com/store/apps/details?id=com.riteshsahu.CallLogBackupRestore
regards

I recently upgraded my stock rooted 4.4.2 Moto G to 4.4.3. The steps you have to take depends on how many modifications you've made. But basically, you need to make sure of these things:
Do a nandroid backup of your working system!
What I did:
Uninstall Xposed modules and Xposed Framework. You *must* do this through the XPosed installer itself.
Re-install/Re-enable system apps that you disabled. For me, I used Titanium Backup, and unfroze the apps that I froze. I made a mistake on my Nexus 7 and uninstalled without backup, which made this process harder.
Repeat the same for any other root apps that made changes to your /system folder.
Uninstall Busybox. If you don't know if you have it or not, download this BusyBox Installer app, and it will tell you. If it is installed, go to the bottom right of your screen and under its preferences, there is a 'delete busybox' option as seen in their 6th screenshot. The order of this is important! Some apps require BusyBox to work and do their installing/uninstalling.
Completely unroot by going to SuperSU's Settings tab, and selecting the Full Unroot option.
Download the latest version of SuperSU onto your SD card if you don't have it already.
Download 4.4.3 update and let it install.
Go into your recovery and re-install SuperSU.
Restore your old root apps like XPosed and BusyBox. I re-installed them and re-did my settings for gravity box and saved my settings using the in-app options for XPrivacy, but you might be able to use Titanium Backup for this if your settings are too extensive.
Alternately, if you're having trouble because you can't find the system apps you need or you're getting an error while updating due to something in your /system folder, you should download stock 4.4.2, extract it, and then re-flash the stock system & boot.img using fastboot or mfastboot. For my XT1034, it was in these images: system.img_sparsechunk1, system.img_sparsechunk2, system.img_sparsechunk3 + boot.img. Yours may differ depending on your model.
Note, I did not test this particular method when I upgraded, but I did use mfastboot to revert to a complete stock 4.4.2 when I changed from CM11 awhile back using this guide.
I was able to keep my bootloader unlocked, and to keep PhilZ's recovery through the update process with no issues.
Hope that helps!

tarotsujimoto said:
I recently upgraded my stock rooted 4.4.2 Moto G to 4.4.3. The steps you have to take depends on how many modifications you've made. But basically, you need to make sure of these things:
Do a nandroid backup of your working system!
What I did:
Uninstall Xposed modules and Xposed Framework. You *must* do this through the XPosed installer itself.
Re-install/Re-enable system apps that you disabled. For me, I used Titanium Backup, and unfroze the apps that I froze. I made a mistake on my Nexus 7 and uninstalled without backup, which made this process harder.
Repeat the same for any other root apps that made changes to your /system folder.
Uninstall Busybox. If you don't know if you have it or not, download this BusyBox Installer app, and it will tell you. If it is installed, go to the bottom right of your screen and under its preferences, there is a 'delete busybox' option as seen in their 6th screenshot. The order of this is important! Some apps require BusyBox to work and do their installing/uninstalling.
Completely unroot by going to SuperSU's Settings tab, and selecting the Full Unroot option.
Download the latest version of SuperSU onto your SD card if you don't have it already.
Download 4.4.3 update and let it install.
Go into your recovery and re-install SuperSU.
Restore your old root apps like XPosed and BusyBox. I re-installed them and re-did my settings for gravity box and saved my settings using the in-app options for XPrivacy, but you might be able to use Titanium Backup for this if your settings are too extensive.
Alternately, if you're having trouble because you can't find the system apps you need or you're getting an error while updating due to something in your /system folder, you should download stock 4.4.2, extract it, and then re-flash the stock system & boot.img using fastboot or mfastboot. For my XT1034, it was in these images: system.img_sparsechunk1, system.img_sparsechunk2, system.img_sparsechunk3 + boot.img. Yours may differ depending on your model.
Note, I did not test this particular method when I upgraded, but I did use mfastboot to revert to a complete stock 4.4.2 when I changed from CM11 awhile back using this guide.
I was able to keep my bootloader unlocked, and to keep PhilZ's recovery through the update process with no issues.
Hope that helps!
Click to expand...
Click to collapse
What recovery were you on?

Kwala Baerr said:
What recovery were you on?
Click to expand...
Click to collapse
Here's the thread with information on downloading & installing PhilZ Touch recovery:
http://forum.xda-developers.com/showthread.php?t=2639583
Looks like there's a new stable release out, but I still had PhilZ Touch 6.26.6 Falcon installed.

tarotsujimoto said:
I recently upgraded my stock rooted 4.4.2 Moto G to 4.4.3. The steps you have to take depends on how many modifications you've made. But basically, you need to make sure of these things:
Do a nandroid backup of your working system!
What I did:
Uninstall Xposed modules and Xposed Framework. You *must* do this through the XPosed installer itself.
Re-install/Re-enable system apps that you disabled. For me, I used Titanium Backup, and unfroze the apps that I froze. I made a mistake on my Nexus 7 and uninstalled without backup, which made this process harder.
Repeat the same for any other root apps that made changes to your /system folder.
Uninstall Busybox. If you don't know if you have it or not, download this BusyBox Installer app, and it will tell you. If it is installed, go to the bottom right of your screen and under its preferences, there is a 'delete busybox' option as seen in their 6th screenshot. The order of this is important! Some apps require BusyBox to work and do their installing/uninstalling.
Completely unroot by going to SuperSU's Settings tab, and selecting the Full Unroot option.
Download the latest version of SuperSU onto your SD card if you don't have it already.
Download 4.4.3 update and let it install.
Go into your recovery and re-install SuperSU.
Restore your old root apps like XPosed and BusyBox. I re-installed them and re-did my settings for gravity box and saved my settings using the in-app options for XPrivacy, but you might be able to use Titanium Backup for this if your settings are too extensive.
Alternately, if you're having trouble because you can't find the system apps you need or you're getting an error while updating due to something in your /system folder, you should download stock 4.4.2, extract it, and then re-flash the stock system & boot.img using fastboot or mfastboot. For my XT1034, it was in these images: system.img_sparsechunk1, system.img_sparsechunk2, system.img_sparsechunk3 + boot.img. Yours may differ depending on your model.
Note, I did not test this particular method when I upgraded, but I did use mfastboot to revert to a complete stock 4.4.2 when I changed from CM11 awhile back using this guide.
I was able to keep my bootloader unlocked, and to keep PhilZ's recovery through the update process with no issues.
Hope that helps!
Click to expand...
Click to collapse
Im rooted running stock rom and using exposed installer with gravity box and a few other modules running and all I had to do to update to 4.3.3 was to use Moto Tool AIO v3.0 to revert back to stock kitkat recovery, after that I just accepted the update, installed it, and then went back to a custom recovery. I lost none of my exposed installs or settings, took maybe 10 minutes start to finish and was painless.

tarotsujimoto said:
Here's the thread with information on downloading & installing PhilZ Touch recovery:
http://forum.xda-developers.com/showthread.php?t=2639583
Looks like there's a new stable release out, but I still had PhilZ Touch 6.26.6 Falcon installed.
Click to expand...
Click to collapse
I have just wasted a lot of time...... I tried Philz Touch 6.43.8, no go, then an earlier version, still no go. Then I found a thread saying that there were bugs in later versions, they recommended the use of 6.26.6
I tried it and it works great. However I wasted almost 2 hours finding this out.

castuis said:
Im rooted running stock rom and using exposed installer with gravity box and a few other modules running and all I had to do to update to 4.3.3 was to use Moto Tool AIO v3.0 to revert back to stock kitkat recovery, after that I just accepted the update, installed it, and then went back to a custom recovery. I lost none of my exposed installs or settings, took maybe 10 minutes start to finish and was painless.
Click to expand...
Click to collapse
I appreciate @tarotsujimoto post and I see the logic of this approach. But I too was thinking that it might be less troublesome (but maybe take longer) to go back to factory, update it to 4.4.3 and then re-install Xposed and apps + data, etc using Titanium.
@castuis I am intrigued by your mention of using a custom recovery. Could you please expand on what you backed up and if possible more details on how you did it etc.
I have wasted too much time today getting a working Philz Touch going, (maybe I should have stayed with TWRP!). But I do like the look of Philz 6.26.6 now its working. But will have to put my 4.4.3 update attempt off for a day or so.
Thanks!

Since none of the methods mentioned works for me, I have tried to extract the system.img from the original ROM archive. But how do I mount that system.img_sparsechunk files on Linux? They can not be converted by simg2img or unyaffs either ...

I had no success with any of the "short cut" methods either. I was hoping that @castuis promise of a 10 minute method would come true, but he hasn't been back to expand on his method. I myself reverted the phone to factory, let it upgrade. Then re-rooted, installed xposed and then let Google play reinstall my apps. It's definitely not a quick method. But at least it gave me a clean install. Significant frustration, caused by using Philz touch, but switched to TWRP. Finally did a system backup with Titanium. I thought that was it. Now it looks like there will be a 4.4.4 soon. I'm thinking to ignore it and wait for the next upgrade. @nodh I would wait for 4.4.4 !
Sent from my Nexus 7 using Tapatalk

I've solved my upgrade problem: I've flashed the 176.44.1 (retail Germany, 4.4.3) stock ROM, as described here. Altough I didn't flash the recovery (to restore root with the ClockWorkMod recovey) and didn't erase userdata. Now I've got the upgrade, with all my settings preserved and even rooted again.

[Q] Installed TWRP. I have questions on it's use cases.

I am new to android. I got sick of apps not being able to write to my SD card so I eventually got the guts to attempt rooting (which worked) and then I even convinced myself to try and install TWRP because I heard I can type commands in there to get my device still rooted after encrypting since superSU does not work after encryption (not tried it yet).
I updated to a new version of TWRP 2.8 I think? Any way, what kind of safety net do I have now? I am in the process of doing a fresh backup (everything ticked) with this new version of TWRP and I will trash the old one once this is done. I had zero intentions of flashing custom OS' on my Galaxy S4 mini (I9195 LTE) for fear of bricking my first ever brand new android phone.
Once this backup is created (and duplicated on every damn hard drive I have for backup purposes...) what kind of protection is this? Could I experiment with Cyanogen Mod and have no fear of it failing to load, have problems with it once installed, something go wrong and phone won't boot up? Would I be able to load my backup into TWRP and magically the phone would be in the state it is in today, rooted and everything?
If there are any things I should know I would appreciate being made aware of them before I dare proceed with any (what I assume would be potentially dangerous things) flashing custom roms etc because I want to always ensure I can get my phone to exactly the state it is now, with all my google apps still installed and everything. With everything ticked on my backup, is there anything that wouldn't be able to be restored, as in apps/data or anything?
Sorry for sounding like a noob, but as far as android and flashing is concerned, I am a noob.
tldr; Essentially I just want to be informed, as well as I can be, as to what I can now do (that I have TWRP installed and made a backup) and what I still shouldn't do, what isn't covered in a backup with all boxes ticked etc.

Morthawt said:
I am new to android. I got sick of apps not being able to write to my SD card so I eventually got the guts to attempt rooting (which worked) and then I even convinced myself to try and install TWRP because I heard I can type commands in there to get my device still rooted after encrypting since superSU does not work after encryption (not tried it yet).
I updated to a new version of TWRP 2.8 I think? Any way, what kind of safety net do I have now? I am in the process of doing a fresh backup (everything ticked) with this new version of TWRP and I will trash the old one once this is done. I had zero intentions of flashing custom OS' on my Galaxy S4 mini (I9195 LTE) for fear of bricking my first ever brand new android phone.
Once this backup is created (and duplicated on every damn hard drive I have for backup purposes...) what kind of protection is this? Could I experiment with Cyanogen Mod and have no fear of it failing to load, have problems with it once installed, something go wrong and phone won't boot up? Would I be able to load my backup into TWRP and magically the phone would be in the state it is in today, rooted and everything?
If there are any things I should know I would appreciate being made aware of them before I dare proceed with any (what I assume would be potentially dangerous things) flashing custom roms etc because I want to always ensure I can get my phone to exactly the state it is now, with all my google apps still installed and everything. With everything ticked on my backup, is there anything that wouldn't be able to be restored, as in apps/data or anything?
Sorry for sounding like a noob, but as far as android and flashing is concerned, I am a noob.
tldr; Essentially I just want to be informed, as well as I can be, as to what I can now do (that I have TWRP installed and made a backup) and what I still shouldn't do, what isn't covered in a backup with all boxes ticked etc.
Click to expand...
Click to collapse
The backup covers /system (Android OS with settings) /data (all user apps with settings) /EFS (Latest TWRP should backup this, too - MOST IMPORTANT as it stores your IMEI and baseband code) /boot (kernel) + caches (not that important)
In any case your phone has a "DOWNLOAD" mode integrated in the bootloader that will allow you to restore all partitions except "EFS" by flashing the stock firmware via ODIN. So as long as you have a EFS backup and nandroid backup and you don't screw up the phones bootloader (You could do this by flashing a firmware for another (incompatible) Samsung model via ODIN) you're on the safe side. You stock rom backup or a custom rom backup can easily be restored via TWRP. Even if TWRP brakes, you can flash it again via ODIN as long as your bootloader is fine.

LS.xD said:
The backup covers /system (Android OS with settings) /data (all user apps with settings) /EFS (Latest TWRP should backup this, too - MOST IMPORTANT as it stores your IMEI and baseband code) /boot (kernel) + caches (not that important)
In any case your phone has a "DOWNLOAD" mode integrated in the bootloader that will allow you to restore all partitions except "EFS" by flashing the stock firmware via ODIN. So as long as you have a EFS backup and nandroid backup and you don't screw up the phones bootloader (You could do this by flashing a firmware for another (incompatible) Samsung model via ODIN) you're on the safe side. You stock rom backup or a custom rom backup can easily be restored via TWRP. Even if TWRP brakes, you can flash it again via ODIN as long as your bootloader is fine.
Click to expand...
Click to collapse
Ok, so Odin is the only thing that could screw my phone up, given that I have a backup? What about if I attempt to install an incompatible rom via TWRP? Is that just as dangerous? Also if I were to some how screw up the bootloader, how would I fix that? In what circumstance might the bootloader get screwed up? From putting a custom mod on? Or is the bootloader getting screwed something specifically I would have to foolishly mess with?
If I download a cyanogen mod zip file and do the install through TWRP, would that essentially wipe everything and start completely fresh with the new OS as a virgin clean OS? Then I am correct, I hope, that if I want to get back my phone how it is now, with the stock firmware, rooted I would just do an install on TWRP and choose the backup and it would just make everything as it is currently? Even if it were screwed up and unable to boot into an OS? If that is the case, I would be a lot more open to trying different mods.
If I do try a custom rom like Cyanogen, is there an official way to get the google apps like playstore and gmail etc on it? I have seen random guides with strange links like "trust us this is a legit download!" Hmm...
Sorry for all the questions guys, I am just trying to become educated on key things before I attempt any other further things.

Morthawt said:
Ok, so Odin is the only thing that could screw my phone up, given that I have a backup? What about if I attempt to install an incompatible rom via TWRP? Is that just as dangerous? Also if I were to some how screw up the bootloader, how would I fix that? In what circumstance might the bootloader get screwed up? From putting a custom mod on? Or is the bootloader getting screwed something specifically I would have to foolishly mess with?
If I download a cyanogen mod zip file and do the install through TWRP, would that essentially wipe everything and start completely fresh with the new OS as a virgin clean OS? Then I am correct, I hope, that if I want to get back my phone how it is now, with the stock firmware, rooted I would just do an install on TWRP and choose the backup and it would just make everything as it is currently? Even if it were screwed up and unable to boot into an OS? If that is the case, I would be a lot more open to trying different mods.
If I do try a custom rom like Cyanogen, is there an official way to get the google apps like playstore and gmail etc on it? I have seen random guides with strange links like "trust us this is a legit download!" Hmm...
Sorry for all the questions guys, I am just trying to become educated on key things before I attempt any other further things.
Click to expand...
Click to collapse
Asking is good. Better safe than sorry
Yes, in case flash TWRP via ODIN, restore the backup and you should be fine.
Bootloader repair is about 40$ on ebay.
. Before flashing any new (different) rom,perform a NANDROID BACKUP" + manually internal SD Crad backup and then a FULL WIPE (/system /data /cache /dalvik cache /internal SD (Virgin like)
- If you just install a newer version of the same rom e.g. 03/01/2015 -> 03/14/2015 you only need to wipe /cache /dalvik cache (Not so virgin like)
- You can restore all apps/settings from NANDROID backups with "Titanium Backup" on your new OS
- I never heard of flashing a custom rom via recovery messed up the bootloader on Samsung phones, (In rare cases the EFS but you got the backup)
- Use only THIS GApps and make sure you pick the right version (For Android 4.4.x / 5.0.x / 5.1.x) -> Smallest (Pico bundle) will totally do it, you can install any other needed apps (also google's apps) from the pklaystore. Legit and safe.
Make sure you READ and UNDERSTOOD everything before you start flashing a custom rom.

LS.xD said:
Asking is good. Better safe than sorry
Yes, in case flash TWRP via ODIN, restore the backup and you should be fine.
Bootloader repair is about 40$ on ebay.
. Before flashing any new (different) rom,perform a NANDROID BACKUP" + manually internal SD Crad backup and then a FULL WIPE (/system /data /cache /dalvik cache /internal SD (Virgin like)
- If you just install a newer version of the same rom e.g. 03/01/2015 -> 03/14/2015 you only need to wipe /cache /dalvik cache (Not so virgin like)
- You can restore all apps/settings from NANDROID backups with "Titanium Backup" on your new OS
- I never heard of flashing a custom rom via recovery messed up the bootloader on Samsung phones, (In rare cases the EFS but you got the backup)
- Use only THIS GApps and make sure you pick the right version (For Android 4.4.x / 5.0.x / 5.1.x) -> Smallest (Pico bundle) will totally do it, you can install any other needed apps (also google's apps) from the pklaystore. Legit and safe.
Make sure you READ and UNDERSTOOD everything before you start flashing a custom rom.
Click to expand...
Click to collapse
Oh I will read everything before trying anything serious like this. I felt as if I was smashing my phone into the ground when I rooted it lol, so dangerous :S, even though I was following a guide. But now that I have all the tickboxes ticked and backed up and I have also copied that backup to 2 different hard drives... I should be safe with that.
So for my additional questions.
Is it possible but unlikely/impossible etc that a custom OS rom install through TWRP would break TWRP to the point of being non-functional to perform restores? (if so I know I could follow the guide again to install TWRP again)
Just to clarify, I should wipe everything except EFS right? When I do a completely new OS rom, perform the install and it should work or it will break. Regardless if it is broken and non functional OR it worked and I don't like it for some reason, I do the same thing again, boot to TWRP, format everything except EFS and install my backup and then the next time my phone is ready for use it will be as if nothing was ever done to it. Does that sound about right? If so, I might have an experiment with Cyanogen.
Also, you said you never heard of the bootloader being screwed over by a TWRP-based rom install. Does that also cover incorrect roms for a different model of the handset or completely different phones? I guess what I mean is, is it safe to perform an OS mod install via TWRP (in case you got the wrong one) and more dangerous to do it through odin if it is the wrong one?
I have a Samsung Galaxy S4 mini GT-I9195 LTE. I see the latest "stable" release is only version 10 of cyanogen mod? Yet there is v11 and v12 versions all without any stable release. Does that mean 11 and 12 won't work on my S4 mini or that it would be a mistake to install it on my phone? Or is there a method I can tell which one would be the best one to get for my phone (newest best)?
Lastly, as for odin, since I have TWRP and a backup of my phone as it is now, is there any reason to use odin for anything other than maybe reinstalling TWRP? If so, what else would require me to use odin that TWRP couldn't do?
Thanks so much for answering my questions, it is really making me feel more confident with the whole process. I don't like going into things blind, I'm a computer techie and like to know what I am doing and why I am doing it. This phone customization business is entirely new to me beyond changing settings and themes lol.

Is it possible but unlikely/impossible etc that a custom OS rom install through TWRP would break TWRP to the point of being non-functional to perform restores? (if so I know I could follow the guide again to install TWRP again)
--> You could flash a wrong zip containing a recovery (Probably you will not do)
Just to clarify, I should wipe everything except EFS right? When I do a completely new OS rom, perform the install and it should work or it will break. Regardless if it is broken and non functional OR it worked and I don't like it for some reason, I do the same thing again, boot to TWRP, format everything except EFS and install my backup and then the next time my phone is ready for use it will be as if nothing was ever done to it. Does that sound about right? If so, I might have an experiment with Cyanogen.
--> Yes
Also, you said you never heard of the bootloader being screwed over by a TWRP-based rom install. Does that also cover incorrect roms for a different model of the handset or completely different phones? I guess what I mean is, is it safe to perform an OS mod install via TWRP (in case you got the wrong one) and more dangerous to do it through odin if it is the wrong one?
--> Every rom has an updater-script that (normally) checks the compatiblity before TWRP installs it
I have a Samsung Galaxy S4 mini GT-I9195 LTE. I see the latest "stable" release is only version 10 of cyanogen mod? Yet there is v11 and v12 versions all without any stable release. Does that mean 11 and 12 won't work on my S4 mini or that it would be a mistake to install it on my phone? Or is there a method I can tell which one would be the best one to get for my phone (newest best)?
--> Stable means NO BUGS, Nightlies are updated nearly every day with the latest commits as they are in development status. May or may not contain bugs. Check out the specific rom thread on xda. Stability of the rom / bugs are discussed there by the users every day. So you can check out which version will work.
Lastly, as for odin, since I have TWRP and a backup of my phone as it is now, is there any reason to use odin for anything other than maybe reinstalling TWRP? If so, what else would require me to use odin that TWRP couldn't do?
--> Restore the phone to fully stock firmware. Such official firmware can be found at SamMobile.com
And most important: Press "thanks" at the botom of my posts

(had to remove quotes due to outside links preventing my posting.)
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
Thanks button pressed on them, because truly your information is extremely helpful.

If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
--> TWRP will be replaced by the stock recovery. You can instantly flash TWRP again.
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
--> Your phone got enough permorfance to handle any kind of android version available. Bugs and performance are rom related.

LS.xD said:
If I were to flash a stock firmware rom with odin, would it destroy TWRP? At which point I could flash it back on again? Or would TWRP still be there?
--> TWRP will be replaced by the stock recovery. You can instantly flash TWRP again.
I think I am going to actually try Cyanogen, once I decide on a build to try. Are there any "minimum requirements" for cyanogen major versions? Like I could see I shouldn't install CM12 on my S4 mini and should instead try ones prior to 12? Or is it pretty much just a features and updates thing and 12 would work just as effectively (in terms of just "working smoothly" discounting any bugs etc) as 10?
--> Your phone got enough permorfance to handle any kind of android version available. Bugs and performance are rom related.
Click to expand...
Click to collapse
So when they say 5.x isn't coming to the S4 mini, that's a sales thing only?! Not based on performance limitations of my phone's hardware?
EDIT: Should I wipe Preload?

Morthawt said:
So when they say 5.x isn't coming to the S4 mini, that's a sales thing only?! Not based on performance limitations of my phone's hardware?
Click to expand...
Click to collapse
Just like that. I use 5.x on both of my phones
Galaxy Ace II -> performance is okay, with 4.4.4 it runs as hell, better than ever with stock firmware [Last official Android is 4.1]
HTC One S -> Flying on a Lollipop [Last official Android is 4.1]

LS.xD said:
Just like that. I use 5.x on both of my phones
Galaxy Ace II -> performance is okay, with 4.4.4 it runs as hell, better than ever with stock firmware [Last official Android is 4.1]
HTC One S -> Flying on a Lollipop [Last official Android is 4.1]
Click to expand...
Click to collapse
I am having trouble finding any specific information about the S4 mini LTE and CM12. I don't know if I should try the last version of CM11 instead? Not sure to try a CM12 or CM11 at the moment. I am sat here ready to perform the wipe but I just can't make my mind up which to try :|
Which reminds me, if I use the latest CM11, will there be any further security updates and things? Or are updates only on the nightlies? I would hope they will update CM11, I'd hate to think the only way you get updates is on the bleeding unstable edge :S ?

Morthawt said:
I am having trouble finding any specific information about the S4 mini LTE and CM12. I don't know if I should try the last version of CM11 instead? Not sure to try a CM12 or CM11 at the moment. I am sat here ready to perform the wipe but I just can't make my mind up which to try :|
Which reminds me, if I use the latest CM11, will there be any further security updates and things? Or are updates only on the nightlies? I would hope they will update CM11, I'd hate to think the only way you get updates is on the bleeding unstable edge :S ?
Click to expand...
Click to collapse
Possible security issues can be fixed later by modules. By the way, stock firmware is also updated just a few times and stays at this state. If you want as less trouble as possible a CM11 variant will be more sensefull for your purpose. Feel free to get some more informations HERE

LS.xD said:
Possible security issues can be fixed later by modules. By the way, stock firmware is also updated just a few times and stays at this state. If you want as less trouble as possible a CM11 variant will be more sensefull for your purpose. Feel free to get some more informations HERE
Click to expand...
Click to collapse
I am on the latest CM11 snapshot Amazing! Although I am confused by some of the options. Is there any documentation on the OS? I see for Network modes things like "2G | 3G", or "2G | 2G + 3G" and "2G | 3G | 2G + 3G" . I pretty much can assume I know that 2G | 3G means 2 or 3G but when it comes to ones with +'s that is just confusing. 2G and 3G at the same time? No idea lol.

Unfortunately the compass sensor does not work. I may have to either risk trying a CM12 or go to CM10 :/ What would you recommend?

Morthawt said:
Unfortunately the compass sensor does not work. I may have to either risk trying a CM12 or go to CM10 :/ What would you recommend?
Click to expand...
Click to collapse
2G = GSM Data
3G = UMTS / HDPA / WCDMA Data
Do you often need the compass sensor?
SlimKAT is a fast, lightweight rom and should be working.

LS.xD said:
2G = GSM Data
3G = UMTS / HDPA / WCDMA Data
Do you often need the compass sensor?
Click to expand...
Click to collapse
Not always but when I am using offline navigation software, it is very handy to see realtime if I am pointed in the right direction instead of having to wait for enough distance to be detected to determine what way I am pointing. I don't like limitations. Period. That is the root of why I am messing with... well, root and roms. I could not use software to write to my SD card because of some security "enhancement" which just crippled the functionality of having an android phone. First I rooted and used SDFIX or what ever it is, now I am testing roms to see if I can find a good one. I have the latest (this year) stable AICP installing and gaps currently. I will give this one a whirl and see what I think. I was disappointed that I could not find a nice "Hey.. this is why you should choose our rom!" page. Nothing. Just a download link and ability to get the source code.
I want to read about all the amazing reasons and features why AICP (or any rom for that matter) is a great choice. But I found no such page.

Morthawt said:
Not always but when I am using offline navigation software, it is very handy to see realtime if I am pointed in the right direction instead of having to wait for enough distance to be detected to determine what way I am pointing. I don't like limitations. Period. That is the root of why I am messing with... well, root and roms. I could not use software to write to my SD card because of some security "enhancement" which just crippled the functionality of having an android phone. First I rooted and used SDFIX or what ever it is, now I am testing roms to see if I can find a good one. I have the latest (this year) stable AICP installing and gaps currently. I will give this one a whirl and see what I think. I was disappointed that I could not find a nice "Hey.. this is why you should choose our rom!" page. Nothing. Just a download link and ability to get the source code.
I want to read about all the amazing reasons and features why AICP (or any rom for that matter) is a great choice. But I found no such page.
Click to expand...
Click to collapse
If you can't find any custom rom that fits your needs, you can also choose a modified (debloated) stock firmware if you need 100% functionality.

LS.xD said:
If you can't find any custom rom that fits your needs, you can also choose a modified (debloated) stock firmware if you need 100% functionality.
Click to expand...
Click to collapse
Those exist in the TWRP zip format? Where can I find those?

Morthawt said:
Those exist in the TWRP zip format? Where can I find those?
Click to expand...
Click to collapse
I should have read before I answered Seems not to exist for your phone. I don't know the reason.

Migrating from one M8 to another - sanity check

Sup guys,
I've rooted every phone I've had, but I do it so infrequently that I always have to refresh my memory with it. Current situation is that I have a rooted M8 running mostly stock 4.4.4 ROM, but with a bunch of Xposed mods and a few system tweaks - it's dialed in just the way I want it, but the screen is separating so I've got my hands on another M8 running 4.4.2. I basically want to get the 4.4.2 M8 to the state of my 4.4.4 device. I've already made a complete backup ROM from the 4.4.4 phone and I want to restore that ROM to the 4.4.2 device. With the 4.4.2 device, I plan to:
S-Off (Try Firewater. May or may not work. If doesn't work, try Sunshine)
Install recovery - CWM or TWRP
Flash Super SU
Update firmware from 4.4.2 to 4.4.4 from here: http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
Flash my complete backup ROM from my current device
Sanity check? Am I missing anything here? When I rooted my current M8 (4.4.2), weaksauce actually worked, and I flashed CWM recovery and Super SU by placing them on the SD card. That is what I plan to do again since that was so easy. Recommendations?
Cheers guys!

j006 said:
Sup guys,
I've rooted every phone I've had, but I do it so infrequently that I always have to refresh my memory with it. Current situation is that I have a rooted M8 running mostly stock 4.4.4 ROM, but with a bunch of Xposed mods and a few system tweaks - it's dialed in just the way I want it, but the screen is separating so I've got my hands on another M8 running 4.4.2. I basically want to get the 4.4.2 M8 to the state of my 4.4.4 device. I've already made a complete backup ROM from the 4.4.4 phone and I want to restore that ROM to the 4.4.2 device. With the 4.4.2 device, I plan to:
S-Off (Try Firewater. May or may not work. If doesn't work, try Sunshine)
Install recovery - CWM or TWRP
Flash Super SU
Update firmware from 4.4.2 to 4.4.4 from here: http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
Flash my complete backup ROM from my current device
Sanity check? Am I missing anything here? When I rooted my current M8 (4.4.2), weaksauce actually worked, and I flashed CWM recovery and Super SU by placing them on the SD card. That is what I plan to do again since that was so easy. Recommendations?
Cheers guys!
Click to expand...
Click to collapse
firewater sever is taken down, even if you have an old version of it laying around it is useless.. you must pay for sunshine.
but other than that everything looks good.
you have your nandroid backup, on the new m8, s-off using sunshine, then update the firmware from 442 to 444, then flash custom recovery (TWRP is recommended), and then wipe and restore the nandroid and you should be good to go. :good:
(no need to flash supersu as the ROM you have backed up using nandroid is already rooted)

Many thanks! A couple of years ago when I did this I remember it being fairly straightforward. Do you personally find any real benefit in upgrading to one of the Lollipop ROMs this go 'round? Seems like it's more trouble than what you gain, though I may be uninformed of course..
Cheers!

j006 said:
Many thanks! A couple of years ago when I did this I remember it being fairly straightforward. Do you personally find any real benefit in upgrading to one of the Lollipop ROMs this go 'round? Seems like it's more trouble than what you gain, though I may be uninformed of course..
Cheers!
Click to expand...
Click to collapse
I find many benefits to LP over KK personally.
If you like a stock ROM we have stock based LP ROMs, and firmware.zip you can flash and you are up an running a stock LP ROM within 10 minutes. Sure you need to set things up, but most can be backed up and if you take some screen shots of everything it's pretty easy to get everything set up to your liking.
If you want some customization there are ROMs like mine, that come mostly stock with some benefits like root, busybox, etc, and then offer you a MOD Pack.
See ROM thread here
If you want to customize pretty much every aspect of the ROM you have Venom at your fingertips.
Venom ROM thread
There is the benefit of having all the security updates with the newest firmware.
We also have Marshmallow 6.0 ROMs out already that are rock solid.
A Google Play Edition ROM found here
And a Sense based ROM found here
You can also run some Sense 7 ROMs that are very stable, you can find one in my linked thread posted above, and in the Development area.
I personally would try things out, that's the great benefit of root/s-off/custom recovery/ROMs
You can always make a nandroid backup of your current ROM, and flash the older firmware to get right back where you left off.
Best of luck, enjoy your flashings