This is still not a bootable build
update 10/16/09 ------
Qteknology has got it booting to splash screen but its in a bootloop
this amazing progress
everything i do will be based off this work from here on out thans so much Qtek!
ill need to get some information on what exactly he changed but i know
modified build.prop
modified hw folder
modified bootscreen (tattoo one wouldnt play right)
still wont boot all the way waiting to work out a few things before i post a link i also wanna ask him if its ok for me to post a link
THIS BUILD WILL NOT BE FLASHABLE YET IT IS SPECIFICALLY FOR INPUT/Developement ONLY!
Code:
*****!!!!!! DISCLAIMER!!!!!!!*******
This is still not a bootable build
i am not responsible if you try to flash these roms
for any damage that may occur to your device
these are not finished and are not bootable
still in EARLY EARLY EARLY BETA!
This is about where im at right now
closed-10.07.09
Tattoo Only from the WWE 1.65.405.1 build
Merged lib and hw (for sensors) folders with 1.6 doughnut for magic 10/13/09 will try new lib folder idea tonight and report back with logcat and DDMS report
Specific items will be listed later today when i can think of everything
added some stuff in system/bin (super user access etc)
cyanogens 4.1.11.1 kernel and corresponding wlan.ko added (Thank you so much jubeh for the boot.img)
update-script should be super barebones... really just hoping for a boot right now
______________________________________
Update 10/07/09
so Jubeh might be my saviour He packed the Tattooboot.img with cyanogens kernel
A big thanks to: Jubeh(wouldve never got this far without his knowledge),Nk02(for dump used), Drizzy Drake Rogers(is my personal htc hero),Qteknology (you rock man), Jac, Haykuro, Cyanogen, ccyrowski,JF,twizzzzzzted and any others I forgot to mention you guys are great lets keep building a better bot
you cant mixe 2 different builds together, rosie is tied to many apps, so if you were to only try and port the rosie onto a hero build already out, then rosie wont load just your regular laucher!
mixing builds is bad, especially if they are odex!
Drizzy~
I have a night job and I'm getting ready to sleep. Sorry I didn't reply to your last PMs, but the questions are a little involved and I'm very very sleepy. When I have time (maybe later today, or tomorrow, or could be the weekend) I'll try to get a very simple (no a2sd, no compcache, no nonsense, no nothing, just tattoo and root) build working so that people can take it and mod it as they wish. I won't promise anything though, I'm a known procrastinator.
jubeh said:
I have a night job and I'm getting ready to sleep. Sorry I didn't reply to your last PMs, but the questions are a little involved and I'm very very sleepy. When I have time (maybe later today, or tomorrow, or could be the weekend) I'll try to get a very simple (no a2sd, no compcache, no nonsense, no nothing, just tattoo and root) build working so that people can take it and mod it as they wish. I won't promise anything though, I'm a known procrastinator.
Click to expand...
Click to collapse
Id feel alot more accomplished if i can make it work with a small ammount of direction (ill try not to ask REALLY stupid questions hahaha OMFG I BRICKED
coding makes all kinds of sense to me I jsut need to know what points where and where the system starts the read from
starts at kernel and kernel on firstboot compiles my libs and runs scripts once the environment is built from kernel loads framework and apps stuff like that
once that happens you have live system
Drizzy Drake Rogers said:
you cant mixe 2 different builds together, rosie is tied to many apps, so if you were to only try and port the rosie onto a hero build already out, then rosie wont load just your regular laucher!
mixing builds is bad, especially if they are odex!
Drizzy~
Click to expand...
Click to collapse
i knew about the odex thing becuase the odex is SPECIFIC to the build correct? when you add it i think youll get a error like doesnt match stored signature no signature on file ignoring in logcat
i need a NON Odex'd hero like haykuro's and update it all with tattoo stuff and the newest hero apps to fill in where tattoo doesnt cut it
I know rosie is tied in with alot of stuff and when you just try to merge rosie it wont parse properly because it needs the sdk4 to parse the package
THEREFORE! haha i want to make basically 1.6 Rosie with hero apps filling in for the tattoo ones that i dont wanna edit all the drawables in
i want functionality of 1.6 speed of the dumbed down rosie for tattoo and apps from hero i know ill have to cook this and in no way am i asking someone to "just make update.zip so i can flash"
lets limit me to 1 n00b question a day and after a week or so of patience ill prolly have it done
Question of the day: Can I Un ODEX builds or do the ODEX's directly correspond with the apk and are necesary for the apk's functionality i know that dexopt will run at firstboot on odex'd builds but the odex's exist before the dexopt runs right?
yes you can unodex. http://jf.andblogs.net/2009/09/10/slay-those-pesky-odex-files/#more-153
alritewhadeva said:
yes you can unodex. http://jf.andblogs.net/2009/09/10/slay-those-pesky-odex-files/#more-153
Click to expand...
Click to collapse
then ill see if unodex'd tattoo and unodex'd TwiztedZero6.14r3 can play nicely together :-D
sounds like a headache to unodex the whole build
*shoots self in head* this will take almost a week man i need my own computer
the classes.dex items go back into the apks right? (sorry that makes 2 stupid n00b questions today
NEVER MIND SCRATCH THIS WHOLE ENTRY
per mister drakes words
dont mix builds its bad!
so build off this droid i will
ok so last night i compiled the two different ideas weve had
1) Mashed Tattoo's APP/framework and merged the lib folder with TwiztedZerox6.14
2)Tattoo Alone with Cyanogens kernel and bin xbin folders and some build.prop changes for LCD DPI density changed from 120 back to default
On test flash i get the same message from both update scripts
(the update scripts had been pulled from the latest cyanogen update to be used in my build)
problem line 64 Chown perm *some numbers* bin:reboot
on both update zips tried editing the update-script and it still has issues
any ideas anyone?
Zarboz said:
ok so last night i compiled the two different ideas weve had
1) Mashed Tattoo's APP/framework and merged the lib folder with TwiztedZerox6.14
2)Tattoo Alone with Cyanogens kernel and bin xbin folders and some build.prop changes for LCD DPI density changed from 120 back to default
On test flash i get the same message from both update scripts
(the update scripts had been pulled from the latest cyanogen update to be used in my build)
problem line 64 Chown perm *some numbers* bin:reboot
on both update zips tried editing the update-script and it still has issues
any ideas anyone?
Click to expand...
Click to collapse
in /system/bin from system.img there is a toolbox symlink "reboot" ? if there is, you have to remove it (because all symlink must be create during installation, as write in update-script)
its actually easy to edit the script ... check every line and try to see! what it is doing , you shouldn need xbin at all, remove all lines about it for now, no busybox nothing
as nk02 said remove all links (do you use linux ?) and then your script hould copy system and data , make a symlink for app_s and change some permissisons that's it.
so clean upp the script , and make your own. I will pst one for you here , make sure you have all files in your system ...
shwan_3 said:
its actually easy to edit the script ... check every line and try to see! what it is doing , you shouldn need xbin at all, remove all lines about it for now, no busybox nothing
as nk02 said remove all links (do you use linux ?) and then your script hould copy system and data , make a symlink for app_s and change some permissisons that's it.
so clean upp the script , and make your own. I will pst one for you here , make sure you have all files in your system ...
Click to expand...
Click to collapse
thanks started using textpa and now my update scripts are fine got the hero+tatto mashup to boot but its giving me all kinds of odex issues
im gunna have to find a UN odex'd hero to mash it with and un odex the tattoo build
havent worked on the ONLY tattoo with cyanogens kernel yet i got busy and i dont have a tester phone just my mytouch and i cant go more than 3 hours with out being able to use it haha
no im not on a linux machine i am still getting comfortable with command line functions and have been doing nothing but reading the android developers page and anything linux related on the internet
my betas are uploading right now neither will boot one boots enough to get into logcat but because i mashed the odex'd builds together i know i know im a bum and i didnt wanna deodexarnt the whole thing (take time to do it right and never do it twice)
next on my list of things to try
get unodex'd hero build and unodex tattoo then mash
see if i cant just get straight tatoo to boot then trim the resolutions of the rom to fit on our 32b devices
any input is greatly appreciated
Zarboz said:
thanks started using textpa and now my update scripts are fine got the hero+tatto mashup to boot but its giving me all kinds of odex issues
im gunna have to find a UN odex'd hero to mash it with and un odex the tattoo build
havent worked on the ONLY tattoo with cyanogens kernel yet i got busy and i dont have a tester phone just my mytouch and i cant go more than 3 hours with out being able to use it haha
Click to expand...
Click to collapse
You can use my Hero build, it's unodexed.
maxisma said:
You can use my Hero build, it's unodexed.
Click to expand...
Click to collapse
wouldnt i need to unodex tattoo as well to ensure that they will work together?
i assume yes since the whole build would be unodexed
**edit**
wich one your new drizzy stuff or the old one thats in sapphire forums
yes would be need to unodexed too.
Can anyone deodexerant the tattoo dump I have no Linux machine
Zarboz said:
Can anyone deodexerant the tattoo dump I have no Linux machine
Click to expand...
Click to collapse
virtualbox ?
Help!
I am willing to help with the Deodex if I can, I already started doing something similar to you but against the latest Cyanogen experimental build which is already Donut.
I am trying to Deodex Tattoo but am struggling, I am trying to get my head round what we need to do to deodex it.
According to the readme of deodex you need to have the phone running the exact firmware you want to deodex (I don't have a Tatoo or know anybody who does), or use a CH Root environment to do it.
This is where I get stuck, are they on about a CH root environment on our phones or within my Unbuntu environment (it is not very clear)? Can somebody give me a clue or even better instructions on the CH root process required to use Deodex?
Thanks
James
james194zt said:
I am willing to help with the Deodex if I can, I already started doing something similar to you but against the latest Cyanogen experimental build which is already Donut.
I am trying to Deodex Tattoo but am struggling, I am trying to get my head round what we need to do to deodex it.
According to the readme of deodex you need to have the phone running the exact firmware you want to deodex (I don't have a Tatoo or know anybody who does), or use a CH Root environment to do it.
This is where I get stuck, are they on about a CH root environment on our phones or within my Unbuntu environment (it is not very clear)? Can somebody give me a clue or even better instructions on the CH root process required to use Deodex?
Thanks
James
Click to expand...
Click to collapse
take my tattoo only build unzip it and take the update script delete the line about system:xbin save and resign then flash this will load the android environment through cyanogens shell for the tattoo i just dont know if it will display anything on the phone itll probably have a bunch of errors in logcat
i just havent gotten this far yet because i dont have a phone that i can flash just to test stuff all i have is my mytouch and i cant afford to be without it for very long and i dont know how to boot custom roms on emulator nor do i think we can boot this due to htc parts missing from the SDK
next on my list to try....
*****************
-get virtualbox up and going and deodexarnt the tattoo build (i think itll boot enough to get dalvik manager to run so we can deodex it)
-once deodexed i would like to see if i can get this thing to boot standalone (if the standalone i have now will boot {not been able to test yet like ive said no device to test with} if the standalone is being a big pain in the [email protected]# and not booting properly or we have issues with screen size differences ill have to stop because my knowledge of these things is limited..)
we cant deodex tattoo without being booted into tattoo
so
oh well for that
lets work on getting original tattoo to boot so we can deodex and build off it
if anyone has started to do these things or is already in the process of doing these things please let me know
Zarboz said:
next on my list to try....
*****************
-get virtualbox up and going and deodexarnt the tattoo build (i think itll boot enough to get dalvik manager to run so we can deodex it)
-once deodexed i would like to see if i can get this thing to boot standalone (if the standalone i have now will boot {not been able to test yet like ive said no device to test with} if the standalone is being a big pain in the [email protected]# and not booting properly or we have issues with screen size differences ill have to stop because my knowledge of these things is limited..)
we cant deodex tattoo without being booted into tattoo
so
oh well for that
lets work on getting original tattoo to boot so we can deodex and build off it
if anyone has started to do these things or is already in the process of doing these things please let me know
Click to expand...
Click to collapse
went through about 15 flashes last night
none booted
the furthest i got the logcat is posted on the OP
i have two more ideas but i need someone to pack my boot.img for me for one of them (i know i should have my own linux machine but im not about to download anything over 100 megs on my tether SLOW!)
and the other ill work on tonight and see if i cant get it to work
So I have a bootable Tattoo build. is that all you need? Different phone but I don't see why it matters. I can unodex but I don't see the point... Tattoo and Hero share a lot of apps and functionality. All I see are cosmetic changes, which I'm working on as well. But, if you tell me what to run I can have it posted within the hour.
I'm not sure what you're really trying to do by backporting to Cupcake based Hero. I can unpack the boot.img, unodex Tattoo, whatever but I don't see what you want to accomplish with this. I don't have your phone so I can't test whether the kernel would work if I mod boot.img for you but it doesn't sound hard. Got the tools in my PATH.
Related
if you want a certain script added, chances are some1 else does too. if you have an idea, or find a script you want added, please either post or PM me. i take a look at this thread alot throughout the day, so i will be able to see your ideas quickly. YOUR IDEAS ARE IMPORTANT
first of all, i did not write this script, i took it from the thread HTC Hero Speedup v2.0 (http://forum.xda-developers.com/showthread.php?t=521421), which was put together by tehseano, who i must thank, however, it seems to only work for Haykuro's Hero ROM
THIS SCRIPT is made to speedup the HTC HERO rom on the g1's. my speedup script is made to work under JACman's. if tried on someone elses, you could brick your phone (although i doubt it), and i will not take responcibility for bricks
trying to use it under JACman 1.72, i couldn't get tehseano's script to work, so im going through a bunch of tweaking and editing for it to work under JACman roms (im guessing twistedumbrella's too).
currently, i'm about to release version 0.2. - released
i have fixed most of the directories and codes except for Battery fix, i have gotten the HTC camera to work, read the readme file
out of curiosity, does any1 have any preference on where i upload the files? want someplace easy and fast, so no rapidshare or anything like that. first working suggestion gets it
please do not use option #8 once it is up, it is not done yet
everything else should be good. this is made STRICTLY for JACman roms, not haykuro's, but twistedumbrella's should work, since it is based off of JACmans
____________________________________________________________________________________________
version 0.2 - http://www.4shared.com/file/113524687/c98398cd/AJZ_HeroSpeed_02.html
very minor changes
fixed the scripts
working on a battery fix
version 1.0 will be more compatible with JAChero 1.8, i expect to release that in the next few day, but this might not be possible because i'm going on vacation
_____________________________________________________________________
I ACCIDENTLY UPLOADED THE BAT AS A TXT FILE. im not gunna change it, so until the next release, just rename the file as a bat
0.1.5: http://www.4shared.com/file/113343120/6c89dd65/AJZ_HeroSpeed_015.html
i must thank dpgc213 for creating the original lockscreen change bat file
Changes:
deleted option to delete pc sync, causes bootloops and doesnt exist
added possibility to change the screen lock image (although doesnt have to do with speed)
added quick directions for changing the lock screen image
____________________________________________________________________________________________
version 0.1 - http://rapidshare.com/files/247165073/hero_speedup_2.0_AJZ_0.1.zip
here's a mirror of 0.1 http://www.4shared.com/file/113320662/7e513586/hero_speedup_20_AJZ_01.html
in version 0.2, expect to see support for the deletion of htc sync, and support for changing your lock screen
can you please include instructions for mac users? thanks good work
did you get it to work with JACman 1.72, you said you would try to tweak it, but did not say if you were successful?
I dont know how to apply the script cuz its made for windows, If some1 put instructions plz?
Franklees said:
did you get it to work with JACman 1.72, you said you would try to tweak it, but did not say if you were successful?
Click to expand...
Click to collapse
i got all the commands and everything working in 1.72 except for #2 to work. #2 will cause a boot loop.
#2 just deletes your htc sync, which idk what it does anyways.
in 0.2, i will try to fix this, as well as add support to change your lock screen
i got the change lockscreen part in, now just gatta see the problem with htc sync
juangil said:
I dont know how to apply the script cuz its made for windows, If some1 put instructions plz?
Click to expand...
Click to collapse
u could try renaming it to something that will work in leopard (er tiger). idk if that would work, im not a mac user. ubuntu and windows
alexjzim said:
u could try renaming it to something that will work in leopard (er tiger). idk if that would work, im not a mac user. ubuntu and windows
Click to expand...
Click to collapse
so if put the optimize.sh file in my sd how do I run it? or is the .bat file the ones that needs to be run? thx
juangil said:
I dont know how to apply the script cuz its made for windows, If some1 put instructions plz?
Click to expand...
Click to collapse
it cant be used for mac users, but basically a bat file just has a bunch of adb commands in it. i can post them for you if you like.
wwwhershcom said:
it cant be used for mac users, but basically a bat file just has a bunch of adb commands in it. i can post them for you if you like.
Click to expand...
Click to collapse
great! that will do it, I appreciate your help
anyone know if HTC pc sync is included in 1.72? if it is, anyone know where it is? once i find this out i can release 0.2.
Wow, this script really made a difference
Henchman said:
Wow, this script really made a difference
Click to expand...
Click to collapse
was aiming for that
juangil said:
can you please include instructions for mac users? thanks good work
Click to expand...
Click to collapse
...Buy a PC lol.
alexjzim said:
was aiming for that
Click to expand...
Click to collapse
When I ran option 3, 6 and 5 in that order without a reboot and then reboot after I did all those I got a bootloop, when I did #5 it was saying success on each one. If I installed dextop-wrapper awhile back like weeks ago do I have to install it again because I didn't install it. I figured I still had it.
jigdagod said:
When I ran option 3, 6 and 5 in that order without a reboot and then reboot after I did all those I got a bootloop, when I did #5 it was saying success on each one. If I installed dextop-wrapper awhile back like weeks ago do I have to install it again because I didn't install it. I figured I still had it.
Click to expand...
Click to collapse
my only suggestion is to wipe and reinstall your ROM, then do everything in order. i cant tell you exactly, because i cant actually see your phone
Okay, thanks I'll try that tomorrow when I get home.
Does this support 1.72 yet?
71CH said:
Does this support 1.72 yet?
Click to expand...
Click to collapse
first of all, i did not write this script, i took it from the thread HTC Hero Speedup v2.0 (http://forum.xda-developers.com/showthread.php?t=521421), which was put together by tehseano, who i must thank, however, it seems to only work for Haykuro's Hero ROM
THIS SCRIPT is made to speedup the HTC HERO rom on the g1's. my speedup script is made to work under JACman's. if tried on someone elses, you could brick your phone (although i doubt it), and i will not take responcibility for bricks
trying to use it under JACman 1.72, i couldn't get tehseano's script to work, so im going through a bunch of tweaking and editing for it to work under JACman roms (im guessing twistedumbrella's too).
currently, i'm about to release version 0.1. - released
i have fixed most of the directories and codes except for uninstalling HTC sync, and replacing the sapphire camera with the official HTC camera. i have gotten the HTC camera to work before, and just need to add in the right codes
out of curiosity, does any1 have any preference on where i upload the files? want someplace easy and fast, so no rapidshare or anything like that. first working suggestion gets it
please do not use option #2 once it is up, it will cause your phone to boot loop - option #2 is now used to change the lockscreen and is completely usable now
everything else should be good. this is made STRICTLY for JACman roms, not haykuro's, but twistedumbrella's should work, since it is based off of JACmans
PC sync is out of all JAChero builds... i spent hours trying to fix something not there . because of this, the next release will be 0.1.5 instead of 0.2
I ACCIDENTLY UPLOADED THE BAT AS A TXT FILE. im not gunna change it, so until the next release, just rename the file as a bat
0.1.5: http://www.4shared.com/file/11334312...Speed_015.html
i must thank dpgc213 for creating the original lockscreen change bat file
Changes:
deleted option to delete pc sync, causes bootloops and doesnt exist
added possibility to change the screen lock image (although doesnt have to do with speed)
added quick directions for changing the lock screen image
__________________________________________________ __________________________________________
71CH said:
Does this support 1.72 yet?
Click to expand...
Click to collapse
Yes.
That's what I'm using ti with. And it's made Rosie completely usable for the first time for me.
Has anyone had the experience where Rosie was really fast when first optimizing using whatever procedure but then lags down over time? That was what I experienced when using a different optimizer. Hopefully this one is consistent.
Hi Guys
I have tried to put together my own config files for the sapphire, these go in the vendor/htc/sapphire directory after you have extracted the source
by no means are they perfect but i hope they will start some fresh development.
http://www.cminion.com/wordpress/2009/08/11/rolling-your-own-android-rom-for-htc-magic-sapphire/
If something doesnt work, or anyone manages to perfect them let me know so I can repost.
please let me know how you get on
Nice work!
Did you try this for a 32A or 32B board?
Looks interesting... anyone tried this for 32A since 32B don't have this issue in the first place?
I have a 32b and someone is testing it with 32a but we are having trouble compiling today its been fine in the past
cminion said:
I have a 32b and someone is testing it with 32a but we are having trouble compiling today its been fine in the past
Click to expand...
Click to collapse
Well keep us updated if you get anything working for 32A since all of 32A users are stuck with the htc kerel... if you need someone else to test you can pm =D
I've been trying my best at building a kernel for 32A, but no matter what I do it doesn't boot at all.
Does anyone know how you can debug a kernel the kernel's boot process at all? I just get hangs or reboots from any of the kernels I build and I've no idea what is missing or where it's going wrong. If it gave some sort of output then I might be able to figure out what I'm doing wrong! (adb logcat doesn't kick in until AFTER it's booted unfortunately)
How have the 32b users gone with this? Anyone managed to boot one?
cminion said:
Hi Guys
I have tried to put together my own config files for the sapphire, these go in the vendor/htc/sapphire directory after you have extracted the source
by no means are they perfect but i hope they will start some fresh development.
http://www.cminion.com/wordpress/2009/08/11/rolling-your-own-android-rom-for-htc-magic-sapphire/
If something doesnt work, or anyone manages to perfect them let me know so I can repost.
please let me know how you get on
Click to expand...
Click to collapse
Hey, just saw your post and I'm taking a look. So far it's OK, but I think you're missing (at least) the keypad files. Also, a little legal note (in case you didn't know), you aren't legally able to pack the qualcomm libraries on the proprietary/ folder. Not that I really care about it, but I thought you should know since maybe you're going against xda rules by posting copyrighted files -not sure anyway-. Maybe it's better if you leave the propietary folder empty (or just with the minimal stuff like the keymaps, audioparametters and .ini files) and let the extract-files script do the job for whoever uses it to compile. After all, if someone uses this, he already has the libraries on the phone
Anyway, I'm going to compile, if I see something else missing, I'll modify accordingly and send you the changes made, ok?
Regards!
PS: Nice work
EDIT: Okay, I did some little changes on the board file definitions,renamed the folder to sapphire-open (to match dream-open added the keymaps, and a kernel & wlan.ko I had laying around (it's still compiling so maybe the kernel doesn't start, but it still needs an hour or so to end the build, but so far, it's not failing). I have packed it, you can get it here: http://rapidshare.com/files/266633357/sapphire_config.tar
If I see something else I'll repost
I need some input im working on porting tattoo over to the mytouch 32b board
Progress:
THIS BUILD WILL NOT BE FLASHABLE YET IT IS SPECIFICALLY FOR INPUT/Developement ONLY!
i am not responsible if you try to flash these roms for any damage that may occur to your device these are not finished and are not bootable still in EARLY EARLY EARLY BETA!
like i said this is where i am at right now with stuff and im hoping to make forward progress
- idea closed staying with only tattoo-
10/03/09
Hero+tattoo Mash Based off Zeroxd6.14r3 (wont boot due to .odex stuff.. need to unodex whole tattoo build recompile and mash with an unodex'd hero)
Merged lib folders and made sure a2dp.so and the other .so out of sapphire folder were in the lib folder
Merged Hw Folder so that sensors were there for hte device
Replaced Framework Folder with Tattoo Framework
Replaced App_S with Tattoo App folder
replaced /system/media with tattoo
cyanogens latest 4.1.11.1 boot.img and wlan.ko
10.05.09
Tattoo Only from the WWE 1.65.405.1 build
Merged lib and hw (for sensors) folders with 1.6 doughnut for magic
added some stuff in system/bin (super user access)
cyanogens 4.1.11.1 boot.img and corresponding wlan.ko added
update-script should be super barebones... really just hoping for a boot right now
http://www.4shared.com/file/137624393/e1c0febe/tattooonlysigned11b.html
** will boot but i dont think itll boot past g1/mytouch screen **
next on my list to try....
*****************
Code:
-get virtualbox up and going and deodexarnt the tattoo build (i think itll boot enough to get dalvik manager to run so we can deodex it) !!!!!!!!! if no one can get tattoo to boot to deodex it or has a tattoo to deodex it then im stuck and the project is pretty much over!!!!!!!
-once deodexed i would like to see if i can get this thing to boot standalone
(if the standalone i have now will boot {not been able to test yet like ive said no device to test with}
if the standalone is being a big pain in the [email protected]# and not booting properly or we have issues with screen size differences im gunna be pretty much stuck until a more experienced dev wants to chime in
just got some direction from Drizzy. He gave me some ideas ill process these ideas and upload tattoonly1.2b.zip this evening. Itll be sometime around 7pm-9pm central standard (im stuck using the neighbors wifi or my tether so uploading SUCKS)
there is hope !!!
http://forum.xda-developers.com/showthread.php?t=564984 if they can port for hero and we can port hero to g1 we can port htc tattoo over to our 32b devices
I DONT WANT A TATTOO ROM!! i am working for an unodexed' 1.6 compatible rosie and corresponding HTC apps (calendar,contacts,messaging,settingswhatever is from the tattoo that sucks app wise is getting replaced with their corresponding 1.5 hero apk counterparts
probably gunna put a hero'ish look to it as well
save for space
No updates ?
Why are there no updates on this ???
Porting tattoo would be more stable then porting hero right ???
the hard part is cuz ofhte way smaller screen size. for updates, check out the sapphire forum. eugene373 is taking over porting it.
chinmayfun said:
Why are there no updates on this ???
Porting tattoo would be more stable then porting hero right ???
Click to expand...
Click to collapse
porting magic sense update would be stable no reason to copy whole phone build when u only wanted sense that would keep drivers intact with working blue-tooth should it not?(dunno)
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 )
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.