yashsingh1/xdaforums huggingface dataset:
[HTC Wildfire S] izi501:
And what is the error this time ?

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] xizt1boy:
F/libc ( 104): Fatal signal 4 (SIGILL) at 0x401ea678 (code=1)

Here you have a logcat
[HTC Wildfire S] 4ndaKava:
The same issue.. Maybe a different Problem, but have a look at it:

https://groups.google.com/forum/#!msg/android-building/4FBs-WSLCwk/seppxxNlP0cJ

Edit:

And here is a miuiport thread. It seems like the Errors are the same, but they solved them.

Edit2:

The libc fatal error appears only at android 4.0.x. Try to replace the file with a cm10 libc?
[HTC Wildfire S] izi501:
That's strange ! You took the same libc.so that thehacka1 took ?

If you are lucky, you fixed the error ;)
[HTC Wildfire S] thehacka1:
I don't think that error is fixed. The error occured after all the jars dexopted. Herre the jars don't even begin to dexopt. Seems we don't need to look at bootclasspath at all.
[HTC Wildfire S] thehacka1:
OK guys. The error says E/JNIHelp. It also states that RegisterNatives failed. This is clearly a lib problem. Taking all of this into consideration I did some research. And it seems JNIHelps is located in libnativehelper.so. I'm guessing this lib is also responsible for RegisterNatives. http://gitorious.org/0xdroid/dalvik...87fb89b338bfafa6f79/libnativehelper/JNIHelp.c
[HTC Wildfire S] izi501:
But as I said, the problem comes from here :

clazz = (*env)->FindClass(env, className);

if (clazz == NULL) {

LOGE("Native registration unable to find class '%s'\n", className);

return -1;

}

So we also need to find where the FindClass() method is defined.
[HTC Wildfire S] thehacka1:
You don't get it. The FindClass() method is defined in JNIHelp.c file which is built into libnativehelper.so.
[HTC Wildfire S] izi501:
OK, so you think we do not have the right libnativehelper.so ?
[HTC Wildfire S] thehacka1:
We have the right lib the methods all fine. I think it's the framework that's not being dexopted like HTCExtension.jar.
[HTC Wildfire S] izi501:
I don't get what you want to do :) You mean that the libnativehelper.so is not used correctly in framework ?
[HTC Wildfire S] thehacka1:
Maybe this error is caused because it doesn't DEXOpt all framework. It only DEXOpts the ones that CM9 does. It doesn't DEXOpt HTCEXtension.jar, HTCDev.jar, wimax.jar, usbnet.jar, etc. I'm guessing this is why the error shows up. If not then crossfire77 is getting some help.
[HTC Wildfire S] thehacka1:
[MENTION=4960219]xizt1boy[/MENTION] How do you decompile a kernel and edit init.rc? If I use your method it may work for me.
[HTC Wildfire S] izi501:
I don't know how he does, but you can always try that.
[HTC Wildfire S] thehacka1:
Installing Cygwin now. It didn't work with Git PowerShell.
[HTC Wildfire S] Kevinjoa:
What's upto you guys ? Why not using ans Linux Distribution like ubuntu or (I have switched to Linux mint 15 now)

Then you can usw kitchen in full speed and more easily. No Problem with Cygwin on Windows, too.

Gesendet von meinem Wildfire S A510e mit Tapatalk 2
[HTC Wildfire S] thehacka1:
Im in Ameica usin my uncle's computer. I don't think he would like it if I dual-boot his computer.
[HTC Wildfire S] Kevinjoa:
Sorry. I dont know that you aren't home at the moment. ;)

Gesendet von meinem Nexus 7 mit Tapatalk 4 Beta
[HTC Wildfire S] izi501:
If you tell me what to mod, I can try to do it for you ;)
[HTC Wildfire S] xizt1boy:
You can decompile by Cygwin. Personally, I use Cygwin + dsixda's kitchen.
[HTC Wildfire S] thehacka1:
First decompile the kernel. In the ramdisk folder you'll find init.rc. Open init.rc with Notepad++/Gedit. Look for the line that says export BOOTCLASSPATH.

