[Q] I need some serious help, I keep making things worse! - Galaxy Tab Q&A, Help & Troubleshooting

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:

Related

[q] need serious help. Phone bricked :(

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!

[Q] After flashing back stock ROM, the phone keeps blinking on the boot screen (HELP)

I am in desperate need of help you guys! I screwed up so hard that I don't even know where to begin...
THE SITUATION:
-Right now when I go to turn on my phone, it will only stay on the current SAMSUNG GALAXY S I9000 screen (the very first screen when booting your phone) and it keeps flashing in and out.
Before trying to use Odin to put back the original Kernal on my phone, it was just stuck as the SAMSUNG GALAXY S I9000 screen, still wouldn't start. <I followed this website step by step>
http://www.samsunggalaxysforum.com/...-to-a-stock-rom-after-installing-darky's-rom/
BEFORE ALL OF THIS EVER HAPPENED:
I finally rooted my phone and manage to download Clockworkmod recovery on my phone and then used it to flash Darky's 10.2 custom ROM. Everything turned out great except at the beginning of the boot, the screen turned all rainbow coloured, completely distorted, and it continued to do that. I then tried to go back to Recovery mode to do the Voodoo lagfix but I couldn't even get into the recovery mode anymore, it either wouldn't let me, or it did but the screen didn't go to it properly (more likely the first one). I read somewhere that if you reflash your phone again, it should make all the tweeks go away. So I tried that from the Darky's tools menu and ever since then, I've been stuck with the Boot Screen this whole time...
I already bricked my phone once, and that was before the Flashing Boot Screen.
I really need help you guys, I would at least like to have my phone back to the original basis, at least! Your help would be greatly appreciated!
THANK YOU
P.S. (i'm not that great at all this phone tweeking, but I've succeeded in doing it up until yesterday)
Can you get into download mode (vol down+home+power while putting the battery in)?
If you can, just reflash a stock or custom rom in odin (like a darky odin rom) as guided by whatever rom you choose.
If you cannot get into download mode then we should know that too.
Edit: oh it looks like you could (and hopefully still can). Try a different rom or reflash. Sometime things do go wrong but as long as you can get to the download screen you should be fine in the end.
G
gfacer said:
Can you get into download mode (vol down+home+power while putting the battery in)?
If you can, just reflash a stock or custom rom in odin (like a darky odin rom) as guided by whatever rom you choose.
If you cannot get into download mode then we should know that too.
Edit: oh it looks like you could (and hopefully still can). Try a different rom or reflash. Sometime things do go wrong but as long as you can get to the download screen you should be fine in the end.
G
Click to expand...
Click to collapse
Yes, I can get into download mode! (thank you for reading my post).
If it's not too much to ask, could you maybe find the ROM that would be good for me to flash, considering my situation?
I want to be sure that it's what the top tech guys would recommend
A link would be appreciated
thank you again!
I'd start with a Darky rom - lots of users - active forum and odin editions for your situation. I have to go but you'll find the link on the first page of the development section.
G
gfacer said:
I'd start with a Darky rom - lots of users - active forum and odin editions for your situation. I have to go but you'll find the link on the first page of the development section.
G
Click to expand...
Click to collapse
So in essence all I have to do is flash the Darky ROM V10.2 with Odin using the Download mode on my phone and it should be okay?
Wait one caveat. Was it a gingerbread rom or froyo? Use a Darky rom of the same type...
Then yes it should be ok if you follow their guide. Cross fingers.
Sent from my GT-I9000M using XDA Premium App
gfacer said:
Wait one caveat. Was it a gingerbread rom or froyo? Use a Darky rom of the same type...
Then yes it should be ok if you follow their guide. Cross fingers.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
well...I did everything you said. The ROM is on there alright, it flashed and everything (And I know this because now when the boot screen STILL FLASHES, the darkcore & darky's rom logo are on it too).
THIS TIME AROUND:
The stock recovery seems to work...
any ideas??
Well we are sort of in long shot territory now... OK first try using a different odin version or ez odin and reflash.
If still not working??
Might be warranty time then but others are welcome to chime in.
Sent from my GT-I9000M using XDA Premium App
gfacer said:
Well we are sort of in long shot territory now... OK first try using a different odin version or ez odin and reflash.
If still not working??
Might be warranty time then but others are welcome to chime in.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Alright I'll try and reflash the same one using a different version of odin the. I'll let you know what happened
gfacer said:
Well we are sort of in long shot territory now... OK first try using a different odin version or ez odin and reflash.
If still not working??
Might be warranty time then but others are welcome to chime in.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
tried ezodin, flashed it, and i still get the exact same thing I've exhausted every single possibility there is!!!
I really need help on this, my warranty is not gonna do anything because i have the phone rooted..
If you flash a stock rom with pit the root is gone. It won't boot but they can't prove it was you either and I don't think it was you.
But see my other post on your other thread for one last thought.
G
Sent from my GT-I9000M using XDA Premium App
gfacer said:
If you flash a stock rom with pit the root is gone. It won't boot but they can't prove it was you either and I don't think it was you.
But see my other post on your other thread for one last thought.
G
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
okay that could be useful data potentially (let's hope it won't have to be).
If you didn't see my reply from the other thread, here it is:
Once I rooted my phone, I automatically went from Stock Froyo to Darky's 10.2 extreme edition. It worked and everything except for that color disfiguration and the clockworkmod recovery not working.
It's weird because after I flashed my first darky's rom, i checked the phone and it said that the firmware version was 2.3.X (I believe X may have been 4). So from what you're saying, I don't exactly think it has anything to do with the fact that I went straight from froyo stock to GB darky ROM.
So are you saying that I should flash darky's 9.3 for Froyo and THEN flash the latest version?
No I think that you need froyo re edition then stock gb with bootloader (as the instructions say I thought) then a custom gb like 10.2.
Sent from my GT-I9000M using XDA Premium App
gfacer said:
No I think that you need froyo re edition then stock gb with bootloader (as the instructions say I thought) then a custom gb like 10.2.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Ok, so just to be 100% on this
-I should flash Darky's 9.2 froyo onto my phone,
-then I should flash regular GB onto my phone (Not sure about the bootloader part though, if you could clarify that)(Also where would I get JUST a stock GB ROM?)
-then I can flash a custom GB ROM?
gfacer said:
No I think that you need froyo re edition then stock gb with bootloader (as the instructions say I thought) then a custom gb like 10.2.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
well i can safely say that flashing the 9.2 froyo rom was a fail. It's still doing the same old routine.
I just know that this problem can be fixed somehow without sending it in to bell or samsung or something.
roma17 said:
well i can safely say that flashing the 9.2 froyo rom was a fail. It's still doing the same old routine.
I just know that this problem can be fixed somehow without sending it in to bell or samsung or something.
Click to expand...
Click to collapse
I think you are right but other than trying again and again, which I've done before -though now I know why I had too - I am out of suggestions. Good Luck and if I have a brainwave I'll let you know.
Sent from my GT-I9000M using XDA Premium App
OK a few last brainwaves:
1) Try a fully complete stock rom with cache.rfs, dbdata.rfs, factoryfs.rfs, modem.bin, param.lfs, zImage, and sbl.bin (this was from JL2 rom for Bell - not sure if they all have the sbl.bin) and pit.
The key is to make sure it is complete. Try downloading the same rom from 2 different sources just to be sure its not a corrupt download (going overboard I know).
2) Can you get into recovery? Try to format partitions (not system) under advanced features (I think - I only have 3e right now as I am trying to diagnose other issues).
3) If you have a froyo rom on at one point, try to put a steam recovery kernel on. Its not really being developed anymore but I think that if you put a CWM packaged rom on to the external SD you could flash from there or at least move it to the internal and then flash it. Worth a shot. Or you might be able to transfer one in regular CWM recovery - can't recall as I have not had to try for about 8 months.
4) If you really want to try something completely different, and I am not sure I've got the balls if it was me but if you can get a file to flash from CWM or steam that you can get on from the external SD, you might try CM7. It uses a completely different file system so you'd have to go back to froyo via odin only (as a samsung based rom will not play well when flashed on top of the cm7 file system).
And calling it a day at this one...
gfacer said:
OK a few last brainwaves:
1) Try a fully complete stock rom with cache.rfs, dbdata.rfs, factoryfs.rfs, modem.bin, param.lfs, zImage, and sbl.bin (this was from JL2 rom for Bell - not sure if they all have the sbl.bin) and pit.
The key is to make sure it is complete. Try downloading the same rom from 2 different sources just to be sure its not a corrupt download (going overboard I know).
2) Can you get into recovery? Try to format partitions (not system) under advanced features (I think - I only have 3e right now as I am trying to diagnose other issues).
3) If you have a froyo rom on at one point, try to put a steam recovery kernel on. Its not really being developed anymore but I think that if you put a CWM packaged rom on to the external SD you could flash from there or at least move it to the internal and then flash it. Worth a shot. Or you might be able to transfer one in regular CWM recovery - can't recall as I have not had to try for about 8 months.
4) If you really want to try something completely different, and I am not sure I've got the balls if it was me but if you can get a file to flash from CWM or steam that you can get on from the external SD, you might try CM7. It uses a completely different file system so you'd have to go back to froyo via odin only (as a samsung based rom will not play well when flashed on top of the cm7 file system).
And calling it a day at this one...
Click to expand...
Click to collapse
Okay, basically at this point, I just want my phone to work I've tried what you said. I remember that before rooting my phone initially I was running Froyo 2.2.1. So I found the ROM for that ( http://www.samfirmware.com/WEBPROTECT-i9000.htm ) Just like you said. I downloaded from the *Provider Samsung Galaxy S i9000 heading and picked the I9000BOJS5 ## from February 2011 because I think somewhere around there I updated my phone to Froyo. Flashed it, did everything, still no luck.
I've had a recent hunch though. When the bootscreen boots up, it keeps saying i9000 only, when before it used to say i9000M at least for a little bit (yes my phone is i9000m). Is there a stock froyo rom that's specifically designed to go with the i9000m model? Or are they just all the same?
Never give up
-Thank you so much

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

