Hello! I have a project that I am working on that involves a handful of Galaxy S4 devices. They were all purchased on ebay, so they are all different models with different versions of android. The goal is to get them running as close to the same software as possible.
The models that i have - as shown in the about phone settings - are
GT-I9505
GT-I9500
SGH-I337
SGH-M9194N
SGH-M919N
SGH-M919
From my understanding, all of these other than I9500 are qualcomm based and should therefore be able to run the unified jfltexx build from lineageOS. IF this is the case - and i am not ENTIRELY sure i understood all of that correctly - I am still out a build for the I9500. Are there any CM or lineageOS builds that will run on this hardware?
The i337 cannot run lineage if the bootloader is locked. I believe att locked the bootloader with the ota update for android 4.3.
The question about the I9500 and LineageOS has been seemingly asked at least once a week for the last several weeks. Unless you can provide an I9500 to a developer to develop upon, you will not see a properly functioning LineageOS build on the device.
Strephon Alkhalikoi said:
The question about the I9500 and LineageOS has been seemingly asked at least once a week for the last several weeks. Unless you can provide an I9500 to a developer to develop upon, you will not see a properly functioning LineageOS build on the device.
Click to expand...
Click to collapse
I do not have access to the devices, I just have a client who asked me some questions about the devices, and I admit that these Samsung devices confuse the hell out of me. This wasnt a "Damnit, gimme lineage now!" post, but more just me trying to get a handle on all the different models and their differences.
audit13 said:
The i337 cannot run lineage if the bootloader is locked. I believe att locked the bootloader with the ota update for android 4.3.
Click to expand...
Click to collapse
Samsung still has not provided an OEM bootloader unlock? I havent dealt with a non unlocked phone for years, so im actually asking. Is there no bootloader hacks, even a third party exploit that allows the bootloader to be reflashed?
As for the other models, if they all run a unified lineage build, how does that work with all the various carriers supported? do you have to reflash the correct radio after, or does lineage just not touch that when flashing?
I believe AT&T requested the bootloader lock as they have with the note 3, G2, etc. and there is no hack or way to unlock the AT&T s4 bootloader.
audit13 said:
I believe AT&T requested the bootloader lock as they have with the note 3, G2, etc. and there is no hack or way to unlock the AT&T s4 bootloader.
Click to expand...
Click to collapse
Great, thank you.
Related
I'm very interested in switching from my stock Verizon Note 3 ROM to CyanogenMod, but after a great deal of research I cannot tell with absolute certainty if http://wiki.cyanogenmod.org/w/Hlte_Info is the correct ROM for use with my Verizon Note 3. Is it the correct ROM?
Additionally, if http://wiki.cyanogenmod.org/w/Hlte_Info is the correct ROM for use with my Verizone Note 3, how do I work around their posted notice as follows? Such as, are there specific instructions for using ODIN?
"If you've applied the 4.4.x update to your hlte device, it is possible heimdall will have communication issues with your device. This is a filed bug already on the heimdall page and this warning will be removed when it is resolved. In the meantime, ODIN still works."
Karine said:
I'm very interested in switching from my stock Verizon Note 3 ROM to CyanogenMod, but after a great deal of research I cannot tell with absolute certainty if http://wiki.cyanogenmod.org/w/Hlte_Info is the correct ROM for use with my Verizon Note 3. Is it the correct ROM?
Additionally, if http://wiki.cyanogenmod.org/w/Hlte_Info is the correct ROM for use with my Verizone Note 3, how do I work around their posted notice as follows? Such as, are there specific instructions for using ODIN?
"If you've applied the 4.4.x update to your hlte device, it is possible heimdall will have communication issues with your device. This is a filed bug already on the heimdall page and this warning will be removed when it is resolved. In the meantime, ODIN still works."
Click to expand...
Click to collapse
If you are on RETAIL VZW N3, there is NO WAY to have anything but a stock or cutsom stock ROM.
If you are on a DEV EDITION VZW N3, check here.
I have the retail Verizon Note 3, and all other resources I've encountered indicate that the link I provided is a universal ROM for all Note 3.
Karine said:
I have the retail Verizon Note 3, and all other resources I've encountered indicate that the link I provided is a universal ROM for all Note 3.
Click to expand...
Click to collapse
That is universal for the international versions, which there are many. Without an unlocked bootloader, we cannot flash aosp, aokp, or cm based roms.
The bootloader issue is what prevents compatibility with the CM installer, but I don't believe it prevents ROM flashes through other means. And I've seen several threads that specifically state that universal covers Sprint, Verizon, etc.
Karine said:
The bootloader issue is what prevents compatibility with the CM installer, but I don't believe it prevents ROM flashes through other means. And I've seen several threads that specifically state that universal covers Sprint, Verizon, etc.
Click to expand...
Click to collapse
Ok. And why isn't this info blowing up the Verizon Note 3 forums? If I'm wrong, I'll admit that. But many smarter people that me have stated time and time again that it's not going to work. And I have seen no information that will lead me to believe otherwise. Can you provide links to where it's being stated we can flash this?
That's why I'm here, to sort whether it will work as all the information available seems unclear and split.
Ok, I got ya. There is info burried here. But as I understand it the ability to install custom roms requires an unlocked bootloader. When we got that leak of kk nc2, we obtained a locked bootloader the had a few "holes" in it (for lack of a better term). With that bootloader, there is the possibility of some exploits that can be applied in order to give us the ability to flash a cm rom amongst other things. But we're not there yet.
Best I can give you is to watch this thread for any news or development:
http://forum.xda-developers.com/showthread.php?t=2812650
Many thanks for the link.
I'm gonna back up Lefty here.
The retail version has a locked bootloader, which means we can't install a custom recovery or an alternate kernel, both of which are required to install non-touchwiz ROMs. (Not the case for the dev edition, which you would know if you had)
This is Verizon's doing. Samsung will provide phones with unlocked bootloaders to cellular companies, but verizon wants them locked down. I believe the only US company that sells bl-unlocked phones is T-Mobile. Lots of international carriers are bl-unlocked.
CM is mostly "universal" across ALL devices, because its based on AOSP straight from Google, and just has to be tweaked slightly for hardware differences. That's why CM builds for a note3 are "universal" -- the hardware is all the same. This comes at a price... last I've heard, the s-pen is just emulated as a mouse input, which is a bastardization of the technology. This is just an example. There are several compromises to running AOSP roms.
Sent from my SM-N900V using Tapatalk
Thanks for the great information. It's a shame that Verizon or anyone else locks the bootloader. It should be no matter to them what ROM I run.
I have searched and tried but i cant find any info on my specific phone . I have rooted other phones and this one seems to be the most difficult! Any help would be highly appreciated... heres my info.
VERIZON GALAXY S4
SCH-1545
5.0.1
I545VRUGOC1
KERNEL VERSION 3.4.0
BUILD # LRX22C.I545VRUGOC1
SECURITY SOFTWARE VERSION MDF V1.0 RELEASE 4 VPN V1.4 RELEASE 4
thank you
http://forum.xda-developers.com/galaxy-s4-verizon is where you want to go. This is the international S4 forum.
In short, your difficulties in rooting come from Verizon locking the bootloader.
WIsh i had found this thread yesterday since i have spent all day trying to figure out how the root this phone.... now i know why i cant.
bootloader locked
After reading your reply, I understand that there is no workaround for unlocking the bootloader. I was under the impression that this kernal SCH-I545_MD2_423399_Kernel.tar.md5 was for that. Of course it didn't work using Odin_v3.07.zip it kept failing.
The kernel and the bootloader are two different things. The bootloader is low-level firmware designed specifically to prepare the device to run the kernel. The kernel is the heart of Android. It provides the interface for the rest of Android to communicate with the hardware.
In devices not sold by AT&T or Verizon, the bootloader usually only checks to see if a kernel is present. If a kernel is present the bootloader hands off control to the kernel, which starts the operating system. In the case of AT&T and Verizon, and I am only speculating here because I have neither AT&T nor Verizon devices, the bootloader checks the kernel to ensure the kernel is not only AT&T or Verizon-approved, but the same age or newer than the bootloader, before allowing the system to boot. To prevent people from replacing this bootloader, AT&T and Verizon encrypt it so the bootloader's code cannot be manipulated to bypass the checks.
With an encrypted bootloader, rooting and custom ROMs are virtually impossible. Your attempt to install the kernel failed because the kernel was older than the bootloader. This is why, if you live in the US, you do NOT purchase a phone from AT&T or Verizon and instead, you do one of the following.
Purchase a device from T-Mobile, either outright or through installment plan. T-Mobile does not lock its bootloaders. You could also purchase a device from Sprint, but their service is the worst of the four major US carriers.
Purchase a device directly from Google (i.e. Nexus) or from device manufacturers like Motorola.
Purchase an international device and have it imported, keeping in mind that LTE may not function due to frequency differences.
S4 i 595 5.0.1 gof1 root finaly working
d1ppxdinhaze said:
I have searched and tried but i cant find any info on my specific phone . I have rooted other phones and this one seems to be the most difficult! Any help would be highly appreciated... heres my info.
VERIZON GALAXY S4
SCH-1545
5.0.1
I545VRUGOC1
KERNEL VERSION 3.4.0
BUILD # LRX22C.I545VRUGOC1
SECURITY SOFTWARE VERSION MDF V1.0 RELEASE 4 VPN V1.4 RELEASE 4
thank you
Click to expand...
Click to collapse
I AM NEW USER CANT POST OUTSIDE LI9NKS...... EMAIL ME AT [email protected] oe message me here and i will give you the links
Since I just got A S4 I have some questions. I mainly am used to nexus/moto devices in terms of roms/etc, and I know the process is entirely different with the S4.
The model is a AT&T S4. Updated to 5.0.1
I know I won't be able to unlock the bootloader, which is okay as long as I CAN have some hopes of running another firmware on it.
All I require is Root/Xposed, and maybe CM13..or any other android 6.0 based ROM. How feasible are my options? I won't know until I physically have it, but what should I look out for in terms of firmware/bootloader codes?
You cannot run any custom ROM unless the rom is based on a Samsung kernel which means no cm or aosp ROMs.
audit13 said:
You cannot run any custom ROM unless the rom is based on a Samsung kernel which means no cm or aosp ROMs.
Click to expand...
Click to collapse
that sucks. Guess I will sell it for a bit higher than I bought it and grab something else. Thank you.
I have an s4 (Canadian version, i337m) which doesn't have a locked bootloader and I find the phone okay with stock unrooted LP. I used to based my phone decisions on whether there was an XDA forum but my flashaholic days are behind me
Hi all.
So, the CM13 shapshot has arrived for the i9505 and I'm considering upgrading my phone. I've been running cm on it since I bought it from new a few years back. Stock android got rooted and replaced without ever upgrading it and as such the modem/baseband/radio (are these 3 words in fact covering the same?) and bootloader has never been updated either. Currently running CM11 M8. According to the app phone info, both baseband and bootloader is I9505XXUBMGA. As far as I can tell from a few searches, this is the latest pre-knox bootloader and from 4.2.2.
I'd prefer to leave the bootloader alone in order to not accidentally tripping knox later on. Should I update the modem/baseband/radio before flashing CM13 (as in do I need to?) or can I just leave it as it is?
Thanks.
I9505/jfltexx (International LTE)
Baseband: I9505XXUBMGA
Bootloader: I9505XXUBMGA
Is the phone under warranty? If not, tripping knox does not matter in my opinion. Also, many of the latest ROMs require an up-to-date bootloader and modem to function properly.
audit13 said:
Is the phone under warranty? If not, tripping knox does not matter in my opinion. Also, many of the latest ROMs require an up-to-date bootloader and modem to function properly.
Click to expand...
Click to collapse
I appreciate your reply.
No, there's no warranty left on the device. Just thinking that the device might be easier to sell eventually if knox is not tripped.
Do you know if the update is needed for 6.x to run properly?
Thanks
If you were looking to resell, you should have done so earlier. A quick look on Swappa shows the S4 can be bought, depending on version, for anywhere from 85-120USD, with the Exynos I9500 available for 180USD. That's a far cry from the 350USD I spent at the end of 2014 for my I9505. In fact, with the exception of the I9500, no international devices are available on Swappa at this time. All available units are either from US carriers or are the I337M, a Canadian model.
Being Swappa, most of these units likely have had Knox tripped. I know the device I purchased did, and I was quite relieved I wouldn't have to deal too much with that headache.
Yes, many 6.x ROMs require an up-to-date bootloader and modem. Ihave seen many posts from s4 and note 3 users where the baseband and imei were null after flashing an MM ROM without an updated bootloader and modem.
As for re-sale, the s4 is not commanding good prices as previously mentioned. The last used s4 sgh-i337m I purchased was in excellent condition for $120 CAD. An advantage with the i337m, i9505, and i9500 over the ATT i337 is an unlocked bootloader.
@audit13: I made a mistake buying my I9505, and focused too much on avoiding the locked bootloader. It's still a good little phone, and it's my backup device still, but if I paid more attention I would have had an I337M instead.
Yeah, the phone in it self is overall fine, just not super aosp compatible.
My I9505's bootloader is not locked, though, been running CM on it since I bought it.
Looks like I am going to look into updating bootloader and baseband before flashing CM13 then.
I appriciate your replies.
The i337m and i9505 are very similar and the same ROMs can often be flashed to both phones. I believe the jfltexx work for both models. The biggest difference between the phones are the frequency bands.
None of the s4 phones have a locked bootloader other than models from AT&T, Sprint, and Verizon as far as I know.
AT&T and Verizon. Sprint doesn't lock bootloaders.
HI, after reading numerous posts it appears I may be better off getting a different version Samsung Galaxy S5 than the one I have. I have the Verizon Samsung Galaxy S5 SM-G900V, 6.0.1 Marshmallow, with the CID 11 Toshiba eMMC chip. I want to end up with the Lineage OS installed and running Android 10 (or similar). To achieve that I would need to root the phone, unlock bootloader, install TWRP Recovery, flash ROM, etc. To do this on my phone is very complex and may not even be possible. My research has found that this may be done a lot easier on phones by different carriers (T-Mobile, U.S. Cellular, Sprint, AT&T) of the Samsung Galaxy S5, and/or with versions earlier than Marshmallow. My question is which carrier(s) do you think would be easier than the Verizon that I have? What versions/models of the Samsung Galaxy S5 have you successfully rooted, unlocked bootloader, installed TWRP Recovery? Thanks in advance for your advice.
The first 3 you listed have an unlocked bootloader. ATT has a locked bootloader.
dave678 said:
The first 3 you listed have an unlocked bootloader. ATT has a locked bootloader.
Click to expand...
Click to collapse
dave678 said:
I decided to give it a try on my Verizon Samsung Galaxy S5 SM-G900V, 6.0.1 Marshmallow, with the CID 11 Toshiba eMMC chip. Following the instructions for the CID 11 chip found in this Forum (https://forum.xda-developers.com/t/guide-root-bootloader-unlocks-and-more.3561529/#post-71202995) , I was able to root , unlock the bootloader, and install TWRP Recovery. Next I'll attempt to install a Lineage OS and current Android version.
Click to expand...
Click to collapse
?
After reading the above posts, I am more confused than ever. The EMMC apk does nothing when ran on my S5.
I don't know if I have an 11 or a 15 EMMC chip.
I read that an 11 cannot have lineageOS installed as the bootloader is locked. Then read the linked post 71202995 where 11 is allowing LineageOS.
I don't understand the chunks of code/programs that are used when the phone boots. I have looked for an explain of the Andriod boot process unsuccessfully. There is a sequence of events that happen, and TWRP and Odin must get plopped into the sequence in place of other things in order to intercept and take over to do the functions.
Is there any place that explains that? Or that can say "Nope, no good, you can't use Linage on your phone" or "Yup, you're good. Just follow this procedure"
I was all ready to try this and found the post saying the EMMC is key and blocks from any change. Locks you into Android 6.0.1(I think) ...
so already cooked/bricked a Fire 7 where there are comments eleventeen pages in that say "it won't work with 5.6.7.8... brick, read the OP" I read the OP and ten pages in and got nothing warning of a brick. Still got one. This is so confusing.
Where to start?
tom
Use the EMMC BrickBug app to check