Database Users

[Q] LTE capability on Nexus 4 after Android (stock) update?

Hi there,
Happy owner of a Nexus 4 runing stock ROM with Android ver. 4.4.4, I rooted it few days ago with Towelroot app and unlocked the bootloader (with BootUnlock app) in order to enable the LTE fonction. I dit it with LTE Nexus 4 Modem Flasher app and it works well (my mobile carrier uses AWE for 4G). The custom recovery TWRP has been installed by the app prior to allow the flash of the modem driver/firmware. Now I am wondering about the coming update Lollipop which I really want to get.
As I could read in the forum, even if the system offers me the OTA update option, I should decline it since my custom recovery has been changed. Am I right? I have a doubt because I also read that people successfully updated OTA their rooted Nexus 4 even before Towelroot was existing and I guess this imply that they necessary changed their revovery...
As you may understand, I'm a bit newbie, I just rooted my phone and unlocked the bootloader without using the toolkit, and ideally I would avoid to do so.
My main concern is the following: updating to Android 5 (stock ROM either fron OTA or the tool kit), will I lose the benefit of LTE, or in other words, will the update change the modem firmware/driver?
Nota Bene: I don't really care about loosing the root privilege but I want to keep the LTE capability.
Thanks,
Guillaume.

guigzmtl said:
Hi there,
Happy owner of a Nexus 4 runing stock ROM with Android ver. 4.4.4, I rooted it few days ago with Towelroot app and unlocked the bootloader (with BootUnlock app) in order to enable the LTE fonction. I dit it with LTE Nexus 4 Modem Flasher app and it works well (my mobile carrier uses AWE for 4G). The custom recovery TWRP has been installed by the app prior to allow the flash of the modem driver/firmware. Now I am wondering about the coming update Lollipop which I really want to get.
As I could read in the forum, even if the system offers me the OTA update option, I should decline it since my custom recovery has been changed. Am I right? I have a doubt because I also read that people successfully updated OTA their rooted Nexus 4 even before Towelroot was existing and I guess this imply that they necessary changed their revovery...
As you may understand, I'm a bit newbie, I just rooted my phone and unlocked the bootloader without using the toolkit, and ideally I would avoid to do so.
My main concern is the following: updating to Android 5 (stock ROM either fron OTA or the tool kit), will I lose the benefit of LTE, or in other words, will the update change the modem firmware/driver?
Nota Bene: I don't really care about loosing the root privilege but I want to keep the LTE capability.
Thanks,
Guillaume.
Click to expand...
Click to collapse
I honestly can't speak for OTAs, as I've never done one on my Nexus 4. When I got mine, it already had 4.4.4, and I've been using custom ROMs since, and never back to stock.
But I can tell you that the radio survives ROM flashes, so I suspect it'll survive flashing the official 5.0 Lollypop ROM. You don't need to do an OTA to upgrade stock ROMs, you can flash them from recovery. You just have to wait until Google makes it publicly available and someone makes the flashable zip, or you can do it with your computer and ADB. I won't go through the steps here, since we haven't gotten there yet.
Regardless, even if it's not immediately, you will be able to update to 5.0 and have LTE, but wait on accepting an OTA or flashing until it's clear exactly how it'll all work.
---------- Post added at 11:50 PM ---------- Previous post was at 11:46 PM ----------
It occurs to me that people have been using the ported L preview on their Nexus 4s for a few months now. I haven't tried it, but maybe one that has could help you better. I'd search, but the L preview thread has 16000+ posts in it, and I'm just not that interested enough to try (I'm probably sticking with KK if/when Xposed works with ART).

OTA's often replace the modems, and since it can replace the entire /system directory it could potentially disable LTE enabler as well. And flashing stock images will replace your modems, and everything else in the phone like recovery, with the stock ones.
If LTE is really important to you, stay with what your using and do not OTA... wait until the new Lollipop radios are modified as a hybrid, then flash the stock Lollipop ROM, flash the radios and enabler, and you should be good to go. This is assuming they don't do something to break the OS so that hybrid radios are not possible.
Also, since you are on custom recovery, NEVER take an OTA... EVER... it will soft brick your device (it will be recoverable, just takes some work).
Personally, I was LTE for a while, and it was very hit and miss... would often drop to 3G and not go back to LTE unless I toggled in/out of airplane mode, and it destroyed my battery, cut my screen time in half. When I was on LTE my average screen time was 1.5-2.0 hours and I could not make it through a 16 hour day on a single charge, now that I removed them and want back to the stock 3G 1.03 radios, I get 3.0-3.5 hours screen time over 16 hours and it makes it though a full day, usually without a bump charge.

