Database Info

Getting update.zip with test key working on froyo

Hi guys, it just came to my mind that test-key signed update.zip files were working back in the eclair days, so i guess the problem is the new recovery in the froyo builds needing Samsung signed files. Same problem was present on the sgs when it moved to froyo, but the devs there managed to change back to old recovery to make them work again, would be nice if someone could find a similar solution for the sg3 also... for more info search for recovery 2e 3e howto in sgs dev section... i am very busy at the moment and go for vacation on Sunday so wont find time to look into this before beginning of March, but eventually someone else could do it and just needed the hint....

Ok, to give this a bump, i need someone with a eclair rom installed and a rooted system. What i need is two files: /sbin/recovery and /sbin/recovery.sh
I think if we swap those files in jpf or whatever Froyo version we could use update.zip files again...

FadeFx
I have JK1 but in sbin directory I have only recovery file, no signs of recovery.sh

sorry, my bad, recovery.sh is part of the modified clockwork mod recovery on sgs custom kernel. also i am in conversation with hardcore about this, and eventually wed have to change the file in initramfs of the kernel... but we will see. to bad i go on vacation tomorrow and will be away for 3 weeks (going to thailand, cant wait to be there...) so i wont have time to complete this, but i will gather info and eventually gsam101 could compile a zimage with old recovery...

Ok, here is my pm conversation with hardcore, seems it can be done easily with loosing new recovery, or the complicated way keeping new recovery for system calls (CSC changes and stuff) and loading old recovery when using 3 button combo. All this is done by recovery.sh
hardcore said:
No u replace /system/bin/recovery in the rom, not kernel.
For kernel if u want to reroute to another recovery u have to use some shell script logic. Check out the initramfs source of my kernel for recovery.sh.
ok, thanx... so we would have to change the file /system/bin/recovery in the zimage´s initramfs to exchange recovery, right?
can we also put the replacement recovery into /sbin to replace the original? and if how is it then called when actually entering recovery mode so we dont enter the old recovery?
thanx Gerd
The recovery executable that comes with the ROM is actually in /system/bin/recovery
Modified kernels like mine have another CWM recovery in the kernel which is in /sbin/recovery which is compiled into the kernel's read-only initramfs.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Content of recovery.sh:
(lagfix stuff is about sztupys lagfix for the sgs and can be ignored for g3 at the moment.
This replaces stock froyo recovery (3e) with clockwork recovery, but same procedure applies to old 2e recovery.
Code:
#!/sbin/busybox sh
/sbin/busybox cp /sbin/fat.format /system/bin/fat.format
# use default recovery from rom if we have an update to process, so things like CSC updates work
# Use CWM if we simply entered recovery mode by hand, to be able to use it's features
if /sbin/busybox [ -f "/cache/recovery/command" ];
then
# if we use the original recovery it might modify the filesystem, so we erase our config, in order to avoid regeneration
# of the filesystems. The drawback is that the lagfix has to be re-applied by hand
/sbin/busybox rm /system/etc/lagfix.conf
/sbin/busybox rm /system/etc/lagfix.conf.old
rm /sdcard
mkdir /sdcard
#/sbin/rec2e &
/system/bin/recovery &
else
# TODO: CWM is a bit more intelligent, but it might fail to
/sbin/recovery &
fi;
Hope someone can make use of this to get update.zip working again...

Nobody looked into this yet? This would make much things easier for us...
Bump

....
realy hope we get some good progress and development on this thread....
sry but im just a noob and flashing is all i do right now
but if i can give any help feel free to ask

Gonna check this out. If I get OCD about this, v1.2 will be delayed.
This could be really useful. For everyone.
Sent from my Lestatious v1.2 Galaxy 3 FROYO

Lestat, i think this is info enough, if not pm me with the questions and ill do my best to find out.

FadeFx said:
Lestat, i think this is info enough, if not pm me with the questions and ill do my best to find out.
Click to expand...
Click to collapse
Alright. Will do chief. Gonna bookmark this thread so I remember tomorrow.
Sent from my Lestatious v1.2 Galaxy 3 FROYO

I have the 2.1 recovery file. . If anyone interested i think i can post if xda allows. ..
Sent from my GT-I5800 using XDA App

I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.

Gsam101 said:
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Click to expand...
Click to collapse
How buggy is it?
And i noticed that's where recovery was also. I was like, Hmm. Strange.

The Dark Lestat said:
How buggy is it?
And i noticed that's where recovery was also. I was like, Hmm. Strange.
Click to expand...
Click to collapse
Like i had to flash my phone back to make it work ^^

Did u use the sgs version of cwm or did u do an own port for the g3? I guess the sgs version wont run due to different bml layout

Gsam101 said:
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Click to expand...
Click to collapse
Hi Gsam101
I interested in compile custom recovery too.
Can You please share build configs for apollo projects?

just wanted to bump this thread, since i think we should now have devs that should be capable of doing such stuff, update.zip support is normally a must have for any android device

is this helpful in any way? -> http://forum.xda-developers.com/showpost.php?p=12244509&postcount=159

No, not yet. Clockwork needs to be ported to our device to run, which i am not able to do. If u can port it i can eventually give some hints...

i have wrote to the developer of ROM Manager APP (Clockwork Recovery) asking him to support our phone. I wrote just because i saw
Don't see your phone? Email me if you want to help me get it working!
Click to expand...
Click to collapse
on his page (http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html)
i'm not good at programming so i think if the developer replies and the answer will be yes then someone like FadeFx or anyone else who can help should contact [email protected] or [email protected]

SK4G Development

Some of you may know me and some not. I was asked to help out on the SK4G development, so here I am.
I have some questions first.
1. You are using CWM?
2. Amend or Edify?
3. Do you have the drivers and adb set up yet?
Depending on the answers I can put out a couple of tests and then get to work on this.
I will need your newest deodexed framework-res.apk, twframework-res.apk, settings.apk, services.jar - and others as needed.
If you do not have a deodexed rom yet then I need a copy of your systemfs.rfs or a full odin to deodex it myself. I have the system dump, is this your newest rom? If so then I have already deodexed it - just let me know.

1. Yes, the epic 4g version which is buggy
2 don know
3.yes
Sent from my SGH-T839 using Tapatalk

1) No. It doesn't sound like the currently available CWM firmwares work well on the SK4G. I am waiting for one designed for this hardware. I have run CWM on other handsets, of course.
2) No. Had not heard of those until you'd mentioned them.
3) Yes. Working well. We're all set here, at least.
System dump: There only seems to be one ROM/firmware version for this phone so far. The one you have should be current. I pulled mine in this thread:
http://forum.xda-developers.com/showthread.php?t=1037403&page=5
Specifically here:
http://forum.xda-developers.com/showpost.php?p=13210149&postcount=59
I'm happy to help further. Please simply let me know what you need.
And thanks for taking this on! This could be a solid phone without some of the bloatware trash foisted on it.

