yashsingh1/xdaforums huggingface dataset:
[Wildfire Android Development] SinawY:
i've already done the first, and the ones that i didn't find their equivalents in sense 2.1 i've left them without any changes. and it didn't work. still boot loops.:mad:

Solar

i will check ur zip if i have time tomorrow.
[Wildfire Android Development] Solar_:
Can anyone make a logcat of v0.1a2?

Would like to know why it won't boot..

I don't have time for it now, gotta make my homework for tomorrow :o
[Wildfire Android Development] kaassaus:
i have try to do a logcat but it fials
[Wildfire Android Development] sasans:
where to find link for v0.1a?
[Wildfire Android Development] Solar_:
Deleted, since v0.1a2 is actually the same, but more added.
[Wildfire Android Development] kaassaus:
who know how to solve the probleme for booting
[Wildfire Android Development] 3xeno:
Please do your homework and stop spamming this thread every 10 minutes.

What on earth man, let the members work without you interrupting them everytime with such needless posts. Surely when the booting problem is solved, you will know.

I come to keep a check of the progress, and everytime I see such needless posts. :mad:
[Wildfire Android Development] kaassaus:
its not my foult i wanna realy this rom
[Wildfire Android Development] Justice™:
True that. I doubt that we'll get it to boot for a few days at least. Until someone much more experienced with android rom development gets involved
[Wildfire Android Development] sasans:
hey gays please fix this rom,i cant wait
[Wildfire Android Development] markkamphorst:
You mean hey guys :p

Let them work on it and have faith, they make miracles happen!
[Wildfire Android Development] SinawY:
Solar

try this solution for boot.img

its by SebastianFM here

i am going to try it. may it work.
[Wildfire Android Development] kaassaus:
sinawy i hope so
[Wildfire Android Development] Justice™:
I think they looked at that, and there was different paths to the ones in the Sense zero boot.img
[Wildfire Android Development] Alyzembawy:
Please man stop posting useless posts, I am getting tons of notifications coz of you! -.-

Sent from my HTC Wildfire XDA Premium App
[Wildfire Android Development] Justice™:
Has anyone tried doing sebastianFM's patch on the boot.img that is stock, also does a dev mind taking a look at the Droid Eris port. I think we could make it boot, it has pretty much the same filestructure of many WF roms
[Wildfire Android Development] VigiDroid:
I tried modifying the boot.img but it still wouldn't get past even splash1 (my splash one is a telstra image) It wouldn't even start so a logcat wouldn't come up using the DDMS tool in android-sdk... Needs lots more modifications and edits. Maybe we could port this into sense 2.1 so we have a sense 2.1/3.5 rom? Its the only way I see possible unless you use A LOT of trial and error to get this rom to boot... :(
[Wildfire Android Development] JoeyDelp:
Has anyone tried using a remapped partition table? as i recall when installing sense 2.1 and beyond on the desire they all needed atleast a custom hboot and without it you would get a bootloop, i dont know where to begin with this, maybe take a look at how the desire's hboot cm7 is mapped out over at alpharevs website
[Wildfire Android Development] sasans:
can you put theme like this rom?
[Wildfire Android Development] mtnhan1996:
I think he mean gays...
[Wildfire Android Development] Solar_:
Don't post anything that isn't related to this thread please.

Can't you see the [DEV] above?

On-topic : Will look at the BOOTCLASSPATH from the Eris, then compare with the stock Pico RUU, and then compare with SenseOnFire.

Also might take a look at the libs from the Eris and the Pico.
[Wildfire Android Development] kylon:
I replaced sense on fire bootclass with the hero port bootclass . But it doesn t work(bootloop)

Then with this boot i replaced some libs and files according to a guide on xda on how to port sense rom but it doesn t work

I think : bootloop is a "good thing" because it s not a "stuck on boot" and means that the phone try to load the system but something is missing

(I think)

Sorry for bad english
[Wildfire Android Development] Solar_:
Yesterday I told some1 that I'll PM SebastianFM, and got an answer now :rolleyes:

I told him that our ROM doesn't boot and that stuff..

''I didn't work yet on porting Sense 3.5. I only ran HTC Pico ROM on the emulator. I think that you should ask Hintay about boot issue. Probably it is kernel related.''

That's what he said.

So now, I will ask Hintay about this problem. I hope it'll be fixed soon :cool:
[Wildfire Android Development] Justice™:
If that doesnt work out, We can use one of the other ports to other HTC devices? I have no idea what your looking for in a good rom to port from though. :/
[Wildfire Android Development] Solar_:
I'm now in contact with Hintay, he also had problems with the boot.img (especially BOOTCLASSPATH).

