Database Users

DEV EDITION Need modem image for G900V DEV EDITION

I have a developer edition phone, and I think I managed to install a retail modem. For my own reasons, I'd like the dev modem version back. Can someone create an image via cat /dev/block/.../by-name/modem > modem.img and attach it? (find /dev | grep by-name) It doesn't contain any identifying info- that's in modemst1, modemst2, and efs. But you probably know that already. No odin tar necessary, just an image is fine. Or do whatever you want, as long as I can grok it back into the image. Do what makes you happy.
I would appreciate it very much. If someone wants to get fancy and make a whole recovery boot chain (past aboot to boot, or whatever) that would be cool, too. But just a modem works. I'm talking about the files like apnhlos, carrier, boot, dbi? ddr? fota? fsc? fsg? modem pad param persdata persist recovery rpm sbl1 ssd tz. I don't know the actual boot chain and boot order. Maybe someone else does.
If one of these contains identifying information please don't shoot me, I'm not trying to steal your IMEI. But I really really really would appreciate the modem binary, and that doesn't contain personal info.
Please send me a dev edition G900V modem partition image!

longus catus said:
I have a developer edition phone, and I think I managed to install a retail modem. For my own reasons, I'd like the dev modem version back. Can someone create an image via cat /dev/block/.../by-name/modem > modem.img and attach it? (find /dev | grep by-name) It doesn't contain any identifying info- that's in modemst1, modemst2, and efs. But you probably know that already. No odin tar necessary, just an image is fine. Or do whatever you want, as long as I can grok it back into the image. Do what makes you happy.
I would appreciate it very much. If someone wants to get fancy and make a whole recovery boot chain (past aboot to boot, or whatever) that would be cool, too. But just a modem works. I'm talking about the files like apnhlos, carrier, boot, dbi? ddr? fota? fsc? fsg? modem pad param persdata persist recovery rpm sbl1 ssd tz. I don't know the actual boot chain and boot order. Maybe someone else does.
If one of these contains identifying information please don't shoot me, I'm not trying to steal your IMEI. But I really really really would appreciate the modem binary, and that doesn't contain personal info.
Please send me a dev edition G900V modem partition image!
Click to expand...
Click to collapse
I maybe wrong, but I think the Dev modem and the retail modem are the same, unless however there has been an OTA that changed the retail modem. I have a Dev S5 and my modem is G900VOYU1ANCG.

Thanks for your response.
My phone still says "MODE: developer" but I think something's not quite right. Actually at one time it didn't say developer, but I kept calm knowing that it just hurts more if you resist.. So I rooted the image and overwrote the aboot with a backup and now it says developer but it's not all quite right. I think. Uh maybe TWRP should have a "full retard/backup" option, but a recursive script over the "by-name" list works well, too.
I had ordered another dev phone a few days ago, and I think I will take the "partial refund" and get a phone that I know works, and get it right *now*. Then I'll be the one making a recovery tar that nobody will care about, but should anyone else have the misfortune of being me (currently the count is 1), they will find some respite in that tar image. But I can still write and boot assorted kernels, recoveries, and roms. So obviously it is somewhat of a development phone.
jpcalhoun said:
I maybe wrong, but I think the Dev modem and the retail modem are the same, unless however there has been an OTA that changed the retail modem. I have a Dev S5 and my modem is G900VOYU1ANCG.
Click to expand...
Click to collapse
I dunno, you may be right. I made a tar with the order of boot, recovery, modem. Because... anyway, odin says the following:
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
When I have a tar in the order of KLTE_USA_VZW.pit, aboot.mbn, spl1.mbn, rpm.mbn, tz.mbn, sdi.mbn, NON-HLOS.mbn, boot.img recovery.img modem.img, I get the following on my phone:
SECURE CHECK FAIL: modem
Invalid percent of drawing download progress bar!
SECURE CHECK FAIL: aboot.
Well I checked the md5sum of that aboot file and the very aboot partition image and they're one and the same, so something is up. I have no idea what I'm doing, but I'm doing it pretty well. It's funny because if I 'cat modem.img > disk' I will end up with the Verizon unauthorized software triangle of doom. So that's one reason I think the dev and retail modems are different. And the maligned bootloader shows its sensitive side, giving an accurate warning of impending doom.
C:\Users\andrew\Downloads\dev>find "G900" modem
---------- MODEM
G900V.00
8░σ♀k☺ ☺|░σ♀k☺0☺╚░σ♀k☺6☺♀▒σ♀G900V.003
G900V.05
SM-G900V
G900VVRU1ANCG
Does yours say the same thing?
Or uh... grep -a G900V /path/to/modem/partition | strings ... or you could adb pull the modem partition... I'm sure there are more ways, most of which do not require goat sacrifice (I wish I had known this before).

