Database Users

[Q] 16gb specific ROMs install on 32gb or 64gb S4?

Maybe it's a stupid question to many, but... I have the chance to order a 32gb korean version of the S4 off Taobao.com, and since I live in China it's quite convenient. The only issue I have is that I refuse to use an android phone without rooting it, and I've been a happy Wanam user for a long time on my S3.
The taobao seller states that 16gb ROMs CANNOT be used for 32gb models AT ALL, but I know better than blindly trusting ignorant Chinese vendors who usually don't know what they are talking about (personal experience).
It does not matter whether it's 9500, 9505 or whatever, this seller has all the models (even 9508 dual sim), I just want to understand if SIZE is a problem or not... Will I be able to just simply root it, and keep using the stock ROM at least? Or maybe I'll even be able to install ANY 16gb ROM of my choice? Or none of the above???
Thanks!
P.S. I searched the S4 forums but found no reference at all to this question...

UoMoTaLpA said:
Maybe it's a stupid question to many, but... I have the chance to order a 32gb korean version of the S4 off Taobao.com, and since I live in China it's quite convenient. The only issue I have is that I refuse to use an android phone without rooting it, and I've been a happy Wanam user for a long time on my S3.
The taobao seller states that 16gb ROMs CANNOT be used for 32gb models AT ALL, but I know better than blindly trusting ignorant Chinese vendors who usually don't know what they are talking about (personal experience).
It does not matter whether it's 9500, 9505 or whatever, this seller has all the models (even 9508 dual sim), I just want to understand if SIZE is a problem or not... Will I be able to just simply root it, and keep using the stock ROM at least? Or maybe I'll even be able to install ANY 16gb ROM of my choice? Or none of the above???
Thanks!
P.S. I searched the S4 forums but found no reference at all to this question...
Click to expand...
Click to collapse
As long as you're flashing a i9505 ROM to an i9505-like(aka U.S. Carriers variants) device, and an i9500 ROM to an i9500-like device, you'll be just fine. Don't try to flash unlike devices(i.e. i9505 to i9500) though. Best case scenario, the flash will fail. Worst case, you'll brick the device.
Internal storage capacity has never, to my knowledge, had anything to do with what you could or could not flash.

unremarked said:
As long as you're flashing a i9505 ROM to an i9505-like(aka U.S. Carriers variants) device, and an i9500 ROM to an i9500-like device, you'll be just fine. Don't try to flash unlike devices(i.e. i9505 to i9500) though. Best case scenario, the flash will fail. Worst case, you'll brick the device.
Internal storage capacity has never, to my knowledge, had anything to do with what you could or could not flash.
Click to expand...
Click to collapse
That would be my same guess, although the seller was adamant to the fact that it won't absolutely work (he even declared that he tried himself...). Though I agree with you, I'll wait for some concrete proof, when 32 and 64 gb versions will be more widely available, or at least until someone comes out with a first-person experience of this.
Anyway, thanks

UoMoTaLpA said:
That would be my same guess, although the seller was adamant to the fact that it won't absolutely work (he even declared that he tried himself...). Though I agree with you, I'll wait for some concrete proof, when 32 and 64 gb versions will be more widely available, or at least until someone comes out with a first-person experience of this.
Anyway, thanks
Click to expand...
Click to collapse
I don't want to call the guy out... but that seller has some very funny ideas; likely he was trying to flash unlike devices. If you want further feedback, I'd suggest posting this question over in the AT&T forums since the 32gb is more widely released. Further, from my past experiences, I've successfully flashed ROMs intended for the Developer Edition(64gb) of the HTC One onto my 32gb.
Let's say, hypothetically, he's correct--the developers who create the ROMs would be required to, perhaps not by forum rules but more so out of "I'm not responsible if you do this," declare their ROMs only usable by certain phones with certain storage capacities?
I will applaud you for taking your time, reading, and doing research before jumping into the fray. Is this your first phone you've rooted?

