Related
I have noticed that some ROMs (nandroid backups) do not have the 850 MHZ band enabled for AT&T North America and show up as No Service on my phone. How do you enable it?
I assume it has to do with the build.prop
I've got the same problem...
Take the following five files from /system/etc/motorola/bp_nvm_default on a working firmware and put them in the same place in the other firmware.
File_Audio
File_Audio2
File_GSM
File_Seem_Flex_Tables
generic_pds_init
Permissions are -rw-r--r-- for all files and user/group are 0:0
I have done this to enable the MotoFrenzy based on EU firmware to work on the Telus network.
shadowofdarkness said:
Take the following five files from /system/etc/motorola/bp_nvm_default on a working firmware and put them in the same place in the other firmware.
File_Audio
File_Audio2
File_GSM
File_Seem_Flex_Tables
generic_pds_init
Permissions are -rw-r--r-- for all files and user/group are 0:0
I have done this to enable the MotoFrenzy based on EU firmware to work on the Telus network.
Click to expand...
Click to collapse
thanks so much
telus how to copy
hi , what program did you used to be able to copy them and how sorry to be dummmm.
i have a telus milestone no network only wifi.thank you
Do you know the three digit conversion for the permission. I believe it starts with 7
shadowofdarkness said:
Take the following five files from /system/etc/motorola/bp_nvm_default on a working firmware and put them in the same place in the other firmware.
File_Audio
File_Audio2
File_GSM
File_Seem_Flex_Tables
generic_pds_init
Permissions are -rw-r--r-- for all files and user/group are 0:0
I have done this to enable the MotoFrenzy based on EU firmware to work on the Telus network.
Click to expand...
Click to collapse
Root Explorer is one of the easier ways to copy the files. It's very much work the cheap price.
shadowofdarkness said:
Take the following five files from /system/etc/motorola/bp_nvm_default on a working firmware and put them in the same place in the other firmware.
File_Audio
File_Audio2
File_GSM
File_Seem_Flex_Tables
generic_pds_init
Permissions are -rw-r--r-- for all files and user/group are 0:0
I have done this to enable the MotoFrenzy based on EU firmware to work on the Telus network.
Click to expand...
Click to collapse
The numerical value for these permissions are 644
telus network no signal
after changing with root explorer those file audio ,i m stock on droid eye on boot and that s it . any help thanks
telus network no signal
after changing with root explorer those file audio ,i m stock on droid eye on boot and that s it . any help thanks
okk it working now thanks any how .
roriii said:
after changing with root explorer those file audio ,i m stock on droid eye on boot and that s it . any help thanks
Click to expand...
Click to collapse
Too bad. Restore to a Nandroid Backup and try again. Also, don't double post.
roriii said:
after changing with root explorer those file audio ,i m stock on droid eye on boot and that s it . any help thanks
Click to expand...
Click to collapse
im having the same issue and tried several times, what did you do diff. to make it work? thanks
you can try the following: go to the testing menu (put *#*#4636#*#* in dialer). Choose Phone information and then push the menu button and choose Radio band where you can choose USA band. I get an error message in the stock euro rom but maybe it works for you.
wmn79 said:
you can try the following: go to the testing menu (put *#*#4636#*#* in dialer). Choose Phone information and then push the menu button and choose Radio band where you can choose USA band. I get an error message in the stock euro rom but maybe it works for you.
Click to expand...
Click to collapse
thanks friend, but it seems like i'm getting the same error as you "SET USA BAND UNSUCCESSFUL"
i able to copy the files over from a working 2.1 rom, i must be missing a step.
ok i got it working, i was missing a very important step, i hope this helps some of you.
after overwriting the files, the file permissions and user/group ownerships changed.
first remount the /System in Read Write mode in ADB
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Then i had to set the proper permissions using chown and chgrp commands via ADB (As stated in the previous posts)
example: chown 0 File_GSM and chgrp 0 File_GSM to all 5 files.
thanks again.
hey guys, so i used an app call super manager to copy the files you said off the workin flash, then i loaded my froyo 2.2 softwar on my milestone an then went back to super manager an pasted the files in the same place i got them, i dont got a signal still, but at the same time i feel like im doing somethin wrong because it never asked me to over write teh files, thanks please help
citrixmeta said:
ok i got it working, i was missing a very important step, i hope this helps some of you.
after overwriting the files, the file permissions and user/group ownerships changed.
first remount the /System in Read Write mode in ADB
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Then i had to set the proper permissions using chown and chgrp commands via ADB (As stated in the previous posts)
example: chown 0 File_GSM and chgrp 0 File_GSM to all 5 files.
thanks again.
Click to expand...
Click to collapse
Has anybody successfully done this?
Using Nook Color, CM7 nighly 107.
Got Netflix working a while back by modifying the build.prop file using ES File Explorer - no issues.
Tried again to make some mods and cannot save it anymore. ES reports "writable - NO"
Tried to "su chmod 666" it and it comes back with "File system read-only"
Is anybody else seeing this? What am I missing?
Thanks...
I encountered a similar situation during the build.prop edit while using ES File Explorer on my NC running CM7 on internal memory.
Possibly, the permissions in the program need to be changed to enable it to "write".
Here's what I did: Menu==>Settings==>Root options. "Check" Root Explorer and if my memory serves me correctly, click "Yes" to get past the "Experimental Feature", toggle the "Cyanogen Mod" (if you're using CM7) radio button, click OK and check the "Mount File System" box to make the system writable.
Now, it should be writable. Hope this helps.
dhyamato said:
... check the "Mount File System" box to make the system writable.
Click to expand...
Click to collapse
Thanks for the tip, that wasn't it
I remember setting those originally. I just checked again and "Root Explorer" and "Mount FIle System" are both checked.
mwilli20 said:
Using Nook Color, CM7 nighly 107.
Got Netflix working a while back by modifying the build.prop file using ES File Explorer - no issues.
Tried again to make some mods and cannot save it anymore. ES reports "writable - NO"
Tried to "su chmod 666" it and it comes back with "File system read-only"
Is anybody else seeing this? What am I missing?
Thanks...
Click to expand...
Click to collapse
In 106 SU wasn't working correctly until I reinstalled it. You can't modify build.prop without superuser rights. Check the thread about SU / Superuser missing in 106 (and I bet 107) for instructions. It worked for me.
DiDGR8 said:
Check the thread about SU / Superuser missing in 106 (and I bet 107) for instructions. It worked for me.
Click to expand...
Click to collapse
Interesting... the OP withdrew his post: (apparently it's back in 107)
http://forum.xda-developers.com/showthread.php?t=1131369
However when I checked it, the SU app was misbehaving, Force closing, refusing to respond to the menu command. So I reinstalled it. Now it's OK.
Unfortunately I still cannot edit the build.prop file.
I don't think it's a superuser problem because without SU access ES cannot even see the system folder!!! I can see it, and edit the file, just cannot save it.
You might try fixing permissions under recovery.
have you tried the app: nook netflix fixer?
I've changed it successfully on the past 6 consecutive nightlies using adbwireless pull/push. However since 106 I've hsd to reflash su. N108 hasn't given me the su issue. Is it fixed?
Same problem with the build.prop file: cannot save changes, or copy over it. Running in nightly 108 today. Tried both Root Explorer and ES File manager.
I think you need to change the build.prop file properties to be rw using chmod. Don't forget to mount system as rw before doing the chmod.
Sent from my Huawei Ascend using XDA App
foltz61 said:
I think you need to change the build.prop file properties to be rw using chmod.
Click to expand...
Click to collapse
Tried that (sudo chmod 666...), get the same message. "file system is read-only"
backup and restore fresh start....?
I'm not great at linux but I do it differently. Try chmod +rw /system/build.prop . Make sure you have system mounted as RW first. I'd also check superuser to make sure whatever terminal/file explorer you are using still has root privileges.
Sent from my Huawei-M860 using XDA App
foltz61 said:
Try chmod +rw /system/build.prop
Click to expand...
Click to collapse
666 is the same thing as +rw in this case...
It looks like the "fresh start" suggestion a couple of posts up is the best
All those numbers always confuse me . Sorry. Good luck.
Sent from my Huawei-M860 using XDA App
bike2002 said:
have you tried the app: nook netflix fixer?
Click to expand...
Click to collapse
Thanks! That did it!
Does anybody know why this app can modify the build.prop file while ES File Explorer cannot?
I had to mount the folder containing build.prop with rw access in order to use chmod. I think the latest version of the netflix fixer may do the same (see my post in that thread). In short, I used;
Code:
su
busybox mount -0 rw,remount /dev/block/mmcblk1p3 /system
in the terminal before using the chmod command in order to give myself rw permissions in the folder. I'm only two days old at this, so it beats me why root doesn't have normal rw permissions on the folder.
NCKevo said:
I had to mount the folder containing build.prop with rw access in order to use chmod...
Click to expand...
Click to collapse
Thanks for the tip. I ran the command successfully (by the way, small typo, I believe it's -o not -0) and was able to chmod and edit the file with vi.
That's where confusion began. I reboot and after the reboot I was able to modify the file without remounting the /system directory. The mount command does not surive a reboot does it?
Have you tried just pulling the build.prop
Code:
c:/<target_folder> adb pull /system/build.prop
then editing it with note pad then pushing it back and rebooting>
mwilli20 said:
That's where confusion began. I reboot and after the reboot I was able to modify the file without remounting the /system directory. The mount command does not surive a reboot does it?
Click to expand...
Click to collapse
That is confusing. What are the full (i.e. ls -l) permissions on the file now? (It's possible that it somehow ended up with o+w, but I don't understand how - vi isn't exactly known for changing permissions on-the-fly.)
Rodney
Hi mates. I am experiencing issues in editing the build.prop. I mean: even if I can access the file, when I try to save it, it tells me I cannot...
I use file expert to browse and jota text to edit (both free). Es file explorer does not allow me to set root option...maybe it it's not working with note yet...
In any case I don't know what to do to save the new build.prop.
Any suggestions?
Thx to all...
Sent from my GT-N7000 using XDA App
Diamantes said:
Hi mates. I am experiencing issues in editing the build.prop. I mean: even if I can access the file, when I try to save it, it tells me I cannot...
I use file expert to browse and jota text to edit (both free). Es file explorer does not allow me to set root option...maybe it it's not working with note yet...
In any case I don't know what to do to save the new build.prop.
Any suggestions?
Thx to all...
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
Es explorer works well. u might have found it if u searched.
Just make sure that u have enabled root options in the settings.
No.
As I wrote before, I don't know why but Es doesn't allow me to have root options enabled, so I was forced to find a new root explorer. The problem is that I can't save the new build.prop: the app tells me it cannot save the file...
Suggestions?
Sent from my GT-N7000 using XDA App
Install File Expert, go to settings and enable "Root Explorer" (under "File Explorer Settings"), go back, press menu, more and then "Mount".
/system is mounted RO by default.
use a shell and as root type
Code:
busybox mount -o remount,rw /system
you should get a full access now to all /system filesystem.
THANKS
BazookaAce said:
Install File Expert, go to settings and enable "Root Explorer" (under "File Explorer Settings"), go back, press menu, more and then "Mount".
Click to expand...
Click to collapse
Thx mate. It worked. After chose the option "Mount", I edit also the properties of the file (write,read,all...). After that, File expert allowed me to choose the app to open the text file: I choose ES text, because Jota text continued not saving the file. I finally saved the build.prop file.
THX.
sibere said:
/system is mounted RO by default.
use a shell and as root type
Code:
busybox mount -o remount,rw /system
you should get a full access now to all /system filesystem.
Click to expand...
Click to collapse
Thank you too.
uff!! what a pain in the ....ss!
Thanks guys! I enabled the Root checkbox, but I cant mount!
I get a Mount failed message.
I tried to be in the / directory when issued the Mount command for RW (using GUI in that application), and being inside /system as well - same error.
I've granted the application Superuser permissions, so thats not it.
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
the first method worked great for me
thanks
Dassen said:
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
Click to expand...
Click to collapse
I tried both without success.. What explorer are you using? I tried with ES and got an error "the operation failed".. and I couldnt change permissions neither
thanks for any help
Are you rooted?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
blazeplacid said:
Are you rooted?
Click to expand...
Click to collapse
I supposed to. I rooted my device to install google play.. but I dont know if I continue been root.. I checked my permissions on system\app and I only have readable..
Could you explain me how to check if I am root, and if not, how to be root again to apply your process?
Thanks for your help
karacc said:
I supposed to. I rooted my device to install google play.. but I dont know if I continue been root.. I checked my permissions on system\app and I only have readable..
Could you explain me how to check if I am root, and if not, how to be root again to apply your process?
Thanks for your help
Click to expand...
Click to collapse
You go to the setting of ES,then at the bottom of setting menu, it has Root setting. Go there and checked all check boxes. If you can, that's mean your KF is rooted.
Sent from my KFTT using xda app-developers app
tried method 1 and it worked right away :good:
Worked
Method 1 worked for me.
Thanks.
Dassen said:
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
Click to expand...
Click to collapse
Worked for me, too. Was surprised about the beautiful wallpapers to see now everytime i turn the thingy on
Adding a Boot Animation
Thanks for this info. I used the 2nd method and it worked immediately. Are there Boot Animations for the KFHD? Or can Boot Animations from, say my LG ICS Spectrum work?
Dassen said:
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
Click to expand...
Click to collapse
Awesome, confirmed working on kindle fire 2 running 10.2.1
frieked said:
Awesome, confirmed working on kindle fire 2 running 10.2.1
Click to expand...
Click to collapse
Thanks a lot for this :highfive:
Confirmed works on KF 8.9, thanks OP! I renamed to dtcp_apk.ads
finally, those horrific ad screens are gone! thank you sir!
if you have adb available, you should be able to do this without a root explorer.
use one of the following codes:
adb shell
su
mount -o remount,rw /system
mv /system/app/dtcp_apk.apk /system/app/dtcp_apk.apk.bak
exit
exit
adb shell
su
mount -o remount,rw /system
chmod 000 /system/app/dtcp_apk.apk
exit
exit
adb shell
su
mount -o remount,rw /system
rm /system/app/dtcp_apk.apk
exit
exit
The first one will rename it. The second one will clear its permissions. The third one will remove it completely.
It should go without saying, but its not my fault if you screw something up, or if it is necessary to have this apk in your system, and you use the third method. I haven't tried it, but it should work. I do know what the commands do.
Didn't also work for me with es file explorer the first time i've tried it, although i've enabled all root options.
Rebooting the device helped me, but it's also important to make sure that you give the explorer the permission to change system data
Sent from my KFTT using XDA Premium HD app
Method 1 working
I tried it just out of curiosity and it worked right away. Using ES explorer, BTW.
Thanks!
Dassen said:
both methods require a root explorer.
Method 1:
navigate to the system folder
find "App" folder
Change the name of "dtcp_apk.apk" to dtcp_apk.bat
Method 2:
Navigate to system folder
find "App" folder
change permissions of Dtcp_apk.apk to all blank
Hope this helped someone.
Credits to spunker88 for sharing this info.
Click to expand...
Click to collapse
Thank you so much!!! Method 1 worked great. Also renamed the odex file to .odex.bat through root explorer. Note, in root explorer you will probably have to push the little 'Mount R/W" button once you get into system/app
Sweet. $15 saved.
Thanks for the quick 'how to'.
Hey Guys,
I got a simply question, I got root but I don't know if I got FULL ROOT, How to check that?
Yes, on Play Store there are 1000 of apps but I don't trust them.
Any commands from Terminal to Determine if I have Full Root?
eclyptos said:
Hey Guys,
I got a simply question, I got root but I don't know if I got FULL ROOT, How to check that?
Yes, on Play Store there are 1000 of apps but I don't trust them.
Any commands from Terminal to Determine is I have Full Root?
Click to expand...
Click to collapse
Uhm open a terminal and make a file in "/system" I guess. You can do that using the following command: "touch /system/roottest.txt".
Better answer provided here.
B1nny said:
Uhm open a terminal and make a file in "/system" I guess. You can do that using the following command: "touch /system/roottest.txt".
Click to expand...
Click to collapse
I executed that command but I don't get anything, not even the file in Device>System..
See the Pic..
eclyptos said:
I executed that command but I don't get anything, not even the file in Device>System..
See the Pic..
Click to expand...
Click to collapse
Get root in terminal first by typing
Code:
su
Then mount system as RW and make a directory by typing
Code:
mount -o remount,rw system
mkdir /system/test
or, mount system using root explorer and then do this
Code:
su
mkdir /system/test
Trust me, you have full root....
Ok.
I just Check in.
gregbradley said:
Get root in terminal first by typing
Code:
su
Then mount system as RW and make a directory by typing
adb shell mount -o remount,rw system
mkdir /system/test[/code]
Trust me, you have full root....
Click to expand...
Click to collapse
A bit confused here with that code....
adb shell mount -o remount,rw system
mkdir /system/test[/code]
It have to be like that in Terminal?
eclyptos said:
I just Check in.
A bit confused here with that code....
adb shell mount -o remount,rw system
mkdir /system/test[/code]
It have to be like that in Terminal?
Click to expand...
Click to collapse
Check his post again, he corrected himself.
I edited my post
@gregbradley
I think I have a problem, what you think? It tells me that system/test is Read-Only..
use root explorer to mount system then try the mkdir again
or just root explorer to mount system..as soon as you can do that you have root.....
Full root just means you keep root after a reboot and the security of the RIC has been disabled
gregbradley said:
use root explorer to mount system then try the mkdir again
or just root explorer to mount system..as soon as you can do that you have root.....
Full root just means you keep root after a reboot and the security of the RIC has been disabled
Click to expand...
Click to collapse
I am not familiar with that, which Root Explorer are you referring too?
eclyptos said:
I am not familiar with that, which Root Explorer are you referring too?
Click to expand...
Click to collapse
root explorer
look on the play store
or use any explorer that can gain root...and just modify something in system...change permission, delete or make a file...
if you just reboot your phone and run an app that requires root and it works then you have full root.
gregbradley said:
if you just reboot your phone and run an app that requires root and it works then you have full root.
Click to expand...
Click to collapse
ok...I will try...at the moment I was using ES File Explorer and it not allow me to make or paste any file in system folder...
..I will keep you updated...
eclyptos said:
ok...I will try...at the moment I was using ES File Explorer and it not allow me to make or paste any file in system folder...
Click to expand...
Click to collapse
then you have root, and if you reboot and can still do this you have "full" root
..I will keep you updated...
Click to expand...
Click to collapse
There is no need... I am really unsure on why you are asking this. Seeing as you have posted loads of help posts about this I would expect you to know the difference and know that you have full root.
Trust me, you have it.
eclyptos said:
ok...I will try...at the moment I was using ES File Explorer and it not allow me to make or paste any file in system folder...
..I will keep you updated...
Click to expand...
Click to collapse
If you are not allowed to modify system that's because is not mounted as Rw. Go to ES, make sure you have turned on root explorer and then click on root explorer. A pop up will appear, then select where says mount system as Rw.
gregbradley said:
then you have root, and if you reboot and can still do this you have "full" root
Click to expand...
Click to collapse
This I don't get it...
gregbradley said:
There is no need... I am really unsure on why you are asking this. Seeing as you have posted loads of help posts about this I would expect you to know the difference and know that you have full root.
Trust me, you have it.
Click to expand...
Click to collapse
I know, sometime I cooking my brain instead of my phone and I missing stupid things...and learn small thing.
luis4ever said:
If you are not allowed to modify system that's because is not mounted as Rw. Go to ES, make sure you have turned on root explorer and then click on root explorer. A pop up will appear, then select where says mount system as Rw.
Click to expand...
Click to collapse
You see! OMG! That was the stupid thing...sooo stupid! You are the man. Now everything is working.
ES was granted by Su and it now allow me to modified System files and folders.
After executing the commands in Terminal I find a new folder named "test" in System. Thanx to @gregbradley
Thank you all!
You see! OMG! That was the stupid thing...sooo stupid! You are the man. Now everything is working.
ES was granted by Su and it now allow me to modified System files and folders.
After executing the commands in Terminal I find a new folder named "test" in System.
Thank you all!
Click to expand...
Click to collapse
Glad you solved the problem
wow....
gregbradley said:
wow....
Click to expand...
Click to collapse
lol...