[Q] Some fairly Noob Clarifications (TWRP/CWM/MDL Related)

Purchased my S4 at launch, only rooted it and never really got around to tweaking it much. It has slowed down a bit so now is the time.
I'm on MDL, stock 4.2.2, and rooted with TWRP 2.5.0.2 On to the questions/clarifications, hopefully these aren't egregious. I know the info is out there but for actually finding specific information, the xda forums are a bit overwhelming and sometimes conflicting...
1) Recovery - Latest/preferred recovery for the s4 (on MDL) with auto-loki baked in? Are any of the latest versions of TWRP/CWM dangerous/incompatible or can I just install the latest/greatest with ROM Installers and go from there?
2) Modem - Flashing an updated modem, regardless of ROM/OS # should not break anything and/or lock down the bootloader any more so than it already is at MDL, correct? Updating the baseband will have no effect on the build # and thus loki is still and option (versus safestrap)? Preferred modem at this time? (ATT, SF Bay Area)
3) ROMS - Any ROM, followed by loki patch or flashed via an auto-loki capable recovery should be fine, correct? Is a ROM specifically built for safestrap applications and thus would not work with MDL, or are ROMs noted as being safestrap ready just able to be used via safestrap, but loki as well?
4) Hard to keep track of all the ROMs and the builds and branches etc - Can anyone point me in the right direction of either a) the latest stock touch-wiz 4.4.4 ROM that can be flashed over MDL without essentially updating past MDL? b) the best/most recent pure google (Play Store S4 Edition) ROM, same story with not breaking MDL?
Again, I apologize I am sure the info is all buried in here somewhere, it just gets to a point where pointed questions rather than multiple 500+ post threads are hopefully less likely to brick my phone. Ideally I just want to get on the latest software (and enable screen casting, for one). Assuming it comes quick enough, once I get this process down I will probably make the jump to 5.0 when it is ready, anticipate a couple months? Who knows.
Thanks, much appreciated.

