Database Users

I337UCUGOC3 bootloader locked, want to update to I337UCUGOK2 to unlock bootloader

I hit on UPDATE on the phone for an OTA update but it only says UNABLE TO CONNECT AT&T SERVER. When I bought it, it had 5.0.1 (I337UCUGOC3) out of the box. Searching on internet says that is bootloader locked (so I cant do anything).
- Can I Update to I337UCUGOK2 and bootloader will be unlocked (I mean, will I be able to do it)?
- Does anyone know where can I grab I337UCUGOK2 for offline install and is it ODIN safe to update it (remember I have I337UCUGOC3 bootloader locked)?
please help

Once the bootloader is locked, it will always be locked until someone finds a way to unlock it. Updating the bootloader will not allow it to be unlocked.

cybercuate said:
I hit on UPDATE on the phone for an OTA update but it only says UNABLE TO CONNECT AT&T SERVER. When I bought it, it had 5.0.1 (I337UCUGOC3) out of the box. Searching on internet says that is bootloader locked (so I cant do anything).
- Can I Update to I337UCUGOK2 and bootloader will be unlocked (I mean, will I be able to do it)?
- Does anyone know where can I grab I337UCUGOK2 for offline install and is it ODIN safe to update it (remember I have I337UCUGOC3 bootloader locked)?
please help
Click to expand...
Click to collapse
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.

help... I want to RMA it
sway8966 said:
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
Click to expand...
Click to collapse
Everywhere says I need a kitkat rom as base.
My s4 came with 5.0.1 with OC3 and bootloader locked out of the box. I tried some post where says I can flash TWRP and CWM but my phone stucked on bootloops. Then I managed to get back to stock rom and now when I want to turn it on it says " SAMSUNG (and lower on the screen) Custom"
Camera began to fail and I want to return it as RMA but I was looking to reset the flash counter but every post I read is that OC3 bootloader locked users are just doomed.
Do you know a method that I can do for reset that counter?
Camera dont focus anymore and I tried all the posts about safemode, etc.

cybercuate said:
Everywhere says I need a kitkat rom as base.
My s4 came with 5.0.1 with OC3 and bootloader locked out of the box. I tried some post where says I can flash TWRP and CWM but my phone stucked on bootloops. Then I managed to get back to stock rom and now when I want to turn it on it says " SAMSUNG (and lower on the screen) Custom"
Camera began to fail and I want to return it as RMA but I was looking to reset the flash counter but every post I read is that OC3 bootloader locked users are just doomed.
Do you know a method that I can do for reset that counter?
Camera dont focus anymore and I tried all the posts about safemode, etc.
Click to expand...
Click to collapse
Flashing TWRP and CWM is for the AT&T S4 with older bootloader (MDL, MDB). After that two firmware versions the bootloader is locked.
For AT&T S4 the last full firmware released is NB1. After that they released incremental updates via OTA. That is why you need kitkat (NB1) as base.
For NB1, Muniz uploaded two firmwares. One is the stock and the other is rootable stock. Try the stock one and see you still have the custom symbol.
To reset the counter, there is an app calls Triangle away by Chainfire. However, it does not work on AT&T S4 with locked bootloader.

Trying Odin-Stock NB1
sway8966 said:
Unlocking/exploiting the bootloader for the AT&T is still in process, I think.
Bootloader locked means you can not install custom recovery like TWRP, CWM or custom kernel. You can still root, you can still use odin and you can still install custom rom using either safestrp or flashfire.
Here is the thread explaining how to upgrade stock or rooted stock roms.
The explanation starts from installation of NB1 firmware so that you can easily root the phone by using twolroot.
If you do not care for the root you can start reading from the step 2 "Flash update in stock recovery"
Since you are on OC3, you need OC3 to OC4 and OC4 to OK2 files to get OK2.
Click to expand...
Click to collapse
sway8966 said:
Flashing TWRP and CWM is for the AT&T S4 with older bootloader (MDL, MDB). After that two firmware versions the bootloader is locked.
For AT&T S4 the last full firmware released is NB1. After that they released incremental updates via OTA. That is why you need kitkat (NB1) as base.
For NB1, Muniz uploaded two firmwares. One is the stock and the other is rootable stock. Try the stock one and see you still have the custom symbol.
To reset the counter, there is an app calls Triangle away by Chainfire. However, it does not work on AT&T S4 with locked bootloader.
Click to expand...
Click to collapse
Thanks. I'll try Odin it with the stock rom from your link. I'll post news here when it finish flashing

