No Multi-Touch RC33 ROM - G1 Android Development

Here is a version of JF's RC33 1.41 without the multi-touch kernal included.
This one is JF's RC33 build modified with the PRE-MT kernal (1.31). It includes all the goodies that are standard with JF's builds and was recompiled from his source. This update does include the 1.41 recovery image.
ALL CREDIT GOES TO JESUS FREKE for providing us with the source for his modified ROM's
If you are interested or do not know what JF has added to the original images check this link
Just like JF's RC33 build this does not include the radio update which can be found here(MD5:CF8714D273FB0274574D9E3831E11FDD) this will need to be flashed separately in any order. To revert the radio you WILL NEED TO FLASH BACK TO RC29 THROUGH THE DREAMIMG.NBH file that can be found here
RC33 PRE-MT Kernal (MD5:97167BFDD7957F4D95C1538410003146)
http://drop.io/qyyqvmd#
*UPDATED* RC33 PRE-MT Kernal 1.42 Recovery image, No Amazon MP3, No Stock Email, no Term Emulator (which can be downloaded from the market, the author has been making changes so I didn't want to include it)
http://drop.io/689ghtm#
(MD5:F1B80E314926C7409DDCA6C0EE107626)
Save the zip file to your sdcard named update.zip, boot into recovery mode (home + power), and then press alt+s. I must recommend that you also do a wipe in recovery mode (alt+w) before applying the update as most of the esoteric issues that arise seem to be from not wiping. This will clear all your data/settings/apps, and you will have to re-register once it boots back up.
Again THANKS JESUS FREKE

Cool thanks for this, glad to see it worked out.
Do you think I would need to do a wipe going from mt rc33 to no-mt rc33?
Doesn't seem like such a large zip is necessary.
Does the MT really alter so many files?
Hopefully there will be a mini version that does the same thing

Only the Kernal is changed so if you want you can extract the boot.img and use the flash_image tool to re-image it over your current one. JF has a thread about the flash_image tool and how to use it at this link
The reason it's so large is because its a full ROM you can flash from RC29 etc. You could probably get away with not wiping but I have to recommend it since 90% of the issues people run into doing the updates seem to end up with a wipe so why not skip the issues. Its easy so re-sync contacts and reload apps.

Hahha thanks, so then the only diff is in the boot.img? Cool.
So I could just switch boot.img's and flash whenever I want to switch between normal and MT?
Ima try it righttt now

Any chance for a ADP1.1 No Multi-Touch ROM? Please?

why would any1 one want it without the multitouch?

Because of few problems with the MT version.

I just used fastboot to flash the image nd I gotta say, touch is workin great.
I like it better this way for sure.
Im gonna wait til multitouch gets fixed up and then ill try it again.

Thers is any "problem" with the multi-touch except that devs are not making apps for its kernal. Therefore some apps may act funny.
I personally don't use the MT at all so I don't want it throught the OS. And I don't know if its in my head but the pre-MT kernal seems to give me better battery life.

topdnbass said:
I just used fastboot to flash the image nd I gotta say, touch is workin great.
I like it better this way for sure.
Im gonna wait til multitouch gets fixed up and then ill try it again.
Click to expand...
Click to collapse
Good to hear. Flashing the boot.img is really all that's needed but I wanted to make a full update just for the exercise etc since this is fairly new to me and fastboot might be more difficult for some.

Yeah It's not really a problem.
I figured it's good that both ways are on here now though.
Thanks again!

If youre already running jf rc33 do you need to do a wipe?

Ah, apparently I didn't announce mine with enough fanfare
Oh well, it is a fun exercise.

Uh, and so why would I ever want or need this flash? Dead thread. Nothing added and of no value.
But nice try. Must really like your iPhone and your paycheck...

learningmore said:
If youre already running jf rc33 do you need to do a wipe?
Click to expand...
Click to collapse
you will probably be fine without a wipe but i recommend wiping when flashing

quietlurker said:
Ah, apparently I didn't announce mine with enough fanfare
Oh well, it is a fun exercise.
Click to expand...
Click to collapse
Glad you got the issues worked out as well. not trying to be disrespectful or anything but I told people i would make up a ROM so i did and figured it might as well have some instructions in case someone needs them. I did see that you had put one up but at the time thekills was complaining about the browser so I went ahead with my version.
and it is a fun exercise

Edited:double post

justanothercrowd said:
you will probably be fine without a wipe but i recommend wiping when flashing
Click to expand...
Click to collapse
Ok i flashed without wiping everything is running good. Phone is much more responsive touch wise. Everything else still works great. Thanks to you and JF

Gadzks said:
Uh, and so why would I ever want or need this flash? Dead thread. Nothing added and of no value.
But nice try. Must really like your iPhone and your paycheck...
Click to expand...
Click to collapse
There were request from a number of people for a non multi-touch version. If your not interested simply don't use it.
And as for the other comments....lol

justanothercrowd said:
Glad you got the issues worked out as well. not trying to be disrespectful or anything but I told people i would make up a ROM so i did and figured it might as well have some instructions in case someone needs them. I did see that you had put one up but at the time thekills was complaining about the browser so I went ahead with my version.
and it is a fun exercise
Click to expand...
Click to collapse
No worries. If you keep updating your branch in the future, you may want to be sure and change the ro.modversion in the build.prop file.

Related

Getting confused, I have RC30 (Rooted), Going to update

Hey all, Ill only ask this once, (Since after this time, Ill know for future updates and be on the right path =) )since this G1 is so new dev wise, its getting confusing when im studying everything all at once and only updated rooted once to the custom RC30. I saw the newer update is RC33, now when I apply that, is it required EACH TIME to wipe the device? Im asking cause it would be a pain to reinstall each app I had installed there to begin with. I know I wiped the 1st time I rooted and updated. So just wanted to check.
Also whats the new additions in these updates? Any good changelogs out there? I kinda like keeping the Tmobile US stuff on mine, but root access is awesome. =)
Thanks for any update tips out there atm.
Edit, My G1 is still on Firmware 1.1 is that a seperate update or how is everyone updating that with the custom stuff? Thanks. (And do I need that FW update before going RC33?)
Nope, you won't lose anything when you upgrade the firmware normally. Going from JF RC30 to JF RC33 should be fine
Check the stickied topic on the top of the forum to find out more:
http://forum.xda-developers.com/showthread.php?t=475381
The changelog is somewhere in there.
Thank you. =) I didnt read that one since it was talking about for UK users. Heh. Least it explained things a lil more. =DDD
What about the firmware? Seems Ill have to do the new radio too, but wondering.. is that radio one for US too or only uk? Since its in a UK thread. =/
Nah, it's not a UK topic. He just modifies the title when he adds something new. The radio should be for the US version. Just download the radio and JF RC33 and throw them on your microSD (one at a time obviously, named update.zip).
Firmware 1.1 is just like the base firmware number, you can ignore that. Firmware 1.5 (I think) is cupcake, so you get the idea.
Ok so the firmware is nothing major atm to update or would you still upset it? I havent looked into cupcake yet.
No, completely ignore the firmware number, the only numbers you want to look at are RC30, 33, etc...
Ok this is odd. I updated fine to RC33, however when I try to get back in recovery mode to apply the radio rom, it wont go into the recovery mode. It just keeps rebooting to the G1 screen when im holding the home button. Anyone seen that before or how to get back into the recovery mode?
Anyone have any ideas?

