For those having problems with bluetooth not working on the new 4.2 OTA from Asus....they screwed up permissions on /system/vendor/lib/libbt-vendor.so. It's permissions are wrong and need to be changed to rw-r-r. This can only be done on rooted tablets....locked or unlocked:
Open a terminal
su to root
Make /system rw with: mount -o rw,remount /system
chmod 644 /system/vendor/lib/libbt-vendor.so
reboot
Now if only I can get my root issue fixed.
Sent from my PG86100 using xda app-developers app
Actually you can wait till ASUS releases the whole firmware file on their webpage. Then you should be able to reflash your firmware without wiping data using that image by moving the image on the SD card. So there is no need for root.
bluetooth fix
bads3ctor said:
For those having problems with bluetooth not working on the new 4.2 OTA from Asus....they screwed up permissions on /system/vendor/lib/libbt-vendor.so. It's permissions are wrong and need to be changed to rw-r-r. This can only be done on rooted tablets....locked or unlocked:
Open a terminal
su to root
Make /system rw with: mount -o rw,remount /system
chmod 644 /system/vendor/lib/libbt-vendor.so
reboot
Click to expand...
Click to collapse
That did it for me and saved me a trip to the Asus repair shop. Thank you.
I just did it using RootExpoler. system/vendor/lib/ longpress libbt-vendor.so and select permissions, Owner should be RW, Group tick Read, Others tick Read. hit Ok and reboot tablet. Done
Thank you. Bluetooth is back again
tbdawg said:
Now if only I can get my root issue fixed.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Hi,
I had to factory reset my device (4.1) before updating to 4.2, I thought I have lost root. But managed to restore root quite easily.
If you have preserved root via VooDoo OTA RootKeeper before updating to 4.2 you can give these instructions a try. They work if su-backup copy is not disturbed by OTA, which is mostly the case (like yours).
bads3ctor said:
For those having problems with bluetooth not working on the new 4.2 OTA from Asus....they screwed up permissions on /system/vendor/lib/libbt-vendor.so. It's permissions are wrong and need to be changed to rw-r-r. This can only be done on rooted tablets....locked or unlocked:
Open a terminal
su to root
Make /system rw with: mount -o rw,remount /system
chmod 644 /system/vendor/lib/libbt-vendor.so
reboot
Click to expand...
Click to collapse
i tryed, but with me not work..
I did the following:
open the terminal
write /system rw with: mount -o rw,remount /system ==> start
write chmod 644 /system/vendor/lib/libbt-vendor.so ==> start
Write reboot ==> start
at reboot, bluetooth whe i actived, the tablet stuck for few second ( 30sec/1min) and continue to not work...
PLease help me...
Thank's
Try this
stevtec86 said:
i tryed, but with me not work..
I did the following:
open the terminal
write /system rw with: mount -o rw,remount /system ==> start
write chmod 644 /system/vendor/lib/libbt-vendor.so ==> start
Write reboot ==> start
at reboot, bluetooth whe i actived, the tablet stuck for few second ( 30sec/1min) and continue to not work...
PLease help me...
Thank's
Click to expand...
Click to collapse
Install: https://play.google.com/store/apps/details?id=com.estrongs.android.pop&feature=related_apps
Make sure ES File Explorer has root permissions. In settings->root settings, check Root Explorer, Up to Root, and Mount File System. Change directories to /system/vendor/lib. Long tap libbt-vendor.so and click properties. Change permissions: check read for User, Group, and Other. Check write for User. Tap OK. Reboot.
bads3ctor said:
Install: https://play.google.com/store/apps/details?id=com.estrongs.android.pop&feature=related_apps
Make sure ES File Explorer has root permissions. In settings->root settings, check Root Explorer, Up to Root, and Mount File System. Change directories to /system/vendor/lib. Long tap libbt-vendor.so and click properties. Change permissions: check read for User, Group, and Other. Check write for User. Tap OK. Reboot.
Click to expand...
Click to collapse
Done, but the permission was to rw-r-r, but bluetooth not work
stevtec86 said:
Done, but the permission was to rw-r-r, but bluetooth not work
Click to expand...
Click to collapse
The only way I know to diagnose such a problem is logcat. If you post the error, maybe someone has seen the error and can help.
bads3ctor said:
For those having problems with bluetooth not working on the new 4.2 OTA from Asus....they screwed up permissions on /system/vendor/lib/libbt-vendor.so. It's permissions are wrong and need to be changed to rw-r-r. This can only be done on rooted tablets....locked or unlocked:
Open a terminal
su to root
Make /system rw with: mount -o rw,remount /system
chmod 644 /system/vendor/lib/libbt-vendor.so
reboot
Click to expand...
Click to collapse
Hi bads3oct,
for the bluetooth problem, are you talking about bluetooth address missing in system info and it couldn't be enabled in setting(I slid the bluetooth switch from OFF to ON, but it rebounds back to OFF immediately)? my bluetooth worked fine with 4.1.1 several weeks ago and i haven't used it until yesterday. During the time, i just upgraded it to offical 4.2.1.
I've rebooted thousands times and switch the laucher from new 4.2 UI back 4.1 , all didn't help.
my tf300 is still running with locked bootloader and unrooted.
I want to know if the problem you guys are talking is same phenomenon as mine
abczhou said:
Hi bads3oct,
for the bluetooth problem, are you talking about bluetooth address missing in system info and it couldn't be enabled in setting(I slid the bluetooth switch from OFF to ON, but it rebounds back to OFF immediately)? my bluetooth worked fine with 4.1.1 several weeks ago and i haven't used it until yesterday. During the time, i just upgraded it to offical 4.2.1.
I've rebooted thousands times and switch the laucher from new 4.2 UI back 4.1 , all didn't help.
my tf300 is still running with locked bootloader and unrooted.
I want to know if the problem you guys are talking is same phenomenon as mine
Click to expand...
Click to collapse
Yes...the bluetooth toggle rebounds back to OFF immediately when the permissions are wrong after an update from 4.1.1 to 4.2.1. If you are not rooted then I think the only way to fix it is to unlock and root. Maybe you could manually reinstall the update while locked and unrooted using the Asus zip file but I don't know if this is possible.
thanks for your quick reply, Asus should notice their mistake and fix it soon.
Sent from my LG-P990 using xda app-developers app
Interesting side-note to this thread. I implemented the fix as prescribed and it worked perfectly. So much so that I am typing this reply on a generic BT Keyboard.
But before I could do this, I had to restart the tablet to re-enable bluetooth. This was after using BT all day with this keyboard. The only thing I did was connect the tablet to the charger, and after it finished charging the BT stack behaved like it did before I implemented the fix. I checked the permissions on the file, and the Owner permissions were still preserved, so I'm at a loss to explain it.
Not sure if there is something else going on here, or if it is pure coincidence. The issue was easily fixed with a restart.
Works for my TF700 - change permission by root browser
my mistake after change permision I do not make reboot and think solution is not working for me - but easy easy
after restart pad - bluetooth works again
great job, many thanks bads3ctor
Fixed my bluetooth problems on my rooted TF300TG by changing the permissions with X-Plore file explorer. Thanks
Sent from my ASUS Transformer Pad TF300TG using xda app-developers app
I don't know if this is due to the BT stack on our devices, but when you disconnect a paired BT device, some apps really hate it.
I did this while playing Pinball Arcade, and the app crashed.
There is a noticeable system pause when within an app when you turn off the paired device (my Logitech Tablet Keyboard has an Off switch, rather than a soft-off feature).
Has anyone else noticed this behavior?
There's another horrific problem with bluetooth A2DP quality. It seems to be hindered by this bug: http://code.google.com/p/android/issues/detail?id=39632
I haven't tried this yet, but if someone can replicate what was done here, it should fix this: http://forum.xda-developers.com/showthread.php?t=2184333
will I still be able to recieve OTA's if I fix the permission problem?
edit: I went ahead anyway, for reference original permissions 600
Related
So I'm rooted and downloaded Super User app from market. I have a bunch of root apps but the only app listed in the super user app is Titanium. Any reason why the other rooted apps (Set Cpu, Minfree Manager, etc.) aren't listed?
Have they asked for superuser?
Via EVO on 4G with XDA App
awenthol said:
Have they asked for superuser?
Via EVO on 4G with XDA App
Click to expand...
Click to collapse
No it doesn't
Sent from my CM6 powered device
krazyflipj said:
No it doesn't
Sent from my CM6 powered device
Click to expand...
Click to collapse
We managed to fix this problem the other night on the irc channel. I didn't post anything because it doesn't seem like many people are using superuser.apk. The problem is that superuser needs to install it's own version of the su program to run properly. The current root method replaces su every reboot. When you lose the su that superuser.apk installs it can't control root access anymore and basically any program can request root without a prompt to you. The fix is to just replace the jk-su file in /system/bin/ with the superuser su. Then every reboot it will just use the one that works with the superuser app. I did this a few days ago and haven't had any problems.
The procedure is as follows (you need to use adb):
Go into the superuser app, go to the "settings" tab and at the very bottom choose to update su (it should change from saying original to something like "su v2.3.1-ef").
Plug the phone into usb and make sure you have USB debugging enabled.
Open a command prompt on the computer and goto your android sdk tools folder to run these commands (IMPORTANT NOTE - Make sure you have the phone screen on and unlocked when you run the su command below because superuser will ask you for permission and you need to click yes. It wont prompt if the screen is off or locked and the adb shell will just sit there waiting for a response. As soon as you click yes on the phone you should get a # in the adb shell):
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
cp /system/bin/su /system/bin/jk-su
exit
Now you should just reboot the phone and check that it worked by running any program that needs root access that isn't already listed with superuser. I suggest shootme or wifi tether. tether asks when you start or stop tethering and when you allow a mac address in the access control.
richse said:
We managed to fix this problem the other night on the irc channel. I didn't post anything because it doesn't seem like many people are using superuser.apk. The problem is that superuser needs to install it's own version of the su program to run properly. The current root method replaces su every reboot. When you lose the su that superuser.apk installs it can't control root access anymore and basically any program can request root without a prompt to you. The fix is to just replace the jk-su file in /system/bin/ with the superuser su. Then every reboot it will just use the one that works with the superuser app. I did this a few days ago and haven't had any problems.
The procedure is as follows (you need to use adb):
Go into the superuser app, go to the "settings" tab and at the very bottom choose to update su (it should change from saying original to something like "su v2.3.1-ef").
Plug the phone into usb and make sure you have USB debugging enabled.
Open a command prompt on the computer and goto your android sdk tools folder to run these commands (IMPORTANT NOTE - Make sure you have the phone screen on and unlocked when you run the su command below because superuser will ask you for permission and you need to click yes. It wont prompt if the screen is off or locked and the adb shell will just sit there waiting for a response. As soon as you click yes on the phone you should get a # in the adb shell):
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
cp /system/bin/su /system/bin/jk-su
exit
Now you should just reboot the phone and check that it worked by running any program that needs root access that isn't already listed with superuser. I suggest shootme or wifi tether. tether asks when you start or stop tethering and when you allow a mac address in the access control.
Click to expand...
Click to collapse
Hmmm cp /system/bin/su /system/bin/jk-su didn't work. I ls /system/bin and don't see jk-su listed just su...
krazyflipj said:
Hmmm cp /system/bin/su /system/bin/jk-su didn't work. I ls /system/bin and don't see jk-su listed just su...
Click to expand...
Click to collapse
What root did you use? I did mine manually so there may be some differences if you used a one click.
Edit: I just looked at noobnl's one click root and it uses the same script that contains the line:
#copies busybox su
cat /system/bin/jk-su > /sdx/su
so it should definitely be there even if you used his one click.
When you run the command "ls -l /system/bin/jk-su" what do you get?
I get this:
ls -l /system/bin/jk-su
-rwsr-sr-x root root 26264 2010-09-18 06:10 jk-su
Please delete
krazyflipj said:
Please delete
Click to expand...
Click to collapse
Did you get it working? After you updated su through the superuser app then it started working so that is why it asked you for permission when you were in terminal. The problem is that if you reboot without applying the rest of the fix to replace jk-su then you will lose the updated su and it will stop working.
richse said:
Did you get it working? After you updated su through the superuser app then it started working so that is why it asked you for permission when you were in terminal. The problem is that if you reboot without applying the rest of the fix to replace jk-su then you will lose the updated su and it will stop working.
Click to expand...
Click to collapse
Hey Richse, I'm trying to get this to work but it isn't.
rose1 said:
Hey Richse, I'm trying to get this to work but it isn't.
Click to expand...
Click to collapse
can you give me more information, what errors are you getting or what exactly is happening?
richse said:
can you give me more information, what errors are you getting or what exactly is happening?
Click to expand...
Click to collapse
Okay, I did the one click root method that is stickied. Then I did
adb shell
su
after doing su, I initially saw on the phone that unknown user was asking for superuser access. Of course, "unknown user" is me so I granted it. Then I saw the # then I went ahead and did
mount -t rfs -o remount,rw /dev/block/stl9 /system
That worked fine . The line repeated itself which indicates that it worked. When I do
cp /system/bin/su /system/bin/jk-su
it then says cp: not found.
Just to give you a little more info, I just restored my phone with odin to factory defaults, then I updated to the DI07 update. Then I installed the final clockwork mod recovery, then I did the one click root method. Then I installed superuser in the system/app folder.
rose1 said:
Okay, I did the one click root method that is stickied. Then I did
adb shell
su
after doing su, I initially saw on the phone that unknown user was asking for superuser access. Of course, "unknown user" is me so I granted it. Then I saw the # then I went ahead and did
mount -t rfs -o remount,rw /dev/block/stl9 /system
That worked fine . The line repeated itself which indicates that it worked. When I do
cp /system/bin/su /system/bin/jk-su
it then says cp: not found.
Just to give you a little more info, I just restored my phone with odin to factory defaults, then I updated to the DI07 update. Then I installed the final clockwork mod recovery, then I did the one click root method. Then I installed superuser in the system/app folder.
Click to expand...
Click to collapse
I'm not sure why cp doesn't work, it just means copy. An alternative to try is to delete jk-su and replace it with the su you updated. Use these commands in place of the cp command:
rm /system/bin/jk-su
cat /system/bin/su > /system/bin/jk-su
Make sure you do this after updating su in the superuser app and without rebooting in between. Let me know if you have any problems.
followed instructions. no errors but i still have no programs asking for permission. i had wifi tether downloaded before and it worked. I downloaded shootme to see if it would ask for permission and it didnt - but it works. neithe one is lited in superuser either.
listed is:
adfree / quickboot / root manager / startup manager ( 3 of them) / super manager / unknown ( spawned right after i followed instrution)
any ideas
uninstall supersuser and reinstalled:
listed apps now:
adfree / busybox installer / root explorer / rootmanager / sufbs / tit backup
again not sure is it is correct. but seems to work "I THINK"
spdwiz18 said:
followed instructions. no errors but i still have no programs asking for permission. i had wifi tether downloaded before and it worked. I downloaded shootme to see if it would ask for permission and it didnt - but it works. neithe one is lited in superuser either.
listed is:
adfree / quickboot / root manager / startup manager ( 3 of them) / super manager / unknown ( spawned right after i followed instrution)
any ideas
uninstall supersuser and reinstalled:
listed apps now:
adfree / busybox installer / root explorer / rootmanager / sufbs / tit backup
again not sure is it is correct. but seems to work "I THINK"
Click to expand...
Click to collapse
When you go to update su in the superuser app does it say "original" and then change or does it stay updated after you reboot?
richse said:
When you go to update su in the superuser app does it say "original" and then change or does it stay updated after you reboot?
Click to expand...
Click to collapse
what i have:
cwm 2.5.1
root 2.1.1
di07
now for the long and skinny:
i checked. went to superuser and it told me 2.3.1 -ef i then HARD rebooted, came back with no root.and superuser told be original, hard reboot again, still no root. So one more time- third time is a charm - i have root and superuser told me 2.3.1 -ef
thanks again for the help.
i think my phone might not be total stable.. lol
any ideas.
also - i thought about upping root to most recent but unsure if i need to unroot or if i can install over it. your thoughts on this matter!!!!
spdwiz18 said:
what i have:
cwm 2.5.1
root 2.1.1
di07
now for the long and skinny:
i checked. went to superuser and it told me 2.3.1 -ef i then HARD rebooted, came back with no root.and superuser told be original, hard reboot again, still no root. So one more time- third time is a charm - i have root and superuser told me 2.3.1 -ef
thanks again for the help.
i think my phone might not be total stable.. lol
any ideas.
also - i thought about upping root to most recent but unsure if i need to unroot or if i can install over it. your thoughts on this matter!!!!
Click to expand...
Click to collapse
I doubt you need to update root. The root I used was the original manual method by joeykrim. The one click just automates that method. There is no reason why you should have to reboot multiple times to get this working. You basically just replaced a file with a similar file and the script that was installed when you rooted uses that file to create a new su every time you reboot. Personally, I would wipe to stock with Odin and then use the manual root method to make sure nothing funny is going on with your phone. When you rebooted and the su was "original" you didn't lose root, it just meant that superuser wouldn't work. For now, as long as the 2.3.1 -ef sticks around superuser will work just fine. As an alternative you could try noobnl's newest stuff. Looks like he made it compatible with superuser, so I think that would negate the need to use this type of fix. I'm not sure what he did to add the compatibility but you could probably ask him.
if you flash noobnl's latest kernel, it includes superuser and it works perfectly.
rose1 said:
if you flash noobnl's latest kernel, it includes superuser and it works perfectly.
Click to expand...
Click to collapse
The only issue I see with that is you have to use a DG27 kernel. If you want to use a DI07 kernel you still need to use this fix.
richse said:
The only issue I see with that is you have to use a DG27 kernel. If you want to use a DI07 kernel you still need to use this fix.
Click to expand...
Click to collapse
Very true. I didn't think about that.
I have latest Noobls kernel flashed on top of DI07 and this fix did not work.First thing that dint work is i never got SuperUser prompt after i typed su in adb shell,i got su in windows but no prompt on the phone.
To make it short i did the whole procedure from BetterTerminal(now i got su prompt) rebooted and back to same problem.Man,this been bugin me for two days now,sometimes i reboot the phone and i have root permissions then i reboot again and they are gone!
Big question is:is everybody on Epic have same issue or is it just on certain phones,kernels or roms?
I updated JID6 using ODIN
Rooted using OCLF One click
Using Root Explorer I am unable to modify these files after JID6 update.
Previously i was able to move/delete these files. Not anymore.
Current Permission is rw-r--r--
I tried to modify my permsission, but it does not permanently apply. Does anybody else have this problem.. Even after its been rooted, i can't make these permission changes therefore i can't move/delete these files.
Bootup: system/etc/PowerOn.wav
Shutdown: system/media/audio/ui/Shutdown_128.ogg
Did you remount /system rw?
busybox mount -o rw,remount /system
samlot said:
I updated JID6 using ODIN
Rooted using OCLF One click
Using Root Explorer I am unable to modify these files after JID6 update.
Previously i was able to move/delete these files. Not anymore.
Current Permission is rw-r--r--
I tried to modify my permsission, but it does not permanently apply. Does anybody else have this problem.. Even after its been rooted, i can't make these permission changes therefore i can't move/delete these files.
Bootup: system/etc/PowerOn.wav
Shutdown: system/media/audio/ui/Shutdown_128.ogg
Click to expand...
Click to collapse
I have the exact same problem. I posted a thread pretty much identical to this one. Still no answer...
busybox mount -o rw,remount /system
worked for me. Once remounted I could rename the startup/shutdown sounds.
Thanks guys for responding, Thats it. Once I installed Busy Box i was able to move those files again. I guess after the JI6 update, it removes your previously installed busy box. I coulda swear i had busy box already installed when i was using titanium backup. But then I remember i had to Re-Root the phone as well.
rmeden said:
busybox mount -o rw,remount /system
worked for me. Once remounted I could rename the startup/shutdown sounds.
Click to expand...
Click to collapse
So just to be clear....type that string exactly as shown into terminal on the phone and that's it? Then I can delete (not rename) the sound files?
yes. you should have needed to do it the first time, too... /system is always mounted read-only.
and you also need a root shell (su)
chui101 said:
yes. you should have needed to do it the first time, too... /system is always mounted read-only.
and you also need a root shell (su)
Click to expand...
Click to collapse
Sweet! That worked for me! I had to change back to the samsung keyboard because everytime I used the , key in terminal SwiftKey would crash.
No more obnoxious startup/shutdown sounds! Woooo hoooo! Made my Friday!
Since updating to the new froyo I have root, but I cannot get root explorer to be able to access /system in any way possible, it reads it but cannot write/modify.
I have replaced every root file with a new version, even tried the /system on boot set to r/w method with that market app. Its getting frustrated as this has ALWAYS worked before.
Did you come from voodoo?
Sent from my SCH-I500 using XDA App
I had a lot of trouble with Root Explorer as well. Super Manager has worked much better with the r/w access.
Sent from my SCH-I500 using XDA App
I'll give it a shot using that other app and see what happens.
That app still only has r/o access. Super user isn't granting my phone r/w access for /system.
Ev3rM0r3 said:
Since updating to the new froyo I have root, but I cannot get root explorer to be able to access /system in any way possible, it reads it but cannot write/modify.
I have replaced every root file with a new version, even tried the /system on boot set to r/w method with that market app. Its getting frustrated as this has ALWAYS worked before.
Click to expand...
Click to collapse
You positive you still are root? Try the root process again just for ****s and giggles...
Run one of the following with your phone connected to your computer and try again.
Voodoo:
Code:
adb shell mount -o remount,rw -t ext4 /dev/block/stl9 /system
Non-Voodoo:
Code:
adb shell mount -o remount,rw -t rfs /dev/block/stl9 /system
Yes, I'm getting this too.
Not only this. I use android commander to see what's in the folders.
While I'm in CWM in the phone, Android Commander shows only one folder in /system. That folder is /system/etc. This might explain why I can't flash anything into my phone to save my life. Anyone know what could be causing this?
It's odd because when my phone boots up, Android Commander shows /system will all of it's glory...
ev3rm0r3 said:
since updating to the new froyo i have root, but i cannot get root explorer to be able to access /system in any way possible, it reads it but cannot write/modify.
I have replaced every root file with a new version, even tried the /system on boot set to r/w method with that market app. Its getting frustrated as this has always worked before.
Click to expand...
Click to collapse
and don't double post!!!
http://forum.xda-developers.com/showthread.php?t=955487
I have the exact same issue. Just talked it over with Adrynalyne.
You are going to have to download an All-In-One Odin Package such as
http://forum.xda-developers.com/showthread.php?t=867648
Then, you're going to have to start over and flash your CWM Recovery from jt
http://forum.xda-developers.com/showthread.php?t=942021
Then you Odin flash the modem of the ROM that you want to install, then you use CWM to flash the ROM that you want to install...
Make sure that you do to not flash using Phone. Use PDA option in Odin.
Apparently, it's a corrupt dbdata partition that is causing it. This can happen occasionally when installing VooDoo... Just another reason to stay away from VooDoo...
BTW, Is this working for you? I think it's working for me as of yet. I'm not done yet so I can't assure you yet.
I don't think is working for me... If it worked for someone else let me know. I don't know what happened.
Re-establishing ROOT using CWM with Adrynalyne modified ChainsDD superuser +busybox package from the link below...
http://forum.xda-developers.com/showthread.php?t=913470
I just installed root explorer and set my system to RW, I can see it all the way through in ADB. Then I re-locked it in root explorer.
I've debranded a UK Orange Flipout and unlocked to use on Vodafone UK.
The mobile signal is terribly weak and spends more time with no bars that with. It makes the phone useless as a phone however great the design is.
Sitting next to another android phone on the same network the bars are almost full on the other phone - when showing nothing on the Flipout.
Does anyone else have this problem? Is there something I can do to re-configure the phone and make it work as a phone? I've had all the data settings from Vodafone reset for MMS and data etc.
If no answer it will have to go back to stock ROM and back to the shop.
Thanks.
Hey, I got the same problem. Had me temporarily switch back to Milestone 'cause Flipout wasn't able to even connect to the service..no signal at all. I noticed that Flipout has slow network acquiration compare to Milestone. But, I have to point out that I flashed it from stock to UK ROM without BLUR so it's more likely possible that something just went wrong. For now I blame the basebands and try to solve it that way..somehow. let me know if any news
Sent from my Milestone using XDA App
ok, it was the baseband.. i changed it from what it was to this (attachment) and everything's fine.
you have to be rooted, and remount system as r/w
the original baseband files are located in /system/etc/motorola/bp_nvm_default
basically you need to replace this folder with the new one and set the same permissions as the original files had. i don't know if you know how so just for sure, here's the how-to
i suggest you doing this:
0]if you are not rooted, install Universal Androot and press Go Root, then reboot your phone
1]unrar the attachment to your phone's sdcard
2]boot up the phone, switch to airplane mode
3a]if you have Root Explorer, navigate to /system/etc and push remount as r/w
3b]if you don't have that, install Root Toolbox go to Mount-System Mount Options-Mount System R/W
4]fire up Terminal Emulator
5]enter those commands: (enter after each line)
Code:
su
cd /system/etc/motorola
cp -R /sdcard/bp_nvm_default bp_nvm_default_nw
cp -R bp_nvm_default /sdcard/bp_nvm_default_BACKUP
chmod 755 bp_nvm_default_nw
chown root.root bp_nvm_default_nw
cd bp_nvm_default_nw
chmod 644 *
chown root.root *
cd ..
rm -R bp_nvm_default
mv bp_nvm_default_nw bp_nvm_default
reboot
6]after the reboot, turn off flight mode, let the phone get registered to network and see what happens.. hope this will fix your problem.
it's a bit tricky, i actually had to reboot after mounting system to R/W and giving Superuser permissions and mount again because somehow it didn't work for the first time.. anyway, let me know if anything goes wrong
Thanks, that looks a bit technical but ill give it a go... thanks for info.
Sent from my Transformer TF101 using Tapatalk
Well I gave this a go - and I kept getting permission denied. sounds like problem you had with the system RW refusing to allow a copy.
Anyhow I am hoping I might have fixed it by using this link
http://dext3r.komodin.org/
And there is a radio file you can install under Quick FAQ with different country baseband radio files. Might help someone else ...
it didnt work
well, i did everything as written except i used ES File Manager to mount the /system as R/W and when it came to:
cp -R bp_nvm_default /sdcard/bp_nvm_default_BACKUP
it said "cp: can't create symlink '/sdcard....': Operation not permitted" for every file so i just did it manually with ES File Manager... that is only a backup anyway and shouldnt affect anything.
it just doesnt work.
and why cant i just drop the baseband files in there with copy and paste? that didnt work either.
i need baseband files for T-Mobile on the US network for the Flipout. does anyone have any others i could try?
thanks!
Hello,
I have SM-N9005 variant and recently I updated to the latest android 4.4.2 leaked version with Odin, and then rooted with CF-Auto-Root.
After that, I lost the permission to write to external sdcard.
I searched and found this: http://forum.xda-developers.com/showthread.php?p=49603814
I backed up /system/etc/permissions/platform.xml and then I followed the instructions there.
After restart, a lot of app stopping messages showed and I had no access to file system or network anymore.
I used adb shell to restore the original platform.xml but it didn't helped in any way.
It seems that all mounts and networks are working, but none of the applications has permission to use any of them.
How do I resolve this, without wiping all my data?
Thank you!
You need to set the correct permissions on the .xml after you overwrite it back into the /system Off the top of my head I can't think what they are (just out of bed and got to work so still sleepy!)
radicalisto said:
You need to set the correct permissions on the .xml after you overwrite it back into the /system Off the top of my head I can't think what they are (just out of bed and got to work so still sleepy!)
Click to expand...
Click to collapse
I tried 644 and 777 but the problem persists.
rw-r-r which is 644 - read wrong
or chmod 666 -- forgive my lack of memory, it has been a long time since I have used chmod commands, few years since my glFTPD / site modding days.
radicalisto said:
rw-r-r which is 644 - read wrong
or chmod 666 -- forgive my lack of memory, it has been a long time since I have used chmod commands, few years since my glFTPD / site modding days.
Click to expand...
Click to collapse
The problem still persist
DxCK said:
The problem still persist
Click to expand...
Click to collapse
i dont know if it helps in your situation but did you try the "fix permissions" from a custom recovery like twrp?
there are also scripts you can execute in a terminal, the knoxout script linked in my sig for example has a permission fixer included.
A.N.Droid said:
i dont know if it helps in your situation but did you try the "fix permissions" from a custom recovery like twrp?
there are also scripts you can execute in a terminal, the knoxout script linked in my sig for example has a permission fixer included.
Click to expand...
Click to collapse
Thank you.
When i run this, no matter what are the parameters, for example: sh kn0x0ut.sh kn0x0ut
it says:
ERROR: Unknown parameter ""
Removing all temp folder /data/media/kn0x0ut_temp...
DxCK said:
Thank you.
When i run this, no matter what are the parameters, for example: sh kn0x0ut.sh kn0x0ut
it says:
ERROR: Unknown parameter ""
Removing all temp folder /data/media/kn0x0ut_temp...
Click to expand...
Click to collapse
just type sh kn0x0ut.sh to get all commands.
if you dont get this working, you can do it from twrp (i think cwm too)if you have it.
tap on "advanced" and then on "fix permissions".