Norcalz71 said:
Purchased my S4 at launch, only rooted it and never really got around to tweaking it much. It has slowed down a bit so now is the time.
I'm on MDL, stock 4.2.2, and rooted with TWRP 2.5.0.2 On to the questions/clarifications, hopefully these aren't egregious. I know the info is out there but for actually finding specific information, the xda forums are a bit overwhelming and sometimes conflicting...
1) Recovery - Latest/preferred recovery for the s4 (on MDL) with auto-loki baked in? Are any of the latest versions of TWRP/CWM dangerous/incompatible or can I just install the latest/greatest with ROM Installers and go from there?
2) Modem - Flashing an updated modem, regardless of ROM/OS # should not break anything and/or lock down the bootloader any more so than it already is at MDL, correct? Updating the baseband will have no effect on the build # and thus loki is still and option (versus safestrap)? Preferred modem at this time? (ATT, SF Bay Area)
3) ROMS - Any ROM, followed by loki patch or flashed via an auto-loki capable recovery should be fine, correct? Is a ROM specifically built for safestrap applications and thus would not work with MDL, or are ROMs noted as being safestrap ready just able to be used via safestrap, but loki as well?
4) Hard to keep track of all the ROMs and the builds and branches etc - Can anyone point me in the right direction of either a) the latest stock touch-wiz 4.4.4 ROM that can be flashed over MDL without essentially updating past MDL? b) the best/most recent pure google (Play Store S4 Edition) ROM, same story with not breaking MDL?
Again, I apologize I am sure the info is all buried in here somewhere, it just gets to a point where pointed questions rather than multiple 500+ post threads are hopefully less likely to brick my phone. Ideally I just want to get on the latest software (and enable screen casting, for one). Assuming it comes quick enough, once I get this process down I will probably make the jump to 5.0 when it is ready, anticipate a couple months? Who knows.
Thanks, much appreciated.
Click to expand...
Click to collapse
I will try to help with a few of these questions, but others I am not familiar with very much. On that note DO NOT update your bootloader!!! It will be locked down further and Loki will NOT WORK. And you could NOT flash any kernels with safestrap. So with safestrap ONLY the stock kernel can be used. Now on to your questions...
1) I am using TWRP 8.1 if I remember correctly. You can find it in the Original Android Development section. It does NOT Auto Loki, so keep the loki-doki flashable zip on your sdcard OR use Roms that already have/use the boot.Loki kernels like ShoStock-i 8.1
2) Modem flashing will NOT lock anything up further as far as the bootloader. You can flash ANY or ALL of them from my modem thread. See which works BEST FOR YOU in YOUR AREA. I am in So Cal and the best for me has been either MDL. But I have and do test ALL of them. You can always flash back to whichever one works best for you.
3.) Like I said I use ShoStock-i 8.1 because it has and does EVERYTHING I need my phone to do and does it without any issues. I have NOT tried to use a Safestrap modified ROM so I have very little experience with that. Normally most devs will have two separate versions, one for safestrap compatible and one for us without safestrap. ShoStock-i is already built with Loki in the kernel so you do not NEED to flash Loki-Doki patch.
4) there are NO Touchwiz 4.4.4 Stock Roms for ATT yet. But I did try out one of the Touchwiz 4.4.4 T-Mobile based Roms and it worked perfectly. You can either get it from the ATT forums and I believe it is already lokified, or get it from the T-Mobile forum and make sure to flash Loki-Doki patch before booting up phone after flashing the ROM. Again the will NOT update your bootloader past your MDL bootloader, so you are good as you are with no worries. By the way on ShoStock-i 8.1 the screen casting to Chromecast works PERFECTLY without having to flash any other .apk's or mess with ANYTHING

This is the exact same boat I'm in. Trying to track down the answers as well. Will keep an eye here as well to watch for answers.

awesome reply thanks RockRatt, that just about covers it. I will maybe give the ShoStock ROM a go and see how I like it. As long as all the normal features are working fine, I should be good.
One last thing I forgot - Odin. I have the stock odin firmware files from when my phone was new (The MDL package). As long as I dont update the bootloader, I should be able to Odin back to the brand new in box state should something go awry or not dig the other ROMs, correct?
Thanks again,

Norcalz71 said:
awesome reply thanks RockRatt, that just about covers it. I will maybe give the ShoStock ROM a go and see how I like it. As long as all the normal features are working fine, I should be good.
One last thing I forgot - Odin. I have the stock odin firmware files from when my phone was new (The MDL package). As long as I dont update the bootloader, I should be able to Odin back to the brand new in box state should something go awry or not dig the other ROMs, correct?
Thanks again,
Click to expand...
Click to collapse
Yep. Just don't update the bootloader...So no flashing newer firmware that contains the bootloader files. Most if not all custom Roms do not have the bootloader files in them. So no problem flashing back to MDL stock if the need never arises. I still in fact have the original MDB bootloader installed that came with the phone before the MDL firmware update.

[Q] Koodo S4 upgrade questions

