hey there,
I have a rooted One Mini which runs on Android 4.3 at the moment. A few days ago, I have recieved the update info for Kitkat 4.4.2.
Now I know that I can not use the regular update on a rooted phone and for the time beeing, I don't even feel the need to upgrade. However, I was wondering about the general problem:
First, I thought about doing a full backup (Nandroid), then flashing back to stock, getting the official update and then flashing the nandroid backup back. However, I realized that makes no sense, since a nandroid backup contains all partitions and therefore would simply overwrite the updated system...right?
Now the question is: what is the most convenient way to stay updated on a rooted phone? Do I really need to flash back to stock, do the update and then go through the root process again each time?
thanks for any info and clarifying!
brokaaa
normally the devs here are much faster in providing an updated ROM then many carriers are with giving you an OTA
I'd go back to stock and take the update. 4.3 was a mistake in my opinion. Att skipped it completely and went from 4.2.2 to 4.4.2 all in one update. Lol or just flash cm11 which is a better choice yet seeing as its already pretty stable and very fast.
Sent from my One Mini using Tapatalk
Hello Everyone,
New member, longtime lurker here. I have a I535 Verizon GS3, and am rooted. It has been quite a while since I did that, and I just wanted to make sure I knew what I was getting into before I tried to upgrade to a newer rom. The reason I want to upgrade is I currently have a Sony Smartwatch 2, that I love but I shattered the screen. In preparation to buy one of the new Android wearables, I need to be on a newer version of android as far as I can see.
Right now I am on: 4.1.2/ Baseband version, I535VRBMB1/ Kernel Version 3.031-86103/Build number JZO54K.I535VRBMB1
I am not sure what of that info is important so I posted it all. I don't remember the exact name of the rom I flashed before, but I think it was created by member Dalep, and it was something like "Stock Rooted". It was basically just a rooted version of the stock rom. My only reason for rooting was to use a wifi tethering app which has been working well for me. I was nervous with the initial rooting and flash process, so once I got what I needed I stopped working on it and used my phone as is until now. Now I would like some guidance on how to get my phone safely up to date.
1. I am running Clockwork Mod Recovery v6.0.2.3. Is this still usable or do I need to update it?
2. What rom would you all recommend for someone who wants a fairly stable phone and does not care so much about tinkering/customizing?
3. What does a nandroid backup do and what can I do with the backup (I did one before I installed this current rom)
4. What is the best way to get my phone back with the apps I have installed? (i.e. reinstall from Playstore, etc) I don't have many apps.
I am sure there will be more questions, but thank you for reading my long first post, I just want to make sure I am clear about my current state, skill level and intentions.
Thanks,
Victor
Update recovery to latest version of whichever recovery you prefer. I use TWRP. Flash the MF1 firmware and ML1 modem in that order. This will bring you as far up to date as possible without locking down the phone. Then you can flash any rom currently available. I run stock deodexed ML1 4.3 base and then mod it the way I want it. Scott has one in the rom threads. As far as nandroid it will make an image of your current setup in case you need to return due to problems or trying some other rom. There are several options for backing up apps such as TIBU, My Backup or even Google can restore your apps. Here is firmware and modem. Flash MF1 first and ML1 second. ML1 will replace the MF1 modem but leave rest of firmware (bootchain) at MF1 level and will retain root and unlock status.
Flash in recovery in order posted:
#1- MF1 Firmware -- http://www.androidfilehost.com/?fid=23329332407591785
#2- ML1 Modem -- http://www.androidfilehost.com/?fid=23329332407591786
Thanks for the response, I will flash those and check out that rom
Hi everyone,
So, not sure if I have a unique situation here, but have looked through the forums and haven't found any that seemed to answer my question. Sorry if there's a duplicate situation posted elsewhere. My level is pretty noob...I do pretty much only the basics. I understand about half of what I read, hahaha. Previously had a Verizon Galaxy Nexus that was unlocked/rooted and running Gummy, and then AOKP, so was able to keep up with that to some degree, though things like S-Off, CID, etc., still are a bit confusing to me.
Main target: Update Verizon HTC One (M8) to 4.4.3 Stock
My current situation:
My PC has adb/fastboot ready to go
My phone is already unlocked and S-Off
Running current TWRP recovery (2.8.0.1)
Phone running stock otherwise (4.4.2, Software # 1.55.605.2 Official)
I got the firmware that Tigerstown/Santod posted http://forum.xda-developers.com/showthread.php?t=2723159 (no boot/recovery version). I installed via Fastboot, and can confirm that the firmware took hold (e.g. radios definitely updated, reads 1.09.20.0702 in fastboot). Phone starts back up just fine.
Now, I assume I'm just stupidly expecting to see my Android version read 4.4.3, but it's still at 4.4.2. I'm guessing that it's because I only updated firmware, not software. Can also confirm I do not have the option for Extreme Power Saving mode. To add to that, I get the OTA notification that I can download 4.4.3 and update, but of course, I can't, because I'm running TWRP, not stock recovery. Tried flashing the stock 4.4.3 recovery from Tigerstown's thread, but the only thing I see is a picture of a phone with a red triangle, so I had to reflash TWRP, which is working again.
You can probably tell I'm in a bit over my head. Would like to be on 4.4.3 everything (not just the firmware underneath). Don't want to have to wipe everything if I decide to stay stock (have tons of photos and video of my kids that I don't want to have to reorganize), though I'm considering Android Revolution or ViperOneM8 (and would obviously have to wipe then). What am I missing, and what should I be doing? Or, since I'm not running any custom ROMs and the firmware seems to have taken hold, should I just leave it alone for now?
I appreciate any help and direction you can give! Let me know if you need further info that I didn't describe here.
branmuffin17 said:
Hi everyone,
So, not sure if I have a unique situation here, but have looked through the forums and haven't found any that seemed to answer my question. Sorry if there's a duplicate situation posted elsewhere. My level is pretty noob...I do pretty much only the basics. I understand about half of what I read, hahaha. Previously had a Verizon Galaxy Nexus that was unlocked/rooted and running Gummy, and then AOKP, so was able to keep up with that to some degree, though things like S-Off, CID, etc., still are a bit confusing to me.
Main target: Update Verizon HTC One (M8) to 4.4.3 Stock
My current situation:
My PC has adb/fastboot ready to go
My phone is already unlocked and S-Off
Running current TWRP recovery (2.8.0.1)
Phone running stock otherwise (4.4.2, Software # 1.55.605.2 Official)
I got the firmware that Tigerstown/Santod posted http://forum.xda-developers.com/showthread.php?t=2723159 (no boot/recovery version). I installed via Fastboot, and can confirm that the firmware took hold (e.g. radios definitely updated, reads 1.09.20.0702 in fastboot). Phone starts back up just fine.
Now, I assume I'm just stupidly expecting to see my Android version read 4.4.3, but it's still at 4.4.2. I'm guessing that it's because I only updated firmware, not software. Can also confirm I do not have the option for Extreme Power Saving mode. To add to that, I get the OTA notification that I can download 4.4.3 and update, but of course, I can't, because I'm running TWRP, not stock recovery. Tried flashing the stock 4.4.3 recovery from Tigerstown's thread, but the only thing I see is a picture of a phone with a red triangle, so I had to reflash TWRP, which is working again.
You can probably tell I'm in a bit over my head. Would like to be on 4.4.3 everything (not just the firmware underneath). Don't want to have to wipe everything if I decide to stay stock (have tons of photos and video of my kids that I don't want to have to reorganize), though I'm considering Android Revolution or ViperOneM8 (and would obviously have to wipe then). What am I missing, and what should I be doing? Or, since I'm not running any custom ROMs and the firmware seems to have taken hold, should I just leave it alone for now?
I appreciate any help and direction you can give! Let me know if you need further info that I didn't describe here.
Click to expand...
Click to collapse
The phone with the red triangle is what you are supposed to see. When you see that, you need to hit Vol-Up + Vol-Down and Power and it will take you into recovery. With that, you should be able to do the OTA to 4.4.3. I'm not sure if you need to flash the 4.4.2 firmware first or not. You can give it a try. If it fails then go ahead and flash back to the 4.4.2 firmware from Tigerstown's thread and try it again.
branmuffin17 said:
Hi everyone,
So, not sure if I have a unique situation here, but have looked through the forums and haven't found any that seemed to answer my question. Sorry if there's a duplicate situation posted elsewhere. My level is pretty noob...I do pretty much only the basics. I understand about half of what I read, hahaha. Previously had a Verizon Galaxy Nexus that was unlocked/rooted and running Gummy, and then AOKP, so was able to keep up with that to some degree, though things like S-Off, CID, etc., still are a bit confusing to me.
Main target: Update Verizon HTC One (M8) to 4.4.3 Stock
My current situation:
My PC has adb/fastboot ready to go
My phone is already unlocked and S-Off
Running current TWRP recovery (2.8.0.1)
Phone running stock otherwise (4.4.2, Software # 1.55.605.2 Official)
I got the firmware that Tigerstown/Santod posted http://forum.xda-developers.com/showthread.php?t=2723159 (no boot/recovery version). I installed via Fastboot, and can confirm that the firmware took hold (e.g. radios definitely updated, reads 1.09.20.0702 in fastboot). Phone starts back up just fine.
Now, I assume I'm just stupidly expecting to see my Android version read 4.4.3, but it's still at 4.4.2. I'm guessing that it's because I only updated firmware, not software. Can also confirm I do not have the option for Extreme Power Saving mode. To add to that, I get the OTA notification that I can download 4.4.3 and update, but of course, I can't, because I'm running TWRP, not stock recovery. Tried flashing the stock 4.4.3 recovery from Tigerstown's thread, but the only thing I see is a picture of a phone with a red triangle, so I had to reflash TWRP, which is working again.
You can probably tell I'm in a bit over my head. Would like to be on 4.4.3 everything (not just the firmware underneath). Don't want to have to wipe everything if I decide to stay stock (have tons of photos and video of my kids that I don't want to have to reorganize), though I'm considering Android Revolution or ViperOneM8 (and would obviously have to wipe then). What am I missing, and what should I be doing? Or, since I'm not running any custom ROMs and the firmware seems to have taken hold, should I just leave it alone for now?
I appreciate any help and direction you can give! Let me know if you need further info that I didn't describe here.
Click to expand...
Click to collapse
SCrosler has posted a stock rooted 4.4.3 ROM. If you flash that you will all up to date (or you could flash Viper 2.4 or NuSense 2.0) essentially flashing any 4.4.3 ROM will get you where you want to be.
Here is the link to the stock, rooted ROM: http://forum.xda-developers.com/ver...m-stock-rooted-vzw-ota-2-21-605-2-wp-t2874699. With your updated firmware and that ROM you will be stock, and up to date on 4.4.3
@BladeRunner & @jsaxon2, thank you very much for your replies and the help. Looks like this was covered to some degree, and has answered my questions.
Going to try dirty-flashing the ODEX rom. I want to flash Viper pretty badly, but don't want to have to wipe everything right now. When Android L comes out, that will be fully worth starting from scratch. I have just enough patience to wait.
Will confirm shortly that everything has worked.
FYI, dirty flash of the ODEX (just wiped cache/dalvik, left data alone) worked perfectly. Software is now reading 4.4.3. Thanks to @scrosler for the stock ROM!
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.