Database Info

how to edit your build.prop to get things like netflix working

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

[Q] apktool problem

yesterday I Tried to modify my systemui.apk using apktool. Got everything to
work even got it to open but after I reboot the
app is gone. Any ideas? Any help would be
greatly appreciate

did u set permissions correctly ?
try to flash via recovery/ or use adb push command so that no need to set permissions at all
try without signing the file .

[Q] Can't transfer nandroid backup from phone to pc?

Hi, I've just made an Online Nandroid backup of my stock rom. It's stored in the clockworkmod folder located on the internal storage, but whenever i try to copy it from that folder to my PC, it just pastes a folder named "35", which contains no files. I have no idea why it's doing this!
Help please?

B0B0D said:
Hi, I've just made an Online Nandroid backup of my stock rom. It's stored in the clockworkmod folder located on the internal storage, but whenever i try to copy it from that folder to my PC, it just pastes a folder named "35", which contains no files. I have no idea why it's doing this!
Help please?
Click to expand...
Click to collapse
What if you do?
Code:
adb pull /sdcard/clockworkmod

deej_roamer said:
What if you do?
Code:
adb pull /sdcard/clockworkmod
Click to expand...
Click to collapse
I'm having the same problem as the OP. I made a nandroid backup using clockworkmod and I can't figure out how to get it off the Moto G and onto my computer. The above adb command just brings over two files: .recovery_version and .last_install_path.
The nandroid backup does not seem to be placed on the emulated sdcard. I can find it by using the Rom Toolbox root browser. It is in /data/media/clockworkmod/backup.
But that directory is not visible when I connect the phone via usb. I try:
E:\install\Moto G Tools\MotoG-Tools>adb pull /data/media/clockworkmod/backup
and get:
remote object '/data/media/clockworkmod/backup' does not exist
Any ideas on how I can get the backup onto my PC?

Hello guys, proper path should be as below:
adb pull /mnt/shell/emulated/clockworkmod/backup /designated/folder/for/backup/backup.date
JP

just use a file explorer like es and move your backup to somewhere that is visible from your comp and then just copy it over .

quizmaniac said:
just use a file explorer like es and move your backup to somewhere that is visible from your comp and then just copy it over .
Click to expand...
Click to collapse
I tried that. With an 8GB Moto G I'm lucky to have enough space for one copy of the nandroid backup. When I tried to move the directory, it runs out of memory - I guess it is actually copying and deleting. I could try moving each file individually, but that is tedious and error prone and I could still run into the space problem.
---------- Post added at 11:40 PM ---------- Previous post was at 11:27 PM ----------
pacmanman said:
Hello guys, proper path should be as below:
adb pull /mnt/shell/emulated/clockworkmod/backup /designated/folder/for/backup/backup.date
JP
Click to expand...
Click to collapse
Thanks. That worked.

Would u please give proper instruction on how to do it, my nandroid backup seems hidden when I open it on pc

First time when I have a problem like this, I see the backup on phone but when I conect the phone to PC I can't find it. So, I use Total Commander and move the backup file in phone in other folder, like "download". After that I seen it to PC. Now, I use TWRP 2.8.7 and I make the backup to an OTG connected USB stick. It's simple after that to move the backup where I want.

G0rg0ne said:
First time when I have a problem like this, I see the backup on phone but when I conect the phone to PC I can't find it. So, I use Total Commander and move the backup file in phone in other folder, like "download". After that I seen it to PC. Now, I use TWRP 2.8.7 and I make the backup to an OTG connected USB stick. It's simple after that to move the backup where I want.
Click to expand...
Click to collapse
I try ur method, but seems not working either,
Im using philz last version. Installing total commander and
I got this message

You give root rights to Total Commander?

G0rg0ne said:
You give root rights to Total Commander?
Click to expand...
Click to collapse
Yes,
Could it be because the su or the recovery?

I use TWRP, but you must find it in this location: /storage/emulated/0/clockworkmod/backup/backup.date. If you not, you can try the adb command described by
pacmanman said:
Hello guys, proper path should be as below:
adb pull /mnt/shell/emulated/clockworkmod/backup /designated/folder/for/backup/backup.date
JP
Click to expand...
Click to collapse
or, you can try another file manager, like ES or RootExplorer
You know how to use ADB commands?