Hello Gurus,
I have the Canadian S4 (I337MVLUFNI2) running stock 4.4.2. I've just downloaded the Lollipop upgrade from Koodo but did not install.
I'm looking to root and flash CM12 or other ROMs, but I'd like to try Lollipop first.
Few questions about the upgrade:
-Will I be able to root the device after upgrading to Lollipop?
-If I don't like Lolipop, can I revert to my 4.2.2 using my Kies back up ?
-If I want to be able to evert, do you recommend that I root my 4.4.2 and take a nandroid back up first ?
(Battery life is important for me. If the upgrade turns out to be disastrous as some online reports indicates, I'd like to be able to go back to 4.2.2).
-What is the recommended way to root and install recovery for my device ?
Thanks to all..

Do what I did.
Backup all files to PC
Flash lollipop firmware through Odin which you can download from sammobile
Reboot into recovery and wipe data and cache(this will erase everything on phone)
Boot up phone and setup accounts
Then once finished flash this through odin http://forum.xda-developers.com/showthread.php?t=2293800
Flash twrp through odin
Boot up and copy files back to phone
Reboot into recovery and flash cm12 or whatever you want

So far, there is not a root method for Lollipop on the S4, nor does Xposed work for it yet (lots of issues with the way Samsung implemented ART to Touchwiz).
There is a keep root method in the S4 general Forum, which is just a way to keep root throughout the install of lollipop if you are already rooted on the current ROM you're upgrading from. I'm on my phone though so apologies for not linking it.
I'm not certain if a kies backup will restore after the upgrade, but even though the keep root method removes safestrap functionality, there is a way to get it working temporarily, which may provide some hope.
Seeing as you're using a Canadian model I don't think you need safestrap, and seeing as I do (AT&T model), I can't tell you how other recoveries will handle the situation.

DankHeals said:
So far, there is not a root method for Lollipop on the S4, nor does Xposed work for it yet (lots of issues with the way Samsung implemented ART to Touchwiz).
There is a keep root method in the S4 general Forum. I'm on my phone though so apologies for not linking it.
I'm not certain if a kids backup will restore after the upgrade, but even though the keep root method removes safestrap functionality, there is a way to get it working temporarily, which may provide some hope.
Seeing as you're using a Canadian model I don't think you need safestrap, and seeing as I do (AT&T model), I can't tell you how other recoveries will handle the situation.
Click to expand...
Click to collapse
Actually http://forum.xda-developers.com/showthread.php?t=2293800 worked for me to root stock lollipop on my Bell s4

Zehlek said:
Actually http://forum.xda-developers.com/showthread.php?t=2293800 worked for me to root stock lollipop on my Bell s4
Click to expand...
Click to collapse
Ah, didn't realize the Canadian model had a root method yet. I'm in america on AT&T and our bootloaders are locked.

Zehlek said:
Actually http://forum.xda-developers.com/showthread.php?t=2293800 worked for me to root stock lollipop on my Bell s4
Click to expand...
Click to collapse
Hey Zehlek, I'm coming from CM11 (details below). I'm trying to move to CM12 because CM11 is doing strange things with my GPS. Which version would you recommend that is stable for the SGH-I337M? I read the CM12 dev page, but I'm a little nervous about the whole "editing scripts" part of the process.
Current Software -
SGH-I337M
CWM v6.0.5.1
CM v11-20141112-snapshot-m12-jflte

L720 Upgrading Modem and Android to Unlock Features

Current device:
L720, rooted android 4.2.2, baseband MF9, kernel kt-sgs4-08-09-2013, rom Negalite-WondeROM-r52.
What's up guys, I am just looking to upgrade to a newer android version and newer rom. When I've tried to update, I either usually lose data coverage or lose the ability to use the dialer. So my question is what kernel, modem, and rom version do I need to install to have access to the following features? -
Mostly, I just want to have my hotspot toggle on the pulldown menu (SQL editing hasn't worked for me), obviously native hotspot enabled, sound boosting mod, and to use emojis without installing an app that logs every key entry. I would also like to stay away from KNOX (even though I still don't fully understand what it does to the phones after being tripped?)
Do I need to unroot, let the updates come through OTA, then re-root and find a new rom for the android version?
Or do I do something like flash each android version by version until I'm all updated?
I've rooted and customized multiple phones with the help of xda, this is just the first time I haven't been able to solve my problem after many many tries at flashing. I am good with recovery, flashing, and odin, but I still don't totally understand differences in kernels, modems, and basebands.

I'd love a little help here too. Similar issues but on mf9 baseband and mk2 firmware, running SACs 4.3. I think twrp 2.6.3.
I'd love to know what I need to do to get my firmware updated and a working ROM installed. Please and thanks.

yall need to odin to at least the oldest version of the Android version you wish to move to. but first, you should know that the MF9 bootloader is a special one. it is one of the last Sprint bootloaders ever to not have a Knox trip.
this opens some opportunities for you -- upon updating via Odin, your phone would become a fresh knox 0x0 with valid warrantee (until your next root or TWRP) and also you could downgrade to the very first rom for the s4. I can't remember the fine details but I think it (MDC) was the only s4 rom that permitted some kind of CDMA editing or APN stuff. if interested you'll have to dig for whatever the perk was
if you want to update to jellybean 4.3, you'll need MJA* or MK2
*first bootloader on s4 both to prevent downgrading and include knox
for kitkat, odin NAE* or NG2**
*might permit downgrade to MK2
**notice! this is the final kitkat version! upgrading past here makes acquiring your MSL more difficult, so be sure to grab that first from any version NG2 or older and write it down. also, last s4 rom to (easily) UUIC unlock. it will stay unlocked
if you want lollipop 5.0.1 you'll need OD2* OH1** or OK3
*does not allow downgrade!
**some of the custom ROMs will require this version or newer.
I don't know if the s4 is one of them, but on some Sprint devices the APN settings are only (easily) accessible from roms with the XAS product code. factory default is SPR. you can change this with GalaxyTools (requires factory reset) or just odin the XAS version (might factory reset).
I know I might have created more questions than answered ...xda search & Google search are your best friends
edit: you can change your recovery to whatever you like, the only trick here is older recoveries don't like installing lollipop / marshmallow(CM13) ROMs -- I think TWRP 2.8 was the minimum? either way, just shoot straight for 3.0.2 there's nothing to lose.

Update Rooted Kit Kat ANI2

Ok, I bought a new Verizon S5 in July of 2015. I rooted it a couple days later using Towelroot. The CID is 11, so it has a locked bootloader. I never had a single issue with the phone, and honestly, never thought about doing any updates, as it just kept chugging along dependable every day. I recently retired the S5, as I bought a mint, used Note 4 and fell in love with it. I am getting ready to sell the S5, but want to fully update it to 6.0.1 Marshmallow DQH2. I am not worried about losing root, as I am selling the phone, and will probably remove root anyway. I have a few questions though:
1) Can I update from Kit Kat all the way to Marshmallow and the latest update, or do I have to do it in increments?
2) Is it easier to update, then remove root?
3) What would be the easiest way to update to DQH2?
4) Since its rooted, can I just download the stock DQH2 firmware and flash it in Odin and go from KK to MM?
4A) If it can be flashed as stated above, will I lose root?
4A-1) Is there a rooted DQH2 firmware that can be flashed?
Thanks in Advance!!!