1. They are using the one click root for the epic by noobnl which installs CWM 2.5.1.0
2. Amend though can't you just use update-binary and make it compatible with both

blu9987 said:
1. They are using the one click root for the epic by noobnl which installs CWM 2.5.1.0
2. Amend though can't you just use update-binary and make it compatible with both
Click to expand...
Click to collapse
Yes, but I am old school and still use amend most of the time and needed to make sure it was going to be compatible.
Once I see some feedback on the theme I posted I will move forward - I just need to know how it turns out so I will have a better understanding of the phones layout.
Might need to send Koush a message and see if we can get a proper recovery going.

I really would love it if this phone got some custom roms. I don't want to get rid of it. But I put a ad up on craigslist to trade for a mytouch 4g.
Sent from my SGH-T839 using XDA App

Also as far a getting a proper working recovery, i think we may need a recovery that supports the ext-SD card. our internal memory isnt used by us because its so small. its used for things like installing apps i believe. if you use a file manager you'll see the only available SD card is the external one and same when mounting the phone. i think the epic and vibrant recovery would work just fine except we'd need one that supports the external SD card.
there is a kernel called dead horse that i used on my vibrant that had this support for ext SD but i dont think theres a way to get just the recovery out of it. hopefully someone might know a way to direct CWM to our ext SD then we might be on to something ..