G0rg0ne said:
I use TWRP, but you must find it in this location: /storage/emulated/0/clockworkmod/backup/backup.date. If you not, you can try the adb command described by
or, you can try another file manager, like ES or RootExplorer
You know how to use ADB commands?
Click to expand...
Click to collapse
Already try that app & didn't work.
I'm trying to use same method as this (using adb) but I can't seem find proper instruction or sample on how to do it - at least easy way
Can u help me give instruction (with capture if u may) or at least pointing me to thread that discuss this.
Thx

First, you may have motorola drivers installed on your PC. You can find them from here.
Another thing you need is Fastboot. Unzip fastboot on your desktop on a folder.
Charge your device above 60% battery level to avoid shutdowns during the process.
Enable USB Debugging on your phone from Settings> Developer options. If you do not find Developer option under device settings, enter to settings/about phone and touch "Build number" 7 times to enable them.
Conect your phone via USB to PC.
Open folder where you have fastboot, right click it and open a comand prompt from there
In the comand prompt enter:
adb devices
now you will see if all is ok and your device has been recognized. You should see something like:
List of devices attached
random numbers and letters device
If not, probably don't have the drivers installed properly OR you failed to authorize your computer for USB debugging.
Now you can enter adb commands in terminal and pull your backup from your phone. Commands will be something like:
adb pull /mnt/shell/emulated/clockworkmod/backup /designated folder for backup/backup.date
You can learn more about Backup with ADB from Here

G0rg0ne said:
First, you may have motorola drivers installed on your PC. You can find them from here.
Another thing you need is Fastboot. Unzip fastboot on your desktop on a folder.
Charge your device above 60% battery level to avoid shutdowns during the process.
Enable USB Debugging on your phone from Settings> Developer options. If you do not find Developer option under device settings, enter to settings/about phone and touch "Build number" 7 times to enable them.
Conect your phone via USB to PC.
Open folder where you have fastboot, right click it and open a comand prompt from there
In the comand prompt enter:
adb devices
now you will see if all is ok and your device has been recognized. You should see something like:
List of devices attached
random numbers and letters device
If not, probably don't have the drivers installed properly OR you failed to authorize your computer for USB debugging.
Now you can enter adb commands in terminal and pull your backup from your phone. Commands will be something like:
adb pull /mnt/shell/emulated/clockworkmod/backup /designated folder for backup/backup.date
You can learn more about Backup with ADB from Here
Click to expand...
Click to collapse
OK, thx u I'll try as soon as I got free time,
One more question, should I connect my phone on recovery or normal condition ?

In "normal" mode , but not forget to enable USB debugging.

G0rg0ne said:
In "normal" mode , but not forget to enable USB debugging.
Click to expand...
Click to collapse
Hello Forgone, I try ur suggestion.
But seems doesn't work, have I did wrong
My phone detected but when I try adb pull, it shows this messages

You not give the right command to pull out. After "...clockworkmod/backup/" you must enter the backup name not the path where to download. It will download to adb folder. The name of backup file could be, how it suggest @pacmanman something like "backup.date" (where date is the date you make it). Sry, but you must find the name of that backup file or at least guess it.

G0rg0ne said:
You not give the right command to pull out. After "...clockworkmod/backup/" you must enter the backup name not the path where to download. It will download to adb folder. The name of backup file could be, how it suggest @pacmanman something like "backup.date" (where date is the date you make it). Sry, but you must find the name of that backup file or at least guess it.
Click to expand...
Click to collapse
Gorgone, if its not to much, can u give screenshot on how u do it?
I'm confused

Look at your picture. As you see in green what you do till here was good. Your device is recognize. Now, what I underlined with yellow was not OK. There you must put your Backup file NAME. The name is usual something like "backup.date" where date means the date you made the backup. It's nothing to do if you don't know that name, so at least try to guess it.
I use TWRP so my path will be a little different. TWRP is better for make and restore backups, you can even make a backup on an USB stick on OTG, so you don't ocupie the internal memory space, also you can easy move it where do you want.

build prop help

i saved original build prop in my pc and and i want pull in my device with adb i do not have any info about this step my device go directly to black screen in firmware update
how i can push my build prop in my lg g3 d850 with pc win 7 64bit
help my

anasmilan said:
i saved original build prop in my pc and and i want pull in my device with adb i do not have any info about this step my device go directly to black screen in firmware update
how i can push my build prop in my lg g3 d850 with pc win 7 64bit
help my
Click to expand...
Click to collapse
Download android sdk, install it as google tells you. Go to the folder your build prop is at, hold shift, press the right mouse button, press on open command prompt. Type this in it:
adb shell
su
stop
mount -o rw, remount /system
push build.prop /system/build.prop
mount -o ro, remount /system
reboot
If you cant do that, you can always reflash the firmware