Although, they fixed it.

So now I'm trying to do the same as he said.
[Wildfire Android Development] Justice™:
Good idea.
[Wildfire Android Development] zexcrazy:
This looks promising. I might help resizing it once you guys succeed to boot it.
[Wildfire Android Development] kaassaus:
if this will work i might be helping rezising if i have time
[Wildfire Android Development] zexcrazy:
You really are something. You have to comment every post. You remind me on melvinchng. Older members remember him.
[Wildfire Android Development] :
Yes i do remember *the one that shouldn't be spoken off* lolz
[Wildfire Android Development] Alex_GP:
No. melvin is a God. Nobody can ever come close to his level.
[Wildfire Android Development] kaassaus:
............
[Wildfire Android Development] Solar_:
Guys, for the last time : This is no 'make lawl'-thread.

On-topic : Testing new build, rebased on Hintay's ported Sense 3.5 Magic.
[Wildfire Android Development] Justice™:
Nice, I've been playing about with eris port. (Not been doing many major things since I'm a newbie android developer). The eris seems to be like the wildfire in ways. Having no GPU is one of them.
[Wildfire Android Development] sasans:
o my god,if you finish this rom this mounth its will be great,comon tried to finis!If you dont now how you close this thread!
[Wildfire Android Development] Justice™:
Hi there. I see you don't understand grammar or reading.
[Wildfire Android Development] Alyzembawy:
Why do people just keep posting useless posts?!... This is developement section ppl!

I am getting tooooo much notifications.

U know the moment when u get excited to check a new post hopefully the specific problem is.solved, and then u find a useless stupid post instead?! -.-
[Wildfire Android Development] jamal2367:
when it is about finished? and you already have the right boot.img?

Sorry for my English!!
[Wildfire Android Development] Justice™:
Don't ask for deadlines. Its done when its done.
[Wildfire Android Development] jamal2367:
ok....

sry
[Wildfire Android Development] SinawY:
what i've tested today:

replaced some files in /system . and replaced kernel in Pico boot.img with kernel from SFM 1.1 and changed init.pico.rs to init.buzz and resultis: stuck on splash screen.

and again tested the same thing with boot.img from magic port and same result, fail to boot.

Guys i've compared BOOTCLASSPATH in SFM 1.1 (2.3.3) and the one in Pico prot (2.3.5) and there are some differences. we need some expert to look at that.

Solar,

i've edited the /system /build.prop in your zip and put the wildfire info instead of Pico info. to be displayed in kitchen when you show working folder info and will be displayed in (about phone) when we mange to get it boot.

you can edit it via gedit (if you using Ubuntu) change the original info with the following:

ro.product.model=HTC Wildfire A3333

ro.product.brand=HTC

ro.product.name=htc_buzz

ro.product.device=buzz

ro.product.board=buzz

ro.product.cpu.abi=arme-a6i

ro.product.manufacturer=HTC

ro.product.locale.langhuage=ldpi
[Wildfire Android Development] Justice™:
Are you using a wildfile kernel with your patches/edits. Try the Eris boot.img if you can.
[Wildfire Android Development] SinawY:
i will have a look at the Eris port

will try to put wildfire's kernel into Eris boot.img and see what will happen?? may it explode?? hehehehehe

we need urgent help with the BOOTCLASSPATH , if you know any dev. who can help, please ask him to check it for us.
[Wildfire Android Development] zexcrazy:
@SinawY, Solar, Justice, etc. Have you considered asking arco for help. After all he is probably the best dev around here for Wildfire. I would ask him myself but i think that one of you could explain him better whats going on.

Edit: Or HCDR.Jacob, but he is not developing for wf any more.
[Wildfire Android Development] Justice™:
Due to the hardware similarities it should be ok. I have no idea about the BOOTCLASSPATH problem though.
[Wildfire Android Development] Justice™:
I'll pm Arco tommorow morning. Unless anyone wants to do it before me.
[Wildfire Android Development] SinawY:
go ahead Justice, and its better to send him a logcat so he can tell us whats wrong.
[Wildfire Android Development] jamal2367:
( BOOTCLASSPATH )

init.rc
[Wildfire Android Development] tazzpatriot:
Guys . I'm one of the devs in the Eris forum.who ported the ROM..if u wanna know how I did it whomever is portin it pm me and tomorrow ill try and help. But please not a bunch of pm just one person please ...tell me what u have done .. can't help tonight but.not sure if u have or not but replace libwebcore.with one from Ur roms to start .that should solve Ur boot loop issue
[Wildfire Android Development] Solar_:
I have an idea for what we can do with the boot.img.

