[in progress] MutantMod ROM - myTouch 3G, Magic Android Development

So, I'm trying something that's probably doomed to failure but I thought was worth a go:
Take the excellent kernel / binaries that Cyanogen has produced and add some hero goodness.
It's currently flashing onto my phone.....
edit: install from sdcard complete... lets see if it boots.
edit2: epic fail. I removed the odex files from the rom when I built it since cyanogen's rom didn't have any... however, on boot I got a complaint about 'no odex file found'...so, I've now added them back in to see if I can boot.
boot attempt 2....

hmm, I'm getting this error on boot... anyone got any ideas?
Code:
bionic/linker/linker.c:1580| ERROR: 75 could not load 'libstdc++.so'
bionic/linker/linker.c:1640| ERROR: failed to link /system/bin/sh
bionic/linker/linker.c:1752| ERROR: CANNOT LINK EXECUTABLE '/system/bin/sh'

did a full wipe, format, reinstall... same error. Hmm. maybe if I describe my methodology someone can see where I'm going wrong:
I took cyanogen's latest rom, extracted everything. took drizzy's latest rom, extracted that somewhere else. then deleted the apps folder from the cyanogen rom and copied in all the apps from Drizzy's rom. Used the update script from cyanogen. Also copied in the /system/framework from Drizzy's (since it's all jars and apks).
Basically anything java based is from Drizzy's rom, everything else is from Cyanogen's.
My thinking is that if everything that's a compiled binary comes from Cyanogen, and the boot.img is from cyanogen then I should be able to use the hero APKs from somehere else without a problem. Apparently not though :/

I assume you have done it, but are you sure libstdc++.so is there? And did you try with another version with the library?

it is in there... maybe I just got unlucky and got a corrupt download or archive somewhere along the way.
I'll try again tonight

Okay, just a tried a rebuild using a different Hero rom (Qteks) and got a slightly different error on boot:
Code:
bionic/linker/linker.c:1580| ERROR: 62 could not load 'libc.so'
bionic/linker/linker.c:1640| ERROR: failed to link /system/bin/sh
bionic/linker/linker.c:1752| ERROR: CANNOT LINK EXECUTABLE '/system/bin/sh'
I don't even know where to start troubleshooting this really...

i have also tried this. When i managed to get it all to boot (removing all odex files and other unwanted crud) it went through all the setups etc then when it restarted the HERO Startupo gif and sound were extremely slow and played twice witjh about 500ms difference so it was like when your a kid singing fre ra jaqua (or whatever)
Giod knows y tbh.I also tried to put the modified launcher in the rom but no joy?
If you try installing apps from a hero ROM update it says "this app cannot be installed on this model"
|Maybe try figuring why hero apps wont run first, Then it may solve it?

Related

[ROM] myTouch 3G: Nothing but Netfilter 1.6 - Donut Update

Download link: MT3GV1.5_NBN1.5.zip
MD5:
1c962a4767659f86776fe6daf3052cf7 MT3GV1.5_NBN1.5.zip
This is the result of the work/messing around I did in this thread.
I started with the T-Mobile OTA stock ROM available here:
signed-opal-ota-150449.95700137.zip
I then:
1. Rebuilt the kernel with the same config as the ROM, except with the addition of the netfilter features required for tethering. (Kernel source is slightly newer than in the ROM as yesterday there were a few security related patches added to the repo.) The wlan.ko driver was rebuilt to match the new kernel as well.
2. Added the Superuser app and the Tethering app.
3. Removed the T-Mobile recovery and radio images. They are redundant at best, bricks waiting to happen at worst.
4. Re-packed and re-signed the ROM. (Only the ROM zip was signed so it would install via our recovery images. The internal apks were left alone.)
The result should be an experience identical to the stock software you had out of the box, but with the possibility of running apps that require root as well as tethering. Speed is the same, features are the same, apps are the same, etc.
There are plenty of great custom ROMs here if you're looking for more, but this will work if you're going for simple with no surprises.
UPDATE: Donut /1.6 update is on page 3.
UPDATE: Donut /1.6 DMD64 update is on page 4.
Is this for 32B or 32A?
This is for 32B.
awesome
hey man great job this is exactly what i want!!! great job!!!
atomtom, thank you for doing that. It's been working great the last 24 hours, no hidden gotchas or surprises from the updated kernel/wifi driver.
Thank you!!!...This is EXACTLY what I was looking for ..expecially for my friends who want root for wifi tether!!
Clean and Stock
Thanks for this ROM. I like clean and simple builts and this fullfill my tethering needs with my Viliv S5. I installed it today on MyTouch 3G.
Hi there
I installed this rom last night and by morning the phone was complaining about memory and had a bunch of processes force close.
Is there a mem leak or anything with this rom?
Not that I know of, but I only tested it for a few hours and then went on to Cyanogen for my daily use. Considering how similar this is to the stock ROM I would be very surprised if there was a memory leak.
Standard debugging questions: What SPL and radio are you running? Did you do a wipe before installing? Do you have a log we could look at?
I'll put this ROM back on my phone and see how well it's doing tomorrow.
Noticed an issue. The SU you are using isn't ideal. With tethering it was fine but as soon as I typed Su in terminal emulator, it starts the superuser permissions app, but it comes up blank. If I go back, its stuck waiting for Su permission. Zenthought.org has/had one I used, its from the JF and cyanogen builds. If u decide to use it make sure u change the Su binary too.
atomtom said:
Not that I know of, but I only tested it for a few hours and then went on to Cyanogen for my daily use. Considering how similar this is to the stock ROM I would be very surprised if there was a memory leak.
Standard debugging questions: What SPL and radio are you running? Did you do a wipe before installing? Do you have a log we could look at?
I'll put this ROM back on my phone and see how well it's doing tomorrow.
Click to expand...
Click to collapse
Hi there
I am running SPL 2005 (aman_ra mytouch root guide)
32B radio from htc site for google ion 2.22.19.26I
recovery 1.2.0G (aman_ra)
I have been going back and forth trying to find the rom that works best for me so yes i have done the format/wipe. Also since i want to be sure i might even run the following ontop of the format/wipe
fastboot erase system -w
fastboot erase boot
I dont erase recovery since i dont think i need to.
Please let me know.
Also - I would LOVE it if you could provide the same rom but with HTC keyboard/dialer.
flamingblue8z said:
Noticed an issue. The SU you are using isn't ideal. With tethering it was fine but as soon as I typed Su in terminal emulator, it starts the superuser permissions app, but it comes up blank. If I go back, its stuck waiting for Su permission. Zenthought.org has/had one I used, its from the JF and cyanogen builds. If u decide to use it make sure u change the Su binary too.
Click to expand...
Click to collapse
Yeah, the one that is available stand-alone is older than the one that comes with other ROMs. When I tried installing the newer apk pulled from Cyanogen 4.0.1 it would fail due to the key used to sign the ROM internals.
adb install Superuser.apk:
Code:
159 KB/s (14979 bytes in 0.091s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
adb logcat:
Code:
E/PackageManager( 58): Package org.zenthought.android.su has no signatures that match those in shared user android.uid.system; ignoring!
W/PackageManager( 58): Package couldn't be installed in /data/app/org.zenthought.android.su.apk
If anyone knows how to sort this out let me know and I'll update it.
That said, su still worked perfectly when I installed Better Terminal Emulator. (Of course, Better Terminal Emulator doesn't work to begin with. Try typing in a number.)
hmm interesting. when I was using just the stock ROM, then used 1click root, went into CM-recovery, followed by your directions, adb mount -a, then adb push the SU in reference, zenthought's, I had no issue. I then pushed the wlan.ko you put up, and flashed boot.img, rebooted, and finally installed the Superuser.apk, and I had NO issues whatsoever. i've got a nandroid backup of that system setup, in case there is anything of interest in there. I would have to boot back into it and remove my txts/mms/contacts, but i'd gladly share it for analysis.
I noticed the myTouch NBH appeared earlier, im going to try downloading that on my WinMo Wing (it connects to the wifi at the college im at but my G1 and myTouch won't.) i'll try flashing the NBH then your ROM, see what happens... oh and yes, I obviously wiped before installing ur ROM.
ROM has Superuser Permissions and Superuser Whitelist? Whats the difference and are they both needed?
Superuser Whitelist is the name of the apk that manages which app gets root access, su is the command line tool that actually performs the actions requested as root.
speedyls91 said:
Hi there
I installed this rom last night and by morning the phone was complaining about memory and had a bunch of processes force close.
Is there a mem leak or anything with this rom?
Click to expand...
Click to collapse
After last night and today of normal use, and leaving it on overnight, I haven't seen any behavior out of the ordinary.
I spent the last hour or so playing around with the donut update, but there are problems.
I downloaded the COC10 to DRC92 update zip and looked through it. Appears to be a new boot.img, a handful of files, and a bunch of binary patches. I made the following changes:
1. New kernel with the netfilter features enabled, but otherwise same sources and config.
2. Replaced the wlan.ko patch with the full file that goes with the new kernel since the one we're upgrading isn't the original and the patch won't apply.
3. Changed the update script to not try to patch the wlan.ko and skip over the version/key checks.
The update (applied manually via the recovery image) went fine, but there are problems with one of or both of WiFi Tether and Superuser. When attempting to start tethering there is just a general failure error but nothing bad in the log screen. In addition the Superuser app no longer honors the "always yes" setting. There are newer versions of both apps so I'll check those out later tonight/tomorrow.
Wow, doesn't sound good. Maybe leave out Wifi tether? I have been using a better su whitelist app, I think u may want to use it. I am using stock Donut at the moment, runs GREAT, so if I can help this would be great. What I am going to do is load my nandroid backup, clear out some garbage, and if you want I can send u my system.img and u can pick it apart appropriately to take a look at the SU I have along with the whitelist app. Perhaps that will solve the problems.
Wifi Tether is kinda the whole point so leaving it out isn't an option (or rather, having the user install it manually won't help). I think getting the new Superuser app working is a higher priority though. Unfortunately a system image of a stock ROM won't do any good. The problem is that the Superuser app ties in to the system in a way that requires them to be signed with the same key (or a shared key, something I haven't looked in to yet.)
Code:
I/PackageManager( 78): /system/app/Superuser.apk changed; collecting certs
E/PackageManager( 78): Package org.zenthought.android.su has no signatures that match those in shared user android.uid.system; ignoring!
My guess that the system is signed with T-Mobile's production key but Superuser is signed with a test key that is used on the fully custom builds. So it works fine with stock Android, Cyanogen, etc., but not here since I only changed the kernel, not the keys.
Obviously I can't re-sign Superuser.apk with T-Mobile's key so I have to re-sign the system with the test key. Unfortunately I have no idea 1) which file this is specifically, or 2) how to do it even if I knew.
Any suggestions are of course appreciated.
You mentioned that before. But even on the stock COC10 ROM, I pushed THAT su (from the last JF ROM,1.51) into /system/bin and then installed the apk into /data/app and it worked previously. If you wouldn't mind, plz send the new boot.img and I'll try flashing it through fastboot, as well as cm-recovery so I can use the root access adb to push the su into the stock donut. Which spl has fastboot enabled? I'll PM u my email.