unremarked said:
I don't want to call the guy out... but that seller has some very funny ideas; likely he was trying to flash unlike devices. If you want further feedback, I'd suggest posting this question over in the AT&T forums since the 32gb is more widely released. Further, from my past experiences, I've successfully flashed ROMs intended for the Developer Edition(64gb) of the HTC One onto my 32gb.
Let's say, hypothetically, he's correct--the developers who create the ROMs would be required to, perhaps not by forum rules but more so out of "I'm not responsible if you do this," declare their ROMs only usable by certain phones with certain storage capacities?
I will applaud you for taking your time, reading, and doing research before jumping into the fray. Is this your first phone you've rooted?
Click to expand...
Click to collapse
Not at all, I rooted my first HTC Legend years ago, then my current S3,and so on. Happy user of Wanamlite ROM on my current S3 at the moment. Anyway, I guess our idea is correct. Not to belittle the vendor's experience, but in MY experience PRC people can be quite often very ignorant, or appear so at the very least, and declare the impossibility of an action or a request just to avoid any sort of responsibility in case the crap hits the fan... Think it as a sort of "ultimate disclaimer": I told you not to do it, so if you try and break it it's your problem.
After saying all this, I guess I'm in no rush since my S3 is still working like a charm after more than one year, I'm just exploring the S4 alley since I bough a SUPERCOOL Nolan bluetooth helmet for my bike, I use 2 sim cards at the same time (1 personal=S3, 1 work=HTClegend) and the HTC Legend's bluetooth is sort of fried So I was looking for a way to upgrade things.
I'll follow your suggestion and try to post in the AT&T section as well.
Thanks!

[Q] Handful of slightly random questions

1. Is SafeStrap the only custom recovery currently available for the Verizon Variant of Samsung's S4 (i545) on build ME7?
2. In general, are there ways to partition ROM slots in order to share data? For example, could stock be installed in the stock slots designated allotment for system, and another (CM or something) on the custom ROM 1's system area, but they both share data?
3. How does a manufacturer know if a unit has been rooted?
4. What are some apps that might be considered necessities on a rooted S4 (for instance, the multi-window fix)?
5. What is your idea of the perfect ROM?

