Related
Again please forgive me if the is noobish but can't find the answered anywhere. I have tried yo flash a few different versions using daz tutorial with replacing the boot.ing file so that swap and apps2sd would work. Ever since then any version of jac hero I use with that boot.ing the WiFi won't turn on. Have tried 3 different wlan.ko files and that didn't work. If I go back to the old boot.img like fatal1ty with enhancements the WiFi works. But I have seenothers get it working on a 32B device. Which mine is the Google io phone. Does anyone know if I am just grabbing a wrong boot.img do I need a different wlan.ko any help would be appreciated. Thank you.
Hi guys,
Over at the HTC Hero forum I have been developing a kitchen to help ordinary people learn how to build their own ROM. It allows you to do basic things such as rooting a shipped ROM, adding apps2sd, modifying the task killer memory threshold, etc.
The appropriate settings are now in place to make it work for the Dream.
Here is the link to the kitchen:
http://forum.xda-developers.com/showthread.php?t=633246
Before you flash your new custom ROM made from this kitchen, please make a Nandroid backup first of your existing ROM!
Thank you, and enjoy!
Working so far on Ubuntu, figures I just learned how to use git and make my own EBI1 kernels 2 days ago, thanks for this. I'll let you know once I flash a rom how it goes.
carz12 said:
Working so far on Ubuntu, figures I just learned how to use git and make my own EBI1 kernels 2 days ago, thanks for this. I'll let you know once I flash a rom how it goes.
Click to expand...
Click to collapse
Cool, thanks. I am most concerned about how the wireless tethering option will work on the Dream because it requires a kernel fix for Android 1.5 and 1.6. The kitchen is supposed to do that automatically but it will replace your existing kernel.
BTW looks like you are from my home town of Edmonton!
It's not booting, I used my own nan sys and boot img's, set up a working directory and then rebuilt, long time at rogers screen and then boot animation for a minute then a blank back-lit screen, I'll logcat and post it later, time for work.
Is this compatible with the EBI1 dream?
dsixda said:
Cool, thanks. I am most concerned about how the wireless tethering option will work on the Dream because it requires a kernel fix for Android 1.5 and 1.6. The kitchen is supposed to do that automatically but it will replace your existing kernel.
BTW looks like you are from my home town of Edmonton!
Click to expand...
Click to collapse
I may need to go to EBI0 to test if it replaces the kernel?
carz12 said:
It's not booting, I used my own nan sys and boot img's, set up a working directory and then rebuilt, long time at rogers screen and then boot animation for a minute then a blank back-lit screen, I'll logcat and post it later, time for work.
Is this compatible with the EBI1 dream?
Click to expand...
Click to collapse
What is different about EBI1 from a kernel level? If all you did was extract the system and boot.img, and then build without modifying anything, then that should work.
EDIT: If this is a customized ROM (e.g. with custom kernel) then the update-script file under META-INF\.... may need some manual tweaking. The Option 1 in the menu is recommended only for stock ROMs, because this option creates a simple generic update-script file.
If you are indeed using a custom ROM then I'd try to get the original update.zip file of this ROM, which already has the correct update-script file. Just copy that update-script into your existing kitchen.
Or even simpler, just use the original update.zip file and run Option 11 instead of the Nandroid backup.
carz12 said:
I may need to go to EBI0 to test if it replaces the kernel?
Click to expand...
Click to collapse
I am not familiar with all the different Dreams, but it will replace the kernel if you have a 1.5 or 1.6 ROM.
It works on my rogers dream, I took the original rom for the g1, set up a working directory, replaced the launcher, took out a few apps, replaced the boot.img and wlan.ko with the ebi1 compatible versions I compiled and put in my own prop files, booted right up, thanks for this. Can't test the tethering thing as it'll change the kernel on me.
dsixda said:
I am not familiar with all the different Dreams, but it will replace the kernel if you have a 1.5 or 1.6 ROM.
Click to expand...
Click to collapse
What would happen if I just replaced the wlan.ko and boot.img-kernel in the dream_1_6_update folder with my ebi1 versions? could I test out the add wireless tether option?
carz12 said:
What would happen if I just replaced the wlan.ko and boot.img-kernel in the dream_1_6_update folder with my ebi1 versions? could I test out the add wireless tether option?
Click to expand...
Click to collapse
I'll try this tomorrow. Looks cool.
downloading now, ill let you know how things go tomorrow.
carz12 said:
What would happen if I just replaced the wlan.ko and boot.img-kernel in the dream_1_6_update folder with my ebi1 versions? could I test out the add wireless tether option?
Click to expand...
Click to collapse
I'm not sure exactly what the modified boot.img-kernel in the kitchen has, but I'm guessing it's a couple of networking-related variables that were changed. If your kernel has those modifications then maybe it will work. Doesn't hurt to try
Let me know if it works, then we can use your version for individuals who are cooking Rogers ROMs.
A question: Is it possible to tell that a ROM is for a Rogers Dream (ie. somewhere in the build.prop)? In that way, the script can automatically decide what action to take.
carz12 said:
It works on my rogers dream, I took the original rom for the g1, set up a working directory, replaced the launcher, took out a few apps, replaced the boot.img and wlan.ko with the ebi1 compatible versions I compiled and put in my own prop files, booted right up, thanks for this. Can't test the tethering thing as it'll change the kernel on me.
Click to expand...
Click to collapse
That's great news so far! Thank you
will ROMs created work with MyTouch 3G
nicknowsky said:
will ROMs created work with MyTouch 3G
Click to expand...
Click to collapse
Lets hope I am setting this up now to try it for my touch 3g
nicknowsky said:
will ROMs created work with MyTouch 3G
Click to expand...
Click to collapse
Since it's the HTC Magic, yes it should! Please try and let me know.
I'll create a thread for this in the Magic forum so that people can post their feedback there. Thank you
EDIT: Here's the thread where you can post Magic/myTouch 3G feedback:
http://forum.xda-developers.com/showthread.php?t=651470
Question...What section on the HTC site would I look for the shipped rom.exe...Specific device = Mytouch?
holmes901 said:
Question...What section on the HTC site would I look for the shipped rom.exe...Specific device = Mytouch?
Click to expand...
Click to collapse
Just do a search in XDA for Mytouch/Magic shipped ROMs. Usually there are links to the original ROMs in the Wiki page for your device.
dsixda said:
I'm not sure exactly what the modified boot.img-kernel in the kitchen has, but I'm guessing it's a couple of networking-related variables that were changed. If your kernel has those modifications then maybe it will work. Doesn't hurt to try
Let me know if it works, then we can use your version for individuals who are cooking Rogers ROMs.
A question: Is it possible to tell that a ROM is for a Rogers Dream (ie. somewhere in the build.prop)? In that way, the script can automatically decide what action to take.
Click to expand...
Click to collapse
I'll try it out tonight, the sources I used to compile were wes's and his kernel has tethering support unless I broke it, I've never used tethering before.
carz12 said:
I'll try it out tonight, the sources I used to compile were wes's and his kernel has tethering support unless I broke it, I've never used tethering before.
Click to expand...
Click to collapse
Tethering is actually useful even if you don't need it all the time, eg. if your desktop PC cannot access the internet or your wife is using an iPod touch to access the internet in a restaurant.
So do Rogers Dreams require a special kernel, due to the 911 fix? So I guess the stock ROM update has the proper kernel, but modifications like the wireless tether for a Rogers Dream would require a patched Rogers kernel.
Edit: wasn't even aware of the ROM kitchen before this.
Untested! I don't plan to provide support for these ports!
The reason I am publishing is from my recent trials of compiling my own kernel for new radio 32A Magic. I have learned a lot about what sanpei's kernel consists of and the similarities between our device and the GSM Hero. In particular, the only difference between our ROMs seems to be mainly just the kernel. Everything else is almost identical. As such I want the community to try to use a tested NR kernel, sanpei's 2.6.32.9, and apply it to some different ROMs and report back with results.
We don't need multiple threads of the same kernel on different ROMs. So I'm trying to consolidate some information here.
I can test it on my cousins phone probably this weekend as well. Hoping for some preliminary results till then.
sanpei2.6.32.9_villain_port
This is a repack of sanpei's kernel repacked via ordinary boot.img method, with init.hero.rc copied to init.sapphire.rc
Flash this after you flash Villain ROM:
http://www.villainrom.co.uk/viewtopic.php?f=44&t=680#p11789
2.1 Sense UI ROM
sanpei2.6.32.9_anykernel.zip
This is a repack of sanpei's kernel repacked via Koush Anykernel
The idea is that you can flash most ROMs from old radio using this port with some caveats.
READ THIS BEFORE YOU FLASH
You cannot use this port if:
1) You are NOT on a 6.35 series radio. This rules out any 32Bs or myTouch 1.2
2) the ROM uses squashfs anywhere (open up the update.zip of the ROM and look at /system/modules/lib and /system/
3) modules have special directory structure under /system/modules/lib (such as Cyanongenmod, which has modules under 2.6.xx.x-cyanogenmod instead of just 2.6.xx.x)
4) you use an ext4 apps2sd partition (it will simply not recognize it)
Explanations:
If the ROM uses squashfs, this kernel does not support it and you will need to fix those problems yourself.
There may be other issues involved when you use this kernel. It is recommended that you stick to the one that came with the ROM.
This rules out any Cyanogenmod because of the use of squashfs.
If missing init.sapphire.rc, copy the Hero one (if flashing a Hero ROM) using:
adb shell cp init.hero.rc init.sapphire.rc
Refer to the ROM Bible for reference:
http://forum.xda-developers.com/showthread.php?t=682243
Any new or old ROMs that already use new radio
This is just the kernel carz12 posted repacked:
http://forum.xda-developers.com/showthread.php?t=689652
Credits:
cyanogen for everything
Koush anykernel
sanpei for his version of AOSP kernel with integrated new radio support
And a lot more I might be missing
FYI and FWIW a few weeks back there were a lot of 6.35 roms that were cooked and posted in this forum. They were all using the 2.6.32.9 kernel that Sanpei ported. That is, the boot.img-kernel was the same for all. The ramdisk was changed as you have done and the two were re-packed into the boot.img.
I have successfully applied this approach for maybe 3 or 4 different 1.6 roms and maybe 10 different 2.1 roms.
dsixda's ROM Kitchen makes executing these steps a piece of cake
http://forum.xda-developers.com/showthread.php?t=633246
Then you just replace the wlan.ko module and GPS lib file for wifi and GPS compatibility.
You're probably aware of these details but I thought they might help others.
Tried to flash VillainROM 6.1, but during the flash it aborts saying "Failure at line 2: assert getprop("ro.product.device") == "hero"
How do I solve this?
pellen said:
Tried to flash VillainROM 6.1, but during the flash it aborts saying "Failure at line 2: assert getprop("ro.product.device") == "hero"
How do I solve this?
Click to expand...
Click to collapse
Must have hero recovery not patched recovery by cursor
Ahh...thougt cursors tweaked recovery didn't differ that much. *change recovery*
I am pretty sure the update script can also be modified. The assert statement can be removed and the rom should load fine on the Hero, Cursor and Amon Ra recoveries.
Ok, so now I've flashed VillainROM 6.1 with the sanpei2.6.32.9_villain_port and I can't say it's working especially well
First of all it doesn't ask me to enter the SIM card PIN when i boot, so the mobile connection is dead. Wifi and bluetooth is dead too. The camera flicker, and then fades to black, taking a pic resulted in reboot.
giant_rider said:
FYI and FWIW a few weeks back there were a lot of 6.35 roms that were cooked and posted in this forum. They were all using the 2.6.32.9 kernel that Sanpei ported. That is, the boot.img-kernel was the same for all. The ramdisk was changed as you have done and the two were re-packed into the boot.img.
I have successfully applied this approach for maybe 3 or 4 different 1.6 roms and maybe 10 different 2.1 roms.
dsixda's ROM Kitchen makes executing these steps a piece of cake
http://forum.xda-developers.com/showthread.php?t=633246
Then you just replace the wlan.ko module and GPS lib file for wifi and GPS compatibility.
You're probably aware of these details but I thought they might help others.
Click to expand...
Click to collapse
I completely missed that post actually . Plus it's now closed.
But I wanted to see specifically how well Hero ROMs translate over to Magic ROMs because of what I've been reading about the similar kernels. The thing is that while I know to copy over init.sapphire.rc to resolve some conflicts, I'm not sure what else is involved in porting a ROM right now to get it to work.
I'm new to porting ROMs.
Maybe mods ought to close this one then?
With Eris ports you will be missing SIM card features.
So with 2.6.32.9 bluetooth and wifi break? I was actually expecting bluetooth to work. What works?
I guess I'll do some reading again. But I haven't seen that information posted regarding how to resolve some of the issues of porting ROMs.
I was looking to figure out some of the incompatibility of the kernel I was compiling so I thought this might help
If the Hero ROMs worked well enough I had the idea of modifying the AnyKernel script to add cpio to recovery by updating busybox so that ROMs can be unpacked, modified and repacked all in recovery. It means unpacking the ramdisk gunzip, modifying it and repacking it, essentially adding one script to AnyKernel. But I guess they don't work that well so
xaueious said:
I'm new to porting ROMs......
I guess I'll do some reading again. But I haven't seen that information posted regarding how to resolve some of the issues of porting ROMs.
Click to expand...
Click to collapse
A lot of the issues when porting are not related to the kernel but to the modules and lib files.
Try testing and hacking through some issues. For example, replace the wlan.ko file in the /system/lib/modules folder with one from a similar rom that is working on 32a same radio version. If you're porting Hero, then pull the wlan.ko from one of Capy's roms.
To get camera working, you'll need to replace the camera related libs in the in the /system/lib/ folder with ones from a similar rom that is working on 32a and so on.
Porting involves, at a minimum, replacing the boot.img-ramdisk and the files for stuff that is not compatible with the 32a hardware, radio version, etc.
Once you figure out these basics by experimenting with swapping out stuff with working pieces from a 32a compatible rom on the same radio version, you can then get into making updates to the files in the boot.img-ramdisk yourself, the update-script, the build.prop files, the init files in /system/etc/init.d, etc.
xaueious said:
Maybe mods ought to close this one then?
Click to expand...
Click to collapse
I think it's a good thread. Maybe some of the guys who have been porting roms will add their comments. I may be wrong but I don't there is a how to guide for porting.
anykernel is useful for a direct kernel port like cm5 to EABI1 on same rom scenarios, nice piece of coding by koush though, way many files to change, an update package would work on roms made for your device(proper assert) but most need the update script modified and at least wlan.ko changed.
testing now Flashing
how long does it take to boot?
Working:
USB
Music app (Sound ok)
Gallery 3D OK takes a while to work
Not Working:
Camara
Wifi
Bluetooth
GSM connection
Issues:
Very very long and slow boot alot of patient is required.
Slow Menu Scrolling
Freezes some times (have to take battery)
Reboots alone sometimes
Hello, since there seems to be some confusion I decided to start this thread for the 32A port.
The G1 / Magic 32B thread is here: http://forum.xda-developers.com/showthread.php?t=776922
Note that all the work on PSFreedom was done by KaKaRoTo, and he was helped by DrMon in the MSM72K port, i merely compiled their work and put it in a simple package for everyone to enjoy.
I created 2 packages, an enabler and a disabler, that you have to flash over your working CM 6.0 Final installation.
Flashing the enabler will install the modded kernel and PSFreedom module. You will lose usb functionality completely (no adb, no mass storage etc.) until you flash the disabler.
After flashing the enabler the module will always start upon boot, you have to enter no commands on the terminal emulator.
[SIZE=+2]HOW TO:[/SIZE]
Preliminary: Make sure you are on CyanogenMod 6.0 Final and everything is working correctly. It has been reported that it works also with older CM6 versions and CM5 too, you may try if it works and report it in this thread. If it's the first time, do a Nandroid backup before testing!
Download these files: http://www.multiupload.com/MY1LOGZ6YP (32A-Enabler), www.megaupload.com/?d=3UU2L0UX (32A-Disabler)
Put them on your SD card
Reboot into recovery and Flash Enable_PSFreedom_32A.zip
Reboot
Now psfreedom should be loaded as a module, you will see no difference, except for the loss of normal usb functions.
To run the exploit:
Make sure you are on 3.41 (DO NOT UPDATE OVER THE NETWORK!)
Connect the phone to the PS3 using usb
Turn it off completely (unplug power cable or turn off back switch on Fat models)
Plug it back in (turn on back switch)
Turn it on and immediately press the eject button (you should hear 3 quick beeps)
Booting should take a bit longer (5-10 seconds)
If you see two new options under the games tab, the exploit worked. You can now unplug the phone. Mind that you will have to do this procedure every time you boot your PS3. Try using another USB cable if it doesn't work with a few tries.
To uninstall:
Boot back into recovery
Flash Disable_PSFreedom_G1.zip
Reboot
You should have usb functions back to normal.
Payloads:
This version of PSFreedom contains the new PSGroove 1.1 payload (peek & poke)and is enabled for backups, but backup manager talk should not be done on this thread, there are other boards for that.
If you want to try other payloads (F.I. the new AerialX's apploader), you just have to load it into /proc/psfreedom/payload . You can do it by typing:
Code:
cat payload > /proc/psfreedom/payload
The payload can be wherever you want and has to be in the classic binary format. (just remember to substitute "payload" with the correct path).
Even better, if you put the new payload in the /data/local directory, named "payload" (no quotes), it will be automatically loaded upon startup, thus becoming the default payload.
Mirrors:
Code:
Enabler: http://depositfiles.com/en/files/o1qpcbkeo
http://www.zshare.net/download/80630364707ab8fe/
http://rapidshare.com/files/420315547/Enable_PSFreedom_32A_v3.zip
Disabler: http://www.zshare.net/download/801637791c6185b2/
Versions:
Code:
v0: initial release
v1: +module loaded on startup
+created disabler
v2: updated payload (peek & poke)
v3: resolved bootloop bug, updated PSFreedom, dynamic payload loading.
reserved (10 characters long)
Thanks for yours work!
What about an application to enable/disable psfreedom? Will it be possible in the future?
My Magic (32A) does just reboot over and over after flashing the enabler.......also after flashing the disabler........so now restoring (i ALWAYS back-up befor flashing anything!)
But thanks for trying!
radio version for cm6
one question, CM6 can be for New Radio, or just Old radio?
H3llSp4wN said:
one question, CM6 can be for New Radio, or just Old radio?
Click to expand...
Click to collapse
there's a port also for new radio showthread.php?t=723520
But there are some issues (like broken camera)
Old Radio, new radio requires a different kernel.
For the app, for now psfreedom requires a modded kernel, and it is not possible to switch them on the fly using an app. I know they're working on using a different driver, to avoid having to recompile the kernel. Still don't know if it can be done though.
Can anyone provide a mirror please?
cm6
i'm just a bit confused about what cm6 rom should be better and should i use, because there are severeal releases (minimou, redux etc).
can u give me a tip about this?
best regards
I always use the vanilla one, straight from the cyanogenMod forums. I think it should work with any of those versions though. Just make sure you're on old radio and you make a nandroid backup before trying.
got everything right now.
thanks for the mirror.
Got a question? Does the mt3gs use the msm72k also and why is it not on the port list? Sorry I'm probably in the wrong area but thought I would try
Hi , just have a question , looked arround with google , couldn't find my answer, maybe someone here knows,
Before trying this out, I would like to know if I can revert my ps3 to original state,
or to how it was before running psgroove?
yes as the exploit must be ran on every boot so simply reboot and delete bxxm
H3llSp4wN said:
i'm just a bit confused about what cm6 rom should be better and should i use, because there are severeal releases (minimou, redux etc).
can u give me a tip about this?
best regards
Click to expand...
Click to collapse
i use redux and it works for me (i still use the release that u have to do thru the terminal)
focus400hp said:
Got a question? Does the mt3gs use the msm72k also and why is it not on the port list? Sorry I'm probably in the wrong area but thought I would try
Click to expand...
Click to collapse
MT3G is 32B, so head off to the Dream section and get that one instead.
with cm6 my g1 go in loop... why?
Hey guys, I'm running into a little trouble after installing the PSFreedom enabler. My htc magic 32a (3.5mm jacket) just sits on the "HTC Magic" screen for eternity after flashing PSfreedom. I do have CM 6.0 installed, I believe its from Cyanogenmod 6.0 S/D version, I don't know what ebi I am nor if need to do something with kernel, but I just know I go into recovery, flash PSfreedom enabler, reboot, the "htc magic" logo shows up and then it sits there forever...Is there something I'm doing wrong?
@ repukken, rock187. You should use the 32B port. The link is in the first post.
Lollipop_Lawlipop said:
MT3G is 32B, so head off to the Dream section and get that one instead.
Click to expand...
Click to collapse
its mt3g slide i believe its different though i did use the precompiled for the dream 32b on a g1 yesterday and works very well and with no probs at all still want to see something for the slide. i asked in the slide forums and everyone just had s*** to talk really
This is a question for someone with really good knowledge of system files within android. I have taken the 3.06.405.1 RUU and cooked it into a rom to use for myself using the dsixda kitchen. Everything works just fine except wifi. I cannot get past the obtaining IP adress when trying to connect to wifi. I have searched through the phone trying to find the files that control wifi and am stumped. Which files would i need to extract from stock rom to make the wifi obtain an IP. I know my router is good because my wife is using it with no issues. When i cooked the rom i had to change the boot.img to one from a rom that i know can boot because the one in the ruu would not get past splash screen. Do i need to try a different boot.img or is there files that i need to replace that are inspire 4g specific.
I have already tried kernels from VU, Klquicksall and lordmod. Any help on this matter would be greatly appreciated.
Gizmoe said:
This is a question for someone with really good knowledge of system files within android. I have taken the 3.06.405.1 RUU and cooked it into a rom to use for myself using the dsixda kitchen. Everything works just fine except wifi. I cannot get past the obtaining IP adress when trying to connect to wifi. I have searched through the phone trying to find the files that control wifi and am stumped. Which files would i need to extract from stock rom to make the wifi obtain an IP. I know my router is good because my wife is using it with no issues. When i cooked the rom i had to change the boot.img to one from a rom that i know can boot because the one in the ruu would not get past splash screen. Do i need to try a different boot.img or is there files that i need to replace that are inspire 4g specific.
I have already tried kernels from VU, Klquicksall and lordmod. Any help on this matter would be greatly appreciated.
Click to expand...
Click to collapse
The wifi is based on the Broadcom 4329 chipset and the bcm4329.ko kernel module is required for wifi operation (it is stored in the /system/lib/modules/ directory on the phone). The module should match the kernel and should have been compiled with the kernel build. You don't mention what kernel you're using so I can't comment further. bcm4329.ko from a different kernel build may work, but with varying degrees of success.
Gene Poole said:
The wifi is based on the Broadcom 4329 chipset and the bcm4329.ko kernel module is required for wifi operation (it is stored in the /system/lib/modules/ directory on the phone). The module should match the kernel and should have been compiled with the kernel build. You don't mention what kernel you're using so I can't comment further. bcm4329.ko from a different kernel build may work, but with varying degrees of success.
Click to expand...
Click to collapse
Thank you very much gene I appreciate it. I did replace that file but did not make sure it matched the kernel. I will give it another shot. And for others that read this I still am using Bindroid as my daily I'm just trying to figure out how to build roms too. I thank all the devs for the great tools available to do so, mainly the kitchen.