Develop Bugs

(THEME-V=2.0)CM 4.0.4 and 4.1.8 Windows Vista (fast & stable)

Yes another vista theme.. no more lag or slow themes... if u know me i only create fast themes. The boot image and the notification are part of my next theme radiant(w/ all colors).
I promise you guys this is very stable no more .9 problems. Please try and donation would be nice.
http://www.megaupload.com/?d=KWPQTW2D
Vista 2.0
*Change the brightness of the clock widget so that the dials are show able
*Removed lock screen
*removed highlights on the background so just touch them and the app will show up
AFTER 1.5 HOURS OF TRAIL AND ERROR LEADS TO THIS ....
http://www.megaupload.com/?d=GJVUL8XK
v1.5 CM 4.1.8
*Updates to the previous version of my windows theme
Please tell me what can be changed
Donate...

apps menu
Is there a way to get the the windows apps menu without flashing the whole theme?

blink200 said:
Is there a way to get the the windows apps menu without flashing the whole theme?
Click to expand...
Click to collapse
yeup, open the theme and navigate to /system/app and push it with adb to /system/app.
You should also be able to use the terminal. Copy it to your sdcard and open terminal
Code:
su
mount -o rw,remount /dev/block/mtdblock3 /system
cp /system/app/Launcher.apk Launcherold.apk
rm -r /system/app/Launcher.*
cp /sdcard/Launcher.apk /system/app
reboot
if for whatever reason that causes problems reflash your rom or boot in to the recovery console and type
Code:
mount -o rw,remount /dev/block/mtdblock3 /system
cp /system/app/Launcherold.apk Launcher.apk
reboot

for some reason, im haveing problems trying to get it to work, anything else i can do?

just tried to boot it up... its stuck at loading screen and loading graphics keep on flashing... nothing is done.
Users be careful when installing this theme... If it does lock your phone to the boot screen. Simply take out your micro sd card then and put it in a SD Card adapter and remove the theme, and copy a working one back on and then rename it update.zip and reboot your phone to reflash it.

can you port to 4.01.1.1 or whatever cy's newest experimental is??

Change G1 Boot Animation without abd

I do most of my hacking from work. I am uncomfortable installing drivers for adb and such on a PC that i am not admin.
So I tried
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/bootanimation.zip /system/media/
reboot
Did not work....
Anyone know if it this possible?

After reading a little more i can see that this will never work for me and my ROM (I'm a donut)
So yea... anyone know if anything like this is possible in a donut build?

not like the animations from eclair . as far as i have been able to find this is only a eclair thing.

ekeefe41 said:
I do most of my hacking from work. I am uncomfortable installing drivers for adb and such on a PC that i am not admin.
So I tried
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/bootanimation.zip /system/media/
reboot
Did not work....
Anyone know if it this possible?
Click to expand...
Click to collapse
adb push boot1.gif /system/media/bootscreen/
adb push boot2.gif /system/media/bootscreen/
adb push boot_animation.xml /system/media/bootscreen/
adb push boot_bg.gif /system/media/bootscreen/
adb push boot_bg.mp3 /system/media/bootscreen/
unzip the file

xile6 said:
adb push boot1.gif /system/media/bootscreen/
adb push boot2.gif /system/media/bootscreen/
adb push boot_animation.xml /system/media/bootscreen/
adb push boot_bg.gif /system/media/bootscreen/
adb push boot_bg.mp3 /system/media/bootscreen/
unzip the file
Click to expand...
Click to collapse
First of all, if you even read his request, he wants to know how to do it via terminal since he doesn't want to install adb drivers on his computer and I'm pretty sure .gif boots won't work on a cupcake/donut/eclair/ ROM unless they are a HTC SENSE ROM. Please read before posting some BS.

Dude you should just flash via Recovery.

ekeefe41 said:
I do most of my hacking from work. I am uncomfortable installing drivers for adb and such on a PC that i am not admin.
So I tried
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/bootanimation.zip /system/media/
reboot
Did not work....
Anyone know if it this possible?
Click to expand...
Click to collapse
try
cat /sdcard/bootanimation.zip > /system/media/

Macrophage001 said:
try
cat /sdcard/bootanimation.zip > /system/media/
Click to expand...
Click to collapse
Not gonna work, 1) What the hack are you trying to do with that command and 2) He's on Donut, he needs eclair

