(I'm new at this, any help would be appreciated)
I'm using Daneshm90's (very awesome) APK Manager to mess around with my framework-res.apk file. I've sucessfully reskinned some pngs and changed some xml files and stuff like that.
Why does the following cause a bootloop?
1) Decompile Framework-res.apk
2) Make a copy of res\drawable\btn_default_small.xml and rename it btn_default_small2.xml
3) Change the background of something to android:background="[a]drawable/btn_default_small2"
4) Compile\flash to phone etc, watch it bootloop
(please note: [a] is really the email 'at' symbol, the forums get mad at me for using it)
I can edit existing files just fine, but whenever I try to add and use a new file everything grinds to a halt, even if its just a copy of a working 'stock' file. What am I missing? Is there a list of files somewhere I need to add my new xml file to? Should I be building from source instead of using apk manager?
I have two phones, a Huawei m860 and an m835. They are both basically the same phone, except the m835 has a smaller screen.
I have a CM 7.1 ROM that runs great on the m860 with the larger screen, but is out of scale on the m835 with the smaller screen.
I edited the BUILD.PROP file and changed the LCD.SCREEN.DENSITY from 160 to 120. But when I inject the edited file back into the zip file, ROM Manager says the ROM is bad and refuses to flash it.
Anyone know how to properly recompile the ROM with the edited BUILD.PROP file, so that I can flash it?
You can use an app to change the screen density.
Can you elaborate a little? What app?
1. You can use LCDDensity
2. Or if you don't want to have an app running in the background, you can simply install ES File Explorer and (as you know) go to /system/build.prop and change the density and reboot. This is permanent or until you change it back or flashing the/a ROM again.
Thanks, I was able to edit the /system/build.prop file after flashing the ROM, and that did the trick once I rebooted.
Now though, I've discovered that the screen does not change orientations when I turn the phone as it should. Any have any ideas how to fix that?
-TheGE128
Hi,
I have an xperia sola with build .54. I did everything according to the instructions (http://forum.xda-developers.com/showthread.php?t=1417375) to make init.d scripts work on closed bootloaders also. I wrote one for myself also:
#!/system/bin/sh
echo "0,0,6144,0,14336,18432" > /sys/module/lowmemorykiller/parameters/minfree
But unfortunately it does not work. If I run it in terminal the value changes, but it reverts after restarting.
Sorry, for my bad english.
Hey mate,
First, check if init.d support was added correctly. Paste this in init.d with 777 permission, then restart phone, Go to/data/local/tmp/ and see if init.d_log_test.txt exists
If it does, then its an issue with script,else init.d Issue Report back and we'll look into your problem
Cheers
There it is. So, the init.d is working.
Which editor did you use to make the file ? And you did set the right permissions, no ?
I'm use notepad++, and the permission: rwxrwxrwx
Ok.. hm.. next thing, Click the "Show All Characters" option in notepad++. It looks like a "P' button.. See if the end of each line says LF or CR-LF
I see LF
Then I cant see any issues Can you send me the file ? Might be a typo or something missed out when you copy-pasted
Here: http://d-h.st/3Sk
Edit: I tried to edit init.rc. I added this line:
write /sys/module/lowmemorykiller/parameters/minfree 0,0,6144,0,14336,18432
but it doesn't work
Sorry my english.
Still couldnt find an issue Just to be sure its not an init.d issue,can you delete that file in data/local/... and reboot to see if its made again ? Maybe init.d support got broken somewhere in between
I delete the file, but it's recreated. I tried to change the sys/module/mali/parametrs/mali_mem file, and it was succeeded. It's let to change either files, but the minefree not.
Good day!
Hi!
I had my Sony Ericson W8 E16i (Android 2.1 Update-1) obtained from an old box...
I decided to upgrade it to Android 2.3.7 via custom rom (thru the help of GingerDX)...
Everything's fine.
Now, I can't edit the "build.prop"...
I want to edit the phone model from "X8" to "W8"...
And also, to edit and delete some lines...
But it always reverts back to the original build.prop of that custom rom every after reboot...
Here's the actions I've already done:
1. Copy build.prop on sdcard. Edit it the way i wanted. Move it to root directory then fix the permission. Then move to /system to replace the existing build.prop. After reboot, it reverts.
2. I created a flashable zip of the editted build.prop, after system boot, nothing has changed.
3. I edit the build.prop directly to /system directory then save it. (It creates .bak file for its backup after I save.) After reboot, it reverts back again to the original build.prop of the custom rom.
Additional info.:
The "GingerDX v031b" is a CM7-based rom.
Any other info should I be provided?
Please help.
I treid to edit this file to get better video/photo/audio quality a while back but when I did edit it and rebooted I was stuck in a boot loop.
I want to give it a go again but do not want to end up in a boot loop again if I can help it.
Is there settings I should not edit or permissions I need to set etc to stop a boot loop? What causes the bootloop in the first place? I would of thought that editing this file would stop the camera from working and not the whole phone but hey what do i know
Can anyone provide some insight?
Cheers
most likely permission error
permission should be rw-r-r (read,write for root, read for group, read for global) or 644 depending on what you are used to
anyway, before you make changes, backup system in TWRP then do your stuff
in case something went wrong, simply restore system and no probs