Hi forum,
I'm having big problems with my galaxy tab 10.1 p7510. I was transferring files from my pc to the tab, the tab stop responding, I pulled the usb cable (big mistake). After that the tab wouldn't boot. Went into android recovery and wiped cache, some errors appeared and I wasn't able to turn on the tab for about a day. I held down the power button for a really long time and it went into a boot loop. Was able to get into recovery again, wiped cache again; since then I couldn't get into recovery any longer. But, I have been able to get into download mode. I downloaded the latest ROM (and the one before it) from sammobile.com; tried flashing both using odin 1.83, 1.85, and 1.87. Tried two different computers and various usb ports for each computer. installed drivers and kies, made sure kies was disabled when attempting flash. Result is always the same:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P7510XABLPL_P7510UELPL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I really don't know what else to do.
Should note, when i power off and power on, some red text appears quick (can't see it) and it automatically goes into download mode. At the top it says, "reason no kernel"
Please help!
Jim
focusbob said:
I was transferring files from my pc to the tab, the tab stop responding, I pulled the usb cable (big mistake). After that the tab wouldn't boot.
Click to expand...
Click to collapse
What exactly were you transferring? Were you flashing a new ROM, restoring a backup or adding an update?
No, I was just transferring videos from pc to tab via usb. It froze, but I think it was when I tried to clear cache in android recovery that things went down hill. There are some known problems with factory resets with galaxy tabs due to a faulty chip. Maybe it was that? who knows. I actually was able to get Samsung to take it in on warranty (though it's past warranty). So, that's the end of that...
focusbob said:
I actually was able to get Samsung to take it in on warranty (though it's past warranty). So, that's the end of that...
Click to expand...
Click to collapse
In that case, congratulations and better luck next time.
Related
I have never rooted my phone, always used official updates. Upgraded to Android 4.1.1 last night and after few hours my phone just stuck wiht the "Samsung Galaxy S3 startup logo". The phone wont reboot at all. I tryed to factory reset (volume up + home + power), wont work.. one time it tryed to do something and failed. I can boot to odin download menu and i tryed to reset to official stock firmare and it says something about partition corrupted or broken. After that i tryed again with the new partition option, it failed again. Is there anything i can do to get this phone working again?
aeinola said:
I have never rooted my phone, always used official updates. Upgraded to Android 4.1.1 last night and after few hours my phone just stuck wiht the "Samsung Galaxy S3 startup logo". The phone wont reboot at all. I tryed to factory reset (volume up + home + power), wont work.. one time it tryed to do something and failed. I can boot to odin download menu and i tryed to reset to official stock firmare and it says something about partition corrupted or broken. After that i tryed again with the new partition option, it failed again. Is there anything i can do to get this phone working again?
Click to expand...
Click to collapse
Send it back for repair if you've never routed or anything. It can likely be fixed by routing and whatnot but if you've never done it, why risk it.
Parva4 said:
Send it back for repair if you've never routed or anything. It can likely be fixed by routing and whatnot but if you've never done it, why risk it.
Click to expand...
Click to collapse
Send it for repairs and wait for several weeks to get it back? Very tempting. :cyclops: Lets call that plan B.
If i can do something to wake this baby up today or tomorrow i'll take it.
It sounds like you somehow softbricked your phone without even rooting it lol.
Anyway, if you can go into ODIN download mode, you might wanna try rooting the phone to see if it works. Cos once the phone's rooted, you can easily flash a stock ROM to save it. If you're worried about voiding the warranty, you can unroot the phone after everything's done.
Instructions for unrooting: http://galaxys3root.com/galaxy-s3-unroot/how-to-unroot-galaxy-s3-i9300/
Hope this helps!
chunghanjie92 said:
IAnyway, if you can go into ODIN download mode, you might wanna try rooting the phone to see if it works. Cos once the phone's rooted, you can easily flash a stock ROM to save it. If you're worried about voiding the warranty, you can unroot the phone after everything's done.
Click to expand...
Click to collapse
I did try that and it did not work. Maybe i did something wrong? Dont know... Im pretty sure the problem is with broken partition. I had the Auto Reboot, Re-Partition and F. Reset Time checked. Got file for PIT and got file for PDA. It just wont work. Odin says every time FAILED!
Do not use pit or repartition unless you know what you are doing.
jje
Sent from my GT-I9300 using xda premium
aeinola said:
I had the Auto Reboot, Re-Partition and F. Reset Time checked. Got file for PIT and got file for PDA. It just wont work. Odin says every time FAILED!
Click to expand...
Click to collapse
NEVER CHECK RE-PARTITION trololololo .... and never use PIT unless you are know what you doing.
Wow! These "never use PIT unless you are know what you doing"-comments are really helpful. Thank you guys! :good:
Follow the instructions on this site:
http://galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3/
The site tells you how to root a phone (look at the picture to see what you need/don't need to check; usually all you need to check is Auto-Reboot and nothing else)
After the phone's rooted you can download a ROM from this site http://samsung-updates.com/device/?id=GT-I9300 and flash it into the phone using the same method you flashed the file to root your phone
Thanks for the help. Odin says: "There is no PIT partition" and FAILS.
So i NEED to Re-Partition, any help would be appreciated.
I try to Re-Partition and here is what Odin says:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXBLH1_I9300OLBBLH1_I9300DXLH1_ROOT_DEODEX.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The files (including mx.pit) is from these forums. What should i do?
aeinola said:
I try to Re-Partition and here is what Odin says:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9300XXBLH1_I9300OLBBLH1_I9300DXLH1_ROOT_DEODEX.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The files (including mx.pit) is from these forums. What should i do?
Click to expand...
Click to collapse
Same thing for me, and I'm stuck with this problem for 2 months now!!!
I read that for some reason unknown, some S3 got these fuc*** motherboards!!!
If u can solve this without samsung service center, please post!!!:good:
Of course you can manage it without Samsng Service center, if you want.
The procedure is:
1. download to PC the I9300 Service Manual;
2. buy motherboard;
3. replace it by yourself.
GS II i9100
Note: Warranty is already expired
Before I write anything further, I have been trying to get the most I can out of this thread: http://forum.xda-developers.com/showthread.php?t=1457458
Sadly, I can't seem to wrap my head around this problem, so here goes:
Yesterday I've found out, that the new CM11 came out. Of course I went off to download it, put it in my phone and started to install it through recovery (I had siyah at that time). Well, it failed, must've been corrupt or something, since I got the error status 7. Anyways, while exiting the install screen, siyah asked me, if I want to repair something, because something may have gotten corrupt (Sorry, can't remember the exact thing). Being the sloppy person I am, I clicked yes.
Five minutes later, after going back to stock firmware, because apparently during the install something did go corrupt, and the phone wouldn't boot, only play the boot sound, I've read, that I need the newest CWM for CM11 to work.
Another five minutes later I'm staring at this:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-i9100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
I've tried changing computers, kicking KIES out through the window, using different USB slots and cables, but to no avail. It just keeps throwing this error at me every time I try to install anything through Odin. The strangest part is, though, that the phone is working perfectly fine.
What could be the problem, and if it is possible, how do I fix it?
Another quick note would be my counter in the download screen of my SII. It's 12 (yeah, I know, I kept forgetting about it, but now, since I'm unable to install anything through Odin, I can't even root the phone and reset the damn thing)
Don't flash nothing to this phone. Be happy it works or get rid of it while it does still works. Seen this before and this is the first stage of mb failure. Trust me don't flash nothing to this phone and get rid of it. If not start reading about the pit file
andrewwright said:
Don't flash nothing to this phone. Be happy it works or get rid of it while it does still works. Seen this before and this is the first stage of mb failure. Trust me don't flash nothing to this phone and get rid of it. If not start reading about the pit file
Click to expand...
Click to collapse
And apparently, this is now happening:
Baseband version - XXMS2
Build - XWLSS
I think I may have messed it up a little...
Please close the thread
This thread can be closed.
Should anyone need this:
After losing patience spending hours on the phone I have decided to JTAG it... Ant it worked. The phone is running like a charm now.
Hi everyone,
My head is spinning from what's just happened. My phone mysteriously decided to crash on me after being a little slow and unresponsive recently. I'm running CM11 M5 on my phone, I found this is the most stable of the roms for me. The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen, so I tried to reboot into the Cyanogen bootloader thingy and it just brings up the crash screen. I tried to reboot into Odin Mode, hooked up the phone to my computer and tried to reinstall a new ROM. First I tried with Odin 3.07 with a ROM I loaded onto it last month (I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5), but the Odin program on the computer crashes each time. I also tried with an updated version of Odin, v1.85 and also Odin Auto. I had an issue last month, looked around and fixed it by downloading this ROM just mentioned, but this time, no joy. I've tried with another that I just downloaded (root66_TMO_T999UVDLJA.tar.md5) and the same thing happens. At one point, I received a message on different attempts where the Odin program would spit back at me this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1
So, how do I proceed from this point? I don't know enough to understand what the problem is with this, maybe something to do with the PIT mapping? I feel like I've covered every possible avenue that I can see posted online, I'm really not sure if there is anyone else with this problem, where the Odin program is so volatile. Your thoughts would be greatly appreciated, I suffer without my phone.
Stuart
blackbeardtwenty said:
Hi everyone,
My head is spinning from what's just happened. My phone mysteriously decided to crash on me after being a little slow and unresponsive recently. I'm running CM11 M5 on my phone, I found this is the most stable of the roms for me. The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen, so I tried to reboot into the Cyanogen bootloader thingy and it just brings up the crash screen. I tried to reboot into Odin Mode, hooked up the phone to my computer and tried to reinstall a new ROM. First I tried with Odin 3.07 with a ROM I loaded onto it last month (I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5), but the Odin program on the computer crashes each time. I also tried with an updated version of Odin, v1.85 and also Odin Auto. I had an issue last month, looked around and fixed it by downloading this ROM just mentioned, but this time, no joy. I've tried with another that I just downloaded (root66_TMO_T999UVDLJA.tar.md5) and the same thing happens. At one point, I received a message on different attempts where the Odin program would spit back at me this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1
So, how do I proceed from this point? I don't know enough to understand what the problem is with this, maybe something to do with the PIT mapping? I feel like I've covered every possible avenue that I can see posted online, I'm really not sure if there is anyone else with this problem, where the Odin program is so volatile. Your thoughts would be greatly appreciated, I suffer without my phone.
Stuart
Click to expand...
Click to collapse
Use this if it fails it needs service repair >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 <<
blackbeardtwenty said:
Hi everyone,
My head is spinning from what's just happened. My phone mysteriously decided to crash on me after being a little slow and unresponsive recently. I'm running CM11 M5 on my phone, I found this is the most stable of the roms for me. The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen, so I tried to reboot into the Cyanogen bootloader thingy and it just brings up the crash screen. I tried to reboot into Odin Mode, hooked up the phone to my computer and tried to reinstall a new ROM. First I tried with Odin 3.07 with a ROM I loaded onto it last month (I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5), but the Odin program on the computer crashes each time. I also tried with an updated version of Odin, v1.85 and also Odin Auto. I had an issue last month, looked around and fixed it by downloading this ROM just mentioned, but this time, no joy. I've tried with another that I just downloaded (root66_TMO_T999UVDLJA.tar.md5) and the same thing happens. At one point, I received a message on different attempts where the Odin program would spit back at me this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_TMO_T999UVDLJA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1
So, how do I proceed from this point? I don't know enough to understand what the problem is with this, maybe something to do with the PIT mapping? I feel like I've covered every possible avenue that I can see posted online, I'm really not sure if there is anyone else with this problem, where the Odin program is so volatile. Your thoughts would be greatly appreciated, I suffer without my phone.
Stuart
Click to expand...
Click to collapse
Happened the same too me and i have CM11 too... If you get a fix contact me please
emnt said:
Happened the same too me and i have CM11 too... If you get a fix contact me please
Click to expand...
Click to collapse
Try the above rescue firmware as suggested above make sure you know what you are doing before flashing.. Exactly same advice if that doesn't work service required partition corrupt..Also I noticed the op above also flashed wrong root file for I9300 which didn't help.
blackbeardtwenty said:
The unusual thing about this crash was that it rebooted with a fuzzy, static-like screen,
Click to expand...
Click to collapse
Hardware issue, either damaged or corrupt emmc chip.
tallman43 said:
.Also I noticed the op above also flashed wrong root file for I9300 which didn't help.
Click to expand...
Click to collapse
Yeah, that was a desperate attempt at trying another root file which was recommended in another post. I initially used:
I9300XXUGNA5_I9300AUTGNA1_I9300XXUGMK6_HOME.tar.md5
and this worked fine last month, but now I'm back to square one again. Any ideas on other PIT files or root files I can download which might do the trick?
Thanks for your comments so far, you're all a bunch of wizards...
So I unfortunately bricked my galaxy S4, but I am having issues unbricking it. I downloaded the full wipe and PIT file from http://forum.xda-developers.com/showthread.php?t=2735172 , installed the samsung drivers, booted into download mode, and set up both files, but whenever I hit start this occurs.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
I have tried installing and uninstalling the drivers, and tried different USB ports. However, everytime I plug it in, it installs drivers even though they are already installed, Am I doing something wrong? I am not unplugging the phone in the middle of it at all, so I dont know why there is the Removed and Added at the end, even though the device is still plugged in and in download mode when both pop up. I need my phone to be usable soon so help is GREATLY appreciated.
Endstepper said:
So I unfortunately bricked my galaxy S4, but I am having issues unbricking it. I downloaded the full wipe and PIT file from http://forum.xda-developers.com/showthread.php?t=2735172 , installed the samsung drivers, booted into download mode, and set up both files, but whenever I hit start this occurs.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
I have tried installing and uninstalling the drivers, and tried different USB ports. However, everytime I plug it in, it installs drivers even though they are already installed, Am I doing something wrong? I am not unplugging the phone in the middle of it at all, so I dont know why there is the Removed and Added at the end, even though the device is still plugged in and in download mode when both pop up. I need my phone to be usable soon so help is GREATLY appreciated.
Click to expand...
Click to collapse
Your phone isn't a 32 Gb model is it? The PIT file from that post is for 16 Gb. I don't even think they made the S4 in 32 Gb. What version of Odin are you using. I just did this same procedure 3 or 4 days ago and it all went perfectly using Odin v3.09. Also make sure you md5 check the PIT file and ROM file you downloaded, that is always very important. When you add the PIT file to the PIT box it should automatically check the box for repartition, so you can check that too. I'm not a developer or an expert by any means but I am a technician, so these are just some things I could think of off the top of my head from when I did this a few days back. Hopefully one of the more experienced experts will chime in too.
Endstepper said:
So I unfortunately bricked my galaxy S4, but I am having issues unbricking it. I downloaded the full wipe and PIT file from http://forum.xda-developers.com/showthread.php?t=2735172 , installed the samsung drivers, booted into download mode, and set up both files, but whenever I hit start this occurs.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
I have tried installing and uninstalling the drivers, and tried different USB ports. However, everytime I plug it in, it installs drivers even though they are already installed, Am I doing something wrong? I am not unplugging the phone in the middle of it at all, so I dont know why there is the Removed and Added at the end, even though the device is still plugged in and in download mode when both pop up. I need my phone to be usable soon so help is GREATLY appreciated.
Click to expand...
Click to collapse
Try flashing it using a different USB (Non-3.0) port. Check how far it gets. Then try using Heimall. A free Odin alternative. Then If It doesn't reboot try a battery pull and hold the button to enter download mode, but then click restart instead/
npjohnson said:
Try flashing it using a different USB (Non-3.0) port. Check how far it gets. Then try using Heimall. A free Odin alternative. Then If It doesn't reboot try a battery pull and hold the button to enter download mode, but then click restart instead/
Click to expand...
Click to collapse
After switching from odin 3.09 to 3.07 the flash went through, so everything is up and running. Also my phone is a 16gb model, and I was downloading the full wipe file directly from the thread, so I'm not sure why it wasn't working. Thanks for the help though
Endstepper said:
After switching from odin 3.09 to 3.07 the flash went through, so everything is up and running. Also my phone is a 16gb model, and I was downloading the full wipe file directly from the thread, so I'm not sure why it wasn't working. Thanks for the help though
Click to expand...
Click to collapse
Glad you got it going. Even files from XDA threads can download faulty, it has happened to me before. So as a good measure performing a md5checksum is a good idea. Most of the folks here who post those links provide the md5 check value so you can ensure your download is clean. I am a Linux user so it's easy to do in Linux from the terminal. Now you can install Safestrap and Hyperdrive ROM to really have some fun! Enjoy!
Same problem
Endstepper said:
After switching from odin 3.09 to 3.07 the flash went through, so everything is up and running. Also my phone is a 16gb model, and I was downloading the full wipe file directly from the thread, so I'm not sure why it wasn't working. Thanks for the help though
Click to expand...
Click to collapse
I am having the same problem that you are/did. Am I reading this correct all you did was download odin 3.07 and flashed the file that goes in AP and it worked fine?
FireMedic1234 said:
I am having the same problem that you are/did. Am I reading this correct all you did was download odin 3.07 and flashed the file that goes in AP and it worked fine?
Click to expand...
Click to collapse
You need the PIT file too. You put that in the PIT box and the tar.md5 in the AP box. I was able to make everything work perfectly using Odin 3.09. Not sure why the OP had an issue with it but if 3.07 works then that's all that really matters.
Thank you
robn30 said:
You need the PIT file too. You put that in the PIT box and the tar.md5 in the AP box. I was able to make everything work perfectly using Odin 3.09. Not sure why the OP had an issue with it but if 3.07 works then that's all that really matters.
Click to expand...
Click to collapse
Thanks. I tried to do the update on Hyperdrive to 18, and weird stuff started happening. I went through all the install options and while it was installing it quit at 30% and went back to safe strap. I tried to reboot it through safestrap and it kept saying there is no system installed. Eventually I tried it anyways and it booted up, and it was Hyperdrive 18. then the wifi didn't work so I tried the old patches for 17 that didn't work, so i tired flashing 17 and was going to wait for 18 and the install did the same thing it quit at 30%. I have no idea what the hell is going on so I figured I'd wipe in and start fresh, but when I woke up this morning, the wifi on 18 works. I am lost.
FireMedic1234 said:
Thanks. I tried to do the update on Hyperdrive to 18, and weird stuff started happening. I went through all the install options and while it was installing it quit at 30% and went back to safe strap. I tried to reboot it through safestrap and it kept saying there is no system installed. Eventually I tried it anyways and it booted up, and it was Hyperdrive 18. then the wifi didn't work so I tried the old patches for 17 that didn't work, so i tired flashing 17 and was going to wait for 18 and the install did the same thing it quit at 30%. I have no idea what the hell is going on so I figured I'd wipe in and start fresh, but when I woke up this morning, the wifi on 18 works. I am lost.
Click to expand...
Click to collapse
It doesn't sound like it flashed properly at all. I am still running RLS 17.1 but it is as smooth as can be. Which Odin Version are you using? What Safestrap version are you running? I used Odin 3.09 and am running Safestrap 3.72. Also make sure you use the USB cable that came with your phone, I have always had success in doing so. Make sure you md5 checksum all your downloads to ensure they are clean and not faulty. Lastly make sure that before rebooting to the system you also install SuperSU from Safestrap and if using Hyperdrive 17 the NC5 Modules. Here is a great video for doing everything.
https://www.youtube.com/watch?v=2bDe_-mB7Rw
Greetings,
Right away, sorry if I'm posting this in the wrong spot.
My story:
One of my friends was about to throw away his tablet because of the "Firmware upgrade encountered an issue" problem. He took it to a "repair shop", they tried restoring the tablet with Kies and Smart Switch. They couldn't get it to work, so he gave it to me.
Kies does not detect the tablet.
Odin DOES detect the tablet, but flashing fails.
I've tried flashing absolutely anything I could find (apart from a custom rom, couldn't find one I could flash with odin).
I CANNOT flash ANYTHING with odin. Sometimes it fails on NAND write, other times it appears like the flash was successful because it says RESET in odin and the tablet turns off, but after turning it back on it goes right back to the "Firmware upgrade encountered an issue" screen.
The USB drivers are OK.
I've tried all ODIN version I could find from 1.85 to 3.11.1.
I CANNOT boot to recovery or download mode (if I could there wouldn't be a problem).
What could be wrong with it? What can I try to fix it? I'll try to list all of the things I tried to flash but forgive me if I forget some (there have been QUITE a few over the past 3 days of trying).
What I've tried to flash:
CF-Auto-Root-espresso10rf-espresso10rfxx-gtp5100
Clockworkmod_Recovery_for_P5100
espresso-any-root-kernel.v2.tar.md5
p5100-recovery.tar.md5
P5100XXAOF1_P5100BTUAOF1_BTU (stock rom region GB I think)
P5100XXDNA1_P5100NEEDNA1_NEE ([Pays Nordiques] 4.2
recovery-cache-fix.tar
philz_touch_6.03.8-jfltexx.tar.md5
CWM-root-P5100-v1
I've also tried flashing with PIT files:
gt-p5100_signed_espresso_20120220_16G
I've also tried to flash with NAND erase all (after everything else failed). That failed also.
I have no idea what else I can try.
I get this when I try to flash a stock rom:
<ID:0/007> Removed!!
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5100XWALD7_P5100OXXALD9_P5100XXLD7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> system.img
<ID:0/007> NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help would be GREATLY appreciated.
UPDATE:
I tried flashing P5100XXALD6_OXEALD5_v4.0.3_Repair_Firmware, it looked like it was going to succeed, but then the tablet powered off and now it doesn't turn on at all, not even to the "Firmware upgrade encountered an issue" screen. The battery only charges to 3.75 volts and then stops (measured with a multimeter). I tried removing the battery, completely discharging the circuitry (it was still showing 0.5 volts on the board after disconnecting the battery from the tablet). It didn't help. The tablet "turns on" just enough for my PC to play the USB CONNECTED sound, but the screen doesn't power on and it shuts down immediately (1 second in between the USB CONNECTED and USB DISCONNECTED sounds on the pc).
Did you manage to find a solution?