Damn My eyes are terrible.
note to self:
READ BEFORE WRITE!!!!

on google donut builds, you're stuck with the android-logo-mask and android-logo-shine boot animations. on hero builds, you can use the animated gifs. on eclair builds, you can do the bootanimation zips. if you want to know how to do a standard google build boot animation without using adb, check the link in my signature. i made a full written + video tutorial on how to do it.
the other easy way to do it, is of course, metamorph. making the .thm files takes about 30 seconds and you can flash it without having to use adb, terminal OR recovery.

So how did Cyanogen make a custom boot animation for CyanogenMod?

exactly in the fashion shown in my video tutorial. its not hard.
CM=google build.

your signature
kusotare said:
exactly in the fashion shown in my video tutorial. its not hard.
CM=google build.
Click to expand...
Click to collapse
Dude I love your sig...its tight how you got everything you are running in the form of a link, so people who want the same can easily learn how to do it without asking questions(which they still will do anyway) by simply clicking your links.
thats what I call community contribution.

heh, thanks, i havent updated the links in a LONG damn time though, as you can see. I'm obviously not running CM 4.2.3.1 anymore.

Kudos for the Vibrant!
Gotta love that 4.0 amoled screen dislplay.
and I love how Klyentel has his "G1-BRICKED!"
in his signature, too funny.

ekeefe41 said:
I do most of my hacking from work. I am uncomfortable installing drivers for adb and such on a PC that i am not admin.
So I tried
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/bootanimation.zip /system/media/
reboot
Did not work....
Anyone know if it this possible?
Click to expand...
Click to collapse
yeah it is possible i do it all the time download terminal emulator form the market and enter the following commands
su
# cp /sdcard/bootanimation.zip /data/local/
# reboot
it works for me all the time

[GUIDE] Update CM without losing custom /system changes (ex Swype, keymap)

There's a really simple way to prevent CyanogenMod from overwriting your custom /system changes during an update. Create the file '/system/etc/custom_backup_list.txt' with a list of files within /system that you don't want to be overwritten.
For example, to prevent CM from wiping out Swype, open adb shell and type this:
Code:
mount -o remount,rw /system
cd /system/etc
echo lib/libSwypeCore.so >custom_backup_list.txt
echo app/Swype.apk >>custom_backup_list.txt
cd /
mount -o remount,ro /system
If you use teferi's custom keymap, do this:
Code:
mount -o remount,rw /system
cd /system/etc
echo lib/libSwypeCore.so >custom_backup_list.txt
echo app/Swype.apk >>custom_backup_list.txt
echo usr/keylayout/vision-keypad.kl >>custom_backup_list.txt
echo usr/keychars/vision-keypad.kcm.bin >>custom_backup_list.txt
cd /
mount -o remount,ro /system
Then the next time you flash CM, your changes to /system will still be there. If you want to see why this works, take a look at /system/bin/backuptool.sh
Hope this helps

Thanks! This is great; now I can easily keep my Email.apk that doesn't require me to enter a alphanumeric password every time I want to use the phone.

CM probably needs to overwrite build.prop but I've been changing the LCD density in this file. Is there a way to use a seperate file to override the lcd density so that i can let CM overwrite build.prop but still maintain lcd density after a flash?

Whatever commands you put in /data/local/userinit.sh will run at boot. So in adb shell, type this for a density of 215:
Code:
cd /data/local
echo setprop qemu.sf.lcd_density 215 >userinit.sh

awesome! thank you!
Don't suppose you would know how to get the CM update to not install/auto delete after installation apks like ADWLauncher and wifi calling?

Thank you!
This may be the long lost solution to my Swype and Cyan Problems. The new Release Candidates are destroying my swype and not liking it's return after installing the new Cyan. So, if this can basically help me update without losing much, it's a god send. Especially the LCD density.
You're a genius.
Thank you.
Hmm, seems the issue is still persistent. Thanks though.

Should userinit.sh and custom_backup_list.txt survive the upgrade or should they both be included in the backup list file?
Sent from my HTC Vision using XDA App

If you look at the actual script, it seems that it ignores the backuptool if .installscript exists, and in practice, I've noticed that nothing gets saved when flashing via ROM Manager. Is this, in fact, what's happening, and is there a way around it?

