Database Info

[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?

[TOOL] G2X Cleanup Batch *** WARNING *** WILL FORMAT INTERNAL SD

If you are going to flash and ICS ROM after this tool please make sure to first install a GB then ICS otherwise your SD card will not be accessible. I am trying to find a fix but it has been illusive. This statement will be removed once a fix has been found and OP updated.
Now with CWM Touch!
This method uses NVFLASH to recreate all partitions and formats them, thereby getting rid of the file allocation pointers and hence renders data inaccessible without effort.
Note: I have never seen a file come back to life or its data affect other files without effort on the users part or a temporary glitch once the partitions and pointers have been overwritten. Please post a reply with evidence if you have seen it.
Benefits:
The contents of the zip file can be used to super clean G2X before a new ROM flash. This tool recreates all the partitions in the phone so wipes the pointers to all files (everything). The method it employes has existed from before. The files here will stop short of pushing a ROM, so that you can push your favorite ROM.
Prerequisites:
G2X (Will not work on O2X due to different partition table)
Desire to have a clean install of your favorite ROM
Backup your data
*** WARNING ***​
This tool will wipe both phone internal memory and internal SD card. External SD card content is safe.
Don't say you haven't been warned!
What to do:
Download the attached Zip file.
Take out the battery (assuming you have backed up your data on external SD card, computer or elsewhere), connect the device via USB while holding VOL+ and VOL- together. Don't let go of the volume buttons until the device is recognized.
(I typically leave Device Manager open to see when it shows up in the list under "USB Controllers").
Launch flash.bat, sit back and wait until the process finishes (generally a good idea to open a command prompt, CD to the directory and then run the file).
Unplug, put battery in, reboot into CWM recovery (pushed by this tool) by holding VOL- first, then pressing and holding POWER).
Flash your favorite ROM.
Enjoy!
I made this package because I could not get the bluetooth to work with G2x GB 2.3.3 (and below). The issue was a disconnect problem where both the phone and headset would still think they were connected but in audio would not be routed for a call or media. After this procedure my phone has not had an issue for almost 3 weeks now. I have tried it with two ROMs and 3 different headsets without any issues.
I guess I will not toss this phone after all .
Putting it out there in the hope that it may help others solve some of their issues as well. I suspect bad data stays in places not touched by other methods.
Your comments are most welcome.
[Update]
Klathmon has made an newer version with CWM 5.0.2.8. RP by Klathmon can be found here:
http://forum.xda-developers.com/showpost.php?p=24768294&postcount=66
I have tested the windows version but linux one is untested. Use at your own risk.
[Update]
Now with CWM Touch!
Thanks to everyone who has contributed on this thread with a drive to positive change! You work/comments/suggestions are very much appreciated.
References:
http://forum.xda-developers.com/showthread.php?t=1248644. This link was the inspiration for the current work.
Link to CWM Touch development thread. I took the image posted there: http://rootzwiki.com/topic/22984-recovery-touch-enabled-cwm-5813/
[EDIT] The zip file should be fixed now. Darn work machine does something to the upload.

was just about to flash the new hellfire rom and saw this tool! will try it out and see how things go
edit: yeah corrupt zip on my end too.

The zip file seems to be corrupt. Could you re-upload plz

worked great on my end, no problems.

khanggle said:
worked great on my end, no problems.
Click to expand...
Click to collapse
The real test is how stable your ROM would stay with this method to wipe than any of the other methods.
I guess only time will tell .

wow this method really blaze hellfire much thanks to your( you) & (rom dev)

Ohh I like this. Thank you for sharing .
This thing is faster than nullifier, and I especially like how you don't need to be in CWM to use it. It just seems like doing it in "update mode" would allow better manipulation of the phone's internals.

so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)

dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
He states in OP that it doesn't write anything, therefor doesn't "nullify". It formats and partitions.

dodgefan67 said:
so this tool DOES format and nullify in addition to recreating the partitions?
deleting and recreating partitions does not remove data. only by writing over existing data can you get rid of it (like nullifier does)
Click to expand...
Click to collapse
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA

mansa_noob said:
Actually you are right. Deleting, recreating and formatting partitions does not get did of the 1s and 0s, so in that sense the data is still there. However the pointers are gone, and hence even though the data is still there it can't be accessed without effort.
What do you think the nand has on it when the device is shipped... I can assure you its not ask zeroes!
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.