Issues going from UK JF-RC9 to JF-RC33

So im just wondering are there any issues in doing this??
Im assuming that i would have to possibly update my Radio as well but im just wondering is there any downside to doing this?? im already rooted and the G1 is (currently) on a clean install of RC9 with nothing installed
so is there anything stopping me getting an RC33 image and flashing right at this second??
Dantehman said:
\
so is there anything stopping me getting an RC33 image and flashing right at this second??
Click to expand...
Click to collapse
Good to go. Just remember to wipe your /data since you're changing the build region (Alt+W in the recovery tool).
aww sweet !! gives me something to do whilst passing time in the office
Since its JF's RC9 anyway do i need to bother regaining root or shall i just leave it as is with the recovery.img and the update.zip on the SDCard??
You already have root (JF RC9) and your target build (JF RC33) already has root, so you don't need to do anything. Just place the update.zip in the sdcard and get it on.
Followed Quoted and Done!!
Sorry for the newbish-ness,,,, mmmmm RC33,,,,, mmmmmm no change (more themes lmao)
don't forget to change your sig. I'm DLing the RC33 myself now that I know it works. BTW, which didi you go to, 1.42 or 1.43? And do 1.42 themes work with 1.43?
ghrayfahx said:
don't forget to change your sig. I'm DLing the RC33 myself now that I know it works. BTW, which didi you go to, 1.42 or 1.43? And do 1.42 themes work with 1.43?
Click to expand...
Click to collapse
Im not sure about themes as its only just finished, but all is working fine, just installing some apps to keep me going till later on and then ill give themes a bash
i grabbed the 1.42 from here;
http://jf.andblogs.net/2009/02/11/jfv143/
and i also go the buildenvironment from there too,,,, just incase a custom boot image takes my fancy
Ok using Astro i've managed to install some of my apps from the SD Card and they are all working quite nicely
Additionally the Wifi Tether App is installed,, but cant check that till i get in from the office
Awesome. I just did this ti mine, and all is working on mine as well. I installed the 1.42 Rc33 aero theme as well. Looking good.
Thats how we Brits roll!! lmao

