[Q] init.*.rc - G2 and Desire Z Q&A, Help & Troubleshooting

Hi,
What do the various init.*.rc files do?
init
init.rc
init.vision.rc
init.goldfish.rc
I only know that they are executed when the device boots. I flashed Godspeed's overclock rom onto my phone, and I am wondering if it had installed more scripts onto my phone (thereby slowly it down).

Related

JIT on SGS with 2.1

I am looking for a dev that can help me try and enable JIT on the SGS i have, a dalvikvm + libdvm.so and libnativehelper.so that should enable JIT. Could a dev with please create an update zip with these original files from our SGS (as a backup) and then sign these files as an update.zip and then do the same with the files i have attached - then try and flash them and see if you can get it to boot.
Please PM me if you have any questions or if you can successfully boot the phone.
(i am away from home for a few days and will not be able to try myself.. using hotel computer...)
Thanks
Sorry forgot to upload the files was watching the match. Will upload them in the next few minutes.
I already done compiled with JIT enable
copy files to my device, succesfully boot up but when I test with Linpack
MFLOPS was decrease, 6.65
before apply those files MFLOPS was 8.92
Hmm I might done somethings wrong?
FYI,
Maybe
Yes you may have made a mistake, could you please try with the files above.
can't boot for my i9000
Hang on boot loop
...
W/BootAnimationSEC( 2179): ms4631 - Repeat Loop Animation
...
Not working and NoooooO !! I can't remove those libs T_T
execute "su" got "Segmentation fault" -__-"
@bratfink May I? where did you got those files.
You can use my Custom Rom for this ;-) http://forum.xda-developers.com/showthread.php?t=724450
I just want to put those (essential) JIT enabled file. Or It will not work? if there're only those 3 files.
Just don't want to use custom ROM right now, it's base on European rom but I'm living in Asia. There're many tasks to do after use others region rom, for me.
@seraphimserapis Could you suggest the information that made me, to build my own custom rom, base on my region's rom. I googling, googling couple weeks ago but still can complete the jigsaw.
-_-" finally, I can recover my devices ...
@bratfink I think those files were dangerous, got stucked at the (big S boot screen), broke the "su" command so I can not restore the original one.
I must flash the Kernel back to LeShak kernel then restore those files. flash current again then device back to normal.

[Q] editing boot.img

i extracted the boot.img from my desire and run this script on it.
but it returns:
Code:
./unpack-bootimg.pl boot.img
Found a secondary file after the ramdisk image. According to the spec (mkbootimg.h) this file can exist, but this script is not designed to deal with this scenario.
i've been searching the internet for two days now and i cant find any other script that does that, only a tutorial for manually doing it with a hex editor, but that still doesn't cover that last file the script is complaining about.
any ideas?
p.s.: i need to modify boot.img because i'm trying to set up dual boot - android + android - for testing purposes, will post if successful
update:
i managed to extract kernel and ramdisk
first i tried booting kernel from fastboot, worked like a charm
then i tried booting kernel+ramdisk from fastboot - hangs on htc logo
i also tried compiling kernel+ramdisk into boot.img instuctions - again hangs on htc bootscreen
adb says no devices, fastboot detects it, but shows no ID, just ??????????
so apparently the last file in boot.img is important
any ideas?
i'm using cyangenmod7 btw

Unable to flash a new kernel, 2 unknown config parameters

I have a phone which is a Wolfgang AT-AS43d. I'm trying to flash a new kernel on the device but it won't boot with the new kernel. The phone is a rebrand of the Techfaith Tracker.
I have pulled the config.gz from my phone and made several kernels (3.0.8, 3.4) using the aurora code for Qualcomm devices. With all of these kernels, the phone comes in a bootloop (show a logo -> black screen -> reboots -> show a logo -> etc). My stock kernel is a 2.6.35.11 version, so at last I made a kernel with the same version. But this one won't boot either.
I unpacked the stock kernel, made a change to a Android system property (ramdisk file), repacked it and flashed it to the phone. The phone will boot, so the way I'm flashing is correct (or correct me if I'm wrong).
In the config I pulled from the phone there are 2 config parameters that I cannot find anywhere in a Linux configuration and I am suspecting that I need these (the drivers) to successfully flash a new kernel. The 2 parameters are:
CONFIG_ANDROID_TF_CODE_BASE=y
CONFIG_MINIDRIVER_BASE_H900=y
Maybe TF stands for TechFaith?
Can anybody confirm that this is the reason why I'm unable to flash a new kernel?
Does anybody knows where to get these drivers?
Or is there an other solution to flash a new kernel on the phone?
Shouldn't these drivers made public, since it's part of a kernel?

[Q] Modifying init.rc

I'm looking to modify my init.rc file. I've able to dump the boot.img with a straight dd from mmcblk0p7 and double checked it with the backup from CWM. I've been using the bootimg-tools (extractboot and packboot) and can successfully extract the boot.img down to modify the actual init.rc file. However when I pack the new boot.img back up and dump it onto the phone it gets into a reboot cycle. At this point I'm simply unpacking and repacking the original, no modifications to any files, and it is still unable to boot. I'm also aware that this exact method has worked for my Motorola Atrix and Nexus One. Is there something different that I need to be doing on the GS3?

[Q] How to Fix Boot Animation (stock-root)

Hey all,
So I tried adding a custom boot animation to my phone, and now all I get is a black screen with the stock sound playing.
Basically what I've done was:
Rooted my device using Super SU
Installed Busy Box
(Copied to my external sd card: bootsamsung.qmg bootsamsungloop.qmg)
Did this tutorial: http://forum.xda-developers.com/show....php?t=2063280
And that's when things went wrong.
I believe, (based off the files used in the tutorial), that the problem may be in/with the following:
/system/bin/bootanimation (exe)
or
/system/bin/samsungani (exe)
or
/system/bin/sh (text file)
I've tried adding the original .qmg files back but it hasn't worked.
I'd like to end up with a custom animation, but at this point I'll be happy with any animation.
Any help would be amazing.

Categories

Resources