MWBehr said:
Well no, it has a next to worthless version of android Also, the point he was trying to get across is that it would be better for you to present the script for what it is and not try to compare it to other scripts that do something entirely different. You do kind of imply that you accomplish the same thing as the Nullifier script and more, when in fact you simply do something different.
Some may and probably will prefer your script, at least for specific purposes, while others will prefer the Nullifier script.
Click to expand...
Click to collapse
Done. OP updated to reflect. Thanks for clarifying that. It was not my intention to state that this tool does anything any other does, or does not.
I think we are all trying to do the same thing... get rid of the issues when swapping ROMs like _____. I can't seem to think of a good analogy here .

thanks for clarifying the OP, that makes much more sense
and no i wasnt trying to say you were reinenting the wheel, just trying to understand what your tool is actually doing
and also i do understand that it would take effort to get data off any type of storage device once the partition has been erased. i deal with wiping hard drives in a data center all the time. we use a DOD wipe tool that writes 1s and 0s over a drive a minimum of three full times to eradicate the data
but with this tool doing it outside of CWM, it sounds like it may do a better job of it
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?

dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).

dodgefan67 said:
but i must ask, why do you need to push CWM? what if i have a newer version of it already on my phone?
Click to expand...
Click to collapse
I was thinking the same thing but seems easy enough .. add the cwm img to the dir and edit the .cfg file. Hopefully that should get the new CWM flashed

So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA

mansa_noob said:
There is no need to push CWM 5.02. As I said in the OP it is a mod of the script found in the reference. In that script it was pushing default recovery. Since the recovery partition is being overwritten as well you will loose existing one and you need a recovery to be able to push a new ROM. Hence the need to push recovery (instead of using super one click).
As long as the recovery is not bigger than the partition that holds it we should be able to push a newer version. However I can't leave it empty or people will look for me with a shotgun (myself included ).
Click to expand...
Click to collapse
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
PL0X_Kleiner said:
So would it be benefitial or pointless to nullify to clear the data then run this script for a... super clean?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
i think it would be pointless unless you are super paranoid

dodgefan67 said:
ahhhhhh now i understand. my eyes have been opened LOL
---------- Post added at 07:36 PM ---------- Previous post was at 07:35 PM ----------
i think it would be pointless unless you are super paranoid
Click to expand...
Click to collapse
Nobody is twisting any arms here... Use it if you want to, don't if you don't want to.
I saw benefit so posted so that others may benefit as well.
Sent from my LG-P999 using XDA

Ok so question, why are you killing all the data on your internal SD card? Why not just the individual partitions that the phone uses? Your destroying data that don't need to be destroyed before flashing a rom...
Sent from my LG-P999 using xda premium

It does not have to be destroyed. I just haven't had a chance to test without recreating emmc yet.
Next step. Likely tomorrow. Would like to test before release.
Sent from my LG-P999 using XDA
[edit] BTW, I do want to restate that there is some data that needs to be destroyed which is not being taken care of by other methods. I don't believe it is in the emmc, but rather it resides in one of the other partitions. Most methods out there are only working in the /data, /system and /cache domain.
My original problem (bluetooth disconnect) which happens to be a problem for some in the community even now was only completely fixed by this method.

efs backup & restore

do we need to do the efs backup & restore if we r coming from another cm7 rom like mtd miui?
thanks
Sent from my SGH-T959V using XDA

ChadBFlores said:
do we need to do the efs backup & restore if we r coming from another cm7 rom like mtd miui?
thanks
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
I dont think its necessary. But it would be safe to go ahead and use it. Ya know CYOA type of thing.

efs-backup won't work right since it's intended to be used from a BML kernel and it tries to mount /efs using the bml mount point. When CM7 release 11 comes out, you won't have to worry about this since the update.sh script will take care of the efs stuff for you. Erik is already using that script in one of his MTD roms, as long as all the roms get up to date with it, the efs-backup/restore zip files will become obsolete.

FBis251 said:
efs-backup won't work right since it's intended to be used from a BML kernel and it tries to mount /efs using the bml mount point. When CM7 release 11 comes out, you won't have to worry about this since the update.sh script will take care of the efs stuff for you. Erik is already using that script in one of his MTD roms, as long as all the roms get up to date with it, the efs-backup/restore zip files will become obsolete.
Click to expand...
Click to collapse
FB I used/followed the directions for the revenge rom to flash mokee and those directions still have us using the efs backup and restore. Is this updater.sh part of a new build?

