Database Users

My P6800 can't access 64-bits WEP WiFi with PA2.55 AROMA 27Dec2012

Hi,
I tried to post on this topic: http://forum.xda-developers.com/showthread.php?t=1838391
but the forum didn't allow me as I didn't post 10 replies yet
Yesterday I've flashed my P6800 with the latest version: AROMA 2.55 27Dec2012 found here:
http://forum.xda-developers.com/showpost.php?p=35953842&postcount=1817
before that, my tab was on android 3.2 .. and I was able to access 64-bit WEP WiFi with no problems at all !
But now, I can't ... It sees the AP with excellent signal, asks me for the password, tries to connect (The signal changes to poor/fair while trying to connect only !!!)... then it's says "Saved" and the signal is excellent again... without actually being connected ! and when I try to connect again, it does nothing at all !
I have to try to connect to another AP/router in order to make it try to actually connect again to my WEP WiFi !
I can't change the security encryption of my AP as I'm using four 3Com routers with WDS enabled and that feature only works with WEP
How did I flash my tab?
1. root
2. CWM
3. flash new rom (no wipe at all)
4. restart
5. wipe whatever required to be wiped
6. flash new rom again (allowing wiping again.. and restart)
There's an UI patch fix that I should do after finishing the initial setup wizard which requires connecting to the internet to sign into Google account
Thank you for your efforts

My baseband version: P6800XXKL2
I tried the factory reset and cache wipe now... didn't work !

I'm now back again to android 3.2 ... Kies doesn't allow me to update to ICS !
I'm downloading now XSG rom ... the baseband version is also different.. but I have to try !
anyone please, which rom would you suggest for P6800 XXKL2 ?
Thank you in advance ?

Daniel_hk sent me this:
Your baseband is too old. I uploaded a new one for you.
http://forum.xda-developers.com/showpost.php?p=36436688&postcount=1882
You may flash it with Odin or mobile odin. Put the file in the Phone part of Odin and flash.
Goodluck!
Click to expand...
Click to collapse
I had to upgrade to ICS official XSG manually... but having problems with WiFi being drops from time to time forcing me to turn it off and on to make it work each time !
I'll try this modem bin !

Now I'm using the official ICS firmware for XSG region... now I can access the WEP WiFi but I have to toggle the WiFi Off/On nearly every hour !
I tried your modem.bin file on that ICS firmware but still have to toggle hourly !

[Q] Problems with Google Edition ROM form Jamal - V4.0

Hello, i'm writing here since, having less than 10 posts, i can't post in the original thread by Jamal2367
http://forum.xda-developers.com/showthread.php?t=2544474
I live in Italy, operator H3G, 9505, baseband I9505XXUEMK9
I tested all previous release from Jamal (and use his 4.3 v2 daily), 4.0 works fine, no reboots, no FC
I have some problems, network related:
- LTE doesn't work, icon doesn't show up
- can't search mobile networks, only get a long wait then no results
- CAN autoregister, internet and calls works fine
- the dropdown notification window got stuck mid-screen, couldn't find a way to remove it, i rebooted
- roaming data comes default on (not good imo)
- APN: i have an additional new APN, 3 IT, never had that. Switching between 3 and 3 IT doesn't make LTE work
Is anyone experiencing these problems?

mike9055 said:
Hello, i'm writing here since, having less than 10 posts, i can't post in the original thread by Jamal2367
http://forum.xda-developers.com/showthread.php?t=2544474
I live in Italy, operator H3G, 9505, baseband I9505XXUEMK9
I tested all previous release from Jamal (and use his 4.3 v2 daily), 4.0 works fine, no reboots, no FC
I have some problems, network related:
- LTE doesn't work, icon doesn't show up
- can't search mobile networks, only get a long wait then no results
- CAN autoregister, internet and calls works fine
- the dropdown notification window got stuck mid-screen, couldn't find a way to remove it, i rebooted
- roaming data comes default on (not good imo)
- APN: i have an additional new APN, 3 IT, never had that. Switching between 3 and 3 IT doesn't make LTE work
Is anyone experiencing these problems?
Click to expand...
Click to collapse
I was on a lower baseband and did an upgrade to I9505XXUEMK9 using this thread -> http://forum.xda-developers.com/showthread.php?t=2192025
I only upgraded the modem.bin using Odin and thus did not have the knox bootloader and also did not need to flash the LTE modems.
Next I flashed Jamal's KK 4.4 GE S4 v4.0 rom (full wipe data, cache and devlik) that already have faux123's kernel bundled in it, and flashed updated superSU 1.8 and I did not have any problems with any of your problems mentioned above.
I suggest going to http://www.sammobile.com/firmwares/2/ to check if you are using the correct firmware.