ayoteddy said:
Also as far a getting a proper working recovery, i think we may need a recovery that supports the ext-SD card. our internal memory isnt used by us because its so small. its used for things like installing apps i believe. if you use a file manager you'll see the only available SD card is the external one and same when mounting the phone. i think the epic and vibrant recovery would work just fine except we'd need one that supports the external SD card.
there is a kernel called dead horse that i used on my vibrant that had this support for ext SD but i dont think theres a way to get just the recovery out of it. hopefully someone might know a way to direct CWM to our ext SD then we might be on to something ..
Click to expand...
Click to collapse
Its just a driver issue. We need to know exactly which SD card reader is in the phone and see if we can contact the manufacturer for the source.
I do not know how to decompile things like drivers, but I would like to know so I could get the ball rolling on this.

I'd love to see development pickup on this phone.
I've had my G1 since Dec 08 and happily rooted and did whatever I wanted to do it with the huge support from the developer community that the G1 received.
I'm keeping myself stock until someone gets Clockwork working with nandroid and there's an unroot method.

d4n137_91 said:
I'd love to see development pickup on this phone.
I've had my G1 since Dec 08 and happily rooted and did whatever I wanted to do it with the huge support from the developer community that the G1 received.
I'm keeping myself stock until someone gets Clockwork working with nandroid and there's an unroot method.
Click to expand...
Click to collapse
I feel the exact same way. I just picked mine up today and I really want to dive into it.

Yeah man, id like to see some development for this phone. I'm willing to help with whatever. This forum seems very dead though. Let's hope it picks up.
Sent from my Sidekick 4G using XDA app

what is the sdcard mounted as? mmcblk0p1? mmcblk1p1? This is key to getting recovery set up.

Where do I find that? I just rooted the phone but I haven't flashed the buggy recovery image
Sent from my little sidekick

gearhead27 said:
Where do I find that? I just rooted the phone but I haven't flashed the buggy recovery image
Sent from my little sidekick
Click to expand...
Click to collapse
adb shell
cd sys
cd block
ls
pastebin that info
that should tell me what I need to know

ive got it. it's mmcblk0p1
Same as the Vibrant, but theirs is mounted to internal sd. I would just need to switch up some stuff.
1st and foremost.... I need your guy's initramfs from your kernel

Idk too much about the initramfs nor how to extract it.
If I'm right the zImage is the kernel maybe this could help you so I've uploaded it to dropbox aswell.
http://db.tt/hhJIGXn
If it needs to be done from our phone could you point us in the right direction on how to get the initramfs.
Sent from my SGH-T839 using XDA App

So exciting seeing the development picking up

so happy to have someone look in this 4rum......im willing to help,,,,,if you guys need someone to be a tester.....just let me know....

ayoteddy said:
Idk too much about the initramfs nor how to extract it.
If I'm right the zImage is the kernel maybe this could help you so I've uploaded it to dropbox aswell.
http://db.tt/hhJIGXn
If it needs to be done from our phone could you point us in the right direction on how to get the initramfs.
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
Thanks, I'll get you guys something to test with tomorrow night when I get to work.

krylon360 said:
Thanks, I'll get you guys something to test with tomorrow night when I get to work.
Click to expand...
Click to collapse
can't wait to test it.....thanks a lot

[ROM][KERNEL]GT-S5660 EXT2 Coming SOON

I am very close to completing my ext2 ROM... benchmarks are going very well...
I might as well add ext3 and ext4 support... But first ext2!
To do
testing
tweaking
Complete
searching everything what I might need
Feel free to donate to speed up the work!

ext2 is FULLY WORKING GUYS!!!!

Any chance to be beta tester?

Actually hmmm let me think
Do you know the right buttons to press to go into recovery mode and/or download mode ???
The process so far is:
1. Install CWM Recovery
2. reboot into CWM Recovery
3. Now connect phone to computer
4. adb shell (as superuser)
5. ... converting cache and data commands ...
6. Now put phone straight into Download mode
7. Connect phone to computer. And flash my tar file
Then your system will act very strange on first start... Like artifacts... But after that everything runs perfectly normal. I believe the system has to rebuild or something like that
Benchmark:
Stock rfs: 1085
ext2 data and ext2 cache: 1645
I am still working on the system partition though... Since that one has to be backed up and everything has to be put back afterwards. And loads of crappy permissions.
But what I got so far works... It's still very buggy. Specially the ext2 being detected as ext4 after a datawipe... So if you want ext2 you can't do a datawipe... Personally I don't find it worth the hassle... But still I am doing my best.
I hope someone more capable will take my job over or point me in the right directions. I have been asking guru's around here in hope they would help me. But they do get tired.
Bugs:
- Booting into CWM and mounting /cache and /data there will make the partitions being detected as ext4... However this is not an issue at this point but still it shouldn't be happening... It may cause problems
Features needed:
- An easier conversion process. This could be done if someone helps me with my init.rc file to be able to detect the filesystem and mount it using correct filesystem