So I got all the partition images from a totally new untouched developer phone.
Writing the other phone's aboot to my aboot partition doesn't seem to do anything abnormal except "Mode: Developer" is gone. And is back when I flash my original copy.
I created a tar called modem.tar with the phone's own modem.bin as its only contents. This is what I see on the screen when I try to flash it:
Code:
ODIN MODE
PRODUCT NAME: SM-G900V
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
REACTIVATION LOCK(kk): OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, A1, A1, P1
MODE: Developer
UDC START
SECURE CHECK FAIL : modem
Which is weird, because that's the modem already installed, through dd/cat to the partition.
I created a tar that had the same file order as G900VVRU1ANCG_G900VVZW1ANCG_G900VVRU1ANCG_HOME.tar.md5, which is aboot, sbl1, rpm, tz, sdi, NON-HLOS, boot, recovery, system, cache, and modem. With just up to but not including system. And failed on flashing the phone's own aboot. Maybe because there's trailing garbage from trying to flash the whole partition image instead of just the signed portion of the file. So how do I know how large the actual file to flash should be...
The modem image says it's G900VOYU1ANGC, which is different than can be seen in the above tar file.
It would be nice to know if the trailing garbage is why the file doesn't flash through odin-only the unprotected (as dev edition) recovery boot and system are ok with it. And how to get rid of the garbage. In the file, that is.

Hey longus catus, did you ever manage to create a restoration image for other SM-G900V dev edition users? I have one as well, flashed TWRP via ODIN, went to make a backup, but I didn't double check that the backup sync'd to my SD card and installed CM11 only to find that my backup of stock was gone. I can get 4G data, but I cannot make or receive calls. I am not sure of what could have happened. After a lot of digging I managed to find a system.img and boot.img from stock ANCG, however, I still cannot make or receive calls (or use <= 3G data).
I am really hoping that my EFS did not get corrupted somehow. My IMEI is still valid, so I do not think that is the case, probably just filling myself with unwanted dread. Anyway, if you managed to create a good recovery tar it might go a long way toward my debugging. I am not far from declaring this a very expensive PDA.

c89memcpy said:
Hey longus catus, did you ever manage to create a restoration image for other SM-G900V dev edition users? I have one as well, flashed TWRP via ODIN, went to make a backup, but I didn't double check that the backup sync'd to my SD card and installed CM11 only to find that my backup of stock was gone. I can get 4G data, but I cannot make or receive calls. I am not sure of what could have happened. .
Click to expand...
Click to collapse
I am in almost the exact same boat. The only difference for me is that I used Philz (instead of TWRP) because of the fact that I wanted to verify I could restore my backup and after 3 times of the backup disappearing with TWRP, I flashed Philz, then backed p, then verified the backup restored. That is when I flashed Cyanogenmod and had "no service" so I restored my backup and assumed I was up and running until a day or two later when I got voicemail notifications. I am not able to make or receive calls but everything else seems to work. Any ideas? How can I get a "stock" S5 dev edition tar that I can restore?
---------- Post added at 09:47 AM ---------- Previous post was at 09:00 AM ----------
unruly1 said:
I am in almost the exact same boat. The only difference for me is that I used Philz (instead of TWRP) because of the fact that I wanted to verify I could restore my backup and after 3 times of the backup disappearing with TWRP, I flashed Philz, then backed p, then verified the backup restored. That is when I flashed Cyanogenmod and had "no service" so I restored my backup and assumed I was up and running until a day or two later when I got voicemail notifications. I am not able to make or receive calls but everything else seems to work. Any ideas? How can I get a "stock" S5 dev edition tar that I can restore?
Click to expand...
Click to collapse
well in a very strange turn of events... This is what I did to fix my issue....
powered off my phone
removed micro SD card
removed SIM card
powered on phone
waited 5 minutes
powered off my phone
installed SIM card
installed micro SD card
powered on phone
placed a call from my work phone to GS5 Dev Edition and GS5 rang.
placed a call from GS5 Dev Edition to work phone and work phone rang.
I really hope this helps someone else.

