Database Develop

[Q] Searching For Gps Problem. HELP!!

I have seen multiple threads on this subject for every other phone but none for the Nexus. Ever since i updated to CM 7.0.2 my gps hasnt worked properly. It locks in on my position and others in latitude very quickly, but if i try to use navigation it stays stuck on searching for gps. When i attempted to use the app gps status to check out the problem, it keeps loading and never finds any satellites. I posted in a g2 thread and the response i got back was this:
"You need to find out what partition on your phone the radio/gps cache is stored. Wipe it. That is the same type of idea of what we are doing here. Hopefully that helps get ya going in the right direction. I would also recommend trying to back it up first if you can. I'm also sure some dev with the know how could write a very easy script for you so that you can't mess it up. But it would obviously have to be someone familiar with the nexus setup. Good luck!"
can anybody help???

I just got the app "FasterFix" and it seems to do its work!

tried it...no luck any other ideas???

apparently gingerbread 2.3.3 has some issues with GPS. Actually it should have been fixed with 2.3.4. What version is CM 7.0.2?

RotasOpera said:
apparently gingerbread 2.3.3 has some issues with GPS. Actually it should have been fixed with 2.3.4. What version is CM 7.0.2?
Click to expand...
Click to collapse
Currently running a nightly which i believe is 2.3.4. Im going to try to wipe everything and go stock to see if that helps. Ill report back.

RotasOpera said:
apparently gingerbread 2.3.3 has some issues with GPS. Actually it should have been fixed with 2.3.4. What version is CM 7.0.2?
Click to expand...
Click to collapse
Any of the 7.0.x series will be based on Android 2.3.3. Supposedly, they will be coming out with 7.0.4 which will include the wonk fix (maybe even the 2-3sec delay fix).
Nightlies starting after an early 60's build have been based on 2.3.4. These will eventually turn into CM 7.1.

I found a Tutorial a few weeks ago, unfortunately I don't know where, but try this:
Download the GPS files which have been extracted from a froyo ROM:
http://www.share. cx/files/971910022477/GPSfiles.rar.html (remove the space)
Now extract the files to the folder where your ADB is located.
Now open your ADB command prompt and enter the following commands:
1. adb remount
2. adb push libgps.so /system/lib
3. adb push gps.bravoc.so /system/lib/hw
4. adb shell
5. cd /system/lib
6. su
7. chmod 777 libgps.so
8. exit
9. cd /system/lib/hw
10. su
11. chmod 777 gps.bravoc.so
12. exit
13. reboot
Hope I helped!

[Q] After rebooting always getting Factory Test

Hello guys,
Here is my problem: When I reboot the phone I always get this black banner with yellow words. I found that it is related to a process running called factory test. When I stop it through Application manager, the banner vanishes. Looking at the forum, I found that by changing /efs/FactoryApp/factorymode to ON, I can solve this issue. Well, it does (temporally). After rebooting the phone, the file is back on off and I still get the banner.
I can live with this problem, and change it manually every time after reboot. However, my phone is almost unusable. In my baseband is showing XXX. Again, looking for a solution in the forum I found that the problem could be on the missing NV.DAT file in /modemfs/PERM/PROT/. I did push the file there, however, after rebooting the file is gone.
On the top of it all, I'm getting the "not enough space" message. I do not have an external sd card. It seems that it's a mounting problem related. I don't know if those problems are related to each other or independent.
I tried to flash a stock rom. However I still getting those problems. I had (and was using) the Maclaw CM10.1 when the phone entered in boot loop. I am running a rooted rom (Jelly Bean).
In resume, it is really messed up. So, the question is: Have any one faced those problems all together? Or have any idea what may be the cause and possible solution for those problems?
Thanks for any help.

kent13 said:
Hello guys,
Here is my problem: When I reboot the phone I always get this black banner with yellow words. I found that it is related to a process running called factory test. When I stop it through Application manager, the banner vanishes. Looking at the forum, I found that by changing /efs/FactoryApp/factorymode to ON, I can solve this issue. Well, it does (temporally). After rebooting the phone, the file is back on off and I still get the banner.
I can live with this problem, and change it manually every time after reboot. However, my phone is almost unusable. In my baseband is showing XXX. Again, looking for a solution in the forum I found that the problem could be on the missing NV.DAT file in /modemfs/PERM/PROT/. I did push the file there, however, after rebooting the file is gone.
On the top of it all, I'm getting the "not enough space" message. I do not have an external sd card. It seems that it's a mounting problem related. I don't know if those problems are related to each other or independent.
I tried to flash a stock rom. However I still getting those problems. I had (and was using) the Maclaw CM10.1 when the phone entered in boot loop. I am running a rooted rom (Jelly Bean).
In resume, it is really messed up. So, the question is: Have any one faced those problems all together? Or have any idea what may be the cause and possible solution for those problems?
Thanks for any help.
Click to expand...
Click to collapse
type in terminal emulator:
Code:
su
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/factorymode
reboot