Very nice progress so far m8. whis i could help but as i said except testing i aint of much use so far

You will be !I promise! The only disadvantage is I don't know what will happen in many cases. I have to work those things out first to make sure nothing bad can happen...
I need to make one change to the boot.img related to the file system check. After that I can release it to be used for normal rfs systems as well.

Any progress made recently? Really looking forward to this!
Sent from my GT-S5660 using xda premium

I am stuck...
I need to know how to mod recovery.img
+
+
in the boot.img:
- I need to do something in the init.rc file
- sbin/init.sh ???
- sbin/pre-init.sh ???
Let's say the ext2 works, but it's a long process and not so handy to get it work... Let's say you need to flash 3-4 times in odin before you have it work properly.
I am trying to make it simple. I need a professional developer to clear some things up for me... But they seem to look down or even to think I am not worth explaining... I know it's much to explain. But I want to learn.
If someone wants to help me that's more than welcome

djjonastybe said:
I am stuck...
I need to know how to mod recovery.img
+
+
in the boot.img:
- I need to do something in the init.rc file
- sbin/init.sh ???
- sbin/pre-init.sh ???
Let's say the ext2 works, but it's a long process and not so handy to get it work... Let's say you need to flash 3-4 times in odin before you have it work properly.
I am trying to make it simple. I need a professional developer to clear some things up for me... But they seem to look down or even to think I am not worth explaining... I know it's much to explain. But I want to learn.
If someone wants to help me that's more than welcome
Click to expand...
Click to collapse
Check your PM

You can use the files from galaxy ace roms with ext4 there is a big chance that this will help you out!
Project seems death! I will try to make everything ext2 tomorrow or so!
Sent from my GT-S5660 using xda premium

ROMS?

Has a ROM been made for the device yet?

As soon as one is made I will be one happy user as this tab has soooo much potential to be great
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!

Yeah i know i need one now lol

bkundert21 said:
Yeah i know i need one now lol
Click to expand...
Click to collapse
Why? What would you like a replacement firmware to do? Remove bloat? Do that with titanium backup (or anything else that can 'freeze' pre-installed crud.) Change the launcher? You can already do that (but it seems most of the replacement launchers are designed more for phones.)
What do you want different that you can't already change?

garyd9 said:
Why? What would you like a replacement firmware to do? Remove bloat? Do that with titanium backup (or anything else that can 'freeze' pre-installed crud.) Change the launcher? You can already do that (but it seems most of the replacement launchers are designed more for phones.)
What do you want different that you can't already change?
Click to expand...
Click to collapse
I gotta say I agree with Gary. Now that we have root and CWM (thanks to Gary) there's not much more I feel compelled to change I can already with root. Perhaps a custom kernel we can OC but this danged this flies now. Perhaps someone can come up with something that'll amaze us all (and that would be very cool!) and I'll be all over it. Right now with ICS looming it might be a better allocation of dev resources to just lay back and wait/see what that brings?
Now custom themes.....THAT would right now peek my interest. Learned a few things from hatman41 on the TF. This might be an excuse to dig back in.
Just an opinion.

skeeterpro said:
I gotta say I agree with Gary. Now that we have root and CWM (thanks to Gary) there's not much more I feel compelled to change I can already with root. Perhaps a custom kernel we can OC but this danged this flies now. Perhaps someone can come up with something that'll amaze us all (and that would be very cool!) and I'll be all over it. Right now with ICS looming it might be a better allocation of dev resources to just lay back and wait/see what that brings?
Now custom themes.....THAT would right now peek my interest. Learned a few things from hatman41 on the TF. This might be an excuse to dig back in.
Just an opinion.
Click to expand...
Click to collapse
I'd like to see a r/w external sd card. Having it be read-only is forcing me to change my process of working. But I do agree with the others, with root and cwm the tab is very very good.

