Related
Okay so now i finally have my droid working on tbaytel, there was a few issues i ran into with android for working on it but it should be solved for now. Just follow these steps carefully and if your phone ever gets in a boot loop don't worry because you can fix it with RSD Lite. This Guide was written by Dexter Fichuk
What you will need:
Everything is listed in this text file with with the links seeing as i cannot post them straight onto here because i am a new user so no links just downlaod the attached file at the bottom
1. First you need to root your phone. i just used the Lifehacker Droid rooting guide because you will end up losing all your data anyways with this guide. So for rooting use the lifehacker guide by googling "lifehacker droid rooting" guide and download there Files
2.Now Fire up rsd lite again and flash the SPRecovery SBF file you downloaded from mediafire onto your droid.
3.Now Shut your phone off and turn it on while holding the X Key and you should get sprecovery, now click mount options -> Enable Usb Mass Storage and now on your compter drage the blugess beast zip file onto the root of your card. Delete the update.zip file there and then rename Buggless Beast "update.zip" but without the quotation marks. Now Click Disable usb stoarge and go back with the power button. Click Install -> Install /sdcard/update.zip (deprecated) and let buggless beast install
4. Now install the Motorola USB Drivers
4. Now Turn the phone off and turn it on while holding the T Key down for diagnostics mode.
5. Start up HW Virtual Serial Port which you can download from the top of this page. Click Login and the password is admin, Put Port Name 5, ip adress 192.168.16.2 and port as 11008. Click Settings on the top bar and disable NVT Enabled.
6. Now open up CDMA Workshop and change the port to COM5 and click connect at the bottom. Click Security and in the SPC box type 000000 and click SPC -> Send and it should say its correct and phone unlocked.
7. Click the Memory tab and where it says NV Items click Write and find the tbaytel nv items you downloaded.
8. Goto the other tab and in the prl box click Write and find your Tbaytel Prl you downloaded. Go back to the security box and in the ESN box click read and write down the first number it gives you.
9. Now you need to go and get it hooked up so make sure you bring that number you just wrote down and tell them that that is the ESN Number. And tell them to get to the programming screen is ##PROGRAM on the dialer not the keyboard so you might want to write that with the ESN number.
10. Now once you get your phone back it should be hooked up and everything should be working except for me i found that i couldn't get incoming texts working, i called Tbaytel, Verizon and Motorola and they couldn't figure out the issue. After a while i found that if you use the Blended Bliss rom Which was ported over from the htc desire the radio framework is different and it worked. its the only solution i could find to the problem if you find another please post it
11. Follow the Instructions for installing Blended Bliss if you cant get incoming texts working but after you get it installed go to SPRecovery and do another Factory Reset on it.
This Guide was Written by Dexter Fichuk
Thanks to:
Bigslanki for the flashing to cricket guide
Whiterabbit.org for the NV Items
xdxdaustin for Blended Bliss
tedo911 for the Tbaytel PRL
SirPsycho for sprecovery
and DexterFichuk which is me
If you have any other questions please leave a comment and if you need more of the setting schances are i have them, and if you find a solution to the incoming text problem please post, until then we are limited to Blended Bliss
What droid are you ussing and where did you get it for how much
Enable USB Debugging and Run the batch file from the attached and follow onscreen Instructions.
75 downloads - no confirmation - files removed.
Doesn't seem to want to temp root my phone. Tried with and without restart numerous times. The phone is rooted, and adb is installed correctly (or at the very least it's always done what I've wanted it to) but the batch times out when checking for temporary root every time. Oh well it was worth a shot.
I think "usb debugging" is not enabled on your phone.
Go to settings, applications, developement and enable usb debugging.
i'm with Canadian Mobilicity ... i am using Bionix V (official Froyo) and its giving me almost instantaneous GPS fix...
Axura worked as well... but this one is damn fast....
What are the commands from the terminal?
This sound good.
Do I install via cwm?
Sent from my SGH-T959 using XDA App
a1jatt said:
I think "usb debugging" is not enabled on your phone.
Go to settings, applications, developement and enable usb debugging.
Click to expand...
Click to collapse
No, USB debugging definitely was on. I always make sure it is. Otherwise straight ADB wouldn't work properly like I mentioned it always has for me
Besides, it tells you in the notifications bar if it's on whenever you plug in, and it's definitely on.
Maybe later I'll open up the batch and try the commands by hand from ADB.
hussarfilms said:
This sound good.
Do I install via cwm?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
No, just double click on the install file.
Deathsnapper said:
No, USB debugging definitely was on. I always make sure it is. Otherwise straight ADB wouldn't work properly like I mentioned it always has for me
Besides, it tells you in the notifications bar if it's on whenever you plug in, and it's definitely on.
Maybe later I'll open up the batch and try the commands by hand from ADB.
Click to expand...
Click to collapse
Maybe,
it gave me same error only when i had it disabled.
a1jatt said:
Maybe,
it gave me same error only when i had it disabled.
Click to expand...
Click to collapse
Going through and doing it by hand. Pushing the files now. The line:
"%adb% -d push %gps% /system/etc"
makes total sense, in that it's pushing the gps.conf file to the folder /system/etc
but the lines following it:
"%adb% -d push %f1% /system/csc/WND/system/CSCFiles.txt"
and so on, they seem to be trying to push the txt file to a txt file already on the device. The shell tells me that "/system/csc/WND/system/CSCFiles.txt" isn't a valid file or directory.
There don't seem to be any lines that make directories /system/csc/WND/system/{files}
Should I assume that's still the intended destination and not an error? Go ahead and put some mkdir lines into busy box?
EDIT: DONE. It rebooted, installed packages, etc. Formatted data and cache when it did, so booting was like first boot (took a while, showed the general 'new rom' screens, etc.) Checking GPS now/soon.
Does it work on Mobilicity?
good work！
It should fix gps on mobilicity, i will add apn settings for mobilicity later.
On mobili u dont have to do *#06# or *#272 , just run the file and reboot.
giving me an error too
Just wanna be clear
I run the prog
Let it do its thing- exit
Then reboot?
Sent from my SGH-T959 using XDA App
How do you get it to work for tmobile in usa?
Sent from my SGH-T959 using Tapatalk
sorry but what does this do? I'm on wind mobile
I'm also using a T-Mobile Galaxy Vibrant on the Wind Mobile network.. in Vancouver.
Does this simply change the settings to use something other than supl.google.com?
it doesnt work gives me an error
I'm going to hold off on this until the errors have been addressed.. seems like there is a bug in the script (maybe).
Note to all users: This thread is now closed. I will no longer be updating GladRoot as there are more reliable and simpler methods for obtaining root on the newer firmwares. Support can still be found through PM for the older firmware versions.Note to all users on non-AT&T/Bell devicesThis is currently untested on anything but AT&T and Bell phones. You can run this on any phone, and at the very worst, it just won't work. There's almost 0 chance you will harm your phone by running this, so feel free to try. Please report back what firmware version you tried it on, and if it worked or not and I'll update the first post here to reflect. I don't have any device but an AT&T Atrix so I can't test any of the other versions myself, I need your help!GladRoot v4.3 (AT&T 1.83 Update Supported - READ DIRECTIONS)
In the interest of cleaning things up and putting all the current information into one place, with links to everything you'll need to get this working.
Basically, there's a ton of misinformation floating around about current root methods. This is your one stop shop for all your root needs. To explain, the SuperOneClick method installs busybox a second time. The Atrix already has busybox installed, so there's no need to install a duplicate. This can cause issues with other mods. GladRoot will take care of everything SuperOneClick did. I've contacted the developer to see if there's a way around this.
Start Here
If you have an AT&T Atrix and want to update to 1.57/1.83 with root, follow the first set of instructions.
If you have a Bell Atrix or an AT&T Atrix on 1.26 or 1.52 and just want to root, go to the second set of instructions.
Please, please, PLEASE, read the whole first post before asking questions. Chances are your question is already covered in the directions.
If you have any features requests or notice any bugs, please PM me, I might miss them in this thread.
To unroot, just run unroot.bat
Note to users seeing "Unable to detect device" error: Disable USB debugging, and turn it back on. Make sure your connection type is set to None. If you need the drivers, they are available here: 32-bit Drivers and 64-bit Drivers
Little bit of additional info here:
This will root your phone. There is no need to run aRoot before this, and you should NOT be running SuperOneClick anymore.
This has options to enable sideloading and the tethering APN. Enabling sideloading will not add an Unknown Sources checkbox, it will just enable it. I don't see any reason for the need to disable this, so unless someone can make a case for the checkbox (that makes sense for users), it will remain this way.
Unlike v1, the scripts are fully automated. You need only click "allow" to superuser when prompted for certain steps.
If you are already on 1.57/1.83 and do not have root, you MUST flash back to 1.26 for this to work. NO EXCEPTIONS.
Installation instructions: 1.26 to 1.57/1.83
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is 1.2.6 and is not running any mods, I recommend a fresh SBF flash of 1.2.6. Download links and installation instructions here
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions (If you're using Windows 7, run as admin by holding down control and double-clicking).
Verify that there are no errors before updating.
Go to Settings -> About phone -> System updates
Follow the on-screen instructions. First download the update (you will need a Wi-Fi connection for this), then it will prompt you to install.
The update will reboot the device and install itself. If this part fails it's because you are not on stock 1.2.6 firmware. Start over and read the directions.
When it boots back up, verify USB debugging is still on. Some users report that disabling and re-enabling USB debugging solves a few issues with the script detecting your device (Settings -> Applications -> Development).
Run afterupdate.bat (If you're using Windows 7, run as admin by holding down control and double-clicking).
Make sure you allow the superuser request on your phone or it WILL fail.
All done! Enjoy your rooted Atrix on 1.57/1.83!
Screenshots**REMOVED FOR NOW UNTIL I GET A CHANCE TO UPDATE**Installation instructions: 1.26, 1.52 and Bell Atrix
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is the correct version. Go to Settings -> About phone -> Build number and make sure it matches one of the following:
OLYFR_U4_1.2.6
OLYFR_U4_1.5.2
OLYLA_U4_0.37.4
If you need to flash an SBF first, Download links and installation instructions here.
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions.(If you're using Windows 7, run as admin by holding down control and double-clicking).
When you get to the step that asks if you're updating to 1.57, just say no.
Verify that there are no errors.
All done! Enjoy your rooted Atrix!
DISCLAIMER
I am not responsible if this bricks your phone or if it doesn't work properly for you. I've done everything I can to ensure smooth execution.
If you have any issues, feel free to PM me, reply to this thread, or come find me on IRC (I'm Fenrir or fen|works on IRC)Special Thanks
Sogarth for adb wizardry, shawnbuck for the concept and getting the ball moving, designgears for the initial aRoot script method, and everyone on XDA and IRC who helped contribute and test.Changelog
Version 4.3
Cleaned up script a tiny bit
Added textual support for 1.83 (the method hasn't changed, it's always worked)
Version 4.2
Added Uknown Sources checkbox to sideloading, as well as enabling it.
Added unroot script.
Version 4.1
Fixed a few minor aesthetic errors in the script
Version 4
Added a pause after the superuser request so if it fails, users can read the output.
Started mapping out log process for error catching.
Removed abd kill-server from the beginning of the file as I think it might be causing problems on slower machines.
Version 3
Removed option to root, it just roots. This will not harm your phone if you're already rooted.
Added support to root all devices, including Bell Atrix.
Cleaned up and improved script.
Changed name from Root v2 to GladRoot (Which is Root v3)
Version 2
Massive improvements to deployment script
Removed need to manually enter commands
Version 1
Initial Release
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Vigneshd said:
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Click to expand...
Click to collapse
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
So do this version allow sideloading?
awww yeahhh
PixoNova said:
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
Click to expand...
Click to collapse
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
plmiller0905 said:
So do this version allow sideloading?
Click to expand...
Click to collapse
i assume so. i'm able to sideload
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync. I put the new retainroot folder in C:\.
Nothing works.
Have I missed something?
Any ideas?
drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
open command prompt and type:
Code:
adb devices
What does it return?
drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
USB debugging on?
USB mode set as None?
Ririal said:
open command prompt and type:
Code:
adb devices
What does it return?
Click to expand...
Click to collapse
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
shawnbuck said:
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
Click to expand...
Click to collapse
So is this a hole that allows us to exploit another hole?
s0dhi said:
USB debugging on?
USB mode set as None?
Click to expand...
Click to collapse
Yes to both.
drjim said:
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
Click to expand...
Click to collapse
I changed directory to C:\ in cmd and typed in adb devices. Its response: List of devices attached.
Only thing I haven't done is flash SBF (whatever that is). But I'm dling it now...along with RSDlite (whatever that is).
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
PixoNova said:
So is this a hole that allows us to exploit another hole?
Click to expand...
Click to collapse
This isn't quite a hole, just a little magic-show type trickery really.
tdamocles said:
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
Click to expand...
Click to collapse
What do you mean second command prompt?
Failed backup?
OK, I'm on stock 1.2.6, said yes to already rooted and yes to side load and no to tether. It starts and says pushing backupsu.sh... then retval = and backup failed to execute properly. What am I doing wrong? I have developer on and usb = none. Can't seem to get it to work...
when i run beforeupdate i get backup failed to execute properly
am i missing something?
Hey, guys after hours of thinkering it seems i devised a fix (at least a temporary, i guess it can be better implemented), but still wifi works with turned on radio.
I will not be doing any scripts or whatever.
DISCLAIMER
THIS IS ALL ON A BASIS OF INFORMING PEOPLE
I AM NOT RESPONSIBLE FOR ANY DAMAGE, LOSS OF DATA, OR BRICKED DEVICES IN CONJUNCTION OF TRYING OUT THESE STEPS
DO IT ON YOUR OWN RISK.
K now the requirements:
1. nonworking sim card (or att sim card)
2. RSD lite 5.0
3. stock 4.1.2.6 SBF flash file
4. Installed drivers on the computer for rsd
5. GladRoot http://forum.xda-developers.com/showthread.php?t=1016060 than you very much Ririal
6. OTA update
7. Working adb shell (there are other ways too but i prefer this one so ill write how i did it)
8. SQL editor, i used SQLite database browser (get it online its freeware)
9. titanium backup (if you wish to backup things, YOU MUST NOT RESTORE the [SETTINGS/BLUETOOTH] Settings Storage 2.2.1 however.
10. turned debug mode on when using adb
The process:
1. backup your data
2. Flash the stock image with RSD lite as its written here http://forum.xda-developers.com/showthread.php?t=991072 thank you kennethpen
3. put in the nonworking/att sim turn on the phone use wifi to configure motoblur
4. do not download the update yet
5. obtain root as described here, use the 1.5.7 method tho since we will be updating the ota http://forum.xda-developers.com/showthread.php?t=1016060
thanks again ririal
6. download and install ota update
7. do the afterupdate with the GladRoot
8. still on wifi, set up google account, update market gmail etc.
9. use adb/root explorer to copy the /data/data/com.android.providers.settings/databases/settings.db file to your sdcard into a directory you made before (name doesnt matter) example:
Code:
adb shell
su
cp /data/data/com.android.providers.settings/databases/settings.db /sdcard-ext/test
10. put phone into airplane mode, turn off phone
11. put in your sim card, turn on
12. let it boot and wait a min or two
13. before sliding press and hold the off button and choose airplane mode (it is IMPERATIVE that airplane mode is turned on)
14. sign into motoblur again (wifi should still work - turn it on tho since your in airplane mode)
15. repeat step 9 but copy to a second directory (lets say test1)
16. turn airplane mode off - you will loose wifi and sign into motoblur again
17. repeat step 9/15 but copy to a third directory (lets say test2)
18. copy the files from test2 and test1 to your computer - obviously to two different folders (use mass storage setting or adb pull)
19. open up the settings.db with sqlite from the not working config (in our case the one in test2) go to browse data and table secure
20. find the entry wifi_country_code and the value will be the one of your country (at least so it was with me), change that value by double clicking on it to US
21. Save the file
22. copy to your sdcard via usb to a directory lets name it "works"
23.turn off your phone, and put in the nonworking/att sim card, power it up
24. register motoblur again blah blah (ye its annoying there are ways around but that comes later and we needed it for the ota update)
25. turn the airplane mode off (its imperative to do so)
26. now we use adb again:
Code:
adb shell
su
cd /data/data/com.android.providers.settings/databases
rm settings.db
cp /sdcard-ext/works/settings.db .
chown system settings.db
chgrp settings.db
chmod 440 settings.db
cd ..
chmod 555 databases
exit adb shell with ctrl+d (in linux dont know about windows)
27. turn off phone, put in your sim card, turn on phone, register motoblur
28. most probably wifi will work for a moment than it will stop working and youll get a notifiaction lost data connection and something on (at least so it was for me)
29. use the wifi toggle on/of button to turn off and on the wifi a few times, than at the third or fourth time turn it off than on than immediately go into the browser and click on refresh as soon as you see the wifi icon in the notification tab. WiFi should work now, you can even turn it off and on with the wifi toggle button and it still works.
30. ANOTHER WARNING THO, THERE ARE QUITE SOME DRAWBACKS TO THIS METHOD (WHICH I HAVENT DISCOVERED ALL YET, TO BE HONEST BUT IM SURE THERE ARE QUITE SOME - SINCE WE DO NOT ALLOW THE SYSTEM TO EDIT THE SETTINGS.DB ANYMORE - BY CHMODDING THE PERMISSIONS), AN ISSUE I SAW IS THAT YOU CANNOT GO INTO AIRPLANE MODE ANYMORE - that is because the airplane mode state is saved in the same settings.db as the setting that blocks wifi, and if you just change that one and dont write protect the file and the databases folder the system just overwrites it again, so for now this is it.
AGAIN this is all on your own RISK, i cannot bi liable for anything out of the ordinary that happens, damages or whatsoever your phone or even you.
So now im awaiting responses if it works for you guys.
Oh and a few of the steps are just for backup purposes
Many thanks goes to Azuzu aswell, he was of great help all the time.
What about for the Canadian Bell Atrix can you please help us.
When I insert non working sim card into the phone, wi-fi working only once, after booting. Then when phone is going to lock, wi-fi is sleep and never work again. Is it instruction help to work with wi-fi during the day without rebooting? Thanks for instruction!
---
All is fine with Wi-Fi when it in Motoblur...
What about GPS?
May be needed to add GPS ON in this instruction?
Thanks guys. Its work for me. But too much DRAWBACKS. GPS does not work, settings are not saved
my friends you figured it all out like i did after a day of testing.
As i already said before there are some rather big probles that arise with this method, however for now this is the only way i found to having a working sim +wifi working.
Basically all the issues arise from the settings menu, since the settings from there are stored in the setting.db file that we disallow changing, due to this fact, i have devised a rather simpler way to do all the above + apply your specific settings - however you still wont be able to change them once you change the permissions.
1. gps state cant be changed as reported
2. ringtone/notification tone cant be changed
3. USB mode is stuck in NONE mode or the one you changed it to before doing read only
4. Possibly you cant pair new BT devices (havent tried that but i assume it might happen)
5. cant change lockscreen type (so if you pick fingerprint afterwards it wont change the lockscreen)
6. more possible problems, still if you want wifi you will endure some of those, they are however rather easy to fix, for people who dont change things all the time.
7. i found out that you have to turn off and on wifi (with the widget or in the networks menu) 2 times to make it work and it stops working if your phone changes the network from 3g to 3g or vice versa, however you just turn wifi off and on again and its fine (eventually you can just set your phone to 2g only or 3g only - either the dialer method or edit a config file - ill post that another time)
8. airplane mode not changing as stated above
So i did it like this this time:
lets assume you already have the phone 1.5.7 rooted (you can even have 1.2.6 rooted but the ota update brings nice features like longer battery, better fingerprint reader etc) and activated. NOW THIS SHORTENS THE PROCESS BY FAR and improves on the things that werent working before, it might lower battery life minorly but, well mine is still at 70% after ~16 hours so )
YOU WILL HAVE TO DO THIS ONLY ONCE (well at least until you want to change your ringtone hahaha )
1. Put in your working sim (just into the rooted atrix and the databases dir has to be read write like before, if you followed my guide above you have to go with adb shell to /data/data/com.android.providers.settings and write chmod 755 databases)
2. turn on phone in normal mode
3. set all your settings as you like and i really mean all - ringtones notifications - everything you can think of
4. turn all the networks on - wireless (it wont work but the state has to be on), bluetooth, gps - the thing is you can always turn them off, but if you write protect the file with them off you cant turn them on properly
5. pair your bluetooth devices (all of them) - havent tried yet if necessary but i think it is
6. reboot phone into normal mode, assure yourself that all the things are as you like
7. connect phone in debug mode, and set usb to none (it will stay in the none state, but you can always copy stuff with adb over, to your sdcard/internal phone mem as opposed to choosing mass storage mode where you have no adb access to them, but that is your choice ( you can manually change the state in the settings.db before making it read only, but i wont go into those details now)
Code:
adb shell
su
cd /sdcard-ext/test
cp /data/data/com.android.providers.settings/databases/settings.db .
ctrl+c/d to exit shell
8. connect phone in mass storage mode, open the settings.db file in the /sdcard-ext/test with the sqlite editor go to the brose tab, and secure, change the wifi_country_code value to ALL (last time i wrote US but ALL works fine so its more relaxed), save it
9. change the usb connection mode back to none
10. failure to chown and chgrp the settings.db to system and chmod it correctly can results in a soft brick
Code:
adb shell
su
cd /data/data/com.android.providers.settings/databases
rm settings.db
cp /sdcard-ext/test/settings.db .
chown system settings.db
chgrp system settings.db
chmod 440 settings.db
cd..
chmod 555 databases
reboot
11. the phone shoudl reboot now with all the networks turned on, you can use the widgets (or int he wireless menu) to turn off wifi and bluetooth (tested it myself and it works), havent tested gps turning off yet, but its no problem since gps turns on itself only when apps use it (maps etc, weatherbug can use it aswell, so might check into it if its permanently turned on than)
12. turn wifi off and on 2-3 times, than turn it on, it should be working now
Thanks for testing this out to confirm that it works at least
Anyhow if someone might get a clue what issues the command to change the wifi_country_code hes encouraged to share, so we can only fix that problem and there wont be these side effects than
you can however change all the settings by just editing the settings.db with the sqlite editor manually, youd have to figure out all the parameters and values yourself (some are fairly easy - for instance for usb mode, some can be rather hard - for instance ringtones, cuz you must have the path and everything)
EDIT, YOU CAN LEAVE OUT THE PAIRING BLUETOOTH DEVICES STEP, pairing works, i just tried it with an apple bluetooth kb, and its fine.
RacecarBMW i cannot say anything with certainty, since i dont have one to test it on, but probably the same method would work for the bell atrix (use the method in the post above, with the ALL value for wifi_country_code), however you have no sbf to flash and its way more dangerous that you will create a softbrick, so please be very careful and its all YOUR RESPONSIBILITY. I AM AND WILL NOT BE LIABLE FOR ANY ADVERSE EFFECTS.
We need to lock only some rows in db file or creating daemon which would keep these lines in memory. Is it posible with SQLite?
crnkoj Please change on step 10 in listing:
cd /data/data/android.providers.settings/databases
to
cd /data/data/com.android.providers.settings/databases
I do all steps and my GPS works fine... Thanks
how can i undo this:
chown system settings.db
chgrp system settings.db
chmod 440 settings.db
chmod 555 databases
what's default settings?
loggin111 said:
how can i undo this:
chown system settings.db
chgrp system settings.db
chmod 440 settings.db
chmod 555 databases
what's default settings?
Click to expand...
Click to collapse
you can just enter to another folder to /data/data/ directory with cd and run ls -l to view directory permissions.
chmod 755 databases
and something like 755 for settings.db
thank you Jartyn, replaced that in step 10. And yes Jartyn exactly as you say we jsut have to keep this line permanent and everything else changeable (maybe there is an option in sqlite to block only 1 line? - i dont know so much).
I do however know now, which process is changing this:
it is the WifiStateTracker ( http://www.androidjavadoc.com/1.1_r1_src/android/net/wifi/WifiStateTracker.html ) from android.net.wifi , i however dont know where to find this on the phone.... we would most probably only have to change one line in the WifiStateTracker and it would work fine (however this still wouldnt be fixing the source, we would just fix the change in country code, yet the reference to which its compared is still unknown to me, but i think it would suffice for us) the funny thing here is the WifiStateTracker is not in the official android tutorial tho:
http://developer.android.com/reference/android/net/wifi/package-summary.html
so if anyone knows where to find this we could fix it easyly
1.5.2
crnkoj said:
thank you Jartyn, replaced that in step 10. And yes Jartyn exactly as you say we jsut have to keep this line permanent and everything else changeable (maybe there is an option in sqlite to block only 1 line? - i dont know so much).
I do however know now, which process is changing this:
it is the WifiStateTracker ( http://www.androidjavadoc.com/1.1_r1_src/android/net/wifi/WifiStateTracker.html ) from android.net.wifi , i however dont know where to find this on the phone.... we would most probably only have to change one line in the WifiStateTracker and it would work fine (however this still wouldnt be fixing the source, we would just fix the change in country code, yet the reference to which its compared is still unknown to me, but i think it would suffice for us) the funny thing here is the WifiStateTracker is not in the official android tutorial tho:
http://developer.android.com/reference/android/net/wifi/package-summary.html
so if anyone knows where to find this we could fix it easyly
Click to expand...
Click to collapse
hi
does it work with 1.5.2 rooted?
i flashed sbf back from unroot 1.5.7 to 1.2.6 , i didn't gladroot because i had not wifi for update & after update.bat
so i stopped @ 1.5.2 & i cannot update anymore, please help me to activate my wifi.....
zeidof you can do it on the 1.2.6 rooted aswell, use the same steps as described above, it should work fine.
hey guys what wifi issues? i have a ATT on vodafone UK and i dont seem to see any issues.
crnkoj said:
zeidof you can do it on the 1.2.6 rooted aswell, use the same steps as described above, it should work fine.
Click to expand...
Click to collapse
Hi can this fix be on a custom rom? i mean it will be included on a custom rom..
ronaldo, use search ... http://forum.xda-developers.com/showthread.php?t=1010942&page=3 lucky you arent one of us who have this issue.
emorej, if you read my first post, it says i wont be doing any scripts/cwm flashable updates/custom roms. If anyone wants to implement this in his rom hes free to do so, he has to be careful tho, since basiically the script that updates it, has to change only the wifi_country_code ALL and than make the databases folder read only, it must not copy over a generic settings.db since there are user specific things in it.
Jartyn and i are trying to figure a more source problem related fix for the issue, but that will take quite some time i fear.
Here is an even better solution from akizakian
http://forum.xda-developers.com/showthread.php?t=1058260
Simplest Solution
I had this same issue and the simplest solution is here:
1. Extract the attached zip file and you will get two files.
2. Turn off Wi-Fi, replace the two files in
/system/etc/firmware/wifi
This can be done using adb or Root Explorer.
turn Wi-Fi back on, and that's it!
Mate you are mistaken, its two totally different issues you and i are talking about, yours is that 5ghz isnt working, mine is that wifi isnt working in certain countries at all. by copying the files you supplied my wifi again stops working, because there is a country lock within the moto atrix wifi drivers (the version doesnt matter, may it be 1.2.6, 1.5.2, 1.5.7 or 1.8.3, the issue you fixed with your method is only the nonworking 5ghz on the 1.5.2. leaked sbf)
ceo.mtcl said:
I had this same issue and the simplest solution is here:
1. Extract the attached zip file and you will get two files.
2. Turn off Wi-Fi, replace the two files in
/system/etc/firmware/wifi
This can be done using adb or Root Explorer.
turn Wi-Fi back on, and that's it!
Click to expand...
Click to collapse
The LG Optimus wifi drivers fixed my simunlocked wifi problem in qatar.
The other solutions that were being thrown around did not.
seems moto is gonna fix it with an update:
https://supportforums.motorola.com/thread/50598?start=15&tstart=0
I've had a Droid 3 for a little under a year now. For the past few months I was having an 'issue' where the phone would not vibrate when I got an SMS message. Apparently this is a known issue caused by installing a non-stock SMS app from the app-store. I took it to the Verizon store and the guy put in a request for a replacement phone. He knew I'd rooted it and just said to make sure I unroot it, uninstall the bootloader, and factory reset before sending it in. I did all 3 things however the reset didn't reset my custom boot animation so I figured I'd activate the phone real quick, reroot, change that, and unroot. I started the activation process and I get to the "Add Accounts" screen, added my Google account, and hit Done. It asks about location services, I hit "Next" and then com.motorola.setup crashes and I have to force close. If I hit the Home button it takes me right back to the "add accounts" screen and I'm stuck in that infinite loop. I can still receive texts and reply to them from the notifications menu, I can send and receive phone calls with voice commands, I can access the browser, but that's about it. I cannot get to the home screen and I cannot open the settings 'app'.
I brought it back to the Verizon store and they were baffled, told me that Verizon would probably charge me full retail for the replacement if I sent this once back, so I sent back the replacement phone and am stuck with this one now.
I think what caused this is that I had the 'Bloat Freezer' app installed and I had frozen a bunch of the default Verizon apps. I didn't unfreeze them before the factory reset and I have a feeling that's what's causing the issue. I had the idea to re-root the phone and install Bloat Freezer again from the Play store but the Play store isn't recognizing my Droid 3 anymore.
Any suggestions?
Factory reset is a deceiving term. It resets it to factory user data (none) and settings. It doesn't restore the system. What you need is an SBF to flash the entire phone to factory software, overwriting all partitions. First though, you must find which system you had. Since you didn't recently get this phone, did you accept an OTA update within the last month or so? If so, head over to the Dev area and download the stickied SBF file to return you from .906 to .890. If not, there is an SBF in the General area called Quick Unbrick or something like that.
http://www.youtube.com/watch?v=pcne9tFtBxY
Awesome! Thanks for the info. I'll give this a try when I get home from work tonight. Do you know if there's any way to tell what version I need without the settings app? Or perhaps if there's a way to forcibly open the Settings app?
If you've had your D3 for over a year and have not updated to .906, then you'll need .890. The .906 update is fairly recent (a couple months old I think?) so if you don't explicitly remember taking it, use .890.
Side note, check the rom you used before this happened. Check if it's based on .906 or .890.
Sent from my DROID3 using xda premium
JDiPierro said:
Awesome! Thanks for the info. I'll give this a try when I get home from work tonight. Do you know if there's any way to tell what version I need without the settings app? Or perhaps if there's a way to forcibly open the Settings app?
Click to expand...
Click to collapse
Do you know if you enabled USB debugging? (from settings->applictaions->development - check "USB debugging" on.) Many root apps require that.
Anyway, if you did, you can install the Android SDK's adb app and, from a command prompt, you can try to type the following command (with the phone on and cabled to the computer)
adb shell cat /system/build.prop | grep "version"
This should show you a bunch of lines, one of which will be "ro.build.version.full". The system version follows that text on the line - I have last month's OTA, so mine is Blur_Version.5.7.906.XT862.Verizon.en.US (so I have 5.7.906).
You can most easily get adb (for Windows) with instructions from here: http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
After you get those files unzipped in c:\android, you can start a command prompt by hitting start, type "cmd" and enter in the search box - this will start a black command prompt window. From there, enter the command cd \android and then enter the adb command I put up above.
I'm not sure it will work, but it should.
You can bypass the activation. Starting with the top left corner, press each corner in a clockwise rotation. This will bring your phone to the home screen so you can then find which version it's on.
doogald said:
Do you know if you enabled USB debugging? (from settings->applictaions->development - check "USB debugging" on.) Many root apps require that.
...
adb shell cat /system/build.prop | grep "version"
Click to expand...
Click to collapse
What USB mode should the phone be in for this to work? I definitely had USB Debugging on before I did the factory reset; would that reset it though? When I try the command (minus grep, i'm in Windows unfortunately) I get 'error: device not found'
eww245 said:
You can bypass the activation. Starting with the top left corner, press each corner in a clockwise rotation. This will bring your phone to the home screen so you can then find which version it's on.
Click to expand...
Click to collapse
I had tried this but it still brought me straight to the "Add Accounts" screen, not to the home screen.
JDiPierro said:
What USB mode should the phone be in for this to work? I definitely had USB Debugging on before I did the factory reset; would that reset it though? When I try the command (minus grep, i'm in Windows unfortunately) I get 'error: device not found'
I had tried this but it still brought me straight to the "Add Accounts" screen, not to the home screen.
Click to expand...
Click to collapse
Needs to be I. Charge only mode. On stock rom I believe its called none
Sent from my XT860 using xda premium
JDiPierro said:
What USB mode should the phone be in for this to work? I definitely had USB Debugging on before I did the factory reset; would that reset it though? When I try the command (minus grep, i'm in Windows unfortunately) I get 'error: device not found'
Click to expand...
Click to collapse
You can grep: because you are running a shell command, I believe it is running on the phone, not on the windows computer.
(The grep is not all that critical, though, as I believe the version number line is one of the last lines displayed by that command.)
You can do an:
adb devices
before you run the shell command to verify that the computer and phone are communicating; it should return a line of characters that represents your phone, if it is connected.