sundar2012 said:
awesome! thank you!
Don't suppose you would know how to get the CM update to not install/auto delete after installation apks like ADWLauncher and wifi calling?
Click to expand...
Click to collapse
You can put the following in /data/local/userinit.sh:
mount -o rw,remount /system
for apk in ADWLauncher.apk MS-HTCVISION-KNT20-02.apk
do
rm -f /system/app/$apk
done
for package in com.android.launcher
do
pm uninstall $package
done
mount -o ro,remount /system
exit 0
Click to expand...
Click to collapse
I haven't tried this for removing the Wifi Calling app, so ymmv. I remove a much larger set of apps myself (facebook, email, live wallpapers, amazon mp3 store, DSPManager, FileManager, Browser). http://wiki.cyanogenmod.com/index.php?title=Barebones has a list of apps that can be removed safely.

@cparekh -- what e-mail app is that? Or did you just use the pre-OTA's Email.apk app?

Rc4 has the trackpad wake fm radio and speaker led fixed its workng very smooth better than rc3
Sent from my HTC Vision using XDA App

sundar2012 said:
awesome! thank you!
Don't suppose you would know how to get the CM update to not install/auto delete after installation apks like ADWLauncher and wifi calling?
Click to expand...
Click to collapse
Just delete them from the cmupdate.zip before flashing. Cwm recovery doesn't require sig so u don't have to worry about resigning it.
OP: nice find, I'm sure ill use it at some point.

This is driving me crazy because I know I have used this command before but i cannot get it to work now... What is the deal?
Code:
$ mount -o remount,rw /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Rooted using gfree on this phone. On my previous phone I used wpthis and did not have a problem. Anyone know what I need to do to mount rw?

cparekh said:
Thanks! This is great; now I can easily keep my Email.apk that doesn't require me to enter a alphanumeric password every time I want to use the phone.
Click to expand...
Click to collapse
I need that apk
Sent from my HTC Vision using XDA App

Used this method to when going from stock to CM 6.1.1 and could not get it to work. I had to push/install manually from ADB.
Anyone had any luck? I did what the OP said then flashed. Was I supposed to do anything after flashing wiping and then flashing (CM & gapps)?

rraxda said:
This is driving me crazy because I know I have used this command before but i cannot get it to work now... What is the deal?
Code:
$ mount -o remount,rw /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Rooted using gfree on this phone. On my previous phone I used wpthis and did not have a problem. Anyone know what I need to do to mount rw?
Click to expand...
Click to collapse
Make sure you have root in the shell by typing su.

cparekh said:
Thanks! This is great; now I can easily keep my Email.apk that doesn't require me to enter a alphanumeric password every time I want to use the phone.
Click to expand...
Click to collapse
IConrad01 said:
@cparekh -- what e-mail app is that? Or did you just use the pre-OTA's Email.apk app?
Click to expand...
Click to collapse
chubb16 said:
I need that apk
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I am also interested in that apk

How can I backup progress on Angry Birds? Drives me nuts starting back over when I reflash CM

Titanium backup. You can use it to restore the app and the data. Usually i just restore the data to a fresh install.

Screen calibration config

I'd like to know where are stored the parameters of the screen calibration.
I ask this because at every reboot they reset to factory default so I want to mod it directly.
Kisses to all

seems to be stored in
Code:
/data/data/org.isageek.dasbrennen.CalibrateScreen/databases/calvalues
which is a sqlite database (which I know nothing about!)
You could try making a copy of it before and after rebooting and see if it changes (binary diff). If it does, maybe you could replace it on every boot in your userinit .sh
If not, maybe the CalibrateScreen app just needs to be started to load the custom values, but you could probably do that on startup too.

mmec2 said:
seems to be stored in
Code:
/data/data/org.isageek.dasbrennen.CalibrateScreen/databases/calvalues
which is a sqlite database (which I know nothing about!)
You could try making a copy of it before and after rebooting and see if it changes (binary diff). If it does, maybe you could replace it on every boot in your userinit .sh
If not, maybe the CalibrateScreen app just needs to be started to load the custom values, but you could probably do that on startup too.
Click to expand...
Click to collapse
Thank you very much for your reply, however I was trying to figure out the place where these values are stored into android system and not into the app... because I think that the app it's only a bridge for the real calibration of the system... or maybe I'm wrong?

