I am on 4.16.401.10 Is this the current build? If not what is the current and are they incremental? I am S-OFF and rooted using Venom rom. Thanks!
That rom isn't based off Verizon software. .401 is international build. Are you asking if you are up to date on firmware? If so, boot to your boot loader and tell me the os version listed there.
I have OS version 4.17.605.5
Your version of firmware is 4.17.605.5. These most recent that I am aware of, is 4.17.605.9 . The person that posted before you, dottat, and whom I have great personal respect for, is the dev that brought us this FW. It includes the patch for stagefright. I have been running it now fort a few days with lollisense ROM (I too like venom, I currently have 4.6.0 in multi ROM but have not yet booted it). Will probably do that now that you have reminded me by way of this post.
Anyways the firware you want can be found here. Be sure to thank dottat (and the other dev's out there as well) for his hard work at keeping our devices running smoothly and helping out from time to time when we run into trouble.
Good luck
Related
Hi everyone, quick newbie question for you if you could be kind enough to answer it.
Yesterday I managed my first root and flash. My aim was to install the latest version of cyanogen on my s3, and following a tutorial everything went well, I'm now rocking kit kat. The only problem is that I've just realised I installed a sspencer10 Rom, which have since been discontinued, meaning I'm not going to get any updates, and there are some more stable snapshots that have been released on the official cyanogen site since that discontinuation.
I thought it would be easy to remedy: just flash an official Rom, just like I flashed the sspencer10 one yesterday - but the cyanogen install guide has this warning: 'you must be a 4.2.2 or older build or this will not work. In fact, if you try to use this method on a newer revision, you will almost certainly brick your device. Seriously don't try it. Downgrading won't work either. If you've updated, a qfuse is already tripped and any attempt to downgrade will also result in a brick.'
I'm hoping they mean that about stock upgrades and not cyanogen ROMs, but they don't say anything about that.
Can I flash a new cyanogen without bricking?
Thanks!
Noam Chomsky said:
Hi everyone, quick newbie question for you if you could be kind enough to answer it.
Yesterday I managed my first root and flash. My aim was to install the latest version of cyanogen on my s3, and following a tutorial everything went well, I'm now rocking kit kat. The only problem is that I've just realised I installed a sspencer10 Rom, which have since been discontinued, meaning I'm not going to get any updates, and there are some more stable snapshots that have been released on the official cyanogen site since that discontinuation.
I thought it would be easy to remedy: just flash an official Rom, just like I flashed the sspencer10 one yesterday - but the cyanogen install guide has this warning: 'you must be a 4.2.2 or older build or this will not work. In fact, if you try to use this method on a newer revision, you will almost certainly brick your device. Seriously don't try it. Downgrading won't work either. If you've updated, a qfuse is already tripped and any attempt to downgrade will also result in a brick.'
I'm hoping they mean that about stock upgrades and not cyanogen ROMs, but they don't say anything about that.
Can I flash a new cyanogen without bricking?
Thanks!
Click to expand...
Click to collapse
You're right, they're talking about flashing a ROM from the new stock 4.3 software, not if you've already successfully rooted, flashed a custom recovery, and flashed a ROM. You'll be fine, just do a factory reset/wipe before flashing.
It's a little strange that they'd mention 4.2.2, since the S3 never had an official 4.2.x release from Samsung, we went straight from 4.1.2 to 4.3.
Brilliant, thanks so much Jacquestrapp. Downloading that snapshot now - hoping for a bit more stability!
Yup, all worked perfectly - just tried recreating crashes that were happening in the earlier rom and I can definitely say the update is a huge improvement on stability. Just hoping that impression lasts! If necessary there shouldn't be any trouble with downgrading to cyanogen 10, right?
Noam Chomsky said:
Yup, all worked perfectly - just tried recreating crashes that were happening in the earlier rom and I can definitely say the update is a huge improvement on stability. Just hoping that impression lasts! If necessary there shouldn't be any trouble with downgrading to cyanogen 10, right?
Click to expand...
Click to collapse
Right. Actually there is a fairly recent stable version of CM10, 10.2.1, released just last month.
Noam Chomsky said:
Yup, all worked perfectly - just tried recreating crashes that were happening in the earlier rom and I can definitely say the update is a huge improvement on stability. Just hoping that impression lasts! If necessary there shouldn't be any trouble with downgrading to cyanogen 10, right?
Click to expand...
Click to collapse
I don't think you'll need to downgrade, I'm running the latest of the CM nightlies and, so far, it's good. There were some problems with the camera, WiFi, etc. with the earlier nightlies but they seem to be all worked out and CM 11 is my daily driver now. Hope it works as well for you.
I am running the stock rom and flashed the new firmware last night ( 1.55.605.2 ) and am interested in running a rom that is based off of an older firmware. Is there any problem in doing this? Will it roll my firmware back to the old one?
I'm currently running the old version of SkyFall (1.3) based on the old firmware, and I updated my firmware today with no problems. So it should be fine, though ymmv. But whatever ROM you want to run will probably be updated soon anyway.
Sent from my VZW HTC One M8
Joeysface said:
I am running the stock rom and flashed the new firmware last night ( 1.55.605.2 ) and am interested in running a rom that is based off of an older firmware. Is there any problem in doing this? Will it roll my firmware back to the old one?
Click to expand...
Click to collapse
I can't remember exactly where I read it but somewhere in the myriads of posts about this OTA it is pointed out that with different hboots, recoveries, kernels and modifications to system files, framework etc. etc. it is almost inevitable that something may go awry.
If you have taken the trouble and time to migrate to a custom ROM, it usually makes sense to let your dev sort things out. On the other hand, if you aren't experiencing any problems with the new firmware, why roll back?
Beamed from the holodeck of my Nexus 7 FHD.
hgoldner said:
I can't remember exactly where I read it but somewhere in the myriads of posts about this OTA it is pointed out that with different hboots, recoveries, kernels and modifications to system files, framework etc. etc. it is almost inevitable that something may go awry.
If you have taken the trouble and time to migrate to a custom ROM, it usually makes sense to let your dev sort things out. On the other hand, if you aren't experiencing any problems with the new firmware, why roll back?
Beamed from the holodeck of my Nexus 7 FHD.
Click to expand...
Click to collapse
It's not so much that I am having issues as I am wanting to try a rom that is showing based on the older firmware and I don't want to cause any issues with that. On a related note, I am running the stock rom currently and flashed the firmware that Santod posted in RUU but my firmware shows that it is still the 1.12.605.11 even though hboot shows me on 1.55.605.2. Did I botch something?
Joeysface said:
It's not so much that I am having issues as I am wanting to try a rom that is showing based on the older firmware and I don't want to cause any issues with that. On a related note, I am running the stock rom currently and flashed the firmware that Santod posted in RUU but my firmware shows that it is still the 1.12.605.11 even though hboot shows me on 1.55.605.2. Did I botch something?
Click to expand...
Click to collapse
See if my post here answers your question/concern.
I urge you to read more of that thread if you have more questions or concerns, as most of them have been answered there.
And for reference:
Old software with new firmware is almost always fine.
Running new software with old firmware is when real issues usually arise.
santod040 said:
See if my post here answers your question/concern.
I urge you to read more of that thread if you have more questions or concerns, as most of them have been answered there.
And for reference:
Old software with new firmware is almost always fine.
Running new software with old firmware is when real issues usually arise.
Click to expand...
Click to collapse
Hey thanks for replying man, I haven't messed too much with manually flashing firmware and didn't want to screw something up. So does the OTA have some software elements to it as well because I've noticed that people who took it are showing the updated firmware and an "Official" or "Unofficial" status in their settings? I've read through a lot of the forums and saw the post you linked to I just wasn't sure if what you were referring to in that post was the same thing as flashing a rom that shows a specific firmware.
G
Joeysface said:
Hey thanks for replying man, I haven't messed too much with manually flashing firmware and didn't want to screw something up. So does the OTA have some software elements to it as well because I've noticed that people who took it are showing the updated firmware and an "Official" or "Unofficial" status in their settings? I've read through a lot of the forums and saw the post you linked to I just wasn't sure if what you were referring to in that post was the same thing as flashing a rom that shows a specific firmware.
Click to expand...
Click to collapse
Firmware is just firmware.
It's not a Rom. It's something that gets updated with the ota that cannot be flashed in a custom Rom.
So before updating to a newer software version based on the update it's best to flash the firmware as well or you just get the software and no firmware by flashing just the Rom.
The firmware is at a lower level on the device and persists through Rom flashing unless you take an ota or flash an ruu.
When running custom roms it's general rule of thumb not to take otas.
Less issues that way.
So to update everything like you would had you taken the ota, you flash firmware and software to be up to date.
In other words, I've provided the firmware part of the OTA.
You just need someone to post a rooted version of the software update now.
Sent from my HTC6525LVW using Tapatalk
NOT AT&T OFFICIAL FIRMWARE
The ROM in question is a 5.0.1 Android build and according to the original source should be good for GT-I9500/9502/9508/9508v versions. The nice folks over at XDA have been playing around with the new software for a few hours now and it appears to be a legitimate official Samsung firmware as opposed to the recent Aurora ports of the leaked Note 3 software.
A few things need to be noted about the Galaxy S4 ROM, though. First of all it has a Chinese region, so even though English is available as a system language, along with two variants of Chinese, some system messages will remain regionalized and so will some functions, like the weather widget.
A stock English keyboard is also missing, but that is easily fixable. Other than that the build seems to be doing well in terms of functionality. NFC, sbeam, GPS, Bluetooth, 3G DATA, Wi-Fi, all sensors for motion and light, hotspot function, Multiwindow all seem to be in working order, as reported by various early adopters.
If you are feeling adventurous and decide to check out the leaked Lollipop software remember to back everything up, as update will almost definitely wipe your internal storage. And if you are a little bit skeptical and wish to wait for the official OTA to start seeding, it shouldn't be long now, as the ROM seems to be just about ready for public consumption.
~~~ FROM THE MODERATOR ~~~ This is not as easy as some may Think...... Caution and an advanced understanding of your phone is recommended before flashing anything "Cutting Edge" releases as this is ....... Caveat ..... Remember you, and only YOU, are responsible for what you do to your phone...no one else.......... ~~~ oka1
http://forum.xda-developers.com/galaxy-s4/i9500-develop/rom-5-0-1-android-lollipop-official-t3005979
Please Make It For AT&T S4 ...
jack_ssl said:
Please Make It For AT&T S4 ...
Click to expand...
Click to collapse
This isn't as easy as it sounds... for several reasons.
I'm not going to really go into the details but basically if your not a firmware with LOKI support you won't getting to run a 5.0 ROM on the S4 for the time being. Updates to Safestrap, among other things need to be made, and with the changes in Lollipop it remains to be seen if it will work. Not to mention the build is Chinese, would be better of waiting for the official update for the U.S, Canada, or the U.K
We'll see what happens though ~
NighthawkXL said:
This isn't as easy as it sounds... for several reasons.
I'm not going to really go into the details but basically if your not a firmware with LOKI support you won't getting to run a 5.0 ROM on the S4 for the time being. Updates to Safestrap, among other things need to be made, and with the changes in Lollipop it remains to be seen if it will work. Not to mention the build is Chinese, would be better of waiting for the official update for the U.S, Canada, or the U.K
We'll see what happens though ~
Click to expand...
Click to collapse
It appears to be a ROM that you flash through ODIN. Would Safestrap and LOKI even matter at that point?
Apoplectic1 said:
It appears to be a ROM that you flash through ODIN. Would Safestrap and LOKI even matter at that point?
Click to expand...
Click to collapse
Even so, flashing it to your device will likely cause issues when trying to go back. If someone is brave enough to take the plunge go ahead and pull up terminal and check the aboot increment. Mind you, this isn't for our model and may brick your device.
We hopefully wait for lollipop for our beloved S4 it's matter of days already so we have to be patient
Sent from my SGH-I337M using XDA Premium 4 mobile app
Its also for the Octacore variant I believe, NOT the i9505 which is similar to our i337 (minis it has unlocked bootloaders). So ATT Variants I HIGHLY suggest not trying to flash this
RockRatt said:
Its also for the Octacore variant I believe, NOT the i9505 which is similar to our i337 (minis it has unlocked bootloaders). So ATT Variants I HIGHLY suggest not trying to flash this
Click to expand...
Click to collapse
I337 is non compatible with this rom.. After install you reboot to recovery.. Appears there is now a i337 edition bootloader providing..
As this is not working for this model before someone damages their phone I am closing this thread
Please don't post firmwares as "Official" if they are not meant for the exact model phone
Thanks
FNSM
Hi,
I am new to this particular phone. There's so much information here, and although I've tried to search through it I'm still overwhelmed by it all - so I'm hoping someone might be willing to help with a few questions.
I have the XT1540 model, and could use some help. I have the stock rom with TWRP intalled and backups. I was notified that I have the Marshmallow update available, but I can't install due to TWRP. I prefer to keep the Motorola provided ROM. Since this was just released, I assume no one has posted the Marshmallow "stock" rom - is that correct?
I know asking for an ETA is poor form, but you guys know these forums and what can be expected - any idea when a backup image of the Motorola provided Marshmallow rom might be posted?
I assume I can't restore the stock bootloader in order to complete the Marshmallow installation - is this correct?
Final question: Is there a highly stable, all-features-intact custom Marshmallow ROM that comes highly recommended?
Thanks in advance,
Chris
There is no estimate as to when the full stock of MM will be available. There is a TWRP backup of the final soak available over in the General forum. It's been the last soak for quite a while now and I suspect it's the final. I've run all the soaks and that last release is running perfectly on my XT1540 1gb model. It is a backup from a 2gb version but that doesn't matter, it works on either model. Once flashed you won't get the OTA but then with TWRP you won't get that anyway.
Sent from my SM-T530NU using Tapatalk
I'm a bit confused because I can't seem to find everything about that and will my cm11 ROM that I currently have installed and any other hboot2.15 ROMs still work after upgrading to 2.16 and does anyone else have any experience (bad or good) after upgrading to 2.16?
No, 2.15 roms won't work on the latest 4.x firmware (which contains hboot 2.16). The storage handling is completely different on the newer/leaked firmware. Therefore, flashing an outdated rom will result in the phone stating that your storage has a size of 0 MB. This makes the phone unusable and is only fixable by flashing a firmware 4.x-compatible rom via TWRP.
Aside from that, firmware 4.x is definitely better than version 3.x. The storage partitions get unified so that you won't run out of space for apps, anymore. And not to forget that the latest android 7 custom roms all require the newer firmware.
Make sure that you use one of the "good" guides that update the whole firmware. There are some posts that only explain how to update the hboot (e.g. in the themes section). That's not enough. If you only update that one single file then your phone lacks essential files from the newer firmware and this will result in bugs and lags of the roms that you're using. The guide in the general section is fine or you use the original guide in the maximus hd thread where the 4.x firmware got published first or you look for the unofficial RUU.zip that is hidden somewhere in the dev section.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
No, 2.15 roms won't work on the latest 4.x firmware (which contains hboot 2.16). The storage handling is completely different on the newer/leaked firmware. Therefore, flashing an outdated rom will result in the phone stating that your storage has a size of 0 MB. This makes the phone unusable and is only fixable by flashing a firmware 4.x-compatible rom via TWRP.
Aside from that, firmware 4.x is definitely better than version 3.x. The storage partitions get unified so that you won't run out of space for apps, anymore. And not to forget that the latest android 7 custom roms all require the newer firmware.
Make sure that you use one of the "good" guides that update the whole firmware. There are some posts that only explain how to update the hboot (e.g. in the themes section). That's not enough. If you only update that one single file then your phone lacks essential files from the newer firmware and this will result in bugs and lags of the roms that you're using. The guide in the general section is fine or you use the original guide in the maximus hd thread where the 4.x firmware got published first or you look for the unofficial RUU.zip that is hidden somewhere in the dev section.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Thank you very much for explaining it really well, same as for the problem that I'm experiencing with the "2nd partition" in app2sd! As soon as my dad gets home, he and I will update the firmware.
Danke vielmals! ^^
Edit:
Oh, and what is the most stable running android rom that you'd recommend? I don't really want to upgrade to the newest android versions because I don't want any lags :/
-----------Update----------------
Never mind, I already found my current ROM that I am using for HBOOT2.16 to download from F-L-Y-E-R
All android 7 roms are stable and they aren't laggier than the stock rom.
Link to the Lineage thread
Link to the Resurrection Remix thread
A link to the latest TWRP version for firmware 4.x can be found in my signature
I'm now also running lineage as I already installed it yesterday. As of now the ROM hasn't let me down just yet, and it seems that I will be able to use it as my daily driver ^^
So far I'm really enjoying lineage!