Related
Hello - It seems as though everyone is somewhat nice and knowledgeable on this board. I'm hoping that no one flogs me in the process of this thread.
I have a T-based Galaxy Tab and am trying to load a new ROM onto it. I've tried multiple times with multiple different ROMs but am not making really any progress. When I plug in the device to a wall outlet, the attached screen is displayed. This is the first time that I've seen this screen and I'm now hoping that this thing isn't bricked. Please help me bring this Tab back from the dark side.
I need to know which ROM to use and the appropriate PIT file. I also need to just understand how I get the device to be recognized by Odin again as it's not being recognized in it's current state. Thanks to all that will help me.
Jim
hi,
can you tell me which firmware files are you using to flash and the PIT files?
Yes. I used the below files. I know it's the European version but it looked as though it was for TMobile. And I'm somewhat desperate to get this fixed.
PIT - P1_EUR.pit
PDA - P1000BOJJ2-REV03-ALL-CL618963.tar
MODEM - MODEM_P1000XXJID.tar
CSC - GT-P1000-CSC-DTMJJ4.tar
Downloaded them from samfirmware.com/samsungtablets.htm
Jim
jimcansler said:
Yes. I used the below files. I know it's the European version but it looked as though it was for TMobile. And I'm somewhat desperate to get this fixed.
PIT - P1_EUR.pit
PDA - P1000BOJJ2-REV03-ALL-CL618963.tar
MODEM - MODEM_P1000XXJID.tar
CSC - GT-P1000-CSC-DTMJJ4.tar
Downloaded them from samfirmware.com/samsungtablets.htm
Jim
Click to expand...
Click to collapse
i guess the issue is due to the incompatible firmware and a different partitioning file (PIT)
may be you can try installing JHA firmware with repartition, PIT file and then install JID directly without repartition and PIT
Not wanting to be pessimistic here but after browsing the Galaxy S section I came across a thread with that image on your tab. You may have to contact Samsung and have the device replaced. http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series#Recovery_Mode
Storm, Chow,
I think you may be right. I followed the instructions that Chow gave me and it failed. See attached. I still have the Tab attached to my pc and it still has the same image as original. I've attached my Odin screen so you guys can look at it and tell me if I'm doing anything wrong.
Jim
Hi,
I had that image many times, whenever my tab fails to install any new firmware.
did you reboot the tab after seeing that image
one more try:
after seeing the flash fail > hold the three button combination (power + volume down + home) for long time (may be more than 1 minute) until the tab is switched off and then use three button combination (power + volume down + home) to enter the download mode (you will still see the above image only). now connect the tab to odin and try flashing it.
if i remember correctly, my tab was connected to COM 8 when flashing but i think its USB port selection
this is how i recover my tab to working mode whenever a flash fails
Have you tried with Odin 1.31 with PIT 816 and JHA.tar selecting repartition?In the pic you are using the 1.71, right? I had something similar going back to JID from JJ4 and when I tried with the 1.31 it passed, cant be sure it wasnt just 'the one more try' or the old Odin but it worked.
Good luck
Sent from my GT-P1000 using Tapatalk
I used the Odin 1.3 per your instructions and used th 816 PIT with the JHA tar. This passed as you can see from the attached. This has worked and I now have a working unit that needs to charge up. I'm a little nervous to now install the JID firmware and will likely just try to keep what I've got working. If I do want to install the JID firmware...will I need another PIT file or can I just use the JID firmware and write over? In addition, would i need to select or unselect the re-partition check box.
Thank you guys so much. It appears as though my unit is working.
Jim
jimcansler said:
I used the Odin 1.3 per your instructions and used th 816 PIT with the JHA tar. This passed as you can see from the attached. This has worked and I now have a working unit that needs to charge up. I'm a little nervous to now install the JID firmware and will likely just try to keep what I've got working. If I do want to install the JID firmware...will I need another PIT file or can I just use the JID firmware and write over? In addition, would i need to select or unselect the re-partition check box.
Thank you guys so much. It appears as though my unit is working.
Jim
Click to expand...
Click to collapse
just install the JID without use any pit and do not select re- partition, keep using the 1. 31
Sent from my HTC Desire using Tapatalk
chowdarygm said:
i guess the issue is due to the incompatible firmware and a different partitioning file (PIT)
may be you can try installing JHA firmware with repartition, PIT file and then install JID directly without repartition and PIT
Click to expand...
Click to collapse
I quote.
I had that bad image on the screen for some time... If you connect to the PC you should find the TAB as connected in ODIN. If you flash JHA repartioning with the correct PIT, that for me was 9 and something if I remember, you should restore normal functionality. Try and let me know!
Can confirm.
Had this image several times while testing var firmwares.
Simply connect tab to odin and flash jha image with repartition.
This should fix it.
Sent from my GT-P1000 using XDA App
Guys, I think that he solved the problem using Odin 1.31.He already install the JHA and the unit is working.Pls stop posting without read.The issue can be related with the new Odin.Now he is concerning to install JID over a working unit...
MODEM file
Greetings,
Where did you guys get your MODEM file from? I only can see the PDA and CSC files on the samfirmwares.com site... :S
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
Hello guys,
Yes... I'm a total noob, I tried to root my phone with the wrong files and ended up bricking my phone.
My reason to root: wanted to be able to use the emulators / controllers on the market. If only I knew this was going to happen
On my attempt to reverse the situation, I did it... my phone stopped booting completely.
I figured since my phone does go onto downloading mode still, that I'd be able to return it back to normal once I educated myself a bit on the processes of flashing androids.
I have tried to find a thread similar to mine, and I have been unsuccessful to the point of utter frustration (I even considered going and getting a new phone).
Then I came across AllGamer's thread:
http://forum.xda-developers.com/showthread.php?t=1379650
I thought my search (of 8 hours by then) was done, that everything would be back to normal.
But somehow I have been unsuccessful to mimic his results on flashing the phone back to Stock.
I'm probably wrong assuming that the bootable files on the phone are missing since my stupid trials at the beginning of it all. Hence why AllGamer's instructions aren't doing it for my phone.
I have a Samsung Galaxy S GT-I9000m
This is my last resource (to which I have no right, but I figured I should try before calling it quits).
Can any of you help me fix my phone?
Did you try flashing using the three files method in ODIN? You need ODIN, a PIT File, and an original ROM that has 3 files (Phone, PDA, CSC) in it. Check the Re-Partition option and your phone should go back to the original rom.
Go to SamMobile dot com to find a Samsung ROM
As long as you have download mode then your phone is still alive.
Go to samfirmware ( or sammobile as it may have changed over now ) and get a zip file for you device which contains 3 files and a pit file.
MAKE SURE YOU GET A FIRMWARE FOR AN I900M NOT A I9000 OR AN I9000T!
Download odin and put the pit file in the pit box.
in PDA box put PDA file or it may be called CODE.
In MODEM put the MODEM file or it may be called PHONE
In the CSC box put the CSC.
make sure that repartition / auto reboot / auto F reset are ticked.
Any other boxes should be unticked.
Put your phone into download mode and connect it to the PC.
MAKE SURE YOU OPEN ODIN AND CLOSE ANY KIES SOFTWARE BEFORE CONNECTING YOUR PHONE!
a yellow box should pop up in odin saying COM XX
press the start button and let odin work its magic and voila! your phone is alive!
Good luck
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
By soft bricked, in my situation, I mean that the only mode I could successfully enter on my SGH-T679 was ODIN download. Recovery and normal boot both locked up no matter how long the phone was allowed to run. Or it reported that firmware failed and to use Kies but Kies failed to recognize the phone.
How I bricked it
I was given one of those fitness wrist bands for Xmas, but it's from a startup company and their app only works in 4.3 or higher. So I got adventurous and tried CM 10.2. I got CM to run but couldn't get Google services to work. I finally gave up and started to revert to stock. When I had my first problem at 2am, I should have gone to bed and finished after a good night's sleep because I soft bricked it. At first, I was running flashes from my internal SD card and could only get it to flip between stock recovery and CWM recovery, it wouldn't take full stock flash. Finally, one CWM recovery flash failed and my recovery mode got stuck so it only showed the hat and gear icon and at the bottom of the screen it said "CWM 6.etc..." and never went further. But I could still get to ODIN download mode.
And that's when I got really stupid. I messed with things I didn't understand in ODIN. Did you know that if you try to run ODIN Multidownloader 4.43 using the "Debug Only" and "MD5 Ram Check" options that you can fully soft brick a T679? If allowed to run for a while (10-20 minutes is sufficient), then after forcing the phone to restart, it will result in the screen about firmware failed please use Kies for recovery (but then Kies can't see the phone because the recovery is bricked).
Long story short, after hours of trying this and that, I finally found a webpage that said you can download the CWM recovery via ODIN. That would have worked if I hadn't gotten the wrong version (resulting in lots of screen flickering), but it proved to me that I might be able to fix the recovery using ODIN.
Here's the walk thru of how I restored my stock recovery and ultimately got back to stock ROM:
Software required:
A zip software that can handle TAR files (I used PeaZip)
Go to this wiki http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G and scroll down to "Flash to stock via ODIN", you need the software discussed and read thru the "STEPS" section just below that
You can first try using ODIN as described in the wiki. But if that doesn't work, you can try what I did...
Restoring stock recovery
If you haven't already, unzip the uvlg3.odin.zip file that you got via the wiki link above
From the .tar file that was in the zip, extract recovery.img and then put it inside a new TAR file (call it something easy like recovery.tar) (depending on your zip program, use "add", do not use "convert", you need the .img file inside the .tar file)
Refer to the wiki link above for more help on ODIN but basic steps are:
- Run ODIN as admin (not sure if it matters if you disable auto-protect on your antivirus software but I followed that recommendation)
- Using "OPS" button, select the Ancora.ops file that you extracted from the zip file
- You may have to recheck the "One Package" box to be able to then select your recovery.tar using "One Package" button
- Press "Start" and cross your fingers
You hopefully have now restored the stock recovery to your phone.
Further steps
I went a step further. I extracted the entire .tar file (not just the recovery image) and put each item into its own new .tar file. I used ODIN to individually load each item. I did first try to load the full file but I now think mine was failing to load system (which is pretty critical, especially if you followed directions that included "format /system"). (Note, the preload file might not work, didn't for me ; I found several posts about it and the general answer was to ignore it.) One trick to this is to watch and push the Vol Down and Home buttons when ODIN reboots the phone so you go back into download mode. Oh, and change the reset time to 30 seconds (I tried 1 but ODIN changed it to 30) so you don't wait as long on "reset". I'm not sure if it would have made my first normal boot go faster if I'd gone to recovery mode between ODIN downloads. I do know it took my phone several minutes on the first normal boot. I'm sure those of you who have bricked phones can appreciate the feeling of waiting for the stupid startup jingle and the relief when it actually plays.
Oh, and save yourself some bother by rebooting 2 or 3 times before you try to do much w/ your phone once you get back to stock ROM (or some other ROM). I was a little freaked because my wifi didn't work but after some googling, I learned Android can require a couple reboots before all services (especially wifi) load properly (which makes me wonder if I should try CM 10.2 again with more reboots... am I a glutton for punishment enough to try???).