[ROM](32A / 32B) Hero3G UNI Final w/ Update 10/26/09

Removed~
Moved to another Fourm
Removed~
Moved to Another Forum
let me flash this right away.....
will post back if i see anythin....
camera don't work.
g-sensor ok
wifi ok
music not play on htcplayer
on call incoming not sound , the phone not play the ringtones ...?¿
+1 camera don't work:/
Working on it, getting ready to flash my MT3G for testing, will post an update soon.
Uploading Updated Rom, please Let me know if anything is still broke.
Gonna wait for more comments for giving it a go.
new rom added
Please leave the java and footprints please.
Hows it running eugene? It's setup to use ext2, 3 or 4 correct and linux swap?
I'm giving up on this for right now, it seems to not wanna work properly for me as it stays in the infinite loop of Hero/HTC no matter what I do from formatting it all over again to wiping and so on so forth. Also if this is an HTC Tattoo rom why is it boot up with the HERO screen?
vinbeaver said:
I'm giving up on this for right now, it seems to not wanna work properly for me as it stays in the infinite loop of Hero/HTC no matter what I do from formatting it all over again to wiping and so on so forth. Also if this is an HTC Tattoo rom why is it boot up with the HERO screen?
Click to expand...
Click to collapse
To be fair the first post says the Tattoo dump was fake.
Really Odd, I only Get a Reboot loop if ext2 / 3 is not formatted correctly.
Also, what build are you using? the lib's and app's are from tattoo system though, I'm currently running evil_tat_10 build, and it running smooth, I still have a few problem to iron out with usb connected and disconnecting, but over all seed it good. I think there is a sync problem, but like I said, I'm not a developer, this is just a hobby, and making system that fits me and sharing it with everyone.
Requirements are listed in first post!
As far the hero boot, not sure, just post what was given for dump. Also, I never said it was a tattoo system, just Tattoo App's HTC Frameworks & lib's.
After further inspecting the rom, it's not a fake and I need to fix my first post, I'm currently still fixing and testing which lib's are causing the Music and Ring issue.
Well my partitions are formatted correctly so I don't know what the issue could be, I deleted and reformatted my partitions trying both ext2, ext3 and ext 4 and I kept getting the boot loop, so not sure what else to try here.
only thing that differs in my system is a linux splash on boot, and the eng. spl loaded.
Working on another update, will post soon.
New Rom uploaded
Should fix the reboot issue.
So far Stable and working good on MT3G of mine, Please let me know if you find any problems as this rom is using the App's and Frameworks from the Tattoo dump.
So please let me know what app you would like to see included and removed from this rom.
so is this the real tattoo now?
Error with installation:
E:Corrupt file:data/app_s/HtcSoundRecorder.odex
E:Verification failed
Installation aborted
Any idea?
sardor said:
Error with installation:
E:Corrupt file:data/app_s/HtcSoundRecorder.odex
E:Verification failed
Installation aborted
Any idea?
Click to expand...
Click to collapse
I just received the same thing...