Yup, I just haven't posted the new instructions in the wiki until Max gets R11 out, but as I said, Erik included that script in his build so you no longer need the efs zips with that specific rom.

[Q][REQ]BML Conversion w/o Odin

I know in the new JB roms there is a mtd converter file and i was wondering if a bml convert file could be made
Sent from my Nice 'n' Stock-y Infuse 4G

isaiahe97 said:
I know in the new JB roms there is a mtd converter file and i was wondering if a bml convert file could be made
Sent from my Nice 'n' Stock-y Infuse 4G
Click to expand...
Click to collapse
I think its possible...if I knew more about conversions I would definatly look into it...I did however look at the updater.sh and it did give me an idea...
After looking at it this is what seems to be the process...(summarized)
Flashes boot.img then reboots, after reboot it then creates the mount points
Now what I'm thinking is this...if we edit the mtd parts to represent our old file system format...maybe that would work? Like switch put the mtd mounts with bml mounts...idk though...
That's just me brainstorming when its past midnight
But I'm positive its possible...just don't know the process
Sent from my SGH-I997 using Tapatalk 2

mg2195 said:
I think its possible...if I knew more about conversions I would definatly look into it...I did however look at the updater.sh and it did give me an idea...
After looking at it this is what seems to be the process...(summarized)
Flashes boot.img then reboots, after reboot it then creates the mount points
Now what I'm thinking is this...if we edit the mtd parts to represent our old file system format...maybe that would work? Like switch put the mtd mounts with bml mounts...idk though...
That's just me brainstorming when its past midnight
But I'm positive its possible...just don't know the process
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Process is as follows, correct me if I'm wrong JT:
Begin flash from CWM, which starts updater script and runs bml_to_mtd, setting mount points and such. Then formatting of all partitions except for maybe boot.
Once done, updater script has a "oneshot" flag so that flashing to MTD only need happen once. after mounts set and partitions formatted, reboot.
second run checks format and, if MTD, begins flash.
Without looking at the updater script file (or anything else in the conversion process for that matter), the above would be my best guestimate, as it's been a REALLY long time since I've had to script anything like this to be done. I've done custom Linux installs and scripted the formatting of partitions, but that was on hard drives that already had all their mount points set.