0) Check if Reactivation Lock is turned OFF.
...
4) Flash this DQH2 and it will erase everything, including root.
4A) Yes.
4A-1) No.
Forget the rest of the questions.
P.S. The first boot after flashing will take 10-15 min. so be patient.

bbsc said:
0) Check if Reactivation Lock is turned OFF.
...
4) Flash this DQH2 and it will erase everything, including root.
4A) Yes.
4A-1) No.
Forget the rest of the questions.
P.S. The first boot after flashing will take 10-15 min. so be patient.
Click to expand...
Click to collapse
Thanks. Whats the highest I can update, and retain root? I am re-thinking things now, as the package disabler app I was using and very fond of.... has been updated, and evidently does not work like it used to. I used this app on my Note 4, and was so happy with being able to disable all the bloatware and OTA etc... that I didnt bother to root the Note 4. I thought that if I lost root upgrading the S5, I would just install the same package disabler app, so it wouldnt be a problem, as thats really the only reason I root.... to get rid of bloatware. I may want to keep root now though

widowmaker17 said:
Whats the highest I can update, and retain root?
Click to expand...
Click to collapse
BPB1, Android 5.0.
You may also like the idea to install a custom debloated 6.0.1 ROM without root. If you've decided not to sell the S5.

Just another viewpoint if you haven't updated the phone yet: there are buyers who look primarily for phones with earlier versions of android, and it could actually increase the value/selling chance of your phone if you keep it on an earlier version and advertise it as such.
This gives the purchaser the opportunity to install the version they might want, especially since it's relatively difficult to find a Verizon S5 (or any Verizon Samsung phone) with 1. an unlocked bootloader and 2. an earlier version of Android such as KitKat installed.
I know this doesn't necessarily answer your questions, but it might be of benefit.