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.
Related
I am using the UCKH7 one click w/root tool.
I start download mode by holding volume up and down while plugging in USB. I click the start button but the program hangs at 'factoryfs.img'
Please help. Thanks.
AT&T galaxy s2
Deenybird said:
I am using the UCKH7 one click w/root tool.
I start download mode by holding volume up and down while plugging in USB. I click the start button but the program hangs at 'factoryfs.img'
Please help. Thanks.
AT&T galaxy s2
Click to expand...
Click to collapse
I use heimdall personally. Never had any problems with it. Do you have all the sgs2 drivers installed?
Also check md5 sums to make sure your download is ok.
Sent from my SGH-I777
I'll try heimdall. Drivers should be fine as kies is installed. Rom should be good as I've tried 2 different download sources
Make sure you install the libusb drivers for heimdall before flashing. The instructions are in the heimdall readme. Good luck
Sent from my SGH-I777
Just wanted to post that my problem is solved.
Summary: My AT&T Galaxy SII showed an error on boot (software upgrade failed. connect to kies...). Kies wouldn't even recognize the device so that route was a no go. So as everyone's recommended method of last resort, I decided to flash the device back to stock via odin. I entered download mode (volume up + volume down and plug in usb) and Odin would recognize the device, I would load the stock rom in the PDA slot and hit start and it would begin normally, but it would always fail after a few seconds on 'NAND write start', or 'factoryfs.img'. So I got a 1 click download solution using odin for reverting my phone back to stock. Same thing, it would recognize the phone, but stall out and fail. I also tried flashing clockworkmod via odin but and same problem. People recommended I try heimdall. It would recognize my device, and then fail after 'kernel 100%'.
I tried both programs on 3 different computers, and must have tried 12 different USB slots amongst all of them. I'm fairly handy with this stuff and I worked for hours on it.
xtra info: I had successfully used odin on my computer to flash a kernel just a week ago so I know my stock usb cable was working etc...
Resolution: So I hung my head and drove to the ATT store. After pressing a few buttons on the device and not getting anywhere they sent me to a nearby Device Support Center. I told the girl at the counter that my phone booted to this error screen and that connecting it to Kies did nothing. She asked if it was ok that in the case that she couldn't fix it she would offer me a replacement. I said that was fine and after 10 minutes in the back room she came out with a replacement (free of charge).
Well that was the good news. For the bad news, unfortunately I still don't know how to fix the problem I had, and don't really know how to avoid it in the future. I thought phone's could only get truly bricked if you messed with PIT files and such. There didn't seem to be anything more I could do than flash with odin or heimdall as those were already last resorts. I know I had the right files, the right drivers, and working usb. No matter how crazy I got with my iphone, a full restore was only a click away by plugging in to iTunes. Somehow I messed up my phone so bad that even the device support center couldn't fix it....? Shouldn't have had to be like that.
Thank yous: Thanks to ATT for having a walk-in store and for so easily offering up a replacement. Thanks to the many people on the web who offered remedies.
tl;dr - phone broke, att replaced, still a mystery
My player is still dead, and I noticed this new feature of Kies. Others have gotten the "Firmware Update and Initialization" working with the SGS3's and such, I tried it on my player by entering the model name as "YP-G70" and the serial number as it's listed on the box.
I'm in download mode via unbrickable resurrector, and when I try it in kies it comes back with "The model information you have entered cannot be verified; the device initialization cannot proceed." I also tried "YP-G70CWY/XAA" as shown on the box and it still doesn't work. I'm sure I have the serial number correct, maybe Samsung decided not to support these via that kies feature??
Has anyone gotten this to work?
If your in download mode just use Odin or Heimdall to flash a stock ROM, not sure whats out there for the 5.0 as I have the 4.0, Keis is a junk virtually useless app, and in a YEAR of ownership and an uncountable number of ROM flashes via Odin, Heimdall and CWM zips I have never once considered using Keis for anything.
daniel644 said:
If your in download mode just use Odin or Heimdall to flash a stock ROM, not sure whats out there for the 5.0 as I have the 4.0, Keis is a junk virtually useless app, and in a YEAR of ownership and an uncountable number of ROM flashes via Odin, Heimdall and CWM zips I have never once considered using Keis for anything.
Click to expand...
Click to collapse
I know, I hate kies too. The filesystem on my player is severely screwed though, if samsung released a way to put in two numbers and click ok I'm more than willing to give it a shot.
I got an SGS3 a few months ago, so while I'd love to have my SGP working again I'm not about to spend $50 to have it JTAG'd.
exodus454 said:
I know, I hate kies too. The filesystem on my player is severely screwed though, if samsung released a way to put in two numbers and click ok I'm more than willing to give it a shot.
I got an SGS3 a few months ago, so while I'd love to have my SGP working again I'm not about to spend $50 to have it JTAG'd.
Click to expand...
Click to collapse
I have the same problem with my 3.6, nothing seems to work, any combo of letters and numbers (switching O for 0 and 0 for O and such)
my phone has problem i download kies to solve but when i enter my model name and series number say the model information that you have entered can not be verified;the device initialization cannot proceed
My model gt-I9300 but samusun kies
The model information that you have entered cannot be verified. The device initialization canot process please contact the service center.
Plzz help me.
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
Please friends, help!
Samsung Galaxy Player 5.0 YP-G70 (with phisycal home button) bricked.
I accidentally flashed the rom to SGS-I9000B to the SGP 5.0 so it got bricked.
It's status is: doesn't turn on, doesn't enter in dowload mode (Volume down + Home + Power), doesn't show charging icon.
After weeks of exaustive researche, the only way I was able to enter in download mode was using the Adam's Outler procedure: Instaling Linux (Ubuntu along W7), Java, Oracle Virtual Box, a XP version of Windows under VBOX, to run Samsung drivers and Odin after using Unbrickable Resurrector R40.
Well, using this procedure SGP 5.0 enters in downloading mode and when I use the PIT file and BootloadersOnly provided by Adam the result in Odin is PASS! Despite that SGP doesn't reboot and keeps the same way: doesn't turn on, doesn't enter in dowload mode (Volume down + Home + Power), doesn't show charging icon.
So I enter in download mode using Unbrickable Resurrector R40 again and try to flash several SGP 5.0 YP-G70 Intl ROMs: Stock Froyo, Stock Ginger Bread and some Customs ROMs most of them PASS in the Odin result BUT SGP 5.0 never reboots or turn on after the procedure.
I have a doubt of marking or not Re-partition in Odin, but the procedure just works if I mark it.
I feel I was close to resurrect it and make it work again but all I've got is frustration.
I'm not an expert as the major of you so I beg some enlightned soul show me the way to make it works: step by step and share with me the right files I have to use to make it works.
I also tryied the same procedure using Odin 1.3, 1.7, 1.83 version. All the same result.
It seems like I miss something. I also tried several procedures I found in other threads none worked for me.
I also have installed Heimdall but I was not able to find the appropriate files to use it and SGP 5.0 can not have the batery removed. Someone wrote Adam has developed a tool for SGP full recovery but I didnt find it.
Please, folks, help me and I will share the solution with other people in the same situation.
Thanks and best regards.
Wanted you to know I saw your post but got a full plate today... If you can get to download mode we should be able to get you fixed up... just give me some time...
Ok, So I've been reading your post and it seems like you've been diligent in looking for fixes. I don't understand this:
"Instaling Linux (Ubuntu along W7), Java, Oracle Virtual Box, a XP version of Windows under VBOX, to run Samsung drivers and Odin after using Unbrickable Resurrector R40."
Does that mean that installed Ubuntu "natively" or in Virtual box? or have tried both?
Same problem
mrlightman said:
Please friends, help!
Samsung Galaxy Player 5.0 YP-G70 (with phisycal home button) bricked.
I accidentally flashed the rom to SGS-I9000B to the SGP 5.0 so it got bricked.
It's status is: doesn't turn on, doesn't enter in dowload mode (Volume down + Home + Power), doesn't show charging icon.
Thanks and best regards.
Click to expand...
Click to collapse
Hi. I'm in the same situation. Flashed the Player 4 rom and I've got a black box now. I've just been chilling for a few weeks, tired of flashing it and failing, so I'm glad to see somebody else is working on this too.
I hope one of us has some luck soon.
Meticulus said:
Ok, So I've been reading your post and it seems like you've been diligent in looking for fixes. I don't understand this:
"Instaling Linux (Ubuntu along W7), Java, Oracle Virtual Box, a XP version of Windows under VBOX, to run Samsung drivers and Odin after using Unbrickable Resurrector R40."
Does that mean that installed Ubuntu "natively" or in Virtual box? or have tried both?
Click to expand...
Click to collapse
Hi, Meticulus.
I've installed Ubuntu so I can run the Unbrickable Ressurector under Ubuntu, then I run a Widows XP version with a VBOX under Ubuntu too to run Odin.
The farest I could go is to make it get into forced Download mode using Resurrector, but It wont turn on after passing in Odin.
Really need your help.
Thanks in advance.
mrlightman said:
Hi, Meticulus.
I've installed Ubuntu so I can run the Unbrickable Ressurector under Ubuntu, then I run a Widows XP version with a VBOX under Ubuntu too to run Odin.
The farest I could go is to make it get into forced Download mode using Resurrector, but It wont turn on after passing in Odin.
Really need your help.
Thanks in advance.
Click to expand...
Click to collapse
OK, once you use the un-brickable resurector to get to download mode (don't reboot or anything), you need to flash a rom with boot loaders such as this one: http://www.4shared.com/zip/vxHoJ8E0/G70JKKE3_STOK_222RU_.html
If your partition tables are messed up, it may not boot but you should be able to get back to download mode without the resurector.... Hold power and volume down to try...
Give that a try let me know how it goes...
No results from Unbrickable Ressurector
dancog said:
Hi. I'm in the same situation. Flashed the Player 4 rom and I've got a black box now. ...
Click to expand...
Click to collapse
I'm not getting any results from Unbrickable Ressurector. Here's the message:
--------------------------------------------------------------------------
#SBL: GPSbl.bin LOCATION:0x40244000 tool:SMDK
1. Apply UnBrickable Mod
2. Remove then insert Device battery
3. Connect to computer via USB.
4. Click the Download Mode button
5. Download new software with Heimdall.
Begin Resurrection Sequence
Requesting Permission to access device
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
Exception in thread "Thread-2" java.lang.ClassCastException: [Ljava.lang.Object; cannot be cast to [Ljava.lang.String;
at com.AdamOutler.LowLevelUnBrick.Shell$1.run(Shell.java:191)
at java.lang.Thread.run(Thread.java:724)
--------------------------------------------------------------------------------------------------
jdk-7u40-linux-i586.tar.gz
Linux Slackware 14.0
UnBrickableResurrectorR40.jar
oneclickunbrick?
try this... google oneclickunbrick. download this and plug in device... wait ten to 30 mins and click open. then click unbrick... its helped me LOTS
---------- Post added at 07:14 PM ---------- Previous post was at 07:00 PM ----------
the reason for your spg not booting is cause your flashing the incorrect stuff onto it. idealy you want to flash a stock rom that works then CWM onto it so it doesn't happen in the future as your then flash the rest from there. ill get your my tablets stocks...
http://www.hotfile.com/dl/200665131/09e0d79/G70XXKPL_G70XXKPL_XSA.zip.html
download that... then you should be able to fix it
dancog said:
I'm not getting any results from Unbrickable Ressurector. Here's the message:
--------------------------------------------------------------------------
#SBL: GPSbl.bin LOCATION:0x40244000 tool:SMDK
1. Apply UnBrickable Mod
2. Remove then insert Device battery
3. Connect to computer via USB.
4. Click the Download Mode button
5. Download new software with Heimdall.
Begin Resurrection Sequence
Requesting Permission to access device
Please wait.... Uploading..
-------------------------------------------------------------
Hummingbird Interceptor Boot Loader (HIBL) v2.1
Copyright (C) Rebellos 2011
-------------------------------------------------------------
Exception in thread "Thread-2" java.lang.ClassCastException: [Ljava.lang.Object; cannot be cast to [Ljava.lang.String;
at com.AdamOutler.LowLevelUnBrick.Shell$1.run(Shell.java:191)
at java.lang.Thread.run(Thread.java:724)
--------------------------------------------------------------------------------------------------
jdk-7u40-linux-i586.tar.gz
Linux Slackware 14.0
UnBrickableResurrectorR40.jar
Click to expand...
Click to collapse
This is obviously a java error. Personally I've never run the unbrickable resurector on anything but Ubuntu. I would suggest that you create a bootable thumbdrive with Ubuntu...
UnBrickable Java errors
Meticulus said:
This is obviously a java error. Personally I've never run the unbrickable resurector on anything but Ubuntu. I would suggest that you create a bootable thumbdrive with Ubuntu...
Click to expand...
Click to collapse
Yes, Java looks like the culprit. So I've tried Ubuntu from a live dvd and got Java errors there too.
Then I tried permutations of (jdk07u40, jdk-6u25, and jdk-6u16) with Unbrickable (R36, R37, R38 and R40) on my Slackware 14 machine. They all gave the same error message. Googling that error message gives many millions of results, all highly specialized Java discussions which I don't understand.
The only positive at this point is that UnbrickableResurrector does see the device and starts the process. Then Java dies.
So I'm looking for another angle. I will try Ubuntu again; I've freed up a small partition and I'll install it there. I'm wondering if I need an older version of Java, to match the era when these devices were current. Maybe Resurrector isn't compatible with newer Java jdk??
Any other ideas?
dancog said:
Yes, Java looks like the culprit. So I've tried Ubuntu from a live dvd and got Java errors there too.
Then I tried permutations of (jdk07u40, jdk-6u25, and jdk-6u16) with Unbrickable (R36, R37, R38 and R40) on my Slackware 14 machine. They all gave the same error message. Googling that error message gives many millions of results, all highly specialized Java discussions which I don't understand.
The only positive at this point is that UnbrickableResurrector does see the device and starts the process. Then Java dies.
So I'm looking for another angle. I will try Ubuntu again; I've freed up a small partition and I'll install it there. I'm wondering if I need an older version of Java, to match the era when these devices were current. Maybe Resurrector isn't compatible with newer Java jdk??
Any other ideas?
Click to expand...
Click to collapse
Hmm... Lets start with why your using the resurrector in the first place...
What condition is your player in right now?
NOTE: I haven't used the resurrector in at least a year so...
EDIT: Almost forgot: At what point do you receive this error? When the app is starting up? After some action?
EDIT2: Here is the source code line for your error. http://code.google.com/p/hummingbir...com/AdamOutler/LowLevelUnBrick/Shell.java#191
Meticulus said:
OK, once you use the un-brickable resurector to get to download mode (don't reboot or anything), you need to flash a rom with boot loaders such as this one: http://www.4shared.com/zip/vxHoJ8E0/G70JKKE3_STOK_222RU_.html
If your partition tables are messed up, it may not boot but you should be able to get back to download mode without the resurector.... Hold power and volume down to try...
Give that a try let me know how it goes...
Click to expand...
Click to collapse
I must use the tar file, right?
With wich version of Odin?
Wich one of the 2 tar files inside the zipfile on the link?
My SGP is International with physical home button
Thanks man
mrlightman said:
I must use the tar file, right?
With wich version of Odin?
Wich one of the 2 tar files inside the zipfile on the link?
My SGP is International with physical home button
Thanks man
Click to expand...
Click to collapse
I can't remember, I think its the one that says "all low" or something like that...
EDIT: I used v1.81 of Odin..
Meticulus said:
I can't remember, I think its the one that says "all low" or something like that...
EDIT: I used v1.81 of Odin..
Click to expand...
Click to collapse
Right, thanks partner.
That's the one I unziped to reach the tar file.
Now Odin is not recognizing the device after running Unbrickable Resurrector and getting SGP into donwloading mode.
I tried to reinstall Samsung drivers using Zadig and it still doesnt recognizes SGP
Any ideas?
mrlightman said:
Right, thanks partner.
That's the one I unziped to reach the tar file.
Now Odin is not recognizing the device after running Unbrickable Resurrector and getting SGP into donwloading mode.
I tried to reinstall Samsung drivers using Zadig and it still doesnt recognizes SGP
Any ideas?
Click to expand...
Click to collapse
Zadig? What is that? Just use the device manager check for missing and non working drivers, you know, typical windows driver troubleshooting....
Meticulus said:
Zadig? What is that? Just use the device manager check for missing and non working drivers, you know, typical windows driver troubleshooting....
Click to expand...
Click to collapse
Ok, will try to have it working.
Zadig is a driver application wich comes along Heimdall
Every time we talk consider to recieve a thank you, even when I forget to write. It's how I feel. I really appreciate to have a partner to dialogue and help to acomplish this mission to bring back SGP to life.
Thanks
mrlightman said:
Ok, will try to have it working.
Zadig is a driver application wich comes along Heimdall
Every time we talk consider to recieve a thank you, even when I forget to write. It's how I feel. I really appreciate to have a partner to dialogue and help to acomplish this mission to bring back SGP to life.
Thanks
Click to expand...
Click to collapse
Don't use Heimdall, After you get the player into download mode. Take it to Windows and use Odin! If you are using Heimdall for Windows then uninstall it. Then reinstall windows drivers from Samsung or install Kies... Then use Odin.
Meticulus said:
Hmm... Lets start with why your using the resurrector in the first place...
What condition is your player in right now?
Hello out there. I'm back with good news, kinda. I'm now in the position of the original poster. I have a totally dead un-responsive do-nothing black box, BUT I am able to use the Resurrector and then Odin and I can successfully flash a pit, a bootloader and a rom. But then the Galaxy does not reboot.
This still feels like progress, since I couldn't even use the Resurrector a few days ago. I finally had to install Ubuntu Desktop on my machine. The Resurrector wouldn't run from Slackware or even from a Ubuntu live DVD.
So it looks like the sticking point for both the OP and I is the reboot.
Any further ideas are welcomed. Thanks for your interest.
Daniel
Click to expand...
Click to collapse
Meticulus said:
OK, once you use the un-brickable resurector to get to download mode (don't reboot or anything), you need to flash a rom with boot loaders such as this one: http://www.4shared.com/zip/vxHoJ8E0/G70JKKE3_STOK_222RU_.html
If your partition tables are messed up, it may not boot but you should be able to get back to download mode without the resurector.... Hold power and volume down to try...
Give that a try let me know how it goes...
Click to expand...
Click to collapse
Well, I did exactly what you said and did it using the same Odin version 1.81 and I got surprised when I saw Samsung Logo aparing but it got stocked on this screen for several minutes so I decided to unplug the USB cable and try to turn if off and on again. It still got stucked into the screen with Samsung logo and after about 5 minutes it turned off and will not turns on.
What to do know?
I think it might be to got out of battery but dont know what do next.
Remebering that my SGP is International version with Physical Home button.
Wait for guidance to next steps
Thanks a
mrlightman said:
Well, I did exactly what you said and did it using the same Odin version 1.81 and I got surprised when I saw Samsung Logo aparing but it got stocked on this screen for several minutes so I decided to unplug the USB cable and try to turn if off and on again. It still got stucked into the screen with Samsung logo and after about 5 minutes it turned off and will not turns on.
What to do know?
I think it might be to got out of battery but dont know what do next.
Remebering that my SGP is International version with Physical Home button.
Wait for guidance to next steps
Thanks a
Click to expand...
Click to collapse
I charged the battery for a while and was able to get it into download mode. I'm very happy with that but would like to know the exact steps I have to follow to bring it back to life now cause I really dont want to loose it again.
Thank you
Hi all together,
maybe someone can help me.
At first, sorry for my english - it is not my mother language
I got a broken Samsung Galaxy S3 GT-I9300 from a friend and I want to give it to my dad, because it has a big screen and is nice device, easy to use. if it works..
The problem is, it will not turn on. When I press the Powerbotton it just shows a white screen with black lines. It will not go in Recovery Mode, but it goes in Download Mode.
Since I am with Linux on my notebook, I tried to flash a recovery or a stockrom with heimdall. Heimdall will detect the device but can not recive the pit- file.
Is there someone who can give the correct pitfile together with the stockrom to me?
I don 't know what I need. There are so many different Roms and no pit-file???
What I can say about the device:
I think the device worked with Android 4.3. before it broke down, but I am not sure.
It is not rooted, in Download mode, it shows.
Odin Mode (in red letter),
GT-I9300,
No,
Samsung Official,
Custom.
Behind the accu is written: GT-I9300,
FCC ID : A3LGTI9300A,
SSN: -I9300GSMH,
RATED: 3,8 V - 2100mA,
IMEI: 353817/05/667558/0,
S/N: RV1C74KDMZK
On the mainboard is written on a white sticker: 071918,
T07A DTM,
AT0313647,
0AA2-A,
BOLF,
on a black plastic: Exynos
and on the other side of the mainboard: GT-I9300,
2012.03.21
I can 't do anything with all the numbers and letters.
Can someone help and give the right pit-file and firmware or recovery or anythink to me?
Thank you in advance.
Best regards
Kraul
Try flashing with different USB cables and USB ports.
audit13 said:
Try flashing with different USB cables and USB ports.
Click to expand...
Click to collapse
Thank you for helping.
I tryed different cable and different port, sometimes heimdall will not detect the device, sometimes it detects the device but when I try to download the pit-file heimdall will show up this:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
ERROR: Setting up interface failed!
Releasing device interface...
I found out something strange. When I ask my PC to show me what is connected to the usb port it says:
Bus001 Device 095: ID 04e8:685d Samsung Electronics Co.,Ltd GT-I9100 Phone (Galaxy SII) (Download Mode)
But I am pretty sure that it is a Galaxy SIII (GT-I9300).
What does this mean?
Thank you fpr helping.
Kraul
To confirm the model #, boot the phone into dowload mode and you can read the model # there.
Maybe try using a machine running Windows?
The pit file is not usually required for Odin or Heimdall are able to read the partition information from the phone.
Be skeptical, the drivers could be showing an old device if the drivers didn't change from s2 to s3..
Other scenario is it has been flashed with something from an s2..
Windows odin is more reliable. Even if you have to run a vm. Use Windows xp, vista or 7 and use odin on that.
shivadow said:
Be skeptical, the drivers could be showing an old device if the drivers didn't change from s2 to s3..
Other scenario is it has been flashed with something from an s2..
Windows odin is more reliable. Even if you have to run a vm. Use Windows xp, vista or 7 and use odin on that.
Click to expand...
Click to collapse
Thank you both for helping again.
I have a Windows maschine at work, but it is running with Windows 10.
Is there a special version of odin that I should take?
And what should I try to flash - I mean what is the easiest thing to flash, have you got a link for me where I can download what I need for flashing?
Thanks in advance again
Best wishes
Kraul
Windows 10 is a no-no because drivers arent the greatest. You can try by all means.
You need the stock firmware for that device. Can't link as i dont know the specs. Get the pit file for it just as a fallback plan. Get odin. Get kies3. Get drivers.
Put the phone in download mode and connect it the to pc.
Install the drivers either manually or via kies3.
*if you install kies3 you must uninstall kies3 and keep the drivers*
Run odin, select pda, find firmware, make sure erase nand is UNCHECKED, click start.
If no joy and the flash craps out then report back with the error. Preferably copy and paste the odin output window here.