THE OFFICIAL BASEBAND
FIRMWARE MODEM UPDATES
Verizon Samsung Galaxy S5
{SM-G900V/KLTEVZW}
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
{The above image is a refrence of all the Stock Firmware, Release Dates, etc...}
CLICK HERE TO EXPANDED THE ABOVE IMAGE
***INFORMATION REGARDING***
***NEW/REWORKED UPDATES***
The Modem packages were recently reworked to include the "much needed" Baseband files (of course) pulled from the Official Samsung Stock Firmware.
This is ONLY because the following list of files are ALL of the Baseband/Modem files that are actually the part of the Firmware that controls ALL the radio devices within the GS5 to include (but, not limited to) the GPS, WiFi, Bluetooth, NFC, Cellular Data/Voice, etc...
MODEM.BIN
NON-HLOS.BIN
RPM.MBN
SBL1.MBN
SDI.MBN
TZ.MBN
Please keep in mind that, because these functions are Highly Regulated & Certified, they are actually Separate from the Android Operating System (aka the Firmware ROM installed like AOSP, LineageOS, etc...).
This is the reason that, after flashing the "Baseband Firmware Modem Update", it DOESN'T DIRECTLY AFFECT the Android Firmware installed on your devide. Your Android Firmware (basically) takes note of the update and updates itself to reflect those said changes (simply put without getting too deep).
DISCLAIMER/FYI
- Any process (like updating your modem) via Odin and/or Custom Recovery is simple/easy to do but, as always, if your not sure of what your doing and don't do your research (ie... searching, asking questions, etc... FIRST), then you take the risk of damaging your device.
- I take no responsibility for any unexpected results or damage that may happen but, we are always willing to provide assistance to help you out.
- Also keep in mind that when performing any unconventional updates, unlocking, rooting, etc... you may end up "voiding your warranty"!
INSTRUCTIONS
1. If not already done, be sure your PC/LPTP has the latest "Samsung USB Driver for Mobile Phones" installed.
2. Download the ".tar.md5" Baseband Firmware Modem file you need from any of the Download Links provided (below).
3. Power off your device and then enter Download Mode (aka Odin Mode) by using the required key combination ("Home" & "Volume Down" then "Power").
4. Connect the USB cable to the Device and PC.
5. Open Odin and select the PDA/AP and choose the ".tar.md5" Modem file you downloaded.
{Please Note: It's typically reccomended to use Odin v3.07-v3.12 but, other versions may also work.
6. In Odin, please be sure not to make any additional selections than the default that was already selected when you opened Odin.
7. Select the Odin "Start" button at the bottom & be patient for the process to complete and Odin should reflect a Green "PASS" when completed (The device will reboot automatically when done).
PRIMARY DOWNLOAD LINK
(NEW UPLOADS BEING WORKED ON. PLEASE USE)
(THE BELOW ALTERNATIVE DOWNLOAD LINK)
Baseband Firmware Modem Updates {Odin Flashable} - XDA DevDB Downloads
ALTERNATIVE DOWNLOAD LINK
Baseband Firmware Modem Updates {Odin Flashable} - Android File Host
PLEASE NOTE: It has been decided not to pursue the Recovery Flashable (aka TWRP, CWM, etc...) Modem Updates at the present time. We apologize for the inconvenience...
Special Mentions/Credits
Samsung - For the Device.
Sammobile - For the Software/Firmware.
The XDA fAMILY - For Valuable Member Feedback.
Let's not forget - To All The Girls We've Loved Before... (LOL!)
Click Here If You Would Like To Donate To My Developements
~{Donations Are Appreciated, but Never Necessary...}~
PLEASE NO MIRRORS!
.
XDA:DevDB Information
[BASEBAND-FIRMWARE-MODEMS]Verizon Samsung Galaxy S5 {SM-G900V/KLTEVZW}[ODIN], Tool/Utility for the Verizon Samsung Galaxy S5
Contributors
Ibuprophen, klabit87
Version Information
Status: Stable
Current Stable Version: G900VVRU2DQL1
Stable Release Date: 2018-01-17
Created 2019-05-02
Last Updated 2019-06-20
Reserved
Reserved
Can i flash them on KK?
What are the differences between them ?
thanks
HazeMC said:
Can i flash them on KK?
What are the differences between them ?
thanks
Click to expand...
Click to collapse
I don't see why not. I know we can on the Verizon S4. @Stupifier may be able to tell you for sure though.
These are all modems from the lollipop releases.
Zips are ss and ff flashable.
And some people prefer Odin so I posted those too.
Thank you for this.
Anyone have the OG5 and OK3 modems? This thread would be the perfect place to add them.
painiac said:
Thank you for this.
Anyone have the OG5 and OK3 modems? This thread would be the perfect place to add them.
Click to expand...
Click to collapse
I will add them tonight. Sorry I lost track of things.
klabit87 said:
I will add them tonight. Sorry I lost track of things.
Click to expand...
Click to collapse
Nothing to apologize for!
painiac said:
Nothing to apologize for!
Click to expand...
Click to collapse
Safestrap flashables are added for OG5 and OK3.
klabit87 said:
Safestrap flashables are added for OG5 and OK3.
Click to expand...
Click to collapse
Very much appreciated!
I have G900V but I'm outside US and my provider does not suport lte band 4, 13.
Can you flash G900F moden on G900V? Would that give my phone access to diferent lte band?
Thanks.
Looking for the PB1 modem for CM13
Nandr0idC0nsumer said:
Looking for the PB1 modem for CM13
Click to expand...
Click to collapse
this one?
https://www.androidfilehost.com/?fid=24459283995308895
Actually this one caused me bootloops. not sure if it works. had to flash back to NCG
thaijunk said:
this one?
https://www.androidfilehost.com/?fid=24459283995308895
Actually this one caused me bootloops. not sure if it works. had to flash back to NCG
Click to expand...
Click to collapse
Thanks. I flashed the full stock PB1 tar to get it (big mistake) and went through hell and back to unlock the bootloader and go back to CM xD
I was wondering if there is a PF4 modem zip file for our phones?
Sorry everybody. PB1, PD1, and PF4 have been added.
If you need/prefer odin tar files let me know.
i dont feel anybody uses them based on the downloads of previous tar files.
I flashed the modem but never changed
Sent from my SM-G900V using XDA-Developers mobile app
ozz200127 said:
I flashed the modem but never changed
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
That does not tell me much.
Did you use FlashFire? Safestrap? or TWRP?
As far as I know they have only been flashed with SafeStrap.
I have not had the chance to test with TWRP.
I can upload others that will work for TWRP if that is the issue.
Might be a day or 2 but I will.
I use twrp...the flash went through but it didn't change
Sent from my SM-G900V using XDA-Developers mobile app
ozz200127 said:
I use twrp...the flash went through but it didn't change
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
ok. I will update them for twrp in the next day or 2.
Sorry. these were started before the bl unlock exploit was developed.
and I never thought to test it myself until you brought it to my attention.
Related
No, I do not have a full I535VRUCML1 firmware package for you.
Yes, I somewhat lied in the title of this thread. But I did it for a good reason: to get your attention.
Mods - I'm sure you'll understand.
You should NOT flash the I535VRUCML1 firmware (or any subsequent releases for that matter). You will brick. This is what vzw/samsung did on the first OTA for the Galaxy S4. They changed the keys they sign the firmware with. This prevents us from 'mis-matching' our firmware like we've been doing all along. We've been leaving aboot (VRUAME6, the african-canadian sock-monkey leaked bootloader) alone and updating everything else. Since they're signing with different keys now, doing this will brick your device. If you update the ENTIRE bootchain (including aboot) you shouldn't brick, but will be stuck with a locked bootloader and any attempt to downgrade (via dd, etc) will brick you as well. Even if you manage to flash an ENTIRE old bootchain over VRUCML1, you'll brick because they trip a qfuse that prevents it from working. More info about qfuse by djrbliss here: http://t.co/myb0LIrN6e
Just stick with VRUBMF1, trust me.
These firmware updates have, up until now, consisted of several partitions that we update:
- tz (trustzone)
- rpm (resource/power management)
- sbl[1,2,3] (secure bootloaders)
- NON-HLOS (modem/baseband)
Due to the way Samsung and Verizon have chosen to proceed with future updates (following what they do for the Galaxy S4) we cannot flash all these partitions anymore (see above) and retain our unlocked bootloader. We CAN, however, update the baseband as it's not signed.
Latest firmware: NE1 modem with MF1 firmware: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip (md5sum: 7a49bb13c1160f4d4a89488127684b5b)
This will be the final zip I make. MF1 was the last firmware that allowed us to use the old bootloader, and NE1 is likely to be the last modem we'll ever receive.
How would we measure objectively, coverage/speed differences between what we have the old and new radios?
I guess bandwidth speed test app? Anything else?
Sweet. Maybe I'll get better signal. My voice/1x reception has been worse than my old dx. I'm dropping calls left and right. I also live in the middle of BFE.
how is baseband/radio affected when we flash something else with cwm or with Odin? I mean, I have stock rooted w. b00stedv.002, but if I flash aokp or cm, will it replace this new radio with whatever one is included with them?
Slightly OT, I remember on the dx, if you wanted to sbf without the radio you did it with Linux, otherwise with moto's rsdlite.
Will this wipe data/swap us back to a stockish rom?
invisiblek said:
I've always liked having a thread dedicated to keeping links for the most updated modems for a device. Just easier to find that way.
These are packaged for flashing with Odin. Flash in the PDA section.
I will not promise anything as far as faster speeds or better coverage.
IMPORTANT:
Do not unplug while this is happening, unless you are in dire need of a paperweight.
Odin tends to seem like it hangs for a short bit toward the end of the flash. Be patient, it will finish and automatically reboot.
Latest one on top.
VRLG1 - http://goo.im/devs/invisiblek/i535/VRLG1.modem.tar.md5
This is the first OTA
VRLF2 - http://goo.im/devs/invisiblek/i535/VRLF2.modem.tar.md5
This is the original shipped modem
Click to expand...
Click to collapse
very good idea these are amaazing.. any idea if the new radio plays nicer with installs etc.. as the old one has more or less everyone with no service here and there.. or globally roaming :/
beanstown106 said:
very good idea these are amaazing.. any idea if the new radio plays nicer with installs etc.. as the old one has more or less everyone with no service here and there.. or globally roaming :/
Click to expand...
Click to collapse
no idea, i'm still rocking a stock rom
would be nice though if this fixed some of the aosp problems
MOD: please sticky this thread
invisiblek said:
no idea, i'm still rocking a stock rom
would be nice though if this fixed some of the aosp problems
MOD: please sticky this thread
Click to expand...
Click to collapse
im on cm10 after all the audio commits etc it seems like the most stable rom other than stock, beats aokp or cm9 right now imho, no data drops etc
So...This is just the new baseband right?
So should be able to flash with custom recovery/rom etc?
this is my first samsung device so not looking for a brick.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm stuck at this screen, its been doing it for about 10 min. is it ok to unplug and start over?
burkett375 said:
I'm stuck at this screen, its been doing it for about 10 min. is it ok to unplug and start over?
Click to expand...
Click to collapse
Did you verify the MD5 before flashing?
nosympathy said:
Did you verify the MD5 before flashing?
Click to expand...
Click to collapse
doesn't it get verified in odin?
burkett375 said:
doesn't it get verified in odin?
Click to expand...
Click to collapse
I don't have any idea. I have always had HTC phones which are very different.
I have built the habit to check MD5 always, regardless of what it is, just so as to not have something happen where I can't say I did everything I could to prevent it.
burkett375 said:
I'm stuck at this screen, its been doing it for about 10 min. is it ok to unplug and start over?
Click to expand...
Click to collapse
yes, if its stuck on SetupConnection unplug and replug
this goes for more than just flashing modems
invisiblek said:
yes, if its stuck on SetupConnection unplug and replug
this goes for more than just flashing modems
Click to expand...
Click to collapse
hmmm...no matter what I do, I can't get past that part
burkett375 said:
hmmm...no matter what I do, I can't get past that part
Click to expand...
Click to collapse
you have the drivers installed?
burkett375 said:
hmmm...no matter what I do, I can't get past that part
Click to expand...
Click to collapse
You are in download mode correct? I literally just flashed this first try.
invisiblek said:
you have the drivers installed?
Click to expand...
Click to collapse
yup, i'm running CM10 right now and working good.
---------- Post added at 01:20 AM ---------- Previous post was at 01:19 AM ----------
nosympathy said:
You are in download mode correct? I literally just flashed this first try.
Click to expand...
Click to collapse
Nope, didn't know it was supposed to be in download mode...i'm a dummy
Edit: all set now...Thanks!
burkett375 said:
yup, i'm running CM10 right now and working good.
---------- Post added at 01:20 AM ---------- Previous post was at 01:19 AM ----------
Nope, didn't know it was supposed to be in download mode...i'm a dummy
Edit: all set now...Thanks!
Click to expand...
Click to collapse
haha no biggie. It happens.
nosympathy said:
I don't have any idea. I have always had HTC phones which are very different.
I have built the habit to check MD5 always, regardless of what it is, just so as to not have something happen where I can't say I did everything I could to prevent it.
Click to expand...
Click to collapse
tar.md5 files have the md5 appended to the end, and I think Odin checks before flashing. Not 100% sure on that though. Checking it yourself is never a bad idea of course.
This newer modem might of improved data throughput. Not entirely sure though, seems like I'm getting faster speed on Speedtest.net but that could be entirely subjective. Thank you invisiblek as always, for your awesome work!
This is reserved for W8 only! If you have any other model, this will not work
Whats different from the other other upgrade threads? This one doesn't block you from going back to 4.3, it allows you to retain knox 0x0 and it's safe.
Just tried this, worked perfectly. I came from X-Note 7.0 and did this on my friends Note 3 and he was on stock. I already had knox 0x1 but i was alble to keep his at 0x0.
As of now, this has only been tested on W8 model as it takes the files from the Telcel firmware (mexico). You can use this method on any W8 model, the only thing you will have to change is substitute my modem (CP) by the modem from the latest 4.3 firmware of your carrier. It seems as the MD5 from all modems for all canadian carriers match exactly, so the model for rogers also applies to Bell and Telus
If you are coming from a non-canadian W8, you can extract your modem directly from stock firmware. Here is how:
This is just an example on how to extract a modem from a stock firmware:
Use winrar to:
1- extract firmware downloaded on sammobile.com or other (please use latest firmware), should output an MD5 file.
2- Rename that file from xxxxxxxxxxxxxxx.tar.md5 to xxxxxxxxxxxxxxxxx.tar
3- extract .tar firmware and locate modem.bin file
4- compress the modem.bin, it should give you a modem.zip
5- rename that modem.zip to modem.tar
6- You not have your flashable odin modem
Click to expand...
Click to collapse
Upgrading to Kit Kat and downgrading back to 4.3 does not trip knox, and rooting using my instructions either. Be sure to turn off reactivation lock before flashing this. This method gives you an easy way to official 4.4.2, once you're there, you can flash any 4.4 rom.
Also, and this is an important factor for a lot of people, this doesn't block you from going back to 4.3. If ever you want to go back to Jelly Bean 4.3, just flash back to it via ODIN
Download all the files, PIT, BL, AP. CP and CSC, the flash via ODIN 3.09. Then flash CF-Root and CWM if you wish. I did not check re-partition in ODIN, it worked for both of my Notes, most users didn't check it either, but a small few said the flash failed until they checked re-partition, either way, it should not brick your device.
Here are the links to the files:
PIT: http://pc.cd/K7H (MD5: e2dba603c963443660b369e04b07d574)
BL: http://pc.cd/gXH (MD5: 1bce2f5a137901e2fb206379d3e7ae11)
AP: http://pc.cd/7kH (MD5: 08443eb20702a975fc0be85f7e9c439d)
CSC (this one is for Canada only, if you have any other carrier please download yours): http://www.mediafire.com/download/xn11kh614eag7ir/Canadian+Multi+CSC.tar
(MD5: beae61ca1628b303657c40e14cac3fb6)
CP: http://www.mediafire.com/download/1oias85eoz8ykuh/Rogers+Modem+(CP).tar (MD5: 45522799eb027108fa1c493cbd83abf5)
ODIN: http://uploaded.net/file/hwtdrpll
CF-Root: http://download.chainfire.eu/352/CF-Root1/CF-Auto-Root-hlte-hltexx-smn9005.zip?retrieve_file=1 Don't use included ODIN in CF-Root, use 3.09 and flash via AP
CWM: http://d-h.st/gb3 (MD5: 31e4a86b58837ba87bfa1bf2073371db)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enjoy!
Thanks to Oogar for a more complete version of this process. This method does break WiFi and NFC so head over to his thread for the patch and a proper thanks
I can confirm after testing this a few times on the N9005 that it is only working on the N900w8.
radicalisto said:
I can confirm after testing this a few times on the N9005 that it is only working on the N900w8.
Click to expand...
Click to collapse
That's too bad, but at least there are other ways for you guys!
There will be a way around it I think, especially as the w8 can do it. Shows it's possible somehow
radicalisto said:
There will be a way around it I think, especially as the w8 can do it. Shows it's possible somehow
Click to expand...
Click to collapse
is there any official 9005 firmware? I saw today that besides poland, russia also got the firmware which is exynos based, also deployment in eastern europe is under way, can't we apply this method to the 9005?
Only the .pl firmware currently, status on sammobile shows AFG (Afghanistan) region is pending apparently, so I expect a wide roll out any time soon.
radicalisto said:
Only the .pl firmware currently, status on sammobile shows AFG (Afghanistan) region is pending apparently, so I expect a wide roll out any time soon.
Click to expand...
Click to collapse
in that case, can we apply this method and substitute the mexican files for the polish ones? It seems technically possible
polish_pat said:
Whats different from the other other upgrade threads? This one doesn't block you from going back to 4.3 and it's safe.
Just tried this, worked perfectly. I came from X-Note 7.0 and did this on my friends Note 3 and he was on stock.
As of now, this has only been tested on W8 model as it takes the files from the Telcel firmware (mexico). You can use this method on any W8 model, the only thing you will have to change is substitute my modem (CP) by the modem from the latest 4.3 firmware of your carrier. You can take the official tar file and extract the modem.bin and re-zip it back to a tar file and use that.
This does not trip knox, be sure to turn off reactivation lock before flashing this. This method gives you an easy way to official 4.4.2, once you're there, you can flash any 4.4 rom.
Also, and this is an important factor for a lot of people, this doesn't block you from going back to 4.3. If ever you want to go back to Jelly Bean 4.3, just flash back to it via ODIN
Enjoy!
Click to expand...
Click to collapse
Rogers user here. Stock. To clarify.
Can I flash these files and well be in 4.4.2? Without tripping Knox? And can go back to 4.3?
Will this reset my phone?or will my data and apps still be intact?
Sent from my SM-N900W8 using Tapatalk
Canadoc said:
Rogers user here. Stock. To clarify.
Can I flash these files and well be in 4.4.2? Without tripping Knox? And can go back to 4.3?
Will this reset my phone?or will my data and apps still be intact?
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
I hope you,re kidding for this "Can I flash these files and well be in 4.4.2? Without tripping Knox? And can go back to 4.3?" If you were not able to confirm this information while reading the OP, i'm not sure anything else but a drawing will help you. No offence
And as for your last question, yes, your phone will be wiped clean
Well I was under impression that flagging would upgrade the bootloader from which you couldn't go back.
Also wanted to be sure the included files were good for Rogers without me needing to separately including my own modem
Sent from my SM-N900W8 using Tapatalk
Canadoc said:
Well I was under impression that flagging would upgrade the bootloader from which you couldn't go back.
Also wanted to be sure the included files were good for Rogers without me needing to separately including my own modem
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
Yes, you're good to go! Enjoy
EDIT: also for anybody wondering, i was able to revert back to 4.3, i actually screwed up the rooting process, i used the ODIN included in zip from chainfires site instead of ODIN 3.09 and it gave me bootloop, so i tried to revert back to 4.3 using ODIN 3.09 and it worked. I'm going back to kitkat now
Do you cause a wipe? Cause I am not ripped so have no backup. Unless you know how to root and preserve knox
Sent from my LG-V500 using Tapatalk
Canadoc said:
Do you cause a wipe? Cause I am not ripped so have no backup. Unless you know how to root and preserve knox
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
I'm not sure i understand what you want, i dont know what causing wipe or being ripped means unless you're talking about muscular mass, but i can tell you there is no way of doing this process, or any other and not wiping the device.
polish_pat said:
in that case, can we apply this method and substitute the mexican files for the polish ones? It seems technically possible
Click to expand...
Click to collapse
I tried, but it just bootlooped for me. Was slightly afraid to force the BL incase I hard bricked it. However I may try again today at some point.
Normally flashing am update leaves your data intact. All I am asking is whether fleshing this will effectively factory reset my phone.
If so,,if I root before and don't trip knox, will I be able to flash this with mobile Odin and preserve root with tripping knox.
Sent from my LG-V500 using Tapatalk
Canadoc said:
Normally flashing am update leaves your data intact. All I am asking is whether fleshing this will effectively factory reset my phone.
If so,,if I root before and don't trip knox, will I be able to flash this with mobile Odin and preserve root with tripping knox.
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
This wipes your phone, call ir how you want, factory reset, format, restore, your data, root and everything else is GONE
polish_pat said:
in that case, can we apply this method and substitute the mexican files for the polish ones? It seems technically possible
Click to expand...
Click to collapse
OK so... I just done this again and whatever I done this time around must have differed from last time Because I just Hard Bricked big style :silly: - My advice is no one try this on N9005 -- Now for the fun of restoring life to my device or playing the dopey card with my retailer! :good:
And fixed. no defeating me!!
Sent from my SM-N9005 using XDA Premium 4 mobile app
radicalisto said:
OK so... I just done this again and whatever I done this time around must have differed from last time Because I just Hard Bricked big style :silly: - My advice is no one try this on N9005 -- Now for the fun of restoring life to my device or playing the dopey card with my retailer! :good:
Click to expand...
Click to collapse
radicalisto said:
And fixed. no defeating me!!
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How did you unbrick a hard brick?
The SDcard image method?
I was under the impression that that one doesn't work on the N9005
radicalisto said:
And fixed. no defeating me!!
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I doubt you were hard bricked if you got out of it that easily. There are two experiences devs that hard bricked their phone, by hard brick, i mean no power or screen whatsoever, no download mode or recovery, NOTHING. They tried a few methods (micro SD and motherboard shortcut method) and both ended up servicing their phone by samsung.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello guys, with this guide you can restore Stock Firmware Images for all Galaxy Tab 4 Series.
This is useful to restore firmware in case something goes wrong, if you flash a custom ROM and it fails, or, for example, if Samsung decides to update this devices to Lollipop. For this you also will need stock untouched firmware.
Pre-requisites:
1) Make a backup of everything you consider important: Apps, photos, music, etc.
2) Download drivers for your specific device from HERE, install the drivers and reboot your PC to apply changes.
3) Download Odin 3.0.9, it is attached below in this post, and extract it.
4) Download the firmware image for your specific device from HERE and extraxt the file inside, it should be a huge 1GB+ size *.tar.md5 file.
5) Make sure your device's battery is at 60% or more.
6) Enable USB Debugging on Settings > General > Developer Options (If you can't find Developer Options menu, go to Settings > General > About Device and tap several times on Build Number, then it will tell you Dev Options is enabled).
Lets start:
1) Run Odin 3.09 as Administrator (in Windows right click on Odin icon and select "Run as Administrator")
2) Turn off your tablet and now turn it on in Download Mode (press Home + Volume Down + Power buttons at the same time until the tablet turns on, then when prompted, press Volume Up button to proceed)
3) Now connect your tablet to PC via USB cable. Odin should show a plugged device and an ADDED! message, like this:
If you can't get Odin to recognise your device, check which drivers you installed or try another USB cable.
4) Make sure that Auto Reboot and F. Reset Time options are selected, like this:
5) Now check the AP option and press the AP button to find and select the firmware image (the *.tar.md5 file you extracted earlier), when you select the image, Odin will check if it has errors. If everything is OK, it should say it succesfully checked it, like this:
6) You are ready to rock, so, hit the START button and wait...
7) Go, watch TV, chat with friends, make a sandwich or play Chess with your cat.
8) Once completed, you will see the Pass! message in ID:COM section, with a green background. Your tablet should auto reboot automatically.
9) Unplug your tablet.
10) Enjoy all the bloatware once again!
Thanks for reading and if you have doubts, let us know in the comments.
Cheers!!!
Thank You!
Thanks Man! Custom ROMS are fun but it sucks when something is not working right that which was working perfectly in the Stock ROM. Will wait patiently. hope Lollipop comes to SM-T230NU soon
Joelsmarias said:
Thanks Man! Custom ROMS are fun but it sucks when something is not working right that which was working perfectly in the Stock ROM. Will wait patiently. hope Lollipop comes to SM-T230NU soon
Click to expand...
Click to collapse
it come in 6 months (might come tomorrow, after month any time), i promise
Any faster links?
sportscrazed2 said:
Any faster links?
Click to expand...
Click to collapse
Yes, here
Or here if you've got a 7.0
I cannot for the life of me get my tab to stay in download mode while flashing. It makes it as far as a quarter though the system partition then it just reboots back to the "firmware encountered an issue" screen. As far as I know the battery has more than enough if not a full charge!! HEEEEEEELP!!!!
thelous said:
it come in 6 months (might come tomorrow, after month any time), i promise
Click to expand...
Click to collapse
"You promise" and where did you get this information from?
Deejaydark said:
"You promise" and where did you get this information from?
Click to expand...
Click to collapse
Just wait and it will come lol, theres no hardware limitation on tab 4 7,0 so 5.1.1 will fall for us, just wait till samsung makes it or till CM12.1 is ready in xda
Will restore of stock firmware overwrite custom recovery
Hi... just finally got my Tab 4 8.0 rooted by using custom recovery and special kernel. I love having root, but in the event i have to send the tablet in for any kind of warranty repair, i just want to know if simply ODIN flashing the stock 5.1.1 firmware will restore the stock recovery and reset my knox counter and stuff... Any details greatly appreciated!
beatbreakee said:
Hi... just finally got my Tab 4 8.0 rooted by using custom recovery and special kernel. I love having root, but in the event i have to send the tablet in for any kind of warranty repair, i just want to know if simply ODIN flashing the stock 5.1.1 firmware will restore the stock recovery and reset my knox counter and stuff... Any details greatly appreciated!
Click to expand...
Click to collapse
It will definitely restore the stock recovery. Idk about resetting the flash counter, my instinct tells me no but that could be wrong. If worst comes to worst and you do have to send it in under warranty, tell them Kies broke it, that's worked for me and a few of my friends even with the knox counter tripped lmao. And if you want the quickest firmware file downloads, check out this thread. About a 5 minute download versus anywhere from 2-8 hours from any other host (seriously, it's awful).
How can I know when the flash is done?
Thank you for this helpful guide. I used this to upgrade my Samsung Tab 4 8.0 from 4.4.2 KitKat to Lollipop 5.1.1.
May I suggest, OP, adding a note on how to know when the flashing is over. I mistakenly thought that all the boxes on the top half (the row that begins with with a green "Pass" box) would all be colored. But the users should know that the flash is over when you see the green Pass box.
Please see my attached screenshot.
thanks for bringing my tablet back to life!
I played chess with my cat.... and lost. Thank you for this, my Tab has been shut away in shame for a while, and I decided to bring it back out again.
Does anyone know if this will activate knox if I revert to the original firmware? T530NU
Cyntil8ing said:
Does anyone know if this will activate knox if I revert to the original firmware? T530NU
Click to expand...
Click to collapse
From where ?
repey6 said:
From where ?
Click to expand...
Click to collapse
From 5.0.2. Non rooted T530NU. Southern Cellular version.
Cyntil8ing said:
From 5.0.2. Non rooted T530NU. Southern Cellular version.
Click to expand...
Click to collapse
nothing will be
repey6 said:
nothing will be
Click to expand...
Click to collapse
OK thanks. Reverted to stock ROM. It didn't trip knox.
thelous said:
Just wait and it will come lol, theres no hardware limitation on tab 4 7,0 so 5.1.1 will fall for us, just wait till samsung makes it or till CM12.1 is ready in xda
Click to expand...
Click to collapse
Yeah... Right. The t-230nu has less powerful hardware and its 2016 and lolipop hasnt even come.
Pix12 said:
Yeah... Right. The t-230nu has less powerful hardware and its 2016 and lolipop hasnt even come.
Click to expand...
Click to collapse
what ive seen so fsr with 4.4.2 i dont see any reason to change 5.1.1 so its not big deal
I have the zip file if anyone has a way for me to get it posted here for devs to get to work on it.
chetqwerty said:
I have the zip file if anyone has a way for me to get it posted here for devs to get to work on it.
Click to expand...
Click to collapse
Upload it to android file host if you have dev status but if not you can upload it to google drive or any other hosting site.
EDIT: If you can get it uploaded somewhere, I'm sure @muniz_ri wouldn't mind looking at it and since it sounds like it prevents downgrading, we may be able to make a ROM out of it using the OD5 bootloader like what was done with the VZW S4 Lollipop update.
No not a dev, uploaded it to a free service http://www.fileconvoy.com/dfl.php?id=g71d4dc928ae33b36999687091905b660934562bab don't know why eset said it was unsafe, it downloaded fine when i allowed it. so just allow its fine.
Tried another service, FileDropper for those who have a problem
http://www.filedropper.com/update_3
ESET Antivirus didn't have a problem with this one
Shotty the first release @muniz_ri LOL
This is a OC4 to OE1 update.
timeToy said:
This is a OC4 to OE1 update.
Click to expand...
Click to collapse
Someone in another thread said they took the OTA and can't downgrage back to kikkat or lollipop via odin.
Sent from my SM-G900V using XDA Free mobile app
aholeinthewor1d said:
Someone in another thread said they took the OTA and can't downgrage back to kikkat or lollipop via odin.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
I personally have a Dev. Ed. S5, so I don't mind, as long as I don't flash the bootloader (aboot.mbn), so I am still interested in this.
It's been confirmed by muniz_ri that the qfuse counter was updated. If you update to OE1, there's no going back.
Guess i don't care about going back as long as i can have root and tether. I deleted the file from cache just have to get rid of this nagging install update message.
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
muniz_ri said:
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
Click to expand...
Click to collapse
Awesome. Downloading now.
muniz_ri said:
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
Click to expand...
Click to collapse
And here is a deodexed version for testing: G900V_OE1_Stock_Rooted_Deodexed_ROM
muniz_ri said:
And here is a deodexed version for testing: G900V_OE1_Stock_Rooted_Deodexed_ROM
Click to expand...
Click to collapse
I see that you say "if you've taken the ota and kept root" does that mean that you will retain root or is it hit or miss? any reports either way? also, have you done ay tweaks to this? enabled tether or anything besides deodexing? Thanks
I have a dev. ed. and it worked for me, including Advanced Calling, but I also flashed the rest of the firmware from the update file(sbl1.mbn sdi.mbn rpm.mbn and tz.mbn)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
awesome, Thanks !
muniz_ri said:
@Dudash
Here is the G900V_OE1_Stock_Rooted_ROM for testing.
For safety reasons it does not include any bootloader, however I expect that it will require the G900V_OD5_Bootloader in order to run.
Warning! Do not flash if you have taken the OE1 ota update and kept root. The ROM may work but there currently is no proven unbrick method, until the OE1 full .tar is available, in case something goes wrong.
Once the OE1 .tar is available we can try repackaging the NCG .tar without the bootloader as a way to downgrade/unbrick and re-root.
Click to expand...
Click to collapse
muniz_ri said:
And here is a deodexed version for testing: G900V_OE1_Stock_Rooted_Deodexed_ROM
Click to expand...
Click to collapse
Sorry it's taken so long to reply. I was at a party when I replied and downloaded the ROMs and didn't want to test them without having my computer in case of an Odin emergency. lol.
I'll be testing them shortly.
timeToy said:
I have a dev. ed. and it worked for me, including Advanced Calling, but I also flashed the rest of the firmware from the update file(sbl1.mbn sdi.mbn rpm.mbn and tz.mbn)
awesome, Thanks !
Click to expand...
Click to collapse
Thanks, which ROM did you test or both?
muniz_ri said:
Thanks, which ROM did you test or both?
Click to expand...
Click to collapse
I tried Odexed only, I'm not necessarily interested in deodexed until Xposed is more stable in Lollipop and TW. I also modified your script to avoid wiping. All good
timeToy said:
I tried Odexed only, I'm not necessarily interested in deodexed until Xposed is more stable in Lollipop and TW
Click to expand...
Click to collapse
Thanks, created new thread for the ROM's here: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
---------- Post added at 11:56 PM ---------- Previous post was at 11:24 PM ----------
chetqwerty said:
I see that you say "if you've taken the ota and kept root" does that mean that you will retain root or is it hit or miss? any reports either way? also, have you done ay tweaks to this? enabled tether or anything besides deodexing? Thanks
Click to expand...
Click to collapse
After reviewing the ota zip I have confirmed that it checks for stock /bin/ddexe which is modified when a device is rooted, therefore the official OC4-to-OE1 ota will fail on all rooted devices. I have not seen an OD5-to-OE1 ota update.zip in order to review.
chetqwerty said:
Guess i don't care about going back as long as i can have root and tether. I deleted the file from cache just have to get rid of this nagging install update message.
Click to expand...
Click to collapse
Confirming, if I'm not rooted, there's no way to disable the annoying update nag? I'm on BOC4 and I can't use the phone without the stupid msg popping up!
I'm a bit of a noob, so apologies if this question has an obvious answer:
Does any of this thread mean there's now a way to downgrade or root a non-rooted OE1?
equazcion said:
I'm a bit of a noob, so apologies if this question has an obvious answer:
Does any of this thread mean there's now a way to downgrade or root a non-rooted OE1?
Click to expand...
Click to collapse
No
I'm getting a problem where everytime I try to call someone or I receive a call, my SIM cards become undetected, the phone crashes after a short time and then doesn't detect SIM cards again, and Samsung or Google backups stop working, and all Samsung account related apps refuse to work. Only fixable after multiple factory resets.
After some investigation, I found that the Baseband and IMEI of the phone seem to be "unknown" whenever this occurs.
Is there a reason to this, or even a fix?
ZaneJulien said:
I'm getting a problem where everytime I try to call someone or I receive a call, my SIM cards become undetected, the phone crashes after a short time and then doesn't detect SIM cards again, and Samsung or Google backups stop working, and all Samsung account related apps refuse to work. Only fixable after multiple factory resets.
After some investigation, I found that the Baseband and IMEI of the phone seem to be "unknown" whenever this occurs.
Is there a reason to this, or even a fix?
Click to expand...
Click to collapse
same with my A125F variant, try to reset your device and it will fix the problem
and don't update your device with the build number of A125FXXU1BUG6, i think there's is a bug with that update..
You were completely right! It WAS the new update. I flashed the previous firmware and my SIMs work perfectly now! I've turned off auto-update in the normal area and developer settings too, hopefully can avoid it till it's fixed sometime. Thanks again!
I found a way how to fix it... try to flash the A125FXXU1BUG6 firmware version together with the pit file and it will fixed the problem
Hi all,
That sounds exactly like the problem I have
When I ROOT, I unblock BOOTLOADER, the connection to the network is blocked.
When I ROOT, I unblock BOOTLOADER, the connection to the network is blocked: / Bootloader unlocked = connection blocking
forum.xda-developers.com
(I was assuming it was due to the unlocking)
I was using Frija to get the latest (bugged?!) version - I was unable to find the previous one
Baseband A125FXXU1BUE1 / Build A125FXXU1BUE3 (XSA)
Could anyone please describe where to get an older version / the pit file?
Thanks a lot for that!
is your device is A125F?
A125F pit file i used this pit to fix the problem
A12_EUR_OPEN
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Jayke770 said:
A125F pit file i used this pit to fix the problem
A12_EUR_OPEN
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Thanks a lot, if I cannot find the lower firmware (it's on Samfrew, but downloading will take ages...), I'll give it a try. And good to have it if I get a bootloop!
Whoooo? said:
Thanks a lot, if I cannot find the lower firmware (it's on Samfrew, but downloading will take ages...), I'll give it a try. And good to have it if I get a bootloop!
Click to expand...
Click to collapse
i have an app that can download latest firmware for Samsung
or just try this website https://www.google.com/url?sa=t&sou...0QFnoECEIQAQ&usg=AOvVaw0neIA-O_nYmWom070upF4v
Just as a note for everyone who has the same problem -
I could fix this without the pit file, all that was required was flashing the complete (previous) firmware with Odin.
So not just the AP file but all the other ones as well (AP, BL, CP, CSC). Maybe a modem issue?
Hey guys, i tried everything, but have not been able to fix it.
I have the SM-A125W
and I tried flashing:
Samfw.com_SM-A125W_RWC_A125WVLU2AUFA_fac
Samfw.com_SM-A125W_RWC_A125WVLU2AUG5_fac
Samfw.com_SM-A125W_XAC_A125WVLU2AUFA_fac
Samfw.com_SM-A125W_XAC_A125WVLU2AUG5_fac
and used the pit file:
from: https://www.full-repair-firmware.com/p/galaxy-a12.html
and also, checked repartition option in odin,
When i make a phone call, and hang up, the sim card and phone number shows UNKNOWN
and when i perform a factory reset, it comes back and then goes again when i make a phone call.
Are we able to use the SP flash tool on this phone?
What seems to be the problem here?
I had this problem as well after updating firmware to A125FXXU1BUG6. I could not find a way to repair the IMEI until I found this file.
All I did was flash the tar file using odin in CP. I didn't need to flash other firmware packages or anything else.
Voilà!! Enjoy!
andef said:
I had this problem as well after updating firmware to A125FXXU1BUG6. I could not find a way to repair the IMEI until I found this file.
All I did was flash the tar file using odin in CP. I didn't need to flash other firmware packages or anything else.
Voilà!! Enjoy!
Click to expand...
Click to collapse
Does it also work with the new update A125FXXU1BUI3?
andef said:
I had this problem as well after updating firmware to A125FXXU1BUG6. I could not find a way to repair the IMEI until I found this file.
All I did was flash the tar file using odin in CP. I didn't need to flash other firmware packages or anything else.
Voilà!! Enjoy!
Click to expand...
Click to collapse
Allehandro said:
Does it also work with the new update A125FXXU1BUI3?
Click to expand...
Click to collapse
THANKS SOOOO MUCH. IT WORKED. IT WORKED WITH THE NEW UPDATE AND IMEI AND BASEBAND ARE BOTH WORKING. LIFESAVER!!!
andef said:
I had this problem as well after updating firmware to A125FXXU1BUG6. I could not find a way to repair the IMEI until I found this file.
All I did was flash the tar file using odin in CP. I didn't need to flash other firmware packages or anything else.
Voilà!! Enjoy!
Click to expand...
Click to collapse
Allehandro said:
Does it also work with the new update A125FXXU1BUI3?
Click to expand...
Click to collapse
I've flashed the new A125FXXU1BUJ4 November security update and the bug is still there but I was able to flash the same IMEI/Baseband repair file and it worked. THANKS FOR THAT.
andef said:
I had this problem as well after updating firmware to A125FXXU1BUG6. I could not find a way to repair the IMEI until I found this file.
All I did was flash the tar file using odin in CP. I didn't need to flash other firmware packages or anything else.
Voilà!! Enjoy!
Click to expand...
Click to collapse
However, this file according to your link now becomes paid, please re-upload into XDA
i already fix my a12
I am using a125n. On Android 11, Clearing /mnt/vendor/nvdata, flashing with pit, re-locking does not work. But flashing android 10 CP makes the phone work well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you're not sure it a software fail, "Unknown" Baseband probably cause by faulty MT6177mv chip on mainboard. Usually damage by warter or falling, and it just need to reflow or replace a new one.both imei will re-apear when the baseband chip working.
Talking from personnal experient