how to edit your build.prop to get things like netflix working - Android Software/Hacking General [Developers Only]

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

Related

build.prop update.zip

Is it possible to make an update.zip file that replaces the build.prop file, or any way to replace the build.prop file without doing a full restore?
I did it using adb commands.
Well I tried using adb shell to swap the file, but when I ran su I got "[1] + Stopped (signal) su"
So I guess I'm going to be forced to do a nadroid restore of my system
Just use root explorer to copy the file to /sd, then use astro to edit it, and root explorer it back to the original spot and reboot. You don't need to change file permissions or any thing. No computer needed.
Sent from my GT-I9000 using Tapatalk
Boot loop
Clienterror said:
Just use root explorer to copy the file to /sd, then use astro to edit it, and root explorer it back to the original spot and reboot. You don't need to change file permissions or any thing. No computer needed.
Click to expand...
Click to collapse
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
remuscat said:
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
Click to expand...
Click to collapse
You could just reflash your current ROM and it should replace it.
korockinout13 said:
You could just reflash your current ROM and it should replace it.
Click to expand...
Click to collapse
Hi korockinout13,
I have tried to refresh from a rom i got, but I am prompted an error with Nand version.
The android in question is not common (Subor, a chinese Android Tablet) and have not found any firmware for my particular model except for the one supplied by the supplier, which still does not install.
At this stage reflashing is not an option, so I am looking for something else...
Thanks for your time
P
remuscat said:
Hi Clienterror,
What if the system is not booting?
I had installed an application which changes resolution and now ended up with a boot loop.
I have searched for ways how to extract the build.prop and correct the error, but none appears to exist.
I was asking if it is possible to extract the current build.prop via the update.zip method so that the build.prop can be repaired...
I read that from the update.zip you can execute code, would it be possible to use a similar method for extracting files from the system folder?
Thanks
Click to expand...
Click to collapse
Actually there is a potential option... can you get into recovery? And does your recovery have a file manager? If so go into mounts and mount /system. Then use the file manager in recovery and you should be able to access build.prop. copy it to your SD and then you should be able to mount your SD to your computer through recovery.
Edit: when you mount /system make sure you mount the SD as well or you won't be able to copy to it while you're in the recovery file manager.
Sent from my SGH-I897 using xda app-developers app
Hi m1batt1,
The recovery does not have any file mount option
I have lost all hope of being able to get the system to boot.
Thanks the same.
remuscat said:
Hi m1batt1,
The recovery does not have any file mount option
I have lost all hope of being able to get the system to boot.
Thanks the same.
Click to expand...
Click to collapse
You might have to flash stock KK4 at this point and go from there.
What kernel do you have for it not to have a file mount? I believe even stock kernel has it Since you can get in download mode, I would flash a newer kernel if I were you (with Odin) to be able to mount in recovery.
remuscat said:
Hi korockinout13,
I have tried to refresh from a rom i got, but I am prompted an error with Nand version.
The android in question is not common (Subor, a chinese Android Tablet) and have not found any firmware for my particular model except for the one supplied by the supplier, which still does not install.
At this stage reflashing is not an option, so I am looking for something else...
Thanks for your time
Click to expand...
Click to collapse
BWolf56 said:
You might have to flash stock KK4 at this point and go from there.
What kernel do you have for it not to have a file mount? I believe even stock kernel has it Since you can get in download mode, I would flash a newer kernel if I were you (with Odin) to be able to mount in recovery.
Click to expand...
Click to collapse
From what I'm reading he doesn't even have a captivate. He's using some Chinese tablet.
Sent from my SGH-I897 using xda app-developers app

Rooted, trying to reinstall deleted Stock.apk

