Just updated to 1.4.1 and it works fine, except for the glaring fact that there is no service, and WiFi doesn't work (it can see the router, but turns off after half a second). amss.mbn couldn't be flashed earlier during the update process.
If its a Problem with Steve's Rom then can you post in the correct thread and not start a new thread thanks
Related
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.
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.
Hey gang. Have to post this here until the post count goes higher.
I've been installing the updates for DSC as they are released, due to the nagging wifi freeze issue. Everything else works great.
However, something changed after .63b, perhaps the wifi_supplicant mod?
While at work, no ROM after .63b will authenticate to the WIFI. It scans and attempts connect 3 times, then goes to disabled.
Re-running ROM install for 63b and then new DSC_Test.zip (I like reboot menu option) works like a champ. Wifi freezes still occur, but are relatively infrequent. I'm on 406 Baseband.
As such, I'm unable to install the new .7, or anything after .63b.
I haven't seen anyone else mention a similar problem, perhaps they're only dealing with a single network. I use two, my home network and work network. My home network is WPA2 AES encryption, and seems to work fine with updated ROMs. My work network, nothing after .63b.
Just tried .7b again, nothing.......reloaded .63b, wifi fine.
Just wanted to bring this up. Thank you all so much for your efforts. Still the best ROM, and the best ROM support available.
Have you tried flashing Olleh kernel from Phoenix release post?
I believe I have, but was a while ago. I'll go try it again, to be sure. Thx.
UPDATE: tried several updated kernals, no avail. As soon as .6b, then .63b go on, my WIFI connects immediately. It's not in the kernal, but the ROM/framework.
I recommend a factory reset after flashing .7
Let's check this:
http://www.littlemaruko.com/Nopteam/DSC_Check.zip
--
It will revert WiFi-related binaries to 407.
--
And be sure to flash Olleh kernel, it's the only actual thing that was changed in 0.64b
I recommend a factory reset after flashing .7
Click to expand...
Click to collapse
Ya, I had done resets and cleans installs on the earlier releases after .63b, all had the same issue...WIFI connects to home network, but not work network (801.x EAP)
As everything is configured and re-installed now, its easier to reload .6b and .63b, without reloading everything.
_n0p_
Let's check this:
http://www.littlemaruko.com/Nopteam/DSC_Check.zip
--
It will revert WiFi-related binaries to 407.
--
And be sure to flash Olleh kernel, it's the only actual thing that was changed in 0.64b
Click to expand...
Click to collapse
Looks like you're onto something here. Have both the Olleh kernal and the DSC_Check loaded and my work WIFI authenticated properly.
Since changing 2 things at once isn't proper troubleshooting protocol, I reloaded .7b. WIFI problem came back. Reloaded DSC_Check (not Olleh Kernal), and WIFI is fine now. So there's something in those binaries my work network wouldn't authenticate to.
If I can help you figure it out, I will. All working now though. You the man!
It's enough info. I'll revert to 407 wifi binaries in future releases.
--
I just wish we figure it out before 0.7 release
It's enough info. I'll revert to 407 wifi binaries in future releases.
--
I just wish we figure it out before 0.7 release
Click to expand...
Click to collapse
Sorry about that......it was the .7 release not working that finally motivated me to speak up.
Thank you for keeping the Streak relevant and rockin.
rodeorat said:
However, something changed after .63b, perhaps the wifi_supplicant mod?
While at work, no ROM after .63b will authenticate to the WIFI. It scans and attempts connect 3 times, then goes to disabled.
Click to expand...
Click to collapse
OMG!!! I was hitting my head all of yesterday. I converted my home network to WPA2-Enterprise (801.x EAP) after installing OpenLDAP and FreeRadius on my servers for AAA and keep getting the connect 3 times and then disabled. It appears from my FreeRadius logs that it send a challenge to my AP which then perhaps sends it to the DS5 and something happens there that is out of spec.
I started using DSC at .65b and that also had the same issue before I went to .7 yesterday. No idea that this would have worked on .63b.
Thanks man for helping me eliminate the LDAP or FreeRadius as the issue since these had passed with other test tools.
Ok. So here's a little tidbit of info.
I had a tenderloin ics build (the first ics one, 0.4 based).
Everything worked fine. But every time i would upgrade to a newer nightly build based off .6 or whatever, wifi would never work.
It would just not turn on, you could toggle it on but it just wouldn't do anything.
I was using CWM to update, and after every update i would have to back down to that first ics build to turn on wifi.
So i practically gave up for a week or so. Then i broke down and tried the ACMEInstaller2 method. Booted to the latest nightly build and presto, wifi turned on first try.
So those who are stuck with a broken wifi, try that install method. Not sure what's different. Maybe i have a broken CWM that doesn't update everything. Maybe it's some sort of bug, not too sure.
Enjoy.
report back after a week and if you didn't encounter any issues at all i'll do that
Has the Nabi 2 Wi-Fi issue supposedly been resolved?
I went through the process described in the rooting thread, including doing the OTA updates to .37 before rooting. I successfully rooted and added gapps. Then I made a TWRP backup of the tablet and all the games my kid installed.
The tablet runs fine for a day or two... then the wi-fi gets stuck on "Turning Wi-Fi On..."
At this point, I can restore my TWRP backup, and all is good again... for another day or two.
Is this the same Wi-Fi issue others are experiencing? Does it take some time for the problem to develop for everyone?
Should I flash back to an early stock image and try again?
Waleslie said:
Has the Nabi 2 Wi-Fi issue supposedly been resolved?
I went through the process described in the rooting thread, including doing the OTA updates to .37 before rooting. I successfully rooted and added gapps. Then I made a TWRP backup of the tablet and all the games my kid installed.
The tablet runs fine for a day or two... then the wi-fi gets stuck on "Turning Wi-Fi On..."
At this point, I can restore my TWRP backup, and all is good again... for another day or two.
Is this the same Wi-Fi issue others are experiencing? Does it take some time for the problem to develop for everyone?
Should I flash back to an early stock image and try again?
Click to expand...
Click to collapse
The main wifi issue was because of not doing the updates, I haven't heard of your issue and is probably related to something else, have you cleared cache/dalvik?