[Q] Ext4 to RFS on the Tab - Galaxy Tab Q&A, Help & Troubleshooting

Hello Everyone,
First of all, let me thank everyone on this forum, because it's an endless source of information regarding our favorite gadgets. I'm pretty new to this so please forgive me if this is too basic.
I've searched the forum but couldn't find a clear answer to this. Here's my background:
I have an Euro Tab, and had a few updates via Kies, first to JJ7/JK5/JJ5 (CPW) and then to JMI/JMA/JM2 (CPW).
I rooted with z4root and then with SuperOneClick (on JMI, as z4 wouldn't work). I was a bit afraid of trying custom roms, but finally took the plunge because I was tired of waiting for official Samsung Gingerbread.
I started by patching the bootloaders on JMI, as instructed in the forum and flashed JQ1. I had a few problems, but I was able to solve everything and get GB running and then rooted with CF-Root
Of course, this is like an addiction and less than 24 hours after that, I flashed Overcome Hermes 2.0.1 with 3.1.0 Kernel, adjusted UV settings and installed a few Mods.
This is like having a new tab. it's responsive, battery is better and apart from a few minor bugs, it's really the greatest experience. Congrats to all the devs. This is what it should have been out of the box.
As I understand, OC Hermes 2.0.1 converted the file system to EXT4 while partitioning (please call me wrong if this is not true). On a friend's Galaxy S, he has the option to convert to EXT4 and revert to RFS on the CWM app which doesn't exist on OC Hermes (again, please correct me if I'm wrong).
Now the question(s). (finally) If I ever want to go back to stock (Froyo) either to try the official Samsung GB for my region when it comes out or if I have to send it to Samsung for some reason (knock on wood), can I just use Odin and flash a stock ROM (say JMI) with repartitioning with no problems or do I have to revert to RFS and then flash Froyo?
If so, how should I proceed to go back to RFS?
How can I confirm which file system it's using?
I've seen threads talking about going from Froyo to GB and back, but never with overcome, always with stock ROMs so, to avoid problems, I decided to ask this for a straight yes or no.
Thanks in advance for any help or comment. If this has been answered before, please link me to it. As I said, I couldn't find it through search.
Best, a.

I use chainfire's ext4conversion tool. It has the ability to switch to rfs. I am not on overcome rom so not sure it will work but its an apk available on xda forums, could give it a whirl.
As for the tool it works good.
Reverting to stock will get u back to rfs as well. (from memory stock gb files from overcome 2.0 rc1 were ok / going back to froyo had to use one of roto rom froyo versions ).

ezynow said:
I use chainfire's ext4conversion tool. It has the ability to switch to rfs. I am not on overcome rom so not sure it will work but its an apk available on xda forums, could give it a whirl.
As for the tool it works good.
Reverting to stock will get u back to rfs as well. (from memory stock gb files from overcome 2.0 rc1 were ok / going back to froyo had to use one of roto rom froyo versions ).
Click to expand...
Click to collapse
Thank you. It's amazing that just by searching what you referred in your post, I was able to find a lot more info on this.
For what I understand, Overcome is based on JPZ and there's no CF-Root for that. I think the tools apk can be used with CF-Root only, right?
Maybe I can flash JQ1 (or other ROM supported by CF-Root) and then convert to RFS if needed.
Now I need to know if I have to go back to RFS to flash a stock Froyo ROM.
Again, thanks ;-)

If you use odin + re-partition with the pit file then essesntially you are formating back to rfs. So any stock froyo rom will be ok. Cwm flash / update wont work. I suppose you have already have your original firmware or just download one.

ezynow said:
If you use odin + re-partition with the pit file then essesntially you are formating back to rfs. So any stock froyo rom will be ok. Cwm flash / update wont work. I suppose you have already have your original firmware or just download one.
Click to expand...
Click to collapse
That's what I thought, but wasn't sure. Being a noob has it's quircks
Thank you so much.
BTW, CF-Root is basically superuser+CWM+busybox. If I have these on Overcome, is it safe to assume the EXT4 tool extension for CF-Root will work on Overcome or should I expect other dependencies? I think CWM versions are different in OC and CF-Root.

You can basicly back to froyo rom
As about the ext4 to rfs , you can do that for overcome hermes , just go through cwm and then vodo and then disable it from there (lagfix) after you reboot your system will start convert from ext4 back to rfs and also u can do the same if u wanna back to ext4
Sent from hell to take your soul

k0sh said:
You can basicly back to froyo rom
As about the ext4 to rfs , you can do that for overcome hermes , just go through cwm and then vodo and then disable it from there (lagfix) after you reboot your system will start convert from ext4 back to rfs and also u can do the same if u wanna back to ext4
Sent from hell to take your soul
Click to expand...
Click to collapse
Thank you, k0sh.
It sure is simple when you know what to look for.
Cheers

k0sh said:
You can basicly back to froyo rom
As about the ext4 to rfs , you can do that for overcome hermes , just go through cwm and then vodo and then disable it from there (lagfix) after you reboot your system will start convert from ext4 back to rfs and also u can do the same if u wanna back to ext4
Sent from hell to take your soul
Click to expand...
Click to collapse
How much time that conversion usually takes? 5min., 10min?

Depending on how much data you have on your tab. If your internal memory is studded with apps it will take quite a long time (45 minutes was reported) as the system backs up your data then restores it after conversion. If the system has fewer data it will take less (5-10 minutes).

jykke78 said:
How much time that conversion usually takes? 5min., 10min?
Click to expand...
Click to collapse
for me last time , around 1hour and my tab didn't boot , so i just force reboot it during the convert and i was know that i have to reflash back , but i take the risk and boot it again and its start over the conversion and it takes 5 to 10 mins

Related

[Q] Update help 2.2.1/2.3

Hello.
I currently have a 2.2 galaxy s firmware witch i got using kies. I added the voodoo lagfix kernel to it.As i have read in the description, clockwork mod doesn't work with voodoo, so i'm stuck using odin for updating.
So, for the question: Is it safe to upgrade to 2.2.1 from Kies? And, moreover, how can I flash a costum rom like darky's or cyanogen? (i'm not sure about them).
P.S. How can I come back to stock 2.2 and delete the Voodoo kernel
Please help,
Thanks
create a folder within the Voodoo folder called "disable_lagfix" then restart the phone, it should convert back to RFS from EXT4 and return the rom to normal (ie. no lagfix applied)
once this is done, download whatever rom you want (JPY is the latest uk OFFICIAL relese i believe) or create your desired rom within Doc's Kitchen....
So, for the question: Is it safe to upgrade to 2.2.1 from Kies?
Yes otherwise it would not be offered by Samsung .
And, moreover, how can I flash a costum rom like darky's or cyanogen? (i'm not sure about them).
READ each post for instructions .
jje
itudorie said:
So, for the question: Is it safe to upgrade to 2.2.1 from Kies? And, moreover, how can I flash a costum rom like darky's or cyanogen? (i'm not sure about them).
Click to expand...
Click to collapse
You should be SURE before flashing custom ROM. Read and collect as much information from their thread. This will minimize the risk for you to repeat same problems others have had...
Cheers...

