Related
My phone downloaded an OTA and keeps bugging me to install it, which I actually want to do. Trouble is, when it reboots it goes into the recovery menu where I installed my root from. It asks where I want to install the update from. Can I point this to where the OTA was downloaded? If so, where is that? Otherwise, how can I get this update installed so it will stop bugging me?
I rooted but kept everything stock so I thought I can use the OTA updates....
sponge14 said:
My phone downloaded an OTA and keeps bugging me to install it, which I actually want to do. Trouble is, when it reboots it goes into the recovery menu where I installed my root from. It asks where I want to install the update from. Can I point this to where the OTA was downloaded? If so, where is that? Otherwise, how can I get this update installed so it will stop bugging me?
I rooted but kept everything stock so I thought I can use the OTA updates....
Click to expand...
Click to collapse
The short answer is yes you can accept OTA Updates while rooted, I know this because I have accepted 3 different OTA's on my GS3 while being rooted. However you can never accept an OTA when you have a custom recovery. Anytime you want to accept an OTA you need to hop on over to Odin, and flash the stock recovery, otherwise the OTA will fail.
Head on over here http://www.epiccm.org/2012/06/sprint-sgs3-stock-restore.html
and read up on how to restore your stock recovery, this will allow you to accept the OTA, and then just reroot.
US Cellular
I'm on US Cellular and rooted. I installed TWRP and the phone won't install the update from it, if it helps anyone, this is what TWRP is showing.
Installing update...
assert failed: getprop("ro.product.device") == "d2usc" ||
getprop("ro.build.product") == "d2usc"
E:Error in /cache/fota/update.zip
(Status 7)
Installation aborted.
Install with custom recovery and before u reboot just flash the team root zip file that work for sprint galaxy s 3 hope this helps
Sent from my SPH-L710 using xda premium
luisortega17 said:
I'm on US Cellular and rooted. I installed TWRP and the phone won't install the update from it, if it helps anyone, this is what TWRP is showing.
Installing update...
assert failed: getprop("ro.product.device") == "d2usc" ||
getprop("ro.build.product") == "d2usc"
E:Error in /cache/fota/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Again as mentioned in my post above yours, if you are trying to install an OTA update, you cannot do so with a custom recovery, you must be on a stock recovery to install an OTA update. Custom recoveries are only for custom flashes. So as a rule, Custom installs Custom, Stock installs Stock.
Apparently I can not do this because I have to use my company's email on my phone. When I added the account it for some unknown reason had to encrypt the phone's internal memory, so when I try to use the bootloader to run that program, it can not see the phone's internal storage.....
So my question now is, is there a file I can delete or something I can do to make the message stop popping up that there is an update ready to install?
sponge14 said:
Apparently I can not do this because I have to use my company's email on my phone. When I added the account it for some unknown reason had to encrypt the phone's internal memory, so when I try to use the bootloader to run that program, it can not see the phone's internal storage.....
So my question now is, is there a file I can delete or something I can do to make the message stop popping up that there is an update ready to install?
Click to expand...
Click to collapse
Make a backup and take a look here http://forum.xda-developers.com/showthread.php?t=1829706
ETA: Don't you have a password set to decrypt it? My company email doesn't do that so confused as to how that worked.
Foreverme89 said:
Make a backup and take a look here http://forum.xda-developers.com/showthread.php?t=1829706
ETA: Don't you have a password set to decrypt it? My company email doesn't do that so confused as to how that worked.
Click to expand...
Click to collapse
It does ask for the password, however, the password is not asked for until after the bootloader would appear.
sponge14 said:
It does ask for the password, however, the password is not asked for until after the bootloader would appear.
Click to expand...
Click to collapse
Also, I'm not seeing a System folder when I hook the USB up to the PC and try to browse it there...
sponge14 said:
Also, I'm not seeing a System folder when I hook the USB up to the PC and try to browse it there...
Click to expand...
Click to collapse
I can't see the system folder on the computer. Either in astro or ES file emplorer, if you go to the root of the phone it should show.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SPH-L710 using xda premium
Last attempt before I report the phone stolen and get a new handset.
In need of help and getting frustrated by the forum software:
I get this:
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
When trying to add this reply:
I used the root method as published on Jul 2, 2012 by qbking77 on youtube (How to Root the Sprint / AT&T / T-Mobile Samsung Galaxy S III)
Am I using a stock recovery?
To this post:
http://forum.xda-developers.com/newreply.php?do=newreply&p=30346020
Despite the fact that I am NOT posting any links, outside or not (whatever outside may mean.)
EDIT:
It worked! I posted!
Apparently the problem with posting stems from quoting other users, even if I have no links.
That's really messed up when one needs to quote to reply and you happen to be new. Your forum software is not kind to new users who lack the patience to try to post upwards of 10x (like myself.)
EDIT CONTINUED:
Now I can't save my edit
"To prevent spam to the forums, new users must wait five minutes between posts. All new user accounts will be verified by moderators before this restriction is removed."
I have a question i currently have my sprint galaxy s3 flashed to Metro pcs which is also rooted, and the ota keeps popping up. I would like to install the ota but it keeps failing. Can i flash back to the stock like mentioned in the previous post and not lose my metro pcs flash because i would hate to pay for the flash again. Thanks
I am not entirely sure what all goes into flashing to another carrier although I do believe the flash to metro would stay intact. Having said that, rather than downgrading it and trying to accept an ota I would first do a nandroid backup and flash the latest build using odin or custom recovery
NOTE: If anyone has any further questions about bootloaders on the S3, please note that I have moved on to another device. Sorry!
Hi everybody,
As you may or may not know, the latest builds of CyanogenMod 10.1 (and many other ROMs which use CM as a base) refuse to install without an updated bootloader on your device. Even if you bypass this requirement, the ROM won't boot. I haven't seen any clear-cut instructions on updating the bootloader except for a single post buried in the CM10.1 nightly thread, posted by Jiangyi, but that update also changes your modem, so I thought I'd throw together a thread dedicated to bootloaders only.
Step 1 - Identify your model
This subforum supports 2 different models; The I747 and the I747M. You can find your device's model in a few different ways:
While Android is running
In Settings, under About Phone, the Baseband version shows the currently installed modem firmware version. If your phone currently works on mobile networks, then you've probably got the right modem firmware for your model, and the Baseband version will start with either "I747" or "I747M". This is your model.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
While the phone is off
Underneath your battery is a sticker showing your IMEI and other information, including the model number.
Step 2 - Download the correct update
You can install this updated bootloader in a couple different ways; Most people should be comfortable flashing ZIPs in their recovery (CWM or TWRP both work fine) while others may want to install the update via Odin. Choose your model and preferred method, and download the matching file from below.
I747U (AT&T)
I747UCALG1 - Jul 1, 2012 - boot_CWM_I747UCALG1.zip - 1.13 MB
I747UCDLK3 - Nov 3, 2012 - boot_CWM_I747UCDLK3.zip - 1.13 MB
I747UCDMG2 - Jul 2, 2013 - boot_CWM_I747UCDMG2.zip - 1.13 MB
I747UCUEMJB - Oct 11, 2013 - boot_CWM_I747UCUEMJB.zip - 1.14 MB WARNING: Do not attempt to downgrade from this bootloader. Doing so will brick your device. Use extra caution when flashing anything via Odin, as many Odin packages will attempt to flash the bootloader.
I747M (Canada and overseas) (Updating this list shortly...)
I747MVLUEMK5 - Nov 5, 2013 - boot_CWM_I747MVLUEMK5.zip - 1.14 MB WARNING: Do not attempt to downgrade from this bootloader. Doing so will brick your device. Use extra caution when flashing anything via Odin, as many Odin packages will attempt to flash the bootloader.
Check my Dropbox if d-h.st is giving you issues.
Step 3 - Flash the update
Depending on which type of update package you downloaded, follow one of the following steps:
Flashing with Odin
Download Odin: [link]
Put your phone into download mode. Some ROMs have this option in the Power>Reboot menu, otherwise just hold "Volume Down" and "Home" while powering on your device.
Launch Odin, then connect the USB cable to your device.
Click the "PDA" button and select the package you downloaded in step 2.
Click "Start" in Odin and wait for the process to complete. Your device should reboot automatically when the flash is complete, and you're done.
Flashing in recovery
If you've downloaded a flashable .ZIP from above, copy it to your SD card or internal storage. Reboot your phone into recovery mode (you can do this by holding "Volume Up" and "Home" while powering on your device; let go of the buttons when you see "Recovery booting..." in blue text in the top left of the screen) and install the .ZIP as an update. Reboot, and you're done.
Note: After flashing in recovery, you need to reboot before you (and ROM installers) actually see the new version number.
Did you brick your phone attempting to downgrade your bootloader?
There really is no reason to downgrade your bootloader; If you did it to be able to flash a ROM that doesn't recognize the newest bootloader version and therefore wouldn't let you flash, you should contact the ROM developer and tell them to add the newest bootloader version to their asserts. The latest bootloaders trigger eFUSEs within the device, no longer allowing it to boot from older bootloaders. These eFUSEs cannot be reset, but @-Mr. X- has come up with an unbricking method that may help you out. Check it out here.
If you're looking to update your modem as well, check my signature for a link to the modem thread.
Look forward to seeing a recovery flashable zip that updates the bootloader. Never have I seen that before. I have always used Odin for that. Thanks and looking forward to trying it out.
Sent from My Spiderman Themed I747
So you created a thread for bootloader only updates, but there are no bootloader only updates available?
What files are available for download? Is that the full firmware or the files created by Jiangyi?
upndwn4par said:
So you created a thread for bootloader only updates, but there are no bootloader only updates available?
What files are available for download? Is that the full firmware or the files created by Jiangyi?
Click to expand...
Click to collapse
Currently I've linked to Jiangyi's files, I'm working on bootloader-only updates right now. I just wanted to get this thread up ASAP because I've had a few different people PM me asking for help. As a temporary option, you could just use the Odin update and then flash another modem on top of that.
dstruct2k said:
Currently I've linked to Jiangyi's files, I'm working on bootloader-only updates right now. I just wanted to get this thread up ASAP because I've had a few different people PM me asking for help.
Click to expand...
Click to collapse
Instead of posting links to someone else's work, you could have just directed them to Jiangyi's post in the CM10.1 thread.
upndwn4par said:
Instead of posting links to someone else's work, you could have just directed them to Jiangyi's post in the CM10.1 thread.
Click to expand...
Click to collapse
The link in my first paragraph does just that, but since this is affecting a lot more ROMs than just CM, people are going to need this information and a single post on a random page of a massive thread usually gets overlooked by 99% of people. The point of this thread is to make information easy to find and ensure that people are able to update their bootloaders and run new ROMs.
Like I said, the links to his work are temporary while I get my own files uploaded. Not exactly on the fastest of connections right now.
Added recovery-flashable bootloaders to OP.
i found this post very helpful and informative i think i would have been MORE confused having just been linked to a single post. the pictures and instructions are so awesome!
thanks man the community appreciates your work, you can ignore the rent a mods
If your phone came with DLK3 when purchased from AT&T this is not necessary correct?
SHOstock3
Jeboo 2.2
mcala said:
If your phone came with DLK3 when purchased from AT&T this is not necessary correct?
SHOstock3
Jeboo 2.2
Click to expand...
Click to collapse
Depends on whether they updated just the modem to DLK3 or the entire system. If you have issues flashing ROMs, try flashing this first.
thanks! :good:
saves me the hassle of going thru 2k+ pages
If your unsure about which bootloader you have, check >>HERE<<
So if I flash this, my flash counter will increase to 1, right? I've been avoiding the bootloader update because of this.
When I got my phone, I upgraded to 4.1.1 (which is what this bootloader update is based on, right?), then rooted, installed CWM, and flashed ROMs. But with that Triangle Away reset the counter to 0 only until a reboot, after reboot it incremented to 1. So to resolve I Odin flashed 4.0.4, rooted, installed CWM, used Triangle away, then flashed ROMs... and my counter stayed at 0 after reboot.
Just trying to hedge warranty concerns versus being a nightly flashaholic....
Correct, the 4.1.1 bootloader does have the newer flash counter. It will increase your flash counter when you reboot if your not running stock (I think it checks the type of recovery installed and something with the kernel. I think.)
robbieas said:
So if I flash this, my flash counter will increase to 1, right? I've been avoiding the bootloader update because of this.
When I got my phone, I upgraded to 4.1.1 (which is what this bootloader update is based on, right?), then rooted, installed CWM, and flashed ROMs. But with that Triangle Away reset the counter to 0 only until a reboot, after reboot it incremented to 1. So to resolve I Odin flashed 4.0.4, rooted, installed CWM, used Triangle away, then flashed ROMs... and my counter stayed at 0 after reboot.
Just trying to hedge warranty concerns versus being a nightly flashaholic....
Click to expand...
Click to collapse
Using a recovery-flashable ZIP will not increase your flash counter.
And I take it you got his permission To post his work right?
Wayne Tech Nexus
I think it's ok to post links to other people's work, and to improve on it by creating another method of flashing, is it not?
Not without their permission it's not.
Wayne Tech Nexus
dstruct2k said:
Using a recovery-flashable ZIP will not increase your flash counter.
Click to expand...
Click to collapse
This is incorrect. Simply having a custom recovery period with the 4.1.1 bootloader will always increment your counter to 1 after a reboot. Triangle Away will reset your counter to 0, but upon reboot it will be back to 1.
This was my experience when I rooted from 4.1.1. Then I Odin`d back to 4.0.4, rooted, CWM, flased ROMs and my counter stayed at 0 through multiple flashes. As soon as I flashed this bootloader patch my counter went to 1 ater reboot. Triangle Away will reset to 0, but on reboot it goes back to 1.
Not sure it really matters, not sure why I even care about the flash counter... guess just want to hedge my bets in case I need warranty and can't Odin to stock before returning.
dstruct2k said:
Added recovery-flashable bootloaders to OP.
Click to expand...
Click to collapse
What does "OP"means?
Hey guys! This might sound noobish, but i really never flashed, rooted, or anything on a droid/etc before. So atm I bought a galaxy s4 for my dad, and tried unlocking this stupid phone, but unlocking thru the dialer didnt work(couldnt even get *#27663368378# to work, when using *#0011#, still couldnt do anything.) All i know about it, is that it recognizes the European sim card, but the simple mobile(usa) sim card doesnt recognize, can't make calls, etc, as when you try to make a call it says "cant register to network" or w.e. So i was wondering what should I do? Do i need to flash the modem? rom? Root it? I want it to be able to work in global, in usa and euro.
On another note, I got my other phone that's on ver 4.2.2. Should i try upgrading my modem/baseband from mdl to nb4? Anything new with the new modem or anything i should update? Since i cant update OTA anymore on my 4.2.2. lol. Any suggestions would be awesome Tell me from your point of you, is it better to stay at 4.2.2? or just get the 4.4.2, and should i root my phone? Any vernabilities/security problems if done?
I found this: http://forum.xda-developers.com/showthread.php?t=2780006
Samsung Galaxy S4 M919 T-mobile
ROM: M919UVUFNB4
4.4.2 kitkat
Den Den said:
Hey guys! This might sound noobish, but i really never flashed, rooted, or anything on a droid/etc before. So atm I bought a galaxy s4 for my dad, and tried unlocking this stupid phone, but unlocking thru the dialer didnt work(couldnt even get *#27663368378# to work, when using *#0011#, still couldnt do anything.) All i know about it, is that it recognizes the European sim card, but the simple mobile(usa) sim card doesnt recognize, can't make calls, etc, as when you try to make a call it says "cant register to network" or w.e. So i was wondering what should I do? Do i need to flash the modem? rom? Root it? I want it to be able to work in global, in usa and euro.
On another note, I got my other phone that's on ver 4.2.2. Should i try upgrading my modem/baseband from mdl to nb4? Anything new with the new modem or anything i should update? Since i cant update OTA anymore on my 4.2.2. lol. Any suggestions would be awesome Tell me from your point of you, is it better to stay at 4.2.2? or just get the 4.4.2, and should i root my phone? Any vernabilities/security problems if done?
I found this: http://forum.xda-developers.com/showthread.php?t=2780006
Samsung Galaxy S4 M919 T-mobile
ROM: M919UVUFNB4
4.4.2 kitkat
Click to expand...
Click to collapse
To unlock your dad's phone the guide you linked to should do what you need done.
As far as your phone still on MDL, you should be able to use the old method through the service menu to unlock if that's what you wanted to do. You can update your modem/baseband if you desire, although if you're staying on stock 4.2.2 TouchWiz there is really no need to. It's only when you flash ROMs based on 4.3 and above that you run into issues using the MDL modem/baseband.
To add to lordcheeto's post, there's a difference between MDL bootloader and the MDL modem. When the S4 was released with Android 4.2 it had an unlocked bootloader (MDL), but with Android 4.3 and 4.4 Samsung included new security software called Knox. Knox doesn't prevent rooting, but if you flash a custom recovery such as CWMR, TWRP, or Philz Touch then a security flag will be irreversibly tripped which voids your warranty. Because this Knox software is tied into the bootloader, developers found a way around it by extracting the modems from 4.3 (MK2) and 4.4 (NB4) firmwares which allows us to keep our MDL bootloader and still use 4.2, 4.3, and 4.4 roms. The advantages are that we keep our warranty and we're able to use any 4.2+ rom. We can downgrade and upgrade easily while Knox phones can't.
lordcheeto03 said:
To unlock your dad's phone the guide you linked to should do what you need done.
As far as your phone still on MDL, you should be able to use the old method through the service menu to unlock if that's what you wanted to do. You can update your modem/baseband if you desire, although if you're staying on stock 4.2.2 TouchWiz there is really no need to. It's only when you flash ROMs based on 4.3 and above that you run into issues using the MDL modem/baseband.
Click to expand...
Click to collapse
Should i keep the 4.4.2 kitkat thats not working with my usa sim card atm? Or should i flash it to 4.2.2. ADL? If having 4.2.2 is better doing that guide i put link to above, then give me a good tut on doing it, need to do it today xD THanks in Advance!
HampTheToker said:
To add to lordcheeto's post, there's a difference between MDL bootloader and the MDL modem. When the S4 was released with Android 4.2 it had an unlocked bootloader (MDL), but with Android 4.3 and 4.4 Samsung included new security software called Knox. Knox doesn't prevent rooting, but if you flash a custom recovery such as CWMR, TWRP, or Philz Touch then a security flag will be irreversibly tripped which voids your warranty. Because this Knox software is tied into the bootloader, developers found a way around it by extracting the modems from 4.3 (MK2) and 4.4 (NB4) firmwares which allows us to keep our MDL bootloader and still use 4.2, 4.3, and 4.4 roms. The advantages are that we keep our warranty and we're able to use any 4.2+ rom. We can downgrade and upgrade easily while Knox phones can't.
Click to expand...
Click to collapse
What do you suggest? Should i downgrade to 4.2.2.? Or just run with the guide i posted above keeping the 4.4.2. NB4, I just need it to run so i can call, use date, and go to euro and use in usa ofc. Ive been using my 4.2.2. pretty good so far, been almost a year and had no problems with it, should i worry about updating my modem on my 4.2.2.? or anything important, etc? If i should go with 4.2.2., i need to root it eh? If so, point me to the good rooting method and downgrading to 4.2.2. frin 4.4.2 Kitkat(updated OTA). Thanks in Advance!
Den Den said:
What do you suggest? Should i downgrade to 4.2.2.? Or just run with the guide i posted above keeping the 4.4.2. NB4, I just need it to run so i can call, use date, and go to euro and use in usa ofc. Ive been using my 4.2.2. pretty good so far, been almost a year and had no problems with it, should i worry about updating my modem on my 4.2.2.? or anything important, etc? If i should go with 4.2.2., i need to root it eh? If so, point me to the good rooting method and downgrading to 4.2.2. frin 4.4.2 Kitkat(updated OTA). Thanks in Advance!
Click to expand...
Click to collapse
I thought the answers given were pretty clear... I'm actually confused about what phone you're asking about, and if there are, in fact, 2 different phones in question... My answer will be a bit lengthy, but I hope that you can put 1 and 2 together and apply the information I am about to type to your particular situation: Also, I'm not trying to be a ****, just concise.
In reference to the S4 that is on 4.4.2 (NB4) firmware: The unlock method which you posted SHOULD enable the device to use different SIM cards and function in "euro" and "usa." That includes making calls and using "date" (data?) as you mentioned. As far as your question on reverting that particular device: There is no way whatsoever to downgrade the firmware on a device running either stock 4.3 (MK2) or stock 4.4.2 (NB4) obtained by flashing via Odin, Kies, or OTA; so that idea can be forgotten about. The unlock method, from what I gather, simply reverts the modem and allows you to use the old unlock method. then returns the modem to NB4. It does not touch the firmware, bootloader, or anything other than the modem/baseband.
For whichever device this applies to: there should be no need to root either to accomplish either goal. If you wish to root, then I can point you in the right direction; otherwise, if you haven't needed it so far and don't foresee needing it in the future, I say don't worry about it.
As for the device running 4.2.2: if you have had no troubles with reception, then there is no need to update your modem/baseband. There are really only 2 times that updating your modem would come in handy. 1: If you are having reception problems, or 2: If you plan on keeping your bootloader at MDL AND using custom ROMs 4.3 and above. The benefit of this scenario is that keeping your bootloader on MDL means that your device does not have the KNOX-implemented bootloader and can easily be reverted to a completely stock state for warranty purposes yet you still get to have the most up-to-date version of Android. If neither of those conditions apply to you, then there is really no real need to update your modem.
Den Den said:
What do you suggest? Should i downgrade to 4.2.2.? Or just run with the guide i posted above keeping the 4.4.2. NB4, I just need it to run so i can call, use date, and go to euro and use in usa ofc. Ive been using my 4.2.2. pretty good so far, been almost a year and had no problems with it, should i worry about updating my modem on my 4.2.2.? or anything important, etc? If i should go with 4.2.2., i need to root it eh? If so, point me to the good rooting method and downgrading to 4.2.2. frin 4.4.2 Kitkat(updated OTA). Thanks in Advance!
Click to expand...
Click to collapse
The guide you posted should work just fine. Just follow the instructions.
Also, I left out one of the most important parts of having the modems extracted from the 4.3 and 4.4 firmwares. The reason for extracting the modems is so that we can flash them separately from the official firmware which would upgrade us to a Knox bootloader. Using the 4.2 modem with 4.3 and 4.4 roms causes data and sound issues that make the phone pretty much unusable. The same goes for using the 4.3 modem with a 4.4 rom. With the extracted modems we can flash them separately for whatever Android version we're using and have full functionality and retain the MDL bootloader and all it's perks.
If you use a 4.2 rom, you'll need to make sure to flash the MDL modem with it.
For 4.3 roms, you'll need to be on MK2 modem.
4.4 roms require NB4 modem.
As long as you don't update to official 4.3 or 4.4, you'll be able to use any version rom you want according to your preference. Personally, I use 4.4 roms, but it's nice to have the option to go back to 4.2 if I want to. Once you SIM unlock, it should stick between all versions. You should be able to flash any rom that you want without having to worry about going through that process again.
lordcheeto03 said:
I thought the answers given were pretty clear... I'm actually confused about what phone you're asking about, and if there are, in fact, 2 different phones in question... My answer will be a bit lengthy, but I hope that you can put 1 and 2 together and apply the information I am about to type to your particular situation: Also, I'm not trying to be a ****, just concise.
In reference to the S4 that is on 4.4.2 (NB4) firmware: The unlock method which you posted SHOULD enable the device to use different SIM cards and function in "euro" and "usa." That includes making calls and using "date" (data?) as you mentioned. As far as your question on reverting that particular device: There is no way whatsoever to downgrade the firmware on a device running either stock 4.3 (MK2) or stock 4.4.2 (NB4) obtained by flashing via Odin, Kies, or OTA; so that idea can be forgotten about. The unlock method, from what I gather, simply reverts the modem and allows you to use the old unlock method. then returns the modem to NB4. It does not touch the firmware, bootloader, or anything other than the modem/baseband.
For whichever device this applies to: there should be no need to root either to accomplish either goal. If you wish to root, then I can point you in the right direction; otherwise, if you haven't needed it so far and don't foresee needing it in the future, I say don't worry about it.
As for the device running 4.2.2: if you have had no troubles with reception, then there is no need to update your modem/baseband. There are really only 2 times that updating your modem would come in handy. 1: If you are having reception problems, or 2: If you plan on keeping your bootloader at MDL AND using custom ROMs 4.3 and above. The benefit of this scenario is that keeping your bootloader on MDL means that your device does not have the KNOX-implemented bootloader and can easily be reverted to a completely stock state for warranty purposes yet you still get to have the most up-to-date version of Android. If neither of those conditions apply to you, then there is really no real need to update your modem.
Click to expand...
Click to collapse
That Makes sense...just trying to grasp info. on everything so it's more clearer ;p and thanks for correcting me, yea it was data lol.
HampTheToker said:
The guide you posted should work just fine. Just follow the instructions.
Also, I left out one of the most important parts of having the modems extracted from the 4.3 and 4.4 firmwares. The reason for extracting the modems is so that we can flash them separately from the official firmware which would upgrade us to a Knox bootloader. Using the 4.2 modem with 4.3 and 4.4 roms causes data and sound issues that make the phone pretty much unusable. The same goes for using the 4.3 modem with a 4.4 rom. With the extracted modems we can flash them separately for whatever Android version we're using and have full functionality and retain the MDL bootloader and all it's perks.
If you use a 4.2 rom, you'll need to make sure to flash the MDL modem with it.
For 4.3 roms, you'll need to be on MK2 modem.
4.4 roms require NB4 modem.
As long as you don't update to official 4.3 or 4.4, you'll be able to use any version rom you want according to your preference. Personally, I use 4.4 roms, but it's nice to have the option to go back to 4.2 if I want to. Once you SIM unlock, it should stick between all versions. You should be able to flash any rom that you want without having to worry about going through that process again.
Click to expand...
Click to collapse
So If i was on 4.3, and it updated to 4.4.2 kitkat, means it went to the official update eh? As "lordcheeto03" said that once u go to 4.3 or 4.4.2 you cant go back to 4.2, the menu options and w.e go updated, the "about me" is now yellow, the top border of the phone is grey, etc. The new security is enforcing, I guess I'll try the guide i found, hope i don't do anything stupid or skip a step(usually doesn't happen) but feels kinda weird doing things the first time.
On another note, if a phone bricks or in a loop, etc can it be solved? So i still have hope if something goes wrong xD
edit: The guide i link that i found, it works for all m919 models? Since i got t-mobile, not sure if all models(tmobile, att, etc) have the same modem, wouldnt want to brick cuz of not flashing the correct file, w.e(disregard this, i forgot i posted in the t-mobile section, man sometimes i feel like an idiot because i dont double check xD)
Den Den said:
So If i was on 4.3, and it updated to 4.4.2 kitkat, means it went to the official update eh? As "lordcheeto03" said that once u go to 4.3 or 4.4.2 you cant go back to 4.2, the menu options and w.e go updated, the "about me" is now yellow, the top border of the phone is grey, etc. The new security is enforcing, I guess I'll try the guide i found, hope i don't do anything stupid or skip a step(usually doesn't happen) but feels kinda weird doing things the first time.
On another note, if a phone bricks or in a loop, etc can it be solved? So i still have hope if something goes wrong xD
edit: The guide i link that i found, it works for all m919 models? Since i got t-mobile, not sure if all models(tmobile, att, etc) have the same modem, wouldnt want to brick cuz of not flashing the correct file, w.e(disregard this, i forgot i posted in the t-mobile section, man sometimes i feel like an idiot because i dont double check xD)
Click to expand...
Click to collapse
Once you hit 4.3, you lost your ability to downgrade. You can upgrade, but you can't go back. Rest easy, as long as you can get into download mode, you can recover your device. Bootloop, soft brick, whatever; as long as Power + volume down brings you to download mode everything is still OK. Just read the directions a few times.. get used to the idea of what's going on, double check and make sure you have the right software and files, and jump in. You'll do fine. Even after years of jailbreaking iphones and rooting Droids, I still get nervous whenever I have to fire up Odin; but just remember... many many others (more than have posted in that thread for sure) have done the same thing you're about to do, so as long as you follow the directions you will be fine!
lordcheeto03 said:
Once you hit 4.3, you lost your ability to downgrade. You can upgrade, but you can't go back. Rest easy, as long as you can get into download mode, you can recover your device. Bootloop, soft brick, whatever; as long as Power + volume down brings you to download mode everything is still OK. Just read the directions a few times.. get used to the idea of what's going on, double check and make sure you have the right software and files, and jump in. You'll do fine. Even after years of jailbreaking iphones and rooting Droids, I still get nervous whenever I have to fire up Odin; but just remember... many many others (more than have posted in that thread for sure) have done the same thing you're about to do, so as long as you follow the directions you will be fine!
Click to expand...
Click to collapse
Thanks for the reply, now I'm all fired up and ready to do this I'll post back here when i'm done and see how it went xD
Edit: Can i ask you a favor? Could you get me the "M919UVUFNB4_M919TMBFNB4_TMB.zip" modem file and "M919UVUAMDL_M919TMBAMDL_TMB.zip", i think that's what the tutorial link i posted is asking for. But the files r huge, 1.6gb, etc, would take me 3hrs+ each for each file to download just to extract the modem =/ If that's the only thing i need.
found these links: http://rapidgator.net/file/59487dc515500a0430ddaddc780fa555/TMB-M919UVUFNB4-20140314115123.zip.html
and : http://terafile.co/32d149264215/M919UVUAMDL_M919TMBAMDL_TMB.zip
Not sure if they are safe to use or not, not everything on the net is...plus they r huge files =/
Den Den said:
Thanks for the reply, now I'm all fired up and ready to do this I'll post back here when i'm done and see how it went xD
Edit: Can i ask you a favor? Could you get me the "M919UVUFNB4_M919TMBFNB4_TMB.zip" modem file and "M919UVUAMDL_M919TMBAMDL_TMB.zip", i think that's what the tutorial link i posted is asking for. But the files r huge, 1.6gb, etc, would take me 3hrs+ each for each file to download just to extract the modem =/ If that's the only thing i need.
found these links: http://rapidgator.net/file/59487dc515500a0430ddaddc780fa555/TMB-M919UVUFNB4-20140314115123.zip.html
and : http://terafile.co/32d149264215/M919UVUAMDL_M919TMBAMDL_TMB.zip
Not sure if they are safe to use or not, not everything on the net is...plus they r huge files =/
Click to expand...
Click to collapse
These files include modem.bin that is required... I'm not sure why the OP linked to the entire firmware instead of just those links, but anywho...
The NB4 modem can be found in this thread. It's only ~20MB.
The MDL modem is in this thread. It is ~25MB.
Also, quote me instead of just replying to the thread. I'll respond quicker
lordcheeto03 said:
These files include modem.bin that is required... I'm not sure why the OP linked to the entire firmware instead of just those links, but anywho...
The NB4 modem can be found in this thread. It's only ~20MB.
The MDL modem is in this thread. It is ~25MB.
Also, quote me instead of just replying to the thread. I'll respond quicker
Click to expand...
Click to collapse
Flashed ADL using odin, somehow got the menu to work(couldnt budge for some reason to umts), went thru all the steps, it rebooted, put it back to download mode, and flashed it back to nb4. Put my simplemobile simcard in, still nothing, am I supposed to put a different sim card in like ATT or something for it to work? Confused why it didnt work, yet it still detects the MTC european version simcard(not in service, but it had a pin set on it, so it always asks you to unlock the sim with the sim pin u put on it to view ur files on it, etc). Am i doing something wrong? I could give you more info on the phone...
Edit: Just checked on Swappa.com of my imei and got this =/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nvm, Looks like i think its blocked on Tmobiles network, but i put in the H2O sim and it worked.(under ATT) phew....
New software update 2.34.401.2
Can anyone tell how i can update my device if i have root and recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC Desire 816 dual sim using Tapatalk
Look in the general forum for full guide. You need to go back to stock. Basically flash stock recovery and re-lock bootloader. If you loaded system mods then you probably have to run the ruuxx.exe for your model before doing the OTA. Otherwise you can try OTA after re-lock.
does anyone know how to delete this update? I clicked it by mistake and it installed and tried to update, but it messed with my root making some apps just showing grayed out SD and it keeps trying to make me try to install it again. I was thinking if I can find out where the install file is, i could just delete it and everything might go back to normal.
What is the update contains ??? Did anyone try???
Sent from my HTC Desire 816 dual sim using Tapatalk
I installed it on my Virgin Mobile A5-chl. Doesn't appear to be anything major, mainly just the Stagefright patch. I don't see any other improvements or changes. It was a small patch, so I'm guessing it was just the patch.
Andy1058 said:
does anyone know how to delete this update? I clicked it by mistake and it installed and tried to update, but it messed with my root making some apps just showing grayed out SD and it keeps trying to make me try to install it again. I was thinking if I can find out where the install file is, i could just delete it and everything might go back to normal.
Click to expand...
Click to collapse
The OTA file should be in your download directory. The install failed so it's going to keep asking. I'm not sure if it has an option to never install the update?
I'm seen that app grayed out thing. It's just the apps you've moved to your SD card through the apps page in settings. For some reason it sometimes takes a few seconds for the app to display correctly. I don't think it has anything to do with the software upgrade.
---------- Post added at 11:45 AM ---------- Previous post was at 11:40 AM ----------
joey jamal said:
What is the update contains ??? Did anyone try???
Sent from my HTC Desire 816 dual sim using Tapatalk
Click to expand...
Click to collapse
It's the Stage fright patch. Google it if you want to know more, but basically anyone can crash or take over your phone just by sending you a text w/video.
pcjunky said:
The OTA file should be in your download directory. The install failed so it's going to keep asking. I'm not sure if it has an option to never install the update?
I'm seen that app grayed out thing. It's just the apps you've moved to your SD card through the apps page in settings. For some reason it sometimes takes a few seconds for the app to display correctly. I don't think it has anything to do with the software upgrade.
---------- Post added at 11:45 AM ---------- Previous post was at 11:40 AM ----------
It's the Stage fright patch. Google it if you want to know more, but basically anyone can crash or take over your phone just by sending you a text w/video.
Click to expand...
Click to collapse
yeah it sometimes does a few seconds for them to come back after be grayed out, but so far they havent at all. I cant find the install file, anyone know the name of the file?
Andy1058 said:
yeah it sometimes does a few seconds for them to come back after be grayed out, but so far they havent at all. I cant find the install file, anyone know the name of the file?
Click to expand...
Click to collapse
It's a zip file with a crazy long name that I will not type, but it starts with OTA_A5_CHL_L50_DESIRE. You can find the full name in the link in the patch thread in the general forum.
Please any help I relock my device bootloader ana back to stock recovery but wen I install the ota update it just restart to fastboot and stopped nothing else ...Please help ad5ug I need the way that I can back to stock and recive update
Sent from my HTC Desire 816 dual sim using Tapatalk
Andy1058 said:
yeah it sometimes does a few seconds for them to come back after be grayed out, but so far they havent at all. I cant find the install file, anyone know the name of the file?
Click to expand...
Click to collapse
I forgot to mention that after the update patch is successful the OTA zip file is deleted. I can't remember if the zip file is also deleted if the update fails, but if it isn't in the download (s) directory than it's deleted. Just download the OTA again and delay the install if you want to copy it to your PC to extract and examine the update.
Does anybody have a pure stock twrp or cwm backup before this OTA? I forgot to make my own. the RUU.exe keeps failing with "RomTool.exe has stopped working."my laptop may be at fault, but I can transfer files to and from my phone just fine. VM a5_CHL
jayblaze406 said:
Does anybody have a pure stock twrp or cwm backup before this OTA? I forgot to make my own. the RUU.exe keeps failing with "RomTool.exe has stopped working."my laptop may be at fault, but I can transfer files to and from my phone just fine. VM a5_CHL
Click to expand...
Click to collapse
Did you try uninstalling and then reinstalling HTC Sync? Can I assume you flashed stock recovery and re-locked boot loader?
Any chance you still have the Kitkat to Lollipop OTA update zipfile and can extract and flash the firmware.zip then run the Lollipop ruu.exe (not the new one with the patch). Take a look at this thread for how to info. Basically you're pre flashing the firmware that should be in the ruu.exe file so the ruu.exe shouldn't fail. Then the ota SF patch should run.
pcjunky said:
Did you try uninstalling and then reinstalling HTC Sync? Can I assume you flashed stock recovery and re-locked boot loader?
Any chance you still have the Kitkat to Lollipop OTA update zipfile and can extract and flash the firmware.zip then run the Lollipop ruu.exe (not the new one with the patch). Take a look at this thread for how to info. Basically you're pre flashing the firmware that should be in the ruu.exe file so the ruu.exe shouldn't fail. Then the ota SF patch should run.
Click to expand...
Click to collapse
Nope. don't have the update zip. I'm s-off. rooted. busybox. xposed framework. So much modding I can't OTA because my system files are tainted. but yes, I've uninstalled/reinstalled HTC sync manager on my pc. tried fastboot drivers from here at xda. even uninstalled all of the android sdk files and reinstalled. I'm currently on the 5.0.2 HTC release already. I was able to complete the ru u.exe on my newer laptop. but all I have now is an old Vista x86 laptop. I think the usb ports aren't the best to work with. flashed stock recovery, relocked boot loader several times over. just fed up I restored my rooted, xposed twrp until I can try a different pc.
All is well! Found a Kit Kat stock unrooted twrp backup on my external drive. flashed that, changed the boot.emmc to boot.img. flashed that. Redownloaded the first Lollipop OTA, extracted the stock recovery from the firmware.zip. flashed that. OTA'd the original lollipop release, then OTA'd the stagefright patch. started from scratch but got it done. bootloader stayed unlocked the whole time since I'm s-off. thanks for info, though.
Looking for CWM backup
I've already flashed recovery stock and re-locked
but OTA download corrupted
So, any option to install this patch without going back to stock, and re-locking bootloader ?
Just got myself a TMO M919 on the cheap today. M919 only got Kitkat while M919V (Canadian) got Lollipop. Figured I could be adventurous and try a M919V firmware on it... And voila, it actually boots!
Not without some modifications to the original firmware though, or Odin will fail at checking authenticity of bootloader or modem (model doesn't match). I used a TAR repackaging tool to remove all the bootloader and modem parts from the firmware, and flashed the repackaged TAR via Odin.
So basically it's a Lollipop TW firmware booting on top of the Kitkat bootloader. Call, SMS, LTE, camera, everything I tested in the brief time I used it works fine. Makes sense, the V variant is even more similar to M919 than i9505.
I know it's kinda late, since most people here should already be on an AOSP-based custom firmware by now (I'll also flash LOS soon), but nevertheless I think it could be a refresher for people who have it on stock for using at home, etc.
I'll upload the repackaged stuff if there are still people actually interested in it.
Screenshot as proof below (note that the baseband is from M919):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi there, I'm interested in your repackaged M919V Firmware. Can you upload it? Thanks ill be waiting. Cheers
MysticBlueDragon said:
Hi there, I'm interested in your repackaged M919V Firmware. Can you upload it? Thanks ill be waiting. Cheers
Click to expand...
Click to collapse
https://androidfilehost.com/?a=show&w=files&flid=239650
I've also tried repackaging the latest i9505G (S4 GPe) firmware and flashing and the experience is also good, though I haven't extensively tested either. They are both in the folder.
it's the wifi calling that's the main problem running a lollipop ROM on SGH-M919
found a solution wifi
kalan1988 said:
found a solution wifi
Click to expand...
Click to collapse
Just install this kernel
https://androidfilehost.com/?w=file...2674a1a5ca61e20aa2c0b1cf1f6c99f1a46298b244ca6
heres is the xda link:
https://forum.xda-developers.com/galaxy-s4-tmobile/general/i9505oa7tw5-0leak-t3045729
AndyYan said:
Just got myself a TMO M919 on the cheap today. M919 only got Kitkat while M919V (Canadian) got Lollipop. Figured I could be adventurous and try a M919V firmware on it... And voila, it actually boots!
Not without some modifications to the original firmware though, or Odin will fail at checking authenticity of bootloader or modem (model doesn't match). I used a TAR repackaging tool to remove all the bootloader and modem parts from the firmware, and flashed the repackaged TAR via Odin.
So basically it's a Lollipop TW firmware booting on top of the Kitkat bootloader. Call, SMS, LTE, camera, everything I tested in the brief time I used it works fine. Makes sense, the V variant is even more similar to M919 than i9505.
I know it's kinda late, since most people here should already be on an AOSP-based custom firmware by now (I'll also flash LOS soon), but nevertheless I think it could be a refresher for people who have it on stock for using at home, etc.
I'll upload the repackaged stuff if there are still people actually interested in it.
Screenshot as proof below (note that the baseband is from M919):
Click to expand...
Click to collapse
Can you flash this thru recovery mode?
I found that the LP kernel needed to get WiFi breaks Widevine L1 (gets set to L3), which would partially defeat the purpose of using a Touchwiz stock rom anyway. I am trying a few other kernels and will see if one works. GPE edition 5.1 flashes fine including WiFi but Widevine L1 does not actually work despite showing up in DRMINFO.
AndyYan said:
Just got myself a TMO M919 on the cheap today. M919 only got Kitkat while M919V (Canadian) got Lollipop. Figured I could be adventurous and try a M919V firmware on it... And voila, it actually boots!
Not without some modifications to the original firmware though, or Odin will fail at checking authenticity of bootloader or modem (model doesn't match). I used a TAR repackaging tool to remove all the bootloader and modem parts from the firmware, and flashed the repackaged TAR via Odin.
So basically it's a Lollipop TW firmware booting on top of the Kitkat bootloader. Call, SMS, LTE, camera, everything I tested in the brief time I used it works fine. Makes sense, the V variant is even more similar to M919 than i9505.
I know it's kinda late, since most people here should already be on an AOSP-based custom firmware by now (I'll also flash LOS soon), but nevertheless I think it could be a refresher for people who have it on stock for using at home, etc.
I'll upload the repackaged stuff if there are still people actually interested in it.
Screenshot as proof below (note that the baseband is from M919):
Click to expand...
Click to collapse
Does this mean you're going to Dev for the s4? We would love to have you!
I installed your repackaged tar successfully and also flashed the kernel you suggested. Wifi worked after flashing the kernel but if I reset the phone, the saved wifi info is lost so I have to re-enter wifi info all over again. Any advice on this? Should I be looking for a different kernel or any advice you guys can give? Greatly appreciated.
AndyYan said:
https://androidfilehost.com/?a=show&w=files&flid=239650
I've also tried repackaging the latest i9505G (S4 GPe) firmware and flashing and the experience is also good, though I haven't extensively tested either. They are both in the folder.
Click to expand...
Click to collapse
Hey man, can't thank you enough for this. In the process of updating the device (GT-I9505G), I managed to screw up somewhere and now the cell phone data does not work. This is the screenshot of my firmware(s). Everything else, like calling, wifi etc works. Before I realized I tried to update install ROM, as it has happened in the past, but still things are the way they are, no cell phone data. APN is correct. I made that sure.
The screenshots of the firmware are below. CSC and PDA version are missing.
Screenshots taken using https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en_US
I was wondering if I flash your I9505GUEUDPF1_Boot+Rec+Sys.tar.md5 to this device, will it address the issue and put back PDA and CSC version?
If yes, how do I flash it in Odin, as what do I choose or extract the file and flash everything separately?
Thanks a million again. You saved my rear end a big time.
Edit: I have realized you can not flash the file as is. So I have extracted the image in *.ext4 format. I need guidance which folders to extract and how to proceed thereon. Thank you very much.
fuzzychicken said:
I was wondering if I flash your I9505GUEUDPF1_Boot+Rec+Sys.tar.md5 to this device, will it address the issue and put back PDA and CSC version?
Click to expand...
Click to collapse
I don't get it - what's stopping you from flashing the *full* firmware available around the web? That's the surefire way to fully recover.
AndyYan said:
I don't get it - what's stopping you from flashing the *full* firmware available around the web? That's the surefire way to fully recover.
Click to expand...
Click to collapse
There is another thread where all ROMs are listed. I have tried flashing those stock ROMs but I have not been successful.
So I went back to 5.0.1 stock ROM and let the phone update by itself, still I have not been successful. I am super confused why repeated updates could not fix this problem.
I have EFS backups from 5.0.1 stock (before I started flashing business). Do you think I can use that? I am not too sure of CSC and PDA are in the efs partition, hence the question.
Thanks again.
fuzzychicken said:
There is another thread where all ROMs are listed. I have tried flashing those stock ROMs but I have not been successful.
So I went back to 5.0.1 stock ROM and let the phone update by itself, still I have not been successful. I am super confused why repeated updates could not fix this problem.
I have EFS backups from 5.0.1 stock (before I started flashing business). Do you think I can use that? I am not too sure of CSC and PDA are in the efs partition, hence the question.
Thanks again.
Click to expand...
Click to collapse
For what I know you *have* to use the full firmware for those partitions...
AndyYan said:
For what I know you *have* to use the full firmware for those partitions...
Click to expand...
Click to collapse
Yes, I totally understand that. Since I9505G firmware is hard to come by and att Galaxy S4 is similar in hardware as that of S4 Play Edition, Is it worth giving a shot to that. I am on att MVNO so, in theory, it should work.
---------- Post added at 11:49 AM ---------- Previous post was at 11:20 AM ----------
AndyYan said:
For what I know you *have* to use the full firmware for those partitions...
Click to expand...
Click to collapse
I found these files. Do they constitute *full* firmware with approx correct file sizes?
These are not the newest files so I will not be able to update the bootloader but assuming that I update after flashing these, it *should*fix it.
Thanks again for help.
fuzzychicken said:
I found these files. Do they constitute *full* firmware with approx correct file sizes?
These are not the newest files so I will not be able to update the bootloader but assuming that I update after flashing these, it *should*fix it.
Thanks again for help.
Click to expand...
Click to collapse
Looks "full" to me, though you don't need that PIT file unless the device is actually bricked.
AndyYan said:
Looks "full" to me, though you don't need that PIT file unless the device is actually bricked.
Click to expand...
Click to collapse
Thanks mate.
My Bootloader and baseband is 2 versions updated to this one. So I don't want to flash those. In that case, there is a mismatch. What troubles should I expect?
At the moment, the phone is working just fine except the cellular data. Worth the risk of going ahead?
ninjamuffinBV said:
Just install this kernel
https://androidfilehost.com/?w=file...2674a1a5ca61e20aa2c0b1cf1f6c99f1a46298b244ca6
heres is the xda link:
https://forum.xda-developers.com/galaxy-s4-tmobile/general/i9505oa7tw5-0leak-t3045729
Click to expand...
Click to collapse
how would I install this kernel?
I just started having problems with wifi in the stock SGH-M919 and custom roms. (Not sure what I did, radio problem, I think) This rom installed fine and the kernel fixed the wifi. Its connected and downloading updates now. The only thing I see so far (I just installed it), is that the camera crashes. I flashed twrp right off the bat. I will reinstall it all to check when I get a chance. Thanks
Update:
Odin 3.12,
flash the full (sammobile) M919UVUFOK3, wipe data, and the wifi doesnt work but camera does
flash the M919VWXUGOL1_Boot+Rec+Sys.tar.md5, wipe data, and wifi doesnt work but camera does
flash twrp-3.2.3-0-jfltexx.img.tar, still no wifi
TWRP,
install Lolli-Test-TW-07.02.2015.zip, and now wifi works but camera crashes
M919UVUFOK3 and Lolli-Test-TW-07.02.2015.zip dont work (just thought i would check)
I dont have an active sim card for this phone so I cant really test it completely. That kernel does fix wifi though.
Im not sure what is going on. I just did Odin the stock firmware (samsung-firmware) three times as well. I can get wifi to turn on like normal now but it will not connect to 2.4Ghz wifi. It seems like its in a loop. It works fine with 5Ghz though. I tried 3 different custom ROMs too. I have 3 other Samsung phones (and 3 printers) that work fine on my 2.4Ghz. I see that both stock firmwares flash modem, aboot, boot, recovery, system, sbl1, sbl2, sbl3, cache, hidden, rpm, tz and hlos. I dont know what Im missing here.
It works fine with 5Ghz so it has to be something in my software, right? I am really bummed that i didnt dd this phone before I started messing with this one. I wont ever skip that step again, lol.