Hi All, New to this forum and have not found a resolve reading the threads so if someone could correct me that would be awsome.
I am trying to un-hard brick our samsung galaxy player 5.0 intl. It attempted to boot with a flat battery along time ago and has been a brick since. i have periodically kept it charged in case one day i find a resolve.
I have been attempting to use Unbrickable Ressurector but cannot even get it to load.
Initial process:
I have installed ubuntu on a spare laptop.
Installed Java through command line and verified the install.
Downloaded Unbrickable Ressurector from: (github) downloaded as a zip file. 'hummingbird-hibl-master.zip'
changed the zip file permissions to allow executable.
Right clicked an run with Java. But nothing happens. A little bit of hard drive noise but nothing comes up.
In the threads there is mention of running the .jar file but there is no .jar file in this package. I have unzipped and searched the folders to no avail.
I have even tried renaming the zip file to .jar which yeilds the same result as above.
I think it may be that i'm simply stupid or am i missing something?
Any help greatly appreciated.
I have just tried installing java 6 instead of java 8 in case there was a compatibility issue. Set default application to Java 6 runtime. Icon pops up in side bar after double click on 'hummingbird-hibl-master.zip'
then after 14 seconds icon disappears.
Not sure what else to try. I must be missing something obvious?
SymondoR said:
Hi All, New to this forum and have not found a resolve reading the threads so if someone could correct me that would be awsome.
I am trying to un-hard brick our samsung galaxy player 5.0 intl. It attempted to boot with a flat battery along time ago and has been a brick since. i have periodically kept it charged in case one day i find a resolve.
I have been attempting to use Unbrickable Ressurector but cannot even get it to load.
Initial process:
I have installed ubuntu on a spare laptop.
Installed Java through command line and verified the install.
Downloaded Unbrickable Ressurector from: (github) downloaded as a zip file. 'hummingbird-hibl-master.zip'
changed the zip file permissions to allow executable.
Right clicked an run with Java. But nothing happens. A little bit of hard drive noise but nothing comes up.
In the threads there is mention of running the .jar file but there is no .jar file in this package. I have unzipped and searched the folders to no avail.
I have even tried renaming the zip file to .jar which yeilds the same result as above.
I think it may be that i'm simply stupid or am i missing something?
Any help greatly appreciated.
I have just tried installing java 6 instead of java 8 in case there was a compatibility issue. Set default application to Java 6 runtime. Icon pops up in side bar after double click on 'hummingbird-hibl-master.zip'
then after 14 seconds icon disappears.
Not sure what else to try. I must be missing something obvious?
Click to expand...
Click to collapse
Did you miss something? Yes, You missed the date on the OP which was DEC 2011!. The links are out of date and so are the instructions.
1. In 2011 I think maybe ubuntu 11.04/12.04 was current. So you might have trouble getting 14.04 or 16.04 to work.
2. The link for the download of Unbrickable Resurrector is not right. You are looking for a file called "UnBrickableResurrectorR36.jar" which is apparently been expunged from the internet. The current link, that is redirected to github.com, leads to the source code that will "compile" UnBrickableResurrectorR40.jar"( or whatever the lasted version was). So unless you've got some java 6 skills...
EDIT: I managed to find 1 copy of the file here:
https://www.4shared.com/file/1Gx6ZSXjei/UnBrickableResurrectorR40.html
Thanks meticulus for taking the time to reply. That got me out of a sticking point. Greatly appreciated. I know i'm trying to revive old tech but i also don't like being wasteful by just throwing it away. I hope to revive it so my daughter can use it as a ipod alternative. Here's hoping.
Hopefully i don't need any further help and this thread will help any other late comers to fixing the old galaxy player 5.0.
Thanks again.
Hi Meticulus. Progress update: Unbrickable Resurrector R40 now functional.
Connect SGP 5.0 intl.
Device recognised.
S5PC110 Detected.
Clicked : Perform Resurrection - Download Mode
Begin Resurrection Sequence
Requesting Permission to access device
Please wait......Uploading...
This is far as the process goes. Device does not go into download mode. Could i be missing something simple again?
SymondoR said:
Hi Meticulus. Progress update: Unbrickable Resurrector R40 now functional.
Connect SGP 5.0 intl.
Device recognised.
S5PC110 Detected.
Clicked : Perform Resurrection - Download Mode
Begin Resurrection Sequence
Requesting Permission to access device
Please wait......Uploading...
This is far as the process goes. Device does not go into download mode. Could i be missing something simple again?
Click to expand...
Click to collapse
1. It's been quite awhile since I used this but I believe that I used it with ubuntu 12.04 LTS. So first make sure you use that version.
2. Make sure you are NOT using virtualization software such as virtualbox or vmware. Either use a thumbdrive, dualboot, or just install ubuntu natively.
3. You man need to set permission on the USB device in udev. Sort of like this: http://ptspts.blogspot.co.il/2011/10/how-to-fix-adb-no-permissions-error-on.html
Use lsusb to find the exact IdVendor
4. Launch the file in the terminal like this: java -jar UnbrickableRessurectorR40.jar . This may* give you more output to tell what is going on.
Hi Again Meticulus. thanks for you instruction. I have managed to make some more headway from your help.
I performed a new native install of ubuntu 12.04 LTS and Java 6
Now Unbrickable Ressurector appears to work. It recognises the device and after password prompt brings up the now in download mode screen on the GUI window. Although the samsung player screen stays black.
I have now also installed Heimdall Frontend in ubuntu and in the process of learning how to use it and acquiring the correct pit file and firmware. It appears to recognise the player at this stage.
Just to refresh it is a Samsung Galaxy Player 5.0 International 16GB. Made in Korea.
I have pit file: GB70-GalaxyPlayer-16gb.pit
also G70intl.pit
I am thinking the first is a safer bet.
Firmware: G70XXKPL_CL1105219_REV01_user_low_ship_HOME.tar.md5
and: CODE_GB70KRKPG_CL762569_REV01_user_low_ship_HOME.tar
Although heimdall expects tar.gz file extensions. so i'm doing something wrong again.
I'm going to sleep on it and re approach in the morning. (I'm on the other side of the planet in good old New Zealand)
If you have any further advise to offer on correct firmware for this device any help is most appreciated.
SymondoR said:
Hi Again Meticulus. thanks for you instruction. I have managed to make some more headway from your help.
I performed a new native install of ubuntu 12.04 LTS and Java 6
Now Unbrickable Ressurector appears to work. It recognises the device and after password prompt brings up the now in download mode screen on the GUI window. Although the samsung player screen stays black.
I have now also installed Heimdall Frontend in ubuntu and in the process of learning how to use it and acquiring the correct pit file and firmware. It appears to recognise the player at this stage.
Just to refresh it is a Samsung Galaxy Player 5.0 International 16GB. Made in Korea.
I have pit file: GB70-GalaxyPlayer-16gb.pit
also G70intl.pit
I am thinking the first is a safer bet.
Firmware: G70XXKPL_CL1105219_REV01_user_low_ship_HOME.tar.md5
and: CODE_GB70KRKPG_CL762569_REV01_user_low_ship_HOME.tar
Although heimdall expects tar.gz file extensions. so i'm doing something wrong again.
I'm going to sleep on it and re approach in the morning. (I'm on the other side of the planet in good old New Zealand)
If you have any further advise to offer on correct firmware for this device any help is most appreciated.
Click to expand...
Click to collapse
".tar.md5" or ".tar" file must be flashed with Odin in Windows but those files are archives that can be opened via the Archive Manager in Ubuntu and the files extracted. As I said it's been awhile and I'm just talking from memory so do your homework but, basically each file in the archive is a raw dump of the partition. So system.img is the system partition, cache is cache and so on (zImage is kernel) and can be flash via heimdall. I am not very familiar with heimdall front end but from the Terminal, the command is something like:
"heimdall flash --system system.img" ( <---real iffy on exact syntax, something close to that.)
DO NOT FLASH PIT FILES!!! ( I have bricked my device many times and have never had to do this and you shouldn't do it unless you are sure that you have muffed up your partition table!)
Odin is available here and the drivers for windows too but the last time I used them Windows 7 was the thing so...
Techically if you can use Heimdall or Odin with any success, you are already in "Download Mode" and you do not need the Resurrector.
The Terminal command "heimdall --print-pit is a good test. If it can connect to the device and print the pit file with out error then Download mode is working and you can flash a stock ROM with ODIN and as long as it's the right one, your golden...
Hi Meticulus, Here's a quick result of a pit print:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
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 receive PIT file size!
ERROR: Failed to download PIT file!
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
So I may have a bigger problem. Would that indicate a muffed partition? from what i have read elsewhere i may have a hardware failure which means RIP samsung player.
What originally bricked the device was an attempted boot with a dead flat battery. the device has never had any custom firmware flashed. Purely stock.
Will do some more research in the meantime.
SymondoR said:
Hi Meticulus, Here's a quick result of a pit print:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
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 receive PIT file size!
ERROR: Failed to download PIT file!
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
So I may have a bigger problem. Would that indicate a muffed partition? from what i have read elsewhere i may have a hardware failure which means RIP samsung player.
What originally bricked the device was an attempted boot with a dead flat battery. the device has never had any custom firmware flashed. Purely stock.
Will do some more research in the meantime.
Click to expand...
Click to collapse
I can be sure but i would say yes, that does point to a partition. The only way to repair you partition table is if you can get into a custom recovery.
Your only hope is if you can flash a custom kernel:
http://www.meticulus.co.vu/p/galaxy-player-5-beanstalk-install-from.html
You can also extract the zImage from the .tar or .tar.md5 file and flash the zImage (kernel) with heimdall sort of like this:
heimdall flash --KERNEL zImage .
The kernel has custom recovery in it and if you can boot into it, you can use the partition tools to straiten yours out.
You might need this:
https://www.youtube.com/watch?v=Uzu4uDTDL5k
and you might want to read through this entire thread:
https://forum.xda-developers.com/showthread.php?t=2398120
Meticulus said:
I can be sure but i would say yes, that does point to a partition. The only way to repair you partition table is if you can get into a custom recovery.
Your only hope is if you can flash a custom kernel:
http://www.meticulus.co.vu/p/galaxy-player-5-beanstalk-install-from.html
You can also extract the zImage from the .tar or .tar.md5 file and flash the zImage (kernel) with heimdall sort of like this:
heimdall flash --KERNEL zImage .
The kernel has custom recovery in it and if you can boot into it, you can use the partition tools to straiten yours out.
You might need this:
https://www.youtube.com/watch?v=Uzu4uDTDL5k
and you might want to read through this entire thread:
https://forum.xda-developers.com/showthread.php?t=2398120
Click to expand...
Click to collapse
Thanks again Maticulus. I have been through all of the above to no avail. The last thread was interesting and tried to repeat the process there to see it the partitions were messed up.
Used adb-shell. (On Windows terminal)after installing Android devalopment suite. but Shows no connected devices. The player shows as SEC S5PC110 test B/D in device manager requiring drivers. Even though I have installed the samsung drivers.
I've also tried to use the zImage previously. Heimdall front end will only allow me to add the extracted file after adding the pit file. But in the end fails to upload the pit file.
Sorry for the low detail as I have decided to give up on this one. I appreciate your input to get me this far. You certainly went above and beyond to help and for that I thank you.
hopefully there is something in here to help someone else in a similar situation.
Related
Hi,
I tried to follow some instructions on how to flash a custom rom on my galaxy tab 10.1 and unfortunately had to abort in step 2: step 1 was to put the device into download mode, step 2 was to use Odin to flash recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5. I used heimdall 1.3.1 to do it as I don't have any Windows nearby. Heimdall detects my device but loading the file mentioned above as a "Heimdall Firmware Package" fails with the following error:
"firmware.xml is missing from the package"
How do I proceed from here? I would like to have a different ROM because I bought my device in the US but live in Europe (Germany). Some apps like amazonmp3 dont work like this - not sure why but I believe it has to do with my credit card being German etc.
Any suggestions?
cheers
mathiase
Hi again, I just found a thread about running Odin in VirtualBox and I immediately tried it: I could pass the device through to a 32bit Windows XP and installed Odin drivers. Odin detected the device BUT THE WHOLE VM CRASHED when I started the process! Now my Galaxy Tab does not boot at all and tells me to attach it to Kies... PANIC!
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
Last night I was helping a friend put CM10.1 on his t-mobile samusung galaxy s2 phone(hercules), but while following the directions on cyanogenmod's website I thought I had soft-bricked his device. I did a lot of searching and found people saying they had similar problems, but no solutions. So I figured I'd post what got this device working again.
So after step 5, "heimdall flash --recovery recovery.img --no-reboot", the device would only reboot directly back into odin mode saying "firmware upgrade encountered an issue. please select recovery mode..." crap. The instructions didn't give any advice about what to do if this happened so I started doing some searching and people said that you could still you odin, but odin would crash every time I tried to run it. Then I found a website saying that heimdall doesn't work with t-mobile's S2, so I'm thinking crap crap now (note that the heimdall version in cyanogenmod's instructions does work for the tmobile s2... I'll get to that later). So I then tried to get kies to connect to it and do a full recovery, but kies wouldn't connect. The device drivers would fail to install for the MSM8x60 device.
So I spent a lot of time just trying to reset the to see if that would do something but to no avail.
So what finally worked?
I went back to the cyanogenmod instructions and followed the instructions to install the drivers with the zadig tool. Then just to see if the heimdall tool is actually communicating with the device I ran the command "heimdall detect", and that responded with "Device Detected". So that looked good. Then I looked at the command options within heimdall (since I was beyond following someone else's instructions by now), and saw the download-pit command and thought that it would be a harmless command to see if heimdall was actually communicating with the device. So I ran "heimdall download-pit --output test.pit" and it spit out a bunch of stuff including at the bottom
Ending session...
Rebooting device...
Releasing device interface...
And walla it reboots back into gingerbread and is working. I was then able to reboot into clockworkmod and finish the CM10.1 install with no problem.
Really I think the step 5 on the instructions just needs to be changed from
heimdall flash --recovery recovery.img --no-rebootto
heimdall flash --recovery recovery.img
Hopefully that helps someone else out there!
Hey all, had this guy running fine for a while, ticked the wrong setting in twrp and deleted everything. Previously used Casual with no issues. This is an i605 (Verizon Note 2)
Can use ODIN3 (1.85) to get it back to stock 4.2.2. VZWAMC3. Loads, fine.
Want to unlock so I am going the route of casual.
Tried on 3 diff comps, 2 windows 1 linux. Same errors each time,
Output from the linux box is here
pastebin dot com / RhAM2YPk (sorry I can't link since new user)
It's bootlooping afterwards, gotta jig it and odin it back to stock to be useable, blah, no fun
Note also tried the root66 ROM, Odin no likey. (maybe versioning or something else?)
I have a nandroid on my sdcard if I can get this rooted/twrp installed to go back to. I was doing them daily since I had been running cyanogen nightlies.
and ypeaxp
Ran it again @ work, linux mint box. Diff cable. Same result
pastebin dot com /VnGsjTE2 (sorry still cant post url's yet)
key lines seem to be
ERROR: Failed to confirm end of file transfer sequence!
ERROR: recovery upload failed!
Ending session...
ERROR: Failed to send end session packet!
Back to Odin and reflashing stock I suppose for now. Really curious to why this won't work... is there another method I can take to this?
In my own stupidity, panic, and lack of sleep over the past day, I realized my issue.
WRONG VERSION of CASUAL for current stock rom.
I hate when it's the small oversights, but then also at the same time am happy that I was able to fix it.
CASUAL is awesome, and I owe Adam some props and likely donations. Works beautifully in linux and windows.
Last time, windows, flawless,
This time, linux, and flawless.
How is it that XDA devs can make something cross platform that WORKS and most corp coders cant...
Just updating this thread in case anyone runs into it. Don't be dumb and miss the small stuff. Saves time and frustration.
So I'm trying to get my device back to stock so I can ship my device to someone I sold it too but somehow I'm running into issues.
I installed Terrasilent kernal and custom rom on my US 4.0 way back last spring and never had to connect my device to a computer since. Well now obviously I have to and am trying to do it off a new laptop I recently purchased.
My steps so have gone like this.
1. Downloaded and installed Samsung Drivers
2. Downloaded and installed C++ Redistrubiutable from: http://www.microsoft.com/en-au/download/details.aspx?id=30679
(I only got the bottom one. Did I need all 3?
3. Downloaded Latest Heimdall
4. Ran zadig and updated the one Samsung device that showed up
5. Ran Heimdall and loaded the pit and recovery files from this thread http://forum.xda-developers.com/showthread.php?t=1531850
But every time I get some sort of error.
The latest error being
Beginning session...
ERROR: Failed to begin session!
Releasing device interface...
After trying reinstalling drivers and such I've also ran into this error
error: failed to access device. libusb error: -12
Am I missing a very simple step? Somehow even though Heimdall won't flash anything I've also managed to get my device soft bricked.
Sadly I don't remember having such issues when I originally rooted my device and flashed it. Any ideas? I'd really love to get this device shipped out to the person it was sold to.
mewrius said:
So I'm trying to get my device back to stock so I can ship my device to someone I sold it too but somehow I'm running into issues.
I installed Terrasilent kernal and custom rom on my US 4.0 way back last spring and never had to connect my device to a computer since. Well now obviously I have to and am trying to do it off a new laptop I recently purchased.
My steps so have gone like this.
1. Downloaded and installed Samsung Drivers
2. Downloaded and installed C++ Redistrubiutable from: http://www.microsoft.com/en-au/download/details.aspx?id=30679
(I only got the bottom one. Did I need all 3?
3. Downloaded Latest Heimdall
4. Ran zadig and updated the one Samsung device that showed up
5. Ran Heimdall and loaded the pit and recovery files from this thread http://forum.xda-developers.com/showthread.php?t=1531850
But every time I get some sort of error.
The latest error being
Beginning session...
ERROR: Failed to begin session!
Releasing device interface...
After trying reinstalling drivers and such I've also ran into this error
error: failed to access device. libusb error: -12
Am I missing a very simple step? Somehow even though Heimdall won't flash anything I've also managed to get my device soft bricked.
Sadly I don't remember having such issues when I originally rooted my device and flashed it. Any ideas? I'd really love to get this device shipped out to the person it was sold to.
Click to expand...
Click to collapse
Did you installed the drivers while you were in download mode? Maybe this would solve your actual issues. Also if you used a different port, you need to reinstall the drivers once again AFAIK.
Hello there,
before getting into details: I am pretty new to the whole business of smart phones; so, if my request doesn't fit here ... please don't get too angry with; but tell me where else I could turn to.
In case this is a good place to ask my question; here we go:
I recently acquired a S4 mini (GT-I9195); currently runing Android 4.4.2; build number KOT49H.I9195XXUCOE4; and as subject says: I want to install cm 12.1; and I am getting nowhere.
I started with this wiki page wiki.cyanogenmod.org/w/Install_CM_for_serranoltexx
The wiki says:
Use heimdall to install the CM recovery image
Then, use that recovery image to install the actual CM build
And well, I am already failing with step 1.
My computer is running ubuntu 14.04; I first installed heimdall from the ubuntu repositories; and when following the instructions; I ended up with
heimdall ERROR: Failed to receive PIT file
Then I fetched the latest heimdall source from github; compiled ... and ran that; but result wasn't much different
heimdall ERROR: Protocol initialisation failed!
Then I tried to do everything with AndroidStudio / adb / fastboot.
I enabled USB debugging within the mobile phone ... and I could actually start an adb shell. I could also use adb to boot the S4 mini into recovery/download mode.
But when I do a "fastboot devices" then ... no devices are showing up at all.
I don't have a windows system; so I tried to get my VirtualBox windows to get it "talking" to the phone; maybe in order to use Odin instead of heimdall; but no luck there.
( I thought about using twrp ... and the wiki pages there basically talk about using Odin on windows)
Long story short: I am looking for the "easiest" way to get CM 12.1 on my S4 mini; preferably without rooting; and low risk of bricking ...
EDIT: with some more help from Uncle Google I figured how to setup my VBox Windows7 to run Odin.
I can start Odin (3.10.7) ... and trying this here: www.s4miniarchive.com/2013/11/how-to-install-twrp-on-samsung-galaxy-s4-mini-gt-i9195.html
The IMG is correct; it shows the MD5sum you can see here: forum.xda-developers.com/showthread.php?t=2449107
And, ah, when running Odin as adminstrator, I starts doing something; and PASSes.
I stop the mobile; and reboot ... and recovery is still showing me the old content?!
So, any idea, anybody?
Resolved
In the end, I got my VirtualBox to run with Odin successfully ... then installed TWRP ... and then figured that I need a different key stroke in order to startup recovery mode.
So, the important things I learned:
* heimdall really doesnt work with Galaxy S4 mini
* Odin (I tried 3.17) and TWRP do (where: Odin needs samsung mobile drivers; and you have to run it as admin!)
* there is a difference between download and recovery mode!