TuoNonno said:
Thank you very much for your reply, however I was trying to figure out the place where these values are stored into android system and not into the app... because I think that the app it's only a bridge for the real calibration of the system... or maybe I'm wrong?
Click to expand...
Click to collapse
For some reason, I assumed it was a built in part of the system, but it's not!
Anyway, your question has got me interested now, so I took CalibrateScreen.apk from Scoot's CM6.1 build, decompiled the apk with apktool and searched the source for "write"
I believe the values you are looking for are
Code:
/sys/class/vogue_ts/xmin
/sys/class/vogue_ts/xmax
/sys/class/vogue_ts/ymin
/sys/class/vogue_ts/ymax
(found in CalibrateScreen/smali/org/isageek/dasbrennen/CalibrateScreen/Calibrator.smali)
so you could just add
Code:
echo NUMBER > /sys/class/vogue_ts/xmin
etc. etc.... to your userinit.sh

mmec2 said:
For some reason, I assumed it was a built in part of the system, but it's not!
Anyway, your question has got me interested now, so I took CalibrateScreen.apk from Scoot's CM6.1 build, decompiled the apk with apktool and searched the source for "write"
I believe the values you are looking for are
Code:
/sys/class/vogue_ts/xmin
/sys/class/vogue_ts/xmax
/sys/class/vogue_ts/ymin
/sys/class/vogue_ts/ymax
(found in CalibrateScreen/smali/org/isageek/dasbrennen/CalibrateScreen/Calibrator.smali)
so you could just add
Code:
echo NUMBER > /sys/class/vogue_ts/xmin
etc. etc.... to your userinit.sh
Click to expand...
Click to collapse
you are the man! You solved a issue that was drilling me since months!
Many many thanks!

It wooooooooooooooorks! HUAHAHAHAHA!
step by step:
1) calibrated screen with screencalibration app.
2) copied
Code:
/sys/class/vogue_ts/xmin
/sys/class/vogue_ts/xmax
/sys/class/vogue_ts/ymin
/sys/class/vogue_ts/ymax
/system/bin/userinit.sh
to sdcard root
3) edited userinit.sh with notepad++ like that:
Code:
#!/system/bin/sh
#
# Fix su so that we use the one supplied with the build. This allows the Superuser Permissions app to do it's stuff
#
/bin/umount /bin/su
/bin/umount /system/bin/su
busybox mount -o rw,remount /system
echo 708 > /sys/class/vogue_ts/xmin
echo 3660 > /sys/class/vogue_ts/xmax
echo 257 > /sys/class/vogue_ts/ymin
echo 3551 > /sys/class/vogue_ts/ymax
chmod 04777 /system/bin/su
chmod 04777 /sys/class/vogue_ts
busybox mount -o ro,remount /system
/bin/mount --bind /system/bin/su /bin/su
4) created a androidupdate.tar file with 7zip containing system/bin/userinit.sh
5) dpad during startup, installed androidupdate and fixed permissions
Happy ^^

could you upload the standard calibrate file to me ?
I dont understand why my kaiser seem to be crazy because touch screen seem to be rotate 90 degrees. it mean .... the app button ( in the center of the bottom screen ) will become middle of the left screen. I mean if I want to touch app button, I must touch the middle left of the screen
I cant do anything with this !!!
Fuk my kaiser >.< sorry for my bad emotion !!!

dai_thang said:
could you upload the standard calibrate file to me ?
I dont understand why my kaiser seem to be crazy because touch screen seem to be rotate 90 degrees. it mean .... the app button ( in the center of the bottom screen ) will become middle of the left screen. I mean if I want to touch app button, I must touch the middle left of the screen
I cant do anything with this !!!
Fuk my kaiser >.< sorry for my bad emotion !!!
Click to expand...
Click to collapse
Sure, here it is, install it like a normal update from dpad menu on boot (remember to fix permission after the install)

thanks for your quick response ! however, my fukin kaiser didnot change in positive way. Comparing to my friend device, I realize that different Kaiser has Different compatibility. I try 3 panel mode but the screen did not work well ! How can I mod a unique sceen calibration for me ? I mean rotate 90 degree counter clockwise T_T ?
I'm waiting for for help, TuoNonno, my own hero !

dai_thang said:
thanks for your quick response ! however, my fukin kaiser didnot change in positive way. Comparing to my friend device, I realize that different Kaiser has Different compatibility. I try 3 panel mode but the screen did not work well ! How can I mod a unique sceen calibration for me ? I mean rotate 90 degree counter clockwise T_T ?
I'm waiting for for help, TuoNonno, my own hero !
Click to expand...
Click to collapse
LOL...
have you tried to follow the instruction that I posted above to extract the correct values for your touch? remember also to do the calibration with the sliding keyboard closed!

