Related
Intro:
I will likely regret announcing this as it means the handful of S10 owners that are outside china will likely update to it and nuke any rom they have installed.
This update is like the title says, updates your S10 to 3.2, likely very similar to the version rolling out for the S7
Requirements:
Be on a stock recovery
Instructions:
Download: Gallo_568_MR2_1.pkg
Copy to 'sdcard'
Install
Finished
Notice:
If you are one of the S10 owners PLEASE tell me what rom you are on BEFORE updating, as the majority of them will be lost to time. I would ask for a nandroid dump or NVflash dump, but those are not currently possible at the moment.
Here's what i'm interested in:
The rom version:
The build number:
The relative age of your s10: (if you can estimate when it left the factory)
An example: (Using this rom)
GALLO1A156815
201109270912
Several weeks away from arriving still...
IF YOU CAN INSTALL IT PLEASE UPLOAD THE UPDATE.PKG.DEC FILE OR WHATEVER IT IS FOR ME, IT CANNOT BE DECRYPTED BY ME
The file should be either
<sdcard>update.pkg.dec
a file located in <sdcard>\lost_dir
My ROM version is: GALLO1A154615
the build number is: 201107220948
I bought the tablet in China on 2011-09-05 from a Dell shop, and it had just arrived there, so could not have been long since it had left the factory.
Btw, the link on the post Gallo_568_201109270912_15_OTA.pkg is now broken. Says 404 at the moment.
However, I'm wondering if this is the same file though: mirror2.streakdroid.com/manii/Streak10/Gallo_568_201109270912_15.pkg? Should I use this file?
That's the same file, but dell re-released 568 and the file is different now (yea it's confusing)
The first 568 release was a semi-public one and anedotically there were issues with it.
The second 568 release seems to be fixed now, but I havnt actually installed it yet. It was put up about a week or so ago
My S10 arrived last week and it's also on 546, that seems to be the only shipped 3.1 rom.
The OP will be updated with the new link, but you can still get the same from using 'check for updates' from within the settings.
Be aware that 3.2 cant be rooted yet, I plan on porting CWM over some time next week, assuming there's no issues in doing it.
TheManii said:
That's the same file, but dell re-released 568 and the file is different now (yea it's confusing)
The first 568 release was a semi-public one and anedotically there were issues with it.
The second 568 release seems to be fixed now, but I havnt actually installed it yet. It was put up about a week or so ago
My S10 arrived last week and it's also on 546, that seems to be the only shipped 3.1 rom.
The OP will be updated with the new link, but you can still get the same from using 'check for updates' from within the settings.
Be aware that 3.2 cant be rooted yet, I plan on porting CWM over some time next week, assuming there's no issues in doing it.
Click to expand...
Click to collapse
Do you have the link for this re-released version?
MR2 is the new one, confusingly it seems to just be the original 568 pkg repackaged or something really minor change-wise. I installed 586MR2 but it's still the same build number but the pkgs are definitely different
Problem updating
Can anyone guide me in updating the package file? Sorry I am a new bee.
Is there any other thread with step by step procedure?
Thanks in Advance.
Android version 6.0.1 bootloader and radio files updated January 7, 2016
Hello all.
I created a few flashable ZIP files which will install the radio and bootloader images from Android 5.0.x, 5.1.x or 6.0.x depending on your choice.
To install the Android 6.0.1 radio (M8974A-2.0.50.2.28) and bootloader (HHZ12k), flash the following ZIP in recovery:
The file is N5_AndroidM_6.0.x-MMB29S_Radio+Bootloader.zip, MD5 9fef18abade89f85fe13b37320b740bd, size 22.7MB.
You can download it here: https://www.androidfilehost.com/?fid=24352994023708028
---
To install the Android 5.1.1 radio (M8974A-2.0.50.2.26) and bootloader (HHZ12h), flash the following ZIP in recovery:
The file is N5_AndroidL_5.1.x-LMY48M_Radio+Bootloader.zip, MD5 c90de28bf48e9461a13c6617c9d792ce, size 22.7MB.
You can download it here: https://www.androidfilehost.com/?fid=24052804347812405
---
To install the latest Android 5.0.x radio (M8974A-2.0.50.2.22) and bootloader (HHZ12d), flash this ZIP in recovery:
The file is N5_AndroidL_5.0.x-LRX22C_Radio+Bootloader.zip, MD5 4c9861bfe068d232340e961aa7726767, size 22.6MB.
You can download it here: https://www.androidfilehost.com/?fid=24052804347812506
Hope this helps!
Thanks
Separate radio frm the zip
Thanks for this.
I already have the updated radio. Could you please split the zip in two, with the updated bootloader separate from the radio.
FunDionysus said:
Thanks for this.
I already have the updated radio. Could you please split the zip in two, with the updated bootloader separate from the radio.
Click to expand...
Click to collapse
I suppose I can, though it doesn't change anything to flash the same radio version on top of itself, so you could just flash the whole thing to update the bootloader. The only reason there would be to split it up would be if you wanted to keep a different radio version than the one in the zip.
Are these updated files? Google factory images are at LRX21O but I've seen threads here that have LRX21V in the name, suggesting there's an update of some kind but I'm unable to find any info regarding this with my searches lol.
I'm just trying to update my wife's nexus 5 with factory files (no custom ROM's) as she just wants her phone to work and not have any instability unlike what I do with my phone haha.
She's had it say no network sometimes, I wonder if Google released this update to the radio to address a bug? Or where did you get these files from? Just wondering
ek69 said:
Are these updated files? Google factory images are at LRX21O but I've seen threads here that have LRX21V in the name, suggesting there's an update of some kind but I'm unable to find any info regarding this with my searches lol.
I'm just trying to update my wife's nexus 5 with factory files (no custom ROM's) as she just wants her phone to work and not have any instability unlike what I do with my phone haha.
She's had it say no network sometimes, I wonder if Google released this update to the radio to address a bug? Or where did you get these files from? Just wondering
Click to expand...
Click to collapse
The bootloader and radio has been the same through all the revisions of Lollipop.
Wakamatsu said:
The bootloader and radio has been the same through all the revisions of Lollipop.
Click to expand...
Click to collapse
So these files are from the Google factory images then?
Do you have a link to get the latest revision of lollipop? I wonder if LRX21O isn't the latest anymore lol
ek69 said:
So these files are from the Google factory images then?
Do you have a link to get the latest revision of lollipop? I wonder if LRX21O isn't the latest anymore lol
Click to expand...
Click to collapse
Yes, these are from the Google factory images. Specifically, the factory images for the Nexus 5. You can see all of the released Nexus factory images here. As you can see, LRX21O is still the latest version released for the Nexus 5. It seems as though other devices have had images released with "higher" letters, for instance LRX21V is the build number for the latest Nexus Player factory image. My guess is that Google makes device-specific changes to Android and then updates only those devices that would benefit, though I have nothing to back that up.
In any case, the radio and bootloader have been the same versions throughout all builds of Android 5.0 for the Nexus 5 so far, and the latest of those builds is LRX21O. This ZIP does contain the latest and greatest that we have officially available at the moment. I'll do my best to keep it updated should that ever change.
iammuze said:
YIn any case, the radio and bootloader have been the same versions throughout all builds of Android 5.0 for the Nexus 5 so far, and the latest of those builds is LRX21O. This ZIP does contain the latest and greatest that we have officially available at the moment. I'll do my best to keep it updated should that ever change.
Click to expand...
Click to collapse
Thanks for this info. When I installed the bigxie stock Lollipop flashable ROM, the OP included a link to the updated radio. But the bootloader was not updated to the latest.
http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
So if the latest bootloader is available as a separate flashable zip that would be best. However I've yet to find a link for such.
No problem!
FunDionysus said:
So if the latest bootloader is available as a separate flashable zip that would be best. However I've yet to find a link for such.
Click to expand...
Click to collapse
Well like i said a couple posts above there's no harm in flashing the same version radio on top of itself, so even if all you want is to update the bootloader (and as long as ths radio in the ZIP is the same version you want to keep), this will work just fine.
Maybe a stupid question but I prefer to be on the safe side.... If I flash this file on my device (Nexus 5 of course) actually rooted with custom KK rom and TWRP. Will this wipe the data in the SD card (flashing a new bootloader) or is it safe ?
Thanks
pierrep56 said:
Maybe a stupid question but I prefer to be on the safe side.... If I flash this file on my device (Nexus 5 of course) actually rooted with custom KK rom and TWRP. Will this wipe the data in the SD card (flashing a new bootloader) or is it safe ?
Thanks
Click to expand...
Click to collapse
Nope! No wiping, perfectly safe.
Thx for all your help and clarifying things
I was just wondering why some threads in the nexus 5 section were referencing LRX21V in the titles cuz like u said LRX21O is the latest out by Google for nexus 5
Simply and easy to upgrade the bootloader. Thanks!
Thanks ! :good:
If we flashed the lollipop factory image I assume we have the latest bootloader?
Thank you for this file! I was already running the latest radio but I needed the boot loader update!
Why does everyone care about latest bootloader update so much?
Just wondering
Sent From Bacon
ek69 said:
Why does everyone care about latest bootloader update so much?
Click to expand...
Click to collapse
For myself just wanting to learn the diff.
Can locate no documentation or changelog.
The Android 5.0 LRX21O - Stock/Flashable ROM I installed did not install the updated bootloader, which I believe came out for the Lollipop Preview back in October,
Just to make sure I don't have to fix anything after I do this process.
If I flashed Cataclysm ROM for Android 5.0, I need to install this correct?
My Nexus 6 received 7.0 update notification and I would like to wait for 7.1 to upgrade together. But yesterday the 7.0 notification suddenly gone, I've manually check the update but the system said my phone already get the latest update. Then I've checked the version of my Nexus 6, it is MOB31H, I don't remember whether I have the November update. Now I have few questions and hope someone can help me.
1. Why the 7.0 update notification suddenly gone?
2. I've checked the Full OTA images, the Nov update contains MMB31C and MOB31K, If I would like to manually apply the update, which one should I use? (My Nexus 6 is international version XT1103)
3. If i manually apply the the Full OTA Images on Nov update by adb sideload, will all the data being erased and need to re-config and reinstall all apps?
Thanks so much in advance for your help.
1. Unknown
2. Your device model doesn't matter as the OTA zips work on both, but based on the model number you gave, you have a US device. The international unit is XT1100. Use the version with the code ending in "K" if wanting Android 6.x. Android 7.x uses codes starting with "N".
3. Flashing an OTA zip will not cause loss of data.
Strephon Alkhalikoi said:
1. Unknown
2. Your device model doesn't matter as the OTA zips work on both, but based on the model number you gave, you have a US device. The international unit is XT1100. Use the version with the code ending in "K" if wanting Android 6.x. Android 7.x uses codes starting with "N".
3. Flashing an OTA zip will not cause loss of data.
Click to expand...
Click to collapse
Thanks so much for your help, I think I mis-type the model, XT1100 international should be correct.
I've just sideloaded the version MOB31K successfully and will wait for the 7.1 fix on the speaker phone echo problem before upgrade to 7.1.
Please don't mind to ask one more question, i guess the MMB31C and MOB31K is for US and International model respectively. On version Nougat, no different on XT1103 and XT1100, one version for both model?
Thanks so much again for your help.
Or you could sideload NBD91X, which is Nougat without the speakerphone problem.
@mega23mac: MMB31C is for CDMA devices in the US, if I recall correctly. As @dahawthorne points out, you could install a 7.0 OTA, but if you don't need the speakerphone, the 7.1 OTA works just fine. Google should have it patched for next month's security update.
On firmware finder is a new EMUI update available, check:
https://pro-teammt.ru/en/online-firmware-database-ru/?firmware_model=WAS-&firmware_page=0
It's available for many variations of the device, however not for was-lx1a c432, which is the device I have at hand atm...
Of course Huawei support doesn't know anything!
Has someone with a fitting variation of the p10 lite received the update already by normal OTA?
I could flash another cust (c55) via HWOTA and everything was fine, except it showed the build as 8.0.0.46 (1HAM) instead of 8.0.0.393...
Hence I reverted via HiSuite to Nougat and updated all the way to 8.0.0.390 from 2019, where it stops for lx1a with cust c432 - which surprises me as I thought that the free EU version (dual/4GB) certainly had it's own build up and running, however no, doesn't look like it...
It should be possible to manually flash the updated partitions via fastboot individually or again use HWOTA again and ignore the wrong build number as THIS most likely will be the very last update for this 3+ years old device anyway.!
Not sure if anyone is still listening here anymore, didn't see any recent conversations here in 4 to 6 weeks I'm playing with this device :cyclops: which is of course kinda normal for aged phones like this one
Edit:
As suggested in this thread:
https://forum.xda-developers.com/p10-lite/development/service-rom-b362-c432-upgrade-o-o-n-o-t3813946
My lx1a is in fact a l21a (c432) and firmware is already available, I'll check it out now, however it's still weird as firmware finder usually suggests the right firmware by searching for lx1a, never before I had to look up l21a...
Gonna report about success later on!
Edit2: when initializing the update via dailer it says the update is incompatibile, even though I setup the dload folder according to the guidelines (zip not update.app) and have the correct package L21A_EU - never gonna understand the way Huawei thinks with this...
Forced update doesn't work for same incompatibility reasons!
Edit3: just tried using update.app files instead of zips but no chance, still errors out.
Also tried firmware finder erecovery DNS method but this gives me a "none authorized update", like using the l21a package on the lx1a isn't supposed to work... I'm running out of ideas!
Last Edit:
Nothing worked so I unlocked the Bootloader to use HWOTA8 to update to package (full) L21AC432B394 and it perfectly worked...
Now finally I'm on 8.0.0.394 c432 with July 2020 security patch and little added functionality, kernel was compiled on 15th of July 2020 - 3+ years and a update has been released, that's actually a big surprise considering it's Huawei and a low level device!
Greetings Sam
what do you think of this update? battery life improved with this new kernel? or nothing has changed?
roxkiller said:
what do you think of this update? battery life improved with this new kernel? or nothing has changed?
Click to expand...
Click to collapse
It didn't change anything obvious, same UI, same experience - Huawei today (assistant app) was added, however no one is forced to use it BUT the most important feature in this update for me is the the 1+ year of security patches, remember it's March 19 to July 20 - I mean it's still Oreo but at least up to date on a security level, system, vendor, kernel, pretty much all parts where updated and improved, it even feels little faster but this could also be because of the factory reset I did to flash the update (unlocked and locked the device in order to use HWOTA8)...
If you want details install firmware finder, search for WAS-L and check out the changelog of 8.0.0.394, maybe the link above provides a changelog, don't remember... There is a pretty long changelog, technically this is not only a security update but a functionality update, I just don't remember all aspects of it!
I'm looking for a good source of firmwares, i know the famous sites but some firmwares doesn't seem to be listed. I know in the time os Samsung KIES there were tools which communicated directly with samsung.
For example these firmware builds for the SM-G975Ux aren't listed on most firmware sites but have the December secutiry update with binary/bootloader version 8: G975USQS8IVL1 and G975USQS8IVL2
All the big sites have ROMs for that phone (same one I have). There is no "Ux" model... it's *U or *U1, with the latter being unlocked. IF you search for U1 ROMs you have many selections, but most get the XAA version which will usually change carriers automatically based on the SIM card.
The latest BL=8 version I see there is https://www.sammobile.com/samsung/g...M-G975U1/XAA/download/G975U1UEU8IWB6/1741280/ which is the February 2023 security update. I believe this is the last one we are getting (but I could be mistaken as there may be 1 more security patch, I don't remember).
There's U U1 0 W F N .... I'm looking for the oldest firmware with binary version 8, but it seems the sites don't show all firmwares available.... i'm looking for the oldest firmware with U8 bootloader (or any compatible bootloader with binary 8 version), i could have a look at all sites and try my luck... but they don't seem to have all data. but like i said i prefer some original source xml files... i saw some url's to original samsung servers but can't find them anymore.
There is already a firmware available with the march update.... but you have to be lucky to find them... i'm looking for original sources. like update.zip's and such
Found the first one....
https://fota-cloud-dn.ospserver.net/firmware/TMB/SM-G975U/version.xml
I'd recommend around sammobile and samfw. These are the two sources I use the most
hey!
after I wanted to update my g973f from "G973FXXUGHVK1" to "G973FXXSGHWC2" (I tried odin 3.13 and odin 3.14) and an error occurred, I can't install anything anymore... recovery and download mode work, and I can also flash the original firmware, but the device no longer boots into the system! even custom roms don't want to boot anymore
Can anybody help me further?
Ben1987 said:
hey!
after I wanted to update my g973f from "G973FXXUGHVK1" to "G973FXXSGHWC2" (I tried odin 3.13 and odin 3.14) and an error occurred, I can't install anything anymore... recovery and download mode work, and I can also flash the original firmware, but the device no longer boots into the system! even custom roms don't want to boot anymore
Can anybody help me further?
Click to expand...
Click to collapse
Do you mind explaining a bit more? Do you mean like that it boots you into recovery only or?
WooBLOATERRRR said:
Do you mind explaining a bit more? Do you mean like that it boots you into recovery only or?
Click to expand...
Click to collapse
if i flash a new rom (whether original or custom rom) nothing happens after the reboot... download mode works too, flashing twrp works too! however, the system boot does not work via twrp either... not even a bootloop, the cell phone does not react at all! the task combination for
Right now I don't even care if I get the original firmware or a custom rom running... I hope I didn't brick it (((
My old device was a G930F, its unbreakable make sure you flash the right rom and wipe data and dalvik cache after flashing.... THis ons is locked so it doesn't have fastboot. My G-930F came with fastboot enabled so you can always fastboot a recovery.img. like TWRP
Did you try to download TWRP from twrp.me and "fastboot boot twrp-3.7.0_9-0-herolte.img" ? it should boot to twrp in fastboot mode (hold volume down + home + power).
Ben1987 said:
if i flash a new rom (whether original or custom rom) nothing happens after the reboot... download mode works too, flashing twrp works too! however, the system boot does not work via twrp either... not even a bootloop, the cell phone does not react at all! the task combination for
Click to expand...
Click to collapse
1. is your KG status is broken?
2. Is your bootloader unlocked?
You know how to flash lineageos through twrp right? and how to use odin?
Maybe flash lineageos to see if everything works.... and then revert to original software. Be sure to wipe cache/dalvik and userdata
DaanNL said:
There's U U1 0 W F N .... I'm looking for the oldest firmware with binary version 8, but it seems the sites don't show all firmwares available.... i'm looking for the oldest firmware with U8 bootloader (or any compatible bootloader with binary 8 version), i could have a look at all sites and try my luck... but they don't seem to have all data. but like i said i prefer some original source xml files... i saw some url's to original samsung servers but can't find them anymore.
There is already a firmware available with the march update.... but you have to be lucky to find them... i'm looking for original sources. like update.zip's and such
Found the first one....
https://fota-cloud-dn.ospserver.net/firmware/TMB/SM-G975U/version.xml
Click to expand...
Click to collapse
Yes, I know there are many other variant firmwares out there, but for a U phone (snapdragon) there is really only U and U1... the rest are incompatible.
There is no "older" firmware with binary 8, because the firmwares are packaged with the proper/compatible binary already. Basically, the "binary" is the bootloader version. On Snapdragon phones, you must have the proper BL/binary to flash, as you already know. You can't interchange the binary/BL with the ROM and security updates because they are not made that way.
The update.zip you're looking for are updates sent by Samsung directly, and they can update the ROM (and Binary) from one stock version to another... but, again, they will update both the binary/BL as well as the ROM, so they can't be broken up to only do one or the other.
It sounds like you're trying to get to an older ROM version (for whatever reason) with an older security patch level as well? Basically, this cannot be done on Snapdragon phones. Once you're on an updated binary/BL, you're stuck there (at least today you are).
WooBLOATERRRR said:
I solved the problem! I had unlocked the bootloader, but I also had to deactivate verity via CMD with twrp+adb "adb disable-verity"
ok i've solved the problem now, but does anyone know why i couldn't even start the original stock roms? Actually, the stock ROM should set everything to factory settings...
Click to expand...
Click to collapse
WooBLOATERRRR said:
1. is your KG status is broken?
2. Is your bootloader unlocked?
Click to expand...
Click to collapse
Thank you for helping so quickly with ideas... I would not have expected such quick help with such an old model, even samsung customer service didn't want to help me yesterday
Ben1987 said:
Thank you for helping so quickly with ideas... I would not have expected such quick help with such an old model, even samsung customer service didn't want to help me yesterday
Click to expand...
Click to collapse
Samsung/apple support in a nutshell
schwinn8 said:
Yes, I know there are many other variant firmwares out there, but for a U phone (snapdragon) there is really only U and U1... the rest are incompatible.
There is no "older" firmware with binary 8, because the firmwares are packaged with the proper/compatible binary already. Basically, the "binary" is the bootloader version. On Snapdragon phones, you must have the proper BL/binary to flash, as you already know. You can't interchange the binary/BL with the ROM and security updates because they are not made that way.
The update.zip you're looking for are updates sent by Samsung directly, and they can update the ROM (and Binary) from one stock version to another... but, again, they will update both the binary/BL as well as the ROM, so they can't be broken up to only do one or the other.
It sounds like you're trying to get to an older ROM version (for whatever reason) with an older security patch level as well? Basically, this cannot be done on Snapdragon phones. Once you're on an updated binary/BL, you're stuck there (at least today you are).
Click to expand...
Click to collapse
I've tried different firmwares, its all about snapdragon. You can also flash SM-G975W parts and other snapdragon variants.... there's a lot of variants out there.
I first upgraded and then downgraded to the parts i wanted and am on a rom now with security patch level December 2022, as long as the binary version is the same there's no problem. I've got the latest modem installed and the oldest firmare and bootloader for the latest binary version, i can upgrade or downgrade my bootloader. I already asked someone before if this was possible and if he could confirm because before i was only able to flash CSC and AP i think.
If there's no updates comming anymore why not downgrade and wait for a new leak
I'm also sure we can unlock the bootloader, i'm trying to make an lposed module. I've installed lspatch and lposed and they work fine for some modules. The bootloader unlock has several prerequisites (properties and such) if i can make it look for other properties or something like that we might get an unlock option. Also it looks for an encrypted file on EFS, if someone with an unlocked samsung phone could copy that file we would be a lot further.
It's called /efs/sec_efs/sktdm_mem/encmembership.txt and should be an encrypted file, also if anyone knows how to set ro properties without root (like a stub before the preference controller starts) this would be very usefull.