Some help needed adding root+tethering to a ROM

I haven't found any solutions to my problem on here, so I figured I'll have to try and make my own solution. Basically I want to take the MT3G stock, vanilla, retail COC10 build, and add root and tethering. That's the probably number 1 requested feature that people want, and I'm trying to find the solution for at least myself, if not to help others. I don't want all the extras and, no offense, garbage that is in all these other ROMs. I understand there's a need for that for some people, but I'm looking for just a clean, retail image for my MT that is very similar to the JF builds. Add root and netfilter/iptables. I'm aware JF added other things, but I don't want those. So here's my ideas for a solution...
I've got an obsession with this new 1-click Root program. I was able to get Cyanogen's 1.4 Recovery on my MT3G without flashing anything else, it's quite a nice trick for now. I've downloaded the original MT3G shipping COC10 image/update.zp and know that as long as i'm not off flashing Radio and SPL i'm pretty much safe. I did a nandroid backup anyway.
I'm going to for the first time try and dabble in ROM development/tweaking. I found in a thread on here someone mentioned how easy it was to add root on the stock ROM. Link to that particular post: http://forum.xda-developers.com/showpost.php?p=4333604&postcount=38
I haven't tried that just yet as i'm on a PPC Mac so no easy way to do it except trying VirtualPC with XP which isn't perfect. So, here starts my questions...
If the assumption of a "rooted" recovery image could work to put the SuperUser apk in, I should be able to do this, right? Again, remember I'm on Cyanogen's 1.4, but still have my stock, retail myTouch COC10.
Most of the commands listed to do over the ADB could probably be done in the recovery's console, correct? I will have no computer to do anything today, but I will have VNC/RDP access to my Mac with VPC/XP to do anything that may require a computer to compile. I figure then i can package it up and email it to myself, should I need to do that.
Now if that takes care of the root half of what I'm doing, how about the tethering... I understand haykuro has compiled a kernel that pretty much everyone is using in their ROMs that has netfilter enabled in it. How would I get access to that particular kernel so that I could use it as say a simple Update.zip much like the one for the Dream/ADP/G1 that is here: http://code.google.com/p/android-wifi-tether/wiki/ADP15KernelUpdate
If that is something in these forums, I haven't found it yet. So please, point me in the right direction. Assumably, with a kernel update and the root added, I would have everything I need, right? I'm not saying I want to break into the MT3G official update and start compiling it as an all-in-one ZIP that could be easily flashed to. That's out of my knowledge. But I would like to at least have the steps so that maybe it can be reproduced for the (apparently) minority out there that would like to stay as vanilla as possible.
UPDATE:
Okay, so I found a boot.img here (http://cluster.physik.uni-freiburg.de/~kuhnen/android/android.html) and I thought to myself what exactly IS the boot.img? That's not the SPL, right? or is it? Is it just the kernel? I never thought about it before, I was always flashing it, but never knew WHAT it did. If the file I found that is for vodafone works fine with the myTouch system, then I may have solved the other half of my problem. Seriously, anyone able to help? Or at least let me know what BOOT.IMG is.
Or even better yet, can't I just yank the BOOT.IMG/kernel out of haykuro's ION R2? Is it a hard task to do that? I would assume that the Ion was just the myTouch rebranded before the myTouch came out. So the kernel couldn't have changed much, if at all, since then. And since haykuro did enable tethering on that kernel, I could assumably use that, right?

Leaked 2.1 for the Eris?

http://forum.xda-developers.com/showthread.php?t=641588
http://imgur.com/AJkH6
It sounds like its a working build, could we use this to our advantage? Like getting the cam working on our current 2.x builds?
Gogogogogogogogo! Please someone port this!
that topic looks soooo sketchy haha
but if its real
Ska8erMush said:
that topic looks soooo sketchy haha
but if its real
Click to expand...
Click to collapse
i read the posts; it seems real. they got it to flash after applying a patch to fix some mismatch, and there's a picture posted.
i'm pretty sure its real.
Looks pretty real to me, kinda wish I had a eris to test it on myself, but oh well. If this turns out to be real it wouldn't be to hard to port because of how close the two phones are right?
justinisyoung said:
i read the posts; it seems real. they got it to flash after applying a patch to fix some mismatch, and there's a picture posted.
i'm pretty sure its real.
Click to expand...
Click to collapse
whoa i should have read the whole topic
now i am super excited!
Some links
Thought I'd try to post these, so you don't have to go look.
Link for 2.1 .zip- Corrupted though
mediafire .com/ ?ycd4wwm12gx
and here's the patch instructions that one of the developers over there made.
zanfur said:
Well, someone might want to try this. I've gotten the unzip errors to go away, but I haven't tested it on an actual device. Anyone want to try? I've uploaded the (very tiny) binary patch. You'll need the bspatch utility (windows port here: ]http:.//sites.inka.de/ tesla/f_others. html#bsdiff). Rename the one you downloaded to something else like PB00IMG-corrupt.zip, and run this:
Code:
bspatch PB00IMG-corrupt.zip PB00IMG.zip eris-eclair.bpatch
That will create a new PB00IMG.zip that is no longer corrupt. Someone test it on a phone and let me know if it works!
Click to expand...
Click to collapse
for now guys, i'd say don't flash this. its definitely risky.
if you open up the file there's a radio img on there, which should make all of us who don't have heros to spare nervous. considering how flashing radios is basically the ONLY way to brick our phones, it's probably a huge risk. i'm not sure if we can even flash this on our phone.
since most of us are probably looking forward to using camera, etc, maybe the kernel img is the one we could try and get working on our 2.1 builds? that's the boot.img, maybe we could try extracting it and signing it instead.
very interesting. im DLing now and gonna take a look at some stuff and see if anything in it is usuable to fix anything.
and i wouldnt flash this if i were you. it should brick your phone. if not tell us lol
I think i peed a little.... This could be HUGE!
one of the screen shots posted shows the kernel as .29...that's what we needed right?
The newly patched rom is here http://thekrtek.net/
Got a good feelin that Christmas is coming early this year, LOL
I sure hope so. Not getting my hopes up but this could be a turning point.
odd.. the system img keeps telling me its corrupted. so i cant extract anything. re downloading i guess..
If anyone gets this to boot without bricking the phone BETA TESTER HERE!
are you using the link in post 99?
Avalaunchmods said:
odd.. the system img keeps telling me its corrupted. so i cant extract anything. re downloading i guess..
Click to expand...
Click to collapse
i extracted it just fine using unyaffs
@avalaunchmods- you have to apply that patch that the eris people came up with.
okay, so i mentioned in my earlier post that we might not want to flash this cause of the ominous presence of the radio.img. or maybe i'm the only one who would feel nervous flashing another radio onto our heros.
like i said, we probably want the boot.img, which is basically the kernel. so i zipped up and signed the boot.img from the leak, and i'm posting it here.
now, i don't have 2.1 installed, and you can flash this at your own risk. of course, i won't have responsibility.
though, the worst that could happen is really just a boot loop. kernels don't really brick phones... at least i don't think so.
for you brave souls out there.
i tried flashing it to a 2.1 rom. it didn't boot. we got some work to do... haha
justinisyoung said:
@avalaunchmods- you have to apply that patch that the eris people came up with.
okay, so i mentioned in my earlier post that we might not want to flash this cause of the ominous presence of the radio.img. or maybe i'm the only one who would feel nervous flashing another radio onto our heros.
like i said, we probably want the boot.img, which is basically the kernel. so i zipped up and signed the boot.img from the leak, and i'm posting it here.
now, i don't have 2.1 installed, and you can flash this at your own risk. of course, i won't have responsibility.
though, the worst that could happen is really just a boot loop. kernels don't really brick phones... at least i don't think so.
for you brave souls out there.
Click to expand...
Click to collapse
you don't need to apply the patch if you aren't flashing it, which we clearly aren't. we're porting it. we're working on porting it to our phones, we don't wanna brick our phones by flashing the radio in that rom

[ROM] [TEST, NOT FOR NOOBS] Rogers Sapphire Sense Port. Android 2.1 Sense. [9/15]

Quick throw-together. I highly reccomend one of pershoot's kernels from here: www.droidbasement.com/db-blog
Please use one of those. They're much more efficient than the king kernel i've included.
Features
Friendstream
Flippy clock (from SMOKI X)
King stuff (twitter.com/kingklick92)
Gapps
A2SD
Sense
Stable
Maps
Pretty
NEEDS A BIG EXT PARTITION AND A SWAP.
Good luck!
http://www.mediafire.com/?soscld37b0q6wiz
THIS IS UNSIGNED, IF YOU AREN'T USING CLOCKWORK, YOU SHOULD FIGURE OUT HOW TO SIGN IT YOURSELF. I'LL RELEASE SIGNED VERSIONS LATER.
EDIT YOU NEED A 114 MB SYSTEM FOR THIS VERSION DUE TO A 25MB BOOT ANIMATION, PLEASE USE MTD UNTIL I FIX IT
i got you bro. once i get my son to sleep ill test. you know anything yet? data/cam/wifi/gps etc? if not its cool, thats what tests are for.
ok, just doing this for people who dont want to sift through for the signed version: not signed by me, boot animation not swapped by me, *******there is a green bar at the bottom for status of install on boot note though, even after the bar is full it will still take a second IF YOU HAVE ADB INSTALLED RUN A LOGCAT, AS LONG AS YOU SEE THINGS MOVING YOU ARE GOOD. ********. let it sit for awhile like usual after it loads (20+ min). you also have to input the tmo apns to get svc.
link to signed version of the rom
http://goo.gl/opI3
tmo apn's:
http://goo.gl/bNtU
will post back a working/not working in a min.
i would also suggest not doing the system update that it says is avail once you get data working.
Love this.
Sent from my HTC Dream using XDA App
Is this compatible with a 32B Sapphire? Or would it be, to the best of your knowledge?
opethfan3 said:
Is this compatible with a 32B Sapphire? Or would it be, to the best of your knowledge?
Click to expand...
Click to collapse
yes this is a port from the 32a rom to 32b. its not signed so you can only flash via clockwork right now. clockwork doesnt require a signiture for it to be able to flash. if you use amon_ra just wait. im booting into linux after i post this now that i have my son asleep and will look into what can possibly be trimmed down then will sign and post up after im done.
ok, decided not to mess with anything, i dont use some stuff but others do, its signed and im gonna test now, just got done doing backup on current rom and will post if it flashes.
need to wait, since i have amon_ra.
Allright!! looking forward to this, I could sign the rom myself but ill wait to see how the rom works for you guys and im also waiting for a class 6 sdcard that I purchased a few days ago... anyways, im gonna try it with the class 4 i have right now after you try it and maybe cut some size
i hate clockwork. and it wont sign for me for some reason. idk why.
can someone please sign this so we can flash.
Good luck, guys. Really interested to see if this works.
im really going to enjoy triming this fat lady and mod a few things
anyone able to sign this thing yet?
Can you make a version that doesn't require an ext partition? Im on a mytouch 3g, should be able to handle it.
can't get it to sign (then again this might be my fault) how about first person to get this signed/flashed uploads some screenshots
btw: i'm using the autosigner
I'm downloading and signin... I replace the bootanimation to one less heavy??
p.s. sorry for my english
edit: I'm uploading to mediafire..if it finish in 5 minutes I give the link...if don't... I must go to work..link tonight..sorry
p.s. I've change the bootanimation..20 mb saved
http://www.megaupload.com/?d=EO5X0HBC
Click to expand...
Click to collapse
I simply signed the original file. gl
Download limit is exited
roalex said:
I simply signed the original file. gl
Click to expand...
Click to collapse
People will need the MTD hack to flash this.
asb123 said:
People will need the MTD hack to flash this.
Click to expand...
Click to collapse
I know, it is pretty easy to do it. I leave it to the devs to play with the size.
asb123 said:
People will need the MTD hack to flash this.
Click to expand...
Click to collapse
No, I take off the bootanimation of 20 MB and replace with one of 640kb... and I don't use MTD partition tonight the link..now I'm @ work...
p.s. I'l make a senseless rom
anyone tested it now? i want results; nothing about uploading elsewhere, signing mtd patch etc;
there are enough threads about it. there is a good working signing tool in xda.. search for it as well as tuts for it;
i think this thread should focus on the rom as it is something very interesting and new.
i wont try it at the moment cause i softbricked my phone with mtd patches.
please tell how the rom is...
EDIT: btw i know that this post is senseless concerning the original topic but i just want that this thread stays focused..

Categories

Resources