I'm on the factory 5.0.1 image right now. What's happening is, when I download the OTA 5.1 image, it reboots and tries to install. Then I get the dead android with the red triangle.
I know that the answer is probably obvious, but I've been googling for about 3 days and can't find the original thread that had the instructions on how to install the custom modem. I know that if I put the factory modem back on, it will more likely than not fix the glitch.
I did NOT use Nexus 4 LTE flasher to update the modem, because at the time it wasn't working on Lollipop, I did the manual install method. Now that it is working, I downloaded it and tried to use it to install the stock modem. Well, that doesn't work, either. Dead Android on reboot.
Anyway, I can't find that original thread to manually install the factory modem firmware, so I can't do any OTA upgrades at this time.
Help me Obi Wan Kenobi, you're my only hope.
Nexus 4 5.1.0 LTE modem not working
theblooms said:
I'm on the factory 5.0.1 image right now. What's happening is, when I download the OTA 5.1 image, it reboots and tries to install. Then I get the dead android with the red triangle.
I know that the answer is probably obvious, but I've been googling for about 3 days and can't find the original thread that had the instructions on how to install the custom modem. I know that if I put the factory modem back on, it will more likely than not fix the glitch.
I did NOT use Nexus 4 LTE flasher to update the modem, because at the time it wasn't working on Lollipop, I did the manual install method. Now that it is working, I downloaded it and tried to use it to install the stock modem. Well, that doesn't work, either. Dead Android on reboot.
Anyway, I can't find that original thread to manually install the factory modem firmware, so I can't do any OTA upgrades at this time.
Help me Obi Wan Kenobi, you're my only hope.
Click to expand...
Click to collapse
I ran into the same problem. I used Skipsofts installer to dD/L the new 5.1 factory image and install because my OTA kept crashing.
Now I have lost 4g LTE on T-Mobile. back to 3G. I used Nexus Root Toolkit v2.0.5 to flash the LTE enabler but had no luck.
I'd like to hear how you are solving the problem? I did have LTE 4G while using Lollipop 5.0.2 but not since I went to 5.1.0
:good:
Related
Goal:
Latest firmware info from SamMobile
GT-I9505 Galaxy S 4 LTE
PDA: I9505XXUBMGA
CSC: I9505OXXBMG3
MODEM: I9505XXUBMGA
Previous set up:
Custom Recovery. Philz Touch
ROM http://forum.xda-developers.com/showthread.php?t=2352258
I has also attempted to update the base band when on this rom to MGA to the About device Baseband version stayed at XXUBMEA
Situation: I was getting lots of force closureswouldn'tentually it just wouldnt reboot, thenre-flashedvery failed. I reflashed the recovery and restored from wouldn'thowever it still wouldnt boot. (About 90% of the way through the bSamsungmation the audio samsung logo sound died. The Samsunghen went to the "samsung" static image with the blue LED light on and just stayed there... for about 30 mins before I force shutdown the phone.
I the attempted to flash stock ROM (listed in Goal above) downloaded from SamMobile. The same thing happened again. Boot gets stuck. I got into stock recovery and wre-flashedactory reset and reflashed. The ROM installed but I had no wifi. I then flashed the I9505XXUBMGA modem. Reboot and I had wifi. However About device still shows XXUBMEA baseband.
I wanted to see if I was able to get OTA updates from Samsung however Samsung update app is saying that the device is modified... so something isnt quite right yet. Im guessing it might be to do with the modem / baseband but to be honest I am a bit lost.
Screen shot of my current About Device Information. Also Device Status is showing as custom..
Thinking outloud here... would a Root->TriangleAway->reset counter etc->flash philz touch->full wipe for new ROM->boot to download->Odin flash stock fix it? Or could that do any further damage?
First install chainfires triangle away to reset your flash counter. For this you need root.
Then do a factory reset in recovery and flash stock with odin.
You wont get ota when flash counter >0 so give it a try.
Hopefully this helps
EDIT: If the new modem wont appear after a odin flash then uncheck the auto reboot option in odin and flash the modem twice, that helped for me.
Device Status is showing as custom, because you had flashed non-stock rom...
so the wifi not working, but can you make call??
The first time I flashed OMEGA ROM, wifi did not work, but flashed Adam kernel fixing the issue.
Look at his attachment, mobile connection seems working
@polcup please report back if it worked.
cellegg said:
Device Status is showing as custom, because you had flashed non-stock rom...
so the wifi not working, but can you make call??
The first time I flashed OMEGA ROM, wifi did not work, but flashed Adam kernel fixing the issue.
Click to expand...
Click to collapse
Wifi is now working after I flashedlashed the I9505XXUBMGA modem. Rebooted and I had wifi. However About device still shows XXUBMEA baseband.
Calls and mobile date is fine.
_sebha said:
Look at his attachment, mobile connection seems working
@polcup please report back if it worked.
Click to expand...
Click to collapse
Yep, I will try that over lunch and see if it works. Not sure that will get me to the XXUBMGA modem though but its certainly a step in the right direction.
I really appreciate both your replys. Thanks.
Look at my edit in first post.
Uncheck auto reboot in odin and flash only the modem twice (manual reboot to download mode after first flash) after second flash reboot device.
That worked for me
_sebha said:
Look at my edit in first post.
Uncheck auto reboot in odin and flash only the modem twice (manual reboot to download mode after first flash) after second flash reboot device.
That worked for me
Click to expand...
Click to collapse
Superb! I will try that as well. Thanks!!
Update
I was unable to root I9505XXUBMGA. CF-Autoroot didnt stick. I tried a couple of installs. One through Odin and one through CWM. Neither took.
I flashed an older pre-rooted stock rom I had XXUBMEA and then ran Triangle away. It returned the counter to '0' and brought the status back to official.
So now im back to stock MEA and to be honest I am happy to stay here for a bit. I will maybe move up to MGA if I find a pre-rooted version.
Thanks for your help.
Sorted!
Hello everyone, i'm a new member. I apologize if my english is not good enough.
After been driven insane by one pre-installed app from my Operator (Claro Peru) i decided that it was time to root my device to get rid from that pest. I'm a noob, so i started to investigate about the safest methods to not damage my phone. My Device's model is SGH I337m.
The plan was to update the FW from JB 4.3 that came with my phone to 4.4.2 and then proceed to root. I downloaded the Canadian 4.4.2 FW with build version I337MVLUFNC1 and installed manually with Odin. After the phone rebooted, my S4 was upgraded with 4.4.2 but Samsumg keyboard was going insane, so i went to the apps and solved that cleaning the cache/data. Then i noticed that the Wifi wasn't connected, i tried to turn it on, but then a message with a shield appeared saying that my device security stopped the operation. Beliving it was only a problem with KNOX, i installed autoroot (CF-Auto-Root-jfltecan-jfltevl-sghi337m) with Odin, open SuperSU and stopped it from working, but the Wifi still wouldn't connect.
So the first thing that crossed my mind was to unroot and do a factory reset, didn't work. The FW still was 4.4.2, so i´ve been searching solutions with this FW because i've read some cases of devices that stopped working completely after trying to do a downgrade. so i don't want to go to that route for now.
After a couple hours of search, some solutions i found on the forum were:
- Install Faux123 Kernel (Found on Youtube, this would be the thread i think http://forum.xda-developers.com/showthread.php?t=2273437http://forum.xda-developers.com/showthread.php?t=2273437
- Flash a modem for i337m
- Safestrap recovery and bypasslkm.zip
- Downgrade
I haven't tried any of this methods because i dont want to get into a deeper trouble. In the first solution i'm not sure what to do because this is the files the author recommends for canadian models (i337m), but when i enter here http://faux.romhost.me/jflteatt/jb42/http://faux.romhost.me/jflteatt/jb42/ only jflteatt appears, and that would be i337 model, isn't it? I thought that installing it may cause more troubles, so i didn't do it.
For the flashing modem method, i'm not really sure if installing a modem from another country would get me in trouble, so again i didn't proceed.
I found the Safestrap and recovery method on a downgrade thread for the i337, so again, didn't do it.
So, is there a way to get one of this methods working on i337m to get wifi working again, or is there any other better method to get back wifi.
I would really appreciate any help you can give me guys.
Copellius said:
... My Device's model is SGH I337m.
The plan was to update the FW from JB 4.3 that came with my phone to 4.4.2 and then proceed to root. I downloaded the Canadian 4.4.2 FW with build version I337MVLUFNC1 and installed manually with Odin. After the phone rebooted, my S4 was upgraded with 4.4.2 but Samsumg keyboard was going insane, so i went to the apps and solved that cleaning the cache/data. Then i noticed that the Wifi wasn't connected, i tried to turn it on, but then a message with a shield appeared saying that my device security stopped the operation. Beliving it was only a problem with KNOX, i installed autoroot (CF-Auto-Root-jfltecan-jfltevl-sghi337m) with Odin, open SuperSU and stopped it from working, but the Wifi still wouldn't connect.
So the first thing that crossed my mind was to unroot and do a factory reset, didn't work. The FW still was 4.4.2, so i´ve been searching solutions with this FW because i've read some cases of devices that stopped working completely after trying to do a downgrade. so i don't want to go to that route for now.
After a couple hours of search, some solutions i found on the forum were:
- Install Faux123 Kernel (Found on Youtube, this would be the thread i think http://forum.xda-developers.com/showthread.php?t=2273437http://forum.xda-developers.com/showthread.php?t=2273437
- Flash a modem for i337m
- Safestrap recovery and bypasslkm.zip
- Downgrade
I haven't tried any of this methods because i dont want to get into a deeper trouble. In the first solution i'm not sure what to do because this is the files the author recommends for canadian models (i337m), but when i enter here http://faux.romhost.me/jflteatt/jb42/http://faux.romhost.me/jflteatt/jb42/ only jflteatt appears, and that would be i337 model, isn't it? I thought that installing it may cause more troubles, so i didn't do it.
For the flashing modem method, i'm not really sure if installing a modem from another country would get me in trouble, so again i didn't proceed.
I found the Safestrap and recovery method on a downgrade thread for the i337, so again, didn't do it.
So, is there a way to get one of this methods working on i337m to get wifi working again, or is there any other better method to get back wifi.
I would really appreciate any help you can give me guys.
Click to expand...
Click to collapse
ok so you have the i337m canadian version... making anything related to safestrap and the att i337 irrelevant, completely different methods so don't get them confused lol
you were updating from stock 4.3 right? your best bet is to factiry reset and reflash stock fw for 4.4.2 before you brick your device... kitkat is very different from 4.3, maybe read up on it a bit too...
for ex, the "message with a shield appeared saying that my device security stopped the operation" isn't related to needing to root, it's an option under security settings.
to enable superuser on kitkat you need to enable developer options, then enable superuser. I prefer supersu so manually install that from play store afterwards. I recommend checking and/or enabling this as soon as the phone completes booting up after flashing.
also I think there's a known issue w/ 4.4.2 and wifi not turning on until after 2nd boot completed if I rememebr correctly, been using 4.4.4 for awhile now though so could be wrong...
good luck and check out the help section :angel:
I was rooted on 4.2.2 with Rogers but wanted to update to 4.4.2 and didnt really use the root anyway. So i installed back the stock rom and resetted to factory. But now wifi wont turn on at all. I ran the softaware update and im still on 4.2.2 and it says I have the latest version available but i know rogers released 4.4.2 in march 2014...
Anyway, which way should i go to get everything working again?
Thanks
I don't know if anyone has explained why this happens, but sometimes the modem firmware doesn't completely "take", leaving parts not working correctly. Reflashing the modem usually corrects this. In your case, where you want to upgrade to the latest firmware, you should download it from sammobile.com and flash it through Odin. Not only will you not have to worry about a software update, but installing the updated ROM through Odin should correct your WiFi issue as a new modem will be flashed with the firmware.
downloading now, i'll report back
fixed thanks a lot
I rooted to 4.4.2 and it went fine- then I realized I had lost wi-fi.
I have tried to restore and tried using odin and zip files to install a stock rom after I found a similar problem with link on
Sprint forums saying it will fix the ""button won't stay on" but the fix only works if the device is in stock rom.
answer on Sprint forum says baseband version was mk2 needs to be nae.
Return the phone to stock, run the fix for the wi-fi and then re-root.
I have downloaded and ran several roms that say they are stock- I've factory reset, cleared cache, no matter what I do,
I end up with a rooted device in 4.4.2 and no wi-fi. If I could just get the wi-fi back I would take it at this point
This was just a little quick upgrade that turned bad and long
The Sprint forum had a link to get it to nae, but wont work if rooted., so need to put the phone back to stock- run the patch and then can upgrade to kit kat again
TLDR: I cannot get my Sprint s4 back to any version that isn't rooted. I have tried several (lots) of roms that say" stock-unrooted" rom,
Never goes back to stock- stays rooted without wifi-
Ran a rom VPUAMDC_L720SPTAMDC_SPR but when I install I get msge "ifooter is wring signature invalid" - and it fails.
reformatted the sd card, tried different roms and get some message and it stays rooted and no wifi.
TLDR: need to get stock rom so I can get back wi-fi and then root the whole thing. as 4.4.2 Or 4 , if it exists)
Any options and any ideas as to where or what to do?
EDIT: for clarity cause I am not making much sense at this point
Thanks
Heh... a TL;DR for a TL;DR... the internet is becoming one crazy place.
thousandwatts said:
The Sprint forum had a link to get it to nae, but wont work if rooted.
Click to expand...
Click to collapse
Maybe a dumb question, but why not just unroot first, then?
Hi there! Recently I updated my phone after using KitKat for quite a while as I grew a bit bored of KitKat and thought Lollipop would do some good. Previously, I had KitKat then went to Lollipop but I didn't like Lollipop so I flashed to KitKat. Then, after some time I am where I am now, stuck on Lollipop. So I am trying to revert back to KitKat again, but on my computer after I load KitKat into Odin and press start, the console log gets stuck on aboot.mbn. Everything works fine until that point, which it then just sits there. My phone also displays a loading bar on the download mode, but sits at the very beginning. Something is wrong here. I would really appreciate any help.
Somethings you may need to know:
- Yes I have successfully gone back to KitKat before on the same phone.
- I have the correct Verizon Retail KitKat Software
- I have Odin 3.0.9
- I am running 5.0.1
- I have done a factory reset and cleared cache partition as well, but nothing seems to work.
Thanks, I look forward to your feedback!
Did you update OTA or flash the safe 5.0.1 update using odin? If you took the OTA upgrades then you are stuck, you will NOT be able to flash that phone again.
Sent from my Galaxy Note 4 using Tapatalk
outcasted2003 said:
Did you update OTA or flash the safe 5.0.1 update using odin? If you took the OTA upgrades then you are stuck, you will NOT be able to flash that phone again.
Sent from my Galaxy Note 4 using Tapatalk
Click to expand...
Click to collapse
I did download a security update after the initial 5.0.1 update, so I'm guessing that's what's doing it? Right after I posted my thread I saw the warning in this forum area, so I think that may be the case. I guess oh well, think there maybe a solution in the future for KitKat? Lollipop isn't too bad after a reset but I would prefer KitKat over time.