Related
Help needed!
Tried to root my Sprint SPH-L720 MDL version (really need to be able to use it as HotSpot like I was using my previous phone) and having issues with getting root access as Sprint has added a SetUID restriction on the kernel with the latest update.
But most important, Good Enterprise stopped working as it detected that phone is rooted or partially rooted (as Titanium Backup gives me a message that it was able to acquire Root Privs – but its UI never opens up). Not having Good Enterprise is not an option for me.
So, decided to go back to Original as seen posts with instructions (these were key for me to move forward with rooting) that it is easy to do, however only know realized that all these ports are using MDC version of Firmware and I could not find Official Firmware for MDL version. Only MDC version available. Ouch!
Question #1: Anyone knows if MDL version of Original Firmware even exists and if yes where to download it? Or should I just use MDC version? Would it work?
If recovery is not available, I could pass this phone to one of my kids but I will need to fix root. To fix root I need to flash new MDL kernel using ODIN & CWM recovery. I have Fixed MDL Kernel, but I could not find instructions on how to flash it.
Question #2: Anyone could point me to the instructions on how to flash Kernel using ODIN and CWM Recovery?
Thank you In advance!
only way right now is to flash mdc and then take the ota.
for some reason Samsung has not released the mdl yet.
kernels you flash in recovery like a rom just read the install instruction in any kernel thread.
there is also an unroot script posted in dev you might try.
for rooting did you odin cf auto root? pretty hard not to root that way.
I usually do this for the Note 3 I have, and it comes in really useful for devs, those running other roms, etc, that just want to upgrade the modem/wifi, bootloader, and CSC without messing with everything else. It's also handy to replace the stock kernel if you need it for whatever reason (towelroot anyone? ). Since I recently picked up a Tab Pro 8.4 from swappa, I did this for mine to do the upgrade, and thought I'd be nice and go ahead and share the extracted parts for everyone else to enjoy.
Here's the MODEM+NON-HLOS (both together and as separate files), Bootloader, Kernel, CSC, and Recovery I extracted from the new T320 1NK1 Firmware. In desktop Odin 3.09, Kernel and recovery would go in AP. Modem + NON-HLOS goes in CP, Bootloader in BL. If you flash the bootloader separately, make sure to tick the box that says bootloader update.
Bootloader:
CSC: http://www.mediafire.com/download/dje1u61d8pk8dou
Kernel: http://www.mediafire.com/download/bi2jsdcub9c9k82
Modem + NON-HLOS (Combined): http://www.mediafire.com/download/3x5bela3la8mllh
modem.bin: http://www.mediafire.com/download/oatak8vgg5vdlu5
NON-HLOS.bin: http://www.mediafire.com/download/xuaar11efato1j7
Recovery: http://www.mediafire.com/download/206e1b2g1uact6s
Full Stock Image T320UEU1ANK1-T320XAR1ANK1: http://www.mediafire.com/download/ul9d01zlrq3dl72/T320UEU1ANK1_T320XAR1ANK1_HOME.tar.md5
If you have trouble getting the bootloader and/or Modem to stick, install "Triangle Away" by @Chainfire and follow the directions to reset your counter (even if it says zero), then boot into download mode, and re-flash them with Odin and they should stick (WARNING: Triangle Away WILL TRIP KNOX).
NOTE: It has also been noted by several people that booting directly into download mode from a powered-off device and flashing the BL/Modems will make them stick as well.
To verify, you can download "Phone Info - Samsung" and make sure that all applicable items say either T320UEU1ANK1 or T320XAR1ANK1 (Bootloader,, PDA and CSC). NOTE: Not all functions of this app work for our tablets, but most do.
Triangle Away by @Chainfire: https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway
Phone INFO ★Samsung★ by @vndnguyen: https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Mobile Odin Pro: https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
Enjoy, and as always, slap that Thanks button!
I'm planning on rooting and going back to an old Kernal. After rooting, I am going back to the NK1 kernal but I'm on T320UEU1ANK1. Can I go back to NK1 kernal using the T320XAR1ANK1 kernal you your post or do I have to find the T320UEU1ANK1? I know you have the full T320UEU1ANK1 image but I just to ODIN T320UEU1ANK1 kernal.
Thanks in advance.
Deca4 said:
I'm planning on rooting and going back to an old Kernal. After rooting, I am going back to the NK1 kernal but I'm on T320UEU1ANK1. Can I go back to NK1 kernal using the T320XAR1ANK1 kernal you your post or do I have to find the T320UEU1ANK1? I know you have the full T320UEU1ANK1 image but I just to ODIN T320UEU1ANK1 kernal.
Thanks in advance.
Click to expand...
Click to collapse
You can use the kernel in my post.
Sent from my leanKernel 3.16 powered stock 4.4.2 SM-N900T
Thank you!
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Just a question but I believe it does not affect root, if I were to install the modem/firmware I would not lose root correct? Also, if you were to flash the whole package, does towel root or manual root (think I used Hashcode script vs towel root) does the new firmware allow root access? I don't believe these devices are as locked down as a carrier device, but just wondering! When people refer to firmware and modem, what part is the firmware on this actually? I see the modem, but is firmware part of the NON-HLOS or what ?Thanks!
Edit: Seeing another thread, seems CF Auto-Root will still work, answering my above questions, thanks and sorry for not fully researching first!
bigmike35 said:
Just a question but I believe it does not affect root, if I were to install the modem/firmware I would not lose root correct? Also, if you were to flash the whole package, does towel root or manual root (think I used Hashcode script vs towel root) does the new firmware allow root access? I don't believe these devices are as locked down as a carrier device, but just wondering! When people refer to firmware and modem, what part is the firmware on this actually? I see the modem, but is firmware part of the NON-HLOS or what ?Thanks!
Edit: Seeing another thread, seems CF Auto-Root will still work, answering my above questions, thanks and sorry for not fully researching first!
Click to expand...
Click to collapse
My Tab Pro 8.4 (Wifi) shipped with the latest firmware already installed. I didn't want to use CF Auto-Root because it trips the Knox flag, so I flashed this kernel (http://forum.xda-developers.com/showthread.php?t=2786800) and then was able to use TowelRoot, which doesn't trip Knox.
Nice job. I upgraded using the full image, downgraded the kernel, rooted my T320, restored your kernel. Very simple and all worked great. Thanks for this.
@toastido Could you give me a link to Kernel BNI1 (Portuguese version) plz?
Thanks in advance.
Hello all.
I know some (maybe all) questions of mine have been answered somewhere, but I just couldn't find them in a concise list, so to say...so please be gentle if I am asking something that's already been answered somewhere.
Here goes:
I bought a second hand Samsung S5, G900F, with SEE firmware G900FXXU1BOH5, still one year in warranty (it was bought from Telenor Serbia, but I can see it is actually with SEE firmware, no operator bloatware, logos etc and sha256sums are equal for SEE and MSR LP firmwares, both taken from Sammobile).
Since it is a rather fresh LP build, as we all know there is no way to root it and keep warranty (knox will trip), unless you go way back to KK with ANE2 firmware (or earlier).
Now, there are 2 versions of instructions for doing that:
- just flash SEE firmware build ANE2, reboot, wipe, install towelroot
- flash SEE firmware build ANE2, use PIT file, reboot, wipe, install towelroot
First confusion is here: do I need to use PIT file? Did partition layout change and will official KK firmware do it on it's own or not?
If PIT file is required, at what moment I should use it? First PIT, then firmware or the other way around?
Also, are bootloader, kernel and CP files required for anything (I do have full official KK image for SEE, so I guess I don't need these files separately, but...)?
Do I need to flash bootloader at some point because KK has different bootloader than LP, or the full firmware will take care of that too?
Next set of questions regards going back to LP, which does not seem to be answered precisely:
if I downgrade to KK (using one of the procedures mentioned), and successfully install root and SuperSU, how do I upgrade back to LP?
- do I install latest LP firmware for SEE through Odin?
- or, do I activate OTA upgrade and let the phone upgrade/update itself back from KK to LP?
I am pretty sure that the first method will again destroy root access, but is the second method even viable now? Will OTA work or I'd need to go through KIES?
Finally, since I'm dealing with stock firmwares all along, knox should stay at 0x0, but what about status? Will it change at some point from official to custom (shouldn't, but than again...)?
If it is not possible to do what I need, the solution seems to be to go to custom LP rom that has been rooted already, and has knox deactivated etc etc. - is it really the only way?
If so, can you propose which ones will not change the status of the phone (knox, official/custom)? How about Galaxy project, that one seems pretty stock-ish to me...
Sorry again if asking wrong/already answered questions and thank you.
Cheers, Andrea
I'm not sure how/if the partition layout changes between KK and LP, so I can't say for certain that a pit file *is* needed.....
My advice would be to try to roll back to KK without using one.......
If the roll back doesn't work, then try with the pit file.......
Plan A......Odin flash KK firmware then recovery wipe, reboot and towelroot.....In that order.
Plan B......Odin flash pit, odin flash KK firmware then recovery wipe, reboot and towelroot.....again in that order.
The bootloader, kernel etc files are all contained in the firmware that you will have downloaded from Samsung-updates.com or sammobile.com so no need to source and flash them separately.
As for upgrading again and keeping root....
Odin won't do that with a regular firmware, OTA will probably fail and Kies....well, I've always tried to avoid using it.
Realistically, the only options you have for upgrading and keeping root, are one of two apps from Chainfire.......
Either Mobile Odin or Flashfire......Both of which inject root while flashing firmwares......as Flashfire is the 'successor' to Mobile Odin, the chances are that it'll have a better chance of success than the older Mobile Odin.
One last thing......The pit file......
If you *do* find that you need one, make sure you get the CORRECT one......
It's not going to do your device ANY good if you try to flash a 32gb pit onto a 16gb device.....There may be other differences with the available pit files too, so research them before flashing one......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
I'm not sure how/if the partition layout changes between KK and LP, so I can't say for certain that a pit file *is* needed.....
My advice would be to try to roll back to KK without using one.......
If the roll back doesn't work, then try with the pit file.......
Plan A......Odin flash KK firmware then recovery wipe, reboot and towelroot.....In that order.
Plan B......Odin flash pit, odin flash KK firmware then recovery wipe, reboot and towelroot.....again in that order.
The bootloader, kernel etc files are all contained in the firmware that you will have downloaded from Samsung-updates.com or sammobile.com so no need to source and flash them separately.
As for upgrading again and keeping root....
Odin won't do that with a regular firmware, OTA will probably fail and Kies....well, I've always tried to avoid using it.
Realistically, the only options you have for upgrading and keeping root, are one of two apps from Chainfire.......
Either Mobile Odin or Flashfire......Both of which inject root while flashing firmwares......as Flashfire is the 'successor' to Mobile Odin, the chances are that it'll have a better chance of success than the older Mobile Odin.
One last thing......The pit file......
If you *do* find that you need one, make sure you get the CORRECT one......
It's not going to do your device ANY good if you try to flash a 32gb pit onto a 16gb device.....There may be other differences with the available pit files too, so research them before flashing one......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
OK, your plans A and B for downgrade are more or less like I thought they should be...
But, on the subject of returning to LP after the rooting of KK with towelroot...regular firmware with Odin will erase everything and ofcourse kill su, like I said in my original post - but, why do you think OTA won't work?
If the downgrade does not change knox (stays 0x0) and status (stays Official) why would OTA upgrade fail? It changes some components, removes some and adds some new, why would it touch /xbin/su if OTA process does not know about its existance in the first place?
Kies should do the same like OTA (at least so they say) but I don't like it also, so I'd use it as a final resort.
Then we have Flashfire - I'm not quite clear how that works...would I be able to install latest LP over downgraded KK, and at the same time install supersu (from where?) during the installation of the original LP firmware? Because that's what I'm understanding from your post, that the process goes like that...
If not, what kind of firmware does Flashfire use? Custom ROM with su, disabled knox etc, simply allowing you to install it from the phone, or original firmware as well? What would be the procedure with it and would it change knox (shouldn't) or status from Official to Custom if I use it with original LP firmware to return from rooted KK to LP?
At last, the pit file - I could obtain only one for 16GB version that is not specifically marked as for some region or country, and I don't know if there is a pit file for 16GB SEE (South East Europe) G900F to be found. I tried searching but the best I could find was for BTU, which is for UK but seems to be usable for all of North Europe, everything else was much more specific.
Does somebody have/know where to find pit file that would be suitable for my device?
Again, thanks
I need to quantify anything i write by saying that the info i share, is (for me at least) untested.....i've done the research and reading so that i am familiar with the processes if i decide to put them to practical use in the future....right now, I'm happy to stay with my rooted, debloated, modified, stock KitKat setup......
That being said.......
You need to find a way to retain root through the *whole* downgrade/upgrade process......many people are finding it damn near impossible to root the latest LP firmwares.....so keeping root would be an advantage.......
I used towelroot on my phone, and it set the system status on my phone to custom, which is enough to potentially cause issues with OTA (I can't say for certain as I rooted my phone on 4.4.2 and disabled the OTA function so I don't have first hand experience with this).
Flashfire will flash regular firmwares as I said in my previous reply......part of this process is to install superSU, so you don't have to worry about that......
Here's the Chainfire Flashfire thread...
http://forum.xda-developers.com/showthread.php?p=59959596
The pit file........
If your device is the F variant with a 16gb user storage partition, then the BTU 16gb pit you mentioned should be ok.....
As I'm sure you know, the pit file doesn't install any part of the firmware or OS, all it does is to set the 'memory blocks' to their default sizes/quantities/ratios ready for an OS flash......so if your device is 16gb then a 16gb pit should work.....
If you are still unsure about it, there is a way to extract a pit file from your existing setup using commands in terminal emulator.....I read about it here on XDA so a quick search should lead you to the thread......
Edit......here's the link.....
http://forum.xda-developers.com/showthread.php?p=52329647
the title of the thread mentions efs and other stuff (no mention of pit) but the second or third post down explains how to backup your pit.......
Edit 2.....forget about that method.....
You need root access to do it.....and you won't have root access until after the point when you will (potentially) need the pit......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
I need to quantify anything i write by saying that the info i share, is (for me at least) untested.....i've done the research and reading so that i am familiar with the processes if i decide to put them to practical use in the future....right now, I'm happy to stay with my rooted, debloated, modified, stock KitKat setup......
That being said.......
You need to find a way to retain root through the *whole* downgrade/upgrade process......many people are finding it damn near impossible to root the latest LP firmwares.....so keeping root would be an advantage.......
I used towelroot on my phone, and it set the system status on my phone to custom, which is enough to potentially cause issues with OTA (I can't say for certain as I rooted my phone on 4.4.2 and disabled the OTA function so I don't have first hand experience with this).
Flashfire will flash regular firmwares as I said in my previous reply......part of this process is to install superSU, so you don't have to worry about that......
Here's the Chainfire Flashfire thread...
http://forum.xda-developers.com/showthread.php?p=59959596
The pit file........
If your device is the F variant with a 16gb user storage partition, then the BTU 16gb pit you mentioned should be ok.....
As I'm sure you know, the pit file doesn't install any part of the firmware or OS, all it does is to set the 'memory blocks' to their default sizes/quantities/ratios ready for an OS flash......so if your device is 16gb then a 16gb pit should work.....
If you are still unsure about it, there is a way to extract a pit file from your existing setup using commands in terminal emulator.....I read about it here on XDA so a quick search should lead you to the thread......
Edit......here's the link.....
http://forum.xda-developers.com/showthread.php?p=52329647
the title of the thread mentions efs and other stuff (no mention of pit) but the second or third post down explains how to backup your pit.......
Edit 2.....forget about that method.....
You need root access to do it.....and you won't have root access until after the point when you will (potentially) need the pit......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
OK, Flashfire part now confuses me...if I use that (already downloaded) only with LP firmware tarball, do I need to go back to KK to obtain root with towelroot or not?
I mean, if Flashfire will install SuperSU (which I already have installed, but not working obviously) during the flashing of full firmware tarball, why would I need to root before using Flashfire? Or it won't even work if you don't already have root...? Flashfire thread does not give specific requirements, although it makes sense that you need to have root before being able to use Flashfire...
Secondly, I thought that using towelroot will not change the status of the device in any way - no custom status, no knox=0x1? Now, you say that it did change your status to custom...do you think that if that happened to me, flashing original LP firmware tarball through Flashfire would return status to official?
Ah, so many questing that link to each other...and just when you think you've got one answer, it generates another question...
You are correct, you can't use Flashfire unless you already have root.
And Flashfire will only return the device status to official if you don't get it to root the firmware as it flashes it.....
Basically, any modifications made to the original firmware have the potential to set the status to custom.......and in some cases, trip knox.....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
You are correct, you can't use Flashfire unless you already have root.
And Flashfire will only return the device status to official if you don't get it to root the firmware as it flashes it.....
Basically, any modifications made to the original firmware have the potential to set the status to custom.......and in some cases, trip knox.....
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
Hm, I've seen couple of solutions to that official/custom problem, although for Note3...basically, it's cache/dalvik clean, and deinstalling and reinstalling some app that uses root therefore triggering something that changes status to custom.
Which app that would be - it's a guessing game. Sometimes it's Titanium backup, might be Root explorer, Battery Monitor Widget...usually, reinstalling it fixes the problem.
But, now there is a second problem here - it seems that you need to have customized LP firmware to keep root using Flashfire...
http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044
and
http://forum.xda-developers.com/galaxy-s5/development/rom-ane4-kitkat-4-4-2-multi-csc-t2813628
Do you think this is true and stock LP rom can't be flashed with Flashfire, getting rooted along the way?
There is an xposed module which will trick the phone into displaying 'official' rather than 'custom' though how deep into the OS this mod goes, I don't know.....
It *may* be enough to restore OTA functionality, but OTA isn't your 'best solution' anyway.......
It was always (and still is) my understanding, that Flashfire was/is able to flash regular 5.0 firmwares and 'inject' them with root......
But as I said, having not actually used it, I'm the first to admit, I'm probably not the best (most informed) person to answer your questions......My advice would be to visit the Flashfire thread and ask there.....You'll get answers from people who have actually used it
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
I guess you've got your answer then.....
1) Download the lollipop firmware and extract the bootloader and modem....
2) Rollback the device (with or without pit depending on what works) to KitKat.
3) Do the necessary wipes.
4) Reboot and towelroot.
5) Install Flashfire and use to flash and root Lollipop firmware.
6) Do not attempt to boot phone normally as the flash won't be complete.
Instead, 7) boot to download mode and Odin flash the previously extracted bootloader and modem....
8) (Might be necessary at this point to perform recovery wipes of cache and data)
9) Finally, reboot as normal.
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
keithross39 said:
I guess you've got your answer then.....
1) Download the lollipop firmware and extract the bootloader and modem....
2) Rollback the device (with or without pit depending on what works) to KitKat.
3) Do the necessary wipes.
4) Reboot and towelroot.
5) Install Flashfire and use to flash and root Lollipop firmware.
6) Do not attempt to boot phone normally as the flash won't be complete.
Instead, 7) boot to download mode and Odin flash the previously extracted bootloader and modem....
8) (Might be necessary at this point to perform recovery wipes of cache and data)
9) Finally, reboot as normal.
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Click to expand...
Click to collapse
Thank you, I've seen your other post in Flashfire section and already replied to the one you refer to, but just to be sure, let's ask here too:
how to extract BL and modem from original LP tar.md5 file, because that's all I have?
Cheers.
This thread explains how to do it.....
http://forum.xda-developers.com/showthread.php?t=2864264
It's been written with the S3 in mind but I should think the procedure is exactly the same for the S5.
The thread mentions winRAR or similar as the extraction tool and goes on to say that it's 'paid' software.......as a free alternative, I've always used 7 zip and have never had any problems with it......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F
Winrar has a 30 day trial, and still works fine once that has expired, but gives a nag screen popup when you use it
I use both Winrar & 7zip
Yep, just seen it, reading now...actually, it was also mentioned in a reply to my post in Flashfire thread, so I have to try what's written in this howto and see how it goes...
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
OK Got my prior issue sorted out and got the tablet back up and running with the original Firmware.
I have the bootloader unlocked, but not able to gain root. Want to remove a lot of bloat and need root based Ad Blocker.
Tried the root method that was posted but it wont boot with patched boot.img flashed in Odin, I suspect it is due to it being Android 13 and the release that came out earlier this month.
Can't seam to get the original firmware to flash completely either with Odin either.
Any know ways that work with current Software?
Thanks for input