Wow I really hope that works. I will try it when I get off work tonight.

It did not work... Were you running the stock firmware?

I flashed to stock and it worked. Thank you so much. I am now running albinoman887's cm12 build successfully (with the exception of NFC).

Question
jpcalhoun said:
I maybe wrong, but I think the Dev modem and the retail modem are the same, unless however there has been an OTA that changed the retail modem. I have a Dev S5 and my modem is G900VOYU1ANCG.
Click to expand...
Click to collapse
If you change modem of g900v to g900t, will 4g lte work, I have problem with my Verizon G900V it shows only e, no lte ot 4g :crying: So if I change modem to t-mobil's modem will it work?
Thanks

[Q] How to do a *REAL* backup

A painful experience - see below - taught me that a NANDROID backup isn't enough.
I had to find a PIT file, a bootloader and a modem.
What else does one need to be able to get back to an earlier version, and is there some software to do that
automatically?
I've tried an Android-5.0 for which I had to flash the boot loader and the modem, as well.
The Android-5.0 system booted well but it turnt out that I got insurmountable difficulties with WLAN
authentication. Therefore I wanted to go back to Kitkat (4.4.2) which I had backed up by TWRP.
I could restore the system but got a boot loop - no wiping helped.
Then I tried to install a stock 4.4.2 system but ODIN-3.09 has stalled for more than an hour such that I had
to kill it. Now my device was broken. Luckily I did find a suitable PIT file, boot loader and modem.
Even then ODIN didn't succeed. With the help of Philz-Touch-Recover I could reformat some partitions.
Only after that ODIN succeeded - together with the PIT file - to flash the bootloader and the modem,
Only now, I could boot into the old version.
Many thanks for a hint,
Helmut.

Bricked - possible misuse of Flashfire

Using Flashfire, I installed the zipped file UPDATE-SuperSU-v1.99r4.zip on my Verizon G900V, which is a towelroot rooted Lollipop. My phone ultimately rebooted, but goes no further than the initial screen. It will not fully reboot, it is not recognized via USB by my PC, it cannot be turned off except by removing the battery, and seems totally bricked. I obviously can’t even odin. I have no other data, such as build, etc., about it since it is no longer accessible. What can I do now? Any help will be most appreciated!

Everhopefull said:
Using Flashfire, I installed the zipped file UPDATE-SuperSU-v1.99r4.zip on my Verizon G900V, which is a towelroot rooted Lollipop. My phone ultimately rebooted, but goes no further than the initial screen. It will not fully reboot, it is not recognized via USB by my PC, it cannot be turned off except by removing the battery, and seems totally bricked. I obviously can’t even odin. I have no other data, such as build, etc., about it since it is no longer accessible. What can I do now? Any help will be most appreciated!
Click to expand...
Click to collapse
That is not totally bricked :victory:
You are just softbricked. First, did you have safestrap installed?
If you don't care about any of the internal data and just want the OS fixed, just put it in download mode (Power+Home+VolDown) then Vol Up to confirm, and get the .tar of the stock image. Flash it with Odin- bam done.
Be warned, because you were towelrooted this would ultimately flash the latest LOCKED bootloader- so to stay on your UNLOCKED bootloader you need to find a tar with NO bootloader (there is a PB1 no bootloader stock tar)
If you had safestrap- all you have to do is flash the NK2 kernel and it will boot into safestrap- allowing for recovery of internal data and flashing of a new ROM.

If he's on any of the Firmwares below OD5, he can safely Odin back to NCG and start from scratch using Towelroot. All of our bootloaders are locked no matter which firmware version you're on. It's the versions OE1 and up that are more locked down from rooting