I had a questions about restoring the deleted Stocks app. I rooted with the new unrevoked last night and then installed Titanium to remove apps. I prematurely removed the Stocks app and I have been trying to get it back since.
I've tried multiple routes, from this Wildefire thread http://forum.xda-developers.com/showthread.php?t=738147 I tried the apk via adb and Root Explorer. Neither worked.
Then I downloaded the stock odexed EVO rom from this thread http://forum.xda-developers.com/showthread.php?t=874251, grabbd the stock.apk and moved it to my \system\apps folder with Root Explorer. I've restarted, tried clearing the Dalvik Cache, pushing it via adb, none have worked.
Right now it's still sitting in the \system\app folder.
I wanted to see if there was anything else I can try to get it back? Or am I doing something wrong?
Thanks in advance.
I take it you are running stock Rom. I think the best way is to make a nandroid of the stock Rom that you are running, with ClockworkMod. Once done download Myn's Rom or sprint lovers. Both of this Rom's have the stock Sprint apps. When flashing the Roms, please, make sure to use Rom Manager and flash ClockworkMod, than flash Amo-ra; is located at the buttom as an alternate recovery. Than once you flash the Rom, let it load, than flash clockworkMod again, than go into recovery, than restore,advance restore, select the newest nandroid, and just restore data. This will give you all the stock apps. OR just try this.
http://forum.xda-developers.com/showthread.php?t=832388
Here are some more apk's.
http://forum.xda-developers.com/showthread.php?t=901393
grab the apk out of the stock rom you have, then in adb do this
adb remount
adb push Stock.apk /system/app
if you need to push the odex do this also
adb push Stock.odex /system/app
the important thing is the remount to make the system/app read write
you can go to the rom file open the file then open system then open app and add the apk you want and reload the rom into the phone that sit more simple
ifly4vamerica said:
grab the apk out of the stock rom you have, then in adb do this
adb remount
adb push Stock.apk /system/app
if you need to push the odex do this also
adb push Stock.odex /system/app
the important thing is the remount to make the system/app read write
Click to expand...
Click to collapse
I did the above while booted in recovery mode with the system mounted. It successfully went in the system/app folder. I see it in Root Explorer, although it still doesn't show up in the apps menu. Oh well.
baker2gs said:
I did the above while booted in recovery mode with the system mounted. It successfully went in the system/app folder. I see it in Root Explorer, although it still doesn't show up in the apps menu. Oh well.
Click to expand...
Click to collapse
Yeah it doesn't work right if you are in recovery because it messes with permissions I heard. Just do it with phone plugged in to computer and on. If that doesn't work you can try deleting the apk and then using
Adb remount
Adb install stock.apk
Don't know if these will work but worth a try. Last resort is find a flashable zip that writes something to system/app and drop the apk in there.
Evo Sent
ifly4vamerica said:
Yeah it doesn't work right if you are in recovery because it messes with permissions I heard. Just do it with phone plugged in to computer and on. If that doesn't work you can try deleting the apk and then using
Adb remount
Adb install stock.apk
Don't know if these will work but worth a try. Last resort is find a flashable zip that writes something to system/app and drop the apk in there.
Evo Sent
Click to expand...
Click to collapse
When I run that command with the phone on charge mode with debugging on plugged into the computer I get a "remount failed: Operation not permitted".
I installed the Sync drivers and tried it with that but it didn't work either.
Any suggestions? Thanks for your help by the way.
baker2gs said:
When I run that command with the phone on charge mode with debugging on plugged into the computer I get a "remount failed: Operation not permitted".
I installed the Sync drivers and tried it with that but it didn't work either.
Any suggestions? Thanks for your help by the way.
Click to expand...
Click to collapse
I can't help with that, never ran in to that problem before, are you nand unlocked and s-off?
ifly4vamerica said:
I can't help with that, never ran in to that problem before, are you nand unlocked and s-off?
Click to expand...
Click to collapse
Yes to both, I have been trying to do research on it. It may be the stock rom...
I tried some workarounds but they didn't work. Thanks for your help.
baker2gs said:
Yes to both, I have been trying to do research on it. It may be the stock rom...
I tried some workarounds but they didn't work. Thanks for your help.
Click to expand...
Click to collapse
No problem, sorry I couldn't help.
Evo Sent
Just an update, I tried the .zip route you suggested. I created a Titanium back up and threw the Stock.apk in the zip. I ran the update.zip in recovery. It placed Stock.apk in the system/app folder but the app still does not appear in the apps menu. Thanks again.