push not found
Remorcer said:
Download android sdk, install it as google tells you. Go to the folder your build prop is at, hold shift, press the right mouse button, press on open command prompt. Type this in it:
adb shell
su
stop
mount -o rw, remount /system
push build.prop /system/build.prop
mount -o ro, remount /system
reboot
If you cant do that, you can always reflash the firmware
Click to expand...
Click to collapse
i moved the build prop file to platform-tools file in sdk and i try go to command prompt with shift and Type this command
adb shell
su
stop
mount -o rw, remount /system
push build.prop /system/build.prop
tell me push: not found
see the pic
and i try the flash tools with the same tot & dll
the flash tools error
read model is deffrent

I use pushbullet for small stuff like this then just move it and set permissions with root explorer
Sent from my LG-D850 using Tapatalk 2

no android in device
screwyluie said:
I use pushbullet for small stuff like this then just move it and set permissions with root explorer
Sent from my LG-D850 using Tapatalk 2
Click to expand...
Click to collapse
the phone go direct to frimware update how i can use pushbullet in this mode?

anasmilan said:
i moved the build prop file to platform-tools file in sdk and i try go to command prompt with shift and Type this command
adb shell
su
stop
mount -o rw, remount /system
push build.prop /system/build.prop
tell me push: not found
see the pic
and i try the flash tools with the same tot & dll
the flash tools error
read model is deffrent
Click to expand...
Click to collapse
I wrote a script, it should be easier now.
Put build.prop into the Puuuuush folder and run PUSH_BUILD.PROP
EDIT: Sorry, I told you the wrong commands. it should be fixed now with this tool.

Remorcer said:
I wrote a script, it should be easier now.
Put build.prop into the Puuuuush folder and run PUSH_BUILD.PROP
EDIT: Sorry, I told you the wrong commands. it should be fixed now with this tool.
Click to expand...
Click to collapse
Does it work if i can only power on the phone in download mode?
I have my phone soft bricked because of a corrupted build.prop and i need to replace it.

anasmilan said:
the phone go direct to frimware update how i can use pushbullet in this mode?
Click to expand...
Click to collapse
my bad, I thought you were just looking to transfer the file
unless I've missed something you can't do ADB in recovery or download mode. which has always seemed stupid to me.
you'll need to use ODIN to flash the rom again

screwyluie said:
my bad, I thought you were just looking to transfer the file
unless I've missed something you can't do ADB in recovery or download mode. which has always seemed stupid to me.
you'll need to use ODIN to flash the rom again
Click to expand...
Click to collapse
ODIN is for samsung phones.
After I modified the build.prop file I forgot to change the file rights and now it is stuck on a black screen with the led on green/blue
I have a backup of the original file on the SD.
The phone can get into download mode.
I have already tried the factory reset but nothing.
I have tried the unroot metod from the post:
http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827
But I got this message:
PID: BS02S140706002625
IMEI:
Model: D850
DLL: D850
BIN: LGD850AT-01-V10D-310-410-JUN-19-2014+0
SWV: LGD850AT-00-V10D-310-410-JUN-19-2014+0
SWOV: LGD850AT-00-V10D-ATT-US-JUN-19-2014+0
Device Model is different!
Check Phone or DLL!
My phone model is the AT&T LG G3 32Gb D850 Metalic Black
Please, can someone helpme?
I am desperate!

Sorry I'm a Samsung guy, lg tool or whatever it is.
There is a file from the g2 that makes it so the model doesn't matter you'll need that
Sent from my LG-D850 using Tapatalk 2

http://forum.xda-developers.com/showthread.php?t=2827381
You mean this file

Same thng happened to me
Ok i edited the build.prop, apparently I did something wrong, I can only boot to black screen with blue/green flashing led. I did back up my original build.prop, and I can get phone into download mode....just not sure what to do from here. I am using a mac, but I can get to a PC if needed. Any help would be GREATLY appreciated.

DIRKxxxDIGGLER said:
Ok i edited the build.prop, apparently I did something wrong, I can only boot to black screen with blue/green flashing led. I did back up my original build.prop, and I can get phone into download mode....just not sure what to do from here. I am using a mac, but I can get to a PC if needed. Any help would be GREATLY appreciated.
Click to expand...
Click to collapse
I'm really desperate, anyone that can help me get my phone back up I would really appreciate it....just get it back to stock or anything. I am willing to donate to anyone that can help me get my phone up. I know I'll get ripped apart for messing with my phone that was above my ability, I have learned my lesson I understand, just need help please. Thanks for anyone that can get me back up.