First we can replace the kernel (zImage) and place the init.buzz.rc from SenseOnFire there, remove the init.sapphire/hero/eris.rc and leave the init.rc INTACT. Don't touch it.

Than we can test if it will work.
[Wildfire Android Development] jamal2367:
You have a good idea...

i hope this is the init.rc or init.buzz.rc
[Wildfire Android Development] Justice™:
You may be right. Can anyone get logcats when it goes into a bootloop?
[Wildfire Android Development] kylon:
No!

I didn t think this

I deleted the boot,f.. :'(

Are you sure it can works with bootloop?
[Wildfire Android Development] VigiDroid:
Yep, logcats work through a boot if it is actually booting, if it is bootlooping then run DDMS from the android-sdk, plugin your phone and watch the log! :D
[Wildfire Android Development] kylon:
I don t remenber very well

But i remenber that i have to mod the boot.img to enable the debug option to have a logcat

Right?
[Wildfire Android Development] tazzpatriot:
Please if u want me to try and help I need some info. I don't have time to read Ur thread ro see what u have done..someone asked me to help..there isn't much I can do with.people.sending pm to saying things like

"You say u can help so say it ". And that's it

I'm not gunna answer a pm like this so please if u want me to try and help u I need some help from u like I asked so only a serious person who wants help feel free to pm me ..not tryin to sound like a ass ..:)
[Wildfire Android Development] Justice™:
I'll be trying to get hold of some logcats soon and I'll PM them to you aswell as the information we've gathered in this thread.
[Wildfire Android Development] tazzpatriot:
Already sent pm to someone told them where to start
[Wildfire Android Development] Justice™:
Thats great news. Thanks for your help and support in this. Even though you dont have a wildfire. Its appreciated a lot.
[Wildfire Android Development] tazzpatriot:
It's ok. I don't have a hero and my Eris is deactivated and i still help them too :D
[Wildfire Android Development] kylon:
Ddms doesn t work with a bootloop
[Wildfire Android Development] Karting06:
Hi,

I have tested this: Zimage from Cyanogen and SfF.

init.buzz.rc copied from sapphire, same for init.buzz.rc.

Bootclass path from : sapphire and buzz SFM (Sapphire and here same bootclasspath!).

Now, I will test only bootclasspath from Sapphire.

So, sorry for my bad english !
[Wildfire Android Development] Solar_:
You shouldn't copy the bootclasspath from any other ROM then Sense 3.5.

It's different.

Plus, don't copy the init.buzz.rc, but modify the original one, then rename it to init.buzz.rc
[Wildfire Android Development] Karting06:
I have one time copied it to test. For the rest never :)
[Wildfire Android Development] Solar_:
It's so weird.

I changed everything that I should, but still can't get past the splash screen.

There must be something more important then init.rc, because I modified it like it should be.

Also changed the libs, but no luck.
[Wildfire Android Development] Karting06:
Have you change Keychars en Keylayout.

But then, he doesn't want to install !
[Wildfire Android Development] Justice™:
Why is the keychars and layout relevant, Thats done during setup. Not flashing and installation?
[Wildfire Android Development] kaassaus:
maby than you need put an new update scipt
[Wildfire Android Development] kylon:
i already changed keychars,but nothing happen

i ve a rom with all libs and files replaced from a wildfire rom

but i m in bootloop and i don t know what i can do
[Wildfire Android Development] Justice™:
Thats probably whats up with it. That was the first thing we looked at, and now we've forgotten it with all theese other things we've been editing to edit that.
[Wildfire Android Development] Solar_:
True. Why should we focus on the keychars and layout while it's not booting.. ;)

No. Kartin meant replacing the keychars and layout, not adding them or removing. So you won't need a new update-script ..
[Wildfire Android Development] Solar_:
Are you able to make a logcat? Because VigiDroid said it is possible to make a logcat if the ROM is bootlooping :cool:

If that's true, we can look into the logcat so we can see EXACTLY what's going wrong/on.
[Wildfire Android Development] kylon:
ddms can t connect the phone while in loop

is there an other way?
[Wildfire Android Development] kaassaus:
Solar i have try to do logcats but its says that it mis a file to do a logcat :S
[Wildfire Android Development] jamal2367:
http://www.androidenea.com/2009/08/init-process-and-initrc.html

http://unix.ittoolbox.com/groups/technical-functional/ibm-aix-l/rcinitrc-and-inetd-files-909729

http://androidforums.com/moment-all-things-root/20320-init-rc-recovery-rc-these-worthwhile.html