Change the line from this:

export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar

To this:

export BOOTCLASSPATH /system/framework/core.jar:/system/framework/core-junit.jar:/system/framework/bouncycastle.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/framework2.jar:/system/framework/android.policy.jar:/system/framework/services.jar:/system/framework/apache-xml.jar:/system/framework/HTCDev.jar:/system/framework/HTCExtension.jar:/system/framework/filterfw.jar:/system/framework/com.htc.android.bluetooth.jar:/system/framework/wimax.jar:/system/framework/usbnet.jar:/system/framework/com.orange.authentication.simcard.jar

Recompile the kernel and send me the boot.img.
[HTC Wildfire S] xizt1boy:
Hold ;)
[HTC Wildfire S] izi501:
That's unfair, I was eating :P

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] xizt1boy:
Sorry, but I had already edited and compiled.. :p
[HTC Wildfire S] thehacka1:
That's fine to me because I'm testing :p.
[HTC Wildfire S] izi501:
Here you are, I've done it myself too :)

But be careful while testing, because the last time I modded the kernel I almost broke my device :D
[HTC Wildfire S] 4ndaKava:
Good luck. :) Hope it works!
[HTC Wildfire S] Olivier:
A pity I can't participate in this project (no wfs for testing, broken laptop, vacations, ...), but you guys rock! All of you deserve the "Recognized Developer" title. And never forget: Trying is the first step towards failure! :p

Good luck. :)

Gesendet von meinem Odys Chrono mit Tapatalk 4
[HTC Wildfire S] izi501:
[OFFTOPIC]

I never visited Dijon, but I hope you enjoy it ;)

[/OFFTOPIC]

---------- Post added at 10:21 PM ---------- Previous post was at 10:17 PM ----------

So thehacka1 did it work ?
[HTC Wildfire S] Kevinjoa:
Yeah, hackr1 and the other guys out here are dammly rocking at the moment. Getting this booted and working normal would be sth. really nice because I could make Marvellous Sense 4 rom with the themes [MENTION=2756582]Mazer.one[/MENTION] created for desire c. I really like cm Roms more but making Marvellous Roms is a thing which has to make sense (Sense 2.1, 3.5 and 4 :D )

Never give up. Maybe I can help out, too.

Gesendet von meinem Wildfire S A510e mit Tapatalk 2
[HTC Wildfire S] 4ndaKava:
We try to get it work together. :)
[HTC Wildfire S] thehacka1:
The new BOOTCLASSPATH didn't fix the error but when it does boot most sense things should work.
[HTC Wildfire S] izi501:
I just wanna say "Ça nous fait une belle jambe :P"

So the new framework jars are all DexOpted ? Because maybe we forgot one in BOOTCLASSPATH, or maybe the kernel mod didn't work.

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] thehacka1:
All important jars have been dexopted. HTC knows best. And yes it so makes us look good.
[HTC Wildfire S] izi501:
Didn't know the English translation ;)

What about DexOpting the jars that are not important ? Because the problem certainly comes from the framework... As the class exists, the lib exists, and they're both correct, there must be something wrong from the framework file that contains this method.

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] thehacka1:
Used Google translate. :p The BOOTCLASSPATH I suggested is the one from the Desire C.
[HTC Wildfire S] xizt1boy:
If you swap libnativehelper.so from sense 4 this error disappear, but still bootloop and then there's a problem with libc.so...
[HTC Wildfire S] izi501:
So maybe we'll just have to keep the library from Sense 4 and try to fix the error with libc.so...

If you use libc from Sense 4, what happens ?

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] xizt1boy:
Stuck on htc log...
[HTC Wildfire S] izi501:
Libc.so being the core library, it seems normal... But we could also try some libs from Sense 3.5...

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] xizt1boy:
I've tried everything .. Slowly I begin to doubt about working sense 4 on ARMv6... :(
[HTC Wildfire S] izi501:
That's certainly difficult, but we mustn't give up ;)

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)

