How to replace build.prop on the 1st gen Scroll - NOT Excel

[Warpedflash]

Hi warpedflash, any chance of posting the version of the prop with 160 density? I have tried using LCD Density Changer which is fine until I reboot but then reverts to 140.

Cheers

Glostermeteor

done

[glostermeteor]

Many thanks!

Glostermeteor

[slarti99]

Ahh, is it possible I am the first to muck this simple change up ?

I appear to have a force close loop from LauncherPro after my first and second reboots after the build.prop change.

I can't appear to get out of it. Any advice.

Thanks

[Charlie]

Ahh, is it possible I am the first to muck this simple change up ?

I appear to have a force close loop from LauncherPro after my first and second reboots after the build.prop change.

I can't appear to get out of it. Any advice.

Thanks

Looks like you might have gone wrong, but your not the first. - I take it that 'LauncherPro' is your default home? -

Which of the 3 sets of instructions did you use? - it looks like you have not transferred the new build.prop file over to the scroll properly (did you make any changes to the new build.prop?)

[jasoninertia]

anyone who has issues with the icons being smaller on this build.prop, I overcame that by installing ADW launcher , you can make the icons as big as you like with that , good home replacement, probably the best I have used on android.

[slarti99]

I used the terminal to perform the commands shown below:

Download the build.prop above and copy it to your sd card
Rename the files to build.prop (if different)
Method 1 - Using a File Explorer
Open a file explorer with root permissions Root Explorer is what I use but Super Manager is freely available on the market.
Navigate to your sd card and copy/cut the file.
Navigate to the /system/ folder on your tablet and rename the current version of build.prop to build.prop.old
Paste the new build.prop into the /system/ folder
Reboot your Tablet
And you are done!

No changes made to the new Build.Prop and I checked that the renamings and moves had worked OK.

LauncherPro is the default HOME.

I can't think what's gone wrong other than I have NO build.prop in system now ?

Thanks

[Charlie]

I used the terminal to perform the commands shown below:

Download the build.prop above and copy it to your sd card
Rename the files to build.prop (if different)
Method 1 - Using a File Explorer
Open a file explorer with root permissions Root Explorer is what I use but Super Manager is freely available on the market.
Navigate to your sd card and copy/cut the file.
Navigate to the /system/ folder on your tablet and rename the current version of build.prop to build.prop.old
Paste the new build.prop into the /system/ folder
Reboot your Tablet
And you are done!

No changes made to the new Build.Prop and I checked that the renamings and moves had worked OK.

LauncherPro is the default HOME.

I can't think what's gone wrong other than I have NO build.prop in system now ?

Thanks

What was the name of the File Explorer App you used to do this?

Is does seem that you have not put the new build.prop on the scroll correctly - the way around this is to use warpedflashes update.zip to put it back (you need to have clockworkmod 1st on the scroll) b4 you can use the update.zip or if you are familiar with ADB - you can push the correct file over to the scroll.

[slarti99]

Thanks Charlie.

It was Super Manager but I just remembered that I used the commands below in terminal to finish the process after renaming everything in SuperManager as it couldn't seem to copy and paste the new build.prop into system.

"su"

"cp /sdcard/build.prop /system/build.prop"

My system directory definitely had a build.prop.old and a build.prop in it.

Oh what have I done ?

Thanks

[Charlie]

My system directory definitely had a build.prop.old and a build.prop in it.

Oh what have I done ?

Thanks

If your system directory has the new build.prop in place - it should be working (unless the file is corrupt) maybe its an issue with LauncherPro??? - Sorry I can not be of any more help - Perhaps another user can pitch in and lend a helping hand here.

[Veng]

If you apply update.zip from this forum using maintenance mode or clockwork, it should put the proper build.prop in place.