.....
[Wildfire Android Development] kaassaus:
...............
[Wildfire Android Development] Alyzembawy:
U r sooooo annoying OMG!
[Wildfire Android Development] kaassaus:
wtf i would what to say but i had the wrong thread that could happen:S

go complian on a other if this happen
[Wildfire Android Development] kylon:
someone can help me or only useless post... <.<
[Wildfire Android Development] Karting06:
Hello,

The updater-script is not the problem. The updater-script only installe the ROM. And he is succesfull install. So, it's another problem.

I think that we must analysing, the boot.img from the Desire HD and the Sapphire and so change something to have anything that's work on buzz (I know, I am too bad in English)
[Wildfire Android Development] jamal2367:
maybe that helps?

on init

sysclktz 0

loglevel 3

# setup the global environment

export PATH /sbin:/system/sbin:/system/bin:/system/xbin

export LD_LIBRARY_PATH /system/lib

export ANDROID_BOOTLOGO 1

export ANDROID_ROOT /system

export ANDROID_ASSETS /system/app

export ANDROID_DATA /data

export EXTERNAL_STORAGE /sdcard

export BOOTCLASSPATH /system/framework/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/framework/android.policy.jar:/system/framework/services.jar

Perhaps the framework files overwritten sense of 2.1?
[Wildfire Android Development] Karting06:
And? What do you mean ?
[Wildfire Android Development] jamal2367:
Perhaps the (bootclasspath) differences framework files?
[Wildfire Android Development] Karting06:
I hope.

I think, In 3.5, there are more files, so they are more files that must to be on when the phone goes on.

Is it that that you mean !?
[Wildfire Android Development] Justice™:
So that means because of file differences, we cant use whatever files we could from SFM/SenseOnFire?
[Wildfire Android Development] kaassaus:
i think that noting going to change if you put somting from a sense 2.1 rom to a 3.5 sense rom but maby i make a misstake :S

maby you cant port sense 3.5 to the wildfire because its not having a gpu
[Wildfire Android Development] jamal2367:
only the files that are sense of 2.1, but we write about?

Lets see what happens then
[Wildfire Android Development] Justice™:
We're trying the droid eris port. That has no GPU but the right screen resolution (320x480).

The screen resolution is irellevant in this.
[Wildfire Android Development] Solar_:
That's not true what you said. You can port almost every ROM you want but it won't be as snappy as a normal WF ROM. It's because of the GPU we're missing ):
[Wildfire Android Development] zexcrazy:
Of course that nothing is going to change. It still wont boot. Try to put eclair files in gingerbread and see what happens.
[Wildfire Android Development] jamal2367:
i cant wait this rom . this is exellent

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

it is up to the boot.img of nothing else .......

the bootclasspath ...

I hope there will soon be a solution!
[Wildfire Android Development] SinawY:
guys you all thinking about the difference in sense versions(2.1 & 3.5)

and forget an important thing which is the android version:

Sense on fire is 2.3.3 and what we trying to port is 2.3.5

the BOOTCLASSPATH differs from android version to another so:

just copying it from 2.3.3 to 2.3.5 won't work

AN IDEA: check the BOOTCLASSBATH in CM nightly 2.3.5 and edit it if you can and add htc files paths just like in Eris port.
[Wildfire Android Development] VigiDroid:
Heres an idea, why don't you instead of trying to port the direct .zip from the RUU why don't you port the eris port to the buzz? Since the eris boots and it has no GPU like the wildfire then maybe you could open the boot.img make some adjustments (like renaming the file to init.buzz) and then try booting it?
[Wildfire Android Development] Justice™:
I think that's what solar had been trying with the Eris port developer. I have no idea since everyone posts their ideas and progress without telling us which port or zip they are using
[Wildfire Android Development] tazzpatriot:
i told him to dl mine from the eris or the hero im working with the hero guys also ,, dont use the pico ,, we had issues also
[Wildfire Android Development] Karting06:
There is no sense and in the bootclasspath are files from sense. But I will test that

That we tried to.
[Wildfire Android Development] Solar_:
I didn't tried the Eris port yet, only Pico RUU (like 20+ times).

I think the Eris port is the best option for now ;)
[Wildfire Android Development] Karting06:
Okay, bootclasspath from cyanogenmod doesn't work...
[Wildfire Android Development] Solar_:
Guys, guys, listen. I've something very important to say :

