I'm using a stock ROM I flashed through Odin a while back after bouncing around some different custom ROMs. I have OCLF installed. I got the notification for the update, chose to install, within 5 seconds my phone rebooted but nothing changed. I still have the same software. If I check for updates I get the no firmware message again. What am I supposed to do to get the update?
Just flash the update via oden. Thats what I did. I got tired of waiting.
You're supposed to look for the change in the baseband version, should read something like T959UVJ16. This isn't a firmware change, just an update.....
Mine did the same thing and my baseband shows the above. I've heard Media Hub works after the update, which mine doesn't, and I don't see task manager anywhere.
I have UVJI5 update installed from Kies, is it possible to flash this update over it.
Sent from my SGH-T959 using XDA App
My baseband hasn't changed. Still JFD.
Related
Hi
I wake up and have an update-from-tmo message . The think is that I already have the OTA JI6. does anyone knows something about this?
Anyone?..................
I haven't heard of any other update since J16.
Did you update manually to J16 or use the OTA?
Yeah, how did you update to JI6?
Install it and let us know if your firmware/baseband are the same.
I had Bionix 1.9, which already had the official OTA JI6 version. Still got the message T-Mo about the update, so I just updated it and everything seems fine. Didn't have any problems.
I have a similar problem. I had the update message but didn't want to apply it since I read about all the horror stories. I manually updated to JI6 and baseband version, etc., all reflects this (as does media hub being unlocked, hd camcorder, GPS working, new sorted gallery and other fixes). However, I still have the damn notification that pops up constantly. How do I get rid of it??
I 1st tried OTA but it got stuck on the vibrant screen so I odin the JI5 but ended up with the JI6. Don't ask me how. The odin files I have in my comp are the JI5. Another thing is that I was rooted when I OTA the JI6. Ended up with JI6 rooted
finally upgraded from DI01 to ED01 and have discovered a problem. the 4 buttons on the bottom of the screen now act weird. they will light up, go out, or flicker depending on what im doing. never had this problem before and i havent seen anyone else post about it but i could have missed it. anyone have any idea?
Did you update stock di01 to stock ed01 or between custom roms?
Sent from my SCH-I500 using XDA Premium App
no, i tried the OTA update several times with the end result being the server IP error. unrooted and tried again several times with the same results. then i followed the link in another post and flashed with odin, the DL09. tried again several times to get the OTA update with no success. had to flash that several times and then finally got it to install. as it sits i am running ED01 stock but rooted. my wifes phone had had all the OTA updates and has always run stock, not even root and has some problems with the buttons as well.
try reflashing a kernel... i only dealt with that problem once a while back and i just reflashed everything and that seemed to fix it.
Also i used to restore system files from titanium backup and sometimes it didn't play nice with whatever i upgraded to and that would cause the backlights to bug out before i got force close messages.
Took an OTA update this AM in the US, but nothing seemed to change. Switched back to stock recovery, took update, downloaded, installed (no errors), rebooted, message said somethings about a Pre-Install APK, then nothing. Tablet info says I am now up to date, but nothing else seems to have changed.
I'm still on custom kernel (thor's), still on 3.1. I forget the GEN info, but I don't think that changed either.
Was this a pre-update update?
I got the update too.
Seemed to freeze up on me after installing (Gave it about 15 minutes on a black screen after installing, before I gave up). I had to power it off and back on. After booting, I got a message that the "Update Was Successful"
Kernal Number is: 2.6.36.3
Build is 4.010.13_COM_GEN2
But still Android 3.1
Ditto. Used stock recovery and unroot to get it to install. It's Gen 2.
Sent from my ADR6300 using XDA App
Same here, updated with no errors. Didn't lose root and it still says 3.1
With the update to 3.1 they sent out a smaller update a few days earlier. This one may be the same thing.
It's just a small update, about less than 20MB download. But I have no idea what's been changed.
GShyneDM said:
I got the update too.Same thing happaned to me
Seemed to freeze up on me after installing (Gave it about 15 minutes on a black screen after installing, before I gave up). I had to power it off and back on. After booting, I got a message that the "Update Was Successful"
Kernal Number is: 2.6.36.3
Build is 4.010.13_COM_GEN2
But still Android 3.1
Click to expand...
Click to collapse
Same thing happened to me...
System Update
System Update 4.010.13
(14.49MB).
A new system update is available for your device. A network connection is required to download and update your device. You may incur additional charges from your service provider. Thank you for not replacing me with the HP TouchPad.
Click to expand...
Click to collapse
i'm gonna hold off on installing this until i know more of what its all about...
I uploaded the zip in development, I don't think I'm gonna install either...
I also installed the 14MB update today. The tablet was rooted, but otherwise stock. After the update the tablet remains rooted. I have experienced no other issues.
Cheers,
A
I had the same experience as above. So far no issues.
This actually made me worried about the possibility of us to get an update to 3.2 on 8/25. Otherwise, they should just pass this incremental.
Does anyone know which is newer, and what changed between the two?
I have XXUAME2, and I've updated my firmware through Kies. I don't remember what I had before. This one must be newer.
Haven't noticed any change, apart from the blue default background in the wallpapers is now a bit darker without the sun flare. I might've noticed a few very minor things in the settings, though I don't remember what they were.
Well I was on XXUAMDC when I first got my handset, and flashed XXUAMDN via Odin when getting root access. I found it removed any carrier branding and fixed a bug with the standard launcher not allowing sorting apps in folders properly. Just wondering if XXUAME2 is newer and fixes anything else.
StuartTheFish said:
Well I was on XXUAMDC when I first got my handset, and flashed XXUAMDN via Odin when getting root access. I found it removed any carrier branding and fixed a bug with the standard launcher not allowing sorting apps in folders properly. Just wondering if XXUAME2 is newer and fixes anything else.
Click to expand...
Click to collapse
I'll tell you a sad story about XXUAME2.
I rooted my phone a few weeks after I got it, everything worked fine. Then I saw the firmware update in Kies, sure I'll download! I already knew updating stock firmware would remove root, but I could always flash it again. So after I updated my firmware, I flashed root again. This time the phone couldn't recognise the superuser app, and kept alerting that there was a threat (meaning the superuser app) every 5 minutes but root still worked. So I removed superuser completely. The threat messages didn't stop, though. I flashed a clean stock ROM, everything was fine.
Until, an ancient evil awakens! (not really ancient, but...) My Group Play app started acting weirdly. It was constantly 50-70% of my battery drain, even above the screen, on my battery page. I freezed the app and hoped for the best, but it didn't work. I couldn't remove it because my root messed up. BetterBatteryStats didn't recognise anything odd. I asked XDA, but my thread only got 1 answer telling me to look for updates, and none were to be found. Google didn't tell me anything. So I gave up, and did a factory reset. I didn't really mind, I got the phone back running and looking the same in one evening, it's not as if I had years worth of stuff in it yet. This was 2 days ago, and everything seems to be pretty much normal.
I probably messed up somewhere, but thought I'd still write a cautionary tale about updating firmware while rooted. As I mentioned, probably nothing of importance was updated, so it would be a little safer to not update. You won't miss out.
Tozenator said:
I'll tell you a sad story about XXUAME2.
I rooted my phone a few weeks after I got it, everything worked fine. Then I saw the firmware update in Kies, sure I'll download! I already knew updating stock firmware would remove root, but I could always flash it again. So after I updated my firmware, I flashed root again. This time the phone couldn't recognise the superuser app, and kept alerting that there was a threat (meaning the superuser app) every 5 minutes but root still worked. So I removed superuser completely. The threat messages didn't stop, though. I flashed a clean stock ROM, everything was fine.
Until, an ancient evil awakens! (not really ancient, but...) My Group Play app started acting weirdly. It was constantly 50-70% of my battery drain, even above the screen, on my battery page. I freezed the app and hoped for the best, but it didn't work. I couldn't remove it because my root messed up. BetterBatteryStats didn't recognise anything odd. I asked XDA, but my thread only got 1 answer telling me to look for updates, and none were to be found. Google didn't tell me anything. So I gave up, and did a factory reset. I didn't really mind, I got the phone back running and looking the same in one evening, it's not as if I had years worth of stuff in it yet. This was 2 days ago, and everything seems to be pretty much normal.
I probably messed up somewhere, but thought I'd still write a cautionary tale about updating firmware while rooted. As I mentioned, probably nothing of importance was updated, so it would be a little safer to not update. You won't miss out.
Click to expand...
Click to collapse
The reason for that is chainfire's root method doesn't work for newer versions (or should I say didn't, apparently it does now). The newer kernel didn't allow root access, making the su binary appear to be missing. The error messages are also normal on newer versions, since it detects something is trying to get root access. To get around the missing binary issue, you can use djembey's modified version of getting root instead, which afaik installs the older kernel again so it can actually get root. Then to get rid of the repeated error messages, you have to disable KNOX. Again, it says how in djembey's root thread.
XXUAMDN is one of the newer versions which didn't work via chainfire's method, yet I have root access with no issues after following djembey's thread. Might be worth a look to get yours sorted.
StuartTheFish said:
The reason for that is chainfire's root method doesn't work for newer versions (or should I say didn't, apparently it does now). The newer kernel didn't allow root access, making the su binary appear to be missing. The error messages are also normal on newer versions, since it detects something is trying to get root access. To get around the missing binary issue, you can use djembey's modified version of getting root instead, which afaik installs the older kernel again so it can actually get root. Then to get rid of the repeated error messages, you have to disable KNOX. Again, it says how in djembey's root thread.
XXUAMDN is one of the newer versions which didn't work via chainfire's method, yet I have root access with no issues after following djembey's thread. Might be worth a look to get yours sorted.
Click to expand...
Click to collapse
Interesting, very interesting. I might look into rooting one more time, then. Thanks!
Funny how you helped me instead of the other way around. Thanks again, I hope more people notice your thread and maybe you'll get your answer!
where is this new firmware xxuamdn, havent found anything about it..
im having camera, battery drain, slowness issuess still hope it fixes..
Sent from my GT-I9500 using xda app-developers app
I have none of those issues, but never did even on the older version. All I did was Google for galaxy s4 update and I found a download link for it along with Odin. But there's also XXUAME2 out there and I don't know which one I'd be better having. Unless the only difference is the radio depending on where in the world you are?
Alright, I have a Virgin Mobile S4. I rooted it a year ago with towelroot and installed clockwork mod on it to install cyanogenmod. I tried it, didn't like it so I restored my backup of the stock rom using CWM.
Fast forward to now. I tried to update my S4 OTA for Lollipop, but it would give me an error. I figured it was because I had changed the recovery software. So I went and downloaded the virgin mobile lollipop stock rom from sammobile. ( I337MVLUGOC4_I337MOYAGOC4_VMC ).
I tried to flash it onto my S4 using Odin 3.09. To no avail, it always failed at the system4.img.ext or something. From there I tried to make it work by using 3.10. Still failed. I googled for a fix or workaround and found something about reinstalling clockwork mod. I also tried reinstalling the PIT file for I337M. It was still not working. So I tried to flash back to my stock backup.
1st time I flashed, I kept having program that didn't want to start errors. I wiped dalvik, I wiped cache, I factory reset. Still bugged. So as a last resort I restored the backup again after having done all this. It worked! But...
Well, I'm at a lost now, I can't update using OTA, I can't update with Odin, I can't update with Kies. Now what? Is there a way to go back to the stock recovery and let the OTA or Kies update go through unhindered?
BTW, I had a problem when trying to use EFS professional to backup my EFS before the procedure. No matter which port I used ( front port or back motherboard port ), I could never make the backup, it said something about the phone currently being offline or something.
Anyway, I'd prefer to be able to switch back to the stock recovery and let the OTA or Kies do its thing. Any clues?
EDIT UPDATE: After fiddling some more around, I changed usb port again and reflashed using a more up to date version of Odin and I finally have Lollipop on my device, only problem is that I have no 3g or 4g connectivity even tho the IMEI, baseband and SMS as well as calls work just fine, what's wrong?
See first post edit^^
Diabo|ik said:
EDIT UPDATE: After fiddling some more around, I changed usb port again and reflashed using a more up to date version of Odin and I finally have Lollipop on my device, only problem is that I have no 3g or 4g connectivity even tho the IMEI, baseband and SMS as well as calls work just fine, what's wrong?
Click to expand...
Click to collapse
Did you check the APN settings? Make sure you have the right one for your carrier.