Related
Purchased my S4 at launch, only rooted it and never really got around to tweaking it much. It has slowed down a bit so now is the time.
I'm on MDL, stock 4.2.2, and rooted with TWRP 2.5.0.2 On to the questions/clarifications, hopefully these aren't egregious. I know the info is out there but for actually finding specific information, the xda forums are a bit overwhelming and sometimes conflicting...
1) Recovery - Latest/preferred recovery for the s4 (on MDL) with auto-loki baked in? Are any of the latest versions of TWRP/CWM dangerous/incompatible or can I just install the latest/greatest with ROM Installers and go from there?
2) Modem - Flashing an updated modem, regardless of ROM/OS # should not break anything and/or lock down the bootloader any more so than it already is at MDL, correct? Updating the baseband will have no effect on the build # and thus loki is still and option (versus safestrap)? Preferred modem at this time? (ATT, SF Bay Area)
3) ROMS - Any ROM, followed by loki patch or flashed via an auto-loki capable recovery should be fine, correct? Is a ROM specifically built for safestrap applications and thus would not work with MDL, or are ROMs noted as being safestrap ready just able to be used via safestrap, but loki as well?
4) Hard to keep track of all the ROMs and the builds and branches etc - Can anyone point me in the right direction of either a) the latest stock touch-wiz 4.4.4 ROM that can be flashed over MDL without essentially updating past MDL? b) the best/most recent pure google (Play Store S4 Edition) ROM, same story with not breaking MDL?
Again, I apologize I am sure the info is all buried in here somewhere, it just gets to a point where pointed questions rather than multiple 500+ post threads are hopefully less likely to brick my phone. Ideally I just want to get on the latest software (and enable screen casting, for one). Assuming it comes quick enough, once I get this process down I will probably make the jump to 5.0 when it is ready, anticipate a couple months? Who knows.
Thanks, much appreciated.
Norcalz71 said:
Purchased my S4 at launch, only rooted it and never really got around to tweaking it much. It has slowed down a bit so now is the time.
I'm on MDL, stock 4.2.2, and rooted with TWRP 2.5.0.2 On to the questions/clarifications, hopefully these aren't egregious. I know the info is out there but for actually finding specific information, the xda forums are a bit overwhelming and sometimes conflicting...
1) Recovery - Latest/preferred recovery for the s4 (on MDL) with auto-loki baked in? Are any of the latest versions of TWRP/CWM dangerous/incompatible or can I just install the latest/greatest with ROM Installers and go from there?
2) Modem - Flashing an updated modem, regardless of ROM/OS # should not break anything and/or lock down the bootloader any more so than it already is at MDL, correct? Updating the baseband will have no effect on the build # and thus loki is still and option (versus safestrap)? Preferred modem at this time? (ATT, SF Bay Area)
3) ROMS - Any ROM, followed by loki patch or flashed via an auto-loki capable recovery should be fine, correct? Is a ROM specifically built for safestrap applications and thus would not work with MDL, or are ROMs noted as being safestrap ready just able to be used via safestrap, but loki as well?
4) Hard to keep track of all the ROMs and the builds and branches etc - Can anyone point me in the right direction of either a) the latest stock touch-wiz 4.4.4 ROM that can be flashed over MDL without essentially updating past MDL? b) the best/most recent pure google (Play Store S4 Edition) ROM, same story with not breaking MDL?
Again, I apologize I am sure the info is all buried in here somewhere, it just gets to a point where pointed questions rather than multiple 500+ post threads are hopefully less likely to brick my phone. Ideally I just want to get on the latest software (and enable screen casting, for one). Assuming it comes quick enough, once I get this process down I will probably make the jump to 5.0 when it is ready, anticipate a couple months? Who knows.
Thanks, much appreciated.
Click to expand...
Click to collapse
I will try to help with a few of these questions, but others I am not familiar with very much. On that note DO NOT update your bootloader!!! It will be locked down further and Loki will NOT WORK. And you could NOT flash any kernels with safestrap. So with safestrap ONLY the stock kernel can be used. Now on to your questions...
1) I am using TWRP 8.1 if I remember correctly. You can find it in the Original Android Development section. It does NOT Auto Loki, so keep the loki-doki flashable zip on your sdcard OR use Roms that already have/use the boot.Loki kernels like ShoStock-i 8.1
2) Modem flashing will NOT lock anything up further as far as the bootloader. You can flash ANY or ALL of them from my modem thread. See which works BEST FOR YOU in YOUR AREA. I am in So Cal and the best for me has been either MDL. But I have and do test ALL of them. You can always flash back to whichever one works best for you.
3.) Like I said I use ShoStock-i 8.1 because it has and does EVERYTHING I need my phone to do and does it without any issues. I have NOT tried to use a Safestrap modified ROM so I have very little experience with that. Normally most devs will have two separate versions, one for safestrap compatible and one for us without safestrap. ShoStock-i is already built with Loki in the kernel so you do not NEED to flash Loki-Doki patch.
4) there are NO Touchwiz 4.4.4 Stock Roms for ATT yet. But I did try out one of the Touchwiz 4.4.4 T-Mobile based Roms and it worked perfectly. You can either get it from the ATT forums and I believe it is already lokified, or get it from the T-Mobile forum and make sure to flash Loki-Doki patch before booting up phone after flashing the ROM. Again the will NOT update your bootloader past your MDL bootloader, so you are good as you are with no worries. By the way on ShoStock-i 8.1 the screen casting to Chromecast works PERFECTLY without having to flash any other .apk's or mess with ANYTHING
This is the exact same boat I'm in. Trying to track down the answers as well. Will keep an eye here as well to watch for answers.
awesome reply thanks RockRatt, that just about covers it. I will maybe give the ShoStock ROM a go and see how I like it. As long as all the normal features are working fine, I should be good.
One last thing I forgot - Odin. I have the stock odin firmware files from when my phone was new (The MDL package). As long as I dont update the bootloader, I should be able to Odin back to the brand new in box state should something go awry or not dig the other ROMs, correct?
Thanks again,
Norcalz71 said:
awesome reply thanks RockRatt, that just about covers it. I will maybe give the ShoStock ROM a go and see how I like it. As long as all the normal features are working fine, I should be good.
One last thing I forgot - Odin. I have the stock odin firmware files from when my phone was new (The MDL package). As long as I dont update the bootloader, I should be able to Odin back to the brand new in box state should something go awry or not dig the other ROMs, correct?
Thanks again,
Click to expand...
Click to collapse
Yep. Just don't update the bootloader...So no flashing newer firmware that contains the bootloader files. Most if not all custom Roms do not have the bootloader files in them. So no problem flashing back to MDL stock if the need never arises. I still in fact have the original MDB bootloader installed that came with the phone before the MDL firmware update.
Ready to sell this phone... tried everything I know how to try... Dev Edition Verizon S5, CAN'T UPGRADE from stock NCG. The most I can do it root... any ROM I flash is nonfunctional on Verizon's network with NO SIGNAL. Replaced SIM, flashed modems, etc etc... I think I'm just not sure how to do it with a dev edition... seriously feel like I'm missing a step. Would like to start from scratch. Does anyone have a stock image of a G900V Dev Edition I could work from, since I'm starting to think the one I've been working from is somehow the incorrect version. Thanks!
http://www.sammobile.com/firmwares/
type g900v in search bar
DSA said:
http://www.sammobile.com/firmwares/
type g900v in search bar
Click to expand...
Click to collapse
I would but I'm trying to avoid locking the bootloader, if possible. Didn't intend on having a developer device, but now that I do, I'd like to try to maintain it's use as one. Bought this phone on swappa, seller didn't give any indication that it was a developer device. Now I'm concerned he did something to it prior to selling that is causing me difficulties. I don't think I should be having these network difficulties, but there could very well be something I'm supposed to be doing with the modem that I'm just unaware of. I figure if I can get back to the way this phone was when it was new (when the original seller bought it) I'd at least have a clean slate to work with.
gatorhater73 said:
I would but I'm trying to avoid locking the bootloader, if possible. Didn't intend on having a developer device, but now that I do, I'd like to try to maintain it's use as one. Bought this phone on swappa, seller didn't give any indication that it was a developer device. Now I'm concerned he did something to it prior to selling that is causing me difficulties. I don't think I should be having these network difficulties, but there could very well be something I'm supposed to be doing with the modem that I'm just unaware of. I figure if I can get back to the way this phone was when it was new (when the original seller bought it) I'd at least have a clean slate to work with.
Click to expand...
Click to collapse
Anything usable in here?
http://www.galaxys5update.com/galaxy-s5-stock-firmware/
kprice8 said:
Anything usable in here?
http://www.galaxys5update.com/galaxy-s5-stock-firmware/
Click to expand...
Click to collapse
I don't think so, but thanks... I think that's the same device firmware that the retail version comes with, which will lock my bootloader. I've actually considered just flashing it anyway and saying the hell with an unlocked bootloader, since I didn't really intend to have one to begin with and apparently there's nothing I can do with it, anyway (none of the unified builds work on my device, anyway) but this is a last-ditch effort to preserve it if i can, and I'm hoping some dev will be willing to help me diagnose my problem.
gatorhater73 said:
I don't think so, but thanks... I think that's the same device firmware that the retail version comes with, which will lock my bootloader. I've actually considered just flashing it anyway and saying the hell with an unlocked bootloader, since I didn't really intend to have one to begin with and apparently there's nothing I can do with it, anyway (none of the unified builds work on my device, anyway) but this is a last-ditch effort to preserve it if i can, and I'm hoping some dev will be willing to help me diagnose my problem.
Click to expand...
Click to collapse
It's not like there's a ton of development going on for Dev edition. I'm loving the retail version of the phone just rooted and running some Xposed. Like it so much, I went out and got one for the wife too and I paid full retail for both to keep my old unlimited data plan. Hers I just left out of the box stock. Will be interested to see how Lolipop looks when it drops to her phone. Sure hope we keep root with Lolipop, I use the heck out of my hotspot, to the tune of about 70gb/mo ...
gatorhater73 said:
I don't think so, but thanks... I think that's the same device firmware that the retail version comes with, which will lock my bootloader. I've actually considered just flashing it anyway and saying the hell with an unlocked bootloader, since I didn't really intend to have one to begin with and apparently there's nothing I can do with it, anyway (none of the unified builds work on my device, anyway) but this is a last-ditch effort to preserve it if i can, and I'm hoping some dev will be willing to help me diagnose my problem.
Click to expand...
Click to collapse
I'm far from a developer, but this may help. I also bought the phone without realizing what it was I was getting into and had similar problems flashing the Optimal rom on my dev edition s5. I could flash but phone would hang on the activation screen with no signal. I eventually succeeded. As near as I can recall this is what I did:
I dirty flashed Beantown 4.4.4 rom (twrp) over my 4.4.2 stock firmware. then flashed n12 firmware (included stock kernel, and modem) from dev edition make an update .tar thread (odin) (http://forum.xda-developers.com/showpost.php?p=56604757&postcount=2). I did a factory reset after flashing. Switched to art. Flashed optimal with clean reset, but did not flash kernel. Later flashed koontsez 4.4.4 kernel. Still running Optimal
Good luck.
JOrkin said:
I'm far from a developer, but this may help. I also bought the phone without realizing what it was I was getting into and had similar problems flashing the Optimal rom on my dev edition s5. I could flash but phone would hang on the activation screen with no signal. I eventually succeeded. As near as I can recall this is what I did:
I dirty flashed Beantown 4.4.4 rom (twrp) over my 4.4.2 stock firmware. then flashed n12 firmware (included stock kernel, and modem) from dev edition make an update .tar thread (odin) (http://forum.xda-developers.com/showpost.php?p=56604757&postcount=2). I did a factory reset after flashing. Switched to art. Flashed optimal with clean reset, but did not flash kernel. Later flashed koontsez 4.4.4 kernel. Still running Optimal
Good luck.
Click to expand...
Click to collapse
Had marginal success using this method... Have been able to maintain a 3G signal, but no LTE after first boot. Rather, when I first booted, I had LTE and thought I was good, but since my first reboot, I can only get 3G and nothing I do can get it back so far.
JOrkin said:
I'm far from a developer, but this may help. I also bought the phone without realizing what it was I was getting into and had similar problems flashing the Optimal rom on my dev edition s5. I could flash but phone would hang on the activation screen with no signal. I eventually succeeded. As near as I can recall this is what I did:
I dirty flashed Beantown 4.4.4 rom (twrp) over my 4.4.2 stock firmware. then flashed n12 firmware (included stock kernel, and modem) from dev edition make an update .tar thread (odin) (http://forum.xda-developers.com/showpost.php?p=56604757&postcount=2). I did a factory reset after flashing. Switched to art. Flashed optimal with clean reset, but did not flash kernel. Later flashed koontsez 4.4.4 kernel. Still running Optimal
Good luck.
Click to expand...
Click to collapse
This happened after I flashed the update.tar (with aboot.mbn removed) and I have note gotten LTE back. Is there something I can do with my aboot.bak that I'm missing?
I just got the Verizon variant of the Galaxy S5 (SM-G900V). I rooted it very easily using odin without tripping knox; that was easy.
I then began looking for ROMs; which for this phone, isn't easy with the locked bootloaders.
I came across a custom ROM, forgot off the top of my head but may go back to retry loading it.
Because these devices have locked bootloaders, any ROM flashed to it will need to have a separate bootloader flashed as well. The aforementioned ROM had one and I understood why, but after I odin flashed the new bootloader, i kept getting a black screen. OK no biggie, factory flash, re-root look for another ROM, except this time, I'm looking for a pre -rooted factory ROM. I came across a lollipop one, 0A8, was hoping for 0G5, but will deal with that later. Of course the ROM had to have, I guess for lack of a better word, a custom bootloader, or index, to tell the phone it's okay to use this software right? So now have lollipop, but have lost TWRP on boot. I'm not sure as to why this has happened, but it's a real pain I want to install and use ROMs on this phone. If I need to downgrade to have TWRP, that's no big deal. So here I am a lollipop stock ROM, rooted wihout TWRP, ugh.
Is there anyone who can help me find a solution to this, it's driving me mad. I just want to have a recovery installed and the klte version won't install. It must be a lollipop thing, but I would love to have cm12.1 when it comes out. And why does this stupid script keep popping up while I'm trying to type this. Just thought I'd share my frustrations or see if there is a way to get TWRP on lollipop?
Thanks in advance.
Hello,
Welcome to XDA.
To better assist you, your thread will be moved to your device Q&A forum linked below.
http://forum.xda-developers.com/verizon-galaxy-s5/help
The experts there may be able to help. Good luck.
U cannot load into twrp or safestrap above the n12 kernal.
If you want to access your recovery, you could try loading the n12 kernal via odin. Then use your recovery. Then reflash the right kernal for your rom via Odin to return to loading status.
That's what I hear is possible- you sound like you can rebuild if u get in trouble.
As for CM - we don't have an unlocked bootloader so that's unfortunately killing it at this time. We are stuck on stock rooted TW roms, or slight variations of TW roms.
Sent from my SM-G900V using XDA Free mobile app
Hi.. I'm in way over my head trying to install a more debloated Rom than the original stock. Unfortunately I didn't succeed very well.
I tried two different ROMS and both of them turned the Sim off and on every second or so. Lots of *pling* noises followed by a message that the Sim card was or wasn't present. It changed so much back and forth that I didn't even get a chance to enter the pin. I belive it is because of some combabillity issues between the rom and baseband/radio version
This lead me to the question: How do I know what rom and baseband would be the most suited for me? I'm living in Denmark (nordic country), but I simply can't figure what rom that is compatible with what baseband.
Boot into Odin mode and verify the model number. Then go to Sammobile.com, download a rom for your country,and install it with Odin.
Did you buy the phone in the country where it is being used?
came99 said:
Hi.. I'm in way over my head trying to install a more debloated Rom than the original stock. Unfortunately I didn't succeed very well.
I tried two different ROMS and both of them turned the Sim off and on every second or so. Lots of *pling* noises followed by a message that the Sim card was or wasn't present. It changed so much back and forth that I didn't even get a chance to enter the pin. I belive it is because of some combabillity issues between the rom and baseband/radio version
This lead me to the question: How do I know what rom and baseband would be the most suited for me? I'm living in Denmark (nordic country), but I simply can't figure what rom that is compatible with what baseband.
Click to expand...
Click to collapse
I noticed you'd posted a duplicate thread, I'm guessing it was by accident but I've removed it for you
Regards
Sawdoctor
Sorry if what I'm asking is obvious, but when I install a custom rom, I also need to make sure I install a compatible radio for my area, right?
Sammobile is only stock ROMS, right? And I'm trying to debloat her phone. So when installing a custom rom from this forum and either the reception is bad, it doesn't register Sim card properly or the like.. It might be because I need another baseband than the one that came with the rom right? And what do I need to look for in that regard?
Sorry, but I find it pretty complicated.
I recommend flashing a completely stock ROM, set it up, and make sure everything is working properly. If it doesn't work properly on a stock ROM, it is unlikely it will work properly on a custom ROM.
I find it best to run the latest bootloader and modem regardless of which ROM will be used with the phone.
Problems can sometimes occur when flashing current ROMs over old bootloaders and modems.
audit13 said:
I recommend flashing a completely stock ROM, set it up, and make sure everything is working properly. If it doesn't work properly on a stock ROM, it is unlikely it will work properly on a custom ROM.
I find it best to run the latest bootloader and modem regardless of which ROM will be used with the phone.
Problems can sometimes occur when flashing current ROMs over old bootloaders and modems.
Click to expand...
Click to collapse
Thank you for the already helpful reply.
The thing you say about always flashing newest modem regardless of rom, is very helpful. I didnt even know you could do that. But my problem persist:
I already flashed back to stock, and it runs fine. SO far so good. The problem is that out of 16 GB, the bloatware is justing taking up to much space. But the last two rom I tried both had problems recognising the SIM card (toggled present/not present all the time).
Thats not the case on stock.. So how do I find the proper modem for my phone to use with a custom rom?
I keep seeing a link to sammobile, but all I can find is the bloated stock rom (or I dont know what to look for). Can I grab just the modem somewhere?
When installing a custom rom, it changes the current modem right? AFAIK I have to flash the proper modem afterwards, right?
And therein lies my problem: I dont know how to find the most suited one for my country (which is denmark). And the one that comes with the roms seems to be the wrong ones.
PS: A follow up question: Kernel and baseband/radio/modem is not the same, right? The kernel is not region specific, as the baseband/radio/modem, right?
came99 said:
Thank you for the already helpful reply.
The thing you say about always flashing newest modem regardless of rom, is very helpful. I didnt even know you could do that. But my problem persist:
I already flashed back to stock, and it runs fine. SO far so good. The problem is that out of 16 GB, the bloatware is justing taking up to much space. But the last two rom I tried both had problems recognising the SIM card (toggled present/not present all the time).
Thats not the case on stock.. So how do I find the proper modem for my phone to use with a custom rom?
I keep seeing a link to sammobile, but all I can find is the bloated stock rom (or I dont know what to look for). Can I grab just the modem somewhere?
When installing a custom rom, it changes the current modem right? AFAIK I have to flash the proper modem afterwards, right?
And therein lies my problem: I dont know how to find the most suited one for my country (which is denmark). And the one that comes with the roms seems to be the wrong ones.
PS: A follow up question: Kernel and baseband/radio/modem is not the same, right? The kernel is not region specific, as the baseband/radio/modem, right?
Click to expand...
Click to collapse
Custom ROMs can't change your modem, they can't write to those partitions.
In other words, your modem will be the same no matter what. The only way to change it is to flash the appropriate modem files or an actual stock ROM.
SO with the stock rom working now, the modem/rom combination would not be the culprit if something doesnt work afterwards?
What could have been the issue with the sim card connecting and disconnecting every second on the other rom I tried? (Iperium/Imperial something)
came99 said:
SO with the stock rom working now, the modem/rom combination would not be the culprit if something doesnt work afterwards?
What could have been the issue with the sim card connecting and disconnecting every second on the other rom I tried? (Iperium/Imperial something)
Click to expand...
Click to collapse
What I said is that a custom ROM can't change your modem. But that doesn't mean it can't be affected by your modem.
You may want to read Imperium ROM's install instructions very carefully, cuz I'm pretty sure you missed something important.
Doh.. You might be right.. Ill try flashing the tar files in Odin.
But I just recently got my phone to behave when connecting on Odin.. It also connected back and forth all the time. Putting a USB hub in the middle solved it though (and made it possible to revert to stock). Any idea wht that was about? I reckon either some driver or USB power problem? But Im really fumbling understanding it all, and when it acts up at the same time, even the most simple problems can be hard to see through (because there is always the uncertainty that I misunderstood something basic)..
Just having this conversation helped me understand a lot better how the ROMs and modem is connected (or more precise: How they are not).
And I actually may have had the right baseband all along (Nordic Countries). I will know when I tried flashing the rom again.
Thank you very much
It doesn't matter where you are from, the phone should work with any baseband in any country.
The thing is that some ROMs (like Imperium here) may require a different modem to function properly. In this case, it may require the PG1 modem (listed in the Imperium thread) to solve your problems.
Before flashing a stock ROM, confirm the model # in download mode.
If you want a debloated stock ROM, you could flash a stock ROM, flash TWRP recopvery, flash supersu for root, and use Titanium Backup to freeze or uninstall apps.
So right now I tried flashing the Resurrection Remix ROM, but it wont make any calls (a voice just says that the number cant be reached, even though I know the numbers exist). What could be the case there?
The modem and bootloader may be too old.
can it also be to new?
I have consulted the below site several times, but the link is dead to the page where I can look up what modem to use.
Can someone please point me in the right direction of which to use?
This site: http://forum.xda-developers.com/showthread.php?t=2192025
What modem should I choose for my phone? Living in Denamrk and trying with the ressurection remix rom? I tried 3 different of the modems starting with XX but all have the same problem: I cant make any calls. It just says that "there isnt any members on the selected number".
Making calls works fine on stock rom
came99 said:
This site: http://forum.xda-developers.com/showthread.php?t=2192025
What modem should I choose for my phone? Living in Denamrk and trying with the ressurection remix rom? I tried 3 different of the modems starting with XX but all have the same problem: I cant make any calls. It just says that "there isnt any members on the selected number".
Making calls works fine on stock rom
Click to expand...
Click to collapse
The ones linked in the Imperium ROM thread are the newest.
And no, it can't be too new.
It's probably something related to your phone model not being fully supported by the ROM.
JDCTeam ROMs should work, because they support a wide range of S4 models.
I got stock rom to work (again again)
And now I managed to flash the JDC Team you recommended and still having the baseband from the stock rom (Which were able to make calls)
But whatyaknow.. I STILL cant make outgoing calls on the custom roms! What in the world can be the problem? I spent the whole day on this.
.. I should be able to make outgoing calls without flashing Gapps, right?
Yes, you should be able to make calls without gapps.
You flashed the latest stock rom and confirmed everything works?
You confirmed the model number in download mode?
hi, im new here. I have a question regarding my galaxy s4 i9505 which is already stated in the title. Im currently using Optimized Cm13 by JDC team which runs in my very old bootloader I9505ZHU and modem. Though i dont have any problems with it, i would still like to update to later version of bootloader like i9505XX that is where the custom rom is based. So is it possible?
Yes.
There is a guide and links to modem files in the S4 General Section.
The guide is by the user Bon_Bon. It's pretty detailed. Though I'm not sure if the modems and bootloaders listed there are the most recent, but they certainly aren't that old either.
Also, you may find that going to the last pages of that thread, users have posted the latest modem/bootloader combo. If not, there's another - older - modem thread that may have them.
Another way to get the latest bootloader and modem on the phone is pretty simple: use TWRP to backup your exiting ROM, flash the latest stock ROM from sammobile.com with Odin, flash TWRP with Odin, and restore backup from TWRP.