I was able to push build.prop to /system/build.prop and chmod it to 644, I also, just for giggles, did this to /system/system/build.prop however whenever I restart the phone, the changes get overwritten with the defaults and my changes are purged.
Is there a way to resolve this? I am trying to do this without root
Sorry no way to do this without root,,,it will revert back to stock on reboot.
MrEpod said:
I was able to push build.prop to /system/build.prop and chmod it to 644, I also, just for giggles, did this to /system/system/build.prop however whenever I restart the phone, the changes get overwritten with the defaults and my changes are purged.
Is there a way to resolve this? I am trying to do this without root
Click to expand...
Click to collapse
Related
Root is required. Make a Nandroid backup! (I accidentally deleted by build.prop file and bootlooped my phone)
1) Download ES File Explorer (Or any other root file editor)
2) In ES File Explorer, go into Setting > Root Settings and enable both check boxes
3) Navigate to /system/ and copy/paste build.prop to /sdcard/ (just in case)
4) Open & edit /system/build.prop
5) Change the following lines to make your phone think it is a HTC G2:
ro.product.model=HTC Vision
ro.product.manufacturer=HTC
OR
ro.product.model=Nexus S
ro.product.manufacturer=samsung
6) Reboot the phone
7) Install the netflix apk (if you haven't already)
8) Enjoy
HELP!
I've run into a problem with this. My phone has gone into bootloop.
Is there a way to copy the build.prop I backed up on my sdcard to the /system/build.prop without booting the phone,... I.E. from the cyanogen recovery mode?
thedarkharlequin said:
I've run into a problem with this. My phone has gone into bootloop.
Is there a way to copy the build.prop I backed up on my sdcard to the /system/build.prop without booting the phone,... I.E. from the cyanogen recovery mode?
Click to expand...
Click to collapse
I have the same issue right now but I don't have Cyanogen Rec Mode. I just have the ENG Bootloader and that's it.
Same issue with Samsung Fascinate
Anyone have any ideas how to copy back a build.prop if the phone is stuck in a boot loop? Adb won't work as it doesn't get far enough in boot to connect and it won't connect in recovery mode. As I can get into recovery, I may be able to flash a rom but that would be a worse case scenario.
theberidox said:
Anyone have any ideas how to copy back a build.prop if the phone is stuck in a boot loop? Adb won't work as it doesn't get far enough in boot to connect and it won't connect in recovery mode. As I can get into recovery, I may be able to flash a rom but that would be a worse case scenario.
Click to expand...
Click to collapse
I haven't yet tried ADB but since you've already answered my question then I guess we're stuck and must upload a stock rom and run it. I will try it once I get home but for now any new info would help. Sucks not having a phone at all
Can you not boot into recovery, mount system and use adb shell to copy the file from the SDCard?
D
dsb9938 said:
Can you not boot into recovery, mount system and use adb shell to copy the file from the SDCard?
D
Click to expand...
Click to collapse
No sir. I cannot do such procedure. I'm trying to load the update.zip without wiping all my info out. I can go into recovery but cannot mount. I cannot use ADB it says error device offline.
Bootloop Fixed
dsb9938 said:
Can you not boot into recovery, mount system and use adb shell to copy the file from the SDCard?
D
Click to expand...
Click to collapse
Thanks. I forgot to mount system. I'm back up and running now. Using clockwork recovery, I mounted system and then adb was able to connect. I then used "adb push build.prop /system/" to move a corrected copy from my pc to the phone (I had originally used an on-phone editer that reformated the file and caused the issue). Rebooted phone and it booted. Netflix still doesn't work, (I changed the ro.product.model=Nexus S & ro.product.manufacturer=Samsung) but at least my phone is back.
FYI Update: I changed my build.prop to ro.product.model=HTC Vision & ro.product.manufacturer=HTC and now no longer get the unsuported message but Netflix now closes after log-in. I guess this was all for nothing for me.
Having problems with captivate
ES explorer wont work, so I had to buy different one. Changed it to Nexus S, rebooted, opened netflix, get an error message saying my device is not supported. Please help.
I'm rooted and unknown sources is on and I dl'd es file explorer and went into settings and root options and click on root explorer it asks cyanogen or HiAPK rom. Is there a specific rom I should be running? When i click root explorer then i get "test failed. This feature cannot run on your phone, and then pops up to grant superuser permissions. Any suggestions? Thanks
And now I'm running cyanogen 7.0.3 and select cyanogen from the pop up but still get same error please help I have the apk for Netflix but says needs update and won't find update and just closes so i believe editing build.prop will get it running but cnnt get in to do the edits thanks in advance
nvm. i got it !!!!
krinilssen said:
Root is required. Make a Nandroid backup! (I accidentally deleted by build.prop file and bootlooped my phone)
1) Download ES File Explorer (Or any other root file editor)
2) In ES File Explorer, go into Setting > Root Settings and enable both check boxes
3) Navigate to /system/ and copy/paste build.prop to /sdcard/ (just in case)
4) Open & edit /system/build.prop
5) Change the following lines to make your phone think it is a HTC G2:
ro.product.model=HTC Vision
ro.product.manufacturer=HTC
OR
ro.product.model=Nexus S
ro.product.manufacturer=samsung
6) Reboot the phone
7) Install the netflix apk (if you haven't already)
8) Enjoy
Click to expand...
Click to collapse
Thanx for the Help!
And Not to Totally get off the subject but does Anyone know what needs to be Changed in the Build.Prop to get the Connection time Faster? I saw it in a thread before but Can't Remember Where?
Thanx in Advance!
PMGRANDS said:
Thanx for the Help!
And Not to Totally get off the subject but does Anyone know what needs to be Changed in the Build.Prop to get the Connection time Faster? I saw it in a thread before but Can't Remember Where?
Thanx in Advance!
Click to expand...
Click to collapse
add this to the end of your build.prop
Code:
#ISE:
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
I just applied Daoist's CWM stock ROM update (should still be rooted, right?). It came up first time.
Then, I modded my build prop (set dpi to 120 because I like it that way). But maybe I screwed up the file name in Root explorer, because now I'm in a boot loop and if I try ADB PULL /system/build.prop it says "file not found."
I can't get SU through adb, so can't push build.prop to /system. ADB remount returns an error. permission denied. Transformer won't boot, so I can't do anything from it.
I CAN get to cwm, and have been trying to create an update.zip that will just copy build.prop to /system, but everything I have tried quits with "install aborted" message.
What can I do?
restore a nand and dont try and **** with it again, lol. no but really, restore a nand and then copy your build. prop and make a flashable zip and place on your sd card in case it happens again, so you can just flash it in cwm.
Resolved..
Well, why go back when you can go forward?
I went ahead and installed the Prime ROM. Looks like it is eating all my currently installed apps.
Y'all should know, though, that if your system can't find a build.prop it won't start. You can ADB to it and have a rudimentary set of commands, but your ability to significantly alter anything in your file system will be prohibited.
Lesson learned.
glg
as a side note most editors in android rename system files when you change them to "nameoffileyouedited".bak so if you pull and rename that file that might have fixed your problem. also try lcd dencity changer from the market. its a little less hazordous
mrevankyle said:
as a side note most editors in android rename system files when you change them to "nameoffileyouedited".bak so if you pull and rename that file that might have fixed your problem. also try lcd dencity changer from the market. its a little less hazordous
Click to expand...
Click to collapse
That is true. I had backups. But without a build.prop, the virtual machine won't start. There is no way to do a file operation to replace the backup. At least none that I found. I had to flash the whole system.
glg
sorry for this post but i dont have the required 10 posts to post in the devolpment thread already on this subject.
I tried the 30fps fix by copying the 4 .so files over but i am still getting 15fps. I am running the latest S7 rom. I dont know what i am doing wrong. I paste them into system/lib and it says that the action was complete. i try to take a vid before and after a reboot and they are still just 15fps. any suggestions.
I've noticed that the multi select function on root explorer and maybe other file managers doesn't work if you are over writing files, might not work for any copy/paste function. I would rename the old files *.so.bak then copy the new ones one by one. after that reboot and see if the changes stuck. if not make sure you are actually rooted. could have a bad su binary causing havoc or something. if you have root ant it is working then to make 100% sure you are mounted rw go into a terminal emulator or adb shell and type
su
(phone should ask for super user permissions or give a toast or notification that su was granted)
mount -o remount,rw /dev/block/stl9 /system
if you don't get any error about illegal operations or permission denied then you should be able to copy the files with 99% certainty. of you have any trouble be sure to include details.
Thanks for the response. I do have full root access. I double checked. I also keep getting a su binarry update warning from Superuser. I update it but everytime i restart the phone it tells me i have to update again. My next mission is to figure out why it keeps reverting back.
I did what you said and replaced the files one at a time. and renamed the originals instead of putting copyies in another location and trying to overwrite the orginals. thank you for your help. I am now recording at 30fps after a reboot.
update to the newwest entropy DD kernel. the older kernels rooted the phone but the trouble with that is if you update the binary the kernel overwrites it on next boot. this is on way the binary can get corrupted.
Renaming the original to .bak also allows you to compare the permissions of the posted file to the original permissions. In some cases, I noticed made a different.
Hi There,
I bought an atrix 2 that is supposedly unlocked and rooted. I download a root checker and it says it is rooted. I was reading that if it is unlocked that u can use a different carrier which I have been. The phone was set up at the beginning to use T Mobile with a APN set up for this carrier and it worked fine. To save some money I switched to simple mobile which is also working fine. This might seem petty but the T Moblie APN is locked and i would like to delete it but dont know how. Can anyone help? My phone is running the currant ICS 4.0 update.
Thank you
chrisroch40 said:
Hi There,
I bought an atrix 2 that is supposedly unlocked and rooted. I download a root checker and it says it is rooted. I was reading that if it is unlocked that u can use a different carrier which I have been. The phone was set up at the beginning to use T Mobile with a APN set up for this carrier and it worked fine. To save some money I switched to simple mobile which is also working fine. This might seem petty but the T Moblie APN is locked and i would like to delete it but dont know how. Can anyone help? My phone is running the currant ICS 4.0 update.
Thank you
Click to expand...
Click to collapse
You'll need SQLite editor for this.
Using that goto settings storage (com.motorola.android.providers.settings)
Open settings.db
Search for and change dun_apn_changeble,dun_enable to 1.
Reboot.
Sent from my MB865 using xda premium
I Tried
deveshmanish said:
You'll need SQLite editor for this.
Using that goto settings storage (com.motorola.android.providers.settings)
Open settings.db
Search for and change dun_apn_changeble,dun_enable to 1.
Reboot.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I Installed SQLite and couldnt find the file u were referring to. I found something ending with providers settings but it was empty
Update
chrisroch40 said:
I Installed SQLite and couldnt find the file u were referring to. I found something ending with providers settings but it was empty
Click to expand...
Click to collapse
Ok I found the database and changed the dun_apn_changable and the dun_enable value from 0 to 1 and rebooted and the t-mobile apn is still locked?????????
Help!!!!
Hey just to be clear before anything else what exactly do you mean the apn is locked???Have you tried adding the apn for your new carrier manually by going into settings/more/mobile Network/acces point name/new apn???
Sent from my MB865 using xda premium
Locked APN
deveshmanish said:
Hey just to be clear before anything else what exactly do you mean the apn is locked???Have you tried adding the apn for your new carrier manually by going into settings/more/mobile Network/acces point name/new apn???
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
When I got the atrix 2 it was set up for T-Mobile with a tmobile apn. This apn has a locked symbol next to it. All i can do is open it and look at it. Cant edit or delete it. I added a simple mobile apn and the phone works fine with everything I am just wondering if there is any way to unlock the t-mobile apn so I can delete it????
You can still use your new apn even if the t-mobile apn is still there
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
I know that
rdhoggattjr said:
You can still use your new apn even if the t-mobile apn is still there
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
I know it works I have stated that already I just want to clean up my phone and get rid of the t mobile apn. Man I didn't think it would be this hard anybody got any suggestions. Somebody put it in the phone and locked it there has to be a way to reverse this.
Thank You
chrisroch40 said:
I know it works I have stated that already I just want to clean up my phone and get rid of the t mobile apn. Man I didn't think it would be this hard anybody got any suggestions. Somebody put it in the phone and locked it there has to be a way to reverse this.
Thank You
Click to expand...
Click to collapse
If you really must remove it, there is only one way.... I will tell you that it is a little dangerous if you mess up you will bootloop and have to fxz.
You will need the android SDK.
Your phone needs to be rooted.
You need to use adb to pull the /system/etc/apns-conf.xml file to your computer.
Code:
adb pull /system/etc/apns-conf.xml
Now you can edit it with any text editor you want, and you will need to remove the whole block that has the tmo APN.
You will need to mount /system read write:
Code:
adb shell
su
mount -o remount, rw /system
exit
exit
Then using adb put it back in place with this:
Code:
adb push apns-conf.xml /data/local
adb shell
su
cp /data/local/apns-conf.xml /system/etc
exit
exit
And do this to set the perms and owner correctly:
Code:
adb shell
su
chmod 644 /system/etc/apns-conf.xml
chown root /system/etc/apns-conf.xml
chgrp root /system/etc/apns-conf.xml
mount -o remount, ro /system
exit
exit
Now you can also just leave it there and it will hurt nothing.
Yes some things on this phone are harder to hack, but to me that makes it a little more fun and challenging.
Editing File
jimbridgman said:
If you really must remove it, there is only one way.... I will tell you that it is a little dangerous if you mess up you will bootloop and have to fxz.
You will need the android SDK.
Your phone needs to be rooted.
You need to use adb to pull the /system/etc/apns-conf.xml file to your computer.
Code:
adb pull /system/etc/apns-conf.xml
Now you can edit it with any text editor you want, and you will need to remove the whole block that has the tmo APN.
You will need to mount /system read write:
Code:
adb shell
su
mount -o remount, rw /system
exit
exit
Then using adb put it back in place with this:
Code:
adb push apns-conf.xml /data/local
adb shell
su
cp /data/local/apns-conf.xml /system/etc
exit
exit
And do this to set the perms and owner correctly:
Code:
adb shell
su
chmod 644 /system/etc/apns-conf.xml
chown root /system/etc/apns-conf.xml
chgrp root /system/etc/apns-conf.xml
mount -o remount, ro /system
exit
exit
Now you can also just leave it there and it will hurt nothing.
Yes some things on this phone are harder to hack, but to me that makes it a little more fun and challenging.
Click to expand...
Click to collapse
Ok i pulled the file with no problems and opened it with notepad. Do i delete everything in the file? I see the words T-mobile through out the whole file.
Permission denied
chrisroch40 said:
Ok i pulled the file with no problems and opened it with notepad. Do i delete everything in the file? I see the words T-mobile through out the whole file.
Click to expand...
Click to collapse
OK i deleted the block and did like u said to push back to phone but keep getting permission denied..Help!!!!
chrisroch40 said:
OK i deleted the block and did like u said to push back to phone but keep getting permission denied..Help!!!!
Click to expand...
Click to collapse
You did not follow my directions then. I gave you every step. Take another look, as you can not copy files directly to /system/etc with out root perms.
permission denied
chrisroch40 said:
Ok i pulled the file with no problems and opened it with notepad. Do i delete everything in the file? I see the words T-mobile through out the whole file.[/QU
Ok i did like u said and deleted the block but when i try pushing back to phone i get permission denied. Please Help.
Click to expand...
Click to collapse
Ok i pulled the file and deleted the T-mobile block i figure that out but when I tried to push back to phone i get permission denied. I followed the instructions.
jimbridgman said:
You will need to mount /system read write:
Code:
adb shell
su
mount -o remount, rw /system
exit
exit
Then using adb put it back in place with this:
Code:
adb push apns-conf.xml /data/local
adb shell
su
cp /data/local/apns-conf.xml /system/etc
exit
exit
Click to expand...
Click to collapse
So Again, you can not just push the file to /system/etc.... follow that above and it will work, I do this all the time.
I do it exactly as u posted.
jimbridgman said:
So Again, you can not just push the file to /system/etc.... follow that above and it will work, I do this all the time.
Click to expand...
Click to collapse
I do it exactly as u say changing it to read write and that part goes fine. When i try pushing the file after that I get permission denied.
I changed the /root to r/w and forgot to change it back before my phone died and now it is stuck in boot loop. I have tried twrp fix permission but does not seem to work. Is there any way for me to change it without wiping my phone. Don't want to lose the files I have on my phone.
Thank You in advance.
Reflash the ROM without a wipe. Quickest fix, providing this is the cause of your boot loop. How did you change the permissions? Root is already read/ write
Sent from my Nexus 5 using Tapatalk
I was changing the tether setting from this tutorial I had done previously but had been undone. And i also had reflash the Rom but still stuck in boot loop
nightang3l said:
I was changing the tether setting from this tutorial I had done previously but had been undone. And i also had reflash the Rom but still stuck in boot loop
Click to expand...
Click to collapse
Please answer my other questions.
I used root Explorer and change the r/o to r/W. I'm sorry if I confused you not the root folder it self but the root directory.
nightang3l said:
I used root Explorer and change the r/o to r/W. I'm sorry if I confused you not the root folder it self but the root directory.
Click to expand...
Click to collapse
That's just mounting it, not changing the permissions.
Connect the device in recovery and use adb shell to run the following command
Code:
adb shell
ls -ld /
Result should be
Code:
drwxr-xr-x
Maybe a link to the guide you used would be helpful.
Thank you will try when I have time.