Database Develop

[Q] Help with phone stuck on Froyo 2.2

Hey guys.
Ok so what happened was that I updated to Froyo and it worked perfectly, had it rooted and installed lag fix. Couple of days later it would boot, go past the samsung logo but then nothing. I would be staring at a black screen and when i press the middle button the two buttons on the side would light up. Now i am not able to go into recovery mode but I can go into download mode. Now I have tried flashing the phone. I tried going stock, stock for other countries and also reflashing froyo 2.2. The most successful is froyo because once I have reflashed and reboot for the first time, it goes into recovery mode telling me it is having problem with a couple of things, one of them being the internal sd card, which is fixed by me doing a sd wipe but the next one is a data error, i think it was called dadata but i am not sure, have to double check. Now i cant get that error to go away even by doing a factory rest and once i reboot the phone, it goes back to the state i mentioned before. Plz can any one help?

Zink6 said:
Hey guys.
Ok so what happened was that I updated to Froyo and it worked perfectly, had it rooted and installed lag fix. Couple of days later it would boot, go past the samsung logo but then nothing. I would be staring at a black screen and when i press the middle button the two buttons on the side would light up. Now i am not able to go into recovery mode but I can go into download mode. Now I have tried flashing the phone. I tried going stock, stock for other countries and also reflashing froyo 2.2. The most successful is froyo because once I have reflashed and reboot for the first time, it goes into recovery mode telling me it is having problem with a couple of things, one of them being the internal sd card, which is fixed by me doing a sd wipe but the next one is a data error, i think it was called dadata but i am not sure, have to double check. Now i cant get that error to go away even by doing a factory rest and once i reboot the phone, it goes back to the state i mentioned before. Plz can any one help?
Click to expand...
Click to collapse
Follow this guide.
If you still get error try finding a rom from samfirmware that has pda modem and csc then flash them with odin3 v1.70.

Sounds like you have a bad internal sd. You may have to take it back for warranty
Sent from my GT-I9000M using XDA App

ya so it says that it has some problem with dbdata and that it cant mount internal sd card. Am I screwed?

