HI all,
Running Cyanogen nightly build and my phone froze yesterday while I was using an app (think it was twitter, but that should be fairly irrelevant). When I rebooted, it got stuck on the "Samsung Galaxy SIII" screen (and it sits there for hours).
I can't boot into recovery (home + vol up + power = the Samsung logo flashes up for a few seconds, then reboots), I can boot into Download but can't do anything from there:
From heimdall my output is:
Code:
sudo heimdall flash --recovery recovery.img
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
And from Odin (on windows) I get:
"File analysis
SetupConnection
Initialization....
Get PIT for mapping
There is no PIT partition
All threads completed (succeeded 0 / failed 1 )"
Is there any way out of this hole?
Have access to Odin? If so, following may help:
http://widefide.com/mobile/galaxy-s3-boot-problem-solution
found via: http://forum.xda-developers.com/showthread.php?p=29240858
Thanks for the reply. I have Odin on a borrowed laptop, so I tried that.
I get:
"SetupConnection...
Initialization....
Set PIT file...
DO NOT TURN OFF TARGET
.
Re-Partition operation failed
All threads completed (succeed 0 / failed 1 )"
If it's not recoverable, is it worth sending the phone back to the Carphone Warhouse (UK) to get it repaired/replaced. Can they tell it's been rooted if it won't even boot up?
Fair enough, worth asking.....
Given that you've tried more than basics, I hope for your sake you've not got nand corruption (seems to be S3 failure-du-jour), unlikely to recover from that.
The only good news is that if you are suffering that same problem (see SGS Sudden death thread) then your phone innards (or specific parts) will be replaced regardless of rooting, they simply don't care. Many xda members reporting the same thing.
Unsure what CPW will say but if you've exhausted the self-help options Samsung repair centre may be a good bet (you could always phone and explain what happened and what you tried since, they should realise you're technically capable and not bother checking the simple stuff). I was advised by 3 to go straight to the local Samsung repair (said they'd be faster), I do hope you've got one local to you.
At least there is a 2-year Samsung warranty on hardware.
thedigger said:
Thanks for the reply. I have Odin on a borrowed laptop, so I tried that.
I get:
"SetupConnection...
Initialization....
Set PIT file...
DO NOT TURN OFF TARGET
.
Re-Partition operation failed
All threads completed (succeed 0 / failed 1 )"
If it's not recoverable, is it worth sending the phone back to the Carphone Warhouse (UK) to get it repaired/replaced. Can they tell it's been rooted if it won't even boot up?
Click to expand...
Click to collapse
Is Re-Partition unchecked in ODIN?
I've tried both with it checked and unchecked. Neither works.
sorry dude ur device seesm about to dead
http://forum.xda-developers.com/showthread.php?t=1993044
its better to get replace under warranty
Sorry to say that it is a hardware issue. Literally motherboard is dead.
I faced that 2weeks ago... Im rooted and i sent back to samsung service centre... They replaced it free without question asked.
Sent from my GT-I9300 using xda app-developers app
thedigger said:
HI all,
Running Cyanogen nightly build and my phone froze yesterday while I was using an app (think it was twitter, but that should be fairly irrelevant). When I rebooted, it got stuck on the "Samsung Galaxy SIII" screen (and it sits there for hours).
I can't boot into recovery (home + vol up + power = the Samsung logo flashes up for a few seconds, then reboots), I can boot into Download but can't do anything from there:
From heimdall my output is:
Code:
sudo heimdall flash --recovery recovery.img
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
And from Odin (on windows) I get:
"File analysis
SetupConnection
Initialization....
Get PIT for mapping
There is no PIT partition
All threads completed (succeeded 0 / failed 1 )"
Is there any way out of this hole?
Click to expand...
Click to collapse
Hey thedigger, sorry for gravedigging this thread, but have you found any solution to this problem? Since yesterday I'm having the exact same issue as you describe here, and I'm starting to fear I'm SOL.
Thanks in advance.
roddds said:
Hey thedigger, sorry for gravedigging this thread, but have you found any solution to this problem? Since yesterday I'm having the exact same issue as you describe here, and I'm starting to fear I'm SOL.
Thanks in advance.
Click to expand...
Click to collapse
Search PIT problems .
jje
Hmm weird i read about this PIT problem more than several times already where the phone just without a warning seems to reboot and then it`s stuck at the bootlogo and it`s not flashing properly through Odin. I wonder what`s causing this to happen.
Facing the same problem
roddds said:
Hey thedigger, sorry for gravedigging this thread, but have you found any solution to this problem? Since yesterday I'm having the exact same issue as you describe here, and I'm starting to fear I'm SOL.
Thanks in advance.
Click to expand...
Click to collapse
i am facing same problem on s3. did you find any solution?
Thanks.
praveen145 said:
i am facing same problem on s3. did you find any solution?
Thanks.
Click to expand...
Click to collapse
Wow. What a blast from the past!!
I did get mine fixed, but it involved sending the phone off to Samsung for a motherboard replacement (it was still in the warranty period).
If you google "Galaxy S3 sudden death", you'll get tens of thousands of posts explaining what the problem is. I believe, in a nutshell, it's because the firmware was configured incorrectly and rather than writing blocks randomly across the NAND chip, it overwrote the same blocks continiously and "wore out" the solid state chip. They fixed all handsets under warranty at the time, and issued a patch to all handsets which supposedly fixed the problem.
There's a huge thread on this issue elsewhere on XDA Devs : http://forum.xda-developers.com/galaxy-s3/general/ultimate-gs3-sudden-death-thread-t1993044 - you may find that someone has a workaround, but my guess would be that it's beyond economic repair.
Related
[Q] Please help, Vibrant bricked, "Failed to open file" attempting to flash kernel...
Hey guys...pretty big noob here, I just got my Vibrant a week ago (first android) and think I bricked it already with what seems like a particularly dumb problem. I flashed it from Froyo to stock 2.1 to try to get Cyanogen on there, and following the directions I was trying to use Heimdall to install Cmenards's OverStock Kernel - but i accidentally put the wrong file name and got this:
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
ERROR: Failed to open file "ZImage"
Click to expand...
Click to collapse
Then trying to run again with the right name:
Initialising protocol...
Handshaking with Loke...
ERROR: Failed to receive response!
Click to expand...
Click to collapse
Thought "hmm...well, this thread says you can exit download mode just by taking the battery out and putting it back in..." and now I'm stuck at the cell-to-computer screen. I've tried holding the volume + power buttons, taking out the SIM / SD cards, taking out and reinserting the battery a bunch of times and it always brings me back to this screen, can't get to download mode. Nothing happens when it's plugged into the computer (neither my windows one nor the mac).
Lesson learned - no more flashing for me until I get educated Please help, thanks!
First big mistake - you tried to flash a 2.2 kernel based of RFS partition/file system on a 2.3 Rom MTD/Yaffs system.
Basically you tied to install a Honda 4cylindar engine in a Ford F350, and when it didn't match up you forced it with a hammer.
Yes you have now bricked your phone.
Read:
http://forum.xda-developers.com/showpost.php?p=13132341&postcount=1
Open Odin
Plug in phone to computer. If Odin sees the phone you are in luck. Ive had the cell-to-computer screen a few times and just treated it as a Download mode. Good luck.
Edit:
Import to note -
** Re-partition is checked now in ODIN - THIS IS APPROPRIATE!! **
When you go from CM7 back to stock you need to repartition. I would also uncheck auto reboot just in case it goes bad you are still connected. If it says "success" unplug and hold the power button for 10sec. IT will reboot.
Heh, I like the auto analogy. However, I actually had 2.1 (Eclair) on the phone when I was doing this. I went from stock 2.2 to stock 2.1 today. Never had CM7 on (you think I did, right?) And also, because Heimdall couldn't even access the flash file on my computer for the bad filename, I'm not sure what exactly it did.
Anyways, looks like Odin sees the phone, hopefully flashing now...
YEP - Looks like it was that simple. Thanks much, now I can get to sleep.
When i use the one click casual root method it goes through all the steps sucessfully then i get error, no partition with identifier 60 exists in pit
are you using the latest java 7?
I'll check when I get home Thanks
Sent from my SCH-I605 using Tapatalk 2
I'm using Java version 7 update number 15 and I'm having this issue
Sent from my SCH-I605 using Tapatalk 2
phnman390 said:
I'm using Java version 7 update number 15 and I'm having this issue
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
this is whats happening then the phone goes to android system recovery
WindowsLinux Galaxy Note 2 Jailbreak.scr...4kb ... Update Sucessful! MD5s verified!
Rebooting into download mode
Waiting for Downoad Mode device.detected!
Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
100%
BOOT upload successful
Ending session...
Rebooting device...
Releasing device interface...
Your device should be rebooting into Android now.
Pushing dependencies
Pushing su binary...
Pushing SuperSU app...
Pushing Exynos-Abuse exploit
Pushing root script
Pushing Busybox
Pushing viewmem
Pushing pit
Setting Permissions....
Executing Root Exploit.
[x]Ready for exploit
[x]Device Verification Checks Complete
[x]Ready for exploit
Injecting Code
[x]Exploit Injection Done.
your device is now rebooting into a totally insecure download mode. Press the Volume Up buton when requested by Download Mode. You will then flash the Suck It Verizon bootloader located here: http://d-h.st/DQG. Upon completion of this step, you will be rebooted into TWRP Recovery. CASUAL will wait for you to complete the insecure flash of the Suck It Verizon Bootloader. Press the Up Key before you flash the bootloader in Odin Mode.
Waiting for Downoad Mode device.detected!
Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Ending session...
Rebooting device...
Releasing device interface...
ERROR: No partition with identifier "60" exists in the specified PIT.waiting for device
Rebooting into recovery
Done
done
Any suggestions
Sent from my SCH-I605 using Tapatalk 2
ya the one click method seems to giving folks some trouble, mainly on macs. do you have access to a windows 7 pc?
droidstyle said:
are you using the latest java 7?
Click to expand...
Click to collapse
yes
droidstyle said:
ya the one click method seems to giving folks some trouble, mainly on macs. do you have access to a windows 7 pc?
Click to expand...
Click to collapse
yes getting same error on windows 8 pc and windows 7 pc
same?
I seem to have the same trouble. Windows 7 64 bit. Verizon Galaxy note 2. Casual r311. Ran once, failed, pulled battery, ran again, made some progress, stopped with the following error message:
>>>ERROR: No partition with identifier "60" exists in the specified PIT.waiting for device
>>>Rebooting into recovery
Now my phone is sitting in recovery and I have no idea what to do. Can't find an answer online. Too timid to press any of the options. I got a pop up window from the Casual BackAtcha Verizon R311 program saying my phone should be unlocked. That was the last pop up I got. Then the error and my phone sitting in recovery mode.
What do I do? I feel so ridiculously stupid. Been trying this for hours and it's supposed to be the simplest method out there. Heh. Ya'll really know how to confuse a man.
If the program is to be believed I have unlocked my phone. But that is all. I wish there was something more intelligent I could ask than simply "WHAT DO I DO????"..... But that's all I got... WTF do I do? My best guess is press "DO IT" again and hope it realizes it already did a few of the steps. But my phone is sitting in this "Android System Recovery (3e)" menu, which was not where it was when I first started. So that can't be right.
Help! Please! I am so sorry for wasting your time!
Reboot mine does the same thing
Sent from my SCH-I605 using Tapatalk 2
But you won't be rooted but your phone will work
Sent from my SCH-I605 using Tapatalk 2
phnman390 said:
But you won't be rooted but your phone will work
Click to expand...
Click to collapse
Awesome. Thank you very much! That is what I expected but I'm just too lost in the overly complicated process to know if it was safe.
Thanks again. It was tough without my phone for a whole day. Hopefully this problem can get figured out so we can both get root working!
I'm having the exact same problem. I hope this is addressed soon.
I see that Cheshire Delusion and phnman390 are both actively posting and trying to find a solution. If either of you get your phone rooted please post to this thread explaining how you did, as we all seem to have the same problem.
I'm going to re-run Casual and see if that works. If it fails, I'm going to try doing it on a different windows 7 PC. I'll post if I make any progress or brick my phone or whatnot.
I was wondering if it is possible for the USB cable to be the problem? I've read somewhere that it can sometimes cause a root to fail, at least with other phone models. I had to try a couple different cables to get Casual 311b to show "LINK CONNECTED". One cable would charge but wouldn't show up as "LINK CONNECTED". If it shows link connected, and I have up to date Samsung drivers, then the cable should not be an issue, right?
I don't think it's a driver issue I think it's the fact that I had the phone rooted before took the update and somehow this is not working with it it has something to do with that I think I show the superuser icon but I'm not rooted
Sent from my SCH-I605 using Tapatalk 2
I'm having same issues ! Cant get it to work
Is it the same error I'm getting
Sent from my SCH-I605 using Tapatalk 2
I am getting the same error. OI have tried two different USB cables and I am on a windows 8 64 bit machine. I am going to try and load windows 7 in a vm and see if that does any better.
Ok let me know
Sent from my SCH-I605 using Tapatalk 2
Hello i've been reading so many threads about this same problem but i don't know why the solutions on others won't help me revive the phone.
My international SGS3 is dead, recovery mode won't work but Download or Odin mode does work, the phone is stuck on the Samsung logo and won't start. also this is what says Odin mode:
Product Name:
Custom Binary Download: No
Current Binary: Samsung official
System Status: Custom
I've tried CF Root v 6.4 with Odin 3.07 on PDA and i get this message: There's No Pit Partition
i've tried with the Mx.pit and CF Root on pda and i get stuck with this message: Get Pit for mapping...
i'm right now downloading GT-I9300_XEO_I9300XXALEF_I9300OXFALEA_I9300XXLEF.zip (it is supposed to come separated files to do the 3 way flash). if anyone can help me fixing this issue i will be happy to donate since i am really desperate seeing nothing works for me.
i've tried with different computers/cords/usb ports idk what to do
nothing works please somebody help me
mariag32 said:
nothing works please somebody help me
Click to expand...
Click to collapse
Nothing works because product name blank usually means motherboard failure this is a service issue not software fix.:crying:
tallman43 said:
Nothing works because product name blank usually means motherboard failure this is a service issue not software fix.
Click to expand...
Click to collapse
See that's the answer i was afraid of getting :crying: anyone has others opinions???
bumping...
Please and thanks!
I need a PIT file from your device, extracted through Heimdall. It's very simple. No modding or flashing or anything, just a file that's on your device that will bring mine back to life. I've been working on root and need to confirm there is a solid way out in case it doesn't work. So far, it can't be done without a PIT.
-----
Using a Mac
I had to install VirtualBox and run Odin through that.
The way to set it up is here: http://www.onebadkid.com/?p=6930
sbrownla said:
Please and thanks!
I need a PIT file from your device, extracted through Heimdall. It's very simple. No modding or flashing or anything, just a file that's on your device that will bring mine back to life.
Cheers.
Click to expand...
Click to collapse
you should probably post specific instructions for the mac users out there on how to extract what you need..
wase4711 said:
you should probably post specific instructions for the mac users out there on how to extract what you need..
Click to expand...
Click to collapse
Heimdall is not just for Mac it is now available on all platforms.
If anyone is willing to do it, I will guide them through it. It's basically:
(1) Put the watch in in Download Mode:
press and hold home button until screen goes off (keep holding and when it comes on and says "Rebooting...")
then tap, tap, tap, the home button until the menu comes up (Continue, Download, Recovery, Power Off or something like that)
then single-tap through the menu to highlight choose "Download"
then press and hold the home button with "Download" highlighted, to choose to enter into Download mode
(2) Open Heimdall: available for OSX, Linux and Windows
(3) Select Utilities (tab)
(4) Plug Device In: you'll see where it says "Device Detected" indicate that you are, in fact, connected
(5) Download Pit: it has its own section, you choose the destination file and location
interesting info; I did not know there was a version for windows too..
good info, especially on how to get it into download mode!
wase4711 said:
interesting info; I did not know there was a version for windows too..
good info, especially on how to get it into download mode!
Click to expand...
Click to collapse
I cleaned it up to make it more easy to understand. Yeah, Heimdall is incredible, but its most important feature is the creation of a PIT from an existing device.
if I had the watch, I would do it for you, but, unfortunately, I dont...yet..
I have an ATT Gear S....
Ok, I have an ATT watch and can provide the file you need. I will work on it tomorrow morning when I can get in front of my desktop.
On a side note, do you know if I can unlock this and use it on Verizon?
Thank you JEEBUS!!!
Mulox said:
Ok, I have an ATT watch and can provide the file you need. I will work on it tomorrow morning when I can get in front of my desktop.
On a side note, do you know if I can unlock this and use it on Verizon?
Click to expand...
Click to collapse
THANK YOU!!!! :good::fingers-crossed::good: I am desperate. I was figuring I was going to have to drive two hours, buy another Gear S, pull the PIT off, and then return it.
I have an AT&T Gear S with my Verizon Note II. My Gear S came carrier unlocked, I have no idea why, it's a long story though. What you will have to do to get it to work with a Verizon phone, is get a plan for the watch (I now have an H20 nano sim--I had StraightTalk before but it wasn't worth it for how little I used it--that I pay 10 bucks for 100 minutes and some tiny amount of data), and that suits my needs perfectly.
You have to have a Verizon phone plan that allows call forwarding. Make sure you have that. Other than that, it works perfectly.
The rest is cake.
Error downloading pit file...
Ok, I was able to enter download mode ok, and Heimdall was able to detect the device, but when I click on download, this is the error I get:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
---------- Post added at 02:29 PM ---------- Previous post was at 02:22 PM ----------
sbrownla said:
I have an AT&T Gear S with my Verizon Note II. My Gear S came carrier unlocked, I have no idea why, it's a long story though. What you will have to do to get it to work with a Verizon phone, is get a plan for the watch (I now have an H20 nano sim--I had StraightTalk before but it wasn't worth it for how little I used it--that I pay 10 bucks for 100 minutes and some tiny amount of data), and that suits my needs perfectly.
You have to have a Verizon phone plan that allows call forwarding. Make sure you have that. Other than that, it works perfectly.
Click to expand...
Click to collapse
So I do have a Galaxy S5 on Verizon. I purchased a brand new ATT Gear S, only because I got a ridiculous bargain at $250, vs. $400 from Verizon!
When I called Verizon and gave them the IMEI, they said it could not be used on their network. So I guess I just need to figure out how to unlock it now, without having to pay.
Mulox said:
Ok, I was able to enter download mode ok, and Heimdall was able to detect the device, but when I click on download, this is the error I get:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
---------- Post added at 02:29 PM ---------- Previous post was at 02:22 PM ----------
So I do have a Galaxy S5 on Verizon. I purchased a brand new ATT Gear S, only because I got a ridiculous bargain at $250, vs. $400 from Verizon!
When I called Verizon and gave them the IMEI, they said it could not be used on their network. So I guess I just need to figure out how to unlock it now, without having to pay.
Click to expand...
Click to collapse
Gear S Pit
Are you running Heimdall on a PC or Mac?
If you're on a PC, you have to make sure the right drivers are installed to connect your Gear to your computer.
Did you ever install Kies? If you did, you'll have to uninstall it to get rid of the Kies versions of the drivers. Windows can naturally detect the proper drivers for the Gear S. Kies installs other drivers, and I think they install other drivers that cause conflicts with competing device mod software ... mmmhrrmmmm ... Same situation if you're on a Mac.
To get rid of the Samsung drivers on your PC you have to go into the program manager and uninstall them as an application. Running CC Cleaner and deleting Samsung mobile drivers helps too (unless you're using a Samsung PC!). Don't worry too much about that because if you want to install Kies again later to connect it to your phone, you just re-install and it will overwrite the drivers. You'll also need to restart after uninstalling the Kies drivers and Samsung drivers, then just plug in the phone and let Windows do the rest. It knows which drivers to install.
Verizon/ATT
So, you shouldn't need to give Verizon the IMEI unless you were hoping that you'd be able to add it to your existing Verizon plan in which case, you have to use the Verizon edition of the watch.
Mulox said:
Ok, I was able to enter download mode ok, and Heimdall was able to detect the device, but when I click on download, this is the error I get:
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
---------- Post added at 02:29 PM ---------- Previous post was at 02:22 PM ----------
So I do have a Galaxy S5 on Verizon. I purchased a brand new ATT Gear S, only because I got a ridiculous bargain at $250, vs. $400 from Verizon!
When I called Verizon and gave them the IMEI, they said it could not be used on their network. So I guess I just need to figure out how to unlock it now, without having to pay.
Click to expand...
Click to collapse
I will seriously pay for your unlocking if you can just get that pit file off of your watch via the instructions.
No one else has offered to help. Which is shocking.
And it's very simple.
still need help?
sbrownla said:
I will seriously pay for your unlocking if you can just get that pit file off of your watch via the instructions.
No one else has offered to help. Which is shocking.
And it's very simple.
Click to expand...
Click to collapse
If you still need this just let me know i can get it to you right away.
bda714 said:
If you still need this just let me know i can get it to you right away.
Click to expand...
Click to collapse
Yes, I still need the AT&T Gear S PIT.
sbrownla said:
Gear S Pit
Are you running Heimdall on a PC or Mac?
If you're on a PC, you have to make sure the right drivers are installed to connect your Gear to your computer.
Did you ever install Kies? If you did, you'll have to uninstall it to get rid of the Kies versions of the drivers. Windows can naturally detect the proper drivers for the Gear S. Kies installs other drivers, and I think they install other drivers that cause conflicts with competing device mod software ... mmmhrrmmmm ... Same situation if you're on a Mac.
To get rid of the Samsung drivers on your PC you have to go into the program manager and uninstall them as an application. Running CC Cleaner and deleting Samsung mobile drivers helps too (unless you're using a Samsung PC!). Don't worry too much about that because if you want to install Kies again later to connect it to your phone, you just re-install and it will overwrite the drivers. You'll also need to restart after uninstalling the Kies drivers and Samsung drivers, then just plug in the phone and let Windows do the rest. It knows which drivers to install.
Verizon/ATT
So, you shouldn't need to give Verizon the IMEI unless you were hoping that you'd be able to add it to your existing Verizon plan in which case, you have to use the Verizon edition of the watch.
Click to expand...
Click to collapse
I never had Kies installed and I am getting the same error. I have a watch and I'm hooked up just need to get past this lib 12 error
EDIT: Forgot to mention no samsung drivers listed in programs either. I can unistall the driver from device manager and reboot but I doubt that will make a difference? I'm trying now to update the driver maniually through the zdiag tool thing
---------- Post added at 04:37 PM ---------- Previous post was at 04:27 PM ----------
I replaced the driver using the zadig.exe tool with all three options. Each time I get
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
EDIT: What version of Heimdall are you using? I have zero experience with it and the only thing I found was suite 1.4.0. I just tried with the mac version on a test mac I have at work and it wont even see the device.
EDIT 2: So I took a look at the read me and it says it should be listed as "Samsung USB Composite DEvice". when plugged in my device is listed as MSM8960. I uninstalled the driver and deleted it. Rebooted the computer and plugged it back in....came right back up as MSM8960. I'll try it on a freshly installed computer for ****s and giggles.
d0ntp4n1c said:
I never had Kies installed and I am getting the same error. I have a watch and I'm hooked up just need to get past this lib 12 error
EDIT: Forgot to mention no samsung drivers listed in programs either. I can unistall the driver from device manager and reboot but I doubt that will make a difference? I'm trying now to update the driver maniually through the zdiag tool thing
---------- Post added at 04:37 PM ---------- Previous post was at 04:27 PM ----------
I replaced the driver using the zadig.exe tool with all three options. Each time I get
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
EDIT: What version of Heimdall are you using? I have zero experience with it and the only thing I found was suite 1.4.0. I just tried with the mac version on a test mac I have at work and it wont even see the device.
EDIT 2: So I took a look at the read me and it says it should be listed as "Samsung USB Composite DEvice". when plugged in my device is listed as MSM8960. I uninstalled the driver and deleted it. Rebooted the computer and plugged it back in....came right back up as MSM8960. I'll try it on a freshly installed computer for ****s and giggles.
Click to expand...
Click to collapse
Uh oh ... I just did a search and found that newer Samsung devices with newer bootloaders are facing incompatibility issues w/ Heimdall. I may have to generate a PIT manually.
Yeah v1.4 is what usually works.
Looks like either Samsung hates modders ... or Yosemite has caused major problems ...
I'll keep looking around.
THANK YOU
sbrownla said:
Uh oh ... I just did a search and found that newer Samsung devices with newer bootloaders are facing incompatibility issues w/ Heimdall. I may have to generate a PIT manually.
Looks like Samsung hates modders ...
I'll keep looking around.
Click to expand...
Click to collapse
Bummer.
If you find something that should work I will give it a shot. I've only ever bricked one device in my years but it f-ing SUCKS!
d0ntp4n1c said:
Bummer.
If you find something that should work I will give it a shot. I've only ever bricked one device in my years but it f-ing SUCKS!
Click to expand...
Click to collapse
That's so cool of you.
So ... I'm back out of bootlooping and I'm going to work on flashing again ... I'm still bricked (stuck in download mode) but I'll do some more looking at what's up with Heimdall.
I am rrreeeeally curious about what's going on ... is it really Heimdall or is it the new Samsung bootloaders ... or ...
Hm, I have an idea though ... I am certain that the rootfs that that person who claimed they'd figured out root changed my permissions and my PIT even though I modded it with my stock firmware. So I'm going to try to pull out the rootfs from my stock firmware for my AT&T Gear S and see if I can just flash that.
Odin can see my device and recognizes that it is in download mode ... it's just that it needs to be repartitioned ... usually, however, that's done with a separate PIT but the thing is, the PIT is supposed to be contained in a few locations within the stock firmware TAR ball, or it's its own separate file within the stock firmware TAR ball. Hehe, tar ball ... And Heimdall has a feature that can extract a usable PIT file ... but nothing else out there seems to.
We need @AdamOutler!!!!! I don't know what his thoughts are on Tizen and Samsung right now ... or on wearables, but the man is a genius.
I also tried the different USB drivers and same issue...
Mulox said:
I also tried the different USB drivers and same issue...
Click to expand...
Click to collapse
yours showing up as msm too?
By the way I'm using the AT&T variant of the Gear S with a Verizon S5. Haven't had any issues but yeah if you want the device on a Verizon telephone number I'm sure they are doing everything they can to say no. Their same damn watch is 100 bucks more then their competitor! >.<
d0ntp4n1c said:
yours showing up as msm too?
By the way I'm using the AT&T variant of the Gear S with a Verizon S5. Haven't had any issues but yeah if you want the device on a Verizon telephone number I'm sure they are doing everything they can to say no. Their same damn watch is 100 bucks more then their competitor! >.<
Click to expand...
Click to collapse
Mulox said:
I also tried the different USB drivers and same issue...
Click to expand...
Click to collapse
Thanks for trying you guys. I am trying every combination of connection and firmware I can.
Hello i have a Galaxy s3 i9300gsmh (Dutch) grey lines on screen / no pit partition.
Samsung kies does not recognize phone, it says phone does not respond!
Odin recognises but does not flash anything..........
phone auto turns on when plugin cable, also charges the battery but no charging screen is displayed.
it does not boot up, when turning on grey lines white screen no sound, no vibration, only downloadmode works, but i am not able to flash anything......
I have 4 pit files, none of them flash. I tried allot of firmwares but only getting the message no pit partition and when selecting a pit file:
In download mode Product name is empty
Custom binary download: no
Current binary: samsung official
System status: Custom
Odin when trying to flash with .pit file:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Removed!!
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
Odin when trying to flash anything without .pit file:
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Heimdall flash error:
Heimdall v1.3.2, Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VIDID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Uploading PIT
ERROR: Failed to confirm end of PIT file transfer!
PIT upload failed!
Ending session...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!
Anybody knows how to fix this ?
I tried differt cables, other laptop, about 30 different roms, Repair firmware, 4 pit files, samsung drivers, heimdall drivers
Did the phone work before?
Where did you get the roms?
The missing product name in download mode is not good and may require a JTAG service to fix the phone.
Could be a buggered phone but try another heimdall or try odin.
Make sure the cable you use is high quality, usually a manufacturer issued cable is best.
Make sure the usb port isn't a shared port (single port side on laptops) (motherboard on desktops).
Make sure you're not using Windows 10. Best results are with xp.
Make sure your efs is good.
Make sure you have the correct firmware/files for the device.
Beamed in by telepathy.
This happend because i flashed it wrong, my brother gave me the phone, and android was dead on it, it would not map anything,
So i flashed root on it and twrp, and cwmtouch but i could not flash the phone with those recoverys strange enough..... It said 0 mb internal memory
And factory restore also did not changed anyhthing......
But flashing the recovery worked....
Was stuck on samsung logo, then i flashed it with selecting the wrong flash file in odin KIES_HOME_I535VRBMB1_861013_REV09_user_low_ship_NOWIPE.tar
It was a succesfull flash (Took 20 minutes) but offcourse the wrong flash file, after that those grey lines...........
Im using windows 7, allready tried flashing with xp on virtual machine.
Tried from my server.....
Tried 10 cables
With odin 3.07 he keeps hanging GET pit for mapping , further allready tried all other odin versions,
I dont know what the right firmware is, but i downloaden from sammobile multiple versions for the i9300....
Without selecting repartitioning, it says no pit partion, with selecting all failes.....
If someone has a link to the right firmware would be nice, but i think i allready have it.
Pit file would also be welcome, i tried the mx.pit, i9300.pit , GT-I9300_mx_20120329, M0_20120220, GT-I9300_mx_20120322 ( Dont know wich one is the right one)
Think i screwed it up by flashing the wrong file on it.....
Is there nothing to shortcircuit ? so it will flash/reset or anything ?
Is there other software to flash without having a box ?
Or any silly tricks ? freezing the phone or something?
Can try everything so tips are welcome before i break it into 2 pieces
shivadow said:
Could be a buggered phone but try another heimdall or try odin.
Make sure the cable you use is high quality, usually a manufacturer issued cable is best.
Make sure the usb port isn't a shared port (single port side on laptops) (motherboard on desktops).
Make sure you're not using Windows 10. Best results are with xp.
Make sure your efs is good.
Make sure you have the correct firmware/files for the device.
Beamed in by telepathy.
Click to expand...
Click to collapse
I also think the missing product name is the problem, so the chip does not know what to do..
I dont have jtag, boxer are to expansive, there needs to be a solution without using boxes or jtag.
Maybe other software to flash, does not matther if it dies for ever... so willing to try everything....
audit13 said:
Did the phone work before?
Where did you get the roms?
The missing product name in download mode is not good and may require a JTAG service to fix the phone.
Click to expand...
Click to collapse
Local phone repair shop? they usually have boxes and probably won't charge you so much for taking the phone back to life if its only soft bricked
If its pit then the chances are it's a dead device. Sometimes you can get pit errors if your setup isn't right. Using a vm isn't always reliable as translation must occur between the 2 operating systems. You should try a dual boot or an xp machine.
If no joy then you can call it a dead phone.
Beamed in by telepathy.
similar situation but product name says GTI9300
Hi guys,
i've a similar situation where the phone shows white and grey lines on the display, I cannot go on recovery mode, just on download mode using a jig usb, but when I try to flash anything with Odin, I get the "No PIT file" error.. tried several PIT files and firmware(both stock and custom rom's) but with no success... I guess that as long as I can see the product name, the phone is not totally dead, am I right?
I found this post here:
https://forum.xda-developers.com/galaxy-s3/general/galaxy-s-iii-gt-i9300-hard-brick-fix-t1916796
and I have a good S3 borrowed from a friend, although I don't want to mess up his while trying to fix mine...
Any suggestion is highly appreciated, thanks!
Have you tried using different USB cables and USB 2.0 ports?
You Better Replace Logic Board
I am 100 percent sure this is SUDDEN DEATH SYNDROME. Because I too was affected today I replaced my logic board.
audit13 said:
Have you tried using different USB cables and USB 2.0 ports?
Click to expand...
Click to collapse
yes, different USB ports, different cables, even different laptops with different operating systems... still no joy
Karthij said:
I am 100 percent sure this is SUDDEN DEATH SYNDROME. Because I too was affected today I replaced my logic board.
Click to expand...
Click to collapse
The SDS was fixed by upgrading the phone to Android 4.1.2 or later version, wasn't it? Plus on many forums it's indicated that as long as the product name on download mode is not empty, the phone can be recovered via software
Tried flashing without the pit file?
yep, it doesn't work as there is no PIT partition
Try flashing the Odin version TWRP and see if you can enter into TWRP after flashing.
audit13 said:
Try flashing the Odin version TWRP and see if you can enter into TWRP after flashing.
Click to expand...
Click to collapse
Tried that too, but unfortunately it's impossible to flash anything into the device.. I took it to a repair shop and they said the only way is to replace the motherboard but actually it's not worth it
Inviato dal mio ONE A2003 utilizzando Tapatalk
The damaged memory chip explains why all recovery methods you tried would not work. You did everything right and everything you could.
steponch said:
yes, different USB ports, different cables, even different laptops with different operating systems... still no joy
The SDS was fixed by upgrading the phone to Android 4.1.2 or later version, wasn't it? Plus on many forums it's indicated that as long as the product name on download mode is not empty, the phone can be recovered via software
Click to expand...
Click to collapse
Believe Me The Chip is Damaged It already have bug and physically it is damaged. So we cannot do any software related tweaks for fixing them unless we REPLACE eMMC chip OR whole LOGIC Board.
It is simple For replacing board i done it myself only
20 USD //