Stephen J. Knill, on Mar 19 2011, 17:12, said:
Yep, put a script in /system/etc/init.d and chmod 755 they will be run after the init.rc
I have no init.d, but no problem If I can get into recovery
Sebastian404, on Mar 20 2011, 15:18, said:
So do you have a working V9 now ? with 2.2?
yes they replaced my phone, what totaly died in this accident, maybe your device is flashable with my img files in this method, but with that russian flashable firmware my V9 died, other problem can be I skipped splash.img :S
- Flash recovery image from Recovery Manager = flash it with fastboot right?
- Edit init.rc can brick phone, I need to add chmod 4755 /system/bin/su line somewhere what chane permissons until phone boots, but I don't want to edig boot.img till I can't get to recovery with volup+pwr
Any idea why volup+pwr not work to get in recovery mode?
I found something like my problem:
We can only get into recovery by pressing vol - on the blade because we hijacked FTM mode. FTM mode uses the same parition as recovery but disabled lots of stuff, so when our custom clockwork recovery starts up it checks to see if it's in FTM mode and then does a reboot recovery to get into proper recovery mode where everything is enabled. You really need to get a modification of clockwork going for your device, this may be as esy as starting with the Blade recovery, unpacking, replace the kernel with yours and re-pack. Then flash either using fastboot or if you can SU then from terminal run flash_image recovery /sdcard/cwrecovery.img.
Sebastian can you help me in this? Now I go to FTM (DFU) mode when press vol down
Last time I flashed a wrong boot.img an I cannot get into recovery, cause there is 2 ways - adb and from the android system, and with damaged img adb not worked, phone rebooted after 1-2s.
I have a working cooked ROM, but there is a chmod to su in init.rc, and manual extracted and recompiled boot.img not worked. They won't replace it next time If I miss something so I have to be safe.
I checked your recover what created from my kernel, and maybe in recovery.sh input4 is not the voldown I really don't understand all about how this works, but they changed something. Only works from adb or phone reboot in recovery mode.
In recovery vol down is key 114 vol up is key 115 power is key 142 long press is 116
Other, not the most important now:
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq and scaling_max_freq Can I set them to 800000 or this kill my phone too?
there is an init.qcom.post_boot.sh what send CPU min fre values to the scaling_min_fre, maybe I can send the max values too.,