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!
Related
Hi all,
I don't under stand the meaning of mob terms firmware,rom ,system image
what is the difference between firmware and rom.
what the system image contains what it's use.
Thanks for your time
Regards,
Sudhish
sudhishchandra said:
Hi all,
I don't under stand the meaning of mob terms firmware,rom ,system image
what is the difference between firmware and rom.
what the system image contains what it's use.
Thanks for your time
Regards,
Sudhish
Click to expand...
Click to collapse
Rom= running system. i.e. windows or linux
Firmware= version. i.e. windows 7 or xp,etc.
I don't know what your asking in your second question.
Sent from my HTC Glacier using XDA App
Sorry, but...
So, what's baseband?
For example, for my phone the Latest SE firmware are:
2.1.1.A.0.6 / 2.1.1.C.0.0
and from that difference, the baseband changes...
So, using Your example may be first xp and second vista?
But where I can read what's are the difference between this two ones?
Is always suggested to change it, anytime a new one release's deployed?
And baseband? How is useful?
Thanks.
Cheers,
M.
Hi
When a rom is based on XXX, does it mean I have to download and install XXX first or is it included in the rom ?
For exemple http://forum.xda-developers.com/showthread.php?t=1506752
"Based on stock 2.3.6 Dxkt5"
This is the Asian 2.3.6 for Samsung Galaxy Ace.
I'm french and using european 2.3.6. (XWKT7) (not yet, but downloading. 2.3.4 atm)
Can I install the OmegaRom? And how?
Thanks
jjjackson56 said:
Rom= running system. i.e. windows or linux
Firmware= version. i.e. windows 7 or xp,etc.
I don't know what your asking in your second question.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
So how can I install firware , it's a nbh file(image file)
Difference between link ROM and firmware at Samsung Updates
Hello,
I am trying to revert back from the latest Jelly Bean update 4.1.1 to stock Samsung ICS. I was going to go through the ROM provided via XDA along with ODIN, but then I checked the Samsung Updates website, and the firmware they provide for the phone is much larger then the one you provided.
I am confused about:
1- what is the difference between the ROM and the firmware.
2- if there isn't any difference why is the one at Samsung Updates much larger then the one linked to here.
http://forum.xda-developers.com/showthread.php?t=1737855&highlight=stock+rom
3- If there is a difference how does one install firmware rather than ROMs.
4- is there a way to disable automatic updates once the ICS firmware or ROM is installed on the phone?
Thank you very much in advance,
-Z
zahink said:
Hello,
I am trying to revert back from the latest Jelly Bean update 4.1.1 to stock Samsung ICS. I was going to go through the ROM provided via XDA along with ODIN, but then I checked the Samsung Updates website, and the firmware they provide for the phone is much larger then the one you provided.
I am confused about:
1- what is the difference between the ROM and the firmware.
On xda interchangable words firmware is called the rom.
2- if there isn't any difference why is the one at Samsung Updates much larger then the one linked to here.
http://forum.xda-developers.com/showthread.php?t=1737855&highlight=stock+rom
3- If there is a difference how does one install firmware rather than ROMs.
Sam up dates stock Samsung firmware or a stock rom.
4- is there a way to disable automatic updates once the ICS firmware or ROM is installed on the phone?
Yes your settings .
Its normal to look in your phones forum for firmware advice .
jje
Click to expand...
Click to collapse
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
Hey guys! So I have a few questions about the oneplus one here, I'm checking for a friend and I always had a nexus where matching firmware doesn't really matter much. So here they are.
1) What happens if you have the wrong firmware for a rom? Softbrick? Hardbrick? Nothing at all?
2) For a Nougat rom, what firmware do you use? Since this phone hasn't got an official firmware update for Nougat yet.
3) Is there a special recovery here on XDA that can flash all roms? (there was one for the oneplus two) or is TWRP good for all roms?
What confuses me the most about oneplus devices is how the firmware works different from most Android devices. Thanks guys!
H4X0R46 said:
Hey guys! So I have a few questions about the oneplus one here, I'm checking for a friend and I always had a nexus where matching firmware doesn't really matter much. So here they are.
1) What happens if you have the wrong firmware for a rom? Softbrick? Hardbrick? Nothing at all?
2) For a Nougat rom, what firmware do you use? Since this phone hasn't got an official firmware update for Nougat yet.
3) Is there a special recovery here on XDA that can flash all roms? (there was one for the oneplus two) or is TWRP good for all roms?
What confuses me the most about oneplus devices is how the firmware works different from most Android devices. Thanks guys!
Click to expand...
Click to collapse
1)I tried all below firmware, nothing wrong happens, I cannot identify any differences. I'm now just use the stock firmware: DI.3.0.c6
* http://forum.xda-developers.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907
** actually this post copy the exact my same post from "cyanogenmod forum"
bacon_firmware_update_2015_05-15_DI.3.0.c6-00241.zip <--- Currently bundled with latest CM13 nightly
bacon_firmware_update_2015_10-15_.4.0.1.c7-00013.zip
bacon_firmware_update_2015_12-30_.4.0.1.c7-00011.zip
bacon_firmware_h2os_update_2015_12-30_.4.0.1.c1.11-00004.zip
bacon_firmware_oxygen_update_2016_01_22_.4.0.1.c7-00013
bacon_firmware_update_2016_1-25_.4.0.1.c7-00011.zip
2)I'm now using ROM: "lineage-14.1-20170126-Okeys-bacon" from https://forum.xda-developers.com/oneplus-one/development/rom-unofficial-okeys-builds-t3534899
* it provide firmware "DI.3.0.c6" by default
3)TWRP is preferred, it is powerful and support for all ROMs
xiaoguazh said:
1)I tried all below firmware, nothing wrong happens, I cannot identify any differences. I'm now just use the stock firmware: DI.3.0.c6
* http://forum.xda-developers.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907
** actually this post copy the exact my same post from "cyanogenmod forum"
bacon_firmware_update_2015_05-15_DI.3.0.c6-00241.zip <--- Currently bundled with latest CM13 nightly
bacon_firmware_update_2015_10-15_.4.0.1.c7-00013.zip
bacon_firmware_update_2015_12-30_.4.0.1.c7-00011.zip
bacon_firmware_h2os_update_2015_12-30_.4.0.1.c1.11-00004.zip
bacon_firmware_oxygen_update_2016_01_22_.4.0.1.c7-00013
bacon_firmware_update_2016_1-25_.4.0.1.c7-00011.zip
2)I'm now using ROM: "lineage-14.1-20170126-Okeys-bacon" from https://forum.xda-developers.com/oneplus-one/development/rom-unofficial-okeys-builds-t3534899
* it provide firmware "DI.3.0.c6" by default
3)TWRP is preferred, it is powerful and support for all ROMs
Click to expand...
Click to collapse
Thanks! So it's not as important as it seems? I notice some roms here on XDA specifically say to have the newest firmware, or a certain version. The rom is still expected to boot? And what's the worst case scenario? A soft brick that can be easily fixed with TWRP or something worse? Thanks for the reply! Like I said, I'm coming from a Nexus 6 where none of this firmware stuff really applies :angel:
H4X0R46 said:
Thanks! So it's not as important as it seems? I notice some roms here on XDA specifically say to have the newest firmware, or a certain version. The rom is still expected to boot? And what's the worst case scenario? A soft brick that can be easily fixed with TWRP or something worse? Thanks for the reply! Like I said, I'm coming from a Nexus 6 where none of this firmware stuff really applies :angel:
Click to expand...
Click to collapse
Yes the rom is a still expected to boot,though,the recommended frimware is to be used so as to avoid any bugs.
However,some roms do require the recommended frimware in order to boot but I don't think even if flash any rom which needs recommended frimware will take you in any kind of brick condition as when you flash a rom on incompatible frimware you'll see error in Twrp,if so happens you just need to have recommended frimware in your storage and flash it then flash the rom again and you'll not face any errors.
Good luck!
H4X0R46 said:
Hey guys! So I have a few questions about the oneplus one here, I'm checking for a friend and I always had a nexus where matching firmware doesn't really matter much. So here they are.
1) What happens if you have the wrong firmware for a rom? Softbrick? Hardbrick? Nothing at all?
2) For a Nougat rom, what firmware do you use? Since this phone hasn't got an official firmware update for Nougat yet.
3) Is there a special recovery here on XDA that can flash all roms? (there was one for the oneplus two) or is TWRP good for all roms?
What confuses me the most about oneplus devices is how the firmware works different from most Android devices. Thanks guys!
Click to expand...
Click to collapse
1. If you are using TWRP, nothing will happens. Because when you flash a ROM, TWRP will comparing your phone model with build.prop on the targeted ROM. Because based on my experience, somehow i download LineageOS for d802 and flash it to my bacon. TWRP gives an error and didn't flash any firmware. I don't know about CWM or other recovery
2. I'm using Lineage OS. It's pretty good so far. No bug or whatever
3. TWRP is good for all ROM. i think any recovery will do
Hiya.
Getting some real glitchy performance with the radio - 3G/4G and WiFi.
It's the latest version of Resurrection Remix 5.8.5 (7.1.2)
- Recovery
TWRP 3.0.2-0
- Bootloader
Tampered
Unlocked
VLE PVT SHIP S-OFF RL
CID-VODAP102
H-BOOT-2.16.0000
RADIO-1.20.50.05.16
openDSP-v33.1.0.45.1128
eMMC-boot
Aug 16 2013, 16:59:47:-1
I'm looking for a current download link for the latest available (and flashable) radio firmware, and a guide to installing just that - my home PC is a Linux Mint box.
If anyone has a better suggestion, please feel free to make it (other than wipe the caches from Recovery, reinstall the same ROM). Constant connection dropping is becoming frustrating.
A separate question -why do I need Magisk - what is its function relating to this ROM and does the ROM stop working without it?
Thanks,
Stuart
The One S doesn't support 4G/LTE. The fastest connection you can get with it is H+/HSPA+ (in some countries called 3.5G or 3G+).
You're already using the latest firmware files. Reflashing them most likely won't make a difference. Have you tested other roms? If Wifi and your mobile data connection work with them then it's a RR-related problem. The so called "data drop" was a quite common issue on older custom roms that weren't based on the One S's stock rom. The reason is (like for all phones that get shipped with different android flavours than vanilla android) that the custom rom devs can't use the OEM's proprietary codes which would be needed for using the hardware properly. It's the same reason for the camera being on custom roms so much worse than on stock rom on such devices.
The answer to your Magisk question depends on the question whether you need root or not. Like SuperSU (which was more commonly used in the past) it's a root app. LOS works perfectly fine without it.
Thanks for the reply, Flippy.
I was aware of the HSPA, I just forgot and wrote 3G/4G out of habit
Am I correct in thinking that the last 'stock' ROM for this phone was KitKat?
I was on Lineage after CM died, but there was an overheating issue which made me switch to RR. There was a certain amount of glitchiness, but it seems worse now. I did update to 1.35 and took the WCNSS and ADSP update at the same time. Seems a little bit better - but only a little bit.
On a personal note - which do you rate at the moment - RR or LO/S? Or any others?
Thanks.
Flippy498 said:
The One S doesn't support 4G/LTE. The fastest connection you can get with it is H+/HSPA+ (in some countries called 3.5G or 3G+).
You're already using the latest firmware files. Reflashing them most likely won't make a difference. Have you tested other roms? If Wifi and your mobile data connection work with them then it's a RR-related problem. The so called "data drop" was a quite common issue on older custom roms that weren't based on the One S's stock rom. The reason is (like for all phones that get shipped with different android flavours than vanilla android) that the custom rom devs can't use the OEM's proprietary codes which would be needed for using the hardware properly. It's the same reason for the camera being on custom roms so much worse than on stock rom on such devices.
The answer to your Magisk question depends on the question whether you need root or not. Like SuperSU (which was more commonly used in the past) it's a root app. LOS works perfectly fine without it.
Click to expand...
Click to collapse
The last official android version was 4.1 (firmware 3.x aka hboot 2.15). ? There's only the semi-official firmware 4.x (aka boot 2.16) based on Android 4.2 and leaked by llabtoofer that's newer than that.
Radio 1.35 and the corresponding Wi-Fi files are ported from a different HTC device (I always forget which one it is) and were only meant as a temporary fix for bilal_liberty's rom ports. They were never meant to be used with other roms and after the issues his ports suffered from got fixed he recommended not using these temporary fixes, anymore.
I personally use LOS. But my choice is only based on the fact that RR didn't exist when I switched to android 7 on the One S and that I'm too lazy, nowadays, to switch between roms every couple of weeks. The One S isn't my main device, anymore. I just want it to work in case I need a backup device.
Sent from my HTC One M9 using XDA Labs
OK, thanks a lot Flippy.
Flippy498 said:
The last official android version was 4.1 (firmware 3.x aka hboot 2.15). There's only the semi-official firmware 4.x (aka boot 2.16) based on Android 4.2 and leaked by llabtoofer that's newer than that.
Radio 1.35 and the corresponding Wi-Fi files are ported from a different HTC device (I always forget which one it is) and were only meant as a temporary fix for bilal_liberty's rom ports. They were never meant to be used with other roms and after the issues his ports suffered from got fixed he recommended not using these temporary fixes, anymore.
I personally use LOS. But my choice is only based on the fact that RR didn't exist when I switched to android 7 on the One S and that I'm too lazy, nowadays, to switch between roms every couple of weeks. The One S isn't my main device, anymore. I just want it to work in case I need a backup device.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I received my New Poco X3 Pro, waited 1 Week for unlock and flashed Arrow OS 11.
I did not install a Xiaomi ROM because I want a Custom ROM on there.
Do I need to update the firmware (or radio or baseband)?
How do I find out what firmware is currently on my phone?
Based on this site, the latest firmware would be V12.5.4.0.RJUEUXM.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
However, I do not find any clue about the baseband on my phone.
In Settings-about-Android version the baseband is listed but there is no version number close to V12...
How do I get the current firmware version and do I need to update it?
You have to decide wether to work with stock firmware or custom rom (firmware)... the stock is provided often in "waves" so it could be that you receive a new firmware over ota, but a friend with the same device will gett it 3 weeks later. with stock firmware you get some updates, but with custom nobody guarantees you new versions. I´m very happy with AICP 16.1, which distributes a new Rom Version every Friday... Tomorrow i will get a new version with regularyly smaller bug fixings. My version is from 4th of february ... i never updated radio or baseband with all my devices, normally you dont need to, its in the custom roms
I am talking about firmware, not the ROM.
The firmware/radio is updated separately.
since more than 20 years of mobiles i have never got a seperate(!) radio update (but i flashed different radio versions to adapt custom roms (from australia i.e) to local conditions). Afaik stock firmware made by manufacturer, adapted to the given hardware and build on the differnt Android versions. Custom Roms are the same but made not by manufacturer but by "free" developers. If it is not so, it would be nice to hear how it is in reality....
The Pixel Experience ROM contains this firmware images for radio or need to be update separately?
andris155 said:
The Pixel Experience ROM contains this firmware images for radio or need to be update separately?
Click to expand...
Click to collapse
You don't need to flash firmware because any of them should work. I flash many rom but haven't flash any firmware.
In an ideal world, the latest firmware should ideally provide performance optimization or bug fixes or securities updates or new features etc.
Of course, unlike drivers, they not obligated to keep us in loop what the update is about.
Lu5ck said:
In an ideal world, the latest firmware should ideally provide performance optimization or bug fixes or securities updates or new features etc.
Of course, unlike drivers, they not obligated to keep us in loop what the update is about.
Click to expand...
Click to collapse
performance opitmization , bug fix and securities update should be include in the rom and kernel. Firmware isn't rom so that should be no need.
Alec Chan said:
performance opitmization , bug fix and securities update should be include in the rom and kernel. Firmware isn't rom so that should be no need.
Click to expand...
Click to collapse
Firmware is an read only system and just like any system it has purposes which this case it provide instructions on how to communicate with the hardware. Just like any piece of codings, it can contain bugs or exploits or unoptimized codings like looping 10 times to do one thing.