Zink6 said:
ya so it says that it has some problem with dbdata and that it cant mount internal sd card. Am I screwed?
Click to expand...
Click to collapse
Ok i have just managed to solve a similar problem on my phone..
donwload the file from this link (it's from samfirmware)
add in all
code file into pda, modem file into modem and csc into csc
and add in the 803 pit make sure repartition is checked.
If that doesn't won't i can't help no more..
Any success?

No my friend, no luck. Thanks for the help though. Any one else have any other suggestions?

I have the same problem with my other i9000m. No amount of flashing with odin with whatever firmware helped. I took it into a local 3rd party repair shop. They have fixed 10+ corrupt sd card phones. They said they needed to keep it for one day which tells me its not just a simple flash job. Maybe they have some sort of jtag setup that allows them to reformat the flash chip or something.
Or maybe they are actually removing the chip off the mainboard and reformating it. Whatever it is they are doing, its worth the $70 to get my phone working again. There is definately a fix out there though. And at $70, it's just for labour. They're definately not replacing parts.
Sent from my GT-I9000M using XDA App

Zink6 said:
No my friend, no luck. Thanks for the help though. Any one else have any other suggestions?
Click to expand...
Click to collapse
Have one last try with the jf3 firmware with the 512 pit.. again in odin v3 1.7 code in pda..modem in modem and csc in csc there are two not sure which is better i tried oxa..
JF3 Link
If that doesn't work then yer i guess your only option is take it into a shop.. or send it back to samsung to see if they will fix it for you.

Soft Brick (ODIN not helping)

I'd recently flashed the Cognition new build. Yesterday morning I woke up (3 days later) and found that my phone was stuck at the white and blue AT&T screen.
I preformed the Odin 1-click (as I have many times in the past<I'm not a noob to Odin>) I got my phone into a reboot but now it gets stuck at the Galaxy S screen and then goes dark.
Naturally, I used Odin again with different degrees of failure.
1. Gets stuck at file analysis.
2. Gets stuck halfway through and a blue, green or black screen appears.
3. Stuck at the AT&T screen again.
I've used Odin about 25 - 50 times in the last twenty-four hours.
I've also used the other Odin using the I897UCJH2 PDA file that's provided.
The phone booted directly into recovery and gave this error:
E:Can't Mount /dev/block/mmcblk0p1
(I/O error)
E:copy_dbdata_media: Can't mount SDCARD:
copy default media content failed.
And then it went back to the aforementioned black screen of hell.
I have build 1007 in case that's relevant.
I NEED HELP! Preferably a genius.

im having the exact same problem.
please help

I'm not sure if it matters too much, but it could certainly have had something to do with the kernel the newer Cognition would have installed when you upgraded to it.
Are you using I897UCJF6-final-OCD-REV or I897UCJI6-OCD-REV02-Low?
Most people have the first one, I would definitely try the second if it wasn't working.
The last option is to use Odin3 v1.7 (which you seem to have) and using that to update the kernel to a CM7 one and try to install CM7 onto your phone (and then reverting back to 2.1 stock if you wish).
Not sure if any of those options would work, but give me a yell if you need any help with doing any of the above.

You didn't disable the lagfix before you flashed, and your internal partition is still running ext4 but your data partition is back on efs. See this thread.
You will get your phone working, just be patient and go step by step.

Thank You Both
Thank you both but neither of those two options worked.
I was hopeful that the CM would fix it. I played around with that thought yesterday.
I know the difference between ODIN 1-click and ODIN3 v1.70. I've tried both and neither can get me back up and running. I'm hopeful that someone comes to the table with some resolution. This is frustrating.
EDIT:
Oh and I forgot, I've actually used both I897UCJF6-final-OCD-REV and I897UCJI6-OCD-REV02-Low

If you can get into recovery you can get into download mode.
If you tried one-click, what happens when you try to flash back to stock?

I'm able to get into Download Mode AND Recovery.
That's not the problem.
What happens is that when my phone reboots after ODIN 1-click or ODIN v1.70 my phone boots like its supposed to boot and then it gets to the Galaxy S screen and at that point it just craps out and the screen goes black after a few minutes. I think that the problem is that the internal sd card won't mount. When I'm in recovery it says:
"E:Can't mount /dev/block/mmcblk0p1
(I/O Error)
E:copy_dbdata_media:Can't mount SDCARD:
your storage not prepared yet. please us UI me nu for format and reboot actions"
When I try to format the internal SD using system recovery it says the same thing. I'm able to get my computer to recognize the internal sd card in recovery BUT when I try to access the drive it asks me to format the drive (INTERNAL SDCARD being the drive). It then calls me a sack of SH17 and the computer tells me that it's unable to mount the internal SD.
The problem seems to be that my phone has not mounted any memory what-so-ever. If I were able to perform a masterclear that might help but without it being able to get to the home screen that presents a problem.
It's sh177y because I'll have to end up returning it on warranty AND for that I have to mail it back to Samsung and wait for them to return it to me. I can't go that long without my phone. There are business things that I need this phone for.
Sorry that was just a tiny rant.

You did not read the thread I linked to.
You can't master clear through odin one-click? You should be able to do that without getting to the home screen. Try installing the specific driver package that comes with one click. When the partitions are formatted squirelly, the computer can't recognize the phone as such. Give that a try. You'll get there, be patient.

?
I'm not sure what I missed in that post. I've read and reread that post several times.
To masterclear I believed that you had to be able to get into USB Debugging. I tried to masterclear in both download and recovery mode. Those are the only options where Odin recognizes my phone.

Bwrandon said:
I'm not sure what I missed in that post. I've read and reread that post several times.
To masterclear I believed that you had to be able to get into USB Debugging. I tried to masterclear in both download and recovery mode. Those are the only options where Odin recognizes my phone.
Click to expand...
Click to collapse
I doubt if you have an overclocking kernel from previous rom which you forgot set back to default values when flashing back to stock it's really a pain in the a...

gorgy76 said:
I doubt if you have an overclocking kernel from previous rom which you forgot set back to default values when flashing back to stock it's really a pain in the a...
Click to expand...
Click to collapse
Do you have any suggestions?
Sorry if I seem brash but I've been working on this for three days.

I wish you the best of luck.

ive had similar issues as described in this thread before on ONE pc i have and it can be a real PITA!
Im no real expert but i DO know the pc i use has voltage issues, basically it is running everything fine but things cant seem to charge or external devices tend to act weird occasionally off the usb. What i have done to minimize the similar issues you are describing is
1) plug the usb directly into the back of the pc, basically try different usb ports, some seem to get better voltage/stability.
2) unplug any external devices using usb *printers and whatnot*
3)Alternate PC *sorry this is my end all since i found i have no issues on my laptop*
It doesnt 'sound' like your phone is fubar'd but that your pc isnt getting the strongest connection. again this is comming from someone who had pretty much exactly what your describing and thats what i found
edit: also saw your warranty posting. From me on their 4th captivate and seems to be the final stable one *HORARY!* i can tell you that they will send you a new phone first and you send your defective one back..just do it in the timeframe or they WILL charge your att account

