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!
Related
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.
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 :/
I'm certainly hoping for help, but also to serve as a warning...
I pulled a noob move and tried to install the Gingerbread 2.3.3 update. I was using Odin3 1.7 and everything SEEMED to go correctly. When I got to the point where I was supposed to wipe the cache and reset data, I got error messages saying "unable to mount /ext filesystem. Bizarre.
At any rate, I tried to flash back to both DJ30 and EA24. My Sprint Galaxy Tab is a brick now. I can still get into the download screen, so hopefully all is not lost. I've tried Odin 1.3, 1.7 and (I think) 1.83. I also found an EA24 flasher on one of the XDA forums but always get "Cannot open binary file!" It appears that it's looking for the .tar file to be in a specific location. I've tried c:\ c:\Program Files c:\Program Files (x86) -- nothing works.
If I had to make a guess (and again, noob move) I don't know how to completely wipe the partition clean and repartion, flash EA24, etc.
I've seen tons of commentary on non-Sprint Galaxy Tabs. Can anyone help with a US Sprint Galaxy Tab?
There is another EA24 flasher for Odin from the same thread as the "can't open binary" version. It worked for me... I wasn't bricked but had lost my camera function.
Failed...
This didn't work. I get the attached error.
Can you tell me which directory you installed this to, and, if you had any command-line arguments?
I got that same error that's why I used the Odin version I linked in my previous post. Download the zip file, read the text file instructions on how to flash the image and you should be good to go.
I did that...
I did that. It fails.
It gets to the "recovery.bin" file, and then fails. Give me a minute and I'll post a reply with the screen shot...
When I use ODIN3 1.7
This is what I get when I use Odin... It simply fails...
Hmm, I'm too much of a noob to know why it would fail.
Maybe you could post in the thread with the flasher and for more input.
I would but.. That post is now "suspended." The guy who wrote it has a Xoom now and couldn't care less about the Sprint Tab. Just my luck, right?
The thread is still open. You might be thinking of another thread.
I think you're right. I'm thinking of the Zypher thread.
At any rate, regardless of whatever firmware I try to flash, it either fails outright, or, it hangs at the Samsung Logo. *Nothing* seems to be working.
Defeated...
I have agreed to send in my Sprint Galaxy Tab.
I have failed.
XDA has failed.
Just sayin'.
Use the gui version of heimdall. Just launch heimdall, then put your tab in download mode and plug it into your pc. Once plugged in, launch the heimdall driver.exe and go to one of the drop down menus and click list all devices. You should see a gadget serial appear. Select it and force install the driver. Then load your pit file and every other file you can in the fields. You need to find the original stock package (usually a .tar or .md5), then extract the .rfs and and .bins in their correct location. And click start. For some reason cdma devices seem harder to flash than GSM. If after it runs, it still doesnt work, reload all the files again except the pit, boot.bin, sbl.bin. I had the same mounting error flashing a verizon fascinate, and i battled with it for a solid day and a half. If you can get into download mode then you are golden.
Dont give up.
For some reason i dont think odin like CDMA. It always fails me everytime.
If you download a .tar.md5 file, just rename it .tar and extract the contents. You need to google and download a .tar archieve utility (there are tons of free ones).
Jonathan
Sent from my GT-P1000 using XDA Premium App
I have a Sprint CDMA Tab and Odin worked for me. I've also Heimdall with success. It seems results may vary depending on what combination of stuff is on the Tab.
Heimdall
I'm trying these now per your advice. They at least finish and I don't get the write errors when flashing using Heimdall. So far, the best that happens is I get to the Samsung Logo screen, and nothing -- no glowing blue, no startup sounds.
Interestingly enough, all of the Zypher stuff that was posted before (without modem, with Epic modem, etc) -- None of those ROMs had boot.bin or sbl.bin in them. So, it looks like all the DJ30 stuff I have can't really flash back to DJ30, correct?
If I repartitioned, wouldn't that stuff get blown away and need to be put back?
All failed...
I was able to get Heimdall up and running and seemed to successfully complete with multiple ROMs (DJ30, EA24, and the Gingerbread ROM floating around.) None successfully boot the Tab, however. I get to the Samsung screen, no glowing blue...
I definitely did a number on this! hahah. Oh well. Live and learn, I suppose.
I got my Galaxy back from Samsung... only took about 10 days but! I'm back in business! Woot!
Sent from my MB860 using Tapatalk
Hi everybody,
I've been at this for a couple days now, trying every solution I can come across, but nothing seems to work. My mom's Captivate decided the other day that encryption had failed (I don't think anyone ever told it to encrypt itself...). It said all I had to do was click the Reset button, but that didn't work. So back to ODIN I went.
Unfortunately, though I could swear I've used ODIN on this phone before (it was running CM10, and I'm pretty sure I messed up a couple times trying to get it on there), I can't get it to work again. I've tried the One-Click ODIN (which is what I would have used before), as well as downloading two different tar.md5s from sammobile.com and flashing them with a different ODIN.
After using the One-Click method, the phone powers on to the AT&T screen, and then it powers off, switching between different charging icons if it's plugged in. The other ODIN flashes got me to Installing packages.. after boot, but then it gave me rfs errors. So I figured I needed to flash a new PIT, but that didn't seem to help. Doesn't One-Click do that anyway?
I've tried two different USB cables and two computers (both Windows 7 SP1, one doesn't even have any antivirus program on it yet), but no luck. I had a different computer the last time I would have used ODIN on this phone. I believe this phone is a 1007 build, assuming I am looking at the right number under the battery.
Any help would be greatly appreciated. Thanks in advance!
see encryption unsuccessful thread. your internal storage is probably dead, but you can run from external sdcard with the fix described in the thread.
http://forum.xda-developers.com/showthread.php?p=21439417
Sent via Monty Pythons Flying Circus
Yeah, that's the problem
Darn. Seems like that is the problem. Simply putting in an external SD card allowed me to boot, but now I have to get CWM on it through ODIN... Thanks.
CWM via ODIN?
Does anyone know how to install CWM through ODIN? I'm back with the stock recovery, and when I try to install a ZIP it fails the signature verification (for any ZIP I try). Seems that ODIN would be the way to go.
Stock recovery won't let ya flash zip files that r not signed by samsung.
Ya have to have the zImage in a .tar file in order to flash it through Odin.
Here is the KK4 Corn Kernel thread. http://forum.xda-developers.com/showthread.php?p=18233847
I recommend the version 7.0A for what u r wanting. There is a .tar version of it there. PDA slot is the one to use in Odin for flashin a kernel.
Sent from my SAMSUNG-SGH-I747 using xda premium
Running CornKernel, repartition error
OK, I'm up and running with CornKernel. I rooted it using the ZIP (and now the phone is unbelievably slow, but it's rooted nonetheless). (I also tried the advanced CWM option to root it, but that messes the phone up.) But when I try to repartition the SD card, it says "An error occured while partitioning your SD Card. Please see /tmp/recovery.log for more details." but /tmp is empty.
Getting rid of the phone
Meh, forget about it. I'm going to sell this phone as-is or part out anything I can. I need to move on, as spending more time on this phone when it's permanently damaged is not worth it to me. (If anyone wants it by chance, just let me know...) Thanks for pointing me to what the problem was though.
...necro bump... You wouldn't still happen to be selling that would ya?
Sent from my GT-I9000 using XDA Premium 4 mobile app
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