samersh72 said:
type in terminal emulator:
Code:
su
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/factorymode
reboot
Click to expand...
Click to collapse
Hi samersh72,
I have tried it before and didn't help. When I reboot the phone, the problem persists and the file still with 'OFF'. I don't know if it makes any differences, but I'm running those commands through adb, since I could not install any app. (I tried to push the apk file of terminal emulator to /syste/app/ but it crashes when I try to open it. I also tried to do it using Root Explorer.. Both cases, no success.)

Towelroot exploit for i9305 – source code

Hi,
I9305 is not officially supported by towelroot. So I searched for some details about the exploit and found this pastebin.com/A0PzPKnM (which seems to be decompiled and cleaned - made more readable towelroot v1) and some articles about how its supposed to work (blog.nativeflow.com/the-futex-vulnerability and tinyhack.com/2014/07/07/exploiting-the-futex-bug-and-uncovering-towelroot/). I have to admit that I don’t understand it fully, but well enough to modify it to this pastebin.com/1fdmC4Xv , which is working exploit on my i9305 with Android 4.3, kernel 3.0.31. I didn’t make any big changes – I made few modifications to compile the code, added lots of debugging output, changed what happens when the hack is successful and added the iov_index variable, which is the most important change. The original code is not nice and my changes are not nice neither, please be lenient while reading it. If you want to use it, compile it with android ndk, push to /data/local/tmp and run. There can be one argument, number from 0 (default) to 7 (you can use bigger, but it makes no sense). If it succeeds, you’ll get root prompt. Otherwise it can freeze or reboot the phone. You can check the kernel panic reason in /proc/last_kmsg. If you see that it crashed in plist_add because “Unable to handle kernel NULL pointer dereference at virtual address 0000000c”, subtract 0xc from the address and use as the argument (iov_index) next time. Don’t give up, it doesn’t work always. Note that, the phone will reboot after you quit the root shell. Its up to you what you do with this, but AFAIK successful execution of this exploit doesn`t change the KNOX warranty bit, at least my phone still says that the system is “official”.
Remember to be careful, when doing anything of this and don’t blame for any damage.
If you want to play with it in debugger, you don’t have to use the android emulator as suggest in the article mentioned above – I used vanilla kernel 3.0.31 compiled with exynos4_defconfig, buildroot userspace and latest qemu with the machine smdkc210.
Pavel
P.S. I don`t have enough posts here, so you have to use the links manually

prqek said:
Hi,
I9305 is not officially supported by towelroot. So I searched for some details about the exploit and found this pastebin.com/A0PzPKnM (which seems to be decompiled and cleaned - made more readable towelroot v1) and some articles about how its supposed to work (blog.nativeflow.com/the-futex-vulnerability and tinyhack.com/2014/07/07/exploiting-the-futex-bug-and-uncovering-towelroot/). I have to admit that I don’t understand it fully, but well enough to modify it to this pastebin.com/1fdmC4Xv , which is working exploit on my i9305 with Android 4.3, kernel 3.0.31. I didn’t make any big changes – I made few modifications to compile the code, added lots of debugging output, changed what happens when the hack is successful and added the iov_index variable, which is the most important change. The original code is not nice and my changes are not nice neither, please be lenient while reading it. If you want to use it, compile it with android ndk, push to /data/local/tmp and run. There can be one argument, number from 0 (default) to 7 (you can use bigger, but it makes no sense). If it succeeds, you’ll get root prompt. Otherwise it can freeze or reboot the phone. You can check the kernel panic reason in /proc/last_kmsg. If you see that it crashed in plist_add because “Unable to handle kernel NULL pointer dereference at virtual address 0000000c”, subtract 0xc from the address and use as the argument (iov_index) next time. Don’t give up, it doesn’t work always. Note that, the phone will reboot after you quit the root shell. Its up to you what you do with this, but AFAIK successful execution of this exploit doesn`t change the KNOX warranty bit, at least my phone still says that the system is “official”.
Remember to be careful, when doing anything of this and don’t blame for any damage.
If you want to play with it in debugger, you don’t have to use the android emulator as suggest in the article mentioned above – I used vanilla kernel 3.0.31 compiled with exynos4_defconfig, buildroot userspace and latest qemu with the machine smdkc210.
Pavel
P.S. I don`t have enough posts here, so you have to use the links manually
Click to expand...
Click to collapse
Hi! I use I9305 with android 4.4.4 - without any branding. Could U help me with root this device without knox flag? Thank u, I'm from polish and my english is soo bad ;/ I want ready aplication to install if u could do this for me

