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.
I have an unrooted non Deceloper Edition Verizon Moto X. I am having trouble using adb commands from the terminal emulator. Specifically I am tying to use wake lock detector on kit kat without rooting my phone using the instructions here goo.gl/Yqdh2F
I've installed USB drivers from the Motorola Device manager, and I'm able to run adb commands from adb/fastboot on my PC, but when I try confirming the connection on the phone side using the terminal error, I get the following error /system/bin/sh: adb: not found. Does anyone know a way around this without rooting?
Does anybody has a dump of the whole NAND flash of a rootable chromecast? (ideally while still in the original factory state)
If not, could someone with a rooted chromecast dump the bootloader (partition)? (basically the first couple of blocks/megabytes)
Any help would be very welcome
To help, if they manage to get adb over wifi working, run
Code:
adb shell su -c 'dd if=/dev/block/platform/*/*/by-name/bootloader' > ccbootloader.bin
. This command should, as root, write the bootloader to stdout, which we will take and write to a local file. (For the non-technical people, it makes a bootloader dump and puts it on your computer) please note that this requires your chromecast to be rooted and have adb working over wifi.
Sent from my iPod touch using Tapatalk
Definitely talk to @rekids - they've been working on this stuff.
I flash "mmcblk0p7" partition by mistake.
May anyone use this code to help me recover:crying:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7
I could get you an edited copy but you would need to insert your IMEI and your providers ID (ORANG001, TMOB etc, etc)
I am unsure it would work, possibly with SIMLOCK and unlock and related codes.
Do you know how you will have to flash the image as well?
Bashing away at my HTC Desire C
So, after owning my beautiful Moto X for 1 month, I found that the screen is not nearly as shatter resistant as my old iPhone 4S. After managing to completely shatter it, I called Motorola up for a replacement (which for a customized Pure cost $125) and it was on its way, but before that I needed to get my old data off. Luckily I have unlocked my bootloader and rooted my phone in advance, but i had turned off USB debugging and had a passcode lock. All of the guides for making a full backup assume that you have screen access. After messing around for a few days, I finally managed to make a full backup of my phone. I thought I'd put together this guide for anyone else who has the same issue.
Assumptions
Your bootloader is unlocked and phone rooted (do not try to unlock it now or it will wipe the phone)
Your phone is not encrypted (there's still a way around this which I'll cover but I did not have to use)
You have ADB/fastboot set up on your computer (and have tested it at least once)
Required files/guides
CWM recovery file - http://motoxroot.com/cwmtwrp-recovery-for-moto-x/
Lock Screen removal guide - http://forum.xda-developers.com/showthread.php?t=1409304
SQLite DB editor (I'm on Windows) - http://sqliteadmin.orbmu2k.de/
Androidscrencast - https://code.google.com/p/androidscreencast/
ADB keystroke events - http://thecodeartist.blogspot.com/2011/03/simulating-keyevents-on-android-device.html
Steps
The first thing I did was download the customer CWM image for the 2014 Moto X which can be found here:
Code:
http://motoxroot.com/cwmtwrp-recovery-for-moto-x/
Next I went rebooted the phone into bootloader mode by holding "Volume Down + Power" for about 15 seconds. I could not see images on the screen but I could tell when it lit up.
Note: If you have an encrypted phone, you can use an OTG cable and a standard USB keyboard to type in the password blind. I used something similar for the PIN code, however this guide does not actually need to worry about that
Test that you have fasboot access by running
Code:
fastboot devices
You should see your device listed
Boot the CWM recovery image (you do not have to flash it which is nice)
Code:
fastboot boot XT1095recovery.img
Wait a few seconds and verify that you can now access your phone via ADB
Code:
adb devices -l
If this works, you now have a shell to be able to do the next part which is removing the passcode and enabling USB Debugging I followed the guide at http://forum.xda-developers.com/showthread.php?t=1409304 to do remove the lock screen
Mount the data partition of your phone by running
Code:
adb shell mount data
adb shell mount system
Grab the settings DB from the phone and copy it locally (Other guides say to copy to an intermediary, but since you're using a recovery ROM the files can be directly accessed)
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
Open the file in your SQLite editor of choice and run the following statements
Code:
UPDATE secure SET value=65536 WHERE name='lockscreen.password_type';
UPDATE secure SET value=0 WHERE name='lock_pin_autolock';
While we have the settings DB open, it's also a good time to enable ADB Debugging by running the following statements (credits to http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb though I had to mod some more stuff)
Code:
UPDATE global SET value=1 WHERE name='adb_enabled';
UPDATE global SET value=1 WHERE name='development_settings_enabled';
Push the file back to it's original location
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
From here, the next set of commands should be run within the shell. You can access it by running
Code:
adb shell
Remove some existing property files
Code:
rm /data/property/persist.service.adb.enable
rm /data/property/persist.sys.usb.config
Add in the ADB settings
Code:
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
Correct the permissions for the settings.db file
Code:
chown system:system /data/data/com.android.providers.settings/databases/settings.db
chmod 660 /data/data/com.android.providers.settings/databases/settings.db
At this point, everything is ready to go and we're ready to reboot to your real install with no pin code and ADB enabled.
Reboot your phone
Code:
adb reboot
Run androidscreencast (don't worry about the keyboard/mouse instructions they don't work). Chances are the screen will be blank, press the Power button your phone and wait (it's got a *very* slow refresh rate)
Once you see your desktop, you can now run an ADB backup. I like getting everything, but this will take a while because it grabs all images, music, SD card stuff, etc.
Code:
adb backup -apk -shared -all -f backup.ab
On the screencast you'll see the prompt pop up asking you to enter a password and confirm. This was the part that took me a while and you have to do it fairly quickly otherwise it'll time out. In a separate windows run
Code:
adb shell input text <yourpassword>
adb shell input keyevent 61
adb shell input keyevent 61
adb shell input keyevent 66
At this point, you should see a full backup kicking off and running. You can run a logcat to watch the process of it. In some cases a full backup may hang if a resource has a file open, the two commands to work with this are:
Code:
adb shell logcat | grep BackupManagerService
To kill a process the backup is hanging on, enter the shell
Code:
su
ps | grep <nameOfProcess>
am force_stop <nameOfProcess> (the clean way)
kill <pid> (the dirty way)
Hope this helps! This took me a little while to figure out but now I have a full backup and my new Moto X will be here within the
week.
Okay so an ADB full backup sucks for a restore. Luckily I got a nandroid backup instead and that worked much better. There's some stuff you have to do with mapping /sdcard for it to work on the Moto X. I'll update this post soon with that information.
Thanks a lot for this! Helped me recover all my data from a Moto X with a completely broken blank screen!
This is an awesome Guide! Congrats!! I have a different situation. My Moto X 2014 is the XT1097 variant. The phone was neither rooted nor had an unlocked bootloader before the screen died. I downloaded the stock rom for my device, and flashed it with RSD Lite, since the program sees the phone connected in fastboot mode. Do you think I could use this method to reach the desktop? Also, the recovery.img in your guide is for the XT1095. Would it work for the XT1097? I know I can unlock the bootloader via fastboot, but what about rooting? Thanks in advance!!