Database Develop

[Q] Help, phone wont boot no matter what flash

Hi,
I flashed the Pre rooted JP3 from http://forum.xda-developers.com/showthread.php?t=748131 and then installed the [UTIL] One Click Lag Fix 2.0 from http://forum.xda-developers.com/showthread.php?t=751864
I used the phone for a couple of hours and then all of a sudden everything kept crashing.
I booted into the clockwork recovery and reset to factory and then was not able to boot.
I tried flashing back to I9000UGJH2 with Pit512 and Odin and after it flashes successfully the phone starts I see the galaxy S I9000 and then it shows me a grey battery sign and then a busy circle sign and then gray battery and keeps repeating.
When I boot without the usb cable it shows me the Galaxy I9000m sign and then just turns off.
When I tried reflashing the JP3 from the site above and after it finishes it comes to the Android System Recovery <3e> and displays the following message:
Update Media please wait
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E:copy_dbdata_media:Can't mount SDCARD:"
Your storage not prepared yet, please use UI menu for format and reboot actions
copy default media content failed.
When I boot it moves past the Galaxy I9000m screen shows me the galaxy screen with animation and sound, the screen then goes of leaving me with a black screen and the buttons lit.
I cannot format the internal SD card and I cannot seem to get the hone to boot into android, I can boot into downloader.
Any help would be appreciated
P.S. I have ticked the repartition option in Odin

Odin should theoretically work. I've never clicked repartition myself however a lot of people do seem to recommend it.
If you're out of things to try and you want to give the latest (not publicly released) version of Heimdall (my Odin flashing software alternative) a go let me know and I'll PM you the download link.

That gray battery with a spinning circle sounds like the charging screen when the phone is off. Have you tried and let it charge up over night?

The battery is full.
I managed to get the I9000UGJH2 rom up and running by inserting an external sd card.
But here are some issues:
Once booted neither of the SD cards are recognized
If I power down / reboot phone, it will not start again, it shows the I9000m screen and turns off.
I suspect whatever the one click lag did to my SD cards needs to be reversed.

Ok,
So after tonnes of playing around with the device. I can confirm that it has something to do with he internal SD card.
I need to somehow format the entire internal SD card so that even Odin can see it. I tried using the stock recovery and clockworks with no luck.
It just wont see the card.
Any suggestions?

Phone won't reboot ODIN says PASS, Frozen on Galaxy S home screen
I first installed JP2 and was able to get it working. Then I made an attempt to install JP3 but it didn't work. My phone screen kept on flashing i.e. off and on. I then went back and tried to install JP2. While I was installing it, I got an error message saying unable to mount sd card (similar to what rumy got). I am in the exact scenario as rumy and now i don't know what to do. It's a brand new phone and I am very scared.
Any ideas on what I can do now. I am installing JH2 as I write. Hopefully, that will work.
Please help me if someone knows how to get out of this situation.
thanks

galaxys00 said:
I first installed JP2 and was able to get it working. Then I made an attempt to install JP3 but it didn't work. My phone screen kept on flashing i.e. off and on. I then went back and tried to install JP2. While I was installing it, I got an error message saying unable to mount sd card (similar to what rumy got). I am in the exact scenario as rumy and now i don't know what to do. It's a brand new phone and I am very scared.
Any ideas on what I can do now. I am installing JH2 as I write. Hopefully, that will work.
Please help me if someone knows how to get out of this situation.
thanks
Click to expand...
Click to collapse
Well, I am still trying but no luck.
We need an adb expert / odin one to help us somehow repartition the internal sd card I think.
I believe with the lagfix on jp3 it got repartitioned and then corrupted.
I also think we should start adventuring outside this device as there might be more senior trouble shooters / experts who own other htc devices that might be able to help.