smokerbond said:
That is not totally bricked :victory:
You are just softbricked. First, did you have safestrap installed?
If you don't care about any of the internal data and just want the OS fixed, just put it in download mode (Power+Home+VolDown) then Vol Up to confirm, and get the .tar of the stock image. Flash it with Odin- bam done.
Be warned, because you were towelrooted this would ultimately flash the latest LOCKED bootloader- so to stay on your UNLOCKED bootloader you need to find a tar with NO bootloader (there is a PB1 no bootloader stock tar)
If you had safestrap- all you have to do is flash the NK2 kernel and it will boot into safestrap- allowing for recovery of internal data and flashing of a new ROM.
Click to expand...
Click to collapse
Many thanks, Smokerbond. I do wish I had waited for your reply, but, as usual, I was impatient (and somewhat concerned). I found part of what you knew elsewhere, downloaded from Sammobile, and flashed. Unfortunately, as you noted, that didn’t keep root. My question now is, can I start over? I flashed G900VVRU1BOA8-G900VVZW1BOA8 which, of course, is filled with bloatware. I have all my files I used originally, but no instructions and, as we say at my age, (77), I have slept since then.

You can Odin flash the PB1.tar with no bootloader, then use @jrkruse root method. That is the simplest way. You can also Odin back to NCG and use Towelroot, but it makes it a PITA with enabling advanced calling.
---------- Post added at 01:14 PM ---------- Previous post was at 01:13 PM ----------
Also, I'm not familiar with that SuperSU version. That is probably what caused the bootloop. I'm currently running SuperSU 2.71 on my S5 and it works great, but you can go with the latest stable version if you prefer.

Shouldn't be trying to flash SuperSU from 2014. Here's the latest version once you get everything up and running again.

Thanks for all the suggestions. I am now up and running, using Chainfire's SU 2.65. Since I was familiar with the path, I did go back to NCG and use towelroot, but since I have no need for the advanced calling (with which I was not familiar), I am happy with my setup.

On PD1 rooted rom, but still on OC4 bootloader help.

So i have spent the last 4-5 hrs trying to get this phone to work for my brother and i am stuck at the moment. Need some help
Ever since OC4, i never updated the bootloader, only the ROM. phone was in OK3....I followed the thread for unlocking the bootloader, and gained the MODE: Developer.
I tried to follow the thread for muniz and got the files i needed.
Once i got MM up, noticed that WIfi, capacitive buttons wouldnt work. So i reverted back to PB1 downgrade.
i once again followed the steps and got MM back into the phone, but still the same problem as above.
Here is how the phone is currently:
Bootloader screen: " Current binary custom,system status custom, reactivation off, qualcomm secureboot enable (CSB), AP SWREV S1,T2,R1,A1,P1 and MODE: Developer, UDC Start
Recovery : Currently it boots to TWRP 3.0.2-2
Once booted into android, i used Samsung Mobile Info.
Build Number: MMB29M.G900VVRU2DPD1
Kernel version: 3.4.0-8025411
PDA: G900VVRU2DPD1
CSC: G900VVRU2DPD1
Baseband: G900VVRU2DPD1
Bootloader: G900VVRU1BOC4
So, can i just update the bootloader to MM, unlock it, re root, and fix? DO i have to revert once again to PB1?
I need some direction as to how get bootloader to PB1 or PD1...
Thanks

Exact same problem here. I've been struggling with this for about a week now. PD1 bootloader will NOT flash in Safestrap or FlashFire. I even tried TWRP for the heck of it.
Sent from my SM-G900V using XDA-Developers mobile app