wow thanks you

Hi schizyk12,
I am afraid, that I will disappoint you. I don`t have any other phone than my i9305 with 4.3, so it would be a blind shot to create such an application. Even if I had some more devices, I am not sure if I have time to do this. Another problem is that I am not even sure whether this would work on 4.4.4. What kernel does it use? See this www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3153 , if your kernel version is higher than 3.14.5 then the bug this is exploiting is fixed. If you kernel is build after May 26th, 2014, it is also probably fixed.
I am attaching the binary that worked for me. You can try it - unzip it and pull it into /data/local/tmp using adb (if you don`t know how to do it, search the web, it`s not difficult) and execute from adb shell as /data/local/tmp/tr_c 1 (or some other integer, see my original post). Keep trying, it may not work for the first time. If it succeeds, you will see something like this:
Code:
cpid3 resumed.
hack.
/system/bin/sh
[email protected]:/data/local/tmp #
If your phone reboots, it is a good sign – the bug is probably not fixed.

I also have i9305 with Android 4.3 (kernel 3.0.31) and everything seems to work fine - when I execute tr_c 1 it displays a lot of lines but there are few, which look exact same like in your post above. Now the problem - this method doesn't give me root access... I don't know what is wrong. Can you help me with this? Maybe you know how to get it working? Thanks for all of your work PS: Sorry for my english.

What do you mean by root access? This is not one the “one click root” applications, this is only the exploit. If you see at the end what I posted in my previous post, you have root access, but only in that one session. If you want to have rooted device, you have to do the rest manually. Unfortunately I didn`t find any article describing what this means. There are only lots of “one click” apps. Finally I used Koushiks Superuser – it is simple and opensource, so it was quite easy to find how the installation (“rooting”) works. Take a look at this script github.com/koush/Superuser/blob/master/Superuser/assets/update-binary . Don`t execute it, it is supposed to be run from recovery. Here are briefly the steps to be done (I hope I didn`t forget anything, don`t do it if you don`t understand it):
1) mount -oremount,rw /system
2) copy su to /system/xbin
3) chown it 0:0 and chmod it to 6755
4) create link from /system/bin/su to /system/xbin/su
5) modify (or create) /system/etc/install-recovery.sh (see github.com/koush/Superuser/blob/master/Superuser/assets/install-recovery.sh)
6) sync and reboot
I actually used the disabled ssh service from /init.rc and I am enabling it install-recovery.sh, so if the su daemon is killed, it is restarted automatically. The daemon is needed because of bypassing SELinux, the suid bit is not enough (I suppose I can chmod to 755 in step 3).
You don`t have to compile the whole supperuser, you can download it from here www.koushikdutta.com/post/superuser .
But there is one problem with this version – if the selinux is enforcing, the su works only from adb shell. It is because the socket used for communication between su and daemon is in /dev, which is not accessible by applications. So I moved it to /data/local/tmp/. Now it works for apps and not for adb shell. But you have to compile the su binary to do this. I should report a bug to Koushik.... Also adding setenforce 0 to install-recovery.sh should help, but it turns off SELinux.
Pavel

Yeah, I thought it will be something like "one-click root". Now I understand - I had root access from adb but not normally rooted phone I read your instructions and I have more questions. Did you do this on your phone? Is the warranty void still 0 after these operations? I don't want to change it to 1
PS: I'm not sure if I can make this work, so I must live without root on this device since it'll be easier to do

I*did all of this on my phone I don`t see any triangle like here www.mobot.net/samsung-galaxy-s2-removing-yellow-triangle-37410 . The know warranty void in download mode says 0, so I guess it is OK. But the device status in settings says custom, but this happened after I removed knox related applications. I didn`t try to put them back. It may fix it. If I remember well, the step I described didn`t change any of these bit and statuses.
It`s not so difficult, you just need some understanding how Linux system works.

Wifi Keeps turning on but never turn on (MAC address shows 20:00:00:00:00:00)

I have problem with WIFI keeps turning on but it never turn on like usual, i tried flash stock rom neswest build and do factory reset it with no luck.
Searching around internet and found that there are some Nexus5 user can fix it by delete folder of mac address (they said it is in /persist/wifi folder) buti cant find that folder in my Marshmallow. Anyone knows how to fix this i think it is something wrong with corrupted MAC address it quite weird that my MAC Address is 20:00:00:00:00:00

Got EXACTLY the same issue...I tried to flash all available roms, right from 5.0.0 to the latest 6.0 and no luck...Wifi and Bluetooth are non existent now! Is your bluetooth ok?? And its not 20.00.....its 02.00.00.....pls check again...

pradipsoman said:
Got EXACTLY the same issue...I tried to flash all available roms, right from 5.0.0 to the latest 6.0 and no luck...Wifi and Bluetooth are non existent now! Is your bluetooth ok?? And its not 20.00.....its 02.00.00.....pls check again...
Click to expand...
Click to collapse
Messed up EFS partition? If you don't have a backup i *think* the device is hard bricked > repair

---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
Droidphilev said:
Messed up EFS partition? If you don't have a backup i *think* the device is hard bricked > repair
Click to expand...
Click to collapse
How can a messed up EFS prevent the WIFI and Bluetooth from working? All other features work well. And if the partition is messed up and device is hard bricked, how does it work and all the other features work...Could you explain please...and if you have the knowledge could you give any tips to get it right?

pradipsoman said:
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
How can a messed up EFS prevent the WIFI and Bluetooth from working? All other features work well. And if the partition is messed up and device is hard bricked, how does it work and all the other features work...Could you explain please...and if you have the knowledge could you give any tips to get it right?
Click to expand...
Click to collapse
AFAIK the factory puts files in that partition that includes the wifi MAC, BT MAC, IMEI etc etc. From there the rom reads the mac addresses. If it cannot find these then wifi won't turn on. I may be wrong that this is the case though. I had a problem with a tablet before. Flashing something caused that the permissions of that file became wrong, i had no wifi either. Luckily for me the file was still there and changing permissions fixed it. Is you IMEI still shown correctly in "about"?

Droidphilev said:
AFAIK the factory puts files in that partition that includes the wifi MAC, BT MAC, IMEI etc etc. From there the rom reads the mac addresses. If it cannot find these then wifi won't turn on. I may be wrong that this is the case though. I had a problem with a tablet before. Flashing something caused that the permissions of that file became wrong, i had no wifi either. Luckily for me the file was still there and changing permissions fixed it. Is you IMEI still shown correctly in "about"?
Click to expand...
Click to collapse
Yes, my IMEI is shown correctly but wifi mac id shown as a bogus number i.e 02.00:00:00:00:00

pradipsoman said:
Yes, my IMEI is shown correctly but wifi mac id shown as a bogus number i.e 02.00:00:00:00:00
Click to expand...
Click to collapse
That's something i guess. Otherwise you wouldn't be able to make calls any further. Hopefully you will find a way to fix. Please report here.

Droidphilev said:
That's something i guess. Otherwise you wouldn't be able to make calls any further. Hopefully you will find a way to fix. Please report here.
Click to expand...
Click to collapse
Could it be related to the /persist folder

pradipsoman said:
Could it be related to the /persist folder
Click to expand...
Click to collapse
check PM.
Can you tell us exactly what you were doing when this happened? you flashed a rom or something like that? Would be good to know.

Droidphilev said:
check PM.
Can you tell us exactly what you were doing when this happened? you flashed a rom or something like that? Would be good to know.
Click to expand...
Click to collapse
I was on 5.1.1 and then everything was working fine...I installed the 6.0 OTA and then this happened....

Went ahead and did the hard brick repair method to see if that would help, but even after that the problem persists!

pradipsoman said:
Went ahead and did the hard brick repair method to see if that would help, but even after that the problem persists!
Click to expand...
Click to collapse
the unbrick thing or the persist thing?

you guys do realize that google is using the wifi to figure out your location, right? even if you never ever turn wifi on. you have to disable scanning in the location settings for google not to use the wifi.

none
If you had a hard bricked device you would know it because your phone would have a black screen and you would have a paperweight

I did everything...including the persist wipe etc....No use...seems the wifi/bluetooth chip is dead after the 6.00 OTA update

pradipsoman said:
I did everything...including the persist wipe etc....No use...seems the wifi/bluetooth chip is dead after the 6.00 OTA update
Click to expand...
Click to collapse
Have you tried setting a custom MAC yet?
Had this for my old N5:
Code:
cd /persist
rm -rf bluetooth
mkdir bluetooth
chown bluetooth:system ./bluetooth
chmod 770 ./bluetooth
echo -ne '\xBC\xF5\xAC\x70\xA9\x5F' > ./bluetooth/.macaddr
chown bluetooth:system ./bluetooth/.macaddr
chmod 660 ./bluetooth/.macaddr
rm -rf wifi
mkdir wifi
chown wifi:system ./wifi
chmod 770 ./wifi
echo -ne '\x8c\x3a\xe3\x41\x8d\x79' > ./wifi/.macaddr
chown wifi:system ./wifi/.macaddr
chmod 660 ./wifi/.macaddr
Reboot afterwards. Of course you'll need root.
Some things to keep in mind:
1. Not all MAC addresses worked for me. setting 1234567890 would cause wifi to get stuck at turning on. Some MACs work, some don't. Didn't bother to find out why.
2. The addresses above are for my old N5, you're free to try them if you want. That motherboard is toast.
3. My N5 died due to a wifi/bt chip burn out. Manufacturing defect. Hence my investigation into the issue and whatnot.

I have the exact same problem but with a completely stock, never-rooted Nexus 6. Marshmallow 6.0 OTA arrived a week after the 1 year Motorola warranty expired, and problems with screencasting started immediately. But yesterday, the wifi quit, and the phone rebooted itself moments later. The wifi has never come back on since. I also noticed the bogus 02:00:00:00:00:00 mac address, suggesting that something got corrupted. For reference, this phone was purchased directly from Motorola, and is using a VZW sim.
Of course there's nothing Motorola will do, since it's 2 weeks out of warranty. But I'm hopeful that the hardware is still alright since I can still turn bluetooth on and off. Can someone confirm that this phone's BT and Wifi are on the same chip? I suppose there is no reason not to root it now...
I'd like to try to set the mac address using the above code. Can anyone suggest a way to retrieve the old mac? Thanks...

Not working..
toastgodsupreme said:
Have you tried setting a custom MAC yet?
Had this for my old N5:
Code:
cd /persist
rm -rf bluetooth
mkdir bluetooth
chown bluetooth:system ./bluetooth
chmod 770 ./bluetooth
echo -ne '\xBC\xF5\xAC\x70\xA9\x5F' > ./bluetooth/.macaddr
chown bluetooth:system ./bluetooth/.macaddr
chmod 660 ./bluetooth/.macaddr
rm -rf wifi
mkdir wifi
chown wifi:system ./wifi
chmod 770 ./wifi
echo -ne '\x8c\x3a\xe3\x41\x8d\x79' > ./wifi/.macaddr
chown wifi:system ./wifi/.macaddr
chmod 660 ./wifi/.macaddr
Reboot afterwards. Of course you'll need root.
Some things to keep in mind:
1. Not all MAC addresses worked for me. setting 1234567890 would cause wifi to get stuck at turning on. Some MACs work, some don't. Didn't bother to find out why.
2. The addresses above are for my old N5, you're free to try them if you want. That motherboard is toast.
3. My N5 died due to a wifi/bt chip burn out. Manufacturing defect. Hence my investigation into the issue and whatnot.
Click to expand...
Click to collapse
Tried changing the mac id as per this method...Does not work..After reboot still shows the bogus id 02:00:00:00:00:00

Thanks for all supported here, seems so many people got tge same problem as mine.
I never unlock bootloader on this device, im at 5.1.1 and it happens with my wifi shows wrong mac address so i just tried to ota to 6.0 and the issue is still there? Anybody find the cause pf problem here?

pradipsoman said:
Tried changing the mac id as per this method...Does not work..After reboot still shows the bogus id 02:00:00:00:00:00
Click to expand...
Click to collapse
Did you happen to try setting it to its original mac, or to some other valid broadcom mac? Or did it fail after setting a random mac. I ask because I am about to root my wife's phone just to attempt this same procedure...

[ROM] CM12.1 BETA 5 For Lenovo-A7000 by PrashantRana BT problem

Hello
I have problem with BT .My Watch (moto 360) get disconected and its hard to reconect it again ... in the process its need to confirm new paircode.
I thing that this will solwe my problem (its from topic for Sony Xperia Z1).
The soluton is :
Code:
Workaround: create a file named "bluetooth_bdaddr" in /data/etc, write a BT address in there (I used one of the random addresses when I started to turn BT on and off), then change the owner and permissions of the file (Terminal Emulator or any other app):
- chown bluetooth bluetooth_bdaddr
- chmod 0640 bluetooth_bdaddr.
Bluetooth is now working fine for me because it uses always the same address
But i canot create file in that adress ... there is no /data/etc/ folder ...and if i use in terminal : "touch \data\etc\bluetooth_bdaddr" it will not create the file ! (i have start the "su" command before)
Cant somebody to help me how to use this workaround it the CM12.1 Beta 5 for lenovo A7000?
Thanks and sorry for my bad english

Nobody know how to youse this fix in this rom.
Another important stuff.
I have found mallware inside this ROM. His name is "teleyphone" , "com.android.services.teleyphone" .