I"m on modem mj8 and v2 4.4 of jamal. everything is stable and fast.
Try to do a full wipe: system,data,cache.dalvik. than flash the rom.
First flash the modem via odin 3.04.

phone works perfectly on 4.3
i always clear cache before and after flashing roms, sometimes i even format /system
I tried 4.4 AOSP and LTE works just fine, tried another GE and no LTE again, so it must be something related to GE
i'm gonna flash MKE to see if it makes any difference

??
i flashed I9505XXUEMKE but in info i still see MK9

mike9055 said:
??
i flashed I9505XXUEMKE but in info i still see MK9
Click to expand...
Click to collapse
If you are having issues with the baseband not changing after flashing, please do the 'manual', more troublesome way
1) When in Odin, remember to select Phone, not PDA and UNTICK AutoReboot
2) Flash modem
3) Once done, reboot once again into Download Mode
4) Flash Modem once more like in Step 1-2
5) Once done,unplug then reboot device manually.
P.S. For me, I rebooted my device manually in Download Mode by lifting the battery after Odin has completed flashing

kenshi08 said:
If you are having issues with the baseband not changing after flashing, please do the 'manual', more troublesome way
1) When in Odin, remember to select Phone, not PDA and UNTICK AutoReboot
2) Flash modem
3) Once done, reboot once again into Download Mode
4) Flash Modem once more like in Step 1-2
5) Once done,unplug then reboot device manually.
P.S. For me, I rebooted my device manually in Download Mode by lifting the battery after Odin has completed flashing
Click to expand...
Click to collapse
THX! Using these steps now i'm on MKE (strange fact, i have flashed modem several times and never got stuck)
For now i restored a 4.3 android, gonna try again soon

mike9055 said:
THX! Using these steps now i'm on MKE (strange fact, i have flashed modem several times and never got stuck)
For now i restored a 4.3 android, gonna try again soon
Click to expand...
Click to collapse
Haa! Sure! Glad that helped!

[Q] Canadian S4 5.0.1 - WiFi Won't turn on