[Q] Question for regular custom rom flashers

I've tried searching the threads before I get shot!
Currently on Darky's and feel the urge to try a few other ROM's.
What is the correct way to change ROM's - flash stock ROM before flashing new custom ROM or flash new ROM from CWM, as I did with Darky.
Thanks in advance.
You can flash from rom to rom without going back to stock, Just remember to disable all ext4 conversions and all voodoo hacks, speedmod hacks, etc. Take it back to stock rfs and you should be good. unless other wise posted on the custom rom FAQ.
normally i flash darky8.0 wipe before upgrading to darky latest rom
If you get in trouble a flash back to Eclair via Odin with repartition checked and PIT file cures any problem ..
jje
I always flash back to stock Eclair before flashing another rom. It's not necessary, but it's safer.
no need to go back to stock. i never had problems going from kitchen to darky to CM7. just make sure - as said above - that all lagfix are disabled.
Cheers guys, very useful.
I don't have any lagfixes running and I'll look into disabling ext4 as I don't know how to do that.
Couple of different opinions though eek! lol
if u doesnt use lagfix, that means u dun need to disable ext4 already

[Q] ROOTing GINGERBREAD

Hi. I have original samsung's gingerbread and I don't know how I can root it. I read some topics abut it but I still haven't got a answer. ;( All possible rooting roms are custom, but I want root (what I say before) original Nordic software. Please answer. Thanks.
flash chainfire's kernel via odin in pda box and dont tick repartion
here is download link
http://forum.xda-developers.com/attachment.php?attachmentid=570247&d=1302966658
Thanks bro. But I have some questions. It's a kernel, yup? I think when I flash that I will can't change system files (OCLF) please answer and instruct me if I wrong Thanks.
grucha143 said:
Thanks bro. But I have some questions. It's a kernel, yup? I think when I flash that I will can't change system files (OCLF) please answer and instruct me if I wrong Thanks.
Click to expand...
Click to collapse
I dont understand what you wrote here. Anyway chainfire kernel is STOCK. He did some scripting and apps to it but the kernel remains stock. You can tweak stuff later but you dont need to.
Also you could try this http://goo.gl/VS4X4 its for root then you flash your stock kernel back.
Thanks you a lot
ok. I have to made lag fix, and I don't know after I flash that kernel I will can do lag fix. I think if it's stock kernel I can do that but I don't want broke phone
grucha143 said:
ok. I have to made lag fix, and I don't know after I flash that kernel I will can do lag fix. I think if it's stock kernel I can do that but I don't want broke phone
Click to expand...
Click to collapse
Ok. So now I understood you wanna change your fs to ext4 (known as lagfix in the good old days).
And you have JVB (NEE or XEE) . So just follow the advice of the second poster. And install the CF kernel. Also his ext4 app from that thread. Problem is you might not have enough space on your system partition as you got stock. But there is also HOW TO fix that problem .
Sorry, my english is low So I must ask You another time If I flash CF kernel, I receive fs ext 4 in this operation? or I must after install kernel use lag fix (http://forum.xda-developers.com/showthread.php?t=749495)??? Sorry and thanks
So you have OCLF installed now?
Get rid of it.
Install Chainfire's 3.1 kernal, and the ext 4 add-on. Then you will be good to go.
No I haven't got it yet.
This kernel have IN HIMSELF ext4?
http://forum.xda-developers.com/showthread.php?t=788108
In post #7, download the ext4 addon apk. Put it on your internal sd card. After you have the 3.1 kernal installed, install the ext4 apk. The 3.1 kernal is in post #6 for JVB.
Then from within the ext4 tools app, you can convert to ext4.
electrotune1200 said:
http://forum.xda-developers.com/showthread.php?t=788108
In post #7, download the ext4 addon apk. Put it on your internal sd card. After you have the 3.1 kernal installed, install the ext4 apk. The 3.1 kernal is in post #6 for JVB.
Then from within the ext4 tools app, you can convert to ext4.
Click to expand...
Click to collapse
OK. Thanks You everybody for answers. I will click "thanks" button of course for all. Last question: Where I can find Odin to download?
http://www.megaupload.com/?d=PWD334EZ
I can't remember if there's 3 versions of Odin in this zip. If so, use v1.7
electrotune1200 said:
http://www.megaupload.com/?d=PWD334EZ
I can't remember if there's 3 versions of Odin in this zip. If so, use v1.7
Click to expand...
Click to collapse
Thank You very much. There are only 1.7
EDIT: Udało się!!! (in polish it mean: Done!!!)
You're welcome
I dont want to start up another thread, and since my question is related to this thread, i thought id continue it.
Im also on the official 2.3.3 sammy g'bread.
All i want is to get rooted, so that i can delete some of the "in-the-box-apps" found on the phone from the beginning. Do i root the phone, as if its a 2.2?

[Q] Flashing from an old rom

Hey guys,
My girlfriend owns a Galaxy S and a few months ago I flashed it from the stock firmware to Hamsters rom, I think when it flashed it from the stock software it changed the file system from RFS to some variant of EXT.
I'm looking at flashing it to MIUI now, but I just wanted to ensure there was no risk with the partition being a different file type than it might expect, I was also hoping to get some pointers on Odin etc.
I know these are pretty basic questions that I really should find out myself, but I don't have much time and as it's not my own phone I'm not overly experienced/ in the know. Anyway I hope somebody can shed some light on the matter and any help is *greatly* appreciated.
Convert the file system first to stock by downloading voodoo control in the market, untick the first ,2 bullets, then reboot. After that you can now flash your phone provided you follow the flashing instructions by your rom provider.
Sent from my GT-I9000 using XDA App
Depending on what lagfix you have, use the voodoo toggle/ext4 app/recovery menu to convert all to rfs, then find the ezbase 2 rom in dev.
Read All!
With ezbase 2 comes
A) ezodin
B) drivers
C) pit file
3x froyo files
3x gingerbread files
Full graphic walk through
As you are going to miui, you need froyo base
Follow instructions, flash froyo ezbase, flash miui(no idea of their flash procedure)
Ezodin is very user friendly, and the graphic walkthrough.....well if you mess up, then you really only got yourself to blame atb
Insanity cm 014/glitch
Ah, fantastic.
You guys are awesome.

