Database Develop

[ROM] [WIP] Custom rom for MetroPCS users (Based off CM6)

I have decided not to build a ROM anymore. Instead, I have been working on the "Proxy Configuration Tool for Alternate Carriers" so that you can use almost ANY ROM (including CM6) with MetroPCS AND Cricket, yes, the Proxy Configuration Tool for Alternate Carriers will also support Cricket.
As you can see, the Proxy Configuration Tool for Alternate Carriers is an open-source project and you can contribute to it.
Here's the current TODO list:
- BUG: Proxy actually not updating properly when setting it through the sqlite db.
- Find out the correct ip for the mms proxy server for both MetroPCS and Cricket.
- Find out the correct network interface used by the Motorola Droid on FroYo.
- Find out the correct eri.xml file for cricket.
- Setup screen first time it runs & check for the following on every boot.
- Automatically setup APN.
- Check build.prop and modify it if it's needed (backup too) (ask for restart if modified)
- Check /data/eri.xml and install the new one if it's needed (backup too) (ask for restart if installed)
- Check for u2nl binary, if not available install it in /system/bin/, it's in the assets folder. (ask for restart if installed)
- Check for sqlite3 binary, if not available install it in /system/xbin/, it's in the assets folder. (ask for restart if installed)
- Drop database tables and replace them with appropriate Carrier Settings in: /data/data/com.android.providers.telephony/databases/telephony.db
- Document, organize and maybe improve configuration screen.
- It needs a better icon.
As you see, at this point is not complete, mostly due to the fact that the Proxy is not changing properly unless you reboot. It must be a stupid mistake on my part. I have been really busy lately and I have only been working on this when I get some free time, I figured somebody could contribute to this
If you'd like to test it go to the github link here and click on the Downloads tab and there should be an alpha version in there. I'll be building new versions whenever I clear out any of the items in the TODO list above.
Thank you.

[RESERVED]

How do you get metropcs on the Dinc....I would love to know
Sent from my ADR6300 using XDA App

there's shops that will flash any cdma phone over to metro. That's why you see sprint and verizon phones with bad ESN #s selling on craigslist