Flashing CM10 on GT-P1000R

Hi all. Couldn't find any posts about this specific problem so here goes:
I'm trying to CM10 on the following device:
Model number: GT-P1000R
Firmware version: 2.3.3
Baseband version: P1000RUXKG1
Kernel version: 2.6.35.7
Build number: GINGERBREAD.UXKG1
I've rooted the device with CF-Root v3.3 (http://forum.xda-developers.com/showthread.php?t=885734, CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.zip) which installs CWM 3.0.0.5. When I reboot in CWM Recovery mode and try to flash the zip, I get the following error:
assert failed: assert(getprop("ro.product.device") == "galaxytab" || getprop("ro.build.product") == "galaxytab" ||
getprop("ro.product.device") == "GT-P1000" || getprop("ro.build.product") == "GT-P1000");
Click to expand...
Click to collapse
I got around this by removing the assert line from updater-script and reflashing and although I see the logo, I get stuck in a boot loop as it tries to finish. Any way to get CM10 working on my GT-P1000R? No one else seems to have this device (it's GSM on Rogers in Canada).
P1000R is just a normal P1000 (M or R, plain P1000)
I have not tried but I am sure CM10 need CM9 first.
pmdarrow said:
Hi all. Couldn't find any posts about this specific problem so here goes:
I'm trying to CM10 on the following device:
Model number: GT-P1000R
Firmware version: 2.3.3
Baseband version: P1000RUXKG1
Kernel version: 2.6.35.7
Build number: GINGERBREAD.UXKG1
I've rooted the device with CF-Root v3.3 (http://forum.xda-developers.com/showthread.php?t=885734, CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.zip) which installs CWM 3.0.0.5. When I reboot in CWM Recovery mode and try to flash the zip, I get the following error:
I got around this by removing the assert line from updater-script and reflashing and although I see the logo, I get stuck in a boot loop as it tries to finish. Any way to get CM10 working on my GT-P1000R? No one else seems to have this device (it's GSM on Rogers in Canada).
Click to expand...
Click to collapse
i think u need to install overcome kernel firts
Seeking help flashing my SGT P-1000R
"I got around this by removing the assert line from updater-script and reflashing and although I see the logo, I get stuck in a boot loop as it tries to finish. Any way to get CM10 working on my GT-P1000R? No one else seems to have this device (it's GSM on Rogers in Canada)."
I have had the same difficulty flashing the rom for my GT-P1000R, as most roms are designed for the generic GT-P1000 and upon flashing check for the version and stop because ours is specific to Rogers. Exactly what did you do to modify the updater-script and what is the file called in rom ZIP package?
To be honest, ever since I was foolish enough to upgrade to Gingerbread earlier this year I have regretted it, as my Bluetooth no longer works with my HID keyboard. As I believe in going forward is best, I am looking to upgrade to ICS, but as a last resort going back to Froyo (if I can find it) would get me back the functionality I lost.
I would appreciate any help you can provide as I have scoured the net and found very little that deals specifically with our version (GT-P1000R) of the SGT.
Because P1000R= P1000
Sent from my GT-P1000 using xda app-developers app
I am still not able to update my ROM
priyana said:
Because P1000R= P1000
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Perhaps, but every time I try to flash a rom made for a P1000, the install fails indicating in the error message that it has detected my tablet as being a SGT P1000R, hence my original inquiry. I am sure it is simply a question of updating a config file to fool the installer, but which one?
Have you heard of Overcome method?
It will ensure your system is detected as P1000
http://www.teamovercome.net
Read the guide,
Missing pictures can be seen here.
https://docs.google.com/file/d/0B7k...EyNS00Yzg5LWE0MTktYmYyMjA1MThmYzQz/edit?pli=1
or
http://forum.xda-developers.com/showthread.php?p=20974872
Follow the picture step by step.
missing files at
http://tabfirmware.com/2012/01/romk...e-7-series-v4-1-0-♫-overcome-kernel-v4-0-0-♫/
and missing kernel here
http://forum.xda-developers.com/showpost.php?p=27801159&postcount=8
Sigh! Mirrors disappearing fast.
Mission Partially Completed.
priyana said:
Have you heard of Overcome method?
It will ensure your system is detected as P1000
http://www.teamovercome.net
Read the guide,
Missing pictures can be seen here.
https://docs.google.com/file/d/0B7k...EyNS00Yzg5LWE0MTktYmYyMjA1MThmYzQz/edit?pli=1
or
http://forum.xda-developers.com/showthread.php?p=20974872
Follow the picture step by step.
missing files at
http://tabfirmware.com/2012/01/romk...e-7-series-v4-1-0-♫-overcome-kernel-v4-0-0-♫/
and missing kernel here
http://forum.xda-developers.com/showpost.php?p=27801159&postcount=8
Sigh! Mirrors disappearing fast.
Click to expand...
Click to collapse
Thank you for the links to the Overcome method, and I now have successfully upgraded my former SGT P1000R, Android 2.3.3, to a SGT P1000, Android 2.3.6 - A significant improvement indeed! Unfortunately my test to see if my Bluetooth HID keyboard works with my new and improved SGT came up short - Will pair, but not connect.
After doing some research and coming to the sad conclusion that only an upgrade to ICS will do to get the aforementioned functionality to work, I tried AKOB and CM9 upgrades, following the instructions available. Each and every time I tried the upgrade, the tablet went into an endless loop of reboots indicating an error, which was displayed too quickly to read. I ended up having to restart the Overcome process again to salvage things.
Alas it is late and my quest to get ICS installed on my tablet (unless someone can tell me how to get a connection to my Bluetooth HID keyboard in 2.3.6) will wait for another day. Thanks anyway for the help.
probstc said:
After doing some research and coming to the sad conclusion that only an upgrade to ICS will do to get the aforementioned functionality to work, I tried AKOB and CM9 upgrades, following the instructions available. Each and every time I tried the upgrade, the tablet went into an endless loop of reboots indicating an error, which was displayed too quickly to read. I ended up having to restart the Overcome process again to salvage things.
Click to expand...
Click to collapse
IIRC the endless boot loop is due to the install process complaining that it couldn't find some partitions. When you get to that point you should just reboot to recovery and install the zip again for the 2nd time and it should work then.
I finally have a fully functional SGT P1000, running the latest version of CM9 ICS, and I must say this has breathed new life to my tablet! My sincere thanks for all the assistance I have received, despite what at times must have seemed endless silly questions for the more veteran members here on xda-developers.
Now time to get used to the ICS interface and some of the quirks (e.g. mapping of storage) that come with this new version of Android. However, thanks to the obvious removal of all the "bloatware" that Rogers added, the performance of my tablet is phenomenal! :victory:
Which files for GT-P1000R running on GB2.3.3?
probstc said:
Thank you for the links to the Overcome method, and I now have successfully upgraded my former SGT P1000R, Android 2.3.3, to a SGT P1000, Android 2.3.6 - A significant improvement indeed! Unfortunately my test to see if my Bluetooth HID keyboard works with my new and improved SGT came up short - Will pair, but not connect.
After doing some research and coming to the sad conclusion that only an upgrade to ICS will do to get the aforementioned functionality to work, I tried AKOB and CM9 upgrades, following the instructions available. Each and every time I tried the upgrade, the tablet went into an endless loop of reboots indicating an error, which was displayed too quickly to read. I ended up having to restart the Overcome process again to salvage things.
Alas it is late and my quest to get ICS installed on my tablet (unless someone can tell me how to get a connection to my Bluetooth HID keyboard in 2.3.6) will wait for another day. Thanks anyway for the help.
Click to expand...
Click to collapse
Hi! First of all, thanks for all this information! I Also have a GT-P1000R (Rogers) running on the same gingerbread version UXKG1 and rooted with the original thread. So, literally, my tab is in the EXACT situation from the original thread. I am assuming that in order to flash any custom ROM's, i need my tablet to be recognized as a GT-P1000 . I am reading the manual, and i am wondering which modem to use. Or do I just need to do an update considering I am already running Gingerbread 2.3.3 ? My overall goal is to have my tablet recognized as a GT-P1000 (not with the r) and eventually upgrade to ICS or higher, also for the primary reason of using a bluetooth (hid supported) keyboard...among other things.
I am familiary with Odin and these instructions are great, I am just slightly unclear what to do in the case of already being on gingerbread 2.3.3, but working with a GT-P1000r. Thank you in advance for your help!
---------- Post added at 08:36 PM ---------- Previous post was at 08:25 PM ----------
probstc said:
I finally have a fully functional SGT P1000, running the latest version of CM9 ICS, and I must say this has breathed new life to my tablet! My sincere thanks for all the assistance I have received, despite what at times must have seemed endless silly questions for the more veteran members here on xda-developers.
Now time to get used to the ICS interface and some of the quirks (e.g. mapping of storage) that come with this new version of Android. However, thanks to the obvious removal of all the "bloatware" that Rogers added, the performance of my tablet is phenomenal! :victory:
Click to expand...
Click to collapse
I also posted this above to another reply, but am worried it will get missed.
I have the same table you do (GT-P1000R) with Rogers, and it was rooted with the same file you used in this original thread on UXKG1.
Do you recall if you just had to do an update with overcome (since you were also running 2.3.3 , UXKG1 as per your first post) , or did you do a complete overhaul.
If you had to do the entire process, which modem did you use? these are the options given...
-GSM based GT-P1000 Tab (Asia, Europe, Middle East, Occeania/Africa, rest of world, etc..) : use JPZ MODEM
-North American T-Mobile Tab user: use T-Mobile Modem
-AT&T (USA), Tel Cel , etc - use JK3 modem.
I am assuming i would use the NA Tmobile based, considering Rogers is Canada's 'sister company' to T-Mobile? but i want to be sure...
Thanks for the help..as you know..there isn't a lot of info on GT-P1000R version..
Not quite.
Rogers is using 850/1900 MHz , the same as AT&T USA
the term NA T-Mobile there is to differentiate that with the UK T-Mobile, which use the usual European frequency.
so At&T modem ?
priyana said:
Not quite.
Rogers is using 850/1900 MHz , the same as AT&T USA
the term NA T-Mobile there is to differentiate that with the UK T-Mobile, which use the usual European frequency.
Click to expand...
Click to collapse
Awesome..thanks for clarifying. JUST in case...I will Clarify then that I should use the A&T , etc modem version? Any other tips I should be aware of ...as I am working with a rogers version? Thanks.
Yes, use AT&T modem.
No other tips regarding special treatment, they are identical to normal P1000 except that the modem radio is made to work on 850MHz for the 3G part.
Anything you read about P1000 here applies equally to a P1000R
And you can use the Overcome method to get yourself a CWM recovery to flash ICS.
The link to its latest files and guide is in my signature.
If you are prepared to wipe out everything and start fresh.
Get the GB-stock-safe-v5 package (it has rom, odin, windows drivers, modem files)
and the PDF (read from page 7 onward)
and the Overcome Kernel 4.0 tar format.
Only the kernel, you don't need the Overcome Series 7 rom, if your eventual target is ICS.
Once you completed the step of flashing the kernel, you can reboot to CWM recovery and use that to flash ICS/JB, then its corresponding gapps, and you are done.
Last question...(i hope)
priyana said:
Yes, use AT&T modem.
No other tips regarding special treatment, they are identical to normal P1000 except that the modem radio is made to work on 850MHz for the 3G part.
Anything you read about P1000 here applies equally to a P1000R
And you can use the Overcome method to get yourself a CWM recovery to flash ICS.
The link to its latest files and guide is in my signature.
If you are prepared to wipe out everything and start fresh.
Get the GB-stock-safe-v5 package (it has rom, odin, windows drivers, modem files)
and the PDF (read from page 7 onward)
and the Overcome Kernel 4.0 tar format.
Only the kernel, you don't need the Overcome Series 7 rom, if your eventual target is ICS.
Once you completed the step of flashing the kernel, you can reboot to CWM recovery and use that to flash ICS/JB, then its corresponding gapps, and you are done.
Click to expand...
Click to collapse
This might sound dumb - but because i've boot looped my galaxy s I9000m before (that STUPID m at the end...just like the r for my tab..) .. i want to make sure what exactly will be happening. I am familiar with Odin and flashing kernels, not so much modems...
My end goal is to EVENTUALLY flash ICS or J/B , but i haven't thought that far as to which one to go with, etc..so i might not do that part for another week or so -whenever i have time.
If i only do the instructions you gave me (for the rom, odin , etc) and the kernel, my tab should be all good to still use in the mean time, until i decide to flash ICS or JB?
I'm sorry if this is a dumb question.... I appreciate the assistance, and will be giving 'likes' and donations for SURE for all the help.
Yes, the guide is for Overcome Rom which is stock Samsung based gingerbread Rom.
The look is very closed to stock, but the kernel is improved.
Many are happy with just running it.
Sent from my GT-I9300 using xda app-developers app
I am sorry, but as I read the thread through some more...i am still a bit confused of a couple of things. I know this is really probably a simple process...but bricking my tablet is the last thing i want to do.
Answers to the following would be so helpful:
1) Do I need to install the modem? I am currently on GB 2.3.3 unlocked and rooted. My tablet and root information is the same as the original thread. It is rooted with
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.zip from the following thread http://forum.xda-developers.com/showthread.php?t=1317384 . I have not installed a modem before..so not exactly sure when/why this should be done and when it is not necessary to. - or do i ONLY need to go into odin and flash the kernel and rom. I am trying to get my tablet to be recognized as just GT-P1000 not with the r. It is the modem that will change how my tablet is recognized?
2) Do I need to insert a SIM card when I flash Overcome modem (if necessary) and kernel and Rom?
I do have a SIM card capable tablet, but I dont actually have a sim card for it. I use WIFI - and tether it from my phone if i need to. My service provider in Canada, Sasktel, blocks SIm cards from being able to use it in more than one device at a time (lame I know) , so buying a SIM card and not using the radio doesn't make sense. that being said , I DO want to be able to use the radio with a SIM card if i need to, like when I travel overseas and purchase one for their carriers.
Thanks again!
Your current rooting method leave your tab as P1000R, that is why I recommended overcome from scratch.
And I didn't know you are rooted and have cwm
Modem is for mobile network.
Wen you flash with Odin "repartition" , your modem will be wiped out.
A modem is required.
if you never use mobile function, any modem will do.
Remember being P1000R, if you are overseas other than with USA at&t, you only get 2G.
In Europe and Asia the UMTS freq is 2100Mhz and your tab is incapable of doing that.
You not need SIM to flash overcome.
Since you have cwm, you can just flash overcome ROM series 7 from cwm. Try that.
Since
Sent from my GT-P1000 using xda app-developers app
There is a really good CM10 (JB) ROM: sapir-rom.blogspot dot com Sorry for this type of link, but I can't post links yet :$
I just just that, went into my already cwm and flashed the rom - must say...impressive! wifi works (connected to two devices for trial, as i've had issues with this in the past) and works great.
Thank you SOOOOOO much for the help on this. you answered sooo many helpful questions.
TBH - i love this ROM , and i would love to keep it as this. but it is does not have HID bluetooth compatibility. any plans for the future to have this available on this ROM?
MY GT-P1000R is now without the stupid "r" !

WiFi Dead? Galaxy Tab GT-P1000 [SOLVED]

What's good, chaps? This problem is currently on Overcome 4.1.0--beautiful ROM.
So what had happened was......
My Tab's WiFi worked perfectly, until yesterday (from the time of this post). Before this problem occurred, I had tried to flash a file I though would be useful for the Tab. The file sent my Tab into bootloops, and I scolded myself for not having made a nandroid.
I decided it'd be a good chance to try another ROM.
I eventually lighted on MIUI v4. I liked it for 5 minutes, then wanted to go back to Gingerbread (Overcome). I read that the MIUI ROM was an MTD ROM; I have no idea what that is, heh.
The only way to return to Gingerbread was to use Odin, so I did that. I followed every instruction on flashing the Overcome ROM to the letter. The installation went smoothly....until I found out my WiFI is broken. In fact, the baseband comes up as unknown--that never happened before. The Tab was getting a cellular signal, but that was it. I tried to reinstall the modem using Odin--no good. I tried using the fix from the Overcome Thread--no good.
I don't know what's wrong or what to do next.
If anyone can help me shed some light on this, it'd be greatly appreciated!
Thanks in advance!
I don't know why most people will try to fix their broken tab using overcome rom, find it broken but didn't tell how it was when it was merely on SG-stock-safe-v5
remember, Gb-stock-safe-v5 is Gingerbread from Samsung, JQ1 rom, in fact.
If it is broken at that stage, it is an entire different story than if it broke under Overcome ROM.
So which one is it?
Sorry for my late reply!
I found out it was broken when I reflashed the Overcome ROM. I never tried WiFI when I flashed GB-Stock-Safe-v5, so I can't tell you anything from there.
Did I do the right thing in using Odin, when downgrading from ICS 4.0.4 to GB 2.3.6?
No idea. But re-do the GB-stock-safe-v5 again and see how it goes.
If all good, add overcome kernel, see again how it goes.
if all good, flash overcome rom, and then see again.
Be methodical when you want to find your root cause.
Alright, I'll give it a go. Thanks for your help!
For the record, does downgrading from flashing a ROM with a different partition set-up have to be done a certain way?
just need a rom that has pit file and you tick the repartition in Odin.
That should take care of the downgrading from MTD rom
Followed your instructions and everything is back to normal!
Thanks again!
priyana said:
just need a rom that has pit file and you tick the repartition in Odin.
That should take care of the downgrading from MTD rom
Click to expand...
Click to collapse
tried every thing. flash froyo, flashed ginger. flashed Overcome's. flashed other roms like Boca or Miui.
but nothing can bring back the wi-fi even tried overcome's wi-fi fix and wpa-supplicant with proper permissions bla bla bla...
the tab was working fine before and was on overcome's last rom. but suddenly if wi-fi switched on, tab started giving constant re-starts.
do you think it's a hardware issue now? i flashed 2.3.6 stock on which it doesn't give restarts but wi-fi keeps scanning and switching off by itself.
3G works fine no issues at all.
please someone tell me if there is any thing that i'm not trying.
Yours sounds like hardware issue.
Sent from my GT-N7100 using xda app-developers app

Categories

Resources