If you have Updated your Vibrant to the J16 and you had no problems, or if you updated and you now have problems. Please post it here. I would like to see some numbers on how well this is working out. I personally am waiting to update, I just keep postponing the update.
Post in this format
Hardware locked or not-Rooted or not-Any other mods-J16 worked or not-If J16 worked, is GPS better
Please follow the above format and keep questions to a minimum. This is just to see the totals of how the J16 is working out.I will update the numbers as we go.
J16 worked - 3
J16 not working - 1
Working on 1 phone
Didn't work on the other.
On the one it's working on, the only unusual sw added was OCLF, Titanium, CWModRecovery. I installed those on a stock phone long enough to make two backups and then removed all traces including the update.zip that cwmod left behind. The tmo update went just fine.
I only removed OCLF on the other and had a bricked phone after the update.
Would've been easier if you made it a poll.
I updated via ODIN, and it's passed the tests with flying colors.
Related
I updated my vibrant today via kies to JI5. Immediately prior to that I did a nandroid backup. I was experiencing some buggy things after the update, and then I saw that Samsung pulled the update. So I decided to revert back to my previous build. I ran Clockwork recovery and did the nandroid restore. It all seemed to go well. Rebooted the phone and now, well, its stuck on the Vibrant Samsung screen. Nothing else happens.
Did I do something wrong? Is there a way to get back to my previous build, or even back to original stock condition??
PLS help...thanks.
BTW- I can manually get into recovery mode, so i guess I am not hardware locked. I just don't know what the best thing to do next. Thanks.
The new build has a different kernel that is not compatible with previous builds. You can download odin, the 512 pit file and the original JFD tar file and restore to stock that way. After that you can use your nandroid backup to get back to where you were.
doenloading files now
thanks so much...i will try that! fingers crossed.
WORKED! Thanks so much.
What "buggy" things and what did you have installed on your Vibrant before you did the update.
This? Which is 100% your fault?
http://forum.xda-developers.com/showthread.php?t=795390
heygrl said:
What "buggy" things and what did you have installed on your Vibrant before you did the update.
This? Which is 100% your fault?
http://forum.xda-developers.com/showthread.php?t=795390
Click to expand...
Click to collapse
You're right. The settings thing was my fault by installing the wrong MobileAP. But there were other strange things happening as well. A lot of force closes with widgets - particularly "word clock." Also, the phone would freeze and the display would stay on whenever I received a text message.
I guess it's possible that all of that was the result of the wrong MobileAP. But the fact is that the update was pulled due to "known issues" according to Tmo. So its safe to assume - at least for me - that this update is not ready for primetime.
EDIT: To be more accurate - the update was pulled by Samsung for reasons unknown. Tmo then tweeted that the update had "known issues." And now there appears to be a JI6 roaming around. So if JI5 were perfect, why the JI6?
pdefazio said:
You're right. The settings thing was my fault by installing the wrong MobileAP. But there were other strange things happening as well. A lot of force closes with widgets - particularly "word clock." Also, the phone would freeze and the display would stay on whenever I received a text message.
I guess it's possible that all of that was the result of the wrong MobileAP. But the fact is that the update was pulled due to "known issues" according to Tmo. So its safe to assume - at least for me - that this update is not ready for primetime.
EDIT: To be more accurate - the update was pulled by Samsung for reasons unknown. Tmo then tweeted that the update had "known issues." And now there appears to be a JI6 roaming around. So if JI5 were perfect, why the JI6?
Click to expand...
Click to collapse
I had little issues after I updated to JI5. Swype was very inaccurate, other keyboard were very buggy as well. GPS was not working very well, and there was more lag than before. So I did a reset and all of those bugs went away.
i just flashed bionix 1.3 from JI5 through clockwork with no issues.
Wierd that you had any...
adm1jtg said:
The new build has a different kernel that is not compatible with previous builds. You can download odin, the 512 pit file and the original JFD tar file and restore to stock that way. After that you can use your nandroid backup to get back to where you were.
Click to expand...
Click to collapse
Ok, I just flashed from JI5 to bionix 1.3 through clockwork with no issue. Or does JI5 and bionix have the same kernal? hmmmm
My coworker is not able to OTA update her completely stock (never rooted/modded) Facinate to 2.2, but when she goes to System Updates->Check New, there is a pop up that says "Please Wait" that stays on the screen for a while, then just goes away and nothing happens.
Also, if you go to System Updates->Status, it says "Server Unavailable" Code: 500.
The only thing I can think of is that Verizon is only letting particular regions update at a time to prevent the server from bogging down. Any ideas?
Verizon seems to be having network issues since 2am. Even if you have a data connection, they probably offlines the OTA servers until the problem is resolved.
http://community.vzw.com/t5/4G-Disc...TE-outage-ETA-for-repair-and-other/m-p/513354
She is on stock DI01, and we downloaded the Verizon official ED01, but it says that it cannot find EA28. So, we downloaded EA28 official zip, and now it says that it cannot install because it needs DL09. Sooooo, should we now look for DL09? There has got to be a more simple way...
I'd leave her at stock and just be patient. Verizon's system will come back.
still down
I am having the same issue, even tried the DL09 no luck
I've had the same issues since the day the update came out but I had ODIN'd EB01 and then ODIN'd back to Dl09 and tried everything but got the server unavailable issue. I gave up and just flashed the ED01 update.zip.
After a lot of trying different things and giving up, an awesome dude posted the solution here: http://forum.xda-developers.com/showpost.php?p=13313409&postcount=12 . I followed the steps and it worked like a charm.
If it helps, my wife's stock, never rooted fascinate had the exact same problem, and using whosdaman's awesome post, I used the stock recovery to manually install froyo- it's still completely stock, and worked like a charm:
http://forum.xda-developers.com/showthread.php?t=1044230
artvandelay440 said:
If it helps, my wife's stock, never rooted fascinate had the exact same problem, and using whosdaman's awesome post, I used the stock recovery to manually install froyo- it's still completely stock, and worked like a charm:
http://forum.xda-developers.com/showthread.php?t=1044230
Click to expand...
Click to collapse
This method is well known, but the OP was asking about OTA.
Ok so I followed the guide at http://forum.xda-developers.com/showthread.php?t=1057003&page=8 and in the end I picked GreyBlur.
Now I get asked if I want to OTA my cell and I think its due to my system version reading back "Version.4.1.57.MB860.ATT.en.US" and I'm sure thats due to installing GreyBlur, It really should read as a Telstra system version instead but it would appear GreyBlur changed it to ATT.
Anyway of resolving this ?
you should change the title to after installing grey blur (some people may think there is an telstra OTA to be had). this is because the build prop is for the AT&T version as grey blur is based off of that and the update was pushed out to the masses yesterday. you could change the build prop file I guess. which line exactly and to what Im not exactly sure. when greyblur gets updated with the current firmware like gingerblur was, it will cease.
Well I modified the build.prop file to display 1.83 as the system version and so far this has not worked to resolve my issue with the OTA update nag.
I have even gone as far as to rename the otacerts.zip file to otacerts.bak in hopes it would prevent OTA updates and that has not worked either.
I by no means a newbie when it comes to figuring things out or following instructions so my next attempt will be to copy the build.prop file from GingerBlur 3.1 over mine and see what happens.
Ok tried replacing the build.prop file with the one from Gingerblur 3.1 and still I get the OTA nag so not sure how to resolve this, any ideas would be wonderful ...
Interesting, then it appears its reading the info from somewhere else. Here's two things you can try.
check your about phone and make sure the changes were pass through.
Check on the motoblur site if it still reads your device at 4.1.57.
It doesn't look like a greyblur is coming for a couple of days since Ken is on exams.
Ok checked to make sure the changes took effect on the phone and they read back "4.1.83.MB860.ATT.en.US" just how I wanted it so then I checked the motoblur website and it as well reads back the same thing "4.1.83.MB860.ATT.en.US" so I'm stumped as to why it continues to tell me there is an available update for me.
Of course as of today I've been getting a different message which says "This update has been recalled. No action required." This message pops up every so often and is more bothersome then the last lol.
Anyways I guess I'll just wait to see what comes down the pipe on the new release of GreyBlur, One thing is for sure some people out there MAY by mistake take the ATT 1.83 update and I think it would soft brick there phone as I'm fairly sure OTA updates overwrite the bootloader as well as opposed to the SBF updates.
yeah I mentioned that in another forum as well. The other thing is that some people that are on the actual 1.83 are getting the notification as well for some reason.
i'm on the new update had it for a week now(did sbf), i've not had the problems that some have mentioned having, it seems to be running great, BUT I have noticed more wifi disconnects since the update, and not sure why because i'm close the the router and have perfect signal and not using bt either.
Ok so what I've done is froze updater 2.2.1 with Titanium Backup and so far so good no more OTA update nags, Will post back if this doesn't hold.
Does anybody know a way to disable OTA updates on Thunderbolt? I have a rooted phone, and don't want to deal with updating for now. My problem is the OTA updates cause the phone to reboot, the update fails and then I have to reboot into recovery, clear the caches, reboot again. It's a pain, and it seems to be happening at least once a day now.
Any hacks out there I can apply to disable the OTA updates?
botzen67 said:
Does anybody know a way to disable OTA updates on Thunderbolt? I have a rooted phone, and don't want to deal with updating for now. My problem is the OTA updates cause the phone to reboot, the update fails and then I have to reboot into recovery, clear the caches, reboot again. It's a pain, and it seems to be happening at least once a day now.
Any hacks out there I can apply to disable the OTA updates?
Click to expand...
Click to collapse
If you have Titaniumbackup Pro then just freeze the update/updater apk. If not, I would suggest getting it, it is well worth the cost.
Great suggestion. I have TiBu Pro and have frozen the two Update apps I found in the list along with "VZW Package Installer 1.0" and "Field Test 2.1-update1" and "Field Trial 2.2.1", having done the last three just now. It did try to do yet another update a few hours ago, so we'll have to see if the last three do the trick.
Anybody got any other suggestions for Apps I should freeze to prevent OTA updates?
Update: None of the items I've frozen seems to have made a difference. Still looking for other ideas.
I'm thinking it was DM.apk or something similiar that controlled ota updates. I don't have a stock rom running atm so i can't be sure. When you find the correct one you won't be able to get to the update phone screen from settings any longer. Wish i could be more help but i just can't remember.
Sent from my HTC ThunderBolt using Tapatalk
I was having that same problem and I just broke down and applied the update. I used clockwork rom manager and a rooted/deodexed update file that I found on the forums (linked from androidpolice, i think). Flashed the update, without wiping the current setup, then flashed the radio from the bootloader. Worked like a charm. I've got the update, it's not searching for more, and it reinstalled all the bloatware that I deleted instead of freezing when I got the phone. I went back through and freezed all the bloat junk, and my TB is running better than ever. Oh, and I'm just running a rooted stock rom.
I too suffered the same problem. I just ended up installing a custom rom to get rid of it for good. Best decision I ever made, I really like the Synergy build.
Long story short I have an M7 running 4.4.2 on AT&T that I haven't touched in about a year. I just booted it up everything is working properly except when I go to Software Update it tells me the software is up to date and that I can check again in 24 hours.
I've tried rebooting, no luck. Any other ideas? Thanks!
When you say you haven't touched it in a year, do you mean you don't use the phone at all? Or that you just haven't updated or modified it? If you just don't use the phone and don't mind starting from scratch you can run the 7.23.502.1 RUU. You can download it directly from HTC, http://www.htc.com/us/support/rom-downloads.html. I used this a couple of weeks ago and everything went smoothly and the phone runs great.
If you don't want to go that route and want the OTA, some have suggested changing the date on your phone ahead a few days and trying Software Update again. It may trigger the update. I have never tried that so can't say for sure if it'll work. And I haven't seen the OTA zips posted to update it manually.