Crackow97 said:
1. Is SafeStrap the only custom recovery currently available for the Verizon Variant of Samsung's S4 (i545) on build ME7?
2. In general, are there ways to partition ROM slots in order to share data? For example, could stock be installed in the stock slots designated allotment for system, and another (CM or something) on the custom ROM 1's system area, but they both share data?
3. How does a manufacturer know if a unit has been rooted?
4. What are some apps that might be considered necessities on a rooted S4 (for instance, the multi-window fix)?
5. What is your idea of the perfect ROM?
Click to expand...
Click to collapse
1. You might want to ask that on the Verizon Galaxy S4 forums -> http://forum.xda-developers.com/forumdisplay.php?f=2314 . This one is for the Google Play Edition, International and International LTE variants so there could be a little difference in the hardware and software.
2. (I think we'd need a dev to answer that)
3. Well, recently, we discovered that the GS4 seems to have an active e-fuse within it, which isn't good news because (in most cases - I think it's different in Europe) once it's tripped ( ie; Knox will show an 0x1 on download mode) there goes your warranty. Once you have updated to the new Knox bootloader, you can't downgrade either but there is an ongoing development on the Note 3 forums that suggests that there is now a way to get around the Knox bootloader (it remains 0x0) when you flash a pre-rooted ROM.
4. The only necessary app IMO is Titanium Backup (and eventually ROM Manager when development gets farther).
5. My idea of a perfect ROM is one that's hybrid stock and AOSP. I like AOSP ROMs as they've almost always had better battery life (there's less bloat) but the camera has always been a weak point because Samsung's camera has always been proprietary so our devs will never see the source which they would probably need to adapt to their ROM projects. The closest ROMs that has gotten to that IME has been ParanoidAndroid and SlimBean.
HTHs
P.S.: Someone correct me if I'm wrong about any points here.

I'm sorry that I posted that question in an inappropriate area, I hadn't realized. :silly:
The inclusion of the eFuse is absolutely terrible news. There is, however, a tiny ray of hope: that is a Knox feature. Knox is not yet active in ME7 build, so (fingers crossed) the eFuse may not be in use, yet. Still, why would Samsung have included security hardware that they are not using whatsoever? Isn't part of the beauty of an Android product the freedom that comes along with owning one? These large companies are beginning to closely resemble the fruity fiends from the other side. Although we may have taken extra freedoms with our devices, we must still be protected from manufacture error. Is this to say, for instance, that if I were to flash my S4 (that happens to need to be replaced, the processor has a terrible heat problem), then Samsung would take a look at the phone, determine that it had been previously flashed, and force me to live with it literally burning holes in my pocket?

Crackow97 said:
I'm sorry that I posted that question in an inappropriate area, I hadn't realized. :silly:
The inclusion of the eFuse is absolutely terrible news. There is, however, a tiny ray of hope: that is a Knox feature. Knox is not yet active in ME7 build, so (fingers crossed) the eFuse may not be in use, yet. Still, why would Samsung have included security hardware that they are not using whatsoever? Isn't part of the beauty of an Android product the freedom that comes along with owning one? These large companies are beginning to closely resemble the fruity fiends from the other side. Although we may have taken extra freedoms with our devices, we must still be protected from manufacture error. Is this to say, for instance, that if I were to flash my S4 (that happens to need to be replaced, the processor has a terrible heat problem), then Samsung would take a look at the phone, determine that it had been previously flashed, and force me to live with it literally burning holes in my pocket?
Click to expand...
Click to collapse
No worries, it's still an S4 after all. Samsung's diving for gov't and BYOD enterprise solutions now that Blackberry's demise is almost certainly a forgone conclusion. For that, they need to have good security on these devices. And yes, with this, Samsung can definitely blame the consumer for hardware issues once the warranty has been voided. One of the supposed reasons this is going on right now (according to someone quoting Samsung) is that Samsung's gotten tired of taking in warranty repairs that are due to ppl not following instructions and either frying their internals or hard bricking. In the case of OC'g, I can see where they are coming from because it's also a fact that when you OC a processor on a PC, it will shorten it's lifespan. Personally, I think it's a cop out from that whole SGS3/SGN2 SDS disaster and that was (IMHO) a QC issue. In any case, between designgears & Chainfire (and brought to us by DjeMBeY), there seems to be a bit of a solution now on how ppl can safely root their phones post Knox install.

New to S7... Why are there only 3 roms posted here?

Is there something I'm missing?

Sammy locked the Bootloader

Yup. This is the most highly sought after device with almost no developer support.
If you wanted root then you should get pretty much any other phone.

if you change the Android Code, you have to share it.
ahq1216 said:
Sammy locked the Bootloader
Click to expand...
Click to collapse
Correct me if I am wrong, but according to the Android Platform User Agreement (I think), if you change the Android Code, you have to share it. Or some form of developers open source agreement. Correct?

So there has been no root accomplished whatsoever on the T-Mobile S7? If that's true, then I'm hanging on to my Note 7 and selling the S7E.

Binary100100 said:
Yup. This is the most highly sought after device with almost no developer support.
If you wanted root then you should get pretty much any other phone.
Click to expand...
Click to collapse
Then what is the post in your signature about?
https://forum.xda-developers.com/ve...sed-unroot-t3411039/post67605246#post67605246

And what's the deal with the engineering bootloader?
http://www.theandroidsoul.com/root-t-mobile-s7-edge-engineering-bootloader/
Looks like S7 has had an unlocked bootloader with this for a while... Still very confused as to why there are no roms here.

unkellsam said:
Then what is the post in your signature about?
https://forum.xda-developers.com/ve...sed-unroot-t3411039/post67605246#post67605246
Click to expand...
Click to collapse
unkellsam said:
And what's the deal with the engineering bootloader?
http://www.theandroidsoul.com/root-t-mobile-s7-edge-engineering-bootloader/
Looks like S7 has had an unlocked bootloader with this for a while... Still very confused as to why there are no roms here.
Click to expand...
Click to collapse
I suppose you really need to read a bit more.
For all Qualcomm US devices the bootloader is LOCKED.
This is well known and documented. Root is possible only with an engineering kernel. The page that you referenced is inaccurate as it referenced an engineering bootloader. It's actually an engineering boot.img file that the writer mistook for a bootloader. Again... it's an engineering kernel not engineering bootloader.

unkellsam said:
So there has been no root accomplished whatsoever on the T-Mobile S7? If that's true, then I'm hanging on to my Note 7 and selling the S7E.
Click to expand...
Click to collapse
There is, but it's very unstable. Phone tends to lag and overheat due to the (something i dont understand).

serendipityguy said:
Correct me if I am wrong, but according to the Android Platform User Agreement (I think), if you change the Android Code, you have to share it. Or some form of developers open source agreement. Correct?
Click to expand...
Click to collapse
Well, yes and no. Parts fall under GPL, and parts of what Samsung uses to enable full functionality of the phone are NOT. The fact that they use special digital signatures in the boot process to prevent loading unsigned code is totally up to them (i.e. its all the stuff that happens before "android" starts...

sbaeder said:
Well, yes and no. Parts fall under GPL, and parts of what Samsung uses to enable full functionality of the phone are NOT. The fact that they use special digital signatures in the boot process to prevent loading unsigned code is totally up to them (i.e. its all the stuff that happens before "android" starts...
Click to expand...
Click to collapse
But arn't there other S7 roms from Verizon, AT&T and Sprint having developers pushing out custom kernels? Is this something that T-mobile can release but won't?
Google gives/updates the OS, Samsung gives the S7 hardware / Updated OS - Patches the OS & then gives to the Carriers (Tmobile) and they plug in their hellware (Bloatware), surely they have the source or the ability to modify the stock rom when updates are being pushed out to the carriers.
When a New Stock drops, it is the phone carriers who modify the kernel's, boot animation, build property, and sets their modems and such . . . Not Samsung because they would not be want to push out the kernels, modems, build property, boot animation & custom roms for each phone carrier in each region of each county. So lf what I am thinking that our phone carriers developers are lame ducks....
Going the other way on this, how does Sam Mobile play into this? how is it that they are able to host the roms on their servers? Arn't there any links from Samsung to host the roms?
Please if I am wrong, please someone correct me.

It's complicated...
Samsung locked the bootloaders on all US (Qualcomm) S7 but left the bootloader unlocked on international (Exynos) roms and some international Qualcomm roms.
This sucks and hopefully is not repeated on the upcoming S8 which may be Qualcomm only.
Last summer, an engineering bootloader was leaked and a group of people here got a root that uses the engineering bootloader. It's not perfect, as it forces people to use a non-production kernel. More people here came up with settings to get the most out of that kernel.
Right now we are in the middle of the transition to Android 7 and the engineering root doesn't work with it presently. Until a solution for that is reached
At the same time, the international rom deveopment has gone smoothly with over a dozen roms updated and a few tweaked kernels. The Exynos phone itself seems to be faster and with better battery life (but worse reception) compared to a standard qualcomm. Rooted with a custom kernel on both, it's like night and day how much better the exynos performance is. Some people ported T-mobile wifi calling and Volte (through CSC settings) to the international version, so for a certain user (of which I am one), the ideal root solution is to run a full speed exynos 930F on Android 7 and retain t-mobile functionality.

unkellsam said:
Is there something I'm missing?
Click to expand...
Click to collapse
Samsung blows

T-Mobile and Samsung both ****ed up around this time
Sent from my SM-G935T using XDA-Developers Legacy app

fracture8 said:
T-Mobile and Samsung both ****ed up around this time
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
I hear you.
Im gonna pay off the half of the phone in 7 months and then will jump ship to a one plus 4/5 when its released.
So much wasted potential

I would get the G935F.
serendipityguy said:
But arn't there other S7 roms from Verizon, AT&T and Sprint having developers pushing out custom kernels? Is this something that T-mobile can release but won't?
Google gives/updates the OS, Samsung gives the S7 hardware / Updated OS - Patches the OS & then gives to the Carriers (Tmobile) and they plug in their hellware (Bloatware), surely they have the source or the ability to modify the stock rom when updates are being pushed out to the carriers.
When a New Stock drops, it is the phone carriers who modify the kernel's, boot animation, build property, and sets their modems and such . . . Not Samsung because they would not be want to push out the kernels, modems, build property, boot animation & custom roms for each phone carrier in each region of each county. So lf what I am thinking that our phone carriers developers are lame ducks....
Going the other way on this, how does Sam Mobile play into this? how is it that they are able to host the roms on their servers? Arn't there any links from Samsung to host the roms?
Please if I am wrong, please someone correct me.
Click to expand...
Click to collapse
T-Mobile and Samsung keep playing around. I'm really hoping the Note 8 comes with an unlocked boot-loader or this may be there strategy going forward for the US.
rp3 said:
It's complicated...
Samsung locked the bootloaders on all US (Qualcomm) S7 but left the bootloader unlocked on international (Exynos) roms and some international Qualcomm roms.
This sucks and hopefully is not repeated on the upcoming S8 which may be Qualcomm only.
Last summer, an engineering bootloader was leaked and a group of people here got a root that uses the engineering bootloader. It's not perfect, as it forces people to use a non-production kernel. More people here came up with settings to get the most out of that kernel.
Right now we are in the middle of the transition to Android 7 and the engineering root doesn't work with it presently. Until a solution for that is reached
At the same time, the international rom deveopment has gone smoothly with over a dozen roms updated and a few tweaked kernels. The Exynos phone itself seems to be faster and with better battery life (but worse reception) compared to a standard qualcomm. Rooted with a custom kernel on both, it's like night and day how much better the exynos performance is. Some people ported T-mobile wifi calling and Volte (through CSC settings) to the international version, so for a certain user (of which I am one), the ideal root solution is to run a full speed exynos 930F on Android 7 and retain t-mobile functionality.
Click to expand...
Click to collapse
I was dead set on getting the Note 7 but after the fiasco i settled for the S7 edge. the G935F also has all the bands that t-Mobiel uses so we get band 12 as well. The issue with getting the G935F is trying to buy online as it has to be imported and still get insurance and so forth. Bought from B&H photo ( aa reputable US store) for insurance and good support. The g935F turned out to be a good gamble. As long as you wait there was alot of development. Since alot of us T-Mobile guys hopped over we were able to get Volte and wificalling ported over via various CSC edits and other workarounds. So we get alot of custom roms and T-Mobile support as well. Only issue you have to root and loose Samsung pay but for me that a okay lol.

Is any customizability permanently lost in OTA nougat update/ security patches?

Hi brand new to S7 edge (SM-G935T). Love this phone so far but would like to update to nougat and security patches ASAP as i had my last phone hacked and want to minimize that chance.
I have rooted/s-off/etc and played with custom ROMs, boot screens and animations, etc for MyTouch 4G Slide years ago.
After that i had some limitations modding a Galaxy S4.
I know sometimes system updates would lock you out of some levels of customization of the system.
So i'm wondering: will any of the OTA updates will lose me something i can't get back?
Thanks in advance

Well i think i can answer this myself now for any of my fellow befuddled would-be buyers.
As Eggleston11 replies here,
Eggleston11 said:
I have the G935F. As far as I understand these kernels are for Exynos only. Good luck if you are searching for a good development scene with the snapdragon version. There are a few ROMs and Kernels i think. I have no idea about quality.
Click to expand...
Click to collapse
So if you bought any of the US carrier models with the snapdragon chip you probably might as well take the OTAs to the last security update (Here is t-mobile's list of releases) for updates and security purposes, and then play with that release and decide if you would prefer to flash to the brandless ROM "G935u" instead of "G935t", which won't come with the carrier's cruft. To specifically answer my OP question, it's still possible to root the latest version of them, for what it's worth, although not GOOD methods.
Sad face. I was beguiled by the xda-developers Samsung Galaxy S7 Edge page into buying the S7 Edge without realizing a lot (all?) of the cool stuff was for the exynos variant.

With the way things are now in the mobile world one should not put his faith in any one website. Most snap dragon chips come locked tight this day in age. My self included should have done much more research in before buying.... I'm am at least thankful for root.

Best Chance of Long Term Support - Sprint Network

Hello,
I am currently using a Samsung S4 (sprint network : using Ting; jfltespr) and I have been happily running Cyanogenmod 13.0 (20161218).
I dont tinker; I set it and forget it... once stable nor do I actively follow the tech as I end up longing for an upgrade.
Sadly there is no native support for LineageOS for my variant s4,
I would love to get the latest on the device and not have to spend any money;
I despise all of the funk on new phones and desire to keep it honed down, thus my desire to stick with LineageOS; (that is unless there is something better.... is there?)
I have also purchased a ouraring.com - but have some 2 months prior to receipt. The only reason I really couldn't use it as I am lacking android v7 on my S4 (already has requirement of bluetooth 4 Low energy requirement.
so I have 2 options: new phone or update s4 somehow
if someone has a suggestion for either I would be grateful.
I have started the painful task of spec diving, trying to optimize in the hopes that it will last a long time and be able to have a long support life under LineageOS.
Kinda narrowed down to Samsung S8 or Motorola X2 Play.
I look toward any feedback.
Best regards and Thanks for your time.
qu1nn

You can use jfltexx rooms most of the time, you can get the stable stuff from jdcteam