I used to get this on my htc dream try going back to original firmware the only I found it to work was rip a rom to pieces get misc.img then enter console via recovery and flash_image misc misc.img then something else but cant seem to remember think its mount-o rw,remount -r yaffs2 /dev/block/mmcblkop3 /system. dont quote me on this try typing the error into google
Sent from my GT-I9000 using XDA App

rumy said:
Well, I am still trying but no luck.
We need an adb expert / odin one to help us somehow repartition the internal sd card I think.
I believe with the lagfix on jp3 it got repartitioned and then corrupted.
I also think we should start adventuring outside this device as there might be more senior trouble shooters / experts who own other htc devices that might be able to help.
Click to expand...
Click to collapse
The lagfixes do not repartition anything so this is (most likely) an issue that is not related to the lagfix.
Try going back to somthing like JF3 with the 513.pit file and repartition enabled.

The exact same thing happened to me - installed JP3 then lagfix. Phone was unstable after so I tried to reflash via ODIN (with repartition) and no matter what I did I could not successfully reflash my phone or get it to boot.
Only solution - returned it to the store as a DOA and got a replacement device.
Upon further research, it is known that JP3 screws up the internal SDCARD. Marks it as read only or something like that - search google for JP3 sdcard for more details.
Bottom line - your phone is bricked. Sorry to be the bearer of bad news.

I wonder if this would help fix it.
http://forum.xda-developers.com/showthread.php?t=762135

rumy said:
I wonder if this would help fix it.
http://forum.xda-developers.com/showthread.php?t=762135
Click to expand...
Click to collapse
That installs a different Linux distro underneath android and is totally unrelated! (Not to mention not doable in the state the phone is in)
OT: I don't believe you should give up quite yet. Try flashing a new firmware and afterwards, install Clockwork recovery!
From there you can format your internal SD. You will lose all your data but I strongly believe it will help fix your problem from what I have read here so far!
Edit: I added a warning to the flash guide in my FAQ for I9000M owners for now!

hey try this
Why dont you try to use the odin 1 click downloader over in the captivate forums. I know that we captivate people are running the i9000 firmware with a stock captivate kernal under it. Worth a try.

ice3186 said:
Why dont you try to use the odin 1 click downloader over in the captivate forums. I know that we captivate people are running the i9000 firmware with a stock captivate kernal under it. Worth a try.
Click to expand...
Click to collapse
I'm not sure what you mean. I am pretty sure he used Odin to flash the firmware. I think you are talking about the same program he already is using.

Damn. There are so many known traps out there, yet we don't have a compile of them anywhere. I didn't know that I shouldn't uninstall Google Talk until I actually did it. We need things like this in the FAQ.

snapper.fishes said:
Damn. There are so many known traps out there, yet we don't have a compile of them anywhere. I didn't know that I shouldn't uninstall Google Talk until I actually did it. We need things like this in the FAQ.
Click to expand...
Click to collapse
"Do not uninstall google talk" is not something you need or want in an faq. It's called a frequently asked questions because they are frequent. I have never before seen someone who tried or even wanted to uninstall google talk (not to mention that this is a goggle os and removing central apps like that is bound to produce problems). And if you mess around with root like that you have only yourself to blame for not doing enough research!
Sent from my GT-I9000 using XDA App

Good idea.
Downloading now will try and post. Fingers Crossed!

OK DONOT TRY THIS!
This made things worse for me.
I lost downloader mode too now all i see is the AT&T screen showing up

Calm down and tell us exactly what you did. It sounds like the initial problems that occurred on early recovery. The download mode should still be reachable. I don't think recovery can completely brick your phone.
rumy said:
OK DONOT TRY THIS!
This made things worse for me.
I lost downloader mode too now all i see is the AT&T screen showing up
Click to expand...
Click to collapse
Sent from my GT-I9000 using XDA App