1st part - Success
I'm on 4.4.2 NB1, flash counter back to normal but still bootloader locked
Now I have to go back to OC3 to RMA it.
OTA does nothing, smartswitch shows no updates neither kies.
I'll have to Odin it back to OC3
Can I have some help?

And Success. I'm back on stock OC3 no root.
time to RMA
- camera still doesn't focus
- boot screen is back to normal but when in odin mode the counter shows 0x1
- sometimes shows "sim card could not be detected" or similar messages and force me to restart the phone (just happend 2 times until now, never happend before)
I followed this thread
http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
Post 2
Thanks to sway8966

Need help upgrading bootloader and modem

I've gotten no help at all with this. Very unlike this forum. My phone is a kltevew, which is straight talks version of a g900v. I need help, there are lots of great looking Roms that require you to have mm firmware I'd like to try!

Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)

ddjr said:
Not sure why I'm getting g no responses on this. Surely someone must know something... The only response I got was not only not helpful but jerky and obnoxious. Doesn't anyone know how to upgrade the firmware on my phone? (And no, google has no answers for me on this.. I look everyday)
Click to expand...
Click to collapse
Download it with samfirm http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 (Model= SM-G900V Region= VZW) or from sammobile http://www.sammobile.com/firmwares/database/SM-G900V/ , do you know how to flash firmware with odin?

I do. Thanks so much for responding. Every time I try with Odin, a few different releases, it always gives me the error message fail. Can it be done with flashfire?

What stands in the log of odin when the flash completes?

Ill have to do it again to see... Be back in a bit!

I think it says FAIL! modem but I'll have to run it again... Brb

Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.

ddjr said:
Last night I used flash fire to install firmware. That didn't get past the red Verizon logo, so I put twrp on it with Odin. Twrp showed it as dpd1, but it just wouldn't boot. So I wiped it once and flashed a ROM that requires mm firmware. Same thing, justbootloop. So I put stock back on it, then mokee 6.0.1. which works, I'm just not on mm firmware and all the great new roms are still unavailable to me.
Click to expand...
Click to collapse
Have you enabled the option to flash bootloader on flashfire setting?

What? No, I haven't... but do do right now. Thanks for the tip! Actually, where would I find it?

So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?

ddjr said:
So would I do it in this order? Flash the dpd1 bootloader, then modem, them rom, then jrkruse patch? All in flash fire?
Click to expand...
Click to collapse
It's in setting of flashfire...but only do it if odin doesn't work because do it from flashfire is more riskiy...
1)do a backup
2)check the bootloader flash option
3)install the firmware with all the wipe except internal storage(it mean that flashfire delete /data excluding /data/media/0 (sdcard) but include it in your backup copy because you never know )
4)wait till reboot skip setup wizard "spamming" the next button then install the rom with flashfire or twrp
On the flashfire site i found this:
Flash bootloaders
"This setting controls if FlashFire will attempt to flash bootloader partitions. By default, bootloader partitions are only read and never written. Even when enabled, flashing bootloader partitions may not succeed - many devices have protections in place against the bootloaders being overwritten.
Please note that flashing bootloaders is extremely dangerous. Any bug, error, or failure may result in an unrecoverable hard-brick. Do not use this feature unless you know exactly what you are doing.
Due to the danger of this feature, it is automatically turned off every time FlashFire starts. You have to manually re-enable it every time you want to use it.
If you must flash bootloaders, it is advised to use a bootloader-based flashing tool such as fastboot or ODIN to do it, as these are the safest methods. OTAs may also update bootloaders, and though slightly less safe than fastboot/ODIN, it is still much safer than having FlashFire flash bootloader partitions directly."
So i suggest to try to flash the firmware directly from odin first

No dice... still doesn't boot up past the red Verizon logo

ddjr said:
No dice... still doesn't boot up past the red Verizon logo
Click to expand...
Click to collapse
did you install the firmware in the "AP" box on odin? (after you factory reset your phone)

I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!

ddjr said:
I did. At this point guess I'm lucky I haven't bricked my phone. Ive tried every possible combination, nothing works!
Click to expand...
Click to collapse
Redownload the firmware extract it again,factory reset your phone,and try to install the firmware,maybe it's a bad download

Should I be flashing a kernel too? Will it even start/boot without the right kernel?

