I am still new in terms of customizing Android. The Sprint Galaxy S4 has an unlocked bootloader, while the AT&T and Verizon Galaxy S4 versions have a locked bootloader. This means that the ATT/VZW required a seperate program called a 'safestrap' which keeps the stock ROM intact, and uses additional internal memory and creates a whole new memory (essentially 2 ROMs in the internal memory) due to the bootloader being locked from the carrier ? Am I understanding this correctly ?
Just making sure, a few friends from VZW knew that I have a custom ROM on my phone and asked, and I didn't realize you can just flash custom recovery wipe, then flash like with Sprint. Thanks
mikeprius said:
I am still new in terms of customizing Android. The Sprint Galaxy S4 has an unlocked bootloader, while the AT&T and Verizon Galaxy S4 versions have a locked bootloader. This means that the ATT/VZW required a seperate program called a 'safestrap' which keeps the stock ROM intact, and uses additional internal memory and creates a whole new memory (essentially 2 ROMs in the internal memory) due to the bootloader being locked from the carrier ? Am I understanding this correctly ?
Just making sure, a few friends from VZW knew that I have a custom ROM on my phone and asked, and I didn't realize you can just flash custom recovery wipe, then flash like with Sprint. Thanks
Click to expand...
Click to collapse
You're correct. You guys on sprint and TMobile are lucky to have unlocked bootloaders. My Verizon s4 is mdk firmware (the original) which can use Loki to bypass the bootloader so to speak. ATT has a similar situation I believe. But every firmware since the original has locked them down further. Requiring SafeStrap.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
You're correct. You guys on sprint and TMobile are lucky to have unlocked bootloaders. My Verizon s4 is mdk firmware (the original) which can use Loki to bypass the bootloader so to speak. ATT has a similar situation I believe. But every firmware since the original has locked them down further. Requiring SafeStrap.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thank for the reply. Since the internal memory keeps the original ROM intact does it bog down the phone and draw resources while the custom ROM is running ? Or is the original ROM essentially "frozen" ?
Will your phone brick if you try and load custom ROMs without safestrap and tamper with the locked bootloader ?
mikeprius said:
Thank for the reply. Since the internal memory keeps the original ROM intact does it bog down the phone and draw resources while the custom ROM is running ? Or is the original ROM essentially "frozen" ?
Will your phone brick if you try and load custom ROMs without safestrap and tamper with the locked bootloader ?
Click to expand...
Click to collapse
Well if you're using SafeStrap the way it was intended ( stock slot + ROM slots ) then the only resources used will be the physical memory which the stock ROM and the custom ROM will be taking up on the internal memory. Now some have wiped the stock ROM slot and installed custom Roms onto that to have more internal memory free. That however isn't recommended because if anything gets screwed up Odin is your only option usually. Whereas if you install to ROM slots you can just keep wiping and installing.
And your chances of bricking one of these locked down s4 is really high if you do anything other than root it and use SafeStrap. If we could do it without SafeStrap we certainly would. Just can't be done that's all.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Well if you're using SafeStrap the way it was intended ( stock slot + ROM slots ) then the only resources used will be the physical memory which the stock ROM and the custom ROM will be taking up on the internal memory. Now some have wiped the stock ROM slot and installed custom Roms onto that to have more internal memory free. That however isn't recommended because if anything gets screwed up Odin is your only option usually. Whereas if you install to ROM slots you can just keep wiping and installing.
And your chances of bricking one of these locked down s4 is really high if you do anything other than root it and use SafeStrap. If we could do it without SafeStrap we certainly would. Just can't be done that's all.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Makes sense. How would the phone get hard bricked if you can flash via Odin if you were to wipe the stock ROM slot ? The locked bootloader would still stay intact but the stock ROM would be gone. I am assuming the possibility of bricking the phone would be restoring the stock rom after it has been wiped while leaving the locked bootloader untouched. I was looking at safestrap for my friend and will pass along the information....too bad it is not like sprint where everything can be deleted haphazardly which is what I do when I flash new roms. I even format the internals so everything is completely empty when I put a new ROM.
mikeprius said:
Makes sense. How would the phone get hard bricked if you can flash via Odin if you were to wipe the stock ROM slot ? The locked bootloader would still stay intact but the stock ROM would be gone. I am assuming the possibility of bricking the phone would be restoring the stock rom after it has been wiped while leaving the locked bootloader untouched. I was looking at safestrap for my friend and will pass along the information....too bad it is not like sprint where everything can be deleted haphazardly which is what I do when I flash new roms. I even format the internals so everything is completely empty when I put a new ROM.
Click to expand...
Click to collapse
When I was using SafeStrap I never ran into a hard brick myself, just soft brick that Odin would fix pretty easily. I'd say about 99% of the time that would be the case.
I'm not sure of the technical details as far as why messing with the stock slot can lead to issues. My guess , and i could be wrong, is maybe to do with the kernel. . SafeStrap Roms must be based of the same version if Touchwiz that the phone is on 4.2 4.3 4.4 etc and it must have the same kernel as well. Again I'm just guessing but when the phone boots up and runs all its checks, if there are any discrepancies i think that would lead you to a soft brick, again this is if you're flashing to the stock slot.
I think someone who is way smarter than me could explain the differences between what really is going on when soft bricks result from flashing to the stock slot vs a ROM slot. I'm just going off my experiences.
That said... Most people have no problems keeping the stock slot and running 2 or 3 ROM slots as long as they manage their internal memory well and send everything they can to external SD card.
I ran SafeStrap on my RAZR for a long time and for a little while on the s4 before I picked up an MDK build S4 that I could bypass the bootloader using Loki.
The RAZR had Kexec support or Bootstrapping, whatever you want to call it, which allowed for custom kernels and Aosp Roms. People are working on that for the s4 and hopefully that day comes because it opens up a ton of options as you can imagine.
Hope I helped a little. And like I said if you want more technical answers about SafeStrap and stock slot vs ROM slot just hop over to a SafeStrap thread I'm sure someone will know
Sent from my SCH-I545 using Tapatalk
Wow, I hadn't realized how big of a hassle some of the carriers were trying to make it for you to customize your own phone. That really stinks. Sprint has always been good to me so far.
Sent via mobile
Related
So we just upgraded my wife's phone to the S5 on Verizon, and I've spent a few minutes going through the forum here and want to make sure I understand the current state of hacking on this phone, along with some other questions:
1) Root is possible - which will provide full access to the system for modification? (TiBu, Xposed, etc)?
2) No bootloader unlock - so standard custom ROM flashing is not available.
3) Ability to use "safestrap" - which as best as I can tell allows you to multi-boot custom ROMs by bootstrapping them from defined partitions in internal memory(?)
Some additional questions:
4) What are the drawbacks to safestrap booting compared to the standard custom ROM flash with a custom recovery? I mean, yes the method is different, but are there limitations on the functionality of custom ROMs flashed using this method? Does it detract from anything, or does it just mean a little more development must go into making a safestrap ROM?
5) I see some posts regarding SELinux being enabled in the kernel and no working fix yet. What actual impact does having SELinux in Enforcing mode have on the system for custom tweaking, etc?
6) Is it possible (and easy enough) to bring the phone back to complete stock if required. Either for return purposes, or because you deleted something and can't get OTA, etc.
7) In general, when all is said and done, what are the tangible areas which the S5 is locked to the extent that it truly diminishes the custom experience?
I am getting myself the M8, and spending most of my time figuring things out on there. My wife preferred the S5 and although she isn't a "power user" she may eventually want some things that the custom ROM can't provide. I'm hoping root and Xposed will be enough for those things - but we are still within our return window and if I deem the S5 just doesn't have the features, we may try something else....though it seems that most everything on Verizon is locked down except maybe the M8.
TIA
1) Root is possible - which will provide full access to the system for modification? (TiBu, Xposed, etc)?
Correct
2) No bootloader unlock - so standard custom ROM flashing is not available.
Correct
3) Ability to use "safestrap" - which as best as I can tell allows you to multi-boot custom ROMs by bootstrapping them from defined partitions in internal memory(?)
In essence, this is how we are loading custom ROMs. Technically you could use it for multiple ROMs, it seems like the consensus is to just load your custom ROM to the primary slot and not switch between multiple.
Some additional questions:
4) What are the drawbacks to safestrap booting compared to the standard custom ROM flash with a custom recovery? I mean, yes the method is different, but are there limitations on the functionality of custom ROMs flashed using this method? Does it detract from anything, or does it just mean a little more development must go into making a safestrap ROM?
The drawback is no custom kernels and no ROMs like CM or AOSP because of that.
6) Is it possible (and easy enough) to bring the phone back to complete stock if required. Either for return purposes, or because you deleted something and can't get OTA, etc.
Yes.
7) In general, when all is said and done, what are the tangible areas which the S5 is locked to the extent that it truly diminishes the custom experience?
Having a locked bootloader does limit the ROM choices in that we will only get Touchwiz-based options, but that isn't necessarily a huge deal.
jcollier said:
1) Root is possible - which will provide full access to the system for modification? (TiBu, Xposed, etc)?
Correct
2) No bootloader unlock - so standard custom ROM flashing is not available.
Correct
3) Ability to use "safestrap" - which as best as I can tell allows you to multi-boot custom ROMs by bootstrapping them from defined partitions in internal memory(?)
In essence, this is how we are loading custom ROMs. Technically you could use it for multiple ROMs, it seems like the consensus is to just load your custom ROM to the primary slot and not switch between multiple.
Some additional questions:
4) What are the drawbacks to safestrap booting compared to the standard custom ROM flash with a custom recovery? I mean, yes the method is different, but are there limitations on the functionality of custom ROMs flashed using this method? Does it detract from anything, or does it just mean a little more development must go into making a safestrap ROM?
The drawback is no custom kernels and no ROMs like CM or AOSP because of that.
6) Is it possible (and easy enough) to bring the phone back to complete stock if required. Either for return purposes, or because you deleted something and can't get OTA, etc.
Yes.
7) In general, when all is said and done, what are the tangible areas which the S5 is locked to the extent that it truly diminishes the custom experience?
Having a locked bootloader does limit the ROM choices in that we will only get Touchwiz-based options, but that isn't necessarily a huge deal.
Click to expand...
Click to collapse
So when using safestrap do you actually overwrite your main ROM in the slot, or you would have your main (factory) ROM loaded as normal, and then your custom in a separate slot? In effect, you could toggle between those if wanted? If so, I might load a custom for her to play with while not interrupting her normal usage. If she prefers it, we could eventually switch her over.
Where in the ROM/RAM are these custom ROMs actually placed and how big are they as in how do they affect the overall storage on your device if you opt to use one? I assume if you were to switch between more than one you would probably have to install all your apps, etc on each one.
What you said about touch-wiz only makes sense though I suppose it isn't that bad of a thing especially with all the proprietary goodies that Samsung has. I would expect that AOSP or CM mods might have problems recreating some of those features anyway.
Thanks again
TraderJack said:
So when using safestrap do you actually overwrite your main ROM in the slot, or you would have your main (factory) ROM loaded as normal, and then your custom in a separate slot? In effect, you could toggle between those if wanted? If so, I might load a custom for her to play with while not interrupting her normal usage. If she prefers it, we could eventually switch her over.
Where in the ROM/RAM are these custom ROMs actually placed and how big are they as in how do they affect the overall storage on your device if you opt to use one? I assume if you were to switch between more than one you would probably have to install all your apps, etc on each one.
What you said about touch-wiz only makes sense though I suppose it isn't that bad of a thing especially with all the proprietary goodies that Samsung has. I would expect that AOSP or CM mods might have problems recreating some of those features anyway.
Thanks again
Click to expand...
Click to collapse
I believe most people are just overwriting the main ROM and that is what I have done. I believe I recall issues when loading into the other slots.
I can't speak to the specific partition the custom ROMs are stored on when using other slots, sorry.
jcollier said:
I believe most people are just overwriting the main ROM and that is what I have done. I believe I recall issues when loading into the other slots.
I can't speak to the specific partition the custom ROMs are stored on when using other slots, sorry.
Click to expand...
Click to collapse
Last I knew, safestrap slots are virtual disks on the data partition. Safestrap hijacks the boot process and remaps /system, /data, et al to the appropriate virtual disk for that slot.
If you flash to the main slot, you would be overwriting the stock rom, which may have drastic consequences. I highly recommend flashing your custom rom to a slot other than the stock rom slot.
When I had my Droid Razr, kexec was used to hot boot a new kernel. Support for kexec may not be available for the S5 though, denying us custom kernels.
fcsager said:
Last I knew, safestrap slots are virtual disks on the data partition. Safestrap hijacks the boot process and remaps /system, /data, et al to the appropriate virtual disk for that slot.
If you flash to the main slot, you would be overwriting the stock rom, which may have drastic consequences. I highly recommend flashing your custom rom to a slot other than the stock rom slot.
When I had my Droid Razr, kexec was used to hot boot a new kernel. Support for kexec may not be available for the S5 though, denying us custom kernels.
Click to expand...
Click to collapse
From what I've read, safestrap with the s5 has problems with rom slots. Most people having small problems here and there are on a rom slot, and when they flash the rom to stock slot most of they're problems go away. I think this is mentioned in the safestrap thread itself.
From what I understand, make a backup of your stock rom, then format, then flash rom choice on stock slot. That way if something screws up you can restore your stick backup.
fcsager said:
If you flash to the main slot, you would be overwriting the stock rom, which may have drastic consequences. I highly recommend flashing your custom rom to a slot other than the stock rom slot.
Click to expand...
Click to collapse
SafeStrap on the S5 is very buggy if you are using a ROM slot other than stock and is HIGHLY recommended by all the devs to use stock slot.
There will be no drastic consequences if you decide to use your stock slot. Just make sure you make a backup of your stock ROM before wiping it. If, by chance, something does go wrong, you can always ODIN back to stock and start over.
So being that the common/accepted practice is to install a ROM to the stock slot (which I did) its probably a good idea to go back in and resize the ROM slot to the smallest size allowable correct? Were never going to be using it so why not? Can this be done easily without affecting the ROM installed in the stock slot?
chetqwerty said:
So being that the common/accepted practice is to install a ROM to the stock slot (which I did) its probably a good idea to go back in and resize the ROM slot to the smallest size allowable correct? Were never going to be using it so why not? Can this be done easily without affecting the ROM installed in the stock slot?
Click to expand...
Click to collapse
You could just delete all ROM slots and call it a day.
MrHyde03 said:
You could just delete all ROM slots and call it a day.
Click to expand...
Click to collapse
Wow, I over thought that a tad aay! lol of course you can do that, thanks man!
I would like the piggyback off this thread since I also just got my S5 a couple days ago. I have an OTA update pending, I'll attach a screenshot of my current version number here but should I not update it until I root it or is it still possible to root with the latest software? After I do root it should I lock the file that is used to detect new versions?
If you have not updated, do not update, use towelroot to root, then freeze SDM using Titanium Backup
Ok, did that, that was easy. Quick read through of that thread says he works for Google now and people who updated basically shot them selves in the foot for that method, is that about right?
What should I do after I root, download SuperSU? Anything else I should need?
EDIT: Oh, it already restored SuperSU from my app sync so I don't even need that.
I had the ne9 version and immediately odin flashed to NCG and rooted. Then I SU'd, busyboxed, then safestrapped. Flashed alliancerom over my system after testing it on a different partition. So now I have alliancerom running and have customized the heck out of it.
berfles said:
I would like the piggyback off this thread since I also just got my S5 a couple days ago. I have an OTA update pending, I'll attach a screenshot of my current version number here but should I not update it until I root it or is it still possible to root with the latest software? After I do root it should I lock the file that is used to detect new versions?
Click to expand...
Click to collapse
berfles said:
Ok, did that, that was easy. Quick read through of that thread says he works for Google now and people who updated basically shot them selves in the foot for that method, is that about right?
What should I do after I root, download SuperSU? Anything else I should need?
EDIT: Oh, it already restored SuperSU from my app sync so I don't even need that.
Click to expand...
Click to collapse
Yes, it's possible to root the latest firmware(NE9). See here: http://forum.xda-developers.com/verizon-galaxy-s5/general/how-to-root-g900vvru1ane9-t2836201
And with any luck we should be able to keep root on any subsequent updates if not with the kernel swap method with other methods.
So I have a unique situation. I have an S4 with an MDB or MDL bootloader (don't remember what I had when I left stock ROM behind) with a 4.4.2 GE ROM on it (using Loki). My recovery is TWRP.
I did flash an MF3 radio if that matters.
I need to SIM unlock the phone but none of the methods I've tried (including Regionlock Away) work on this GE ROM.
I know if I return to a stock (rooted) ROM I can run RegionLock Away or use a few methods here but I want to do this the fastest/easiest way possible and get back the phone back onto a new 4.4.4 KK ROM (waiting a bit for LP).
Anybody have any suggestions for a rooted & defanged but generally stock ROM I can flash temporarily? I need the CSC data to be intact for RegionLock Away to work.
Seems like most of the older ROMs out there are broken links at this point and all the newer TW ROMs I've seen are for SafeStrap (plus they have been heavily modified)
I know worst case scenario I can ODIN back to MDL (probably flash MDL radio first just to be safe) then re-root but I don't even have all the tools for that anymore (I originally rooted using a work PC I no longer have) and I suspect a lot of what I need will be broken links since they were last useful for most people in 2013.
Anyways I'm just looking for the shortest/easiest path to SIM unlock (without paying for a code). I did try the official AT&T but I'm still under contract for another month so they denied. I want to use the phone for a T-Mobile test drive next week.
Thanks for any advice/suggestions.
raitchison said:
So I have a unique situation. I have an S4 with an MDB or MDL bootloader (don't remember what I had when I left stock ROM behind) with a 4.4.2 GE ROM on it (using Loki). My recovery is TWRP.
I did flash an MF3 radio if that matters.
I need to SIM unlock the phone but none of the methods I've tried (including Regionlock Away) work on this GE ROM.
I know if I return to a stock (rooted) ROM I can run RegionLock Away or use a few methods here but I want to do this the fastest/easiest way possible and get back the phone back onto a new 4.4.4 KK ROM (waiting a bit for LP).
Anybody have any suggestions for a rooted & defanged but generally stock ROM I can flash temporarily? I need the CSC data to be intact for RegionLock Away to work.
Seems like most of the older ROMs out there are broken links at this point and all the newer TW ROMs I've seen are for SafeStrap (plus they have been heavily modified)
I know worst case scenario I can ODIN back to MDL (probably flash MDL radio first just to be safe) then re-root but I don't even have all the tools for that anymore (I originally rooted using a work PC I no longer have) and I suspect a lot of what I need will be broken links since they were last useful for most people in 2013.
Anyways I'm just looking for the shortest/easiest path to SIM unlock (without paying for a code). I did try the official AT&T but I'm still under contract for another month so they denied. I want to use the phone for a T-Mobile test drive next week.
Thanks for any advice/suggestions.
Click to expand...
Click to collapse
As long as those Safestrap ROMs are for our device they'll work for you, not to mention they usually have Aroma options for both. Just make sure it's an AT&T base ROM. Otherwise, you can try and dig back for the MF3 Unadulterated ROM that's somewhere in this section.
DeadlySin9 said:
As long as those Safestrap ROMs are for our device they'll work for you, not to mention they usually have Aroma options for both. Just make sure it's an AT&T base ROM. Otherwise, you can try and dig back for the MF3 Unadulterated ROM that's somewhere in this section.
Click to expand...
Click to collapse
Thanks but since my phone never took MF3 I was never limited by safestrap.
What I ended up doing was:
Using ODIN to flash MDL back on the phone.
Tthen re-rooted using CASUAL (which only works on MDB or MDL bootloaders)
Then used RegionLock away to remove the SIM Lock (this is not RegionLock Away's primary purpose but is a convenient side effect)
Then installed a new copy of TWRP (CASUAL installs TWRP but an old copy)
Then finally installed Danvdh's excellent Google Play Edition ROM.
I had to flash loki-doki after I flashed the ROM and I updated to the NJ4 radio for good measure.
Was a lot of time and a fair amount of work and I cringed seeing the Samsung OS boot on my phone but all in all it was successful.
Hi all,
It's been a few yrs since I've flashed a phone (the last being my SGS1 variant) and I'm very out of practice. That being said, I just need a little help in understanding how to flash my SGS4. So far, I've had this phone for yrs and I would've jumped to custom roms as I did normally but there was the whole KNOX debacle and I didn't want to do anything to damage my phone - while within warranty. I've been out of the loop for awhile, so I need a little help in my choices here.
My phone is still running on it's original software (that's right, I completely haven't updated in yrs), so it's a 4.2.2 and the build is I9505XXUBM4 (pre-KNOX). If I am going to root, I was thinking that I should use the method from this thread: [GT-I9505 + GT-I9505G] CF-Auto-Root. Would I be right in using this method or is there something better?
Secondly, I've only ever used CWM. I'm assuming the recovery to use currently is TWRP since I've seen it brought up in a good number of threads. Can I make a nandroid with TWRP the same way it was done with CWM or do I need to find another way to backup my data?
Lastly, this is the rom I'm leaning towards; [JDCTeam][6.0.1][9 July] The Android Open Source Project MOB30M. Could I just flash this on top of my stock or do I have to update first and then flash this?
TIA for your responses.
Oniyuri said:
Hi all,
It's been a few yrs since I've flashed a phone (the last being my SGS1 variant) and I'm very out of practice. That being said, I just need a little help in understanding how to flash my SGS4. So far, I've had this phone for yrs and I would've jumped to custom roms as I did normally but there was the whole KNOX debacle and I didn't want to do anything to damage my phone - while within warranty. I've been out of the loop for awhile, so I need a little help in my choices here.
My phone is still running on it's original software (that's right, I completely haven't updated in yrs), so it's a 4.2.2 and the build is I9505XXUBM4 (pre-KNOX). If I am going to root, I was thinking that I should use the method from this thread: [GT-I9505 + GT-I9505G] CF-Auto-Root. Would I be right in using this method or is there something better?
Secondly, I've only ever used CWM. I'm assuming the recovery to use currently is TWRP since I've seen it brought up in a good number of threads. Can I make a nandroid with TWRP the same way it was done with CWM or do I need to find another way to backup my data?
Lastly, this is the rom I'm leaning towards; [JDCTeam][6.0.1][9 July] The Android Open Source Project MOB30M. Could I just flash this on top of my stock or do I have to update first and then flash this?
TIA for your responses.
Click to expand...
Click to collapse
For first you MUST update your phone, if you have root, update with odin on the latest firmware version and then flash flash recovery(cwm, twrp, philz) and flash the rom, because firmware request of the rom is android lollipop stock. Try cyanogenmod 13 nighty for this smartphone
Alessandro's said:
For first you MUST update your phone, if you have root, update with odin on the latest firmware version and then flash flash recovery(cwm, twrp, philz) and flash the rom, because firmware request of the rom is android lollipop stock. Try cyanogenmod 13 nighty for this smartphone
Click to expand...
Click to collapse
Ok, so after I root the phone, can I go straight onto CM13 or do I still have to get lollipop first and then flash CM?
I'm still trying to avoid getting KNOX on the phone.
Oniyuri said:
Ok, so after I root the phone, can I go straight onto CM13 or do I still have to get lollipop first and then flash CM?
I'm still trying to avoid getting KNOX on the phone.
Click to expand...
Click to collapse
Then you install lollipop stock, make root , flash recovery and then flash cm13
Oniyuri said:
Ok, so after I root the phone, can I go straight onto CM13 or do I still have to get lollipop first and then flash CM?
I'm still trying to avoid getting KNOX on the phone.
Click to expand...
Click to collapse
Knox does matter once you're on a custom ROM.
Most content creators recommend to use the latest modem and bootloader in order to avoid problems.
You don't necessarily have to update the whole ROM to have the newest modem and bootloader, there are Odin flashable packages.
I don't know if CF-Auto-Root works with 4.2. I know it works for 4.4 and above.
As long as you do your wipes (this means system, data, cache, dalvik) you can flash anything over anything.
Yes, you can do nandroid backups, but TWRP and CWM backups are not compatible with each other. Also, TWRP has a problem with TouchWiz backups, meaning you can make and restore a TouchWiz backup, but it either won't boot or will give you lots of errors.
GDReaper said:
Knox does matter once you're on a custom ROM.
Most content creators recommend to use the latest modem and bootloader in order to avoid problems.
You don't necessarily have to update the whole ROM to have the newest modem and bootloader, there are Odin flashable packages.
I don't know if CF-Auto-Root works with 4.2. I know it works for 4.4 and above.
As long as you do your wipes (this means system, data, cache, dalvik) you can flash anything over anything.
Yes, you can do nandroid backups, but TWRP and CWM backups are not compatible with each other. Also, TWRP has a problem with TouchWiz backups, meaning you can make and restore a TouchWiz backup, but it either won't boot or will give you lots of errors.
Click to expand...
Click to collapse
Ok, so is there a way that I could at least get to lollipop w/o getting KNOX and have a nandroid that would work or should I just OTA all the way up to current and then root and flash?
Oniyuri said:
Ok, so is there a way that I could at least get to lollipop w/o getting KNOX and have a nandroid that would work or should I just OTA all the way up to current and then root and flash?
Click to expand...
Click to collapse
Why are you so obsessed with Knox? I just told you that it won't be an issue on custom ROMs. There is no knox on custom ROMs. Knox is a Samsung thing. So, unless you plan on staying stock, there is no reason to be concerned about it. Even if you stay stock, there still is no reason to be afraid of it, it's just some security crap, and it won't affect you in any way. Why are you so afraid of it?
My device came with Knox pre-installed and it didn't do jack.
Just update if you want to update or flash a recovery (flashing custom ROMs doesn't require root, just a custom recovery) and flash your desired ROM.
GDReaper said:
Why are you so obsessed with Knox? I just told you that it won't be an issue on custom ROMs. There is no knox on custom ROMs. Knox is a Samsung thing. So, unless you plan on staying stock, there is no reason to be concerned about it. Even if you stay stock, there still is no reason to be afraid of it, it's just some security crap, and it won't affect you in any way. Why are you so afraid of it?
My device came with Knox pre-installed and it didn't do jack.
Just update if you want to update or flash a recovery (flashing custom ROMs doesn't require root, just a custom recovery) and flash your desired ROM.
Click to expand...
Click to collapse
Well, I've been out of the loop for a while (the last time I was active was circa late 2013/ early 2014), but I do remember there was a lot of concern regarding warranty and the flags. I do admit that there was a lot of speculation from losing a section of memory from tripping the flag to actually burning the motherboard. I originally decided to wait until the dust settled but life took over and I ended up only sporadically checking the forums before disappearing for long periods of time. I actually don't know what the end of the story is to be honest.
Oniyuri said:
Well, I've been out of the loop for a while (the last time I was active was circa late 2013/ early 2014), but I do remember there was a lot of concern regarding warranty and the flags. I do admit that there was a lot of speculation from losing a section of memory from tripping the flag to actually burning the motherboard. I originally decided to wait until the dust settled but life took over and I ended up only sporadically checking the forums before disappearing for long periods of time. I actually don't know what the end of the story is to be honest.
Click to expand...
Click to collapse
The only concern is about the warranty. Since your phone is some years old, I doubt that is an issue for you anymore.
By losing memory you mean losing data or actually losing storage space?
Either way, I haven't heard of anyone with such a problem around here.
Nor about somebody with a fried motherboard.
There might have been some unfortunate cases, but this is to be expected when you modify your device. There always is a risk of damage, it doesn't matter if it's by rooting or by flashing a ROM.
I meant lose storage. As I understood it, KNOX worked like a container and once the flag was tripped, you'd lose whatever it contained - as in never being able to access that bit ever again.
Oniyuri said:
I meant lose storage. As I understood it, KNOX worked like a container and once the flag was tripped, you'd lose whatever it contained - as in never being able to access that bit ever again.
Click to expand...
Click to collapse
You have to use the knox app first for that to even be considered a risk.
Knox will not put anything in that container without user input.
GDReaper said:
You have to use the knox app first for that to even be considered a risk.
Knox will not put anything in that container without user input.
Click to expand...
Click to collapse
Ok, so to get the steps straight:
1. I'd need to get a lollipop bootloader & modem
2. root + nandroid (CWM) + titanium for app data (non-system app data)
3. change recovery to TWRP
4. flash rom + gapps
....and then I should be ready to go, correct?
Oniyuri said:
Ok, so to get the steps straight:
1. I'd need to get a lollipop bootloader & modem
2. root + nandroid (CWM) + titanium for app data (non-system app data)
3. change recovery to TWRP
4. flash rom + gapps
....and then I should be ready to go, correct?
Click to expand...
Click to collapse
1) Is not mandatory, it's just recommended. The only exception is if your device is a Verizon or AT&T phone, then don't - and I repeat - don't update or you risk losing the possibility of any custom ROM flashing or rooting due to the locked bootloaders.
2) and 3) CWM and TWRP backups do not have cross-compatibility. If you backup with CWM you have to restore with CWM.
Please tell me you haven't flashed anything yet. I can help with the entirety of the procedure.
robcore said:
Please tell me you haven't flashed anything yet. I can help with the entirety of the procedure.
Click to expand...
Click to collapse
No I haven't done anything yet. I found something else to occupy me for the last few nights - a chromecast that seems to hate me.
Oniyuri said:
No I haven't done anything yet. I found something else to occupy me for the last few nights - a chromecast that seems to hate me.
Click to expand...
Click to collapse
Haha I hear ya. I've been building a kernel for about a year now and finally (knock on wood) arrived at something I'm happy with. Lesson learned, electronics are definitely conspiring against us.
That said, please feel free to pm me when you're ready for the flashing process. Though it's a silly skill, it's become second nature to me and something about your situation flipped a helpful switch in me : P what's the Chromecast like?
robcore said:
Haha I hear ya. I've been building a kernel for about a year now and finally (knock on wood) arrived at something I'm happy with. Lesson learned, electronics are definitely conspiring against us.
That said, please feel free to pm me when you're ready for the flashing process. Though it's a silly skill, it's become second nature to me and something about your situation flipped a helpful switch in me : P what's the Chromecast like?
Click to expand...
Click to collapse
Well, so far, the chromecast is only plugged into my tv and basically did the setup by itself only for the google cast app on my phone to not recognize it when it said that it's ready to cast. I've ran out of things to do aside from going to the google forums (which I've already done). I'm starting to wonder if it's my phone that's causing all the issues.
Hello,
A few months ago, I was able to successfully root my AT&T S4 (SGH-I337, builld LRX22C.I337UCSGOK3) using KingRoot. The KNOX warranty bit was not set at the conclusion of the root process.
After wrestling with storage problems, including the "system memory" taking up 6.29 GB out of the meager 16 GB that is on this phone (preventing practically any Google Play updates from occurring, as the available space would always dip below 500 MB periodically), as well as performance problems (very long delays for some touch events and a general resentment of TouchWiz), I decided that enough was enough, and I decided to change my ROM/OS out for LineageOS.
LineageOS offers builds for jfltexx, which is reported to work for jflteatt since they are similar enough. I am not really willing to try "older" builds, as one of my goals is also to bring the security of the operating system up to date, so I am not exactly inclined to go for old CyanogenMod builds. The LineageOS install guide stipulates that I install TWRP to successfully install the OS via a supported recovery; however, the message SECURE MAGICCODE FAIL: recovery appears, as the upgrade process seems to be expecting something signed by Samsung (right?). Other guides warn that the stock recovery only allows stock OS installation and not custom operating systems, so I decided not to try that route. This effectively prevents me from installing LineageOS due to a problem that is inherent in OK3.
Why did I make the mistake to install OK3? More than a year ago, I decided to do the final update that AT&T pushed out for this phone. Thinking that it would be something significant, I went for it, only to find out months later that it was a minor update whose purpose was also to add an additional lock to the bootloader. As this phone is "fairly old" (is 2013 already considered ancient times?), I have not found many guides that cover OK3, and those that do pertain to either rooting the S4 (already done) or something about downgrading (but I can't really do that, seemingly due to the OK3 lock-in). Oops.
That said, is there any hope to bring more life out of my phone, or is it time to throw the phone out and buy a Pixel or related product like any typical consumerist would do? My goal is to move to another OS to end the storage problems and other quirks of this phone that I have grown to deplore; that is all I wish to attain.
The phone is relatively reliable: it had ~1200 hours of uptime before I had to reboot it a few days ago to fix a data connectivity problem. The battery is also very manageable and can last a day and a half in regular use, but it can last 2-3 days under maximum power-saving mode.
I have read the rules and done some research on this forum, among some others. Thank you for your assistance.
Upgrading the phone to 4.3 locked the boot loader which prevents the installation of TWRP.
audit13 said:
Upgrading the phone to 4.3 locked the boot loader which prevents the installation of TWRP.
Click to expand...
Click to collapse
I see; so I was already screwed when I had OK2?
oldmud0 said:
I see; so I was already screwed when I had OK2?
Click to expand...
Click to collapse
Yes, anything past MDL has the bootloader flaw patched. MDL firmware and below have a flaw in the bootloader that allows loki doki to be installed bypassing the bootloader lock so you can install TWRP recovery and custom AOSP ROMs.
Since you're on OK3, you're forced to use safe strap recovery and can only install custom touchwiz ROMs like golden eye and albe95.
If you want to read up on the MDL bootloader, I have written a guide here: https://forum.xda-developers.com/galaxy-s4-att/general/how-to-one-guide-to-mdl-bootloader-t3584122
My wish is to escape TouchWiz, so I suppose I have hit a dead end.
Thank you for your help anyway.
oldmud0 said:
My wish is to escape TouchWiz, so I suppose I have hit a dead end.
Thank you for your help anyway.
Click to expand...
Click to collapse
If you want away from touch wiz, I think there's a Google play edition ROM for the galaxy s4 that you can use with OK3, but I am not too sure. I would just check the galaxy s4 ROM section for it. I'm on the MDL bootloader which allows me to use TWRP, so I don't know too much about safe strap recovery.
Even if one wanted to do a TouchWiz-based ROM, I don't think we on OK2/OK3 even have the option to install SafeStrap, so far as I can gather
Hold the phone, I think I've found something. Evidently we can Odin back down to NB1 and go from there! Experiments, here we come.
Yes, NB1 is as far back you can go I believe without bricking your phone.
Hello
My son used an S4 years ago, and now I want to use it as my daughter's first phone. I booted the phone, and found all kinds of things from 2017. I also see that the phone is rooted on software I337UCUGOK2 with Android 5.01.
We're using Simple Mobile, so I would like to use it.
1. Can I simply insert the simple mobile sim? When I booted the phone, I saw a Samsung logo and an unlocked lock image. So I either have the bootloader unlocked or it's sim unlocked; it's been a while.
2. Being on Android 5, I'd like to bring it up to a recent version. I see that Lineage 16 is out. Can I flash that?
Thank you
nabril15 said:
Hello
My son used an S4 years ago, and now I want to use it as my daughter's first phone. I booted the phone, and found all kinds of things from 2017. I also see that the phone is rooted on software I337UCUGOK2 with Android 5.01.
We're using Simple Mobile, so I would like to use it.
1. Can I simply insert the simple mobile sim? When I booted the phone, I saw a Samsung logo and an unlocked lock image. So I either have the bootloader unlocked or it's sim unlocked; it's been a while.
2. Being on Android 5, I'd like to bring it up to a recent version. I see that Lineage 16 is out. Can I flash that?
Thank you
Click to expand...
Click to collapse
To answer your questions:
1. Yes just insert the SIM. The unlocked image on boot up just means you're rooted and/or running a custom TW ROM.
2. You are stuck with lollipop. Only an S4 running the old MDL firmware can boot lineage OS due to a flaw exploit which was patched in later firmware. All other firmwares are locked and yours is one of them.
StoneyJSG said:
2. You are stuck with lollipop. Only an S4 running the old MDL firmware can boot lineage OS due to a flaw exploit which was patched in later firmware. All other firmwares are locked and yours is one of them.
Click to expand...
Click to collapse
Thanks a lot stoney. And I have no way of going backwards, I presume?
nabril15 said:
Thanks a lot stoney. And I have no way of going backwards, I presume?
Click to expand...
Click to collapse
No problem. And you are correct, once the phone has been updated past the MDL firmware, there is no going back. Check Ebay, you might be able to find one still on the MDL firmware. I have an AT&T S4 that's still on the MDL firmware that I bought off Ebay. If you find one, I have a guide here in the forums that covers how to operate the MDL firmware and such.
@StoneyJSG or anyone
Might you know how I can clear dalvik cache? I don't have twrp installed, and that's the only way that I know how to.
Can I simply erase the contents of the /data/dalvik-cache directory?
nabril15 said:
@StoneyJSG or anyone
Might you know how I can clear dalvik cache? I don't have twrp installed, and that's the only way that I know how to.
Can I simply erase the contents of the /data/dalvik-cache directory?
Click to expand...
Click to collapse
If you have root, you can use an app called root cleaner. It has an option to clear dalvik.