Related
with people talking about porting builds etc now i thought i would ask the question in a new thread that a lot of people have been asking but no one has yet to explain totally to us who want to learn how to do this stuff.
What exactly is the difference between a boot image from 32A and a 32B boot image? Is it in the kernel or is it in ramdisk or the init.sapphire.rc? Or none of the above?
I extracted a boot image last night but got stuck repacking it- i will eventually figure this out (when the wife forgives me for spending so long on it last night ). I could see all the different files in it (i extracted cyanogen's boot.img)... maybe if someone had a bit of free time they could write a tutorial for recompiling a boot.img for either 32A or B?
I just think that the more help we offer to people the more cooks we will eventually have and this can only be a good thing for those of us with a Magic/Sapphire in the future.
Thanks
1. The kernel is different (32B google kernels will not work on 32A boards)
2. The offsets for repacking are different => Read this, and if you want more details including an example read this
Amon_RA said:
1. The kernel is different (32B google kernels will not work on 32A boards)
2. The offsets for repacking are different => Read this, and if you want more details including an example read this
Click to expand...
Click to collapse
OMG been looking for that very helpful.... thanks so much!
thanks for that. I will probably just use your build anyway but i would like to learn still
It would be great if a mod could please sticky this so that we do not continue to get random threads and confusion.
I have decided to make this thread because there are a LOT of EBI1 users out of the loop, i my self just a few weeks ago (after 3 months) learned that EBI1 users can use more than just cyano.
Ok, with the recent rogers mandatory update the EBI1 community has grown quite a bit.
You may be wondering what is EBI1?
well, it is the radio version 3.22.26.17, this radio is on the rogers dream and on sapphire/mt3g/magic phones as well.
On the dream it is known as EBI1/32b on the magic it is EBI1/32a
You can check to see if you have the EBI1 radio buy booting into fastboot mode(hold camera when booting) and look where it shown radio. If it says 3.22.26.17 on the screen anywhere, you are EBI1.
If your phone falls under the EBI1 category you have a few options
1) you can go to www.briancrook.ca and use any EBI1 kernel ports from his website. He is the guru of EBI1 ports and will have the most trustworthy of ports.
2) You can visit the sapphire dev forum (on xda (just below the dream/g1 forum)) Here you can download any kernels ports that are listed as 32a or old radio. The old radio/32a sapphire has the same EBI1 radio as the rogers dream!
3) OR most importantly, you can make your OWN ports using this simple tool:
http://faruq.yandao.com/magicport/
We can credit arctu for this amazing tool!
-just extract the rom you want to use
-in the extracted folder you will see a boot.img
-in the program browse and select the boot.img
-choose your settings (minimal is optimal)
-It will create you a EBI1 kernel!
there is a discussion of this tool in the sapphire dev forum.
you may now be asking, what do I do with the port file?
Well, once you get your kernel port,
-You go into recovery (preferably amon because you can flash multiple zip files)
-Flash the desired ROM
-Flash your Kernel Port
-You're done!
We must also be careful when it comes to recovery images
Your recovery is an amazing tool and can save your phone from disaster. Remember: always make a nandroid (or nandorid +ext3) backup before flashing a new ROM!!!!
My personal favourite recovery is Amon's, it is great because it has all the features you could ever want, plus it is great for EBI1 users because you can easily flash multiple zip files without rebooting (which is what you do when flashing ROMs on an EBI1 phone)
You must be careful what recovery you install
EBI0 recoveries are not compatible with the EBI1 radios, you can BRICK your phone, when installing a recovery make sure you install the EBI1 version
With Amon's recovery the EBI1 version is the "R" version. A direct download to the recovery is here:
http://rapidshare.com/files/32033517...am-v1.5.2R.img
I would highly suggest visiting his thread for instructions on use and installation:
http://forum.xda-developers.com/showthread.php?t=566669
G1 devs please listen up:
Inorder to run your ROMS on EBI1 phones we need to make a kernal to flash over the ROM. This means that your existing kernel will be replaced, this is always a negative for us as your kernels create large improvements.
One method you can use to help reduce the gap between you regular rom and an ebi1 version is to:
1) Optimize your ROM to run at its best without any special kernal adjustments
***2) If your ROM utilizes the 10MB ram hack, please also release a non ram hack version.
The reasoning behind this is that the ROM is ment for the ram hack so 3d and hq doesn't work properly on the ROM, when we flash our EBI1 kernel over the ROM, the ram hack is gone. The result is a ROM which has the set backs of the 10MB hack (no 3d, no HQ) AND it DOES NOT get the positves if the hack (we do not get the extra 10MB)
3) Create your own EBI1 ports
thanks to ottawanate:
minimum requirements for porting a ROM to EBI1 are
1) wlan.ko patch or wifi wont work
2) boot.img with Kernel config file marked for CONFIG_MSM_AMSS_SUPPORT_256MB_EBI1=y
Please consider the now vastly larger EBI1 community when making your ROMS, thank you!
Here is a list of Devs who the EBI1 community applauds for making showcasing their EBI1 compatibility friendliness:
King Klick
enomther
If you are a dev and would like to be added to the list please post here and let me know or PM me. (with a link preferably to the page with your ROM/Kernel)
What is EBI1
EBI1 is actually a term derived from the kernel config file. When the line 'CONFIG_MSM_AMSS_SUPPORT_256MB_EBI1=y' is set, the kernel supports 32A Magics and the 3.x series radio.
The kernel itself sits in your boot partition. Typically you flash a boot.img file to your phone to install the kernel. The kernel boots up your system after the boot launcher.
So I prefer to call the 3.x series radio the EBI1 kernel radio, since EBI1 refers to support for 32A Magics as well.
Any 3 series radio needs the EBI1 kernel. So that would include 3.22.20.17. There's another one floating around and installed stock on some 32B Magics (notably from Europe).
If you have the source code of the rom you want to flash, you can build your own kernels by following the instructions here:
http://wiki.cyanogenmod.com/index.php/How_to_build_a_kernel_port
What to pay attention to if I have a 3.x series radio and need the EBI1 kernel
Well first of all you need a ROM with the EBI1 kernel. First of all, the kernel itself is located in your 'boot' partition. Hence you need to be careful when flashing any update.zip files from recovery, because they may overwrite your EBI1 kernel, if it contains a boot.img. To make sure, just open the zip file to view its contents before you flash it. For example, the RAM hack requires a different kernel than the original, and application of it necessitates that you flash a new boot.img. However all the boot.img RAM HACK kernels are being provided without EBI1 support.
In addition to the kernel itself, the wireless drivers need to be recompiled to make it work with the different kernel. This file is wlan.ko. If you do not have a compatible version installed, your wireless lan will not function, which can cause your phone not to boot properly into the system, as it would freeze trying to startup your wireless lan.
The kernel goes hand in hand with your system rom to make your phone work. So if you update your system rom, you typically have to update your kernel as well.
It would be also useful to note that having the 3.x series radio requires you to have a different recovery image than if you didn't have the radio.
What happens if I install the wrong one?
Installing the wrong kernel is not destructive to your phone. If you have the wrong kernel installed, your phone will freeze after the first boot screen (non-animated). Don't worry about installing the wrong kernel.
What if I want to change to the 3.x series radio from the 2.x series radio or vice versa?
Changing to the 3.x series radio does have advantages for certain people. However, changing the radio is can brick your phone if you do not have the correct recovery flashed before changing your radio. There should be ample information on xda to help you with this process.
Other Stuff
The current active roms with EBI1 ports that I know of that work on my Rogers Dream:
Super D
Cyanogenmod
OpenEclair
Question to the OP: Does the WesGarner EB1 kernel include the 32b/dream RAM Hack?
very nice addition, to the post!
I have not personally tried a wes ROM before but i am going to assume that it does not, if anyone knows please telll us!
This thread http://forum.xda-developers.com/showthread.php?t=624545&highlight=ebi1 says I need DangerSPL first. If I used cyanogen wiki here http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod to change my spl will it work?
U can add my AOSP 2.1 to the ebi1 support list
the no wipe update for it is in my op
kingklick said:
U can add my AOSP 2.1 to the ebi1 support list
the no wipe update for it is in my op
Click to expand...
Click to collapse
I added your name to the OP as an applauded dev by the EBI1 community.
Used http://faruq.yandao.com/magicport/ to port this ROM, using the No-Wipe update for No RAM Hack kernel. Worked perfectly! Thanks to King Klick, asb123, and Faruq!
Zoltair Wright said:
Used http://faruq.yandao.com/magicport/ to port this ROM, using the No-Wipe update for No RAM Hack kernel. Worked perfectly! Thanks to King Klick, asb123, and Faruq!
Click to expand...
Click to collapse
how is that ROM in terms of 1)speed 2)stability when compared to the eclair ROMS?
also, what exactly do you mean you used the no ram hack kernal, did u flash ROM, flash the no ram hack kernal, then flash the ebi1 kernal you made? if so, i think that would just over right the no ram hack kernal.
Or does the kernal GIVE it ram hack? thus the ROM itself doesnt have the hack built in?
on a side note:
I want to run a hero ROM but I think they are 1.5 based so I cannot use the tool on them. If anyone has any info on getting a Hero ROM working on EBI1 plz let us know.
Macmee said:
This thread http://forum.xda-developers.com/showthread.php?t=624545&highlight=ebi1 says I need DangerSPL first. If I used cyanogen wiki here http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod to change my spl will it work?
Click to expand...
Click to collapse
yeah, you are going to need the danger SPL, you can follow that guide right there to get it. 1) Do you have root? if so all you need to do is skip to the part about flashing the spl zip file. if you have root i am going to assume to can get into recovery, 2) make sure you have amon's recovery (it makes things so much easier because with ebi1 you need to flash multiple zip files to get up and going at once.
please answer #1 and 2
For what its worth
I use a HTC Dream from Roger's on AT&T here in the US.
At first I used the tmobile radio 2.xxxx.
Then I read that there are higher speeds with the Rogers Radio (3.xxxx) while on EDGE.
I have done side by side tests, and at least for me, there was not a considerable speed change between EDGE speeds on either radio.
So for now, Im back to the tmobile radio.
does this mean all the lousy 32a users can use supported ROMs NOW?/ lol I dont want them all over here now, they are all snotty about G1 users being over in the Sapphire Section
Hi everybody
I just have a Dream Rogers, I have root and installed 4.2.14.1 Cyanogen. My radio is 3.22.26.17 and the SPL is Haykuro 1.33.2005 . Now I want to try the other rom requires 2.xx radio and a different SPL, I can change them or not ?
Please help me because I want to try the other 2.0 2.1 roms but not more experienced, I'm afraid to brick my phone.
Thanks so much.
asb123 said:
yeah, you are going to need the danger SPL, you can follow that guide right there to get it. 1) Do you have root? if so all you need to do is skip to the part about flashing the spl zip file. if you have root i am going to assume to can get into recovery, 2) make sure you have amon's recovery (it makes things so much easier because with ebi1 you need to flash multiple zip files to get up and going at once.
please answer #1 and 2
Click to expand...
Click to collapse
1) I have root. I followed the rogers cyanogen guide by the book so that's currently exactly what I have. Can I just flash directly to this rom?
2) I don't know how to get amons recovery.
ok, so if yo have root u probably have a recovery image (cyanogen) you want to get amons,
go here:
http://forum.xda-developers.com/showthread.php?t=566669
download the R version, i would probably use the via terminal instructions as i think they are the easiest!
once you have that come back here.
Raziel2 said:
Hi everybody
I just have a Dream Rogers, I have root and installed 4.2.14.1 Cyanogen. My radio is 3.22.26.17 and the SPL is Haykuro 1.33.2005 . Now I want to try the other rom requires 2.xx radio and a different SPL, I can change them or not ?
Please help me because I want to try the other 2.0 2.1 roms but not more experienced, I'm afraid to brick my phone.
Thanks so much.
Click to expand...
Click to collapse
when it says you need 2.xx radio, it is usually false, what it should say is that you need the latest radio (ebi1 works)
you dont need to change anything to work a 2.1 ROM, just follow the instructions in the original post, if you do not yet have amon's recovery, follow the post above this.
p.s. I dont think you can change the radio now that you have flashed your SPL, it will BRICK yor phone.
nicknowsky said:
does this mean all the lousy 32a users can use supported ROMs NOW?/ lol I dont want them all over here now, they are all snotty about G1 users being over in the Sapphire Section
Click to expand...
Click to collapse
well, the only reason they focus in the sapphire section is because nobody took charge and made a EBI1 thread in the g1 section, we could always use "supported roms" we just needed kernels.
asb123 said:
ok, so if yo have root u probably have a recovery image (cyanogen) you want to get amons,
go here:
http://forum.xda-developers.com/showthread.php?t=566669
download the R version, i would probably use the via terminal instructions as i think they are the easiest!
once you have that come back here.
Click to expand...
Click to collapse
Ok. What about SPL, will the one from the cyanogen tut work?
yeah, follow that guide for your SPL, if you have root i think you can just skip the first part (as its about getting root, if i remember correctly)
asb123 said:
yeah, follow that guide for your SPL, if you have root i think you can just skip the first part (as its about getting root, if i remember correctly)
Click to expand...
Click to collapse
erm. Follow what guide?
once you have root and have amon's recovery,
go here:
http://wiki.cyanogenmod.com/index.p...ers_Dream_EBI1_to_CyanogenMod#SPL_Replacement
skip down to the SPL replacement part to get the 1.33.2005 SPL
Sorry if this is already being discussed in our G1 forums, had a look but one thread created was closed (therefore hope I'm not doing something I shouldn't be by opening this one, apologies if so!)
I found the link for an untouched OTA Froyo update for the myTouch 3G:
http://android.clients.google.com/packages/ota/tmobile_opal/e059adc603a3.signed-opal-ota-60505.e059adc6.zip
I read the forum over there and they talk of perhaps needing another file, as the update supposingly comes in 2 parts. Is it the case that we need a different radio/spl etc? What is the next step for us?
Hopefully one of our genius developers can get this working and ready to flash on our G1's, an official Froyo!
Wohoo!
Well it looks like it's flashable OOTB. It does contain a new radio image, but I'm not sure how that would work with 1.33.2005/whatever safe SPL is...
I guess stage one is removing the radio and flashing?
Then testing the radio with engineering SPLs?
AdrianK said:
Well it looks like it's flashable OOTB. It does contain a new radio image, but I'm not sure how that would work with 1.33.2005/whatever safe SPL is...
I guess stage one is removing the radio and flashing?
Then testing the radio with engineering SPLs?
Click to expand...
Click to collapse
Im not too sure myself, hopefully the Dev's seethis soon and offer their input on how we get this working on our devices!
cd993 said:
Im not too sure myself, hopefully the Dev's seethis soon and offer their input on how we get this working on our devices!
Click to expand...
Click to collapse
Im guessing they are either working on it now or we are the only ones home on a sunday afternoon lol
All the magic (pun intended) seems to be going on in this thread.
From what I've looked at thus far:
The kernel is built from the latest update in ASOP; at a new starting offset. Since the Dream source has no code to backup this alternate offset; and no configuration for trout in the ramdisk the new rom has the boot image will not work.
You can try to take the rom w/o radio/hboot and run it on a CM6 kernel.. this may operate.
As for the radio update.. it works with 1.33.2003/1.33.2005 as any 2.22.x radio however cm6 kernels fails to initialize the 3d graphics region that the radio moved and the phone reboots (RA-Recovery and adp1 1.6 rom boots without issue on the new radio)
Last HBOOT.. its a perfected HBOOT (it will work on the dream with a 2.x radio so dangerSPL rules apply) however if you are not very very careful you can get stuck..
In short at the very least some coding it required to get the same benefits as the Magic users will have.
I'm really excited bout this...perhaps recompiled with latest nightly CM kernel could work....!!!
ezterry said:
From what I've looked at thus far:
The kernel is built from the latest update in ASOP; at a new starting offset. Since the Dream source has no code to backup this alternate offset; and no configuration for trout in the ramdisk the new rom has the boot image will not work.
You can try to take the rom w/o radio/hboot and run it on a CM6 kernel.. this may operate.
As for the radio update.. it works with 1.33.2003/1.33.2005 as any 2.22.x radio however cm6 kernels fails to initialize the 3d graphics region that the radio moved and the phone reboots (RA-Recovery and adp1 1.6 rom boots without issue on the new radio)
Last HBOOT.. its a perfected HBOOT (it will work on the dream with a 2.x radio so dangerSPL rules apply) however if you are not very very careful you can get stuck..
In short at the very least some coding it required to get the same benefits as the Magic users will have.
Click to expand...
Click to collapse
ezterry, join us here http://www.stinto.net/pages/chat.htm?id=4hlqu
and anyone else who wants to/is knowledgable
ezterry said:
From what I've looked at thus far:
The kernel is built from the latest update in ASOP; at a new starting offset. Since the Dream source has no code to backup this alternate offset; and no configuration for trout in the ramdisk the new rom has the boot image will not work.
You can try to take the rom w/o radio/hboot and run it on a CM6 kernel.. this may operate.
As for the radio update.. it works with 1.33.2003/1.33.2005 as any 2.22.x radio however cm6 kernels fails to initialize the 3d graphics region that the radio moved and the phone reboots (RA-Recovery and adp1 1.6 rom boots without issue on the new radio)
Last HBOOT.. its a perfected HBOOT (it will work on the dream with a 2.x radio so dangerSPL rules apply) however if you are not very very careful you can get stuck..
In short at the very least some coding it required to get the same benefits as the Magic users will have.
Click to expand...
Click to collapse
one point of your thing here is wrong. i don't know about the others, they're probably right knowing you.
In the chatroom i posted, I successfully booted this ota with a cm kernel. duh.
I also booted a cm kernel WITH the tmobile-provided ramdisk. weird.
jcarrz1 said:
I also booted a cm kernel WITH the tmobile-provided ramdisk. weird.
Click to expand...
Click to collapse
I'm a bit surprised about this... but all that is needed to correct any issue is a init.trout.rc (seems most of the needed init logic is in init.rc)
we need a working sense ui 2.2 rom with bluetooth and touch focus
ezterry said:
I'm a bit surprised about this... but all that is needed to correct any issue is a init.trout.rc (seems most of the needed init logic is in init.rc)
Click to expand...
Click to collapse
that's it?? and then the tmobile kernel will work on a g1?
XIPRELAY2010 said:
we need a working sense ui 2.2 rom with bluetooth and touch focus
Click to expand...
Click to collapse
I guess i heared theat somwhere...:-D
sorry for OT...
jcarrz1 said:
that's it?? and then the tmobile kernel will work on a g1?
Click to expand...
Click to collapse
no the ramdisk will.. the kernel is compiled without dream support.. and at a different offset than usual.. this will take some poking and re-build from asop to make a similar kernel.. the problem with using the CM kernel is I suspect that there is additional ram make available by the new radio+kernel configuration.
so what do i have to download and what do i have to do with it, to run it on my G1?
ezterry said:
no the ramdisk will.. the kernel is compiled without dream support.. and at a different offset than usual.. this will take some poking and re-build from asop to make a similar kernel.. the problem with using the CM kernel is I suspect that there is additional ram make available by the new radio+kernel configuration.
Click to expand...
Click to collapse
I agree on that speculation... you mean you haven't tried it yet? i thought you did...
jcarrz1 said:
I agree on that speculation... you mean you haven't tried it yet? i thought you did...
Click to expand...
Click to collapse
I tried and failed to boot the kernel on a dream; and I looked at the source code; and noted the new boot offset.. Just booted it with a CM kernel now
Edit: Camera works, seems smooth.. wifi error.. need to inject root
woot, thank you!
XIPRELAY2010 said:
we need a working sense ui 2.2 rom with bluetooth and touch focus
Click to expand...
Click to collapse
No we don't.
ezterry said:
I tried and failed to boot the kernel on a dream; and I looked at the source code; and noted the new boot offset.. Just booted it with a CM kernel now
Edit: Camera works, seems smooth.. wifi error.. need to inject root
Click to expand...
Click to collapse
is there any improvement on memory/memory management with this change?
*32a New Radio 6.35 Sapphire/Magic only*
magic 32a old radio here http://forum.xda-developers.com/showthread.php?t=776929
g1/32b magic here http://forum.xda-developers.com/showthread.php?t=776922
------------------------------------------------------------------------------
Well I managed to figure out with a lot of reading and sleepless nights compiling source how to build a recovery for you PS3 guys.
It's based wholly on PSFmod recovery for hero.
Thanks klutsh for the git source. Thanks kakaroto for the pl3 source. Thanks Cyanogen for the kernel source(I'm using my modified 6.35 CM kernel)
I posted this in my kernel thread and those that tried it say it works, I have no PS3 myself.
If you let me know about updates in this thread I can re-compile for you.
PSFreedom Recovery for New Radio Sapphire
MD5: 1a8a1e063fc9af5efb3ec780d9b802bd
Here are the custom bins that I compiled with psfreedom pl3 bins
psfmod for 32A
hey man once again,
a few minutes ago i tried to load a custom payload from here -> http://www.psfreedom.com/wiki/HTC_Hero with u'r recovery, but it gives me an error.
i've checked the error log and it seems to be something related with this: -> PSFreedom gadget: Error: Payload size is more than the maximum allowed of 3808
i attach here my error log, it will possibly help you
thanks in advance
H3llSp4wN said:
hey man once again,
a few minutes ago i tried to load a custom payload from here -> http://www.psfreedom.com/wiki/HTC_Hero with u'r recovery, but it gives me an error.
i've checked the error log and it seems to be something related with this: -> PSFreedom gadget: Error: Payload size is more than the maximum allowed of 3808
i attach here my error log, it will possibly help you
thanks in advance
Click to expand...
Click to collapse
Oh those aren't compatible, I compiled all the payloads myself, I guess I should post them. Back in a bit.
Edit: some on that page are ok, the pl3 ones of kakaroto
so.. what does this do for you PS3 owners?
carz12 said:
so.. what does this do for you PS3 owners?
Click to expand...
Click to collapse
Allow us to enter in recovery mode, being able to load some homebrew.. Most people use it to load "backups"
xiserre said:
Allow us to enter in recovery mode, being able to load some homebrew.. Most people use it to load "backups"
Click to expand...
Click to collapse
ok, something sony should have allowed anyways
carz12 said:
Oh those aren't compatible, I compiled all the payloads myself, I guess I should post them. Back in a bit.
Edit: some on that page are ok, the pl3 ones of kakaroto
Click to expand...
Click to collapse
are the payloads you compiled compatabile with the psfmod for the Evo?? and if so which one includes the hermes v4? I'm just trying to get MOH and MMA working
Young_e said:
are the payloads you compiled compatabile with the psfmod for the Evo?? and if so which one includes the hermes v4? I'm just trying to get MOH and MMA working
Click to expand...
Click to collapse
It looks like just one set of payload files for all the psmod recoveries, but I have no idea what is what with those, I don't even own a ps3
it's work on 32b???
I get paranoid about flashing anything other than roms so I'd just like to double-check with someone who's done it.
I have a Roger's HTC Dream, with RA-dream-v1.5.2R, Radio-3.22.26.17, and hboot-1.33.2005. From what I remember, it's a 32A radio, and flashing Sapphire roms will work ok, but will flashing this recovery image work on this phone or will it produce a brick?
Thanks
capebretonsux said:
I get paranoid about flashing anything other than roms so I'd just like to double-check with someone who's done it.
I have a Roger's HTC Dream, with RA-dream-v1.5.2R, Radio-3.22.26.17, and hboot-1.33.2005. From what I remember, it's a 32A radio, and flashing Sapphire roms will work ok, but will flashing this recovery image work on this phone or will it produce a brick?
Thanks
Click to expand...
Click to collapse
Brick, you have to have the 6.35 radio and matching spl, this is only for new radio sapphire/magic, I though there was a g1 or 32a old radio version in the other thread.
miguelchico said:
it's work on 32b???
Click to expand...
Click to collapse
no it doesnt
what about 32B
i don't see a 6.35 radio for that
do i even need that
will it work?
or has a 6.35 radio for 32B not been developed yet?
Hey Carz, I am using the Magic 32A old radio, I see you added the link up top for it, appears to be the original wich is dated 9/07, or is this for your new comp with the new payloads?
I know that, but I have no old radio device to test on, one of my magics bricked during the 2.1 update of rogers
Is it possible to use the hermes v4b payloads with this recovery?
That sucks, always worrying bout brickin. I have tried flashing both the v3 for 32a and the other one .kAroshi made with the pl3 and both just hang on the htc magic screen. On the recovery screen says 32a, my phone is the mytouch with the 35mm jack, so it is 32a right? Pretty sure it is. Dont remember what I finally flashed with in the first place! Trying to get back to there at least!!
psfmod for 32A
hy guys,
it seems there was released a few days ago a new version of psfmod recovery for hero (psfMod-hero-0.9.7.1.img),i dont know what improvements were made this time. but is there any kind soul who can port this for our 32A devices ?
very grateful once again
H3llSp4wN said:
hy guys,
it seems there was released a few days ago a new version of psfmod recovery for hero (psfMod-hero-0.9.7.1.img),i dont know what improvements were made this time. but is there any kind soul who can port this for our 32A devices ?
very grateful once again
Click to expand...
Click to collapse
0.9.7.1
[27/10/2010]
fixed Eris boot & prop issues
no updates for ours yet, its the pl3 payloads and pl3 itself that gets the updating and I pull from git every morning, nothing has changed yet.
thanks man
I'd like to bring TWRP 2.2 to as many variants of the rather fragmented Sapphire platform as possible. I could use some direction to live repositories containing healthy copies of the kernel and proprietary files for CM7 and any tips developers experienced with this platform might have for building 32A and 32B versions as well as the Frankenstein Fender and 1.2 devices.
I happen to have a Fender to test with but, will need volunteers to test builds on the 32A and 32B devices.
Yaaaaaaay
Sent from my HTC Magic using xda premium
xanda143 said:
Yaaaaaaay
Sent from my HTC Magic using xda premium
Click to expand...
Click to collapse
Well, I'm hoping that will be the response. IF I can get it to build nicely and fit TeamWin will likely take over official support and users will be able to access it via GooManager. Already added the WFS as the first MDPI device and the HeroC was a close second.
Well, last I check teamwin recovery project needs to be built in ics.
tvall said:
Well, last I check teamwin recovery project needs to be built in ics.
Click to expand...
Click to collapse
TWRP can be built in either ICS or Gingerbread and they are working to make sure it builds fine with JB as well; however, it was originally designed around Gingerbread and is often most successful with those sources and I'm not aware of any healthy ICS builds for the Dream or Sapphire. Some encouraging works in progress maybe but, nothing I'd want to build a recovery around.
My ics repo is healthy enough to build recoveries as long as you change the kernel. (Never got it to build in gb) Already started on twrp. Want me to upload what I have?
tvall said:
My ics repo is healthy enough to build recoveries as long as you change the kernel. (Never got it to build in gb) Already started on twrp. Want me to upload what I have?
Click to expand...
Click to collapse
If you have something you think is worth uploading it's beyond me to stop you. As I understand it there are some extremely stable and low bug ports of Gingerbread for the Dream/Sapphire platform and quite the handful of kernels. I've been inspecting the publicly available source for as many kernels as I can as I'm aware supporting each fragment of the Sapphire platform properly can be a little tricky. Having a Fender I'm all too familiar with how barmy the device can behave with a kernel that wasn't designed for it. I've built TWRP in GB and ICS and I know that there have been successful builds using JB. It usually isn't too problematic if you're familiar with the device and source.
The only issue I have with my twrp build is it defaults to using /data as if its the sdcard. Probably an issue with my config files.
tvall said:
The only issue I have with my twrp build is it defaults to using /data as if its the sdcard. Probably an issue with my config files.
Click to expand...
Click to collapse
It might be. I'm not really sure why it would mistake the SD card for an MTD partition without provocation tho. TWRP usually requires minimal configuration. You usually need to accommodate for it's linked nature and to provide the device resolution. It usually only gets crazy when you have extra MTD partitions for things like WiMAX, efs and pds.
If you can pull the log from /tmp and a dmesg there is a good chance I might be able to tell you what's going on.
Well... I'm lazy and you seem to know what you're doing, so you'll probably get it done before I find out what's wrong. I'd love to help you with this project. I also have a fender (actually its my girlfriends, but she let's me mes with it)
Regarding kernels, you should only need one for 32b (and fender), I don't know much about the 32a. And you shouldn't need anything fancy. I would use ezterry's 2.6.34 kernel because it seems incredibly stable.
tvall said:
Well... I'm lazy and you seem to know what you're doing, so you'll probably get it done before I find out what's wrong. I'd love to help you with this project. I also have a fender (actually its my girlfriends, but she let's me mes with it)
Regarding kernels, you should only need one for 32b (and fender), I don't know much about the 32a. And you shouldn't need anything fancy. I would use ezterry's 2.6.34 kernel because it seems incredibly stable.
Click to expand...
Click to collapse
I've always had charging issues with ezterry kernels, the Fender and Gingerbread. It fails to properly recognize the 1A AC charger and quick charge, every time. I believe this is specific to the Fender/1.2 I think the only one I remember working well was some old mod for the fender/1.2 specificly. I'm trying to track it down. I think I'll need a 32A, 32B and Frankenstein 32A/B (Fender/1.2) build to make sure everyone is covered. I believe that this platform uses offmode charging in recovery so it's kinda important that the kernels properly support changing for their host device. I believe the software I'm running now in recovery and system both have flawed kernels as the poor thing takes forever to charge.
They charge while they are actually off. that's handles by either the radio or spl I think. I had a bricked fender that couldn't get into hboot or anything that I used for spare parts and battery charging.
tvall said:
They charge while they are actually off. that's handles by either the radio or spl I think. I had a bricked fender that couldn't get into hboot or anything that I used for spare parts and battery charging.
Click to expand...
Click to collapse
I believe it's using recovery like the Wildfire S. The SPL boots to a special offmode charging state in recovery when the device is supplied power while off-line. There are service binaries to deal with this request in recovery and it will hard-lock the device if it isn't handled properly. I only remember this because this feature was broken much earlier on my device with faulty recovery software and I've since run into issues on a handful of HTC devices that utilise this solution and recovery software that wasn't setup properly.
It's fairly easy to test as all you have to do is disable the feature in the recovery init and it will cause the device to hard lock when it's plugged into a power source. It will illuminate the amber led as if it's charging but, the state will never change and it will remain locked after power is removed. Occasionally the device will panic and reboot but, you usually have to remove the battery to get it to shut down afterwards, especially if the service to detect button presses is also disabled in the recovery init.
The lines I'm talking about look like this:
Code:
service offmode_charging /sbin/offmode_charging
+ disabled
oneshot
service detect_key /sbin/detect_key
+ disabled
oneshot
I also just checked and yes, under the ezterry based kernel currently powering CronMod on my Fender the device fails to properly recognize the 1A input from the AC charger. If I used that source unmodded to build a recovery for the Fender/1.2 offmode charging would take forever. I believe it works fine on 32A and 32B devices, it's only the hybrid 32A/B devices that are afflicted but, as I said I recall a fix having been found I just have to track it down.
It charges with a bad spl/radio flash that can't boot into anything at all. So charging is not handled by the recovery.
tvall said:
It charges with a bad spl/radio flash that can't boot into anything at all. So charging is not handled by the recovery.
Click to expand...
Click to collapse
You'll forgive me if I choose to base my development off of data from the manufacturer and my own experience with numerous HTC devices instead of the behaviour of a broken device I've never seen. As I can reproducibly break offmode charging on the device by flashing a recovery image with the service disabled in the init I find it hard to accept that the recovery partition isn't involved in the process. I find it far more likely that you may have an incompatible radio/hboot combination that doesn't boot but, still loads offmode charging properly as this mode isn't reliant on a healthy SPL/Radio.
Can you get me a recovery with it disabled? I want to test this
tvall said:
Can you get me a recovery with it disabled? I want to test this
Click to expand...
Click to collapse
I'm not sure if I can provide one right away but, I'll gladly provide some for testing. You could also resurrect your lame device with a little JTAG magic. A malformed HBOOT/Radio flash isn't lethal, just extremely inconvenient.
WoefulDerelict said:
I'm not sure if I can provide one right away but, I'll gladly provide some for testing. You could also resurrect your lame device with a little JTAG magic. A malformed HBOOT/Radio flash isn't lethal, just extremely inconvenient.
Click to expand...
Click to collapse
I don't have the tools, soldering skills, or money to jtag. Its lethal if you don't have that.