The only thing that I can think of is... Put a kernel that has CWM loaded on to it as recovery (maybe speedmod kernel), boot into recovert (and thus into CWM).
Try deleting all data/cache/etc on it, then try reboot it. Other wise, try and install a ROM straight from CWM (via .zip file, if you can somehow get it on your sdcard).

I'm stuck with phone pc-pc screen. I'v flashed multiple times and went back to stock too without issue. But now... I am stuck at that screen and no button combo works. Ordered a jig but that will take days to get here.. Dont know what to do. And its a work phone. lol Any other things to try?

I'm having a similar issue. I can get into download, and it's recognized by odin. But when I try to write or wipe it just sits at the zimage and does nothing. I've even left it over night to no avail.

Bwrandon said:
Do you have any suggestions?
Sorry if I seem brash but I've been working on this for three days.
Click to expand...
Click to collapse
can your pc still recognizes your phone and copy files towards internal sd card? can you enter 3e recovery? does you lost 3 button combo? file extensions uses lagfix should be one of the culprit and the clock values in the kernel in your previous rom not setting it to default (disabling lagfix and setting voltage and clock speed to default) when flashing back to stock as this would probably causes conflict with the stock 2.1 system. it is realy important not to neglect those default settings as this is the usual reasons for bricked phones that would corrupt the installation process. many people forgot this process due to excitement and ended up with a paper weight phone.

clemmie said:
You didn't disable the lagfix before you flashed, and your internal partition is still running ext4 but your data partition is back on efs. See this thread.
Click to expand...
Click to collapse
gorgy76 said:
file extensions uses lagfix should be one of the culprit and the clock values in the kernel in your previous rom not setting it to default (disabling lagfix and setting voltage and clock speed to default) when flashing back to stock as this would probably causes conflict with the stock 2.1 system.
Click to expand...
Click to collapse
You just can't make it clear enough for some people.
clemmie said:
You can't master clear through odin one-click? You should be able to do that without getting to the home screen. Try installing the specific driver package that comes with one click.
Click to expand...
Click to collapse

Clemmie,
"Try installing the specific driver package that comes with one click."
I'm not sure if you read my OP; I've already done that. I've actually done that several times. I understand how to use ODIN 1.00 and 1.70. I've been using them since they were released.
The lagfix/overclock issue that has been mentioned. I understand that. Fixing it is the problem.

Have you tried my solution? It's definitely worth a try :/

[Q] OH NO! Another noob bootloop thread :p