TuoNonno said:
It wooooooooooooooorks! HUAHAHAHAHA!
step by step:
1) calibrated screen with screencalibration app.
2) copied
Code:
/sys/class/vogue_ts/xmin
/sys/class/vogue_ts/xmax
/sys/class/vogue_ts/ymin
/sys/class/vogue_ts/ymax
/system/bin/userinit.sh
to sdcard root
Happy ^^
Click to expand...
Click to collapse
How can I generate this information ???
What did U mean .... by saying "copied" ?

Those are the steps I did, so I wrote "copied".
Just follow those steps, nothing more to do
Basically, you need to run the calibration screen app, then you copy the 5 files in "/sys/class/vogue_ts" to your sd card root in order to be more handy and do those steps.

dai_thang said:
thanks for your quick response ! however, my fukin kaiser didnot change in positive way. Comparing to my friend device, I realize that different Kaiser has Different compatibility. I try 3 panel mode but the screen did not work well ! How can I mod a unique sceen calibration for me ? I mean rotate 90 degree counter clockwise T_T ?
I'm waiting for for help, TuoNonno, my own hero !
Click to expand...
Click to collapse
actually i cant speak english properly. but ill try to answer ur questions.
i have a stupid solution for the problem of calibrating the screen. i use Incubus26Jc's Super Froyo 2.2 [Deodexed] [RLS15] on my kaiser.
i do the screen calibration once a week. for the screen calibration on my android, will appear a black screen with two red dots on the screen to the left top, and bottom right. all i have to do is touch one red spot twice, until the recalibration text does not appear. (or other writings that tell you to re-calibration).
finished ...!!! what i have to do is press the "OK" to apply. i hope now ur screen is not mad anymore.

TuoNonno said:
It wooooooooooooooorks! HUAHAHAHAHA!
step by step:
1) calibrated screen with screencalibration app.
2) copied
Code:
/sys/class/vogue_ts/xmin
/sys/class/vogue_ts/xmax
/sys/class/vogue_ts/ymin
/sys/class/vogue_ts/ymax
/system/bin/userinit.sh
to sdcard root
3) edited userinit.sh with notepad++ like that:
Code:
#!/system/bin/sh
#
# Fix su so that we use the one supplied with the build. This allows the Superuser Permissions app to do it's stuff
#
/bin/umount /bin/su
/bin/umount /system/bin/su
busybox mount -o rw,remount /system
echo 708 > /sys/class/vogue_ts/xmin
echo 3660 > /sys/class/vogue_ts/xmax
echo 257 > /sys/class/vogue_ts/ymin
echo 3551 > /sys/class/vogue_ts/ymax
chmod 04777 /system/bin/su
chmod 04777 /sys/class/vogue_ts
busybox mount -o ro,remount /system
/bin/mount --bind /system/bin/su /bin/su
4) created a androidupdate.tar file with 7zip containing system/bin/userinit.sh
5) dpad during startup, installed androidupdate and fixed permissions
Happy ^^
Click to expand...
Click to collapse
Awesome! my Kaiser 100 now holds screen calibration, even after a dead battery or a power cycle. Really enjoying Dark_Prince's Froyo 2.2.2 on this AT&T tilt. But the method of creating a androidupdate.tar did not work for me. The update reported it worked as a success, then a fix permission seemed to finish, but still no calibration save.
This is what worked on my device:
As TuoNonno said I copied the four files containing the needed values, and in the end I went to market and got a file manager that had root permissions and edited ' /system/bin/userinit.sh ' to reflect the values those four files held.
my userinit.sh on my device now looks like this:
Code:
/bin/umount /bin/su
/bin/umount /system/bin/su
busybox mount -o rw,remount /system
echo 1345 > /sys/class/vogue_ts/xmin
echo 3387 > /sys/class/vogue_ts/xmax
echo 334 > /sys/class/vogue_ts/ymin
echo 3615 > /sys/class/vogue_ts/ymax
chmod 04777 /system/bin/su
chmod 04777 /sys/class/vogue_ts
busybox mount -o ro,remount /system
/bin/mount --bind /system/bin/su /bin/su
Not sure if that is the 'proper' way to fix, but it surely seems to work - I no longer have to use the physical buttons to navigate to and open the screen calibrate app.
Thank you to all that had a part in developing this fix. The knowledge of the gurus on this forum is outstanding!

