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
how to unbrick MID tablet after changing framework-res.apk file
Is there any way to unbrick my tablet im stuck in bootanimation of it i could not push my backup through ADB coz my debugging is not enabled and i could put the right driver for its to push a fil;e using ADb command ,I could not boot to recovery coz its bootloader is also locked is there an way of file maybe that could put my tablet back to stock or something or bring it back, or maybe a file to enable debugging mode or just a zip file to bring back my framework to its place using may external sdcard ....My device name is now gt-n7000 i change its build.prop its version is 4.0.4
please guys help me out to solve this mess i did ==Advance thanks to replies:good::crying:
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?
I've got myself into quite a predicament. I replaced the build.prop on my kyocera torque with what should have been an exact copy of the original. However, now the phone 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 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 but I don't know if that's helpful.
Does anybody know a way I may be able to push a new build.prop file to my phone? Or a way that I could access the file system on the phone to build a system image from my system file with the correct build.prop? Or could someone just send me a system.img? This is my primary phone so any help would be very much appreciated.
Thanks,
Allan
I have a rooted micromax canvas a76 phone and I have deleted build.prop file while exploring with ES FILE MANAGER. Now the boot animation just keeps on looping nothing else.need help...!!
Hi, thank you for using XDA Assist. You'll either have to find a working copy of build.prop or re-flash your OS to restore it. Unfortunately there is not a dedicated forum on XDA for your device so finding someone with a working copy of build.prop is going to be difficult. There's also not much help on returning your device to stock on XDA. you could try searchinh here, http://forum.xda-developers.com/android/general
Just a word of advice, if you don't know how to return your device to stock do not root it and mess with things.