At wits end, but can't get my WiFi to turn on at all.
The setup l had before was stock Bell 4.4.2 but rooted and TWRP (with backups).
Forgot to turn off (replacement phone, forgot to turn off), auto-updates. Phone tried to update to 5.0.1 but failed, telling me to use Kies. Had to flash in Kies as my phone got stuck in Samsung's boot logo. Before plugging into Kies, l tried wipe cache, battery out, and then wipe/reset, none worked. So l plugged into Kies, it did it's thing. Went smooth. Now, my wireless just won't turn on at all. Rooted it with CF AutoRoot. Went to wpa_supplicant folder, to find l don't have the .conf file. Renamed the folder, power cycles, system created the folder but no file again. Created a file named "wpa_supplicant.conf" and power cycled, renamed it, system didn't create it again. So l think l found the issue but any fix to this? Maybe running the wrong version, even though l have stock Bell apps (how l missed them )
MODEL SGH-I337M
VERSION 5.0.1
BASEBAND I337MVLUFNI2
KERNEL 3.4.0-4508315 [email protected] #1
BUILD LRX22C.I337MVLUGOC4
KNOX 2.3 (TRIPPED)
Side note: I do get a WiFi MAC address that appears valid (haven't compared to my router logs) under status.
=================
Update I FIXED IT! YAY!
For those who are having the same issue. Do the following steps:
Download Odin 3 - Make sure Kies isn't running
Verify ID COM has a number like COM0 or something.
Leave everything else alone.
Download ROM from SamMobile or another ROM site Link (filtered to Bell)
Unplug phone
Place phone into download mode (Vol Down, Home, Power)
Using Odin, hit PDA and put the ROM in, give it some time
Plug phone in, and verify COM and message saying ADDED!!
Start it, then give it some time.
If you want to root it, do the same procedures but grab CF-Auto-Root and repeat it. Easy root.
Optional stepsbut l did it anyways:
Before doing this, l rooted it with CF Chain, and installed TWRP. Wiped Cache, Dalvik, System.

Hello dear friend
i wanted to thank you for your solution and specially download links, had the exact same issue which was resolved by the solution you provided.

I recommend flashing with Odin and a stock ROM from Sam mobile.com. kies has never worked for me so no now stick with Odin.

Wi-Fi not working anymore, weirdest problem ever!

I promise, this is not one of those "reset your access point" or "clean your networking settings" question.
Some background: the phone is not rooted, using stock Android with latest OTA update, locked and never been played with. This problem happened all the sudden with no major changes or accidental drops. Bluetooth and Mobile Data works fine, I can receive and makes phone calls too.
The Problem: the phone can discover available access points and SSIDs, connect to them, performs authentication also, but it fails to get an IP. Android tries to get an IP up to 5 times by issuing a DHCP discovery, eventually failing with the message "IP configuration error"
Why is it weird? because I tried all of the following:
- Tried 4 different access points, 4 different brands, configuration and setup, they all produced the same result of "IP configuration error"
- Tried configuring the phone with a Static IP address, that gave me the error "Connected, no internet".
- Performed a "Factory Data reset", no go.
- Flashed the latest 7.1.1 factory image from Google "angler-n4f26i", no go.
- Flashed the first 7.0 factory image from Google "angler-nbd91k", no go.
- Flashed the first 6.0 factory image from Google "angler-mda89d", no go.
- Tried to use the Backup and Rest -> Network Settings Rest, no go.
- Tried to use the Developer Options -> Use legacy DHCP client, no go.
- Enabled tethering on the phone and tried to connect my laptop to it, my laptop can discover the SSID network on the phone, connect to it, perform authentication, but also fails to get an IP address.
At this point I'm running out of options and dunno what to try next, any lead or recommendation from you guys would be really appreciated. RMA is very hard, nearly impossible to perform where I live "Middle East" :/
Help?

Noorish said:
I promise, this is not one of those "reset your access point" or "clean your networking settings" question...
Click to expand...
Click to collapse
How were you flashing? Sideloading OTA images, or unlocked bootloader, full factory image flashing?
On first boot after clean install, exactly what happens when prompted for your Wi-Fi connection? If it fails there, no point in going further into the OS.
Have you tried using a custom kernel like Franco or EX Kernel that handle the Wi-Fi? (To rectify the problem, not what caused it)
Have you tried formatting modem partition and flashing to the latest radio? (v03.78)

v12xke said:
How were you flashing? Sideloading OTA images, or unlocked bootloader, full factory image flashing?
On first boot after clean install, exactly what happens when prompted for your Wi-Fi connection? If it fails there, no point in going further into the OS.
Have you tried using a custom kernel like Franco or EX Kernel that handle the Wi-Fi? (To rectify the problem, not what caused it)
Have you tried formatting modem partition and flashing to the latest radio? (v03.78)
Click to expand...
Click to collapse
Let me try to answer one by one:
How were you flashing? Sideloading OTA images, or unlocked bootloader, full factory image flashing?
I've gone the unlocked boot loader full factory image way. all my images were downloaded from: https://developers.google.com/android/images#angler
On first boot after clean install, exactly what happens when prompted for your Wi-Fi connection? If it fails there, no point in going further into the OS.
It shows a full list of available access points, I select my SSID and provide a password, the authentication succeeds and the phone proceeds to enable the DHCPClient, it broadcasts a request over wireless but never gets an IP, it tried the process again up to 5 times eventually failing with the error message "IP Configuration Error", configuring an IP address gives the error message "No Internet Connection". I've been able to test this today using a 4th access point brand (tried TP-Link, Cisco, Huawei, ZTE), I'm 100% sure that there's nothing wrong with the access points, as everything else I have works just fine (PS4, laptop, wife's mobile, tablet... etc)
Have you tried using a custom kernel like Franco or EX Kernel that handle the Wi-Fi? (To rectify the problem, not what caused it)
I haven't, but will be doing so today or tomorrow and will be reporting back my results. this is a new lead to follow.
Have you tried formatting modem partition and flashing to the latest radio? (v03.78)
This was done in part of the full image flash, I've tried different full images as stated in my original post, so basically I've had 1.29, 3.72, 3.78 and even the latest 3.79 but those didn't work, do you suggest to do the radio image alone? after performing the full image flash?

Noorish said:
Have you tried formatting modem partition and flashing to the latest radio? (v03.78)[/I]
This was done in part of the full image flash, I've tried different full images as stated in my original post, so basically I've had 1.29, 3.72, 3.78 and even the latest 3.79 but those didn't work, do you suggest to do the radio image alone? after performing the full image flash?
Click to expand...
Click to collapse
Yeah, it was more just formatting and flashing the radio separately, but I'm pretty sure the kernel is handling WiFi on our device. Try one of the custom kernels.... you may have a hardware issue. Good luck.