- Don't continue with the Pico RUU, some other team in Hero section also had those problems, they couldn't make it boot (like we also can't boot it right now).

BUT some experienced developer from a Chinese forum (

idogx

) modified it so it booted for the HTC Hero. :cool:

So if we port any port, then we can make it boot because the biggest boot issue is solved by a Chinese forum member.

I have permission to port this ROM : (Zero Hero) http://xdaforums.com/showthread.php?t=1287844.

Plus they got many things working (gps, bluetooth) that are important! :D

So guys, download that ROM, BUT GIVE THE CREDITS ONCE IT BOOTS.

Now I'm going to edit that ROM. :rolleyes:
[Wildfire Android Development] Karting06:
Okay, I will test it :)
[Wildfire Android Development] Solar_:
You should do this. Thanks tazzy for ur help :D
[Wildfire Android Development] Justice™:
Great news solar! It seems we are finally going to get this Rom to work
[Wildfire Android Development] vilks:
when can we expect this rom will be full working?
[Wildfire Android Development] 3xeno:
Dec 22nd 2012.

A useless answer to an equally useless question.
[Wildfire Android Development] VigiDroid:
I was more thinking 30th of February but you can make your predictions :P
[Wildfire Android Development] tazzpatriot:
yea u can port it bro,, my team suicide and the team Hydra worked together on both , just post credit in the op , hope it works bro :D
[Wildfire Android Development] Karting06:
It doesn't boot ;(

Zerohero with buzz modification doesn't want to install.

Pico with boot.img zerohero + buzz modification => doesn't boot.

Pfff...
[Wildfire Android Development] tazzpatriot:
doesnt wanna install? as in not loading ? rebooting? pico didnt boot for us either
[Wildfire Android Development] mtnhan1996:
dude , U watch too much HBO :cool:
[Wildfire Android Development] Solar_:
People like you shouldn't deserve this ROM at all even when it's fully working. ;)

Just be quiet, and wait.

We have no ETA, and that's kind of impossible now, since it's not booting (but who knows :D).
[Wildfire Android Development] Justice™:
It's done when its done. Read the thread if your desperate to know progress.
[Wildfire Android Development] Karting06:
In CWM, he says. Finding update package, opening update package and then back in the main menu...

I think you know more then us for the ROM ! (if he boot or not...)
[Wildfire Android Development] Justice™:
Restart and see if it works? Sometimes my CWM will randomly go back to the menu with no reason for it.
[Wildfire Android Development] kaassaus:
hey guys are you really sure that it will works in the wildfire?

maby it cant boot because wildfire can handel it :(
[Wildfire Android Development] Karting06:
Really ? I will test it back. (roh, english...)

I hope that isn't it so...
[Wildfire Android Development] Solar_:
No. I'm just being positive. Once it'll boot, so..

I also tried the Zero Hero, changed /system/lib/hw, /system/lib/modules, build.prop, boot.img, init.heroc.rc to init.buzz.rc and edited, new kernel, left init.rc intact.

Same did with the Eris port, no luck :(

Still can't get past the splash screen. Not even a bootloop :(

What the hell is this..
[Wildfire Android Development] Karting06:
;(;(;(

The pico rom is a base from Wildfire S. But the Wildfire S can not be port to the Wildfire. So what we can do ? HCDR.Jacob ? Can he help us ?
[Wildfire Android Development] Alyzembawy:
Just a small remark, maybe a stupid one, but it has previously caused me some problems...

Did you wipe everything EVEN DALVIK CACHE before flashing?!
[Wildfire Android Development] Karting06:
Yes, I do this but ;(
[Wildfire Android Development] jamal2367:
its not work with your tip
[Wildfire Android Development] Alyzembawy:
Guys you got me wrong, I was talking to Solar_ because he's got the version which may boot, but the version uploaded on the thread can't and WON'T boot no matter what you do...
[Wildfire Android Development] Karting06:
What can we do ?

Nothing works !
[Wildfire Android Development] Justice™:
Has anyone got in contact with some of the bigger wildfire developers. (HDCRJacob and arco)
[Wildfire Android Development] Karting06:
I don't know, but I will do it.
[Wildfire Android Development] Solar_:
Yeah the uploaded version was actually the rom.zip from PicoRUU and modified some things, but I'm not using that one.

And yes, I wiped data/cache/dalvik cache, everything .. ;)

But it isn't booting.
[Wildfire Android Development] kaassaus:
solar do you have try everting if it is so then we can maby forgot about sense 3.5 :S
[Wildfire Android Development] Justice™:
Corrected:

Can we create a hybrid rom of Sense 2.1 and 3.5. Possibly using the UI elements from Sense 3.5 and the core files and such from sense 2.1
[Wildfire Android Development] jamal2367:
was my suggestion from yesterday
[Wildfire Android Development] Karting06:
Why not ?

I have a idea, in the Bootclasspath: why we set no al the files from /system/framework ?!