I had the same problem that I could not get the buttons to work over several days several and several different methods, each time having to ODIN back to PB1. Two of the times I even had to go find a flash file for firmware because the ODIN did not restore the bootloader back to PB1. When I did finally get it to work I followed the information in the OP for unlocking the BL that I will paste below the main thing being place the ROM on the phone storage not the SD as the files flashed below use the TWRP that doesn't see SD cards
Download these 2 files and place on phone And A Custom Rom
PB1_Flashfire_Prepare.zip https://www.androidfilehost.com/?fid=24572369242686444
PD1_Firmware_With_Dev_Aboot_Twrp_Recovery_Image_Flashfire_Only.tar.zip https://www.androidfilehost.com/?fid=24572369242686471
Reboot to TWRP and flash PB1_Flashfire_Prepare.zip
Reboot
Open Flashfire (It will be installed by the zip you flashed in TWRP) grant supersu permission
Goto Flashfire Settings check box to Flash bootloaders and uncheck box for Emulate framebuffer
Goto Actions
Now add Flash firmware package and choose PD1_Firmware_With_Dev_Aboot_Twrp_Recovery_Image_Flashfire_Only.tar.zip
Now manually check on all the partions to flash. Check them all make sure to scroll down. Now click check mark at top right for ok
Now on the warning dialog that pops up about splitting protected partitions select no
Now in the actions dialog box where it says reboot change that to recovery
So it should look like this
Flash firmware package
Primary Bootloader
Secondary Bootloader
Etc........
EverRoot
EverRoot Disabled
Reboot
Recovery
Click FLASH
When finished phone will reboot to TWRP
Wipe Data, Wipe Cache, Wipe System
Install Custom Rom
For the custom rom I used the one from here labeled G900V_PD1_Stock_Rooted_ROM.zip http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784 and the ROM took short of a min to boot past the samsung screen then roughly 8-10 mins to boot past the red Verizon screen.
Of course once it reboots and your up and going on the new rom you'll have to flash TWRP I used 3.0.0.0
Hope this helps.
---------- Post added at 03:22 PM ---------- Previous post was at 03:06 PM ----------
Oh and if you make a Nandroid backup before you try PD1, you can always ODIN flash TWRP and then just restore your previous rom (that's what I kept doing after the first 2 total losses)
TWRP https://www.androidfilehost.com/?fid=24459283995310730

Thanks ecen92!! i saw your message a bit late, but i did go back at it with a fresh mindset last night and got it working!!
Here is how i did:
So, after many reading between the lines, something about bootloaders not flashing if the kernel and firmware dont match... anyways, since i was on OC4 i almost went back to a OC4 full tar, but couldnt find it... Glad i didnt.
So i decided to see if i could restore to PB1 fully, and start from there....
I flashed the PREPARE YOUR PHONE FOR ROOT from here http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
But after it finished, now i was in PB1 but still with OC4 bootloader.... something told me to redo it.... so i did.. i RE DID the above flash again!!! and once completed i was on a full PB1 with locked bootloader.
The trick for me was that i HAD TO FLASH THE PB1 FULL TAR 2X IN A ROW!
From there i did the working root method found on the same thread http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
After i gained root, i then unlocked the bootloader based on this steps http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
After unlocking the bootloader, then i followed the instructions labeled in light blue called "Upgrade To PD1 Rom With PD1 Unlocked Bootloader From 5.0 TW Rom With PB1 Unlocked Bootloaders" (annoying a** color to see)
After which i was then on PD1 rom rooted, PD1 unlock bootloader and no more problems with wifi, capacitive buttons not responding, etc.
Hope i can help anyone else stuck with this problem.

Good to hear you've got it all working! :good:

I will make a post for those confused that still dont know how to properly update to PF4 rooted using this post http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
The initial instructions for rooted arent too clear. I have asked for clarification from the source and others, and my questions have fallen on deaf ears.
I had my brothers phone on PD1 rooted/unlocked, and by flashing the rooted version on the OP followed by stock PF4 bootloader, bricked the software. (The msg that it cant boot) and after D-king around for 4 hrs, i finally got it.
Anyways here is the steps i did ( i dont own steps, just trying to copy paste info to paint a clear picture)
Had to flash the PB1 full tar on ODIN
Then i had to root the PB1 as mentioned here. http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
After root i had to unlock bootloader. http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
I used Method 2: Unlocker via Safestrap Samsung_Bootloader_Unlocker.zip in safestrap or flashfire
After this i verified i was on PB1 rooted and unlocked.
From there i went to Flashfire and flashed G900V_PF4_Stock_Rooted_ROM.zip (For "Unlocked" Bootloaders Only!) as posted on the OP
This placed me on PF4 ROM and firmware, but with a PB1 unlocked bootloader. (This is where the back button, recents and wifi dont work)
I then flashed TWRP 3.0.0 via ODIN
From there i followed the "If You Already Have Bootloader Unlocked And On A Samsung TW Rom" found here http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
In case instructions changed, like it has on the past, they are:
In TWRP Flash TWRP_Prepare.zip
Reboot to Download Mode
In Odin Under AP slot load PB1_Firmware_Only_NK2_Kernel.tar.md5
Now in Odin Under PIT load S5_KLTE_USA_VZW.pit If you have a 32gb phone instead of 16gb phone skip this step
Click Start
When finished on reboot watch for Safestrap Splash Screen and enter Safestrap
Now goto Power Menu/Reboot Menu and reboot to Download Mode
Make sure in download mode the current binary is Official. If it is not reflash In Odin Under AP slot load PB1_Firmware_Only_NK2_Kernel.tar.md5
Now in Odin Under PIT load S5_KLTE_USA_VZW.pit
Click Start on reboot enter Safestrap reboot back to download mode and make sure binary status is Official
If Binary Status is Official Pull battery restart and enter SafeStrap
Flash: SafeStrap_PF4_Bootloader_Unlock_AIO.zip
Phone will Power Off.
Pull Battery enter download. Flash via ODIN TWRP 3.0.0 as the previous flash will install 3.2 which doesnt see the SD card.
There u go, thats it, this will have you on a rooted/unlocked PF4.

PL1 modem/baseband?

Anybody have a tar.md5 of just the modem and baseband from PL1 update?
TIA

dragonhart6505 said:
Anybody have a tar.md5 of just the modem and baseband from PL1 update?
TIA
Click to expand...
Click to collapse
Perhaps. I followed the tutorial which works if you are already on the modem you want to backup. I will upload later but if you already are on PL1 modem then follow instructions I found (no warranties, all risks of damage etc)
Run in TWRP's terminal or ADB while in TWRP or Terminal command in Android with USB debugging on (root required and terminal app)
ls -al /dev/block/bootdevice/by-name
Look for modem or mdm. Once you find it, make note of the block.
To back them up in Terminal modem: dd if=/dev/block/mmcblk0pXX of=/sdcard/modem.bin
where XX means proper block partition.
you can also backup APN-HLOS, fsg, modemst1, and modemst2 providing other names instead of modem.bin
Got information from here: https://forum.xda-developers.com/showpost.php?p=64169401&postcount=3
For creating tar file use TAR_MD5_PACKAGER

AjvarXX said:
Perhaps. I followed the tutorial which works if you are already on the modem you want to backup. I will upload later but if you already are on PL1 modem then follow instructions I found (no warranties, all risks of damage etc)
Run in TWRP's terminal or ADB while in TWRP or Terminal command in Android with USB debugging on (root required and terminal app)
ls -al /dev/block/bootdevice/by-name
Look for modem or mdm. Once you find it, make note of the block.
To back them up in Terminal modem: dd if=/dev/block/mmcblk0pXX of=/sdcard/modem.bin
where XX means proper block partition.
you can also backup APN-HLOS, fsg, modemst1, and modemst2 providing other names instead of modem.bin
Got information from here: https://forum.xda-developers.com/showpost.php?p=64169401&postcount=3
For creating tar file use TAR_MD5_PACKAGER
Click to expand...
Click to collapse
Unfortunately Im not on PL1, I'm on OK2. I'm having Bluetooth and Wifi disconnections/failures. Sometimes after a while they will completely die out and refuse to turn back on or allow connections, requiring a reboot where they will work again for a while. I'm hoping that an update to the baseband will either subdue or fix these issues. I've tried multiple roms and tried reverting to older basebands (which killed BT/Wifi all together). Stock works ok, but since the device is no longer in service I'm unable to tether my wifi/Bluetooth without root. If I'm rooting anyway, I might as well be running a custom ROM.
It's a longshot, but if it COULD help I'd like to update anyway

dragonhart6505 said:
Unfortunately Im not on PL1, I'm on OK2. I'm having Bluetooth and Wifi disconnections/failures. Sometimes after a while they will completely die out and refuse to turn back on or allow connections, requiring a reboot where they will work again for a while. I'm hoping that an update to the baseband will either subdue or fix these issues. I've tried multiple roms and tried reverting to older basebands (which killed BT/Wifi all together). Stock works ok, but since the device is no longer in service I'm unable to tether my wifi/Bluetooth without root. If I'm rooting anyway, I might as well be running a custom ROM.
It's a longshot, but if it COULD help I'd like to update anyway
Click to expand...
Click to collapse
OK, I just downloaded full official PL1 stock, these were right in the tar file as my backups contain slightly more info. It is getting uploaded right now.
https://mega.nz/#!8chxiDJa!OS_i03da_uJ4p2BKzo7DGPEGubcEIzEOgk6zVjbCDfE
NON-HLOS should have more chances to help as modem is for GSM although it might end up with same incompatibility with ROM (turned off Wi-Fi). As for your problem, maybe another Kernel would work better.
How to install: you can try Heimdall or Odin. This topic provides enough info about how to do this: https://forum.xda-developers.com/galaxy-s4/general/ref-galaxy-s4-i9505-modems-bootloaders-t3315987

AjvarXX said:
OK, I just downloaded full official PL1 stock, these were right in the tar file as my backups contain slightly more info. It is getting uploaded right now.
https://mega.nz/#!8chxiDJa!OS_i03da_uJ4p2BKzo7DGPEGubcEIzEOgk6zVjbCDfE
NON-HLOS should have more chances to help as modem is for GSM although it might end up with same incompatibility with ROM (turned off Wi-Fi). As for your problem, maybe another Kernel would work better.
How to install: you can try Heimdall or Odin. This topic provides enough info about how to do this: https://forum.xda-developers.com/galaxy-s4/general/ref-galaxy-s4-i9505-modems-bootloaders-t3315987
Click to expand...
Click to collapse
Awesome! Thanks alot. Hopefully the wifi won't go out. That would certainly be the opposite of what I'm trying to achieve as the S4 on Wifi is primarily my tether device for my PC. If the case is that it'll kill my Wifi, I am more than familiar with using Odin to flash back to OK2 (this is not my first rodeo with Samsung devices).
Thank you very much mate

dragonhart6505 said:
Awesome! Thanks alot. Hopefully the wifi won't go out. That would certainly be the opposite of what I'm trying to achieve as the S4 on Wifi is primarily my tether device for my PC. If the case is that it'll kill my Wifi, I am more than familiar with using Odin to flash back to OK2 (this is not my first rodeo with Samsung devices).
Thank you very much mate
Click to expand...
Click to collapse
Please, tell me how it worked out.

Fail
Both Failed in Odin for me. It seems the only option is to reflash the whole stock image and reinstall the custom recovery
Now , all we need is someone to upload the whole PL1 stock rom to androidfilehost or mega so that we wouldnt have to wait 6 hours on a throttled download from these greedy Samsung Firmware losers.....
Ill post a link to the stock PL1 rom as soon as it finishes......

Reinstall of custom recovery shouldn't be of any problem as you already flash firmware in Odin so just extra reboot to DM and quick flash. Just uncheck Reboot, then when finished press power button and remove battery (for modem to get switched) and then boot in D mode.
---------- Post added at 09:19 PM ---------- Previous post was at 08:41 PM ----------
dragonhart6505 said:
Anybody have a tar.md5 of just the modem and baseband from PL1 update?
TIA
Click to expand...
Click to collapse
Also, are you on L720 or L720T? Had to ask earlier, I assumed you are on L720.

AjvarXX said:
Reinstall of custom recovery shouldn't be of any problem as you already flash firmware in Odin so just extra reboot to DM and quick flash. Just uncheck Reboot, then when finished press power button and remove battery (for modem to get switched) and then boot in D mode.
---------- Post added at 09:19 PM ---------- Previous post was at 08:41 PM ----------
Also, are you on L720 or L720T? Had to ask earlier, I assumed you are on L720.
Click to expand...
Click to collapse
L720T. I've had the phone up and running for a while now on Oreo. It's been better, but my Wifi speeds have cut down from 25Mbs to like 10 even right next to my router with every other device disconnected. BT still cuts out often. I like how much cleaner Stock runs so I've been waiting for the post above to link PL1.

Tried to install the PL1 Modem from this thread, but Odin displays 'Fail' message. Receive response from BootLoader.
My bootloader is a PL1 (5.0.1). I went from PL1 (Stock, Unrooted, SIM locked) to NG5 (Rooted, SIM Unlocked) and now on 6.0.1 JDCTeam's ROM. https://forum.xda-developers.com/ga...dcteam-android-source-project-mra58v-t3251663
As per 6.0.1 Rom's requirement, both Bootloader and Baseband have to be above 5.0. My baseband is still stuck at NG5.

I have the Sprint L720, has anyone posted the full PL1 rom? I bought it used and it was already on PL1. Tried flashing back to NG2, but kept getting the no seandroid error. Used a pit file that was listed on XDA and now it flashed, but it'll get stuck at the Sprint screen. Need some assistance on getting it to at least boot. Thanks much.