DIRKxxxDIGGLER said:
I'm really desperate, anyone that can help me get my phone back up I would really appreciate it....just get it back to stock or anything. I am willing to donate to anyone that can help me get my phone up. I know I'll get ripped apart for messing with my phone that was above my ability, I have learned my lesson I understand, just need help please. Thanks for anyone that can get me back up.
Click to expand...
Click to collapse
Woot! got it fixed!

How did you end up fixing it?
Sent from my LG-D850 using XDA Free mobile app

Quick way of accessing screen to broken devices.

Hi,
So my screen broke yesterday and I needed to check my phone for missed important calls. I know there is lots of solutions out there, but I needed a way access your screen without the installation of any software on your phone. I was lucky because my digitizer still works so I can still use the touch feature and figure out on my screen where to press . I figured i would post it, might save someone someday....
Note: Works on Android 4.0 +
You need to have have developper options enabled so this can work. So first of all, I need to enable ADB from recovery. There is lots of post on the forum and google, so I will not cover this part.
Once I had ADB enabled, I wrote a small batch file that would take a screenshot from my phone, then pull it to my pc, wait 1 sec, then restart. After I used chrome and a auto-refresh extension to refresh the image every second. I will assume that you have ADB installed and all drivers for adb working. Here it goes
1. You will need to create a batch file. Open notepad and paste this into it.
Code:
:start
adb shell screencap -p /sdcard/screen.png
adb pull /sdcard/screen.png
timeout 1
goto start
Save it as ss.txt, or whatever you like. Then go to desktop and rename ss.bat or "whatever you like.bat"
This may vary a bit if you do not have an SDcard, or if your directory is not named the same way, So change SDcard to the name of your storage folder.
Copy it to your adb directory.
2. Open a Command Prompt as Admin change directories to ADB folder. Once you are there, just type ss and the batch should start.
3. Open chrome and install an auto-refresh extension. I used this one:
HTML:
https://chrome.google.com/webstore/detail/easy-auto-refresh/aabcgdmkeabbnleenpncegpcngjpnjkc?hl=en
4.Then open your c:\ drive in chrome (type in the address bar file:///C: ). Navigate to your adb folder and open screen.png.
5. Start auto refresh on screen.png opened in chrome and set to 1 second.
Now you will have a screenshot of your phone being refreshed every second! I agree its slow, but its an easy way to get on your phone and configure other applications such as vnc or other stuff or just to get the phone number of that hot date you had last night.
Other thoughts: I your digitizer is broken, you can always just get a USB on the go adapter and plug-in a mouse and use ADB over wifi.
I guess you can also use an usb micro to hdmi adapter and plug it in to a monitor, they have them at bestbuy for 20$ if you dont want to make your life complicated.
Have Fun!

Need busybox do you not? screencap is not in my /system/xbin nor /system/bin folder

kirito9 said:
Need busybox do you not? screencap is not in my /system/xbin nor /system/bin folder
Click to expand...
Click to collapse
What phone and what rom are you using? What I read is that some vendors do not include screencap in their stock rom. ..

Steph_D said:
What phone and what rom are you using? What I read is that some vendors do not include screencap in their stock rom. ..
Click to expand...
Click to collapse
Using Blu Dash Jr D140a, stock ROM ( Gingerbread 2.3.6)

kirito9 said:
Using Blu Dash Jr D140a, stock ROM ( Gingerbread 2.3.6)
Click to expand...
Click to collapse
Should of mentionned, dosen't work with gingerbread, you need 4.0+ if i recall correctly. Maybe, if your lucky, the manufacturer may have included their version instead of screencap since it did not exist back, i would take a look in the bin folder to try to find an equivalent if not you are out of luck with this method.

Steph_D said:
Should of mentionned, dosen't work with gingerbread, you need 4.0+ if i recall correctly. Maybe, if your lucky, the manufacturer may have included their version instead of screencap since it did not exist back, i would take a look in the bin folder to try to find an equivalent if not you are out of luck with this method.
Click to expand...
Click to collapse
OP should be updated then and here's my bin folder.

kirito9 said:
OP should be updated then and here's my bin folder.
Click to expand...
Click to collapse
Ya, I don't believe it will be possible for you using this method. :/ Sorry Will update original post...

Steph_D said:
Ya, I don't believe it will be possible for you using this method. :/ Sorry Will update original post...
Click to expand...
Click to collapse
No problem, I will try on my 4.2.2 device.
EDIT: It works bro. Nice little guide of doing it manually