LG Optimus Chic (e720) Custom Recovery + Kernel (overclock)!

This Custom Recovery and this Custom Kernel were created by drellisdee! All credits goes to him! I just created this post to show this great news at all LG Optimus Chic's owner. Special thanks by all of us to drellisdee.
After thanking drellisdee and have assigned all the merits of his work, we start with the guide.Remember that this recovery is still in beta, I do not assume any responsibility in case of brick or malfunction.
1) Root your device with z4root or SuperOneClick
2) Download this recovery and unzip it into the root of your sdcard.
Recovery Drellisdee (password is "gnmtest", without the " ")
3) Download flash_image.zip and unzip into the root of your sdcard.
Flash_Image.zip
4)And now give these commands through the terminal or adb shell.
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 0755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak (notice this file install-recovery.sh may not be on your device if it gives an error or file not found move on)
flash_image recovery /sdcard/recovery-alessi-gnm.img
sync
Then power off device and boot holding most likely vol-dn + vol-up + power button. You will see the custom recovery. To move into the recovery: Vol Up and Vol Down to go up and down. Back to go back and Menù to give enter.
The message E: bad boot message is normal disregard it.
For debugging use the move recovery-log to sd option under other and please upload it with feedback.
And nooooooow... The Custom Kernel!
Custom Kernel (for overclocking)
(password is "keepout", without the " ")
Put this kernel (not extract!!!!!) into the root of your sdcard.
Then flash it with this newest Custom Recovery!
Personally, I was able to step up the cpu to 729mhz ... This kernel is still a "beta", drellisdee said that soon it will improve and make it more stable.
Links works again!
Thanks again drellisdee!

Tested... Works 100%

Thanks for sharing this useful tweaks. it work pretty well on my e720, but my stock launcher always crash recently, don't know if this problem relate to this custom recovery.
sorry for my bad english.

Updated my recovery thread is here 2.2.1
Updated to 3.06 http://androidforums.com/getitnowmarketing/330813-all-one-recovery-thread.html

Thank U very much！It's too late to find this post；I'm a chinese， please forgive my terrible english。Thank u very much

Oh It's a good kernel..
I need a your help
Could you give a mcs6000.c (touchbug fixed) to me?
I made a kernel for korean chic
I made a oc kernel for korean chic but I can't fix touchbug....
please help me for korean chic.....
my e-mail address is '[email protected]'
I sorry to my bad english

Awesome share. It works, and I flashed mine with AndMelk rom. Now, my chic is running smooth... Thanks.

Updated recovery http://androidforums.com/getitnowmarketing/330813-all-one-recovery-thread.html
Andreoid said:
This Custom Recovery and this Custom Kernel were created by drellisdee! All credits goes to him! I just created this post to show this great news at all LG Optimus Chic's owner. Special thanks by all of us to drellisdee.
After thanking drellisdee and have assigned all the merits of his work, we start with the guide.Remember that this recovery is still in beta, I do not assume any responsibility in case of brick or malfunction.
1) Root your device with z4root or SuperOneClick
2) Download this recovery and unzip it into the root of your sdcard.
Recovery Drellisdee (password is "gnmtest", without the " ")
3) Download flash_image.zip and unzip into the root of your sdcard.
Flash_Image.zip
4)And now give these commands through the terminal or adb shell.
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 0755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak (notice this file install-recovery.sh may not be on your device if it gives an error or file not found move on)
flash_image recovery /sdcard/recovery-alessi-gnm.img
sync
Then power off device and boot holding most likely vol-dn + vol-up + power button. You will see the custom recovery. To move into the recovery: Vol Up and Vol Down to go up and down. Back to go back and Menù to give enter.
The message E: bad boot message is normal disregard it.
For debugging use the move recovery-log to sd option under other and please upload it with feedback.
And nooooooow... The Custom Kernel!
Custom Kernel (for overclocking)
(password is "keepout", without the " ")
Put this kernel (not extract!!!!!) into the root of your sdcard.
Then flash it with this newest Custom Recovery!
Personally, I was able to step up the cpu to 729mhz ... This kernel is still a "beta", drellisdee said that soon it will improve and make it more stable.
Links works again!
Thanks again drellisdee!
Click to expand...
Click to collapse