The problem is related to the message
Update Media please wait
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E:copy_dbdata_media:Can't mount SDCARD:
Your storage not prepared yet, please use UI menu for format and reboot actions
copy default media content failed.​
If you research this error via Google you will find several references to JP3 screwing up the permissions/structure of the internal SDCARD.
I spent several days trying to fix this issue on my phone and no matter what I did (Clockwork or no) I could not get the phone to reset/recognize the SDCARD.
As I said, my only recourse was returning the phone for a replacement. I really hope you find a fix but I think it unlikely.

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

2 i9000's keeps rebooting (softbrick) $20 bounty

Hello,
I have read many threads and have tried many solutions with no avail. I am giving out $20 (may not be much but still an insentive) to whomever that will help me solve this.
I have 2 vibrants that keep booting to the Galaxy S i9000 intro and keeps rebooting there. I can't get into the recovery mode, but I can get into download mode and ODIN works just fine.
Please someone help

trojjanhorse said:
Hello,
I have read many threads and have tried many solutions with no avail. I am giving out $20 (may not be much but still an insentive) to whomever that will help me solve this.
I have 2 vibrants that keep booting to the Galaxy S i9000 intro and keeps rebooting there. I can't get into the recovery mode, but I can get into download mode and ODIN works just fine.
Please someone help
Click to expand...
Click to collapse
Just flash another firmware with Odin.Download a stock firmware,click re partition in odin,load all 3 files and pit and flash it.
You see sometimes after flashing with odin in some cases you might have to do a factory reset to boot the phone,since you cant go in recovery you will need to flash a complete stock firmware.This will probably work.

trojjanhorse said:
Hello,
I have read many threads and have tried many solutions with no avail. I am giving out $20 (may not be much but still an insentive) to whomever that will help me solve this.
I have 2 vibrants that keep booting to the Galaxy S i9000 intro and keeps rebooting there. I can't get into the recovery mode, but I can get into download mode and ODIN works just fine.
Please someone help
Click to expand...
Click to collapse
Follow this guide: http://forum.xda-developers.com/showthread.php?t=853950
and flash this firmware: http://forum.xda-developers.com/showthread.php?t=883568

The people above me pretty much said it.
Go into download mode, connect to odin, download a firmware that will work with your phone, flash your phone. That should fix it.
Best of luck! Tell me how it goes

K. Just came back from bell corporate store. Said I can't do anything without a receipt so until I get a hold of my friend that I bought this off of, I will try what you guys have suggested.
By the way, the gentleman (who seemed very knowledgable) tried flashing my phone on the spot behind the counter and now the phone boots with a black screen and the bottom keys glow when pressed.
When entering recovery mode <3e> and try to format internal sd-card, i get the following:
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
I will now try what you guys have suggested and keep you updated.

tried kewjoe's suggestion but no luck. Any other suggestions?

Time for a replacement - looks like you've got the ever-so-popular internal SD card death.
If you take it into a Bell store they'll send it out and you should get a new one sent back to you in the mail. Bonus if you have any scratches on the phone or anything.

trojjanhorse said:
tried kewjoe's suggestion but no luck. Any other suggestions?
Click to expand...
Click to collapse
Read some of the bell threads that deal with this sdcard issue. Some people went through samsung directly and didn't need a receipt.
Sent from my GT-I9000

trojjanhorse said:
K. Just came back from bell corporate store. Said I can't do anything without a receipt so until I get a hold of my friend that I bought this off of, I will try what you guys have suggested.
By the way, the gentleman (who seemed very knowledgable) tried flashing my phone on the spot behind the counter and now the phone boots with a black screen and the bottom keys glow when pressed.
When entering recovery mode <3e> and try to format internal sd-card, i get the following:
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:copy_dbdata_media:Can't mount SDCARD:
I will now try what you guys have suggested and keep you updated.
Click to expand...
Click to collapse
I've had that problem, shouldn't be too hard to fix.
Flash the Rom JPC with a 512 pit, make sure re-partition is ticked.
Then you can go back the original rom you was on without a pit and without re-partition ticked.
Make sure you do all them steps
Hope this has helped!

