• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Set my density too high, how to fix? (C'mon, really need help)

The mod I made is made for CWR, that's probably why you are getting the error message.

The easiest way would be to just adb push it to your phone.
 
Can you make an update.zip for the standard recovery menu? Also, in order to push the file I need to remount system to r/w which I think requires root.
 
Giggybyte said:
Can you make an update.zip for the standard recovery menu? Also, in order to push the file I need to remount system to r/w which I think requires root.
Click to expand...

I'm assuming you have the android-sdk installed and setup as well as your phone drivers.


1. Make sure your phone has USB Debugging turned on.

2. Just go to the tools folder (most likely "platform-tools" or "tools" folder in your android-sdk directory). Put the build.prop file you want to push to your phone in that folder (should be the same folder where your adb.exe file is located).

3. Plug your phone in and let it connect to your PC.

4. Once connected open up a command prompt and cd yourself to the directory where your adb.exe and build.prop are located......mine for example is C:\android-sdk-windows\platform-tools

5. Once you are there at the command prompt type:

adb remount <------This command makes your phone Read/Writable
adb push build.prop /system/build.prop <------This pushes the new build.prop to your phone.

6. That's it, your new build.prop should be pushed to your phone, now just reboot for it to take effect.
 
bouchigo, his problem is that he can't click "allow" on the Superuser dialog, so he doesn't really have root access on the phone.

Giggybyte said:
Can you make an update.zip for the standard recovery menu? Also, in order to push the file I need to remount system to r/w which I think requires root.
Click to expand...

Nobody can make an update.zip for the standard recovery. The standard recovery requires .zip files to be signed with Motorola's private key.

Frankly, without root access for any of your apps, I don't know how you can edit that build.prop in any way. You may have to SBF.
 
in the android overclock app , goto extras, build properties, and there you'll find the sliders to change the density.

simple reboot and you're done.

SMS
 
esemes said:
in the android overclock app , goto extras, build properties, and there you'll find the sliders to change the density.

simple reboot and you're done.

SMS
Click to expand...
That probably requires root access, and as such I can't click on Allow when Superuser pops up.

Idea:
I rooted with SuperOneClick with psneuter. At one point it pushes Superuser.apk which is found in the folder "root" when extracting SuperOneClick. Maybe I can add the build.prop to "root" and somehow edit the psneuter code to push the build.prop as well.
 
Giggybyte said:
That probably requires root access, and as such I can't click on Allow when Superuser pops up.

Idea:
I rooted with SuperOneClick with psneuter. At one point it pushes Superuser.apk which is found in the folder "root" when extracting SuperOneClick. Maybe I can add the build.prop to "root" and somehow edit the psneuter code to push the build.prop as well.
Click to expand...


my bad. yes, you do need to be rooted to use this program (not sure if the whole program/features require root access tho)
 
I FIXED IT GUYS!

What I did:
1. Did a factory reset on the phone.
2. Using SuperOneClick, I did a Shell Root instead of a normal root. This way I can freely use the adb commands and such.
3. I adb pushed the build.prop to /system/build.prop.
4. ????
5. PROFIT!
 
Oh, I didn't realize you weren't rooted, I must have selective reading :p

But, I figured adb would get it done for you in the end.

Glad it worked out for you ;)
 
bouchigo said:
Oh, I didn't realize you weren't rooted, I must have selective reading :p

But, I figured adb would get it done for you the end.

Glad it worked out for you ;)
Click to expand...

I actually was rooted, but I did a *shell* root, meaning I can run adb commands and such without the Superuser dialog popping up. Thing that sucks though, I don't remember many of the apps I had installed.
 
Giggybyte said:
I actually was rooted, but I did a *shell* root, meaning I can run adb commands and such without the Superuser dialog popping up. Thing that sucks though, I don't remember many of the apps I had installed.
Click to expand...

Well if you were rooted then you should have been able to do the steps I pointed out in my earlier post, you don't need any prompts to pop up for you to accept like when you run an app requiring root for the first time.

If you didn't have USB debugging turned on and you couldn't get to it to turn it on because of your messed up resolution then that makes sense.

Side note:
Titanium backup, you should really think about purchasing this app :D
 
bouchigo said:
Well if you were rooted then you should have been able to do the steps I pointed out in my earlier post, you don't need any prompts to pop up for you to accept like when you run an app requiring root for the first time.

If you didn't have USB debugging turned on and you couldn't get to it to turn it on because of your messed up resolution then that makes sense.

Side note:
Titanium backup, you should really think about purchasing this app :D
Click to expand...
Yeah, I'm gonna download the free version.
 
Giggybyte said:
Density is currently at 480 :/

I can use Root Explorer to edit the build.prop file, but due to my screen resolution I cannot click allow when the Superuser window pops up.

I dun goofed, is there a workaround to give Root Explorer access?
Click to expand...

i have the same problem pleas help me
 
You must log in or register to reply here.
Back
Top Bottom