If you have a main modem then access point internet set-up try doing the following steps:
1.) Forget the Wi-Fi network on your phone. Afterwards enable Airplane mode.
2.) Next turn-off your AP and allow 10 seconds to pass.
3.) Then turn-off your main modem and allow 30 seconds to pass.
4.) Once the alloted time has passed sequentially power back on your equipment. So power back on your main modem, allow another 30 seconds, then power back your AP.
5.) Give the AP another 30 seconds after which disable airplane mode, enable Wi-fi then re-attempt to connect.
*I just wanted you to give those steps a shot juat to eliminate the main modem as a possible factor (in case you have such set-up). Your router/AP is clearly not causing the issue so at this point the problem could either be caused by:
A.) A modem glitch preventing an IP to be handed to your phone when it's MAC address is detected.
B.) Or possibly an issue with the phone's Wi-fi hardware.

v12xke said:
Yeah, it was more just formatting and flashing the radio separately, but I'm pretty sure the kernel is handling WiFi on our device. Try one of the custom kernels.... you may have a hardware issue. Good luck.
Click to expand...
Click to collapse
I've been able to install Lineage OS with EX kernel, and I can confirm that my wireless chip is to blame. I ran every possible combination/setup I could think of that involves software, I keep having the same result... sooo.... yup, dead piece of a: https://www.broadcom.com/products/wireless/wireless-lan-bluetooth/bcm4358
blitzkriegger said:
If you have a main modem then access point internet set-up try doing the following steps:
1.) Forget the Wi-Fi network on your phone. Afterwards enable Airplane mode.
2.) Next turn-off your AP and allow 10 seconds to pass.
3.) Then turn-off your main modem and allow 30 seconds to pass.
4.) Once the alloted time has passed sequentially power back on your equipment. So power back on your main modem, allow another 30 seconds, then power back your AP.
5.) Give the AP another 30 seconds after which disable airplane mode, enable Wi-fi then re-attempt to connect.
*I just wanted you to give those steps a shot juat to eliminate the main modem as a possible factor (in case you have such set-up). Your router/AP is clearly not causing the issue so at this point the problem could either be caused by:
A.) A modem glitch preventing an IP to be handed to your phone when it's MAC address is detected.
B.) Or possibly an issue with the phone's Wi-fi hardware.
Click to expand...
Click to collapse
Thanks for the suggestion, but this didn't work. I've been able to do an extra step and test connectivity using 4 different types of access points / modems, even using tethering from different mobiles that was acting as access points. it's no good.
Looks like the only option left is to do a repair with one of the local shops, hopefully they'll know what a Nexus is and how to handle it (it's not officially sold here yet), according to iFixIt, it'll be very hard to do so: https://www.ifixit.com/Teardown/Nexus+6P+Teardown/51660
Thanks for all the help everyone, really appreciated.

Noorish said:
Thanks for all the help everyone, really appreciated.
Click to expand...
Click to collapse
Sorry to hear. This is the first time I've heard of Wi-Fi failing due to a hardware issue. I doubt it is repairable. It may be located on the motherboard, which although readily available is not really economical to replace. May be the end of the road. This appears to be one more blot on Huawei's QA/QC.

Exactly my thought. Never had such a case in my life, and I'm a tier 3 support engineer in network infrastructures. go figure!
To add even more light into the case, I've ran a packet sniffer in my LAN to check if the mobile is performing a DORA against the DHCP service in my network, but nope, there is no trace for it's MAC address or any broadcast messages from the mobile.
This is the second Nexus that I own and have failed within a year of its life span (previously a Nexus 5 owner, charging station at phone died). I think I'm going to give OnePlus a try very soon.

Trouble flashing S8 Active (SM-G892U) from Sprint to TMobile

I have migrated to TMobile and am trying to reflash my unlocked S8 Active from Sprint to TMobile mainly for wifi calling functionality. The phone was already running Android 9.
I downloaded & flashed the latest TMB firmware from sammobile via Odin v3.14.4 per the instructions on sammobile.
I flashed all the files including CSC and Userdata to ensure a complete wipe and flash.
I even wiped the cache and performed a factory reset after the firmware flash. The phone has been rebooted multiple times now since the reprogramming.
Unfortunately when the phone starts up I still get the Sprint flash screen and I don't have the Wifi Calling option available. The phone shows the latest TMB software is loaded (G892USQS6CTB2) however it still shows software ownership as Sprint (SPR/SPR/SPR).
Any advice on what I should be doing differently? Thanks!

It's a bit old to bump, but I'm in the exact same boat. Anyone have a fix for this?

I also am in the same boat: I want to use my SM-G892A on T-Mobile with wifi calling enabled. Many rooting resources say rooting this phone is not possible, but apparently on Sammobile there's instructions. I could not find them though. Any pointers appreciated.