[Q] HELP - no build.prop

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

rom manage recovery problem

I cant go to recovery through Rom Manager for some reason. It works manualy( power+volume) but when I click it from the app it freezes, and shows an exclamation point triangle
have you tried to reinstall the app?
Wich CWM do you have?
thy the above post; if that doesn't work, go into recovery manually and fix permissions
that must be why
I was following this video http://www.youtube.com/watch?v=PVyGw6vycFo
and it said I had to wipe my data which I did, and maybe CWM was removed?
Ill try to flash CWM and see what happens.
Worked! thanks
In wich way?
Have you reinstall Rom manager App or reflah CWM Recovery?
actually, theres been a trend going on here....
I went on recovery to check if its working after I flashed it and it worked, after turning it off and removing the usb out of my computer I tried again and it didnt work.
Any ideas why?
Edit: when I had ROM manager I already tried to Flash CWM there if you're wondering.
Rename /etc/install-recovery.sh to something else with your preferred file explorer with root capability. Now reflash cwm and it will stick. What you are seeing now is stock recovery.
Harbb said:
Rename /etc/install-recovery.sh to something else with your preferred file explorer with root capability. Now reflash cwm and it will stick. What you are seeing now is stock recovery.
Click to expand...
Click to collapse
where can I find /etc/install-recovery.sh and what do you mean by file explorer with root capability?
Root explorer, ES File Explorer or something of the sort. This will let you directly modify files on the /system partition. Just enable root functionality in the settings, allow root when the popup comes up and rename/delete the /system/etc/install-recovery.sh file (this is the correct path, /etc is a link to /system/etc - ignore the other one).
Directories work pretty much the same as windows except it doesn't use "drives" (ie, C:\, D:\, etc), everything is found within the root directory (which is /).
Harbb said:
Root explorer, ES File Explorer or something of the sort. This will let you directly modify files on the /system partition. Just enable root functionality in the settings, allow root when the popup comes up and rename/delete the /system/etc/install-recovery.sh file (this is the correct path, /etc is a link to /system/etc - ignore the other one).
Directories work pretty much the same as windows except it doesn't use "drives" (ie, C:\, D:\, etc), everything is found within the root directory (which is /).
Click to expand...
Click to collapse
fairly new to android so I have no clue what you are talking about sorry... can you give me some steps on how to do that. again I apologize, Im still new
Download this from the market, i'm sure you'll figure it out
quick unrelated question: I tried to apply the ROM and it didnt continue, it said it was aborted or something

[Q] Boot looped Kyocera Torque. Push build.prop in fastboot

I've got myself into quite a predicament. I was trying to install a dictionary for a 4.4 keyboard on my 4.1.2 torque, and in doing so I found that I may want to change the build.prop. Before I even reboot the device I see that that would only work if I were installing through the market, and so I replace the build.prop with an exact copy of the original file. I reboot and then the device will not boot. I guess something must have gone wrong with es explorer. I do not know how to fix the build.prop file because 1. I can't find the file available online yet and 2. this phone has no recovery, so I cannot access it through adb. I can however access it through fastboot when I put it in fastboot mode. This phone also has a download mode I magically got into, but it cancelled itself out after 10 seconds and I don't know how to get back into it or what purpose it would serve.
Does anybody know a way I may be able to push a new build.prop file to my phone? Perhaps I could use the fastboot flash command if I could find the build.prop info? This is my primary phone so any help would be very much appreciated.
Thanks,
Allan
I got the build.prop backup off my sd card, but I still don't know how to push it. Would it be possible to get a copy of the system partition through fastboot, inject the build.prop into it, then reflash? Wouldn't that just be doing the same thing that got me into this mess though?

Categories

Resources