Interactive updates?

Just throwing an idea out there, and since it's for developers (specifically people who make their own recovery images) I assume this is the right section.
Since we have 'control' over the recovery image on our phones, would it not be possible to add a little script to an update.zip that a suitably modified recovery image could extract and run to interactively prompt the user for various Rom options? I'm thinking specifically of kernel choices, but it could be extended to almost anything that needs to be done prior to booting the installed image.
Imagine installing a rom, and during the install you got a little menu like this:
1: RamHack, BFS Kernel
2: RamHack, CFS Kernel
3: No-RamHack, BFS....
etc...
inefficient, it adds extra baggage to rom, and more things can go wrong. what would you rather downlaod a 90mb file or a 110 mb file.
Which would you rather download, one 110MB ROM or 2 90MB ROMS?
I'm pretty sure there's more than a few people who'll download different variations of the same ROM so they can see which is faster, how much easier would it be to just download one thing and then choose which options you want in there without downloading anything else.
I believe it is entirely possible. As a matter of fact, I was working on a ROM project that would have an interactive installer from the update.zip that would selectively install different features, apps, customization, themes, etc., based on the recovery menu application. It would use a lot of the /cache for temp space, though, as the installer application and its resources and configuration file, and later, the necessary parts of the ROM itself, would need to be unzipped before the install can run, if I recall correctly.
Does anyone have a good link to a reference for the command syntax for the /META-INF/com/google/android/update-script file? I'll go search for it in a few moments myself. I could probably make a simple ROM installer that chooses between ROM X and ROM Y based on a key input, as a proof of concept. I'll test it myself, I don't really mind half-bricking my device for science. (As long as I don't need to touch the SPL/Radio, that is.)
Update: Some creative searching finds me this:
JesusFreke said:
Assuming you mean update-script in an update.zip update, you will need to either look at existing update-script files for an example of the syntax, or look at the source of the recovery program in the android source
Click to expand...
Click to collapse
There's also a "make-update-script.c" file I'm seeing here and there, I'm trying to find the file in the Android source.
Update 2: From install.c at donut from cyanogen's android_bootable_recovery:
Code:
#define ASSUMED_UPDATE_SCRIPT_NAME "META-INF/com/google/android/update-script"
#define ASSUMED_UPDATE_BINARY_NAME "META-INF/com/google/android/update-binary"
and in commands.c, toward the bottom at register_update_commands is all the commands defined, and above that are all the functions they carry out.
sorry about that deicist i was sleepy when i wrote that so i must have been cranky yea i guess that is a fine idea, with just 30 more mb you have like 300mb worth of stuff. and you can pick which 90 mb you want.
markolo25 said:
sorry about that deicist i was sleepy when i wrote that so i must have been cranky yea i guess that is a fine idea, with just 30 more mb you have like 300mb worth of stuff. and you can pick which 90 mb you want.
Click to expand...
Click to collapse
Well, on the 32B platform with the Death SPL (my phone) we have the following partitions of the internal NAND memory (mtdblock*) from the df and mount command:
NAND 3: /system 92160kb - OS partition, static and read-only
NAND 5: /data 91904kb - User, system config, app config, and apps (without a2sd)
NAND 4: /cache 30720kb - OTA cache, Recovery/update config and temp
And I'd assume NAND 1 and 2 are the kernel, ramdisk, and bootloader config.
So the ROM wouldn't exceed 92MB installed (most leave some room in /system for hacks and updates). And the update process doesn't ever really "flash", per se; it just formats, copies files, and sets permissions and initialization configs, like Windows or Mac.
So the files that are common to the different ROMs being packaged don't need to be duplicated, only the ones that are changed (like a boot.img, or 32A/B compatibility, or different apps). The update script and chooser menu will decide which files to copy. Meaning the ROM package in and of itself shouldn't really need to exceed 128MB, even if choosing from a wide variety of platforms. And upon installation, the system might take less than 32 MB.
yeah, what he said ^
The scenario I was thinking about specifically was SuperD. If you look here:
http://forum.xda-developers.com/showthread.php?t=613809
There's 8 different downloads there. How many files are actually different between those 8? I guess the themes mean a lot of application files are different (due to having different resources in them) but the underlying framework files will be pretty much the same I think.
Deicist said:
yeah, what he said ^
The scenario I was thinking about specifically was SuperD. If you look here:
http://forum.xda-developers.com/showthread.php?t=613809
There's 8 different downloads there. How many files are actually different between those 8? I guess the themes mean a lot of application files are different (due to having different resources in them) but the underlying framework files will be pretty much the same I think.
Click to expand...
Click to collapse
I could download them all, and find the differences of each. It would be cool if a ROM like this were available in a single download, from which you would choose the content from the device before flashing.
Also, inspired by talking about this, I wrote up a guide on the update-script in the package file. It's still not finished, but it'll be the only guide available for that syntax yet (trust me, I couldn't find one myself ). Link's in my sig.
I'm surprised that nobody's mentioned the Droid... the sholes.info rom (now called droidmod) have used a .tgz archive instead of a .zip, the .tgz installs have always allowed this customization, droidmod makes one of the most common recovery's AND rom's. (SPRecovery/Droidmod).
It give you the option to choose what launcher to install, what theme, what apps to remove.
page here: http://droidmod.org/news/droidmod-v1-0-is-out/
how big of a ROM are you thinking about?
There are roms (WG etc...) that offer more than one kernel as update.zip you can flash over an existing installation of your rom instead of adding all the stuff to one big file. also you can download themes for several roms/for metamorph.
so why would you want some big install script instead of just downloading the files you like and flash it?
jmhalder said:
I'm surprised that nobody's mentioned the Droid... the sholes.info rom (now called droidmod) have used a .tgz archive instead of a .zip, the .tgz installs have always allowed this customization, droidmod makes one of the most common recovery's AND rom's. (SPRecovery/Droidmod).
It give you the option to choose what launcher to install, what theme, what apps to remove.
page here: http://droidmod.org/news/droidmod-v1-0-is-out/
Click to expand...
Click to collapse
Is the Droid's recovery image capable of running on the G1, and/or is it open-source enough to be cross-built to the G1? If so, we could port it here. Only problem there though, is that all the roms are in update.zip format for the G1 already, we'd need to make it dual-compatible if we don't want to split the community and annoy generally everyone ("My rom only supports TGZ recovery!" "ROMs are in ZIP format, and I will not make a TGZ one for those unfortunate enough to use the other Recovery!")
domenukk said:
There are roms (WG etc...) that offer more than one kernel as update.zip you can flash over an existing installation of your rom instead of adding all the stuff to one big file. also you can download themes for several roms/for metamorph.
so why would you want some big install script instead of just downloading the files you like and flash it?
Click to expand...
Click to collapse
Well, for one, devs need to host one file only, and users need to download one file only. The file won't be much bigger or more complex at all, really. And the way things look on the recovery side, we could probably put a selection of themes in with the updater and patch them in post-install with a Metamorph script straight from recovery. That way, the rom is as you want it out-of-the-box, no multiple reboots, etc.
Also, those scripts that usually run on first-boot, like zipalign, dexopt, apps2sd etc. should run from the recovery environment, instead of before the Android bootanimation (I do get tired of hearing "This ROM will take a LONG time on the first boot. If it's stuck at the G1 screen, just wait 10-30 minutes.")
So what would you rather have, one single ROM (G1_Android_ROM_v1.17.zip) for each version released,
or six different ZIPs to flash (G1_Android_ROM_10MB_CFS.zip, G1_Android_ROM_Greentheme.zip, G1_Android_ROM_Bluetheme.zip, G1_Android_Nowipe_GApps.zip)?
Would you rather select what you want to include at flash (and be able to change things like themes or features after flashing), or have 20 different files to choose from, wiping and flashing on each?
I am aware of the no-wipe upgrades for many ROMs, but they can get confusing (I once flashed a CFS_10MB.zip that was for a Hero ROM, stupidly thinking that it might have been for the Eclair that I just downloaded.) Needless to say, I had to wipe and reflash. Again.
TylTru said:
Is the Droid's recovery image capable of running on the G1, and/or is it open-source enough to be cross-built to the G1? If so, we could port it here. Only problem there though, is that all the roms are in update.zip format for the G1 already, we'd need to make it dual-compatible if we don't want to split the community and annoy generally everyone ("My rom only supports TGZ recovery!" "ROMs are in ZIP format, and I will not make a TGZ one for those unfortunate enough to use the other Recovery!")
Well, for one, devs need to host one file only, and users need to download one file only. The file won't be much bigger or more complex at all, really. And the way things look on the recovery side, we could probably put a selection of themes in with the updater and patch them in post-install with a Metamorph script straight from recovery. That way, the rom is as you want it out-of-the-box, no multiple reboots, etc.
Also, those scripts that usually run on first-boot, like zipalign, dexopt, apps2sd etc. should run from the recovery environment, instead of before the Android bootanimation (I do get tired of hearing "This ROM will take a LONG time on the first boot. If it's stuck at the G1 screen, just wait 10-30 minutes.")
So what would you rather have, one single ROM (G1_Android_ROM_v1.17.zip) for each version released,
or six different ZIPs to flash (G1_Android_ROM_10MB_CFS.zip, G1_Android_ROM_Greentheme.zip, G1_Android_ROM_Bluetheme.zip, G1_Android_Nowipe_GApps.zip)?
Would you rather select what you want to include at flash (and be able to change things like themes or features after flashing), or have 20 different files to choose from, wiping and flashing on each?
I am aware of the no-wipe upgrades for many ROMs, but they can get confusing (I once flashed a CFS_10MB.zip that was for a Hero ROM, stupidly thinking that it might have been for the Eclair that I just downloaded.) Needless to say, I had to wipe and reflash. Again.
Click to expand...
Click to collapse
You could just have flashed the original rom without wipe.
Would be a step forward if you could simply put roms and additional files in folders... maybe even whole zip files containing some updates and an xml like file to describe them. This would guarantee compatibility with earlier boot images (just unpack the updates in the zip). Tar might work better than zip as it is not compressed thus faster afaik.
http://droidninja.com/?p=26334
We got ninja'd. Apparently the Droid Does exactly this.
So let's get to work on porting it! Like this comment says, I'm working on finding the source code to a good Droid recovery image (sadly Droid hasn't its own forum here), and if it's closed source, I'll get on reverse-engineering a .tgz rom to see exactly how it works.
TylTru said:
http://droidninja.com/?p=26334
We got ninja'd. Apparently the Droid Does exactly this.
So let's get to work on porting it! Like this comment says, I'm working on finding the source code to a good Droid recovery image (sadly Droid hasn't its own forum here), and if it's closed source, I'll get on reverse-engineering a .tgz rom to see exactly how it works.
Click to expand...
Click to collapse
This is pretty awesome. I was going to say, we could easily run bash scripts but this is so much better.
This needs to be merged with both Amon_ra's recovery and the new 2.x based recovery...

How to make MP4 work using Cyanogen eclair kernel on G1?

Hi Guys,
I compiled an eclair rom using the 2.9.26-eclair branch of Cyanogen kernel on github . And I ported the camera-related sources from donut branch to eclair branch. Now both 3d and camera can work on my G1. But I still canoot play mp4 on G1.
Would you please tell me how to make mp4 work on G1? I knew Kingklick had succeed to make mp4 work. Is his sources open?
Thanks.
loveheaven said:
Hi Guys,
I compiled an eclair rom using the 2.9.26-eclair branch of Cyanogen kernel on github . And I ported the camera-related sources from donut branch to eclair branch. Now both 3d and camera can work on my G1. But I still canoot play mp4 on G1.
Would you please tell me how to make mp4 work on G1? I knew Kingklick had succeed to make mp4 work. Is his sources open?
Thanks.
Click to expand...
Click to collapse
working dec libs come from the 2.1 drioderis dump which you can find in the eris dev forums.
you can also find them here
http://forum.xda-developers.com/showpost.php?p=5793964&postcount=667
Firerat said:
working dec libs come from the 2.1 drioderis dump which you can find in the eris dev forums.
you can also find them here
Click to expand...
Click to collapse
Would you please tell me which libs I should push into my 32B G1? I pushed libopencore_mp4*.so libOmxMpeg4.so from droid eris dump into my g1. But after that when I reboot my phone, my phone cannot be rebooted and stays at the first "G1 Tmobile" splash screen.
loveheaven said:
Would you please tell me which libs I should push into my 32B G1? I pushed libopencore_mp4*.so libOmxMpeg4.so from droid eris dump into my g1. But after that when I reboot my phone, my phone cannot be rebooted and stays at the first "G1 Tmobile" splash screen.
Click to expand...
Click to collapse
Code:
mkdir eris;mkdir Firerat3dvid
cd Firerat3dvid
unzip <fullpath to the update zip>
export SomeOtherDir=$PWD
cd ../eris
unzip <fullpath to dump zip>
cat > ~/bin/compmd5sum << "EOF"
#!/bin/sh
# md5sum a bunch of stuff
md5sum $1;md5sum $SomeOtherDir/$1;adb shell md5sum /$1
EOF
chmod 755 ~/bin/compmd5sum
find . |sed s/^/compmd5sum\ /|sh
now you can compare files in two dir on your linux box against the ones on your phone, tells you whats 'missing' what are the same and what are different
PS the files you need are in the zip files in the link I gave you
just thought that the above script might come in handy for someone wanting to compare files
Thank you very much!
I downloaded the CE-12-Patch_3D_vid_signed.zip you prodivded and pushed all the libraries in your zip (except the wlan.ko) into my G1. The kernel my G1 used is built from Cyanogen kernel eclair branch. After pushing the libraries, I reboot my G1.But the G1 got stucked in the first "T-mobile G1" splash screen and couldn't be reboot into the system.
Why did it happen? I should use your kernel?? The opencore library depends on the kernel?? I think the opencore is independent. Even if there is something wrong with opencore, G1 can always be reboot. Am I wrong?
Firerat said:
Code:
mkdir eris;mkdir Firerat3dvid
cd Firerat3dvid
unzip <fullpath to the update zip>
export SomeOtherDir=$PWD
cd ../eris
unzip <fullpath to dump zip>
cat > ~/bin/compmd5sum << "EOF"
#!/bin/sh
# md5sum a bunch of stuff
md5sum $1;md5sum $SomeOtherDir/$1;adb shell md5sum /$1
EOF
chmod 755 ~/bin/compmd5sum
find . |sed s/^/compmd5sum\ /|sh
now you can compare files in two dir on your linux box against the ones on your phone, tells you whats 'missing' what are the same and what are different
PS the files you need are in the zip files in the link I gave you
just thought that the above script might come in handy for someone wanting to compare files
Click to expand...
Click to collapse
loveheaven said:
Thank you very much!
I downloaded the CE-12-Patch_3D_vid_signed.zip you prodivded and pushed all the libraries in your zip (except the wlan.ko) into my G1. The kernel my G1 used is built from Cyanogen kernel eclair branch. After pushing the libraries, I reboot my G1.But the G1 got stucked in the first "T-mobile G1" splash screen and couldn't be reboot into the system.
Why did it happen? I should use your kernel?? The opencore library depends on the kernel?? I think the opencore is independent. Even if there is something wrong with opencore, G1 can always be reboot. Am I wrong?
Click to expand...
Click to collapse
your linux will be running fine, its the Android that isn't happy
the libs are not dependent on the kernel, but may be dependent on something which is already in CE
tbh I can't really help you , I have no idea what 'ROM' you are pushing these libs to.....
logcat is your friend, I have a whole bunch of them on one line
Code:
adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat
make sure your phone is connected the first time, and it will happily sit there when you unplug, 'waiting for device' till you plug it back in.
and in another console
adb shell busybox top
sometimes you can even shell in if you are not seeing anything on logcat
'busybox top' will give you an idea of what is running
and there is nothing stopping you from having a couple more terminals open
one with a shell for 'doing stuff' and another for pushing and pulling stuff
all while watching top and logcat
your loop is probably to do with drm, but the logcat will tell you
Firerat said:
your linux will be running fine, its the Android that isn't happy
the libs are not dependent on the kernel, but may be dependent on something which is already in CE
tbh I can't really help you , I have no idea what 'ROM' you are pushing these libs to.....
logcat is your friend, I have a whole bunch of them on one line
Code:
adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat;adb logcat
make sure your phone is connected the first time, and it will happily sit there when you unplug, 'waiting for device' till you plug it back in.
and in another console
adb shell busybox top
sometimes you can even shell in if you are not seeing anything on logcat
'busybox top' will give you an idea of what is running
and there is nothing stopping you from having a couple more terminals open
one with a shell for 'doing stuff' and another for pushing and pulling stuff
all while watching top and logcat
your loop is probably to do with drm, but the logcat will tell you
Click to expand...
Click to collapse
Thank you very much!
I used your method and found it is because my rom could not load the libwebcore.so in your zip. So I pushed my orignal libwebcore.zip back into G1, my G1 can boot now. But after that I still cannot watch Mp4 on my G1...
Would you please give me some advice? Thanks.
loveheaven said:
Thank you very much!
I used your method and found it is because my rom could not load the libwebcore.so in your zip. So I pushed my orignal libwebcore.zip back into G1, my G1 can boot now. But after that I still cannot watch Mp4 on my G1...
Would you please give me some advice? Thanks.
Click to expand...
Click to collapse
CE1.2 with my vid patch
wait for CE2
or Kings 1.8 AOSP
or
check the code in this
http://forum.xda-developers.com/showpost.php?p=5889900&postcount=4
with a bit of deduction, you could figure out what is missing/different
as I said in my last post, I can't help you as I have no idea what ROM you are trying to get mp4 to run on.........................................
Installing/Pushing CE-12-Patch_3D_Vid_signed.zip
Got a question... I recently downloaded the v4_1.zip, and was wondering if it's possible to incorporate the CE-12-Patch_3D_Vid_signed.zip in to it. I'm not new to the whole rooting thing, and have tried several variations of the Eclair and Donut roms floating around here. Unfortunately, I'm not to well versed in ADB. My main interest in pushing the above zip is to finally have an Eclair rom with working video. If anyone can help me out with this, it'd be greatly appreciated.
will4958 said:
Got a question... I recently downloaded the v4_1.zip, and was wondering if it's possible to incorporate the CE-12-Patch_3D_Vid_signed.zip in to it. I'm not new to the whole rooting thing, and have tried several variations of the Eclair and Donut roms floating around here. Unfortunately, I'm not to well versed in ADB. My main interest in pushing the above zip is to finally have an Eclair rom with working video. If anyone can help me out with this, it'd be greatly appreciated.
Click to expand...
Click to collapse
the v4 is a different beast
King's Eris has working video
King's Eris CachHacked has working video and is a lot faster
CE-12-Patch_3D_Vid_signed.zip
Thanks for the response. Actually, I was only using the v4 rom as an example. I have tried King's Eris rom, and I think I have the most recent version of it, but the last time I tried it the camcorder did it's I'm not gonna work for you thing. Is there a way to push the CE-12-Patch_3D_Vid_signed.zip to this rom instead, or did I misinterpret the description of this patch? At any rate, it is fun trying all these new and different roms. Can't wait for a fully working 2.0 pastry.
P.S: I just tried the FR-v4OL-CH-0-1_S.zip rom, and it does have video playback. Unfortunately, the camcorder is still non-funtional, of course, and data doesn't appear to be working.
will4958 said:
Thanks for the response. Actually, I was only using the v4 rom as an example. I have tried King's Eris rom, and I think I have the most recent version of it, but the last time I tried it the camcorder did it's I'm not gonna work for you thing. Is there a way to push the CE-12-Patch_3D_Vid_signed.zip to this rom instead, or did I misinterpret the description of this patch? At any rate, it is fun trying all these new and different roms. Can't wait for a fully working 2.0 pastry.
P.S: I just tried the FR-v4OL-CH-0-1_S.zip rom, and it does have video playback. Unfortunately, the camcorder is still non-funtional, of course, and data doesn't appear to be working.
Click to expand...
Click to collapse
/data not working?
if data wasn't working it wouldn't boot past the bootanimation splashscreen
if data is 'full' reboot, it will correct itself
Unfortunately, when I try to do something that requires a data connection, it suggests using wifi. During setup, I did select the first connection option, which I think was data and wifi or something like that. When I try to go into Market to sign in that way, I can't connect. Is there a step I'm missing, or has this happened to anyone else? Also, is there a way to push the CE-12-Patch_3D_Vid_signed.zip into the FR-v4OL-CH-0-1_S.zip rom, or can I just flash like a normal zip? Thanks in advance.
will4958 said:
Unfortunately, when I try to do something that requires a data connection, it suggests using wifi. During setup, I did select the first connection option, which I think was data and wifi or something like that. When I try to go into Market to sign in that way, I can't connect. Is there a step I'm missing, or has this happened to anyone else? Also, is there a way to push the CE-12-Patch_3D_Vid_signed.zip into the FR-v4OL-CH-0-1_S.zip rom, or can I just flash like a normal zip? Thanks in advance.
Click to expand...
Click to collapse
ahh, sorry I'm getting all mixed up, because everyone is stressed out over FR-a2sd using /data for something useful instead of leaving it as an empty,wasted space.
yes, data connection is not working, tbh I don't know why the Market doesn't work even if wifi is working..
The CE-12-Patch_3D_Vid_signed.zip isn't going to do anything for FR-v4OL-CH-0-1_S.zip
its just a 3D kernel , and libs I took from the eris dump which got video working.
infact , the libs are 'mostly' the same as the ones already in v4OL
( which means I'm totally not understanding why video is dark, got to be a framework thing, maybe, I don't really know, just guessing )
Flashing / pushing CE-12-Patch is just going to kill v4OL
I did CE-12-Patch a long time ago, shortly after re-visiting xda after initially rooting my g1 way back in Feb '09.. kinda wished I'd stuck around then.
anyway, CE-12-Patch WILL break v4OL, is it doesn't mount mtdblock4 in the right place.
the v4OL is beta , lots of things don't work
if you get your kicks trying to fix broken things, or making yourself understand things you don't understand ( i.e. you self teach )
then it is for you.
if you want things to work 'out of the box' ,
King's Eris mostly works
ce12 cachehack works
ce2.0 works ( with a 'lil' fixup, facebook fix is in the thread FR*S.zip coming soon.. )
OE1.3.0.1 has things working ( anyone flashed ce12-patch over oe1.3 ? )
and good ol' SuperD works very well.
personally I think your best root is the CE12 CacheHack
It's fully functional, and best of all, CE2.0 is a *no wipe* update
You can flash CE2.0 , just a couple of fixes that need to be consolidated
they are in the thread , minor fix is at post #1401 ( which I will update to a "no hassle,flash straight after CE2.0" soon )

[KERNEL] OTA 1.47.651.1 stock boot.img in update.zip

CAUTION: ANY CUSTOM ROM WHICH HAS A MODIFIED KERNEL, PROBABLY WILL BREAK BY USING THIS.
More than likely you will need to copy over the ramdisk. If you don't know how to do this, then wait until your ROM developer does it for you!
Who: For those who are ANXIOUS and the DEVELOPER type (more advanced users) who want to load the new kernel which comes with the OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip released today.
If you're not an advanced user or the developer type, please wait for the builder of the ROM you're using to release their own update!
What: I've pulled the boot.img from the firmware.zip inside of the OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip and put it into this update.zip.
Tech Details: This update.zip copies flash_image and boot.img to /system/bin and /system, flashes the new boot.img and deletes boot.img from /system. My first time creating this type of update.zip on the EVO!
Advantages:
npace said:
Here's a rundown of the issues that I tested for fixes:
1. Touch input lag -- fixed -- tried with multitouch visualizer 2
2. Improperly grounded touchscreen -- fixed -- tried on multiple surfaces
Click to expand...
Click to collapse
http://www.joeyconway.me/evo/stock/jk-stock-OTA-1.47.651.1-kernel-signed.zip - WiFi will not work until the System Software portion of the OTA update is loaded
I got my retard helmet on and I'm ready to test this baby on Avalaunch's Froyo ROM.
Sorry for the noob question, I'm new to android. Is this for stock rooted roms? I am running stock evo rom rooted and nand unlocked, so is this essentially an update for rooted users running stock rom? And will I have to update the radio with a seperate flash? Thanks for your help, and everyone's hard work!
I'm using Jk-original 1.0.8 odex and I flashed the update image...giving error..."Can't chown/mod /system/flash_image (No such file or directory) Failure at line 3:set_perm 0 0 0755 SYSTEM:flash_image Installation aborted." I do have "flash_image" in /system/bin.? Also, followed Joey's script for that update.zip in adb manually and didn't get any error, I just don't know how to verify the install. Will it show in build???
snandlal said:
I'm using Jk-original 1.0.8 odex and I flashed the update image...giving error..."Can't chown/mod /system/flash_image (No such file or directory) Failure at line 3:set_perm 0 0 0755 SYSTEM:flash_image Installation aborted." I do have "flash_image" in /system/bin.? Also, followed Joey's script for that update.zip in adb manually and didn't get any error, I just don't know how to verify the install. Will it show in build???
Click to expand...
Click to collapse
Re-download. He had to make a change and just re-uploaded it, I just downloaded and applied it without a problem, after having the same error you did with the first file.
Any comments from people that have this applied (and working with full root)?
Shane Pitman said:
Re-download. He had to make a change and just re-uploaded it, I just downloaded and applied it without a problem, after having the same error you did with the first file.
Click to expand...
Click to collapse
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
That worked Thanx
Kernel's working just fine with Avalaunch's Froyo ROM.
joeykrim,
Have you used Koush's anykernel? I think you can make a update.zip that works with any kernel..
It just hasn't worked properly for me yet...
Here's link:
http://github.com/koush/AnyKernel
It should extract the ramdisk and everything from your current kernel and just replace the zImage and then flashes boot.img.
Kiraly said:
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
Click to expand...
Click to collapse
I've got most of the Sprint/HTC crap removed, rooted, nand unlocked, custom recovery, running joeykrim-original-1.0.8 deodex rom, and this worked just fine.
lafrad said:
Any comments from people that have this applied (and working with full root)?
Click to expand...
Click to collapse
this ONLY updates the kernel and will not effect root access.
Kiraly said:
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
Click to expand...
Click to collapse
this is ONLY the kernel. has nothing to do with ANYTHING in /system including bloatware/apps.
npace said:
joeykrim,
Have you used Koush's anykernel? I think you can make a update.zip that works with any kernel..
It just hasn't worked properly for me yet...
Here's link:
http://github.com/koush/AnyKernel
It should extract the ramdisk and everything from your current kernel and just replace the zImage and then flashes boot.img.
Click to expand...
Click to collapse
nice. i remember seeing this once but had forgot about it.
i prob wont delve into this yet cuz i haven't modified the ramdisk at all, but this is encouraging!
ill prob wait till we get some htc source code for the kernel, and then dive into customizing the kernel and the ramdisk or if i get bored and wanna customize my ROM with this stock kernel and custom ramdisk!
this is def good to know! thanks for the link!
Did anyone else have an issue with 4G stuck saying its turning on? Worked fin again after.restoring a backup.
Yep... 4th got stuck for me. Camera ad ADW also crashed a bunch too
Sent from my PC36100 using Tapatalk

Categories

Resources