---------- Post added at 10:13 AM ---------- Previous post was at 10:10 AM ----------

What is this error ?

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)

---------- Post added at 10:17 AM ---------- Previous post was at 10:13 AM ----------

Did you try to swap libnativehelper.so from Sense 3.5 ?

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] xizt1boy:
Yes..

I/Netd ( 177): Netd 1.0 starting
[HTC Wildfire S] izi501:
[MENTION=5043290]4ndaKava[/MENTION] also proposed to replace libc.so with the cm10 one.

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] xizt1boy:
The same .. I think I've tried everything..
[HTC Wildfire S] izi501:
It's always the same libc error ?

For the Netd problem, I think it is possible to fix it.

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)

---------- Post added at 10:41 AM ---------- Previous post was at 10:27 AM ----------

OK, so when we get a SIGILL error with libc, we mustn't even try to fix it :P

The reason here : http://stackoverflow.com/questions/7901867/what-causes-signal-sigill
[HTC Wildfire S] benjamingwynn:
I'm pretty sure libc and dalvik are the master libs. If you boot into the bootscreen, don't touch them.
[HTC Wildfire S] benjamingwynn:
Also, I read your question earlier and we too were confused on why all of the paths had L infont. We just came to the conclusion that it was short for framework.jar/ and I think I remember reading some evidence of this

Edit: http://xdaforums.com/showthread.php?t=1698139
[HTC Wildfire S] izi501:
Yeah benjamin is right, we mustn't touch the main libs.

I just opened a thread to ask a few devs for help : http://xdaforums.com/showthread.php?t=2368430 (ok I know you also did that ben, but the thread was dead and nobody replied :( )
[HTC Wildfire S] Guitarfreak12:
still stuck at the same error?
[HTC Wildfire S] izi501:
Yup, always the same, and the same the Ben, oliverG96 and dudeman experienced.

Does anybody else have any ideas ?

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)

---------- Post added at 02:07 PM ---------- Previous post was at 01:34 PM ----------

But NetworkManagementSocketTagger is in framework.jar, and the path doesn't have a L...
[HTC Wildfire S] thehacka1:
We are all talking about libc here which in my opinion should not be touched. Good to have you back Ben. The error says Register natives failed for class. I've had no reply from JDevs ( the usual ). Any ideas on this?

EDIT: When Ben says libc and dalvik I think he means libc.so and libdvm.so.
[HTC Wildfire S] izi501:
When Java is compiled, if I understand well, it builds every class in one file. So every .smali file is a class (that is what I understood, maybe it's false).

I still think there is something strange with the path given... There is no L.
[HTC Wildfire S] thehacka1:
Guys I'm trying something very risky that all of you will kill me for. Don't blame me for doing this. If this does work then it's good. I have a slight chance of hardbricking my device.
[HTC Wildfire S] izi501:
Hmpf. I've created a GitHub account, forked the repo, etc, and I wanted to add my modifications to the kernel, but it didn't work :P Git says that everything is up to date in my repo...

EDIT : Ok, working now

What the hell are you gonna do ?!
[HTC Wildfire S] Kevinjoa:
Hope it will work and not brick your device. ;) why doing sth. like this ? What are you doing ?

Gesendet von meinem Wildfire S A510e mit Tapatalk 2
[HTC Wildfire S] thehacka1:
Right now I can't do it because my sdcard is being a d**k. But will try it soon.
[HTC Wildfire S] Kevinjoa:
I tried Tod install fedora 19 and broke my bootloader. :(

Gesendet von meinem Nexus 7 mit Tapatalk 4 Beta

---------- Post added at 03:47 PM ---------- Previous post was at 03:32 PM ----------

Who, fixed it with Win7 DVD by using cmd and thoose inputs

bootrec /fixmbr

And

bootrec /fixboot

Easy peasy.

Gesendet von meinem Nexus 7 mit Tapatalk 4 Beta
[HTC Wildfire S] izi501:
But what do you want to do ?

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] thehacka1:
Let me try it. If it works then I can tell you. If it doesn't then you won't like what I did.
[HTC Wildfire S] izi501:
When will you do it ?

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] benjamingwynn:
Libc: C Interpreter (afaik)

