Related
Hi everyone,
I own a captivate-i896 (rogers)
I have run into a very serious trouble
I tried to odin back to stock and now I am experiencing this problem. I get the following message:
update media. please wait
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdata:media:Can't mount DBDATA:
copy default media content failed.
PLEASE HELP.
I tried delete all user data. reinstall packages. delete cache. EVERYTHING.
I even trying flashing again 3 times. No luck.
Can someone please help?
First thing is your phone isn't bricked if it still has power and you can see things on it. Second, what were you doing with Odin when it was flashing? Was it the full Odin or a one click version? Are you making sure you flash the proper firmware? What did you have on your phone before you tried going back to stock? Lots more detail is helpful because your phone works...just not like it should. Again its no brick and searching the forums will help with your issue.
This is my Captivate. There are many like it but this one is mine.
haroonazeem638 said:
Hi everyone,
I own a captivate-i896 (rogers)
I have run into a very serious trouble
I tried to odin back to stock and now I am experiencing this problem. I get the following message:
update media. please wait
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdata:media:Can't mount DBDATA:
copy default media content failed.
PLEASE HELP.
I tried delete all user data. reinstall packages. delete cache. EVERYTHING.
I even trying flashing again 3 times. No luck.
Can someone please help?
Click to expand...
Click to collapse
You had a lagfix installed that you did not disable before you reflashed. Your internal partition is still on ext4 but the data is on efs. This is not a problem. You need the one-click version of odin. Search the threads for it and instructions on flashing. You will have the att boot logo but there are ways to work around it, but first do the one click.
Sent from my SAMSUNG-SGH-I896 using XDA App
clemmie said:
You had a lagfix installed that you did not disable before you reflashed. Your internal partition is still on ext4 but the data is on efs. This is not a problem. You need the one-click version of odin. Search the threads for it and instructions on flashing. You will have the att boot logo but there are ways to work around it, but first do the one click.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
I thought Lagfix didn't need to be disabled if you were flashing to stock, just going from ROM to ROM. Besides that, I don't feel comfortable running 1-click for any reason as it bricked my first phone, just trying to flash.
What ROM were you running when you encountered this problem?
Stock, with a SpeedMod kernel. I wanted to go back to a stock kernel with voodoo. Trust me on this one, one-click will restore you to 2.1 if you follow the instructions.
See this thread:
http://forum.xda-developers.com/showthread.php?t=964749
Sent from my SAMSUNG-SGH-I896 using XDA App
The reason you have to disable the lagfix is because with a new ROM you are likely flashing an integrated kernel with a lagfix. Some are Captivate-based, some are i9000-based. Additionally, some use Supercurio's Voodoo Lagfix, some use Hardcore's SpeedMod. One or more of these elements might be incompatible going from one configuration to the new flash config. Without knowing more about what you had before and what you wanted to flash, this is the best explanation I can give.
If you are irked by the AT&T boot screen, I am also partial the this fellow's package, which I have used and works well. Read and make sure you have the Rogers version.
http://forum.xda-developers.com/showthread.php?t=944418
clemmie said:
Stock, with a SpeedMod kernel. I wanted to go back to a stock kernel with voodoo. Trust me on this one, one-click will restore you to 2.1 if you follow the instructions.
Click to expand...
Click to collapse
It has nothing to do with following the instructions - It has to do with the Batch version of the phone - 1010 and 1012 batch numbers do NOT play well with 1-click.
Dante04SRT said:
It has nothing to do with following the instructions - It has to do with the Batch version of the phone - 1010 and 1012 batch numbers do NOT play well with 1-click.
Click to expand...
Click to collapse
I'm well aware of that:
http://forum.xda-developers.com/showpost.php?p=11649620&postcount=5
What you might not be aware of is that Rogers Captivates are not prone to these failures as they are different build numbers. This is a fellow Rogers customer. I'd bet dollars to doughnuts that his build is 10.11.
Thanks everyone for all the responses.
Actually I had doc's rom installed on my phone and I believe I had the hardcore speedmod kernel OR the glitterball's kernel on my fone and also had the lagfix.
I was actually in process of flashing the cyanogen 7 gingerbread when this happened. I forgot to copy the actual flash file(that i was supposed to instal from speedmod kernel recovery) and so i just decided to odin back to stock and start the process all over again. But after doing that my phone never went past the rogers splash screen.
I use the ODIN 1 click software where u just load the PDA and PIT files and flash the fone. I have tried Odin back to stock for Rogers eclair 2.1 and froyo 2.2 without any luck. I also tried the at&t 1 click odin flash back to stock without any luck.
The best I was able to do was to reach the rogers splash screen and then the screen turned black and thats it.
I flashed many different kernels but nothing happened.
I even downloaded the giorgio armani firmware for the captivate and flashed that which got rid of the mounting error in the 2e recovery screen but after the splash screen, the phone just kept vibrating and nothing happened.
I have tried everything you guys asked me too.
Also, after flashing the I9010 rom(giorgio armani), my download mode 3 button combo changed. First, I used vol up and down plus USB to get into download mode but now its changed to vol down + power. This one is not a big deal as i can still get into download mode. But I am telling you all just to help.
I also read somewhere that we cannot repartition and flash using odin 1 click if we have a lagfix kernel installed. I might have done that too that might have caused the problem.
Someone here mentioned that the file system is changed from ext4 to efs or something like that. I don't know what the real problem is.
Please help
clemmie said:
I'm well aware of that:
http://forum.xda-developers.com/showpost.php?p=11649620&postcount=5
What you might not be aware of is that Rogers Captivates are not prone to these failures as they are different build numbers. This is a fellow Rogers customer. I'd bet dollars to doughnuts that his build is 10.11.
Click to expand...
Click to collapse
My build is 10.10
but I never had a problem with flashing with 1-click ODIN to stock before.
I have tried both AT&T and rogers versions through 1-click odin.
Hope that helps.
clemmie said:
Stock, with a SpeedMod kernel. I wanted to go back to a stock kernel with voodoo. Trust me on this one, one-click will restore you to 2.1 if you follow the instructions.
See this thread:
http://forum.xda-developers.com/showthread.php?t=964749
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
I am just going to try your method. I am downloading from here:
http://forum.xda-developers.com/showthread.php?t=731989
However, I cant do master clear because im stuck in recovery. Does it matter?
im going to try and see.
will update soon
clemmie said:
Stock, with a SpeedMod kernel. I wanted to go back to a stock kernel with voodoo. Trust me on this one, one-click will restore you to 2.1 if you follow the instructions.
See this thread:
http://forum.xda-developers.com/showthread.php?t=964749
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
I got it working. THANKS A LOT TO YOU.
YOU ARE THE MAN clemmie.
I didn't know that what I was using before wasn't a 1-click odin lol
it's fixed now. just have to install the rogers eclair or froyo now. Thanks a LOT!
haroonazeem638 said:
I got it working. THANKS A LOT TO YOU.
YOU ARE THE MAN clemmie.
I didn't know that what I was using before wasn't a 1-click odin lol
it's fixed now. just have to install the rogers eclair or froyo now. Thanks a LOT!
Click to expand...
Click to collapse
It can be pretty harrowing when you are in limbo like that, glad to be of assistance.
Clemmie, YOU rock!!! I haven't had this problem, but... your instructions were stated in a way that I could visualize the whole process! If I ever have issues, I'm looking for YOU!
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
Hey Guys,
I have a couple of questions in regards to going back to stock from DarkyROM 10.2.
After using 10.2 for about a month now, I have noticed that while the rom is fast, There are quite alot of glitches in my day to day operations. My 3D HD games no longer work smoothly (as they did in 2.3.3 with CWM), the phone will randomly freeze up when using the browser/gallery/calender etc. After multiple re-flashes I am coming to the conclusion that to get back to my original performance I may need to flash a stock JVQ and then mayby just us CF ROOT or something of the like to get CWM access.
My question is, what preparations need to be done before preforming this flash. Also, can the stock files be flashed with ODIN? Also, if anyone has any input on why DARKYROM 10.2 seems to have these issues, please feel free to let me know. Any help will be greatly appreciated, thanks in advance!!
Phone Specs:
Samsung Galaxy Vibrant (i9000m)
DarkyRom 10.2 RE -w- KC1 Modem
Only Mod preformed after flashing RE was updating the SMS application to the SGS2 App to restore the chat bubble colors. The issues were present before this update. Did the update through DarkyRom Tool.
If you guys need any more information, just let me know..
Anyone??????
Alright, I'll take this one if no one else will. I too have the i9000m, and have learned all I can about keeping it alive and well. Going back to stock is easy. Go to general and look for the stock firmware thread. You will get instructions there on how to flash with odin. I've never used darky before but I did use CM7 and flashed back no problem. You could also look for Ramad's prerooted roms. I'm running one right now, UGKG3. Works great as I couldn't root it myself.
Sent from my GT-I9000M using XDA App
Getinaf said:
Alright, I'll take this one if no one else will. I too have the i9000m, and have learned all I can about keeping it alive and well. Going back to stock is easy. Go to general and look for the stock firmware thread. You will get instructions there on how to flash with odin. I've never used darky before but I did use CM7 and flashed back no problem. You could also look for Ramad's prerooted roms. I'm running one right now, UGKG3. Works great as I couldn't root it myself.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
Hey Dude, Thanks alot for your response! One more question before making the switch....Should the voodoo lag fix that comes with Darky 10.2 be disabled before flashing with Odin back to stock?
If you want to go back to stock ROM. Before flashing disable the lagfix (for safe). You can download the firmware from www.samfirmware.com. and its an odin base installation.
Post your problem in www.darkyrom.com some expert will help you...
Hey guys.
I have flashed stock ROM (2.3.4) via Odin and worked absolutely fine. Didn't need to fiddle with the lagfix or anything. Simply popped phone into DOWNLOAD mode and flashed (with re-partition/wipe and backing up "stuff" beforehand).
The lagfix menu I think, is in the RECOVERY mode in the extended power options menu. I think thats the CWM with the DarkyROM maybe? Either way, you can enable/disable the lagfix in that menu.
Hope this helps!
Akhtar
Hello,
I have Galaxy S 2.2.1 rooted (CF-root) with woring CWM, a Nandroid backup, and Onecosmics ICS goodys locked and loaded on my internal SD card. But still I can't find the b...courage to do a full wipe and flash ICS as if something goes wrong I will be without a descent smartphone for about 2-3 months.
My question is if I can flash straight from 2.2.1 or I should go through CM7 first.
One flash is simpler than 2 in my head..
I reckon that as the days go by I will do it and I want to make sure I do it the right way.
Thank you in advance.
Hi,
I, personally, went through a CM7 flash before going to OneCosmic's ICS, leaving Froyo. It took me about 10 minutes to do it, and in doing it this way, you stay close to OneCosmic's installation instructions.
1. Flash CM7
2. Reboot and test your phone (without installing apps & widgets)
3. Flash OneCosmic's ICS
Hope it might help!
Tilk94 said:
Hi,
I, personally, went through a CM7 flash before going to OneCosmic's ICS, leaving Froyo. It took me about 10 minutes to do it, and in doing it this way, you stay close to OneCosmic's installation instructions.
1. Flash CM7
2. Reboot and test your phone (without installing apps & widgets)
3. Flash OneCosmic's ICS
Hope it might help!
Click to expand...
Click to collapse
I would recommend flashing JVU (using Odin) before cm7 as it contains the latest bootloaders, just to make sure everything works as it should
Sent from my sgs
thanks!!!!
Yeah,
First I think you should install JVS with CF-Root and recovery.
Just register to samfirmware, where you can easily download the required files, also you'll find some tutorial. For CF-root, just google it, and you'll also find some tutorials, than just put the zip in your internal sd, and install it from recovery. Don't forget to remove your microSD before flashing, cause it can be damaged after.
If you did something wrong, you can still go back to stock JVS ( happened to me ) and start it over.
Regards
mformarcee said:
I would recommend flashing JVU (using Odin) before cm7 as it contains the latest bootloaders, just to make sure everything works as it should
Sent from my sgs
Click to expand...
Click to collapse
Works perfect! Thanks
aristomenis said:
Hello,
I have Galaxy S 2.2.1 rooted (CF-root) with woring CWM, a Nandroid backup, and Onecosmics ICS goodys locked and loaded on my internal SD card. But still I can't find the b...courage to do a full wipe and flash ICS as if something goes wrong I will be without a descent smartphone for about 2-3 months.
My question is if I can flash straight from 2.2.1 or I should go through CM7 first.
One flash is simpler than 2 in my head..
I reckon that as the days go by I will do it and I want to make sure I do it the right way.
Thank you in advance.
Click to expand...
Click to collapse
Dont worry, you can always Odin back to 2.x
Download mode through 3-button-combo > Odin (re-partition checked!)
Thank you for your insights, I will probably go to CM7 and then to ICS and if i get any issues I ll go back to 2.2.1 and then start from JVU.
I will let you know, soon I hope..
Going via CM7 should be the safest way. CM ROMS are the easiest and quickest ROMS to flash imo and you shouldn't have any problem. Once you do that without any problems, flashing ICS should be as easy.
Gluck!
So I tried to get CM7 over 2.2.1 with no success so I took the long road and upgraded to stock 2.3.4 via Odin, then flashed rooted CF root kernet, then upgraded to CM7 and finally (and after a lot of sweating) I got to Onecosmic's ICS which is great and really a major upgrade!
I think I have some donating to do........
aristomenis said:
So I tried to get CM7 over 2.2.1 with no success so I took the long road and upgraded to stock 2.3.4 via Odin, then flashed rooted CF root kernet, then upgraded to CM7 and finally (and after a lot of sweating) I got to Onecosmic's ICS which is great and really a major upgrade!
I think I have some donating to do........
Click to expand...
Click to collapse
wow.. ur phone went thru a marathon of flashing and booting !
You don't need courage its like an adventure learn and do it without fear
Flash gingerbread jvs or anything than cm7 or miui and than the onecosmic or teamhacksung
Sent from my GT-I9000 using xda premium
I have a 2.3.4 darky rom JVQ, with darkcore 2.9.2, can i flash directly to cm 7.1 and then to onecosmics rc3.1? Are there anychances to brick my phone in the process?
Sent from my GT-I9000 using Tapatalk
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: