Related
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.
Hi!
I'm new to this forums. I was led here by the people from another forums (LinusTechTips) since I was asking for help about rooting and modding my Samsung Galaxy S4.
Now, I really don't know anything about rooting or modding, but I just realized that my phone is starting to go slow, and there are some bloatwares I do not really use. I heard that if I root and mod my phone, all the bloatware can be erased and I will be able to have more space in my phone.
Can someone please link me or teach me how to root and mod my Samsung Galaxy S4? I've been reading around, but I am scared that the thread I am following is either out of date, or would not turn out well, so if you do have the time, please do help me!
Thanks!
Yours,
Veridisduo
Hey veris, i have a s4 GT-i9505 and i recently rooted it. First... did you get it by carrier? Just youtube this ( GT-i9505 (LTE, ATNT etc.) Root (Android version) sorry for bad english.
Yours, Jan
Veridisduo said:
Hi!
I'm new to this forums. I was led here by the people from another forums (LinusTechTips) since I was asking for help about rooting and modding my Samsung Galaxy S4.
Now, I really don't know anything about rooting or modding, but I just realized that my phone is starting to go slow, and there are some bloatwares I do not really use. I heard that if I root and mod my phone, all the bloatware can be erased and I will be able to have more space in my phone.
Can someone please link me or teach me how to root and mod my Samsung Galaxy S4? I've been reading around, but I am scared that the thread I am following is either out of date, or would not turn out well, so if you do have the time, please do help me!
Thanks!
Yours,
Veridisduo
Click to expand...
Click to collapse
Easiest way to root your phone is with Chainfire Autoroot.
Deleting system bloatware won't really free up space. The System partition is a set size, so while deleting some apps will free up space in that partition, it won't give you extra space for, say, games or photos or music or other non-system stuff. Any extra space will be minimal anyway. It's also dangerous to do if you don't know what you're doing. Read, read, and read.
If you install custom recovery, such as TWRP (easy to do on this phone after rooting), you can however flash custom ROMs. This includes ROMs like CyanogenMod that are based on stock Android, and also customized Samsung TouchWiz ROMs that have been modified and typically de-bloated like you wish to do with your phone. Omega and Hyperdrive are probably the most popular modified TouchWiz ROMs for the S4. Custom recovery is an essential life-saver for learning about root and ROMs, because it allows you to make an exact backup, so when you screw something up (and you will, we all do, it's all part of the learning process) all you have to do is restore the backup.
There's plenty of youtube videos that'll walk you through the processes, but the best thing to do is read, read, and read. Educate yourself not just so you know what to do, but why you're doing it.
NeoNyte said:
Hey veris, i have a s4 GT-i9505 and i recently rooted it. First... did you get it by carrier? Just youtube this ( GT-i9505 (LTE, ATNT etc.) Root (Android version) sorry for bad english.
Yours, Jan
Click to expand...
Click to collapse
Hi! How would I know what carrier I got it from?
I am from the Philippines and so, I didn't get it from ATNT or whatever carrier you mean. Sorry if I don't get it!
Planterz said:
Easiest way to root your phone is with Chainfire Autoroot.
Deleting system bloatware won't really free up space. The System partition is a set size, so while deleting some apps will free up space in that partition, it won't give you extra space for, say, games or photos or music or other non-system stuff. Any extra space will be minimal anyway. It's also dangerous to do if you don't know what you're doing. Read, read, and read.
If you install custom recovery, such as TWRP (easy to do on this phone after rooting), you can however flash custom ROMs. This includes ROMs like CyanogenMod that are based on stock Android, and also customized Samsung TouchWiz ROMs that have been modified and typically de-bloated like you wish to do with your phone. Omega and Hyperdrive are probably the most popular modified TouchWiz ROMs for the S4. Custom recovery is an essential life-saver for learning about root and ROMs, because it allows you to make an exact backup, so when you screw something up (and you will, we all do, it's all part of the learning process) all you have to do is restore the backup.
There's plenty of youtube videos that'll walk you through the processes, but the best thing to do is read, read, and read. Educate yourself not just so you know what to do, but why you're doing it.
Click to expand...
Click to collapse
Hello!
First of all, I would like to thank you for your lengthy reply about my post. I really appreciate it a lot.
If I use the Chainfire Autoroot, it would do no harm with my files, am I right? (Well, I will of course back it up, but just to make sure!)
Next, what is custom recovery? Should I install this first before doing any mods?
I have heard about CyanogenMod (was thinking of modding my phone to it). What are TouchWiz ROMS though? Oh and other than CyanogenMod, are there any other mods that are nice to try out there? Would be nice to try something nice.
Sorry I ask too much question!
Veridisduo said:
Hello!
First of all, I would like to thank you for your lengthy reply about my post. I really appreciate it a lot.
If I use the Chainfire Autoroot, it would do no harm with my files, am I right? (Well, I will of course back it up, but just to make sure!)
Click to expand...
Click to collapse
It's my understanding that as long as you're not using encryption, your data won't be wiped. But definitely back your stuff up first.
Next, what is custom recovery? Should I install this first before doing any mods?
Click to expand...
Click to collapse
Recovery is sorta like the BIOS menu on a computer. The stock recovery on a Samsung gives you the options reboot, clear your data or cache, or do a factory reset. Custom recoveries allow you to flash things like ROMs, kernels, modem firmwares, as well as do full back-up and restores. The wiping options differentiate between storage and the ROM, so when flashing ROMs, you can choose not to wipe your data (music, pictures, etc). The most popular and easy to use custom recovery is Team Win Recovery Project (TWRP). There's an app you can download from the Play Store that will install it for you (and update) once you're rooted. A custom recovery is an indispensable tool for modding your phone, and fixing it when you screw something up. Read up on TWRP and its capabilities before doing anything drastic with it.
I have heard about CyanogenMod (was thinking of modding my phone to it). What are TouchWiz ROMS though? Oh and other than CyanogenMod, are there any other mods that are nice to try out there? Would be nice to try something nice.
Click to expand...
Click to collapse
CyanogenMod is by far the most popular custom ROM. It's very close to stock (ie: Nexus) Android, with some very useful features added without bogging the phone down with tones of useless crap. Many other custom ROMs borrow from CM, many built upon it and borrow from other custom ROMs. Personally, I think there's better ROMs out there than CyanogenMod, but that's a personal preference, and CM is a good place to start for anybody venturing into custom ROMs.
TouchWiz is what Samsung calls their UI. It'll be the stock ROM on the device. As I mentioned, Omega and Hyperdrive are examples of customized TouchWiz ROMs. They're tweaked for performance, some useless/unwanted features removed (like KNOX), often they port over features from newer or more powerful Samsung devices; it's possible to get features from the Note series and the S5 and S6 on your older S4 this way. They can also add other UI tweaks like expanded reboot menus, audio mods, visual tweaks, etc. The main advantage for using a customized TouchWiz ROM is that it'll be familiar, yet greatly improved.
Apart from that, custom kernels are fun to play with too. I use Koontz kernel on my S4. The kernel, simplistically put, is a bit of software that tells the operating system (ROM) how to use the hardware. This includes everything from the screen and buttons and speakers to the CPU, GPU, and RAM. A custom kernel can give you options like overclocking, undervolting (to save battery), adding touch-wake options, screen calibration, etc. Koontz is a very adjustable kernel. Messing with kernel options can be very risky though, so do your research before making any changes (and do a back-up!)
Sorry I ask too much question!
Click to expand...
Click to collapse
No problem! We're all here to learn and help others learn.
Planterz said:
It's my understanding that as long as you're not using encryption, your data won't be wiped. But definitely back your stuff up first.
Recovery is sorta like the BIOS menu on a computer. The stock recovery on a Samsung gives you the options reboot, clear your data or cache, or do a factory reset. Custom recoveries allow you to flash things like ROMs, kernels, modem firmwares, as well as do full back-up and restores. The wiping options differentiate between storage and the ROM, so when flashing ROMs, you can choose not to wipe your data (music, pictures, etc). The most popular and easy to use custom recovery is Team Win Recovery Project (TWRP). There's an app you can download from the Play Store that will install it for you (and update) once you're rooted. A custom recovery is an indispensable tool for modding your phone, and fixing it when you screw something up. Read up on TWRP and its capabilities before doing anything drastic with it.
CyanogenMod is by far the most popular custom ROM. It's very close to stock (ie: Nexus) Android, with some very useful features added without bogging the phone down with tones of useless crap. Many other custom ROMs borrow from CM, many built upon it and borrow from other custom ROMs. Personally, I think there's better ROMs out there than CyanogenMod, but that's a personal preference, and CM is a good place to start for anybody venturing into custom ROMs.
TouchWiz is what Samsung calls their UI. It'll be the stock ROM on the device. As I mentioned, Omega and Hyperdrive are examples of customized TouchWiz ROMs. They're tweaked for performance, some useless/unwanted features removed (like KNOX), often they port over features from newer or more powerful Samsung devices; it's possible to get features from the Note series and the S5 and S6 on your older S4 this way. They can also add other UI tweaks like expanded reboot menus, audio mods, visual tweaks, etc. The main advantage for using a customized TouchWiz ROM is that it'll be familiar, yet greatly improved.
Apart from that, custom kernels are fun to play with too. I use Koontz kernel on my S4. The kernel, simplistically put, is a bit of software that tells the operating system (ROM) how to use the hardware. This includes everything from the screen and buttons and speakers to the CPU, GPU, and RAM. A custom kernel can give you options like overclocking, undervolting (to save battery), adding touch-wake options, screen calibration, etc. Koontz is a very adjustable kernel. Messing with kernel options can be very risky though, so do your research before making any changes (and do a back-up!)
No problem! We're all here to learn and help others learn.
Click to expand...
Click to collapse
Awesome! Thanks a lot again!
It seems you have lots of knowledge on the S4, and since you have the same phone as I do, would it be okay if I just message you up instead of posting all my questions here?
Veridisduo said:
Awesome! Thanks a lot again!
It seems you have lots of knowledge on the S4, and since you have the same phone as I do, would it be okay if I just message you up instead of posting all my questions here?
Click to expand...
Click to collapse
Honestly, I'm not particularly knowledgeable about the S4; what I know is fairly basic and I'm relatively inexperienced with modifying this specific device. I got mine for $70, and after rooting and flashing TWRP, I tried a couple ROMs, found a custom kernel, and basically haven't really messed around with anything else for months. My S4 is not my primary device, that'd be my OnePlus One. Mainly I use the S4 as a mobile hotspot and to USB tether to my computer for home internet, since the battery is removable and I can use it for that purpose without ruining my OnePlus One (running a constant hotspot destroys batteries) .
Feel free to PM me, but it might be more prudent just to keep it public so anyone searching for the same answers can find them here, and if I can't answer them, someone else can. Right now though, it's bed time, then I'm off to work so don't think that I'm ignoring you if I don't answer in the next 20 hours or so.
THIS ISSUE IS FIXED
..so who rated it 1?
Thanks to @gilby2704 for telling me about the kernel fix and @pakrett-bm for creating it.
I fixed it by doing the following:
Wiping Dalvik/ART Cache, Data, System, and Cache.
Flashing the ROM (Resurrection Remix).
Flashing the kernel fix.
Restoring Tee, NVData, and NVRam from my TWRP backup.
---
I hope this helps someone, and that I didn't type that for no reason. Thanks again to the people who helped me not have to buy a new phone.
Old post:
Code:
I've flashed a couple of different ROMs, all of which are based off Nougat 7.1.2, including [URL="https://forum.xda-developers.com/android/development/micromax-canvas-5-e481-ressurection-t3667680"]Resurrection Remix[/URL] and [URL="https://forum.xda-developers.com/android/development/crdroid-v3-5-micromax-canvas-5-e481-t3685656"]crDROID[/URL], originally designed for the Micromax Canvas 5. Both of those worked fine, though a LineageOS 14.1 port to the Elephone P8000 bootlooped my device until I managed to get into recovery by accident.
However, both RR and crDROID aren't registering my SIM card. I'm not sure how I could go about fixing this, if anyone could provide some help I'd appreciate it.
Some ideas I've had are to:
[LIST]
[*]Flash a boot.img from [URL="https://forum.xda-developers.com/general/device-reviews-and-information/blu-life-one-x-2016-porting-resources-t3385109#post74342084"]here[/URL],
[*]flash a kernel made for this device,
[*]flash a radio.img / modem.bin for this device,
[*]or reflash the stock ROM.
[/LIST]
The only problems with the above options are:
[LIST]
[*]I'm not sure if I can just flash a boot.img and not brick my phone,
[*]I can't find a kernel for this device,
[*]I can't find a radio/modem file for this device,
[*]and reflashing the stock ROM didn't work correctly, though I only tried it once.
[/LIST]
As I've already said, all help is appreciated.
Thanks, and good day.
- Awanonimik
Awanonimik said:
I fixed it by doing the following:
Wiping Dalvik/ART Cache, Data, System, and Cache.
Flashing the ROM (Resurrection Remix).
Flashing the kernel fix.
Restoring Tee, NVData, and NVRam from my TWRP backup.
- Awanonimik
Click to expand...
Click to collapse
Which TWRP version did you use? I'm on 2.8.7.0 I haven't touched fastboot since two years ago...
Also did u restore Tee1 and Tee2, or just one of them? Have you faced any bugs in the remix rom? Stock rom is rock solid for me, usually go 30-60days or more between reboots. And screen on time? Stock gives me 5-7hrs.
Sorry for all the questions. Just want to make sure I get this done right. Thanks in advance.
BereiBlue said:
Which TWRP version did you use? I'm on 2.8.7.0 I haven't touched fastboot since two years ago...
Also did u restore Tee1 and Tee2, or just one of them? Have you faced any bugs in the remix rom? Stock rom is rock solid for me, usually go 30-60days or more between reboots. And screen on time? Stock gives me 5-7hrs.
Sorry for all the questions. Just want to make sure I get this done right. Thanks in advance.
Click to expand...
Click to collapse
Check my other posts for more details; in case you don't know where you found this thread: https://forum.xda-developers.com/t/blu-life-onex2016
I'm actually unsure of the version of TWRP I'm using, I'll attach it in the post. "twrpmat.img" is the one that I boot with RR on 7.1.2, it's a material version that I renamed and I don't have my phone with me; I think it's the latest one from the main post. From the stock marshmallow ROM I booted "twrp.img", don't ask me what version that is. I couldn't get the other versions to boot, but it could've just been something I did and it didn't damage my device in any way - it just failed to boot into it, restarted, and attempted to boot to system.
I restored both Tee1 and Tee2.
As for bugs, it could've been just something I did, but occasionally my apps just stop working; usually it's the ones that access the internet. "Updating" the app works - I just extract the apk and install it, without uninstalling. You don't have to have the apk beforehand, it fixes itself if you update the package at all, even if you don't make changes. It's likely that this is a glitch caused by not having Gapps installed, however.
Reboot wise, I have no idea - I'm constantly changing things so I reboot a lot. I haven't experienced any major system crashes though, sometimes when I do weird stuff the UI randomly reboots.
I also couldn't tell you about screen on time, since when I'm doing things I generally have it on the charger, and I have all sorts of things on it that run constantly, including OpenVPN, which I imagine drains battery like a mother****er. Without Gapps installed it probably has more than stock, though.
I don't mind the questions at all, happy to help. Feel free to ask more if need be, but be warned that I'm not on here all that often.
Cheers,
Tazeki.
Just after a bit of advice of possible. Firstly I am fairly new to the a/b slot part of flashing and haven't really managed to fully get my head around installing a backup from twrp or going back to stock rom from a custom ROM. Each time I have tried I have usually end up with an encrypted device in twrp (jumbled letters). Please could somebody explain or point me in the direction of a thread explaining how (I have looked but haven't really found anything). I know that flashing a custom you wipe days and not system as we used to do. Is reverting to stock the same process?
I know we don't have a complete implementation of recoveries, like twrp/of (I know it's basically the same), yet. But now that we have the kernel source, what is still missing (vendor?)?
Also and kinda of a similar question, what is still missing regarding a "normal" flashing process? Like wipe system, data, dalvik/art, cache, flash rom and not having to have a base stock firmware and needing to format data.
To be honest, I'm a bit confused with this phone. My other phones (admittedly last one's didn't get past Android 9), were so different in that regard.
So I'd really appreciate if someone could take the time to shed some light on this.
Maybe we'll see a stable version of twrp for surya but support for dynamic partitions will not be available soon.
Having to format data everytime you flash a new rom may be solved having the kernel source. I think it has to do with encryption keys. Even if you don't have any password set in the OS, miui still generates keys to encrypt the data and when you wipe only, they get deleted hence, data on the internal nemeory remains encrypted. That's what I think.
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Ok, to be honest and judging by the fact that the announcement by Dees_Troy was over a year ago, things look pretty difficult to say the least.
I had my last phone (axon7) for so long that all the new implementations, like dynamic linking and super partition, weren't really on my radar.
Guess I was a little naive in thinking that the kernel source would be of any help in that regard.
This lack of stable time-tested solutions worries me, too.
That's the main reason why I'm still on stock ROM on the Poco and the Axon 7 is still my daily driver.
.
pnin said:
This lack of stable time-tested solutions worries me, too.
That's the main reason why I'm still on stock ROM on the Poco and the Axon 7 is still my daily driver.
.
Click to expand...
Click to collapse
How about EU ROM ?
Thanks for your thread.
I'm asking too.
I went from an old device too (redmi note 4 mido), and i'm a bit lost on flashing process.
Is it possible to :
Install orangefox via fastboot.
Wipe all & format data.
Flash recommend firmware for rom.
Flash custom rom.
Flash gapps.
And boot ?
Any problem with that ? What i'm missing ?
Don't have phone now, I'm waiting for shipping, and will wait for unlock bootloader access. I hope it will more clear and simple when I will discover poco x3.
You can do all those things. What you can't do for example is make a backup and restore your current custom rom.
Oh ok.
Sorry, miss understood your op post.
I was confused because on some custom roms thread, I find strange install instructions, like : dont wipe anything, format data AFTER flash custom roms...
Somes roms requires frimware 12.0.3. What about if phone have a more recent ? Can I downgrade just by flash fw+vendor on recovery before flash rom ?
And some people said they have bricked there devices.
Just to be sure to don't make stupid error on fresh new device, that I can't solve with miflash and fastboot.
Thank you for your reply.
I only clean flash roms, never backup, don't have a lot of apps, and majority have import/export options in-app.
But I hope for you it will be fixed soon.
atifnr said:
How about EU ROM ?
Click to expand...
Click to collapse
As @[armitage] pointed, it doesn't enable nandroid backups that I know of.
.