Libdvm: Dalvik Virtual Machine, the Android JVM.

So if both are failing its probably an incompatible framework/lib combination. Again with this whole ARMv6/7 thing.

EDIT: I have pointed out many times about a working ARMv6 Sense 4 port being almost impossible. 3 developers, including myself have tried and failed. I personally cannot see it booting and even if it does I cannot see things like internet connectivity working correctly/at all. Porting to different arch's always has bugs, take Sense 3.5 for example, for a long while that refused to run Facebook and I couldn't figure out why. Probably a lib problem.

Heck, if I say it's impossible, might as well try it.
[HTC Wildfire S] izi501:
I KNOW !

Or at least I have an idea ;)

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] izi501:
It is effectively "almost" impossible... But JDevs say they have made it, and I have no reason to think that the lied :)

However they told us that the ROM was very unstable, which is perfectly understandable.

But would you have thought we would one day get AOSP 4.2 with Beats Audio ® ? Would you have thought we would get MIUI 2.10 ? That we would have enough memory and processor to run the latest Android versions two years after the end of official support for our device ? Everything is possible ;)

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)

---------- Post added at 05:00 PM ---------- Previous post was at 04:58 PM ----------

So, if you look into Sense 3.5 framework.jar, you'll see that there are two files and one folder. In Sense 4's, there is only one file. That means the framework is not signed and all. Maybe there is something interesting there...

EDIT : in Elegancia ROM, there is, as in Sense 3.5, the file preloaded-classes, which contains the class we are looking for :) I think we should try to add this file in framework.jar and see what happens.

Sorry I can't test anything at the moment because I need my phone...

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] thehacka1:
Send me that shiz now! By the way my method did not work. I'm not even going to tell you what it was. :p So someone send me those preloaded classes.

EDIT: Just looked at sense 3.5. There's a manifest in the framework.jar and pre-loaded classes. I'm going to take a closer look at the manifest.

EDIT2: The manifest contains nothing. Just:

Manifest-Version: 1.0
Created-By: 1.6.0_26 (Sun Microsystems Inc.)

EDIT3: The preloaded classes are recognized by com/android/internal/os/ZygoteInit.smali. Time to look at that file.

EDIT4: I'm going to make a preloaded classes file for the Sense 4 framework.jar. I'll add the class:

com.android.server.NetworkManagementSocketTagger

Hope this works.
[HTC Wildfire S] izi501:
I took them from Sense 4.1, so I download another Sense 4.0 rom to get the right version :)
[HTC Wildfire S] thehacka1:
Could someone send me their patched framework.jar? I lost mine. :p
[HTC Wildfire S] izi501:
Here it is :) All the framework.jar of the desire C (only the files preloaded-classes in important, and maybe the folder META-INF).

https://drive.google.com/folderview?id=0Bzu23Ofpngi3ZDhxM082bXNOekE&usp=sharing

---------- Post added at 06:01 PM ---------- Previous post was at 06:00 PM ----------

Is the GitHub one patched ?
[HTC Wildfire S] thehacka1:
Yeah it is. :p I forgot.
[HTC Wildfire S] izi501:
If I were you I would use the file from the Desire C instead of making one yourself :)

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] thehacka1:
The preload-classes thing doesn't work. Whatever I try to do Netd fails to start.
[HTC Wildfire S] izi501:
So did it work ? :)

EDIT : okay we posted at the same time...

Which file did you choose ?