mexicanigga said:
How do you get metropcs on the Dinc....I would love to know
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
- Use the ##778 programming instruction just like as if you were flashing a Droid Eris.
- Find somebody (a dealer most likely) to put the ESN into MetroPCS's database.
- Flash this rom (hopefully it'll be completely done soon)

WOW!! Ok I am currently running CyanogenMod 6.0RC1 on a HTC Sprint Hero and had a vendor here in town who gets ALL Verizion\Sprint CDMA phones on MetroPCS hook me up. He uses DamageControl 1.0 and everything works except the market of course..It does work on WiFi however.
My problem began when I just did NOT have consistent internet. It just was hit and miss. WiFi worked no problems. So I started messing around with different ROMS with NO luck at all. I have wiped and wiped (phone and SD card)everything you could do..Still notta!!! So I am super curious if this would work? I really just need my dam internet to work..It would be awesome if it was on this CyanogenMod 6 ROM...It's smoking and appears to be the best ROM I have found for a Hero..Man if anyone could help me get this baby on the net...I would be willing to pay. I think my settings are off honestly...HELP!
Your thoughts?

CyborgNM156 said:
WOW!! Ok I am currently running CyanogenMod 6.0RC1 on a HTC Sprint Hero and had a vendor here in town who gets ALL Verizion\Sprint CDMA phones on MetroPCS hook me up. He uses DamageControl 1.0 and everything works except the market of course..It does work on WiFi however.
My problem began when I just did NOT have consistent internet. It just was hit and miss. WiFi worked no problems. So I started messing around with different ROMS with NO luck at all. I have wiped and wiped (phone and SD card)everything you could do..Still notta!!! So I am super curious if this would work? I really just need my dam internet to work..It would be awesome if it was on this CyanogenMod 6 ROM...It's smoking and appears to be the best ROM I have found for a Hero..Man if anyone could help me get this baby on the net...I would be willing to pay. I think my settings are off honestly...HELP!
Your thoughts?
Click to expand...
Click to collapse
It will work for you, but you must be sure to take one very important step before you attempt this, or you will end up with a bricked phone.
Buy a HTC Droid Incredibile
Using this rom, or any other rom for the incredible on a device that is not an incredible will result in an unusable phone, if not bricked forever!

Teksu said:
It will work for you, but you must be sure to take one very important step before you attempt this, or you will end up with a bricked phone.
Buy a HTC Droid Incredibile
Using this rom, or any other rom for the incredible on a device that is not an incredible will result in an unusable phone, if not bricked forever!
Click to expand...
Click to collapse
That's completely right.
The beauty of what I'm doing here, is that, just like I did for the Droid Incredible and the Droid, it could also be done for the Hero and the EVO, since CM supports all of these devices. As long as the source is completely open of course.
Once I fix these issues with the u2nl binary not working properly, I'll update my winzip and build the "roms" for the Droid, EVO and Hero.
For now, this build above only works for the Droid Incredible.

Nice would this work for my flash metropcs hero? Please let me know.
Thanks
velazcod said:
I have forked and prepared a vendor repo to build CM6 for MetroPCS on the Dinc.
DO NOT FLASH THIS UNLESS YOUR PHONE IS ON METROPCS AND YOU KNOW WHAT METROPCS IS.
Reason why I did this was so that anyone that wanted to "flash" a Dinc/Droid to MetroPCS didn't have so much of a hard time doing it, and also so that everything worked out of the box (including internet on apps, connected to wifi or not).
I also managed to build a little service "app" that runs on the background and detects changes on the state of wifi connections, and it activates/deactivates proxy (and u2nl) depending on that.
Wifi Disconnected = Proxy/U2NL activated
Wifi On = Proxy/U2NL deactivated
When proxy/u2nl is active, all data goes through MetroPCS's proxy server, otherwise use wifi's internet connection.
At this point, it works great, but it's unfinished.
- Calls and SMS work perfectly with no issues at all.
- MMS can be sent and received with no issues either.
- On wifi, everything works perfectly.
- On MetroPCS data, only browser works, for some reason the u2nl binary it still not working properly.
This is meant to be free and open sourced. Not a paid solution.
The "proxy switcher" also has a configuration screen which allows to change the configuration. You can use a custom proxy, activate/deactivate proxy/u2nl, etc.
If you have the time and know about this, please figure out a way to make the u2nl binary work properly, or contact me, my twitter is in my signature, or you can PM me and we can gchat or email. I have had limited time to work on this these past few days.
Everything is open sourced,
vendor config is here http://goo.gl/ISk6
"wifi switcher" (for proxy) is here: http://goo.gl/2wwM
Also,
If you are interested on doing this on the Motorola Droid, here's the vendor config:
http://goo.gl/kuX3
Here's a built rom, if you'd like to test it
http://bit.ly/aBa5Qr
As soon as you install it, let it boot, and open APN configuration (use AnyCut or BetterCut).
Edit the one that says "metropcs" and on on the username, make replace "MDN" with your phone number, press menu, save, and then click on the radio button for that entry. After that, MMS will work.
This is based off CyanogenMod-6.0.0 and it hasn't been modified at all. All credits go to the CyanogenMod team
Click to expand...
Click to collapse

I'll tell you what work for me.
You need to the u2nl.zip from whiterabbit.org
In that file you will find the autostart.sh file for htc hero eris under metropcs folder.
I have to edit the autostart.sh file in order to work getting rid off some lines.
This is the file I'm using. autostart.sh
export PATH="$PATH:/system/bin"
iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -F
iptables -t nat -F
iptables -X
iptables -t nat -A OUTPUT -o rmnet0 -p 6 ! -d 10.223.2.4 -j REDIRECT --to-port 1025
u2nl 10.223.2.4 3128 127.0.0.1 1025 >/dev/null 2>&1 &
exit 0
and that's all
I've pushed the files via adb in Clockwork recovery console mounting system and data
adb shell su
cd /data/
mkdir opt
chmod 0777 /data/opt/
chmod 0777 /system/bin/
exit
adb push autostart.sh /data/opt/autostart.sh
adb push u2nl /system/bin/u2nl
adb shell
chmod 0777 /data/opt/autostart.sh
chmod 0777 /system/bin/u2nl
reboot
Result is working

ahernandez4110 said:
Nice would this work for my flash metropcs hero? Please let me know.
Thanks
Click to expand...
Click to collapse
That question was answered in the post right before yours.

diegov600 said:
I'll tell you what work for me.
You need to the u2nl.zip from whiterabbit.org
In that file you will find the autostart.sh file for htc hero eris under metropcs folder.
I have to edit the autostart.sh file in order to work getting rid off some lines.
This is the file I'm using. autostart.sh
export PATH="$PATH:/system/bin"
iptables -P INPUT ACCEPT
iptables -P OUTPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -F
iptables -t nat -F
iptables -X
iptables -t nat -A OUTPUT -o rmnet0 -p 6 ! -d 10.223.2.4 -j REDIRECT --to-port 1025
u2nl 10.223.2.4 3128 127.0.0.1 1025 >/dev/null 2>&1 &
exit 0
and that's all
I've pushed the files via adb in Clockwork recovery console mounting system and data
adb shell su
cd /data/
mkdir opt
chmod 0777 /data/opt/
chmod 0777 /system/bin/
exit
adb push autostart.sh /data/opt/autostart.sh
adb push u2nl /system/bin/u2nl
adb shell
chmod 0777 /data/opt/autostart.sh
chmod 0777 /system/bin/u2nl
reboot
Result is working
Click to expand...
Click to collapse
Yeah, if you take a good look at the vendor source I posted on the OP, this is basically what I'm doing (especifically this file). At first I tried building u2nl from scratch that didn't work, then, just to try it, I tried the u2nl binary found in whiterabbit.org and that didn't work either.
There's still something wrong with this setup I'm using, but I haven't been able to track it down yet, I did this about 2 weeks ago but lately I haven't had the time to troubleshoot it all

Link to your ROM is dead.
Been trying to get the new Skyraider 3.0 to work on Metropcs

dannystang said:
Link to your ROM is dead.
Been trying to get the new Skyraider 3.0 to work on Metropcs
Click to expand...
Click to collapse
Sorry, I was messing with some files and screwed up the links.
I'm currently rebuilding it again with a few changes I made and also sync'd everything with CyanogenMod's source.
Will post new link tonight and also have builds for the Motorola Droid and HTC EVO.

Updated OP with latest build. This is based on latest CM6.
http://bit.ly/incredibleMetro
http://bit.ly/bh4wbh - Google Apps (Latest)

Thanks! I couldn't sleep so I finally figured it out
I mounted the Skyraider 3.0 RC2 release, everything works except hulu on data without wifi which is ok cause metro is slow data anyhow.
I read past instructions to get data to work I just used whiterabbit u2nl File but it seems he has a "new" folder with an edited autostart which when I pushed it on works fine...
No need to edit anything, I can switch on and off wifi no problems...

dannystang said:
Thanks! I couldn't sleep so I finally figured it out
I mounted the Skyraider 3.0 RC2 release, everything works except hulu on data without wifi which is ok cause metro is slow data anyhow.
I read past instructions to get data to work I just used whiterabbit u2nl File but it seems he has a "new" folder with an edited autostart which when I pushed it on works fine...
No need to edit anything, I can switch on and off wifi no problems...
Click to expand...
Click to collapse
That is strange, nothing works for me except the browser, as in, only the proxy is working and not the u2nl... I'll work on this tomorrow again

diegov600 said:
I'll tell you what work for me.
Result is working
Click to expand...
Click to collapse
+1 This worked for me on Skyraider 3.0 RC2.
Thanks!!!
Will try it on CM6 now.
Edit: Won't work on CM6 NIGHTLY 08/24.
Works on IncredibleDoes AOSP - FRF91.

I got it working on CM6 RC3.

Now we just need Skyraider with the Froyo Final
Why did you guys have to use the edited autostart though?
Wondering why mine works and its so different...

newb help please... help with adb copying files.... no permissions??

Sorry... newb question... can not figure out this deal...
Trying to copy the jupiter files to my phone... can not.
I dont have permissions... how can I get permissions opened up?
Below is some of what I am getting in regards to errors -
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\a
ndroid-sdk-windows\tools>adb push jupiter.xml /system/etc/jupiter.xml
failed to copy 'jupiter.xml' to '/system/etc/jupiter.xml': Permission denied
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\a
ndroid-sdk-windows\tools>adb push jupiter.xml /sdcard/jupiter.xml
failed to copy 'jupiter.xml' to '/sdcard/jupiter.xml': Permission denied
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\a
ndroid-sdk-windows\tools>adb shell
$ su
su
Permission denied
$
Note - this is a samsung captivate phone with a fresh cognition 2.36b rom and I used one click root on it to root the phone after the build..... (but I think the rom was rooted to start with??
Sorry ... just need a way to get access to this phone - trying adb.... also is there a windows file manager that would browse/edit the contents of this phone?
thanks in advance Kevin

PLEASE DIVERT ALL QUESTIONS TO Q&A FORUM NEXT TIME.
IF you're on Froyo.. for some reason froyo does not allow pushing to /system .. at least for me that's the case (someone correct me)
root your phone:
1. adb push /sdcard/jupiter.xml
2. adb shell
3. su
4. cp /sdcard/jupiter.xml /system/gps/jupiter.xml (or wherever you need to put it)
5. do the same for the rest of the files.. but tbh
THERE'S NO FIXING GPS YET

darkamikaze said:
PLEASE DIVERT ALL QUESTIONS TO Q&A FORUM NEXT TIME.
THERE'S NO FIXING GPS YET
Click to expand...
Click to collapse
What he said.

If froyo didn't fix your gps then you are sol. But don't be so sure its still broke, it can take some time on the first lock. Once it gets a lock within 5-10 meters it should work decent afterwards with the occasional hiccup usually when its not used every day. But some are reporting poor performance still with froyo.
A factory reset can fix some bugs I have seen on jf7 and ji6 on my phone causing the gps to turn off. Jj4 doesn't seem to have that bug on my phone. Cog2.3b6 is jj4 based
Some claim to have performance degrade over time, I think that's all placebo but others have completely different experiences with gps than I do. I notice it having to occasionally need to get new gps data causing a delay in the initial lock but it seems more random than progressive and I never fail to get a lock.
If you are trying to use the jupiter.xml file in the gps solution thread from clshortfuse our what ever his name is, you will likely see an no improvement to a slight improvement. It gets faster locks on eclair roms but on froyo the jupiter file already resembles his and the major difference being that his forces the google server for gps data.
Sent from my SAMSUNG-SGH-I897

OK thanks for all the help so far -
I had a n82 phone, like 2-3 years ago, it was awesome.... google maps and all... blue dot was where the phone was... I could watch me walk around my house... it would show me getting the mail walking down the drive way to the mail box and back....
I have an iphone 3gs....works fine.... maybe not quite as good as the n82 did, but works ok, locks quick and will the blue dot with in a few feet of me IN MY HOUSE.
While I dont get this whole GPS problem on this phone I hear you about not trying to fix it.
I have some limited unix experience... used vi and other stuff, was able to move,copy, edit and replace files... change permissions and other standard stuff.
So if the cognition rom is rooted as is, and I was rooted before the rom, I assume I still am rooted....
Why wont the commands I tried work?
I did not try the other commands noted in this thread, yet, I will soon.
So is it my phone? or do I have the commands/syntax wrong?
If I am going to stick it out with the phone I need to figure out how to fix it.
thanks again for your help.
Kevin

Any ideas or reasons why this command would not work?
C:\Documents and Settings\Kevin\My Documents\Downloads\android-sdk_r07-windows\android-sdk-windows\tools>adb push jupiter.xml /sdcard/jupiter.xml
failed to copy 'jupiter.xml' to '/sdcard/jupiter.xml': Permission denied
My file on my PC is in the folder I am working from ....\tools and I assume I should have permissions to the sdcard folder?
Any help would be appreciated.
thanks Kevin

Have you made sure to grant superuser permission on the phone?
I had that issue the first time I tried it and found that I hadn't granted superuser access.
Also to the OP, if you switch to Perception, DG includes the Jupiter fix in the ROM.

You can't push to /system in FROYO.
you have to push it to /sdcard first
adb shell
su
cp /sdcard/jupiter.xml /<LOCATION>
and chmod it
and chown it.

thanks for the help... to make sure I have the right permissions I need to use the chmod and chown commands -
Do I need to mount the system first? Something like -
Code:
adb shell
$ su
# mount -o rw,remount /dev/stl9 /system
# chmod 777 /system/etc/*
thanks again, Kevin

haeffnkr said:
thanks for the help... to make sure I have the right permissions I need to use the chmod and chown commands -
Do I need to mount the system first? Something like -
Code:
adb shell
$ su
# mount -o rw,remount /dev/stl9 /system
# chmod 777 /system/etc/*
thanks again, Kevin
Click to expand...
Click to collapse
I would never do 777 on any file. Jupiter.xml should be 644 and user and group root.
Sent from my SAMSUNG-SGH-I897 using XDA App

[FIX] Final fix for nonworking WIFI on unlocked ATT Atrix in some countries

So guys, here is a quick tutorial how to fix your nonworking wifi in certain countries. The problem for it not working is that motorolas wifi driver is missing some country codes ... i guess they still live 20-30 years back, if anyone has the will to do it, we might post on motos forums to change the driver int he upcoming updates/releases. Here is the link to working wifi drivers: http://www.megaupload.com/?d=V8TGAY0C
if anyone can host it on a better location, feel free to do so.
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE, YOU OR TO ANYTHING THATS IN RELATION WITH THE PHONE OR YOU.
this tutorial will be for use with adb shell (if anyone wants to make a script or a batch or even cwm flashable out of it, be my guest, i dont really have the time and my knowledge is a tad limited in doing those things )
Prerequisites:
1.the wifix.zip
2.adb on your computer with at least some adb/linux terminal knowledge
3.rooted ATT Atrix (i tested it on mine thats from ATT and several others did too, dont know if anyone tried with the bell or other atrix's but im sure it should work)
4.some common sense
5. i assume you have am external sdcard aswell (if not swap the sdcard-ext for sdcard only to use the internal card)
Code:
TURN OFF WIFI in the settings/wireless networks menu
1.connect phone to computer with us on usb mass storage mode and without adb debugging, create a folder called wififix on your external sdcard, unzip and copy the three .bin files to that folder
2.do the safely remove on windows/linux and than change connection to none, disconnect usb, enable adb debugging and reconnect your phone to the usb
3. run cmd/terminal
4. write as follows, after each line press enter:
adb shell
su (allow su on your phones display if its the first time you are using adb with su)
mount -o rw,remount -t ext3 /dev/block/mmcblk0p12 /system
rm /system/etc/firmware/wifi/*.bin
cp /sdcard-ext/wififix/*.bin /system/etc/firmware/wifi/
chown root /system/etc/firmware/wifi/*.bin
chgrp root /system/etc/firmware/wifi/*.bin
chmod 755 /system/etc/firmware/wifi/*.bin
reboot
5. let your phone reboot, disconnect usb, unlock phone, enter pin, enable wifi and its working.
Feel free to comment in the thread and help eachother with problems and ideas
Updated link due to request and megaupload being down, fee free to host it if you want to: http://filesave.me/file/13333/wififix-zip.html

Where was this driver taken from?

lg optimus 2x /system dump
the driver itself is a tad older version as the one moto has, but everything works for me fine now, several other users reported the same. i wanted to use the driver from the UK atrix (from orange) but its identical with the one from the ATT atrix (even the nvram.txt has region US in and not UK ...), so for the time being this is the only way for a few of us to have a fully functional phone.

one more thing, everyone who uses the fix and it works for him please post on motorolas forum that you have the problem:
https://supportforums.motorola.com/thread/50598
i started the thread just add that its not working.

and I was thinking how can wi-fi be related to country/location?!
because I remember in the old thread that several users from the same country (Qatar) reported the same problem.
I just sent an e-mail about your thread to one of those users who was in contact with me via e-mail while trouble-shooting his problem.
Thanks and gold luck.

Ye, just post in the moto forums that he/you have the same problem.

Does not work
on the line: chmod -R 0755 /system/etc/firmware/wifi
I get: Bad Mode
then I use: chmod 755 /system/etc/firmware/wifi/*.bin
and after reboot the same problem... WiFi appears for few seconds and gets lost

crnkoj, since this is the case. do you think using the market enabler app to spoof the SIM carrier will make wifi work in non-supported countries?!

uhm, did you copy the files over properly? the thing is its working for me fine and several others have confirmed this to work. Honestly i dont know why it wouldnt work, did the method from akizakian work for you at least? with the modified and locked settings.db?
genatsvale said:
on the line: chmod -R 0755 /system/etc/firmware/wifi
I get: Bad Mode
then I use: chmod 755 /system/etc/firmware/wifi/*.bin
and after reboot the same problem... WiFi appears for few seconds and gets lost
Click to expand...
Click to collapse

Tried that, it wont help. Market enabler spoofs the mcc and mnc, which comes from the sim card itself. The problem here becomes once you have cellular signal and turn on wifi, at that point wifistatetracker request country code from the cellular network, sets it to the one in which country you are and than the driver doesnt reckognise the code and blocks wifi. If you would take lets say a german sim card and put it in in your country wifi still wouldnt work, if you would take your sim card go to germany, turn on wifi and it would work. im trying to get something solved int eh motorola forums but until now only one guy is responding (not sure if hes motorola staff or whatsoever).
CyberPunk7t9 said:
crnkoj, since this is the case. do you think using the market enabler app to spoof the SIM carrier will make wifi work in non-supported countries?!
Click to expand...
Click to collapse

Still doesnt work for me. I can see my wireless, and can connect to it. but if I try to go to the market, or anywhere using the browser.. nada

uhm, but your laptop can use the wifi? is it any special encryption maybe, maybe you have to do vpn or stuff?
did you try ping from a terminal emulator?

guys, motorola is gonna fix it with an update it seems
https://supportforums.motorola.com/thread/50598?start=15&tstart=0

I made an update.zip for CWM if you need it. THis way you just have to apply the update after SBF/root. It SHOULD work....I did not try it.

Thanks Dennis, i was too lazy to do it

crnkoj said:
So guys, here is a quick tutorial how to fix your nonworking wifi in certain countries. The problem for it not working is that motorolas wifi driver is missing some country codes ... i guess they still live 20-30 years back, if anyone has the will to do it, we might post on motos forums to change the driver int he upcoming updates/releases. Here is the link to working wifi drivers: http://www.megaupload.com/?d=V8TGAY0C
if anyone can host it on a better location, feel free to do so.
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE, YOU OR TO ANYTHING THATS IN RELATION WITH THE PHONE OR YOU.
this tutorial will be for use with adb shell (if anyone wants to make a script or a batch or even cwm flashable out of it, be my guest, i dont really have the time and my knowledge is a tad limited in doing those things )
Prerequisites:
1.the wifix.zip
2.adb on your computer with at least some adb/linux terminal knowledge
3.rooted ATT Atrix (i tested it on mine thats from ATT and several others did too, dont know if anyone tried with the bell or other atrix's but im sure it should work)
4.some common sense
5. i assume you have am external sdcard aswell (if not swap the sdcard-ext for sdcard only to use the internal card)
Code:
TURN OFF WIFI in the settings/wireless networks menu
1.connect phone to computer with us on usb mass storage mode and without adb debugging, create a folder called wififix on your external sdcard, unzip and copy the three .bin files to that folder
2.do the safely remove on windows/linux and than change connection to none, disconnect usb, enable adb debugging and reconnect your phone to the usb
3. run cmd/terminal
4. write as follows, after each line press enter:
adb shell
su (allow su on your phones display if its the first time you are using adb with su)
mount -o rw,remount -t ext3 /dev/block/mmcblk0p12 /system
rm /system/etc/firmware/wifi/*.bin
cp /sdcard-ext/wififix/*.bin /system/etc/firmware/wifi/
chmod -R 0755 /system/etc/firmware/wifi (you can use chmod 755 /system/etc/firmware/wifi/*.bin )
reboot
5. let your phone reboot, disconnect usb, unlock phone, enter pin, enable wifi and its working.
Feel free to comment in the thread and help eachother with problems and ideas
Click to expand...
Click to collapse
_Dennis_ said:
I made an update.zip for CWM if you need it. THis way you just have to apply the update after SBF/root. It SHOULD work....I did not try it.
Click to expand...
Click to collapse
Contribute, collaborate, conquer!! Outstanding.
It just seems strange that the OS wouldn't let you choose your country, like most routers already do... or is that taboo? Is wifi on Android mobile/cellular dependent? If so... what think tank came up with that...? How does Windows (desktop) handle this? It's not like laptops don't go on airplanes and visit other countries!!! BTW I can't believe I had to specify 'desktop'... I was thinking/worried ... "What if someone thinks I mean Windows (phone)." Seriously... who has a Windows phone? Let me re-phase... Who would be reading this specific thread and have a windows phone?

genatsvale said:
on the line: chmod -R 0755 /system/etc/firmware/wifi
I get: Bad Mode
then I use: chmod 755 /system/etc/firmware/wifi/*.bin
and after reboot the same problem... WiFi appears for few seconds and gets lost
Click to expand...
Click to collapse
The fix for that is to switch the numbers and -R, chmod expects to the the numbers first.
Code:
chmod 0755 -R /system/etc/firmware/wifi

Guys, before applying this method to my Bell Atrix (using it in Qatar, WiFi not working), I need to know:
1) Given it's a Bell Atrix, is there anything different I need to do?
2) Which root method should I use?
3) Did Bell's update fix this? Will this conflict with Bell's update? I'm planning to update my software once I get WiFi working.
Thanks

Can I apply this fix AFTER deodexing?

NOT WORKING for me either.
Rooted using Gladroot.
Non-deodexed Bell Atrix.
Followed all instructions.

Getting Ad-Hoc Mode on a SG Tab

I finally got it working, **It sees them, but disconnects right after I try to connect, at least its a good start**
I followed http://forum.xda-developers.com/showthread.php?t=854913 however, his instructions were not clear. I did post my answer in that thread, but, who is going to check page 9. I will just re-cap it Here.
Download wpa_suppliment from the post mentioned above, or here http://www.gasjen.com/?p=888 (I used this one, but they could be the same) I posted the one from Gasjen
Make sure your tab is rooted
For Froyo, go here
http://forum.xda-developers.com/showthread.php?t=812367
Gingerbread go here (This is what I am using)
http://forum.xda-developers.com/showthread.php?t=1115318
But I followed the directions and downloads Here
http://www.addictivetips.com/mobile/how-to-root-samsung-galaxy-tab-on-android-2-3-3-gingerbread/
(Its also good I went there, since I didn't know there was a download mode when you press volume down and power. I had no idea why I couldn't till I realized this )
Download the ADB shell
from here http://developer.android.com/sdk/index.html
1) Put the adb shell in the PATH
Right click my computer > Properties > Advanced System Settings > Advanced > Environment Variables > System Variables > Locate Path in the window. Mine is C:\Program Files\Android\android-sdk\platform-tools
2) Pull up cmd and type "ADB" (without quotes, nor this text too ), you should be able to see the help stuff if it worked correctly.
Turn on Tab
Make sure the tab is on
Make sure Wifi is off
Connect your tab to the computer
Upload wpa_supplicant to the Tab
In cmd, type this. ### is a comment
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
chmod 777 /system/bin ###This code was not in the XDA explanation, but a different source
cp "/system/bin/wpa_supplicant" "/system/bin/wpa_supplicant2" ###Copy the file just encase you mess up
exit ###Exits out of su
exit ###Exits out of the ADB shell
adb push "D:\wpa_supplicant" "/system/bin" ###First param is the location of the wpa_supplicant file, second is where you put it, instead of D:\wpa_supplicant, change it to where you put it
adb shell
su
chmod 777 "/system/bin/wpa_supplicant" ###I didn't do this the first time, nor was it shown in the previous thread. This is why it didn't work for me, and most likely, if you followed the previous thread and didn't do this, this will probably help :)
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system ###Changes it to read only
exit ###Exits out of su
exit ###Exits out of ADB shell
Turn Wifi on, and you should be able to see adhoc networks with (adhoc) attached to them.
____________________
Now, the only problem is that when I connect, I disconnect right away. I am searching for a solution to this, I think it may be in the /etc/wifi/wpa_supplicant.conf file. I am going to take a look and I will get back when I find it out. Or if you know what to do, tell me I will update the post when I find a solution.
I hope this helps!
~404

In case I need a second post!

I used root explorer to replace wpa_supplicant in/systems/bin/ . I did not experience any problems connecting tab to my nokia phone that has joiku hotspot as adhoc.
I looked at the properties of the wpa file seems the same. I also did not do any changes to the file whatsoever.
Sent from my GT-P1000 using Tapatalk

For root explorer, do you have to pay for that?

Whereis404 said:
For root explorer, do you have to pay for that?
Click to expand...
Click to collapse
yes but it is very cheap....

[GUIDE] Fix fingerprints and Wi-Fi after failed Oreo update

If, like me, you tried to update to Oreo while you were on Nougat rooted, you should have been greeted with some encryption problems, leading to an almost complete loss of data. Except Joocx posted a guide for how to get the data back, so you could get the data back. Nice, but how do we get a working phone back? Maybe you flashed Nougat again and restored your /data and internal storage backups, hoping it would work. It did work. Except Wi-Fi was broken and fingerprints didn't work.
If you haven't managed yet to get a working phone back, you can have a look here.
Restore Wi-Fi and fingerprints on Nougat or Oreo, without data loss
Reboot in TWRP (no matter which version, as long as you use 3.2.1-0 if you're on Oreo), and from your PC run the following commands.
If you feel like it, you can also run the three rm commands from the TWRP terminal, but it's hard.
Code:
C:\> adb shell
~ # rm /data/misc/wifi/wpa_supplicant.conf
~ # rm -rf /data/system/users/0/fpdata
~ # rm /data/system/users/0/settings_fingerprint.xml
Reboot to system, and voilà.
Update: 3DSammy has pointed out that plugging in your phone to your computer is actually not required. All the file management operations can be done using TWRP's file manager (in the "Advanced" section), the commands can be run directly on the phone using TWRP's terminal and OTG storage can be used for the ROM and Magisk. I had forgot about that file manager since I thought it was only for reading (not for writing/deleting).

Just so others know, TWRP under the "Advanced" menu item has a "File Manager" which allows you to remove each of these files. That's important for those who can't get to a PC with a working adb to mount the shell. I used OTG external storage to access the OTA and Magisk zips for flashing and storage of my nandroid backup.
Personally I would need the File Manger as I have a fully functioning PC fastboot but for some reason can't see my OP5 using adb. Not a big deal but there is a user-friendly built right into TWRP which always has "root" privileges to "/data".

zdimension said:
If, like me, you tried to update to Oreo while you were on Nougat rooted, you should have been greeted with some encryption problems, leading to an almost complete loss of data. Except Joocx posted a guide for how to get the data back, so you could get the data back. Nice, but how do we get a working phone back? Maybe you flashed Nougat again and restored your /data and internal storage backups, hoping it would work. It did work. Except Wi-Fi was broken and fingerprints didn't work.
If you haven't managed yet to get a working phone back, you can have a look here.
Restore Wi-Fi and fingerprints on Nougat or Oreo, without data loss
Reboot in TWRP (no matter which version, as long as you use 3.2.1-0 if you're on Oreo), and from your PC run the following commands.
If you feel like it, you can also run the three rm commands from the TWRP terminal, but it's hard.
Code:
C:\> adb shell
~ # rm /data/misc/wifi/wpa_supplicant.conf
~ # rm -rf /data/system/users/0/fpdata
~ # rm /data/system/users/0/settings_fingerprint.xml
Reboot to system, and voilà.
Update: 3DSammy has pointed out that plugging in your phone to your computer is actually not required. All the file management operations can be done using TWRP's file manager (in the "Advanced" section), the commands can be run directly on the phone using TWRP's terminal and OTG storage can be used for the ROM and Magisk. I had forgot about that file manager since I thought it was only for reading (not for writing/deleting).
Click to expand...
Click to collapse
Hey Z,
I was hoping you can walk me through this process as I'm still unable to fix this Wifi Issue. I've done exactly as you said in the guide but my wifi is still not working. It will turn on and everything but will not connect to a network. It just says "configuring ip address".

Dchoi229 said:
Hey Z,
I was hoping you can walk me through this process as I'm still unable to fix this Wifi Issue. I've done exactly as you said in the guide but my wifi is still not working. It will turn on and everything but will not connect to a network. It just says "configuring ip address".
Click to expand...
Click to collapse
Indeed, it's weird that it's still not working. But if I understood correctly, you are able to turn it on and scan networks, which is a step forward fixing the problem. The message you are getting means that there is a problem while requesting an IP address through DHCP. Try using a static IP on that network. If it works, then there may be a conflict it some other DHCP problem on your router. Otherwise, try on another WiFi network. If neither if those works, then I don't know.

zdimension said:
Indeed, it's weird that it's still not working. But if I understood correctly, you are able to turn it on and scan networks, which is a step forward fixing the problem. The message you are getting means that there is a problem while requesting an IP address through DHCP. Try using a static IP on that network. If it works, then there may be a conflict it some other DHCP problem on your router. Otherwise, try on another WiFi network. If neither if those works, then I don't know.
Click to expand...
Click to collapse
Thanks for the response Z! I just tried it and my wifi isn't stable at all when trying to connect to wifi. It's my workplace wifi that I usually have to sign into to access. It'll connnect and disconnect constantly. Is there anything you'd advise me to do?

Ok so I'm a little confused.
Are we running the command in one full line? eg:
C:\> adb shell ~ # rm /data/misc/wifi/wpa_supplicant.conf
My fingerprint sensor never died so I don't require that fix. I just cannot connect to wifi network. Detects it but once connection attempts in just reverts to 'saved' and tries to reconnect.
Also are you sure this is run once you boot into TWRP and not Fastboot mode?
Running from TWRP via ADB:
C:\>adb shell ~ # rm /data/misc/wifi/wpa_supplicant.con
/sbin/sh: /: Permission denied
From TWRP terminal manager I ran the same command and errored with sh: adb: not found.
I'm rooted and encrypted.
Cheers.

buzzfuzz1 said:
Ok so I'm a little confused.
Are we running the command in one full line? eg:
C:\> adb shell ~ # rm /data/misc/wifi/wpa_supplicant.conf
My fingerprint sensor never died so I don't require that fix. I just cannot connect to wifi network. Detects it but once connection attempts in just reverts to 'saved' and tries to reconnect.
Also are you sure this is run once you boot into TWRP and not Fastboot mode?
Running from TWRP via ADB:
C:\>adb shell ~ # rm /data/misc/wifi/wpa_supplicant.con
/sbin/sh: /: Permission denied
From TWRP terminal manager I ran the same command and errored with sh: adb: not found.
I'm rooted and encrypted.
Cheers.
Click to expand...
Click to collapse
Nah, the command is supposed to be run when the phone is in TWRP.
First, you use adb shell to open a terminal from your PC (ignore this step if you want to use TWRP's integrated terminal directly on the phone).
Then, when you're in the shell, run the rm command.

Well it seems this fix didn't work unfortunately :/ Wifi still cannot connect to any network.
Is the command simply deleting the file and it regenerates upon reboot?

buzzfuzz1 said:
Well it seems this fix didn't work unfortunately :/ Wifi still cannot connect to any network.
Is the command simply deleting the file and it regenerates upon reboot?
Click to expand...
Click to collapse
The file the command deletes is basically the "Wi-Fi" settings file, which contain identification settings for the network card amongst other things. If you keep the Nougat one while you're on Oreo, you can't turn on Wi-Fi, or use anything related to the Wi-Fi antenna; Thus, we delete it. That solves the problem "Wi-Fi doesn't turn on". Here, you've got another problem: "Wi-Fi can't connect". I have no clue of what could be causing this, this issue never happened to me. I'm gonna search a bit and update here if I find anything.