find out if you phone is refurbished. to install stock ROM you would need the main board and boot to be the same model.
if it's not, then you just need to install bootloader/modem without full ROM. look around in xda for bootloader/modem.

How to flash back and forth between Marshmallow and Lollipop? We need a clear guide.

I'll start off explaining my situation and then explain what myself and lots of other people seem to be confused about.
I was on Kikat last week and then upgraded to PB1 and unlocked my bootloader using method 1 by jkruse. Everything went fine and I was running stang5litre. I wanted to try Phoenix but I could not find instructions on how to get to PD1 first. I then saw that I could go right from PB1 to CM 13. I booted to recovery, wiped, installed CM and gApps, and everything went fine also.
I know my baseband is still PB1 but I'm guessing since I'm on CM now that I'm not actually on any official build right? (PD1, PF4, etc). So with that being said I don't understand how to go to other ROMs or back to LP.
I tried going back to recovery, wiping, and installing stang5litre again but my phone would not boot past the Samsung screen. Guessing something with the kernel? Soni flashed back to CM for now and I've been reading like crazy on here.
I'm trying to understand the process for switching between LP and MM. I found instructions by jkruse in the Phoenix forum (post #68) which talk about upgrading/downgrading bootloader but they are not clear and also they specifically say "Upgrade To PD1 Stock Rooted Rom With PD1 Unlocked Bootloader From 5.0 TW Rom". Well I'm not on a 5.0 TW ROM now.
I've seen countless posts in multiple forums showing a lot of other people are confused about this stuff. If I had all the details (clear instructions, file links, etc) I would glady make a very easy to follow guide and explanation of everything. I'm good at writing out stuff like that and making it very easy to understand.
Some things I want to understand so I can make a guide..
-How to go from PB1 to stock rooted PD1 (I see a guide to get to PF4 but Phoenix says you need PD1)
-How to go from CM to stock rooted PD1
-How to go from CM back to stock rooted PB1
-How to go from PD1/PF4 back to stock rooted PB1 (this process might be the same as the process coming from CM?
Any help/explanation would be greatly appreciated. Some of this info might be scattered across different forums but I think a guide specifically for switching between all the builds would be a huge help to a lot of people. Please link files also. I will definitely give credit to all who help if I do get the info needed to make it!! Thanks!

Bumppp

If you need help finding these things maybe you shouldn't be making a guide....

Sandman-007 said:
If you need help finding these things maybe you shouldn't be making a guide....
Click to expand...
Click to collapse
Please dont bother commenting pointless stuff. I read these forums every day and see lots of people looking for clarification for how to go back and forth between MM and LP. Mainly how to go back to LP. You will also find threads and posts with people giving different instructions. Some say just flash the PD1 rooted stock in recovery.. some say that won't downgrade the bootloader..

Some say to follow Jkruses guide in the second post of the bootloader unlock thread. The part about going back and forth between bootloader's.. which is a way more complicated method. There is different information all over

I highly suggest you read the 2nd portion "If You Already Have Bootloader Unlocked And On A Samsung TW Rom" link.
I think the key you need to understand is that you have to match the bootloader version with the corresponding ROM you are trying to flash. PB1 is for LP ROM. PD1/PF4 is for MM ROM.
Having above said, here's my answer to your question below:
-How to go from PB1 to stock rooted PD1 (I see a guide to get to PF4 but Phoenix says you need PD1)
Click to expand...
Click to collapse
Please follow the 2nd portion of the link above.
If you want to try Phoenix, then you can use the SafeStrap_PF4_Bootloader_Unlock_AIO.zip as jrkruse confirmed PF4 does work with it.
Upon complete the 2nd portion, then you can flash Phoenix's v12 ROM in TWRP directly.
-How to go from CM to stock rooted PD1
Click to expand...
Click to collapse
First of all, find out which CM you are at. I assume you are at CM13, then you would need follow the same 2nd portion instruction again (using the PD1 Bootloader), then flash the stock PD1 rom in twrp.
-How to go from CM back to stock rooted PB1
Click to expand...
Click to collapse
Same as above, except use PB1 bootloader in the process.
-How to go from PD1/PF4 back to stock rooted PB1 (this process might be the same as the process coming from CM?
Click to expand...
Click to collapse
You are right, it is the same process.
I hope I cleared it out for you. If you are not sure where you are at, then I would suggest you odin the original PB1 image, root it, unlock bootloader, flash twrp, then follow the 2nd portion of the link.

ruokuo said:
I highly suggest you read the 2nd portion "If You Already Have Bootloader Unlocked And On A Samsung TW Rom" link.
I think the key you need to understand is that you have to match the bootloader version with the corresponding ROM you are trying to flash. PB1 is for LP ROM. PD1/PF4 is for MM ROM.
Having above said, here's my answer to your question below:
-How to go from PB1 to stock rooted PD1 (I see a guide to get to PF4 but Phoenix says you need PD1)
Please follow the 2nd portion of the link above.
If you want to try Phoenix, then you can use the SafeStrap_PF4_Bootloader_Unlock_AIO.zip as jrkruse confirmed PF4 does work with it.
Upon complete the 2nd portion, then you can flash Phoenix's v12 ROM in TWRP directly.
-How to go from CM to stock rooted PD1
First of all, find out which CM you are at. I assume you are at CM13, then you would need follow the same 2nd portion instruction again (using the PD1 Bootloader), then flash the stock PD1 rom in twrp.
-How to go from CM back to stock rooted PB1
Same as above, except use PB1 bootloader in the process.
-How to go from PD1/PF4 back to stock rooted PB1 (this process might be the same as the process coming from CM?
You are right, it is the same process.
I hope I cleared it out for you. If you are not sure where you are at, then I would suggest you odin the original PB1 image, root it, unlock bootloader, flash twrp, then follow the 2nd portion of the link.
Click to expand...
Click to collapse
Thanks for the reply. I found instructions from Jkruse on page 7 in the Phoenix thread. That's why I am confused because there are so many methods scattered everywhere.
So here's what I tried and something went wrong already.
------------------------
Flashfire Method to Upgrade/Downgrade Your Bootloaders Dev Unlocked To Stock Roms
This Method Only Works If You Have A Dev Unlocked Bootloader Or Have Previously Unlocked Your Bootloader
I just want to add this warning. If you use this method you dont have the safety net that safestrap provides so if something goes wrong in this process you may end up with a unrooted phone and locked bootloaders causing you to have to start The whole rooting process over since you will not have safetrap to boot back into
Upgrade To PD1 Stock Rooted Rom With PD1 Unlocked Bootloader From 5.0 TW Rom With PB1 Unlocked Bootloaders
Download these 2 files and place on phone
PB1_Flashfire_Prepare.zip
PD1_Full_Firmware_With_Dev_Aboot_Twrp_Recovery_Ima ge.tar.zip
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
-------------------------
. I rebooted to TWRP. Flashed the PB1_Flashfire_Prepare.zip and rebooted right away. I now had safestrap installed which I did not before. So I go to open it up and my screen goes white for a second and then just returns to the app drawer?? It will not open
So then I delete the file and figured maybe it was a.bad download. Downloaded it again and tried to boot to recovery but it went to stock recovery not TWRP.
So I have no clue what to do now. How can I get TWRP installed again? All I did was flash that one zip so idk what went wrong. I am on PB1 everything.

aholeinthewor1d said:
Thanks for the reply. I found instructions from Jkruse on page 7 in the Phoenix thread. That's why I am confused because there are so many methods scattered everywhere.
So here's what I tried and something went wrong already.
------------------------
Flashfire Method to Upgrade/Downgrade Your Bootloaders Dev Unlocked To Stock Roms
This Method Only Works If You Have A Dev Unlocked Bootloader Or Have Previously Unlocked Your Bootloader
I just want to add this warning. If you use this method you dont have the safety net that safestrap provides so if something goes wrong in this process you may end up with a unrooted phone and locked bootloaders causing you to have to start The whole rooting process over since you will not have safetrap to boot back into
Upgrade To PD1 Stock Rooted Rom With PD1 Unlocked Bootloader From 5.0 TW Rom With PB1 Unlocked Bootloaders
Download these 2 files and place on phone
PB1_Flashfire_Prepare.zip
PD1_Full_Firmware_With_Dev_Aboot_Twrp_Recovery_Ima ge.tar.zip
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
-------------------------
. I rebooted to TWRP. Flashed the PB1_Flashfire_Prepare.zip and rebooted right away. I now had safestrap installed which I did not before. So I go to open it up and my screen goes white for a second and then just returns to the app drawer?? It will not open
So then I delete the file and figured maybe it was a.bad download. Downloaded it again and tried to boot to recovery but it went to stock recovery not TWRP.
So I have no clue what to do now. How can I get TWRP installed again? All I did was flash that one zip so idk what went wrong. I am on PB1 everything.
Click to expand...
Click to collapse
The SS/FF method was old instruction. People sometimes has hit or miss. I think Jkruse found out the cause (my guess is the binary status). Please go for the latest one, which is at the OP of the link I gave you.
If you still have the unlocked bootloader, you can always odin the twrp image (I recommend v3.0.0.0).
If you happened lost the unlocked bootloader status, then I would recommend you to odin the original PB1 tar, root, unlock bootloader, odin twrp, then follow the 2nd part of the OP.
I hope this helps.

Installing PF4 MM onto my OK3 5.0

This phone has been such a pain in the ass. My s4 was easy and my sprint s5 was cake to work with. This VZW s5 has been a royal headache.
Im living in a homeless shelter so I really dont wanna end up softbricked overnight before I can try to fix it at the library the next day.
Iam currently downloading a Deodexed/Debloted PF4 Rom for my VZW phone, got it on droidviews, PM me for the link it wont let me post it
So it looks like it has you use flashfire to install the rom and then has you Odin the proper Bootloader. Is this going to work for me?
When I was rooting the phone it had me messing with different kernals and stuff so I just wanted some clarification or something if anybody can provide some.
Thanks,
Raedon

I have both the Roms. The one for the unlocked bootloader and the locked one as well. Is there any easy way to see if my bootloader is unlocked?
Im pretty tech savvy but this **** is ridiculous.

Boot to download mode if you see a line that says developer mode you are bootloader unlocked
Sent from my SM-G900F using Tapatalk

In download mode it looks like my bootloader is locked. Is installing MM as simple as flashing the rom with flashfire and then flashing the new bootloader in odin?
Sounds like cake for real.

Yes you can install it in flash fire by having the firmware on your device then open flash fire app and click plus symbol in bottom right corner and choose flash firmware and choose the firmware let it check md5
then make sure inject su or root is off
Then click flash
You will lose root if you flash an official mm firmware and there is no way to root mm

Well I softbricked my phone and Im boned until tomorrow. I followed the instructions in the thread
"[How-To] Update to G900V_PF4 - 6.0.1"
It says at the top "**You can begin the following process from any Build/ROM but you must already have Root Access**"
You have to be rooted since it requires FlashFire. I downloaded the locked bootloader version since my bootloader is still locked. Followed all the directions and ended up stuck on the samsung screen. I have 40 minutes to try and fix this until Im stuck all night.
Im just gonna try to put the stock factory PB1 back on with the PB1 bootloader. Id love to get this 6.0.1 on my phone tomorrow tho

Boot to recovery and wipe data and cache
Sent from my SM-G900F using Tapatalk

What ROMs can I install using SafeStrap on a locked Verizon bootloader?

I have a Galaxy S5 (Verizon) SM-G900V that's running stock rooted Lollipop. Safestrap is on here, but yes, the bootloader is locked. Other than going to Marshmallow (and losing root), are there any custom ROMs (I'm looking for speed and stability) that this phone can take? Or am I stuck with stock, which means I'm stuck with Lollipop if I want to stay rooted?

My choice is this one without root for CID11 or full-featured systemless devbase for CID15.

Thank you. I assume I use safestrap to install on my rooted stock CID 11, but on this new one without root won't be able to restore apps from Titanium. Are there any other alternatives an 11 can use and keep root, and if I try one can but change my mind can I restore a backup in safestrap to get back to rooted stock?
bbsc said:
My choice is this one without root for CID11 or full-featured systemless devbase for CID15.
Click to expand...
Click to collapse

androidman807 said:
1) is that right that it's possible to safestrap a different ROM with my locked bootloader?
2) If yes, how can I tell which ROMs are stock I can use in safestrap (like Phoenixrom) and which are custom I can't use (like LineageOS)?
3) if I have a SS backup of my stock lollipop and don't like phoenix (which seems to be MM) can I restore from safestrap back to my stock LL? Or could I just re-install the stock LL image?
4) can I/should I update the modem in this process, or does the locked bootloader prevent that?
Click to expand...
Click to collapse
You'd better use a single thread for similar questions. There's a nice SM-G900V section too.
1. Yes.
2. You're limited to a stock signed Verizon-Samsung kernel, not to a stock ROM. You can (in theory) install any ROM that can use a stock signed Verizon-Samsung kernel but even a kernel from SM-G900F will not work.
LOS uses it's own kernel.
TWRP uses it's own kernel.
RR uses it's own kernel.
Root on 6.0.1 and above needs kernel modification.
These won't work.
If Phoenix can use a stock kernel (I don't know), it will work.
3. You may want to have a look at this thread: https://forum.xda-developers.com/verizon-galaxy-s5/help/getting-safestrap-loop-t3601977
I don't usually do it myself but it should be possible.
It's not an easy way and there are some logical traps on it.
So think it over before the action.
4. Locked bootloader does not prevent modem updating. It's definitely possible. You can simply flash a modem part of stock firmware in Odin.

Thanks. I've tried casting a broader net, unsure if my problem was Verizon-specific or not. Turns out, it's even more specific than that, as at least some 900Vs have unlocked bootloaders and some (mine) don't.
As I look back over my journey, you were there from the beginning when I was trying to upgrade from 4.4.2 to my current Lollipop and keeping root. Following the steps of the amazing @jrkruse led to different problems, which still persist. There seems no way to fix that, from which I conclude the jrkruse stock ROM and this phone don't get along. Hence, the idea to try a different ROM other than this LL. It seems that my locked bootloader has me on stuck on this particular stock ROM if I want to keep root. There is no list of other ROMs I can put on this CID11, and I'm not sophisticated enough to know which I can try and Safestrap back safely if things aren't wonderful. This has me doing a hot reboot every day or two when I see wifi can't get DNS, but I don't see any other option other than buying a newer Galaxy with a microSD card and an unlocked bootloader (maybe the S8?). Regardless, this sums up my journey, I've learned a lot along the way, and both you and @KazuDante were extremely helpful and earned my Thanks button many many times. Thanks again.
bbsc said:
You'd better use a single thread for similar questions. There's a nice SM-G900V section too.
1. Yes.
2. You're limited to a stock signed Verizon-Samsung kernel, not to a stock ROM. You can (in theory) install any ROM that can use a stock signed Verizon-Samsung kernel but even a kernel from SM-G900F will not work.
LOS uses it's own kernel.
TWRP uses it's own kernel.
RR uses it's own kernel.
Root on 6.0.1 and above needs kernel modification.
These won't work.
If Phoenix can use a stock kernel (I don't know), it will work.
3. You may want to have a look at this thread: https://forum.xda-developers.com/verizon-galaxy-s5/help/getting-safestrap-loop-t3601977
I don't usually do it myself but it should be possible.
It's not an easy way and there are some logical traps on it.
So think it over before the action.
4. Locked bootloader does not prevent modem updating. It's definitely possible. You can simply flash a modem part of stock firmware in Odin.
Click to expand...
Click to collapse

bbsc said:
4. Locked bootloader does not prevent modem updating. It's definitely possible. You can simply flash a modem part of stock firmware in Odin.
Click to expand...
Click to collapse
ps: I read the first ten pages of this thread about modems, but the first post strongly implies that they're not flashable with all the crossouts, which leaves with Odin, but if I'm reading it right one needs TWRP, which I don't have, only safestrap. If there's a different modem thread I should look at, or if should try the Odin ones, thanks for pointing me in the right direction. It seems I'm terrible at finding what I'm searching for in this info-rich site.

androidman807, which firmware (modem, kernel, bootloader) do you have and which do you want to have?
P.S. "Odin: (necessary for those with TWRP recovery)" means that a phone with TWRP has "Binary status: Custom" and there's no other way to update modem except Odin.

Baseband : PB1
Build : PB1
Kernel : 3.4.0
At this point I'll take any rooted firmware that is stable and not sluggish with this phone, with ability to at least get back to this if it's a step backwards.
bbsc said:
androidman807, which firmware (modem, kernel, bootloader) do you have and which do you want to have?
P.S. "Odin: (necessary for those with TWRP recovery)" means that a phone with TWRP has "Binary status: Custom" and there's no other way to update modem except Odin.
Click to expand...
Click to collapse

androidman807 said:
Baseband : PB1
Build : PB1
Kernel : 3.4.0
At this point I'll take any rooted firmware that is stable and not sluggish with this phone, with ability to at least get back to this if it's a step backwards.
Click to expand...
Click to collapse
I think, if you have network problems with this phone, it will be the best to backup your data and try a factory firmware with full factory reset.
If you're currently on BPB1 you can try any firmware above (and including) BOK3 and return back to BPB1 if you don't like it.
Firmwares BOK3 and BPB1 (your current) can be rooted after installation.
If I remember correctly, you need root to use Titanium backup app.
But you may want first try if the network problems persist on different stock firmwares.
I'd begin with the latest - DQI2.

Titanium is a big reason why I want to keep root. So BOK3 and DQI2 are ones I can root and still return to PB1. Thanks, I'll start looking for them and their rooting procedures.
bbsc said:
I think, if you have network problems with this phone, it will be the best to backup your data and try a factory firmware with full factory reset.
If you're currently on BPB1 you can try any firmware above (and including) BOK3 and return back to BPB1 if you don't like it.
Firmwares BOK3 and BPB1 (your current) can be rooted after installation.
If I remember correctly, you need root to use Titanium backup app.
But you may want first try if the network problems persist on different stock firmwares.
I'd begin with the latest - DQI2.
Click to expand...
Click to collapse

androidman807 said:
So BOK3 and DQI2 are ones I can root and still return to PB1.
Click to expand...
Click to collapse
No. I've written something different above.
You can flash BOK3 - DQI2 and return back after this. There're 14 firmwares.
But you can root only BOK3 and BPB1 from those 14 firmwares.
I advice you to flash DQI2 just to see if it solves network problems.

androidman807 said:
ps: I read the first ten pages of this thread about modems, but the first post strongly implies that they're not flashable with all the crossouts, which leaves with Odin, but if I'm reading it right one needs TWRP, which I don't have, only safestrap. If there's a different modem thread I should look at, or if should try the Odin ones, thanks for pointing me in the right direction. It seems I'm terrible at finding what I'm searching for in this info-rich site.
Click to expand...
Click to collapse
You can flash modems using odin even if you dont have twrp , they made it that way for those who are not on stock firmwareand that have twrp for example those who are on nougat , instead of flashing back stock and redoo the whole thing all over again , so in the vzw section there is a thread that has all the latest modems ( i think qh2) , just download qh2 ( i used the non-hlos for 4g) and in odin use ap and select the downloaded tar(modem) and flash , phone has to be in download mode.

Thank you. I was hot on the modem idea when I was going to switch to Lineage or something else as a natural step. But since it's tied to 4G and cell service and not my sporadic DNS-on-wifi issue, I'm not sure I see the benefit, but then I could be wrong. I figure a different ROM will have different drivers for the wifi radio and solve things. At least that's been my hope all along.
KazuDante said:
You can flash modems using odin even if you dont have twrp , they made it that way for those who are not on stock firmwareand that have twrp for example those who are on nougat , instead of flashing back stock and redoo the whole thing all over again , so in the vzw section there is a thread that has all the latest modems ( i think qh2) , just download qh2 ( i used the non-hlos for 4g) and in odin use ap and select the downloaded tar(modem) and flash , phone has to be in download mode.
Click to expand...
Click to collapse

Thank you! I will likely flash this with Odin over the weekend (or with SafeStrap?). I've found QI2 here, the first of the two links. Just to be prepared, what steps will I take to rooting this new ROM?
bbsc said:
I advice you to flash DQI2 just to see if it solves network problems.
Click to expand...
Click to collapse

Where can I find BOK3, and how do I root it after installation if I don't have TWRP (but only safestrap)?
Edit: here's OK3 with steps on how to root it, but they're quite scary and possibly outdated.
bbsc said:
I think, if you have network problems with this phone, it will be the best to backup your data and try a factory firmware with full factory reset.
If you're currently on BPB1 you can try any firmware above (and including) BOK3 and return back to BPB1 if you don't like it.
Firmwares BOK3 and BPB1 (your current) can be rooted after installation.
If I remember correctly, you need root to use Titanium backup app.
But you may want first try if the network problems persist on different stock firmwares.
I'd begin with the latest - DQI2.
Click to expand...
Click to collapse

Thanks again - I flashed with Odin the DQI2 I found but didn't know how to root it (Safestrap erased and no TWRP). Maybe the answer is the same as the other post I just replied to. That's obviously a blind spot I have that has me stuck on PB1 - I don't know how to root anything else on this CID 11.
bbsc said:
No. I've written something different above.
You can flash BOK3 - DQI2 and return back after this. There're 14 firmwares.
But you can root only BOK3 and BPB1 from those 14 firmwares.
I advice you to flash DQI2 just to see if it solves network problems.
Click to expand...
Click to collapse