So ive run out of ideas on this problem. I no longer can update my prl and profile. I was on freeza's not3 2.2/2.25b rom had some issues with slow data and other hiccups. Flashed stock debloated and got tired of its blandness so i moved back to freeza's hoping for a better experience now that it had some time. After flashing back to it ive run into these issues.
Poor network signal, unable to update prl or profile with error code 6602. Ive gone stock tar nh7 and reflashed the modem too with no solution. Ive regained network connection after losing it entirely for a bit but still cant update prl or profile. Everybody else is talking how theirs is working great....i havent done anything different. Hope to get some input. Thx ahead of time.
Reminder at this point everything is stock flashed on odin. Twrp recovery latest version. Odin 3.09
Jataadroid said:
So ive run out of ideas on this problem. I no longer can update my prl and profile...
Click to expand...
Click to collapse
I had similar PRL/Profile problems, 'tho I was getting error code 6500. Network connections remained strong and through-speeds were very good. But the failure to update Prl/Profile really pissed me off. I also tried return to stock, other ROMs, but same error 6500. I just lived with it and did the occasional battery pull to good effect.
Then I installed Sacs_Note4 _Ported_apps_Rom_V2.
As part of the installation instructions, I updated PRL & Profile and was shocked when they worked!
Then I set up the phone as I like it, and back to error code 6500.
I turned-off the various Wanam mods and presto, no 6500 error code.
I then added them one at a time, (stuck with a few less this time) and still no error code 6500.
Good luck!
Related
So I noticed that my 3G wasn't connecting all day on my fascinate. I was running Evil Fascinate 3.3.2 with the nemesis ED01 kernel and the ED01 modem. So I flashed the EC01 modem. No 3G. So I completely wipe everything after a nandroid backup and installed stock DL09. Bam, 3G is back. I allow it to update itself to Froyo OTA. 3G working great. I wipe the phone and install the new Community Rom from scratch. 3G is gone again. I wipe the phone and I flash EF 3.4. 3G still gone.
So I'm back on stock Froyo. I'll do more testing later to see if rooting makes 3G go away again, but at this time I'm suitably freaked out.
Tenburn said:
So I noticed that my 3G wasn't connecting all day on my fascinate. I was running Evil Fascinate 3.3.2 with the nemesis ED01 kernel and the ED01 modem. So I flashed the EC01 modem. No 3G. So I completely wipe everything after a nandroid backup and installed stock DL09. Bam, 3G is back. I allow it to update itself to Froyo OTA. 3G working great. I wipe the phone and install the new Community Rom from scratch. 3G is gone again. I wipe the phone and I flash EF 3.4. 3G still gone.
So I'm back on stock Froyo. I'll do more testing later to see if rooting makes 3G go away again, but at this time I'm suitably freaked out.
Click to expand...
Click to collapse
Looks like smilepak had the same issue. see here also
Just a suggestion for when I get random bugs that others don't seem to get. I re-download the file i tried to flash, from a different link if i can get it. A lot of times it's a bad download
I think the piece of code in the unknown tethering module is phone home code. I think it's a combination of the phone home not happening, and high 3g usage triggering a disconnect on the other end. I can't prove it yet, but I'm trying to figure out a way to get tcpdumps for wireshark. I know my usage is very high right now.
This seems to be a problem alright..see this thresd: http://forum.xda-developers.com/showthread.php?t=1051543
Mine is low. For me, going to ed01 started the whole mess. Eve going back to dl09, didn't solve anything. The 3#g shows up and random disconnect every five minutes. Remind me of old modem days of bad handshake and reconnect loop. That is basically what it is doing. Once connected, hell of slow tried speed test and the result was horrible.
Looked through all settings values, factory reset, tried several different radio and from. All no such luck.
Sent from my Xoom using Tapatalk
dl09 radio > all
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.
So I've had root (stock Froyo) on my TB for a month or 2 now and really like being able to take off the bloatware and maintain consistent backups with TI and pull back a recovery with ROM Manager.
Over the past 2 weeks or so the damn OTA has been forcing its way into my phone, literally!!!
Every so often I would open my phone and it would be in process of DL a Firmware update. I'd pull the battery and restart and give me a server failure error and I was able to continue wihtout error.
All other times it would give indication that Verizon was trying to do something and I would reject it. It would disappear for a few days and reappear with the same 3 selections. I would always reject.
Then one day, as mentioned previously, I noticed my phone was in process of DLing a firmware update.
I thought I caught it in time, but then it kept happening.
I guess yesterday was the last straw VZW had with me rejecting their update and it was forced on. I was then stuck in a boot loop. It would start up and run some processes, get past the SD connection and then hang for a minute then return to a shutdown.
After this I decided to run the Deodexed 1.70 update and the Radio update.
Sat down last night and started messing with it.
Ran the Deodexed through HBOOT and nothing really happened. Did not process as I would expect or had seen when I set up ROOT originally.
So I then ran the radio through HBOOT and this one ran as expecxted asking me for the next step to run the install.
Seemed to work fine and the phone rebooted without a problem, that is until I saw my phone had 'No Service' on the lock screen and the little [x] next to the reception bars.
I tried running both files again through ROM Manager and received the same result.
What I noticed is the following;
Yeah I switched my Tom's and I had no data connection. This is what I did.
Step 1. ##778
step 2. Password 000000 ( six 0's)
Step 3. Tap on edit mode
Step 4. Go to modem settings and scroll to Rev.A (I was on eHRPD so I switched to Enable or whatever the first option is. If your oh enable switch it to eHRPD I did this setting when I didn't have connection a looong time ago)
Sounds like you successfully flashed an MR2 radio but you are still on MR1 (1.13.605.7 indicated by your screencaps) thus no service.
Assuming your recovery still works, flash the 1.70.605.0 rom via recovery.
bloated: http://forum.xda-developers.com/showthread.php?t=1160374
debloated: http://forum.xda-developers.com/showthread.php?t=1161251
If your recovery doesn't work, reflash it then flash the rom.
As you see in the screencaps, you should see 1.70.605.0 under build and software.
The OP's issue is a common one. Rejecting updates is a sorry way to retain root.
First, the 1.13 RUU that was flashed after rooting via ADB was NOT intended to be retained as the long-term solution. Please take a look at this radio link. As you'll see, RUU 1.13 is OLD. I believe many are under the impression this is the firmware that was on their device pre-root, and it likely wasn't. Most started with RUU 1.66 or 1.68. By running that post-root RUU, you're running firmware that is significantly older and less efficient than just about anything out there. And it WILL continue to attempt an auto-update until you fix that situation.
If you like your stock ROM, flash the RUU 1.68 rooted ROM but keep your radios. An even better idea would be to flash the RUU 1.70 ROM and radios since they are the most stable and efficient Froyo releases out. Of course, flashing a real custom ROM would be the best solution, but I know some people like bone stock or have some irrational paranoia about custom ROMs.
Check the Access Point name
Someone else had a similar problem. He realized he had no Access Point Name assigned. (Menu/Settings/Wireless & networks/Mobile networks/Access Point Name)
He wasn't able to reset it from the menu/reset option on the APN page, but was able to add a new APN with VZWINTERNET as the Internet name with the same settings as the non-working APN. Once he had the new APN enabled, he had data access.
brenick said:
Someone else had a similar problem. He realized he had no Access Point Name assigned. (Menu/Settings/Wireless & networks/Mobile networks/Access Point Name)
He wasn't able to reset it from the menu/reset option on the APN page, but was able to add a new APN with VZWINTERNET as the Internet name with the same settings as the non-working APN. Once he had the new APN enabled, he had data access.
Click to expand...
Click to collapse
Not this case since from the pics, the OP never actually flashed a rom that would work with his radio anyway as I mentioned above.
A few days ago, the wifi connection to my Verizon Note II stopped working. I see a strong signal from my router, and it attempts to connect, but inevitably gets "Authentication Error". It did the same thing with other networks, so it's not just my home wireless.
This is a well-known problem with 4.1.2 - and has been for a while. Google it. I did, and quickly went down a rabbit hole, leaving me frustrated, confused and still no closer to a fix. So I installed a 4.3 ROM, which also required an updated firmware.
I was using Jelly Beans 22 (http://forum.xda-developers.com/showthread.php?t=2032447)
I wiped everything and installed JellyWiz 4.3 (http://forum.xda-developers.com/showthread.php?t=2564495) with TWRP and VRUEMJ9 WIfI Firmware via Odin.
And still the error persists.
F** it. I'll jump to KitKat.
So I wiped everything again, updated TWRP, and installed Gummy (http://forum.xda-developers.com/showthread.php?t=2592339)
STILL NO WORKING WIFI. Same "Authentication" error
In between the above steps, I have tried literally everything I could find to fix this problem. Restarting my router (duh), changing settings in the wifi menu, the hidden "service mode" menu, energy saving, even dropping the /etc/wifi directory and replacing with a copy from 4.1.1.
What silly, stupid, inane detail did I miss?
SCH-I605
Android Version 4.4.2
Baseband I605VRUEMJ9
Kernel 3.0.64-gummy...
Have you updated to the mj9 firmware?
Fine. I'm done dealing with this, I thought, and nuked the phone back to the stone age.
Using Odin and instructions here: http://forum.xda-developers.com/showthread.php?t=2024207 I flashed back to 4.1.1 and a full factory reset.
Still. No. F***g. Wifi.
I have now spent the entire weekend upgrading and downgrading my Note II, to no effect. I'm almost *almost* convinced it's a hardware problem. If it didn't match so many other examples of a 4.1.2 wifi bug, to a T.
Anyhow, to the Verizon store I shall venture on the morrow, and demand satisfaction.
Kil4Thril said:
Have you updated to the mj9 firmware?
Click to expand...
Click to collapse
Yep. As part of flashing to 4.3 and Jelly Wiz.
No dice.
Did you use Odin or the flashable zip? ONLY the Odin method works. I tried using the zip, and while my phone said it was on mj9, it didn't update anything but the modem. This left me unable to use my WiFi on anything over 4.1. I hope this can be of some help
Alright guys, this is gonna be kinda long so get ready. I was running stock 4.4.2 NEW and I saw that there was a way to get GPE 4.4.3 and 4.4.4 rom working on the s4. I followed all the instructions on RickGrimes's post and wifi didn't work. Not and big deal. I couldn't soft reboot, so I tried flashing gogolies nc2 wifi fix and this modem worked. I then tried to update to 4.4.4, also following the instructions and the wifi didn't work once again. I flashed gogolies nc2 wifi fix again but it did not work. I also realized that I had no service at all and that I couldn't send or receive any messages or calls. So I did the safe thing and used Odin to get back to stock. I am currently running stock but the service is still terrible in places where I usually get great signal. Also, my wifi strength seemed to go down from what it usually is. Another issue is that my contacts that were backed up in backup assistant aren't there anymore at all. I generally know what I'm doing when it comes to this stuff but for some reason I have no idea how to resolve these issues. Any help will be appreciated.
Reolved
Jessooca said:
The easiest way to fix your phone or any phone for this matter is always to download and flash the stock tar file of whatever version of Android you were last on in Odin.
Then visit towelroot.com in your browser on your phone and root it again. (Don't forget to enable usb debugging first)
Click to expand...
Click to collapse
I wound up going back to stock 4.4.2 via Odin, but the problem still persisted. I figured out the my network settings were changed to Global instead of CDMa/LTE. Changed it back and all is well! Thank you though!