trojjanhorse said:
Hello,
I have read many threads and have tried many solutions with no avail. I am giving out $20 (may not be much but still an insentive) to whomever that will help me solve this.
I have 2 vibrants that keep booting to the Galaxy S i9000 intro and keeps rebooting there. I can't get into the recovery mode, but I can get into download mode and ODIN works just fine.
Please someone help
Click to expand...
Click to collapse
I had this issue when flashing from JL2 to another
- some of your partitions got messed, first boot odin, put your phone into download mode and make sure odin see's it. Select JL2 in the PDA secion and click the phone boot loader update
- after it's flashed, find the speedmod from hardcore on xda and flash that, also in the pda part, make sure everything else is default so it's best to close odin and reopen it
- after you have the speed mod on you should be able to get back into recovery.
- almost there, flash the stock 2.1 on your phone this has some data that no other rom has, once you flash that you can flash JL2 over top once again and you should be good to go
- msg me if you have issues

is this issue still on ongoing?
try this (if you haven't tried it before):
1. Launch Odin
2. Put the necessary stock firmware + PIT file that goes with it
3. tick re-partition (not sure what partition you are currently in so that's why I'm suggesting repartition)
4. Go into DL mode and plug the phone in via USB
5. Flash it
6. Once done, go flash hardcore's latest speedmod kernel via Odin again
7. Go to cwm recovery (hardcore's speedmod will give you this)
8. wipe partition cache+factory reset + clear dalvik cache
9. reboot system (will take a several minutes to boot out of the Galaxy S screen)
10. Hopefully your problem is solved.
11. If my method worked for you, PM me. I'll ask you to give that $20 to a local charity of my choice. Street kids needs some love too in the new year

Had this problem yesterday. I wrote in this post how to fix it. Looks like similar advice to what others are telling you.
http://forum.xda-developers.com/showthread.php?t=892534

this will work for sure..
download jpu from here http://hotfile.com/dl/88094739/f5545cc/I9000XXJPU.exe.html
after self extract
put the phone on download mode
open odin
select the files (pda, csc, pit )
check repartation , reboot , reset time

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] Problem flashing from USB Key

Dear All,
I need some help!
I had a weird issue with my tab over the weekend where it would boot to the upgrading dialog, but would only say application 1 of 1, rather than the usual 50+. This would run for hours, so I decided just to reflash the os again without a clean wipe. I imagine this may have been a bad idea. So, I went into CWM and went to flash again, but the tablet crashed just as it started the flashing process, which was bad enough. However, when I went back into CWM, I remembered Nandroid backup and I hoped I had made one! However, rather than hit recover, I selected store (clicked without thinking), which was the cherry on the top of my day of major you-know-whats.
So, the .zip (I think it is v10.1) appears to be corrupt, so I can't flash my original again.
I can't boot the OS to transfer over a new .zip (10.2 would be nice) as I normally would, as I can't start Android at all.
Putting the files on a FAT-formatted USB key isn't recognised by CWM. Trying to mount usb storage gave an error regarding lun path.
So, my questions are:
1) Is there a way to transfer an image onto the internal storage of my tab via CWM, or get it to recognise the USB storage?
2) What are my other options, if 1) isn't possible.
3) If 2) is answered in the negative, have I just made myself a fancy coaster and a good excuse to get a LG G-Pad?
Thanks for your help!

If you can boot to download mode you can use ODIN to flash a rom.

upconvert said:
If you can boot to download mode you can use ODIN to flash a rom.
Click to expand...
Click to collapse
Hi upconvert,
Thanks for the suggestion.
I can get to download mode and I did try to flash a stock ROM from a hotfiles link provided elsewhere on this site last night. However, at NAND Write Start I get three errors on my tablet: WritePartition, DownloadPartition_odin, and Tegra_Nand_Write. I'm not sure what they mean (google didn't reveal any added info). I'm assuming it means the flash storage is either write-protected or can't be found?
I'm going to try and download the ROM again in case it was corrupted somehow. I will retry in the meantime but after I've wiped it again. Any other suggestions would be helpful.
Thanks