I think we need something like this...http://forum.xda-developers.com/showthread.php?t=1375272
Hope that guy can figure it out...if he can then all we would have to do is edit to match our device and our format (I think...correct me if I'm wrong)
Sent from my HTC PH39100 using Tapatalk 2

mg2195 said:
I think we need something like this...http://forum.xda-developers.com/showthread.php?t=1375272
Hope that guy can figure it out...if he can then all we would have to do is edit to match our device and our format (I think...correct me if I'm wrong)
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Well, at least its easier now than it used to be. I remember having to set static memory locations (IE 0F0D3000-0F0D38AA), but this seems a whole lot easier since all you have to do is set partition sizes and mount points...
Sent from my SGH-I997 using xda app-developers app

[Q] Resizing /efs partition, possible?

Hi, I have a t959v and I have been trying to restore my IMEI (that's because I was able to backup my /efs partition).
However, after I flash CM 10.1 for my device, my IMEI is gone, or has turned to 0000000.... or has turned to ASCII characters that I couldn't even read. I tried restoring my nv_data.bin file, done everything I could(googled and tried so many posts, I've lost count already.) and ended up with still, a corrupted/missing IMEI. Well after tinkering with my device, I've found out that the reason why my nv_data.bin (5.2 Mb) corrupts as I transfer it to the /efs partition--it's because my /efs partition is a little bit small, that's why my nv_data.bin ends up in an incompleted transfer state(corrupted file). From 5.2Mb, it falls to around 3-4Mb. No, it's not compressed or anything, it's cut-off, or "cropped" if it's the right term(which I doubt). Now, the my question is, is it possible to resize or grow my /efs partition? If yes, then how? First of all, thanks for spending some time in reading my post. Now, could anybody help me? or if it's such a pain to do, is there an alternative to CM 10.1 that has minimal glitches or bugs? 'Coz it's a pity if I couldn't upgrade from GB. The hardware of this phone is good enough, but the firmware is kinda frustrating(slow, freezes, and worst of all, GB), don't get me wrong, I don't hate GB but for the hardware of this phone, it's too good to just stay in GB. Thanks again!

Reflash back to gingerbread. That should restore your ieme number. Than try again.
Sent from my BNTV250A using XDA Free mobile app

cryzone77 said:
Hi, I have a t959v and I have been trying to restore my IMEI (that's because I was able to backup my /efs partition).
However, after I flash CM 10.1 for my device, my IMEI is gone, or has turned to 0000000.... or has turned to ASCII characters that I couldn't even read. I tried restoring my nv_data.bin file, done everything I could(googled and tried so many posts, I've lost count already.) and ended up with still, a corrupted/missing IMEI. Well after tinkering with my device, I've found out that the reason why my nv_data.bin (5.2 Mb) corrupts as I transfer it to the /efs partition--it's because my /efs partition is a little bit small, that's why my nv_data.bin ends up in an incompleted transfer state(corrupted file). From 5.2Mb, it falls to around 3-4Mb. No, it's not compressed or anything, it's cut-off, or "cropped" if it's the right term(which I doubt). Now, the my question is, is it possible to resize or grow my /efs partition? If yes, then how? First of all, thanks for spending some time in reading my post. Now, could anybody help me? or if it's such a pain to do, is there an alternative to CM 10.1 that has minimal glitches or bugs? 'Coz it's a pity if I couldn't upgrade from GB. The hardware of this phone is good enough, but the firmware is kinda frustrating(slow, freezes, and worst of all, GB), don't get me wrong, I don't hate GB but for the hardware of this phone, it's too good to just stay in GB. Thanks again!
Click to expand...
Click to collapse
Interesting...
champ1919 said:
Reflash back to gingerbread. That should restore your ieme number. Than try again.
Click to expand...
Click to collapse
Sure, but that doesn't answer the original question. Going back to BML (which was on Gingerbread, of course) will restore the original /efs partition. This is because all of the MTD installs do not overwrite the original BML /efs partition.
Now, the concerning issue is that the nv_data.bin shouldn't be getting any bigger then the original (I don't have my sgs4g on hand to verify), but what may have happened is yaffs2 partition options in the kernel may not be the same or formatting may have added more partition data to the filesystem layout that makes the available free space on the partition less. (does this paragraph not make sense? If so, ask and I'll go into more detail)
So, let me ask you to do a test.
WARNING!!! Make sure you backup the EFS partition while on GB before emptying the directory!
Backup EFS (do this from recovery with adb shell):
Code:
su -
mount /efs
mount /sdcard
cd /
tar cf /sdcard/efs-backup.tar /efs
Go back to stock GB. There are Cne-Clicks I made to do this. Root the install and post the output of:
Code:
su -
rm -rf /efs/* /efs/.*
df /efs
Restore EFS (again, from recovery, adb shell):
Code:
su -
mount /efs
mount /sdcard
cd /
tar xf /sdcard/efs-backup.tar
Next, do the same for cm-9.1.0.
After that, do the same with which ever cm-10 or 4.4.x kernel you're using.
Post all of the values here and lets debug that way. I'll bet you that the available free space and total size are DIFFERENT when the partition is empty.
You don't need to restore the EFS on MTD installs, but MAKE VERY SURE you restore the EFS on the BML (Gingerbread) install!!!
Maybe also try different CM10.x and 4.4.x kernels and see if there is a difference. For each test, note which kernel, which rom. Also for each test, flash back to Gingerbread (bml, from the oneclick) before flashing a new rom!

All the nv_data.bin files I have are 262.1kB.
The tar backups the installtion script creates for you should be 700kB or less.
It sounds like something went seriously wrong with the nv_data.bin file you are trying to restore, so I recommend you follow the advice @champ1919 gave you and go back to gingerbread an flash your ROM again.
After you flash make sure that the nv_data.bin file under /efs/root/afs/settings/nv_data.bin is exactly 262.1kB. If that's the case then save the efs backup the install script made for you in a safe place.

Mine from froyo are 256.0 KB for locked and 260 for unlocked., weird..

champ1919 said:
Mine from froyo are 256.0 KB for locked and 260 for unlocked., weird..
Click to expand...
Click to collapse
Interesting. I think all the ones I got were from phones built at around the same time since they have similar text in the nv_data files.
The locked/unlocked files should be the exact same file size every time. All the tends to change is a single 1 in the file becomes a 0 to unlock it.

I had stored them in Dropbox. I betcha one is from the vibrant I lost, but, I thought I deleted it so I would not goof. As soon as I can get to a PC, I'll dig into it somemore. I wonder who wrote that guide years a go on how to hexedit that file. I should give them another thanks.

bhundven said:
Interesting...
Sure, but that doesn't answer the original question. Going back to BML (which was on Gingerbread, of course) will restore the original /efs partition. This is because all of the MTD installs do not overwrite the original BML /efs partition.
Now, the concerning issue is that the nv_data.bin shouldn't be getting any bigger then the original (I don't have my sgs4g on hand to verify), but what may have happened is yaffs2 partition options in the kernel may not be the same or formatting may have added more partition data to the filesystem layout that makes the available free space on the partition less. (does this paragraph not make sense? If so, ask and I'll go into more detail)
So, let me ask you to do a test.
WARNING!!! Make sure you backup the EFS partition while on GB before emptying the directory!
Backup EFS (do this from recovery with adb shell):
Code:
su -
mount /efs
mount /sdcard
cd /
tar cf /sdcard/efs-backup.tar /efs
Go back to stock GB. There are Cne-Clicks I made to do this. Root the install and post the output of:
Code:
su -
rm -rf /efs/* /efs/.*
df /efs
Restore EFS (again, from recovery, adb shell):
Code:
su -
mount /efs
mount /sdcard
cd /
tar xf /sdcard/efs-backup.tar
Next, do the same for cm-9.1.0.
After that, do the same with which ever cm-10 or 4.4.x kernel you're using.
Post all of the values here and lets debug that way. I'll bet you that the available free space and total size are DIFFERENT when the partition is empty.
You don't need to restore the EFS on MTD installs, but MAKE VERY SURE you restore the EFS on the BML (Gingerbread) install!!!
Maybe also try different CM10.x and 4.4.x kernels and see if there is a difference. For each test, note which kernel, which rom. Also for each test, flash back to Gingerbread (bml, from the oneclick) before flashing a new rom!
Click to expand...
Click to collapse
thanks for the fast response bhundven and the rest...
i apologize for not being able to reply as soon as you posted.
going back... i tried reflashing to stock and backed up my efs... however, when i looked at how big it was as a tar(ive tried making an rfs then put it into a tar. this is from the commands cat /dev/block/stl3 > /sdcard/efs.rfs or something like that. im sure that code came from a post here in xda too.) its size is 6.2mb.
and also... i have the log files of my cm10.1 upgrade attempt. posting it in case it would help...
also tried reflashing to stock ang flashing slimkat but the problem persists.
thanks for giving your time in helping me. i will try to reply as soon as i can. thanks again.
Q: is t959v the same as vibrant? been googling but posts are really confusing.. XD

cryzone77 said:
thanks for the fast response bhundven and the rest...
i apologize for not being able to reply as soon as you posted.
going back... i tried reflashing to stock and backed up my efs... however, when i looked at how big it was as a tar(ive tried making an rfs then put it into a tar. this is from the commands cat /dev/block/stl3 > /sdcard/efs.rfs or something like that. im sure that code came from a post here in xda too.) its size is 6.2mb.
Click to expand...
Click to collapse
Nope, that does not work. That is also not what my directions said to do.
cryzone77 said:
and also... i have the log files of my cm10.1 upgrade attempt. posting it in case it would help...
also tried reflashing to stock ang flashing slimkat but the problem persists.
thanks for giving your time in helping me. i will try to reply as soon as i can. thanks again.
Click to expand...
Click to collapse
You kinda buggered up the Quoting of the post, kinda hard to follow. So I removed what I wrote and only quoted what you said so it makes sense. But even after that, I can't really make sense of what you are doing and why you can't follow my directions?!?
cryzone77 said:
Q: is t959v the same as vibrant? been googling but posts are really confusing.. XD
Click to expand...
Click to collapse
It's not confusing at all. SGH-T959V (VibrantPlus) is not the same as SGH-T959 (Vibrant). They are not compatible, and flashing roms between the two will lead to bricks. Make sure that under the battery it says: SGH-T959V
The only thing these two devices have in common is their original provider: T-Mobile
Otherwise, go to the right forum for your phone before following any directions in this forum.

champ1919 said:
Reflash back to gingerbread. That should restore your ieme number. Than try again.
Sent from my BNTV250A using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the quick reply!
Well, the reason why I was trying to flash CM10.1 is to upgrade from GB so if I were to reflash to GB then I would've defeated my purpose.
But, I did try that, and backed up my EFS so as to restore it later on after I have flashed CM10.1 but to no avail.

cryzone77 said:
Thanks for the quick reply!
Well, the reason why I was trying to flash CM10.1 is to upgrade from GB so if I were to reflash to GB then I would've defeated my purpose.
But, I did try that, and backed up my EFS so as to restore it later on after I have flashed CM10.1 but to no avail.
Click to expand...
Click to collapse
Which phone model do you have?
Im running the new slimkat with no issue. Fb's cm11 was just as good. I bounce between those and back to GB when I need tv out with no issues.
Sent from my BNTV250A using XDA Free mobile app

bhundven said:
Nope, that does not work. That is also not what my directions said to do.
You kinda buggered up the Quoting of the post, kinda hard to follow. So I removed what I wrote and only quoted what you said so it makes sense. But even after that, I can't really make sense of what you are doing and why you can't follow my directions?!?
It's not confusing at all. SGH-T959V (VibrantPlus) is not the same as SGH-T959 (Vibrant). They are not compatible, and flashing roms between the two will lead to bricks. Make sure that under the battery it says: SGH-T959V
The only thing these two devices have in common is their original provider: T-Mobile
Otherwise, go to the right forum for your phone before following any directions in this forum.
Click to expand...
Click to collapse
Im sorry for the messed up reply sir, and thanks again for your reply,
Just to confirm, my device is INDEED T959V.
I did the cat > /sdcard/efs.rfs bla bla bla thing in the hope to make an ODIN flashable "fix" in the hope of getting my IMEI and baseband fixed.
And, just as you said, it didn't work. I also tried erasing the /efs by erase_image then mkdir -p /efs and then cd /efs then tar xf /sdcard/efs.tar but that also produced a "cropped" nv_data.bin. Im sorry I can't try your directions as of now because I'm currently using my phone for work, however, I will do as you said as soon as I can free up my device.
Q: Do I need to take my backup before I flash a custom kernel? or is it ok if back it up while using a custom kernel?
Q: So T959V is VibrantPlus, is it the same as Samsung Galaxy S 4G?
Q: So if T959V is VibrantPlus, should I look for ROMs with the naming convention of <rom name>-vibrantplusmtd?

champ1919 said:
Which phone model do you have?
Im running the new slimkat with no issue. Fb's cm11 was just as good. I bounce between those and back to GB when I need tv out with no issues.
Sent from my BNTV250A using XDA Free mobile app
Click to expand...
Click to collapse
I have a T959V.
I tried the SlimKat and SlimSabre but I still got no IMEI even after manual restore. I also tried the CM11 and still have the same problem.

So, when you go back to gingerbread, your number is still hosed?
Sent from my BNTV250A using XDA Free mobile app

cryzone77 said:
Im sorry for the messed up reply sir, and thanks again for your reply,
Just to confirm, my device is INDEED T959V.
I did the cat > /sdcard/efs.rfs bla bla bla thing in the hope to make an ODIN flashable "fix" in the hope of getting my IMEI and baseband fixed.
Click to expand...
Click to collapse
I have no clue where you got those directions.
cryzone77 said:
And, just as you said, it didn't work. I also tried erasing the /efs by erase_image then mkdir -p /efs and then cd /efs then tar xf /sdcard/efs.tar but that also produced a "cropped" nv_data.bin. Im sorry I can't try your directions as of now because I'm currently using my phone for work, however, I will do as you said as soon as I can free up my device.
Click to expand...
Click to collapse
Here it sounds like you are mixing up directions.
cryzone77 said:
Q: Do I need to take my backup before I flash a custom kernel? or is it ok if back it up while using a custom kernel?
Click to expand...
Click to collapse
Go back to stock gingerbread with my oneclick. Read all of the directions here first.
cryzone77 said:
Q: So T959V is VibrantPlus, is it the same as Samsung Galaxy S 4G?
Click to expand...
Click to collapse
Yes
cryzone77 said:
Q: So if T959V is VibrantPlus, should I look for ROMs with the naming convention of <rom name>-vibrantplusmtd?
Click to expand...
Click to collapse
No, we don't call it vibrantplus, because it cause so much confusion with vibrant. we call it galaxys4g for bml or galaxys4gmtd for mtd.
champ1919 said:
So, when you go back to gingerbread, your number is still hosed?
Click to expand...
Click to collapse
I'd like to know the answer to this as well. Good question!

bhundven said:
I have no clue where you got those directions.
Here it sounds like you are mixing up directions.
Go back to stock gingerbread with my oneclick. Read all of the directions here first.
Yes
No, we don't call it vibrantplus, because it cause so much confusion with vibrant. we call it galaxys4g for bml or galaxys4gmtd for mtd.
I'd like to know the answer to this as well. Good question!
Click to expand...
Click to collapse
Well I've tried many posts about restoring nv_data.bin but none of them seems to work. I even tried to edit nv_data.bin by hex. That's how desperate I am to upgrade. XD
By hosed, you mean corrupted or invalid? I use OneClick Heimdall by sir bhundven I believe..
and to answer the question, I get my IMEI and baseband back everytime I flash the OneClick. It's when I try to upgrade to CM++ that I get the null baseband and IMEI.
and to clarify, I got that backup process directions from this post http://forum.xda-developers.com/showthread.php?t=859914

cryzone77 said:
Well I've tried many posts about restoring nv_data.bin but none of them seems to work. I even tried to edit nv_data.bin by hex. That's how desperate I am to upgrade. XD
By hosed, you mean corrupted or invalid? I use OneClick Heimdall by sir bhundven I believe..
and to answer the question, I get my IMEI and baseband back everytime I flash the OneClick. It's when I try to upgrade to CM++ that I get the null baseband and IMEI.
Click to expand...
Click to collapse
Ok, so you go back to gingerbread and get your imei back.
cryzone77 said:
and to clarify, I got that backup process directions from this post http://forum.xda-developers.com/showthread.php?t=859914
Click to expand...
Click to collapse
NO This is not the right place to look for help. Although the 'Galaxy S 4G' is a 'Galaxy S' based-device, it is VERY different from the i9000!!!
Do not use instructions from other device forums!!!
We have documented a lot for this phone in this device forum and on our wiki
As I mentioned before (in this thread) instructions on backing up your efs, and restoring it. Use my instructions and let us know in this thread if you have any problems!

bhundven said:
Ok, so you go back to gingerbread and get your imei back.
NO This is not the right place to look for help. Although the 'Galaxy S 4G' is a 'Galaxy S' based-device, it is VERY different from the i9000!!!
Do not use instructions from other device forums!!!
We have documented a lot for this phone in this device forum and on our wiki
As I mentioned before (in this thread) instructions on backing up your efs, and restoring it. Use my instructions and let us know in this thread if you have any problems!
Click to expand...
Click to collapse
1st, YES I got my IMEI and baseband back, but its a shame if I can't upgrade to CM++(because I don't get my IMEI and baseband after flashing meaning I can't use my phone for work.) because it's a cool rom, it has everything I'm looking for in a custom rom.
AND yeah, I wasn't aware that they were THAT different. Anyways, thanks for pointing that out.
Q: Is there an upgrade path or something that I need to do aside from the standard flashing procedure for these roms?

Bhundven's modified kernel should give you root. You could skip that step of using the oneclickroot and use the heimdall one click (of his kernel) and get cwm & root in one step. It's linked in the link he gave you.
After you install cwm, is that when you loose the imei number? Are you letting the phone fully boot? How were you getting cwm in order to flash the cm?

champ1919 said:
Bhundven's modified kernel should give you root. You could skip that step of using the oneclickroot and use the heimdall one click (of his kernel) and get cwm & root in one step. It's linked in the link he gave you.
After you install cwm, is that when you loose the imei number? Are you letting the phone fully boot? How were you getting cwm in order to flash the cm?
Click to expand...
Click to collapse
Sorry,
What I meant by OneClick is using Heimdall in flashing the purely stock GB rom. After that, I root using Framaroot(successful) then I flash a custom kernel(bhundven's blastoff...IMEI and baseband still ok after this), then I flash CM++ ROM, this is where it gets ugly--I lose my IMEI(null) and baseband(also null). and YES I let the phone fully boot, I even wait around 15mins and try to turn the radio on and off to see if I got my IMEI and baseband back, I also tried taking out the battery and letting the phone loose all it's power and then turning it on, again, to no avail. And to answer the other question, I get CWM through the blastoff kernel.