EDIT 2 : one thing is strange, every ROM has normally this file... So certainly the smali file that manages the creation of it has a problem, maybe needs to be patched.

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] thehacka1:
I don't think so. I've patched the smalis. I don't think we need a manifest or preload-classes to fix this error.
[HTC Wildfire S] izi501:
Yes but don't you think it's strange that every rom has this file (even the stock Desire C one) and this one doesn't ?
[HTC Wildfire S] thehacka1:
This rom that I've ported is mmmfc's Slim Sense rom. It is based off Desire C's stock rom.
[HTC Wildfire S] izi501:
That's strange because I took the file from the stock rom (a little bit modded, like crossfire77's rom for the wfs).

Could you please try the file attached ?
[HTC Wildfire S] thehacka1:
That's gingerbread. This is ICS. Won't work like that.
[HTC Wildfire S] izi501:
Errr... Nope it's Sense 4 :)

I took the framework.jar from github and modded it a bit.
[HTC Wildfire S] thehacka1:
I was porting MIUI from the Nexus S and I got this error:

E/JNIHelp ( 128): Native registration unable to find class 'com/android/server/NetworkManagementSocketTagger', aborting
[HTC Wildfire S] xizt1boy:
LOL. The same as in sense 4.. :eek:
[HTC Wildfire S] izi501:
Yes, they have the same framework :) At least, that's what I've been told.

So [MENTION=4960614]thehacka1[/MENTION] did you try my framework ?
[HTC Wildfire S] thehacka1:
Not yet. Will do soon.
[HTC Wildfire S] thehacka1:
[MENTION=4749032]izi501[/MENTION] You framework doesn't work. Netd fails to start.
[HTC Wildfire S] izi501:
That's sooo strange... So then I guess we've got either to fix the smali that generate this file, or to find another way of fixing the error.

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] 4ndaKava:
Sorry guys, wasn't at home till now.. So:

Maybe we should turn back to the Point where the 'NetworkManagementSocketTagger' wasn't found.

(http://xdaforums.com/showthread.php?t=2247474&page=19)

It could work if we add at this point the preloaded classes. Just an idea.
[HTC Wildfire S] izi501:
I don't understand :)

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] 4ndaKava:
Well.. As I understood the actual Problem is a libc problem.. So there is no point of adding the preloaded classes.

But a bit before there was the problem with the 'NetworkManagementSocketTagger'.. There it was needed.

But maybe just my mind is a bit fu***d up. :D
[HTC Wildfire S] izi501:
In fact, the problem with libc happens while trying to fix the " NetworkManagementSocketTagger" error :)

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)

---------- Post added at 01:00 AM ---------- Previous post was at 12:57 AM ----------

Hey people, someone replied to the thread I created earlier, requesting a full logcat. Could you please give it to him ? As I'm going in holidays I won't be able to logcat or to test anything :)

http://xdaforums.com/showthread.php?t=2368430

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] thehacka1:
WOW. Someone actually replied. :p I'll get him the logcat.
[HTC Wildfire S] izi501:
Yes that's what I thought too :D

Sorry I can't test anything but now I need my phone to be usable, so I can't mess up a lot with roms.

Envoyé depuis mon HTC FeuSauvage S avec CM10.1 :)
[HTC Wildfire S] thehacka1:
I gave him the logcat. Lets hope he knows what he's doing.
[HTC Wildfire S] Olivier:
[MENTION=3423567]samuel2706[/MENTION] , maybe you can help? :)

Gesendet von meinem Odys Chrono mit Tapatalk 4
[HTC Wildfire S] 4ndaKava:
Hope this guys can help :)
[HTC Wildfire S] samuel2706:
What's going on?
[HTC Wildfire S] Kevinjoa:
Hi samuel we are trying to port Sense4 to our Wildfire S (marvel) and stuck with some errors. [MENTION=4960614]thehacka1[/MENTION] main developer is facing some complicated errors and we want get it booting. Maybe you can help us. :)

Thanks in advance. ;)
[HTC Wildfire S] thehacka1:
[MENTION=3423567]samuel2706[/MENTION] Here is the logcat. Hope it helps.
[HTC Wildfire S] samuel2706:
E/JNIHelp ( 187): Native registration unable to find class 'com/android/server/NetworkManagementSocketTagger', aborting

F/libc ( 187): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)