otamctech said:
I'd like to see a r/w external sd card. Having it be read-only is forcing me to change my process of working. But I do agree with the others, with root and cwm the tab is very very good.
Click to expand...
Click to collapse
Really? I can change r/o to r/w and back again with Root Explorer in extStorages

skeeterpro said:
Really? I can change r/o to r/w and back again with Root Explorer in extStorages
Click to expand...
Click to collapse
yes i can do that also, but even when it is in r/w, i cant say, save an excel file to the card using quickoffice or any other app for that matter. It will only let me save to the built in storage

otamctech said:
yes i can do that also, but even when it is in r/w, i cant say, save an excel file to the card using quickoffice or any other app for that matter. It will only let me save to the built in storage
Click to expand...
Click to collapse
Interesting. I was just able to copy/paste from root to a folder on the exStorages and copy a file from the internal to the exStorages (an apk and an ePub)
Just re-read your post. From an app to exStorages. Hmmm...will try that.
Don't have quickoffice but polaris has very few options. Almost too few.

otamctech said:
I'd like to see a r/w external sd card.
Click to expand...
Click to collapse
I'd like to see that as well, but it'd probably be a kernel change, not what people here call a ROM change. Let's see, here's how it's currently mounted:
Code:
/dev/block/vold/179:17 /mnt/sdcard/extStorages/SdCard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
It's already mounted as read-write. The thing that's preventing normal user write access is the uid/gid combo with the fmask/dmask (not sure why samsung didn't just use a umask instead of both of the other masks.) Essentially, what that is doing is say that all the files and directories (including the root of the mount) are readable by anyone, but only writable to the "system" user, or a user in the "media_rw" group. I'm going to take a wild guess that the "camera" application, the "my files" application, and other samsung apps are in that "media_rw" group. (not sure how to check that...)
Interesting... I'm trying to remount it manually (mount -o remount,...) and while it's not giving any error, it's not working either.
I'm not sure how these "vold" mounts work, what options are valid for them, etc. It's an interesting issue, though...

All I want is a deodexed rom. Might have to break out android for dummies and learn how to.
Once we get that then let the theming begin.
Sent from my Insanity powered SGS2

Not to difficult i may give it a try soon.

deodex'ing honeycomb stuff isn't as easy as gingerbread and prior...

garyd9 said:
deodex'ing honeycomb stuff isn't as easy as gingerbread and prior...
Click to expand...
Click to collapse
I know, thats why I havent learned it yet lol.
However I am slowly figuring out theming while the rom is odexed. Got a few things going now

This device is powerful and awesome. Id love to be able to change themes and icons. The bloat ware doesn't get into the way and slow performance down. This devise will do me good for about 1 year to 1 1/2 years than ill upgrade to a new more powerful device.

this may help..
http://forum.xda-developers.com/showthread.php?t=1373131
I will likely wait for a clockwork recovery to start ripping stuff apart.
this is my first sammy product, wife has a cappy that I flash. nota huge fan of touchwiz but its easy on the eyes compared to my past 2 devices, dell streak 7 & 5.

Moving this to a proper forum.

chrisrotolo said:
I will likely wait for a clockwork recovery to start ripping stuff apart.
Click to expand...
Click to collapse
Which model do you have? GT-P6210 (wifi only), GT-P6200 (international 3G) or SGH-T869 (USA/TMobile 3G)?
There's no CWMR for the p6200 (yet), but I've already done them for the other two.

P6200 3G from malaysia. no rush, patiently waiting. Im more than willing to help with any info needed. Thank so much.

chrisrotolo said:
P6200 3G from malaysia. no rush, patiently waiting. Im more than willing to help with any info needed. Thank so much.
Click to expand...
Click to collapse
Are you fluent with a shell prompt? If so, in order to attempt a CWM recovery (based on what I've already done for the p6210 and t869), please run the following two commands as root via adb shell... (and copy the resulting information)
mount
cat /proc/partitions
.. that will give me a hint as to which partition is probably your recovery partition. Send me that info IN A PM. I'll respond via PM with some more commands (based on the info you send me, I'll need you to dump a partition or two and get the images to me.)
Once I have the proper information and images, I can PROBABLY make a successful CWM recovery image (but please understand that I'll have to recompile a kernel BLIND with no possible way to test myself.)
Take care
Gary
---------- Post added at 11:43 PM ---------- Previous post was at 11:40 PM ----------
I should also mention that I'm going to be VERY busy over the next 3 days, so even if I get the images and all works okay, the earliest I'd be able to have a recovery would be Thursday or so.

[INFO]What is EpicMTD, and what you need to know.

Getting started
Before I get into the thick of this, I've been for a little over a week or maybe even more taking as much time as I can to explain to people what MTD is and the risks of it. And unfortunately most people just by natural human tendencies have an issue comprehending it which believe me is perfectly fine haha, it's a lot to take at once. So I'm going to layout the basic need to knows, and if any more information is needed feel free to pm me and I'll add it into this main post.
I'm going to try to make this as simplistic as I can.:x
What is a partition?
A partition is an area of allocated space, a division of the whole overall area of space. In this case our partitions on the Epic 4G are /System, /Data, as well as /Cache. All with set permanent sizes.
What is a partition map?
A partition map is the configuration of our partitions, it's what in a vagueness sets our required sizes for the divisions of our nand also known as flash memory. A partition or partition map should not be confused with a file system. An example would be BML and MTD.
What is a file system?
A file system resides on the partition map and governs the data being read/wrote/moved/etc by the Operating System, in this case Android. Changing a file system is less complex than an overall change in partition mapping. They again, are not the same thing.
What is MTD?
MTD is an Open Source Partition map. It allows those who are using it control over how their partitions are sized and how much space is allocated here and how much space is taken away from there. Currently on MTD we have 689 megabytes of space allocated to our /data partition allowing more to be downloaded from the market as an example. MTD as a partition config has YAFFS2 as a file system residing on it governing how data is transferred and the speed of which it is done. EXT2 through 4 aren't possible on the MTD platform, just as YAFFS2 may not be possible on the BML proprietary platform.
What is BML?
BML like MTD is a partition map, however it is proprietary in nature, Close Source if you will. The size for /System /Data /Cache is set and permanent and makes opening up space more of a task for Developers. Stock the Epic 4G comes on BML, and is running RFS as it's file system, once rooted you can leave RFS for EXT4 (Journaled or Un-Journaled) as long as the kernel you use allows for EXT4. But in the end, changing a file system on BML does not lessen or enhance the control you have over your partitions.
What do I need to know before flashing a rom with this?
Currently there are two distributions which have moved over to the MTD platform.
One of which and the first inital one being:
[ROM] Epicmtd CM7 SELFKANG (12/10) - 2.3.7
And the second which is a basis of the first:
[ACS] [MTD] [YAFFS2] MIUI 1.12.2 Beta 6 MTD (Updated 12/10/2011)
Within the flashable zips for these two roms there are scripts which completely format your device and move you to MTD. It is required to back up the things you wish to keep with Titanium backup if you have it. Nandroids from RFS/EXT4/BML do not work on MTD/YAFFS2. Alternatively if you have purchased appextractor or titanium back up pro licensing from the Android market you can make a nandroid before your move and then extract the data apps or system apps you want from that backup while on MTD/YAFFS2 without going into recovery.
When flashing one of these ROMS in CWM5 your phone shall reboot during the installation if it finds you're on BML, don't panic it is a natural process of this move.
When booting into recovery on MTD it reacts to how long you hold the 3 button combination. Being Volume down, Camera, and Power. Don't panic if it doesn't pop up, you must let go to let it know which path it goes to. If your phone looks like it's booting again don't do the combination. It's switching from the init to the recovery.
CWM 5 is not broken, on MTD our kernel now has a 2 stage init. And it's part of the process.
How do I go about flashing other roms if they're not MTD?
Flashing a Stock TouchWiz rom can be very problematic, mainly due to the nature of and differences between MTD and BML. Currently there isn't a stock MTD kernel. To return to BML, you have a choice of either using Heimdall or Odin. To do so you require the victory.pit as well as a stock tar of your choice which includes our bootloader so that when you repartition your device all goes well without problem. There is no method to return without using Odin/Heimdall because BML is a proprietary configuration. We lack the tools to replicate Samsung's methods and mannerisms.
What does it mean for me as an end user?
As an End User, MTD is an opening to a new life for the Epic 4G. Things like ICS, more space in data or system, are more within our reach and grasp due to the nature of Open Source MTD is immersed in. We're closer to the Captivate, Fascinate, Vibrant, and Galaxy S international by being on MTD, we've that new freedom they've had for a long time. Not to say things like ICS aren't possible on BML but with this we're at a better standing point.
Stock EI22 on MTD
noobnl as well as Tortel have worked together to put a stock EI22 rom for the MTD platform which can be found here.
[EI22] Stock-ish MTD Build
This is for a stock experience and for those want to use MTD as well as make use of the stock features our phone has, nothing out of the ordinary or custom, just as a basic point. Rom Developers can go on towards moving their roms over to this platform now with the use of the boot.img but for now kernel developers will still have an issue nonetheless.
Those responsible for this in no specific order: Decad3nce, noobnl, jt1134, mkasick, nullghost, nubecoder, DRockstar, UberPinguin, Rodderik, wtogami, as well as countless others.
All things within this thread are subject to change if a need for correction is to be met.

First. Good post. Sticky request.
Sent from my SPH-D700 using XDA App

Too bad this wasn't up before I flashed the MIUI update.... It looks like MTD=FML for me. I now have no choice on if i want 4g or not because the only 2 ROMs with MTD are CM7 and MIUI which dont support 4g. Grrrr. I hope someone can make something to get back to EXT4 or RFS W/O odin or heimdall. Last time I used odin to go to a stock ROM it ended up hard bricking my phone and i had to pay $600 for a new one.
I hope other users read this post before making the ssame mistake I did. Thank you AproSamurai.

No. Those are proprietary. You need to use Odin because it has the Samsung code that we don't have.
Edit: make sure you use a pit and make sure you check repartition and auto reboot. Nothing else.
Sent from my SPH-D700 using XDA App

roddygonzo17 said:
Too bad this wasn't up before I flashed the MIUI update.... It looks like MTD=FML for me. I now have no choice on if i want 4g or not because the only 2 ROMs with MTD are CM7 and MIUI which dont support 4g. Grrrr. I hope someone can make something to get back to EXT4 or RFS W/O odin or heimdall. Last time I used odin to go to a stock ROM it ended up hard bricking my phone and i had to pay $600 for a new one.
I hope other users read this post before making the ssame mistake I did. Thank you AproSamurai.
Click to expand...
Click to collapse
I apologize I couldn't have gotten it out sooner. Been a bit busy as of late, my apologies. Things are being worked on now regarding overlay and 911 by the CM team. And then CM will be official and we'll begin to see work on ICS and beyond, if that's of any consolation.:x

roddygonzo17 said:
Too bad this wasn't up before I flashed the MIUI update.... It looks like MTD=FML for me. I now have no choice on if i want 4g or not because the only 2 ROMs with MTD are CM7 and MIUI which dont support 4g. Grrrr. I hope someone can make something to get back to EXT4 or RFS W/O odin or heimdall. Last time I used odin to go to a stock ROM it ended up hard bricking my phone and i had to pay $600 for a new one.
I hope other users read this post before making the ssame mistake I did. Thank you AproSamurai.
Click to expand...
Click to collapse
You're gonna have to Odin, sorry. There's absolutely no way and there most likely will never be a way without it.
By the way, $600? I've bricked my phone a few times, and when I went to sprint I got a replacement for $35. Not sure what you did there.
Sent from my Samsung Epic using CM7!

Great post. This was very needed
Sent from my SPH-D700 using xda premium

Thanks for a quick reply marcusant. If its not too much of a hassle would you mind making a video and possibly post links for the .tar and .pit to use unless the .pit is the same as for froyo. I just really need my phone and dont want to have to buy another one.
---------- Post added at 07:31 PM ---------- Previous post was at 07:22 PM ----------
|| Acer || said:
You're gonna have to Odin, sorry. There's absolutely no way and there most likely will never be a way without it.
By the way, $600? I've bricked my phone a few times, and when I went to sprint I got a replacement for $35. Not sure what you did there.
Sent from my Samsung Epic using CM7!
Click to expand...
Click to collapse
The representative from sprint told me that the only way i would have been able to brick it like that (would not turn on, no recovery mode, and no download mode and when plugged the charger in it wouldnt charge or be recognized by the computer) is if i rooted it which voided my warranty and wouldnt be covered by insurance.

roddygonzo17 said:
The representative from sprint told me that the only way i would have been able to brick it like that (would not turn on, no recovery mode, and no download mode and when plugged the charger in it wouldnt charge or be recognized by the computer) is if i rooted it which voided my warranty and wouldnt be covered by insurance.
Click to expand...
Click to collapse
I would have fought that by playing stupid and asking what he was talking about. Sprint also came out last year stating rooting does not void warranty but did require being noted on your account IIRC. I can give at least 1 scenario where that could have happened without rooting ... go drop your phone in the bathtub.
Memory modules and other ICs can easily go bad as well so sprint employee was playing a jumping to conclusion game and a manager would have been called over quickly.

onilink67 said:
I would have fought that by playing stupid and asking what he was talking about. Sprint also came out last year stating rooting does not void warranty but did require being noted on your account IIRC. I can give at least 1 scenario where that could have happened without rooting ... go drop your phone in the bathtub.
Memory modules and other ICs can easily go bad as well so sprint employee was playing a jumping to conclusion game and a manager would have been called over quickly.
Click to expand...
Click to collapse
You know I wasn't really thinking of that at that point, i was just worried about getting my phone back but that would have been a great idea. That way the little stickers that turn red when they get wet would have changed colors since water damage is covered.

"Wouldn't naturally do this but needs to keep this relevant until it can be stickied."
BUMP

I need to make a tutorial to restore... I'm really busy right now but will try to put up a simple guide without pictures. When I have time I will do pictures or a video. *qbking77 may beat me.
Sent from my SPH-D700 using XDA App

Its old but still relevant.

roddygonzo17 said:
Thanks for a quick reply marcusant. If its not too much of a hassle would you mind making a video and possibly post links for the .tar and .pit to use unless the .pit is the same as for froyo. I just really need my phone and dont want to have to buy another one.
Click to expand...
Click to collapse
http://db.tt/Pf4qPUIV
This is the tar and pit file.

very usefull info, im allready on one before this was posted, but i knew most of what i needed, you should ask qbking to put his video in the op. it has alot of good info in it for those people who dont read anything.....

If I,
1.) make a nand backup in CWM5 of MTD CM7, would I be able to Odin back to stock, then restore the nand backup?
Or,
2.) would I have to reflash the ROM then advanced restore data?
Im leaning toward option 2 since CWM5 wont preserve the partition map, only the filesystem. I just want to be sure.
Thank you Apro
vvvvvvvvvvvvvvvvvv

theduce102 said:
If I,
1.) make a nand backup in CWM5 of MTD CM7, would I be able to Odin back to stock, then restore the nand backup?
Or,
2.) would I have to reflash the ROM then advanced restore data?
Im leaning toward option 2 since CWM5 wont preserve the partition map, only the filesystem. I just want to be sure.
Click to expand...
Click to collapse
2 would be the correct answer to your question.

I installed the miui and didn't realize that I would have oden back to stock but I just followed qbking's video and I after that I was able to restore my nandroid backup. I got freaked out because i couldnt restore my backup at 1st but in the end it was my fault for not reading before l did it.
Sent from my SPH-D700 using XDA App

Thanks for the info Apro. Knowing is half the battle.
Born from an Epic Rebirth.

|| Acer || said:
You're gonna have to Odin, sorry. There's absolutely no way and there most likely will never be a way without it.
By the way, $600? I've bricked my phone a few times, and when I went to sprint I got a replacement for $35. Not sure what you did there.
Sent from my Samsung Epic using CM7!
Click to expand...
Click to collapse
only $35? I haven't had to send my Epic in for replacement yet but every phone i've sent to Asurion in the past is always $100 per incident... are you on a different insurance plan or something?