Ok, I was able to wipe /data, but it seems to be hanging when trying to wipe /cache. I'd expect it to be finishing in a few seconds, but this is going for minutes.
shcassacazz said:
Hi upconvert,
Thanks for the suggestion.
I can get to download mode and I did try to flash a stock ROM from a hotfiles link provided elsewhere on this site last night. However, at NAND Write Start I get three errors on my tablet: WritePartition, DownloadPartition_odin, and Tegra_Nand_Write. I'm not sure what they mean (google didn't reveal any added info). I'm assuming it means the flash storage is either write-protected or can't be found?
I'm going to try and download the ROM again in case it was corrupted somehow. I will retry in the meantime but after I've wiped it again. Any other suggestions would be helpful.
Thanks
Click to expand...
Click to collapse

So, I've not been able to get anywhere with this. I also can't download a new odin tarball after what happened to hotfile. Anyone got any suggestions as to why the nand write errors are happening? Has the storage drive actually died on the tablet?
shcassacazz said:
Ok, I was able to wipe /data, but it seems to be hanging when trying to wipe /cache. I'd expect it to be finishing in a few seconds, but this is going for minutes.
Click to expand...
Click to collapse

shcassacazz said:
So, I've not been able to get anywhere with this. I also can't download a new odin tarball after what happened to hotfile. Anyone got any suggestions as to why the nand write errors are happening? Has the storage drive actually died on the tablet?
Click to expand...
Click to collapse
Have you tried to format your sdcard from CWM?, cuz formatting it might let the nand write errors disappear
I didn't follow everything you said so I don't know if you've tried the adb files push through USB or not
so if computer can recognise your device through adb try this METHOD
Oh and by the way, SAMMobile website has a new mirror website, so now you can download Odin tar files again
Directly Here is the latest FW for P7300 , and if you're more comfortable with dev-host mirror than Here you go (the two files are the same latest release)
and Here is the the latest FW for P7310, I don't have any other mirrors for that

Hi,
Thanks for the reply. I can't even get access to CWM anymore. Goes straight to Odin download mode after the Samsung splash screen. Unfortunately, I found another post on XDA that seems to explain my problem:
http://forum.xda-developers.com/showthread.php?t=1532636&page=3
I think the HDD has died completely, as I am getting exactly what that chap was getting. I can't install a PIT file. I couldn't access my sdcard from CWM previously either. Sounds like tablet is a goner. Will post to Samsung and see what they say.
Thanks for your time.
omarainea said:
Have you tried to format your sdcard from CWM?, cuz formatting it might let the nand write errors disappear
I didn't follow everything you said so I don't know if you've tried the adb files push through USB or not
so if computer can recognise your device through adb try this METHOD
Oh and by the way, SAMMobile website has a new mirror website, so now you can download Odin tar files again
Directly Here is the latest FW for P7300 , and if you're more comfortable with dev-host mirror than Here you go (the two files are the same latest release)
and Here is the the latest FW for P7310, I don't have any other mirrors for that
Click to expand...
Click to collapse

Tab repaired by Samsung
Ok, eventually sent my tab off to Samsung for warranty repair. Received it back and working fine now. Not sure what they did in the end, but got my tab back at least. Thanks for everyone's help.
This thread can be closed.
shcassacazz said:
Hi,
Thanks for the reply. I can't even get access to CWM anymore. Goes straight to Odin download mode after the Samsung splash screen. Unfortunately, I found another post on XDA that seems to explain my problem:
http://forum.xda-developers.com/showthread.php?t=1532636&page=3
I think the HDD has died completely, as I am getting exactly what that chap was getting. I can't install a PIT file. I couldn't access my sdcard from CWM previously either. Sounds like tablet is a goner. Will post to Samsung and see what they say.
Thanks for your time.
Click to expand...
Click to collapse