Try putting NetworkManagementSocketTagger*.smali from base to sense 'framework.jar'

That may fix your problem.

You need to patch a lot of Smali files when doing this kinda thing.
[HTC Wildfire S] xizt1boy:
We tried and didn't work. Both .smali are the same..
[HTC Wildfire S] samuel2706:
Done the whole bootclasspath thing?
[HTC Wildfire S] samuel2706:
Also did you replace all the NetworkManagementSocketTagger files?
[HTC Wildfire S] xizt1boy:
Yes. Also edit bootclasspath in init.rc.

Yes. Besides, only one differs in several letters, numbers..
[HTC Wildfire S] samuel2706:
Changed the static fields sections to correspond with the changed smali files? also when you put it back in you set the perms correctly right?
[HTC Wildfire S] samuel2706:
Can I have both framework.jars please, see if I can see what's going wrong.
[HTC Wildfire S] xizt1boy:
Here's my edited sense 4 framework.jar, I'm with this error too..
[HTC Wildfire S] thehacka1:
The framework.jar is from Sense 4 and the framework_base.jar is from our CM9. See attachments. These include latest changes from my GitHub: github.com/thehacka1/htc_sense_4_marvel
[HTC Wildfire S] samuel2706:
Right, are you trying to port using a CM base to HTC base?

Why not sense 4 from somewhere else (as close to the wildfire S as possible) and then swap the files and such, change the libs and change all that, take the files from the 3.5 sense wildfire and put it in the sense 4 and it SHOULD boot, if you have an ICS kernel, if you don't; a kernel dev MAY perhaps be able to get us kickstarted with this.
[HTC Wildfire S] thehacka1:
We are porting from the Desire C. We can try from the HTC Pico if you like. We have a CM9 kernel so I guess we should ask [MENTION=4511965]crossfire77[/MENTION] about the ICS kernel. Using sense 3.5 gingerbread files for sense 4 ics sounds a bit dodgy but we'll give it a go. Looks like it's back to square 1. :D

EDIT: By the way I tried your porting method. It was good but it didn't work for me. Phone always got stuck at HTC screen.
[HTC Wildfire S] samuel2706:
Ahh yeah that's a bit out of date haha

To be honest it doesn't matter what you take it from, as long as it's HTC sense 4.0 it's all about the kernel, if we can get a partially patched ICS kernel it'd boot I'm almost sure of it however the desire C would be brilliant as you wouldn't have to change any apps to fit screen res also you may have failed due to incorrect amount of storage on the /system partition, we used to have a script when we ported from Sensation to Desire HD that put /system apps on /data and symlinked it so it used the data partition and thus we had more space, you could try using my thread and then boot and logcat, if you can't get logcat it might be that you ran out of space on system partition.
[HTC Wildfire S] 4ndaKava:
We have a cm9 kernel (http://xdaforums.com/showthread.php?t=2010083), but what to do with it? What should we edit exactly?
[HTC Wildfire S] samuel2706:
No idea I'm not a kernel developer It'd just make sense to use a sense based kernel rather than an AOSP one.
[HTC Wildfire S] samuel2706:
Yeah the desire C rom is 400+ MB so it's doable maybe.. but will require the use of /data/app as it won't all fit on system/app that's why it wouldn't boot.
[HTC Wildfire S] 4ndaKava:
[MENTION=4511965]crossfire77[/MENTION] could you help? :)
[HTC Wildfire S] thehacka1:
I have already got the size down to 170 MB so there is no need for data/app. What do you mean by a sense based kernel? Do you mean using htcdev.com to get kernel source? The we are porting right now is from the Desire C. So I'm guessing that there's no way to fix NetworkManagementSocketTagger error.
[HTC Wildfire S] samuel2706:
I can't see how to fix that pal sorry, I'd say get a working gingerbread kernel and make it ICS if you can i'm not sure how that all works, but if you did you could boot up using a straight sense to sense port instead of AOSP I really wouldn't use AOSP to sense you will have so much problems.