[Q] MTD/Non-MTD, Safety Advice?

Hi guys, need some advice. I have read allot of confusing/conflicting info on this and I just want some clarification as a precaution.
I have a P1000 and am currently on the latest nightly of CM9 but I read about MTD and possible brick if flash incorrect rom. What I want to know is, is it safe to re-stock using Overcome and also to come back directly to CM9 or do I need to follow some other procedure first?
I previously came straight from Overcome to CM9 without issue but not sure if same goes for going back?
Sorry if this has been covered but couldn't find any clear cut answers.
Thanks in advance.
Actually I don't think it will cause hard brick.
At most you need to restock using Odin.
But no, you can't convert an MTD partition (running yaffs2) back to Overcome ext4 fs.
You need to restock with Odin with pit file selected.
EDIT: the updater can convert FROM ext4 to YAFFS2, so you go from Overcome to CM9 direct but not the other way round.
priyana said:
Actually I don't think it will cause hard brick.
At most you need to restock using Odin.
But no, you can't convert an MTD partition (running yaffs2) back to Overcome ext4 fs.
You need to restock with Odin with pit file selected.
EDIT: the updater can convert FROM ext4 to YAFFS2, so you go from Overcome to CM9 direct but not the other way round.
Click to expand...
Click to collapse
Well there isnt really any other brick then "hard" brick. If you can still use download/cwm etc then its not bricked at all. I think the term is just used far too loosely nowadays.
When I mentioned stock with Overcome I was referring to overcome safe stock guide/files, So its safe to re-stock with them after using CM9, I just need to repartition etc?
Thnx for reply bud.
pretty much it.
restock to GB-stock-safe-V5 with repartition should get rid of MTD safely.
MTD and EXT4 are different partition styles. All you need to do, as per priyana, is go to download mode, run odin, select the .pit file, check the re-partition and shoot. That will get you back to the stock partition style.
Actually....BML and MTD are partition type.
EXT4 and YAFFS2 are filesystem types.
Sent from my GT-P1000 using XDA
Can anyone help me?
I've did the exact thing that you're not supposed to do. Flash fra a MDT rom to a non MDT rom. Now whenever i try ti reflash to stock rom i'll get a bootloop. Not just with this rom but with all other roms. But if i try to flash the AOPK rom with MDT partition it boots fine.
How do i partition that MDT partition to stock?
Wrong to say not supposed to.
That in fact is how most if not all of us get to mtd rom.
How else to go to mtd if not from non mtd.
To flash back to stock, flash with Odin with pit file selected and repartition checked.
Sent from my GT-P1000 using XDA
Ok Safety Advice:
1st to go back from MTD to any file system whether RFS or EXT4 a FULL RESTOCK with with REPARTITION is mandatory (no workaround or shortcuts around that).
2nd Safety Advice. Since the dawn of the MTD CM9 has requires repeated attempts to restock. I would say you need to Strip the stock safe package from the bootloaders (just Delete boot.bin and sbl.bin files from the tar archive). They aren't needed anymore after you have jumped Ship from Froyo to GB. Also Bootloader bad flash is the only way really to brick a Samsung Device as you may have known.
Just my 2 cents.
So, it is not as easy as ABC to revert back to GB from CM9?
I see that GB-Stock-Safe-v5 has got everything in the package (including the dbdata.rfs that gives many people trouble). If after flashing it with a pit still does not work, what else can we do?
I found this youtube on moving from MTD back to BML, but on Samsung EPIC.
www.youtube.com/watch?v=ds9rwAoI2IQ
I know it's probably a stupid noobie question, ... but I did forgot to do this simple thing so many times:
You did a factory wipe and cache data wipe, right?
did you flash it like documented in the picture attached by phlooke here ?
http://forum.xda-developers.com/showthread.php?p=20974872
priyana said:
did you flash it like documented in the picture attached by phlooke here ?
http://forum.xda-developers.com/showthread.php?p=20974872
Click to expand...
Click to collapse
Oh, I am not the one in trouble (knock on the wood). I give comment because I also see his post on AOKP while I'm learning about the ROM. He mentioned that he already did repartition:
http://forum.xda-developers.com/showthread.php?t=1523174&page=168
Ah I see.
Well, I don't know what he did.
But if he re-stock. he should at least boot up the JQ1 stock rom and confirms everything is ok, which I am sure it was not yet ok for him.
He shouldn't go ahead with Overcome Kernel yet.
You have to proceed logically and rule out each possible cause of problem.
you cannot go back from mtd to ext4 so easily. you need to flash gb stock package via odin or heimdall to go back to ext4 from mtd. cwm will not work
Actually going back to stock means going from mtd to bml, not ext4.
And it will then format the partitions with RFS file system.
You only get ext4 if you flash overcome kernel.
Sent from my GT-P1000 using XDA
Already tried flashing stock rom with odin, and checking re-partition, didn't help.
Anyway it's working now ^^
@jakk212 -Please post your problem at ONE thread buddy. I'm sure you did not even see my reply at the AOKP thread.
----
And STOP flashing GB-stock-safe over and over again. I am very greatful teamovercome created it but sometimes there are easier and better solution than forcing it down your throat.
-----
As I said in the AOKP post, (actually the link I provided with it)
what I did was, I reverted to a 2.3.3 gingerbread STOCK downloaded from sammfirmware OR check.fus downloader attached it with .pit file(please search or use the one included with ODIN) while checking the repartition.
After finish, mostlikely you will still be in the bootloop because many ROMs do not inclide dbdata.rfs.
Flash dbdata.rfs.tar (please search).
when u r done flashing dbdata, reboot, and wait on the 'samsung' boot for as long as 10minutes for it to update the partition and retrieving and reading and updating.
Don't assume it is on a bootloop forever before you waited at least 10 minutes on SAMSUNG boot.
Jakk212 said:
Already tried flashing stock rom with odin, and checking re-partition, didn't help.
Anyway it's working now ^^
Click to expand...
Click to collapse
Anyway it's working now
(without telling us who tried to help, what did you do, for the benefit of others)
oh well... all good for you. That is good to hear.
Just wish you can share.
Ah! I missed that one short sentencd.
priyana said:
Anyway it's working now
(without telling us who tried to help, what did you do, for the benefit of others)
oh well... all good for you. That is good to hear.
Just wish you can share.
Click to expand...
Click to collapse
Dude relax;
I've followed the overocme stocksafe guide, but when flashing i've also included the modem.
So i've did the same as before but flashed the modem and it worked.
Sorry for spamming.

Categories

Resources