Hello fellow captivate users, I need some help here!
I've just brought a 'bricked' at&t captivate off of trademe here in NZ (it's like ebay) and I'm having a little trouble recovering it.
With the help of a homemade JIG I was able to force DOWNLOAD mode, and have tried using ODIN to flash various all-in-one firmwares. However, it seems no matter which I use the phone always ends up in some sort of bootloop, either with just the at&t logo looping, the at&t plus either a samsung s i897 or i9000 screen looping or just the samsung screen looping (depending on one-click used).
So far I've tried these oneclicks-
I897UCJF6 with bootloaders
I897UCKK4 with bootloaders
Plus various other packages that use odin to flash the different parts of the filesystem etc...
I've also used different ports and cables on the computer (although download mode and connection to pc do not SEEM to be a problem)
I'm sure I'm missing something here, but I'm also sure I'm following each firmwares instructions to the 'T'!
I've flashed other android devices in the past with no issues, is there something the samsung requires that I'm missing or messing up? (It's probably the latter )
Any help would be greatly appreciated
Cheers XDA Gurus

I have had success using Heimdall when stuck in a boot loop before. It will change the drivers on your computer so you will have to deal with that (Odin won't recognize them) but this can be dealt with. Apex even has a Heimdall package that will put cwm on your computer.

ok well you HAVE gingerbread bootloaders... STOP FLASHING BOOTLOADERS. gingerbread bootloaders are good with any captivate rom. no need to flash again.
odin likes to lock up. if odin locks up durring bootloaders... well its the only REAL way to permanently brick a cappy... until you unbrick it..
do you need the jig? is the button combo not working? both volume + plug in usb to PC
if odin is seeing the phone (turning yellow) and "PASS" ing the flash(turning green) then you dont have usb port or cable problems.
but try this KK4 gingerbread heimdall package, with re-partitioning.
http://forum.xda-developers.com/showthread.php?t=1386924
heimdall is like odin but open source (more features and more stable), but it uses different drivers that it will install itself, but that usb port will be your heimdall port, all others will work with odin, unless you install the heimdall drivers on other ports too.
or...
try flashing a custom rom using the guide in my sig. it will quickly give you a custom kernel with cwm recovery, you can mount usb to pc from recovery menu, then transfer a rom to flash.
give that a shot...

Wow, quick replies guys, thanks.
I have had success using Heimdall when stuck in a boot loop before. It will change the drivers on your computer so you will have to deal with that (Odin won't recognize them) but this can be dealt with
Click to expand...
Click to collapse
I should have mentioned - I did try one Heimdall oneclick, but had same bootloop result.
ok well you HAVE gingerbread bootloaders... STOP FLASHING BOOTLOADERS. gingerbread bootloaders are good with any captivate rom. no need to flash again.
Click to expand...
Click to collapse
I figured that, just wanted to make sure the bootloaders weren't at fault - I'll make sure I use the non-bootloader oneclicks from now on.
do you need the jig? is the button combo not working? both volume + plug in usb to PC
Click to expand...
Click to collapse
Originally the jig was needed (the phone arrived bootlooping at&t with no button combos working). But since my original stock flash (I897UCJF6) this hasn't been needed.
if odin is seeing the phone (turning yellow) and "PASS" ing the flash(turning green) then you dont have usb port or cable problems.
Click to expand...
Click to collapse
Cool, so cable/ports are ok
Code:
but try this KK4 gingerbread heimdall package, with re-partitioning.
http://forum.xda-developers.com/show....php?t=1386924
Thanks, I'll give this a shot first. If no go I'll try using the cwm method from your sig. How does the sd need to be formated/partitioned for captivate - guess I'll just use a single fat32 parition to start.
To sum up, now that I've got stock GB bootloaders, I'll quit using oneclicks with bl's included. USB cables and ports are fine. I'll try the KK4 heimdall package that was linked, if still no go I'll flash a custom rom and use clockwork to install changes from then on.
Thanks again

I must be messing up - having trouble getting into recovery.
Here's what I did;
The links here: http://forum.xda-developers.com/showthread.php?t=1386924 are dead, so I went straight to method 2.
Downloaded speedmod kernel from here: http://forum.xda-developers.com/attachment.php?attachmentid=566807&d=1302623831
Used odin to flash (kernel selected under pda), this seems to have worked as I now have the samsung i897 screen show up after the at&t. BUT when I try to enter recovery via three button method I get nothing.
How long should I hold the 3 buttons down for? (How many bootloops?)
Should I let go of them at th at&t splash, the samsung s i897 splash or at the blank screen?
All of this was done after my last odin oneclick attempt (which was a KK4, re-part, bootloaders included flash from here on xda)
**edit
I've also tried using the heimdall package (i897-Speedmod-K13E-GBbootloaders-One-Click.jar) to install the kernel with no luck getting into recovery.

For button combo to get into recovery--release when u see 1st att screen.
Or
Have u tried Adb (Android Debug Bridge) to get into recovery ??
Sent by XDA Premium App

cant adb... bootlooping.. or ... does adb work durring boot? no .. right? never tried, cant now...

Yep, no adb on bootloop. Still no joy getting into recovery - it's a stubborn wee device! Gona try some different kernels today.
Am I right that there's no kernels available that will boot straight to cwm without button combos? (I'm thinking my power button may be iffy coz I have no problems getting into download mode)
Sent from my FUSIONideos using XDA

TRusselo said:
cant adb... bootlooping.. or ... does adb work durring boot? no .. right? never tried, cant now...
Click to expand...
Click to collapse
I've used adb during a loop plenty of times..on a couple devices.
My captivate, and my gf incredible.
Its pretty handy, you can push a framework-res you are messing with without having to make a zip, and if you broke it and it loops, you can push the original back, reboot and you're back in business

*removed double post

studacris said:
I've used adb during a loop plenty of times..on a couple devices.
My captivate, and my gf incredible.
Click to expand...
Click to collapse
How exactly? adb doesn't see the captivate because it's only connected for a second before it reboots,adb just tells me device not found or something to that affect.

You have to hit enter at the Right moment, it takes practice

Lol, lucky I've got plenty of patience then!
Strangely if I 1-click back to stock eclair (maybe froyo not in front of PC at mo, and I know I shouldn't be messing with bootloaders but ehhh) I am able to get into what I assume is samsungs recovery mode, but I have to hold button combo for maybe 3 or 4 bootloops. Sticky button(s) maybe?
Am I able to use adb from there to get an update.zip to internal sdcard?
How come if the Odin oneclick seems to work I still end up in bootloops? Something not doing its job right? Partitions not working or kernel or system or bootloaders? Looking through adb shell the system looks intact-but still looping away!
Also am I right in assuming that because it gets to download mode it is eventually fixable?
Sent from my FUSIONideos using XDA

Just an update - from the stock eclair recovery I'm unable to push to the internal SD, get a permission error. Unable to remount that either, comes back with a fairly generic remount not allowed error.
Looking through the forums most people seem to have trouble getting into download mode rather than recovery - doesn't seem any cwm kernel will let me into recovery. Phone is model 1007 if that helps.
Is it possible the internal SD is stuffed? Can't see why all oneclicks end in loop - shouldn't they be overwriting the entire internals?
Gona format a microSD from my tablet and see if that will help, should I leave it fat or use Ubuntu to ext4 it for stock Samsung?
Sent from my FUSIONideos using XDA

If a Internal or External SD card is fried, then no amount of formatting and flashing will help it.

Is there any way to tell if the internal is cooked though? Odin and heimdall both seem happy to flash to the phone, but I've yet to find a package that doesn't end with a bootloop.
There must be some hardware issue though, seems unusual that aside from stock eclair I'm unable to enter recovery. According to the guy I got it from, it simply died while he attempted to update firmware, but the fact that I'm able to flash from download mode would suggest that's not the issue.
I guess there's no way to tell if hardware is cooked other than to send to samsung, is it common for people to get stuck with bootloops from stock flashes? Should I give up and see what samsung would charge to fix (if they will/can) or keep attempting different oneclicks (without bootloaders of course )

How about a non one click?
I've heard some peoples phones bootloop with one clicks, but work fine with .tar packages and the full Odin flashing utility.

Worth a shot. Got to wait a few days for my net to reset though, hit my limit for the month and it's painfully slooow - damn NZ's overpriced adsl!
Sent from my FUSIONideos using XDA

Still not working unfortunately. Using packages with odin3 gets me the same results, bootloops and no access to recovery. I also downloaded the aio captivate package and used the heimdall that came with that to flash stock eclair, which ended with a kernel panic screen - though am able to access recovery. Recovery doesn't see my fat32 microsd though so unable to flash from there.
I don't know my adb shell commands well enough to try and mount or format internal sd and I get permission denied when trying to push update.zip to internal sd via adb.
Unless anyone has any other ideas I'm stumped for now.

When my internal sd got messed up from cognadaian bacon (ooooold dg ROM) i reformated it with my computer and it then let me Load another rom on it... don't remeber if fat 32 or not ....mabey someone else might know
Edit: mabey designgears remembers what fix it when cognadian bacon porked it
Sent from my SGH-I897 using xda premium

Another Brick Verizon Galaxy Tab 7

Hello yall any help would be much appreciated.. Thanks in advance Lexi
I bought a Samsung galaxy tab 7 Verizon branded from someone at my university.
He said he had not idea what was wrong with it.
Symptoms on receipt: Booted through Samsung screen to Verizon screen then looped.
I did some research online and though I could fix it. So I bought it.
I was able to get in the mode with Power + up button screen.
Tried to wipe data, but alot of commands came out: E;/ Failed to mount. And other commands like that
I figured I needed to flash it.
After reading a bunch of posts I downloaded Hemidall and Odin, along with SCi800 Verizon stock .tar and Galaxytab.pit
My first attempt was with Odin, but computer went unresponsive.
After this happened I was no longer able to get to verizon screen. Just samsung and Download mode (power +down button)
I tried again. It just hang when it said writing. On the tablet there was a small blue progress bar but it didnt move for 20-30 mins. So I pulled it out again.
Also note: when I tried to download the USB dirvers as suggested on this forum through hemidal. It was not recognizing my tab.
I got the usb drivers from Samsung website
I know it was recognizing because when I did the Odin it popped up at Com 4 or something like that.
I took a break and put it on the charger to charge.
Now it does not even turn on by itself
It turns on when the power is plugged in from a wall socket but it goes to a all white screen.
I can get into download mode
But when I plug it in the computer USB nothing recognizes it. Not even Odin.
Question 1: what can I use or do for my compute to see my tablet again.
Question 2: If I get my computer to see my tablet again. Can someone show me how to flash from scratch? Meaning redoing partition too? I think that might be bad as well?
Any suggestion guys would be great.. I know a thing or two about computers but really need a bail out on this one.
THANKs

somehow the best platform to launch heimdall is linux.
It doesn't need drivers.
I never run heimdall in Windows. But I think its driver and Odin's are conflicting.
So you may have to uninstall the zadig USB driver and reinstall Samsung's driver to get it working with Odin.
Or get a clean windows machine that never has either software nor Kies in it.
Using XP is also better than Vista/Win7 rather than have to deal with 64 bit and permission control.
The PIT file is to repartition the device storage. So you are on the right track.
Good luck.

priyana said:
somehow the best platform to launch heimdall is linux.
It doesn't need drivers.
I never run heimdall in Windows. But I think its driver and Odin's are conflicting.
So you may have to uninstall the zadig USB driver and reinstall Samsung's driver to get it working with Odin.
Or get a clean windows machine that never has either software nor Kies in it.
Using XP is also better than Vista/Win7 rather than have to deal with 64 bit and permission control.
The PIT file is to repartition the device storage. So you are on the right track.
Good luck.
Click to expand...
Click to collapse
Is it possible its bricked for good?

I let it charge for about 20 mins. and Now it is at least making the windows tone (the tone when you connect a usb device to it)
If I chose to USE Oden again and I want to start from scratch. Meaning fixing everything possible.. Similar to formatting my computer HD and reinstalling everything. Does that mean I have to redo my partition?
Or what else would I have to do?

I tried hemidal
Got this error after loading a stock .tar file and .pit file
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
I see it is connected with Oden v3.07
ID com is
0:[COM4]
Also in device manager it shows Samsung USB composite Device
This means its being seen by my computer right?
I would like to try oden again but I can't find another .tar file and .pit file for my Galaxy tab 7 Verizon
Anyone out there

You can use Sprint one. No difference.
From this post,
http://forum.xda-developers.com/showthread.php?p=42913151
And read the thread
Sent from my GT-N7100 using xda app-developers app

priyana said:
You can use Sprint one. No difference.
From this post,
http://forum.xda-developers.com/showthread.php?p=42913151
And read the thread
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the link. I will search a bit more.
Woke up this morning and the tab is not connecting again. Very frustrating.
I am going to try to run it down again and go from there.
How long should the whole flash process take? I just want to confirm I have enough battery life in it.
thanks again

trinilex said:
Thanks for the link. I will search a bit more.
Woke up this morning and the tab is not connecting again. Very frustrating.
I am going to try to run it down again and go from there.
How long should the whole flash process take? I just want to confirm I have enough battery life in it.
thanks again
Click to expand...
Click to collapse
The SPH-P1000 sprint and the SCH-i800 Verizon are the same?

Update:
Well I was able to get back the verizon and samsung screen.
I used Odin v.3.07
and
verizonEC02.tar.md5
Checked the auto reboot and the F.reset time. Unchecked re-partition
Did not put any file in the PIT section
and I put verizonEC02.tar.md5 in the PDA section
Rebooted but now I am getting this error in the Adnroid System Recovery
IN RED
E: Can't mount /dev/block/mmcblk0p1
(No such file of directory)
E: Can't mount Cache; Reovery/command
#Manual Mode #
E: can't mount /dev/block/mmcblk0p1
(No such file or directory)
E: Can't mount CACHE: log/recovery.log
E: Can't open CACHE: log/recovery.log
E: Can't mount /dev/block/mmcblk0p1
(No such file or directory)
Any ideas on what this mean?

Either the partitions not formatted or the storage chip itself is bad.
Sent from my GT-N7100 using xda app-developers app

;-(
ok so lets say its the partition formating problem.
I re-flashed it again using the same .tar file but this time I used a .pit file.
would that have attempted to format it?
Or do I have to use Nand erase all?
thanks again

Just pit and tick repartition. No need nand erase.
Sent from my GT-N7100 using xda app-developers app

I got it to work!! finally
thanks so much!

How?
trinilex said:
I got it to work!! finally
thanks so much!
Click to expand...
Click to collapse
I have been having the same problem since may! One day my tablet would hang at the Samsung screen! I don't know how many hours I have researched and many different ways I have tried to install the firmware but still get the same thing. It hooks to Odin (every version) passes every install the Roms, the pit, the dbdata, but I still can't get it to work. I've tried on 3 different computers. I don't want to give up because I know it should be fixable. Everyone else seems to be able to fix theirs. I'm on Canada on the Rogers network and got the right files but can't seem to get it right!! Anyone have any other suggestions? I haven't tried to format the SD card and repartition it yet. Not really sure on how to go about that.

Mopsqueezer said:
I have been having the same problem since may! One day my tablet would hang at the Samsung screen! I don't know how many hours I have researched and many different ways I have tried to install the firmware but still get the same thing. It hooks to Odin (every version) passes every install the Roms, the pit, the dbdata, but I still can't get it to work. I've tried on 3 different computers. I don't want to give up because I know it should be fixable. Everyone else seems to be able to fix theirs. I'm on Canada on the Rogers network and got the right files but can't seem to get it right!! Anyone have any other suggestions? I haven't tried to format the SD card and repartition it yet. Not really sure on how to go about that.
Click to expand...
Click to collapse
I thought it was fixed but when I got it back it was in the same condition I gave my cousin.
I did some more research since then. I found a forum about this same error.
As stated in previous posts the error I was getting. Where it said it could not mount the files.
As Priyana said it could either be the partition or the INTERNAL SD Card is bad.
I found a post about this same exact problem (as soon as I find it again I will post in this post)
There is a description on how to open your galaxy tab 7
http://www.ifixit.com/Teardown/Samsung-Galaxy-Tab-Teardown/4103/1
Then remove the internal SD card
Then install the operating system (android) on the external SD card

FIXED
Today I decided to try to partition the external sd card after trying everything for over 2 months now. I only have an 8 gig card at home but I thought what the heck I would give it a try and it worked!! I partitioned it with 3 partitions by watching a video on youtube then i installed the factory roms and overcome kernel with Odin and it worked. I'm a happy camper now!

[Q] Boot loop after attempted re-stocking using Odin

I have a Galaxy Tab 7, T-Mobile version (although I only use wi-fi, not data). I flashed once before using Overcome and it worked perfect, but after my tab started acting crazy - constantly crashing and rebooting - I tried to re-stock and re-flash. I went through the first steps - pit, GB safe stock, T-Mobile modem...and it all went fine, except it was stuck in boot. I tried the hidden pit, which I found in a troubleshoot thread - still stuck in boot.
Then I tried the dbdata.rfs in PDA, which I came across on Fix My IT System...still stuck in boot, and now if I try to load GB safe stock in PDA, I get a fail. Twice I have unplugged in Download, because of Fail and not advancing download...and both times when connect to Odin and load dbdata.rfs in PDA it resets and I can re-enter download mode and recovery<3e>, but it's still stuck in boot.
Is there any hope for me?

If you are restocking and still failing, there is a possibility that your internal nand chip is failing. Also the fact that it suddenly start crashing initially.
There may be ways to run cm rom on external sd that is properly partitioned, if you still want to get some live out of your tab.
Sent from my GT-N7100 using xda app-developers app

priyana said:
If you are restocking and still failing, there is a possibility that your internal nand chip is failing. Also the fact that it suddenly start crashing initially.
There may be ways to run cm rom on external sd that is properly partitioned, if you still want to get some live out of your tab.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
The thought had occurred to me, although I did fix the Odin stock load fail with some further digging (re-loaded USB drivers, plugged cable into different port). Still boot looping...doesn't even boot enough to get adb logcat.
P1 add hidden doesn't help, and makes the next attempt fail, and I have to reload drivers. Same with dbdata.rfs. Although after reflashing dbdata.rfs I can get to recovery<3e> and boot into download. Checksum fails after P1_add_hidden and after dbdata.rfs, but not after USB reload and GB Stock Safe flash. Still stuck at Samsung logo, though.
Is there any way to find out if the chip is my problem for sure, short of tearing the Tab apart?