• 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)

Giggybyte

Giggybyte

Newbie
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?
 
Yup, 480 isn't a good number.

Did you create a backup in recovery that you can restore?

Have you tried landscape mode (phone sideways)?

O/W, can you open the Superuser app itself and try different settings?

You might try changing the "notification type" to "notification" to see if that helps.
 
Try this: Open Rom Manager, go to download rom, then to Beesley's build props.

There's a 200 and 220 DPI there you can download. If you can't flash them from RM, you should be able to boot into recovery (if you'd done that before) and flash the file from the clockworkmod/download folder.
 
None of your suggestions worked...
I DO however, have the original build.prop on my computer, I can't adb push it to the phone, but could I put in an update.zip and then boot my phone in recovery mode?
 
Giggybyte said:
None of your suggestions worked...
I DO however, have the original build.prop on my computer, I can't adb push it to the phone, but could I put in an update.zip and then boot my phone in recovery mode?
Click to expand...

Why can't you adb push it to your phone?

Might be easier to troubleshoot adb than to build an update.zip.
 
binary visions said:
Why can't you adb push it to your phone?

Might be easier to troubleshoot adb than to build an update.zip.
Click to expand...

Well I need root access so I can remount /system to r/w, which I cannot do because the Superuser prompt is too big for me to click Allow.

Also, just realized something. My phone is a MILESTONE X, instead of a DROID X.
Apparently they're the same thing but the Milestone X is for smaller carriers.

Gonna be a lot harder to find a Milestone X ROM.

I feel stupid.
 
Gotcha.

Building an update.zip doesn't appear to be too hard, but it does require you to sign it. I tried doing this a while back but actually never got it to work right and didn't put much time into it. However, what was failing for me was not the signature verification part, something was flaking out in the somewhat-complex update.zip I was putting together. In retrospect, I should have tried a simple one first, before attempting what I was screwing around with.

Check this link:
How to Create Android Update Zip Package | All About Web & Mobile Application Development
 
binary visions said:
Gotcha.

Building an update.zip doesn't appear to be too hard, but it does require you to sign it. I tried doing this a while back but actually never got it to work right and didn't put much time into it. However, what was failing for me was not the signature verification part, something was flaking out in the somewhat-complex update.zip I was putting together. In retrospect, I should have tried a simple one first, before attempting what I was screwing around with.

Check this link:
How to Create Android Update Zip Package | All About Web & Mobile Application Development
Click to expand...
Thanks. Apparently I had used an old/non-working method to sign my ZIP.
I will try this once my phone has enough charge to boot.
 
update.zip didn't work, same issue with the verification

I hate to make any of you guys do work, but could any of you try verifying it yourselves? I'm new to rooting and all, so I may have done something wrong.

The update.zip I want to use is a few posts above.
 
Giggybyte said:
update.zip didn't work, same issue with the verification

I hate to make any of you guys do work, but could any of you try verifying it yourselves? I'm new to rooting and all, so I may have done something wrong.

The update.zip I want to use is a few posts above.
Click to expand...

That link is broken, just thought I'd let you know ;)
 
It doesn't look like your update.zip is signed. Also it looks like you are setting permissions for the "app" folder in /system instead of the build.prop.

Try this, it worked on my X with my build.prop of course ;) (this uploaded file has your Milestone X build.prop in it).

Let us know how it goes.

update_build_prop_MX.zip
 
bouchigo said:
It doesn't look like your update.zip is signed. Also it looks like you are setting permissions for the "app" folder in /system instead of the build.prop.

Try this, it worked on my X with my build.prop of course ;) (this uploaded file has your Milestone X build.prop in it).

Let us know how it goes.

update_build_prop_MX.zip
Click to expand...

Instead of the verification error I get:
"E:failed to verily whole-file signature"
"E:signature verification failed"
Installation aborted.

EDIT:
On the fourth try I get "E:Can't open /cache/recovery/command"
 
Giggybyte said:
Instead of the verification error I get:
"E:failed to verily whole-file signature"
"E:signature verification failed"
Installation aborted.

EDIT:
On the fourth try I get "E:Can't open /cache/recovery/command"
Click to expand...


Are you using CWR to apply the file?

The milestone might require different method/signing than the X does. Do you have a mod zip for the milestone (a known working one) that we can examine?
 
bouchigo said:
Are you using CWR to apply the file?

The milestone might require different method/signing than the X does. Do you have a mod zip for the milestone (a known working one) that we can examine?
Click to expand...

No. I'm using the one that comes with the phone.

I don't have a mod zip for android other than the update.zip I made.
 
You must log in or register to reply here.
Back
Top Bottom