Related
Dear Guys,
Call drops very badly, I would like to send the i9000 back to Samsung for checking. What should I do first, if have the speedmod K12 Kernel on it at the moment? How to remove it and restore the Filesystem ? Is the option on the recovery to restore the filesystem good enough? if so, where can I got the original Kernel? I used the ODIN to write the SpeedMod, should using the same tools?
Sorry a lot of question stupid question. I know nothing about the system, I just want a faster i9000. But, recently, I find call drops in almost every call. I have upgrade the K12 to a newer version, but does not have any improvement. I believe it is not the Kernel issue, nor the Provider.
Thanks alot.
Flash stock firmware with ODIN, then you got original firmware + kernel
Go to http://www.samfirmware.com/ register and then download your stock firmware then use odin and flash the files and it should be ok I Had the same problem
Thank you.
Will try the samfirmware today .
BTW, shall I convert the Filesystem back to RFS first? Or just apply the file directly?
Convert to rfs first..
Sent from my GT-I9000 using Tapatalk
Hi,
I have upgraded to the Chainfire Gingerbread ROM and everything is great.
I was previously using the Modaco ROM with my filesystem converted to ext4.
Did flashing the Gingerbread ROM convert me back to RFS?
Apologies if this seems like a daft question.
There are no stupid questions. We are all here to learn. The short answer is Yes the gingerbread rom reverted you back to RFS filing system. Long answer is that what we did is simply flash a stock ROM back to our tabs with stock repartition using the pit file which practically reverted the file system to samsungs RFS.
Thanks very much for the prompt answer. Much appreciated.
Sent from my GT-P1000 using Tapatalk
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
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.
So my wife got a good deal on some Galaxy Tabs at her work, and being so familiar with rooting and installing custom ROMs with my Galaxy S2, I jumped right in. Stupid mistake #1. I didn't realize there were so many different versions (The S2 is international, so 99% are all I9100, and mine being I9100M, there was no concern about using I9100 firmware - apparently this was not true of the P1000 and P1000M as I've come to learn), and just followed the first comprehensive guide I found to upgrade from 2.2 froyo to 2.3.3 gingerbread, so that I could go to CM9 or CM10. I tried to flash XWJK8 (and one of the kids ran by and bumped out the USB cable!) and it would only power on to the emergency download mode. I somehow managed to get Froyo back on and working by flashing the Euro flash package (Flashing the PIT and XWJJ4), then flashing OXAJK5. I was able to boot up and was running Froyo again.
Undeterred by the set back, I tried again for Gingerbread (again, not realizing that there were GSM-only ROMs that I shouldn't have been using). I followed a guide by Chainfire (I think) that involved flashing XXJQ1, a new bootloader, and a dbdata file in PDA then finished up by flashing the CF Root OXA-JQ1 kernel. I went into CWM and did a factory reset, clear cache, etc... but it wouldn't boot past the Samsung logo. About this time, I learned about the GSM/CDMA thing, and realized I went wrong. So I set out to try and figure it out for CDMA. Unfortunately, everything refers to this Overcome guide, but the page would not load, so I figured that with CWM working then I may as well try for CM9. It failed (assert errors), so I decided to try for the stock Bell Gingerbread ROM (P1000MUGKF6). It flashes successfully, but after flashing - I get the following errors on boot up:
-- Updating filesystem...
E: failed to mount /dbdata (Invalid argument)
E: discard_filesystem_for_rfs: Can't mount /dbdata
-- Wiping cache...
Formatting /cache...
Cache wipe failed.
-- Applying Multi-CSC....
Installing Multi-CSC
Can't access to '/system/csc/KOR/system/'.
Successfully applied multi-CSC.
Click to expand...
Click to collapse
So just for giggles, I tried a factory reset with the following results:
-- Wiping data...
Formatting /data...
Formatting /dbdata
E: format_volume: rfs format failed on /dev/block/stl10
Formatting /cache...
Data wipe complete.
Click to expand...
Click to collapse
I tried doing the Euro flash again (as it got everything working again last time), and it runs successfully but still won't boot up. So I flashed the Gingerbread firmware for Bell again (P1000MUGKF6), and it still won't boot at this point, just hangs at the Samsung logo. Long story short, I've made a mess of things, and I am thinking that the more I try and fix this myself, the more I'm messing things up. I'm praying that someone here is able to help me fix this mess, otherwise I am at the point of throwing in the towel and letting this thing end up as a brick, as if no one on XDA knows how to fix this, I don't think anyone will know how.
Thanks for reading this novel, I can't tell you how much I would appreciate some assistance!
Use overcome method.
Follow my signature.
Download the GB stock safe and the PDF guide
Jump to page 7.
P1000 and P1000M is identical except for the radio.
But they both are gsm.
If you had flashed wrong ROM you would have had a brick.
You just haven't been flashing correctly.
Sent from my GT-P1000 using xda app-developers app
priyana said:
Use overcome method.
Follow my signature.
Download the GB stock safe and the PDF guide
Jump to page 7.
P1000 and P1000M is identical except for the radio.
But they both are gsm.
If you had flashed wrong ROM you would have had a brick.
You just haven't been flashing correctly.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
I just saw your reply on a different post, and gave it a try. I can't thank you enough! It worked perfectly. After I flashed the Stock Safe I was able to get it to boot up no problem, so I went on to do the kernel, and then flash the Overcome ROM from there (which was successful), but now it's been sitting on the Overcome ROM boot screen for the last several minutes, starting to think it's not going to boot... My end goal was to get CM9 installed on it, so even if Overcome ROM won't boot, am I safe at this point to try flashing CM9, or should I get Overcome ROM working first?
Also if anyone happens to know if I need to download the p1c (cdma) version of CM9 (I'm assuming based on your reply that I don't, and the p1 (gsm) version of CM9 should work, but I just want to be safe).
Thanks again for your help, at least I got things working at one point, and am confident I can get back to that point if things go south again.
So I went with my gut, flashed CM9 for the P1000 (non-CDMA) and it works like a charm. Again, can't thank you for all your help! I can't tell you how much time and grief you saved me from!!
Glad it works out.
In the future, you don't need to flash the overcome ROM.
Only overcome kernel is needed o use its cwm recovery.
The stock safe is needed to give you a clean stock baseline that works with overcome kernel.
the ultimate goal is just to have cwm recovery.
Sent from my GT-P1000 using xda app-developers app
priyana said:
Glad it works out.
In the future, you don't need to flash the overcome ROM.
Only overcome kernel is needed o use its cwm recovery.
The stock safe is needed to give you a clean stock baseline that works with overcome kernel.
the ultimate goal is just to have cwm recovery.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Thanks again for the help, she had bought 2 - 1 Bell and 1 Rogers Galaxy Tab. The Bell one was the one I was working on when I posted this, after finishing it (in total close to 12-14 hours of straight working on it and looking stuff up) I was able to get the Rogers one done in less than 20 minutes haha! :highfive: