[Q] Trying to reflash with stock firmware using JODIN3 - Galaxy Tab 2 Q&A, Help & Troubleshooting

After fooling around with CyanogenMod, I decided that I want to put the stock firmware back on my P3113. So I acquired the firmware from here: hxxp://samsung-updates.com/device/?id=GT-P3113 (which I then unpacked) and JODIN3 (Linux64) release 1035. I've already installed Heimdall with the packages pointed to from hxxp://glassechidna.com.au/heimdall/.
I started JODIN3, pressed the PDA button, and gave it the file "HOME_XAR_P3113UEUCMK3_1978026_REV04_user_low_ship.tar.md5". It wants to get a pit file from the device. I let it do that and put the tablet back into download mode. Then I pressed "start". JODIN3 then complained that the firmware file was corrupt. I tried a few more times. The unzip program on my computer seemed satisfied that the zipfile was not corrupt. Tar seemed satisfied that the tar file within was not corrupt.
I then tried feeding JODIN3 the zipfile itself. That caused JODIN3 to ask to download a pit, which I allowed. I pressed "start" and then it complained that the pit file was corrupt.
After repeating the above several times, I tried again with the .tar.md5 file. That seemed to do something. The spew in the xterm in which I
started JODIN3 flashed the names of the six file contained within. The spew then kept printing stuff about "heimdall detect" confirming that a
device was attached. Nothing new was printed to the JODIN3 GUI. I let it sit there for 30 minutes. Nothing -- not even a complaint of
something being corrupt. Scrolling back in the xterm, I saw this:
Exception in thread "Thread-103" java.lang.OutOfMemoryError: Java heap space
at CASUAL.communicationstools.heimdall.odin.OdinFile.extractOdinContents(OdinFile.java:145)
at CASUAL.communicationstools.heimdall.odin.Odin.getHeimdallFileParametersFromOdinFile(Odin.java:50)
at com.casual_dev.jodin.JOdinController.getHeimdallCommandFromOdinPackageList(JOdinController.java:619)
at com.casual_dev.jodin.JOdinController.access$3300(JOdinController.java:53)
at com.casual_dev.jodin.JOdinController$13.run(JOdinController.java:570)
at java.lang.Thread.run(Thread.java:744)
[DEBUG]Run Heimdall from
DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
Now, the questions: Am I doing anything wrong here? Can somone suggest a known-good version of JODIN3? I quick check of my system gives me to reason to suspect I'm legitimately out of memory.
Using regular Odin isn't an option because I don't use Windows and I can't make it work with Virtualbox. I hear there are problems inherent to emulation that prevent Odin from working correctly there. Trying to run the plain jar file doesn't work because it complains that it needs a newer version of Java. I'm running OpenJDK7 and that seems to be what the Linux64 package uses. Someone, please help me out here.

dgriffi said:
After fooling around with CyanogenMod, I decided that I want to put the stock firmware back on my P3113. So I acquired the firmware from here: hxxp://samsung-updates.com/device/?id=GT-P3113 (which I then unpacked) and JODIN3 (Linux64) release 1035. I've already installed Heimdall with the packages pointed to from hxxp://glassechidna.com.au/heimdall/.
I started JODIN3, pressed the PDA button, and gave it the file "HOME_XAR_P3113UEUCMK3_1978026_REV04_user_low_ship.tar.md5". It wants to get a pit file from the device. I let it do that and put the tablet back into download mode. Then I pressed "start". JODIN3 then complained that the firmware file was corrupt. I tried a few more times. The unzip program on my computer seemed satisfied that the zipfile was not corrupt. Tar seemed satisfied that the tar file within was not corrupt.
I then tried feeding JODIN3 the zipfile itself. That caused JODIN3 to ask to download a pit, which I allowed. I pressed "start" and then it complained that the pit file was corrupt.
After repeating the above several times, I tried again with the .tar.md5 file. That seemed to do something. The spew in the xterm in which I
started JODIN3 flashed the names of the six file contained within. The spew then kept printing stuff about "heimdall detect" confirming that a
device was attached. Nothing new was printed to the JODIN3 GUI. I let it sit there for 30 minutes. Nothing -- not even a complaint of
something being corrupt. Scrolling back in the xterm, I saw this:
Exception in thread "Thread-103" java.lang.OutOfMemoryError: Java heap space
at CASUAL.communicationstools.heimdall.odin.OdinFile.extractOdinContents(OdinFile.java:145)
at CASUAL.communicationstools.heimdall.odin.Odin.getHeimdallFileParametersFromOdinFile(Odin.java:50)
at com.casual_dev.jodin.JOdinController.getHeimdallCommandFromOdinPackageList(JOdinController.java:619)
at com.casual_dev.jodin.JOdinController.access$3300(JOdinController.java:53)
at com.casual_dev.jodin.JOdinController$13.run(JOdinController.java:570)
at java.lang.Thread.run(Thread.java:744)
[DEBUG]Run Heimdall from
DeviceCommunicationProtocol:/usr/local/bin/heimdall detect
Now, the questions: Am I doing anything wrong here? Can somone suggest a known-good version of JODIN3? I quick check of my system gives me to reason to suspect I'm legitimately out of memory.
Using regular Odin isn't an option because I don't use Windows and I can't make it work with Virtualbox. I hear there are problems inherent to emulation that prevent Odin from working correctly there. Trying to run the plain jar file doesn't work because it complains that it needs a newer version of Java. I'm running OpenJDK7 and that seems to be what the Linux64 package uses. Someone, please help me out here.
Click to expand...
Click to collapse
Apparently Jodin3 does not support Stock Firmware flashing at this time...

spidergrafxxx said:
Apparently Jodin3 does not support Stock Firmware flashing at this time...
Click to expand...
Click to collapse
You are correct. I always use Heimdall Frontend to flash Samsung on Linux. OP, do you need a pit file?
Sent from my SGH-T989

cant flash a .tar.gz file
dgriffi said:
After fooling around with CyanogenMod, I decided that I want to put the stock firmware back on my P3113. So I acquired the firmware from here: hxxp://samsung-updates.com/device/?id=GT-P3113 (which I then unpacked) and JODIN3 (Linux64) release 1035. I've already installed Heimdall with the packages pointed to from hxxp://glassechidna.com.au/heimdall/.
I started JODIN3, pressed the PDA button, and gave it the file...
I then tried feeding JODIN3 the zipfile itself. That caused JODIN3 to ask to download a pit, which I allowed. I pressed "start" and then it complained that the pit file was corrupt.
After repeating the above several times, ...
Now, the questions: Am I doing anything wrong here? Can somone suggest a known-good version of JODIN3? I quick check of my system gives me to reason to suspect I'm legitimately out of memory.
Using regular Odin isn't an option because I don't use Windows ...
Click to expand...
Click to collapse
So, the last reply to this thread branch was nearly a year ago. I'm having identical difficulties. Every time I download the pit file from my Galaxy S3 and hit the start button I get the corrupt pit file error message. Additionally, I have an impossible time getting jOdin3 to pick up my phone after the reboot to pull the pit file. If this is a Heimdall shortcoming it makes the an impossibly useless utility for me, at least for the time being.
I'm running Ubuntu 15.04 (Vivid vervet? friends don't let friends use Windows...) with all the latest updates. I've downloaded and built Heimdall and Heimdall-frontend. The binaries are in my shell's PATH variable, as is that of the platform-tools folder for the android sdk. I have the latest java update from the oracle site, both x64 and i386 libraries.
Anyway, I guess I'm not really expecting a fix or help in this regard. This is more just sort of a status ping with regards to the issue. I'm going to go back to using Heimdall-frontend directly. I had to package the firmware I wanted to flash so I could use jOdin3 anyway. I just wanted to avoid the desmadre that happens sometimes when flashing firmware from Heimdall (seems to hang after trying to flash a modem partition, sometimes, and I'm not at all sure I can characterize the conditions of the failure). I'm trying to take my UCUFNE4 I747 firmware back to a T-Mobile T999UCALJ2 setup which purportedly enables the AWS/LTE 1700/2100 band AND unlocks the unit to T-Mobile (I'm a feeling a bit incredulous at this point....). And, yes, I've pulled the aboot.img file out of the package I'm installing. God forbid I step on the Samsung/Qualcomm/ATT locked primary bootloader and brick my second GS3 (8}
Hasn't seemed to be an issue doing this before, I took it back to DLK3 to see if I could get the hidden service menus back, unfortunately to no avail. At this point I just want to cut to the chase. I've spent a month of more than full time effort getting to the point I'm comfortable with what I'm about to do, although I still have nagging doubts and a feeling of uncertainty, lol. At this point I'm about ready to offer myself back to the development gods and take on some real work. I vowed I'd NEVER go back to being a software developer after the stock market crash of 2001 cost me my house et al and left me homeless (another long saga for another time and place)...
'nuf said, off to the races. See you on the other side of Heimdall
BTW, good work Adam, I am impressed! just chagrined that this won't serve my current purposes. peace out
one last thing, if anyone knows how I can change the ro.anyprop properties in the build props file so they stick (they didn't from a terminal emulator via the setprop command), please inform me. I want my phone to tell the world it's a(n aboriginal) TMO unit even though it's really a red-headed step child. Quality goes in before the label goes on....

riches2rags said:
So, the last reply to this thread branch was nearly a year ago. I'm having identical difficulties. Every time I download the pit file from my Galaxy S3 and hit the start button I get the corrupt pit file error message. Additionally, I have an impossible time getting jOdin3 to pick up my phone after the reboot to pull the pit file. If this is a Heimdall shortcoming it makes the an impossibly useless utility for me, at least for the time being.
I'm running Ubuntu 15.04 (Vivid vervet? friends don't let friends use Windows...) with all the latest updates. I've downloaded and built Heimdall and Heimdall-frontend. The binaries are in my shell's PATH variable, as is that of the platform-tools folder for the android sdk. I have the latest java update from the oracle site, both x64 and i386 libraries.
Anyway, I guess I'm not really expecting a fix or help in this regard. This is more just sort of a status ping with regards to the issue. I'm going to go back to using Heimdall-frontend directly. I had to package the firmware I wanted to flash so I could use jOdin3 anyway. I just wanted to avoid the desmadre that happens sometimes when flashing firmware from Heimdall (seems to hang after trying to flash a modem partition, sometimes, and I'm not at all sure I can characterize the conditions of the failure). I'm trying to take my UCUFNE4 I747 firmware back to a T-Mobile T999UCALJ2 setup which purportedly enables the AWS/LTE 1700/2100 band AND unlocks the unit to T-Mobile (I'm a feeling a bit incredulous at this point....). And, yes, I've pulled the aboot.img file out of the package I'm installing. God forbid I step on the Samsung/Qualcomm/ATT locked primary bootloader and brick my second GS3 (8}
Hasn't seemed to be an issue doing this before, I took it back to DLK3 to see if I could get the hidden service menus back, unfortunately to no avail. At this point I just want to cut to the chase. I've spent a month of more than full time effort getting to the point I'm comfortable with what I'm about to do, although I still have nagging doubts and a feeling of uncertainty, lol. At this point I'm about ready to offer myself back to the development gods and take on some real work. I vowed I'd NEVER go back to being a software developer after the stock market crash of 2001 cost me my house et al and left me homeless (another long saga for another time and place)...
'nuf said, off to the races. See you on the other side of Heimdall
BTW, good work Adam, I am impressed! just chagrined that this won't serve my current purposes. peace out
one last thing, if anyone knows how I can change the ro.anyprop properties in the build props file so they stick (they didn't from a terminal emulator via the setprop command), please inform me. I want my phone to tell the world it's a(n aboriginal) TMO unit even though it's really a red-headed step child. Quality goes in before the label goes on....
Click to expand...
Click to collapse
This thread is for the Tab 2, not S3. Please post in the correct forum for your device.
jrc2

jrc2 said:
You are correct. I always use Heimdall Frontend to flash Samsung on Linux. OP, do you need a pit file?
Sent from my SGH-T989
Click to expand...
Click to collapse
Hi, sorry if i resume the threat, I am trying to flash the origin firmware. If I have understand well it could not bi done with jodin3 on Mac ? I have to use another program ? Could you tell me more please ?

Related

[Q] Use Heimdall 1.3.0 to create compatable roms?

Hi unfortunately I'm on a mac and have been unable to use odin for obvious reasons. I came across a program called Heimdall, which you all know of. Well the program recently has been updated to 1.3.0 and in turn has introduced Heimdall Firmware Package format. See here: http://www.glassechidna.com.au/2011/devblogs/heimdall-suite-1-3-0-and-anti-squish-graphical-update/
My issue is whenever I go to load a package file, I've tried to use odin roms, it look like its about to work and then after it loads up you get a error saying "Firmware.xml Is Missing From The Package" obviously this package was not made to be used with Heimdall 1.3.0.
So can somebody here create a proper firmware.xml file and place it inside the rom package? I would but it's a bit too complicated for me to understand. Maybe a developer with the right knowledge be able to do this.
Thank you so much people
Not having a windows computer at my disposal really keeps me behind on all these updates lol
Run vmware and try odin
Sent from my SGH-T959V using XDA Premium App
dualkiller said:
Hi unfortunately I'm on a mac and have been unable to use odin for obvious reasons. I came across a program called Heimdall, which you all know of. Well the program recently has been updated to 1.3.0 and in turn has introduced Heimdall Firmware Package format. See here: http://www.glassechidna.com.au/2011/devblogs/heimdall-suite-1-3-0-and-anti-squish-graphical-update/
My issue is whenever I go to load a package file, I've tried to use odin roms, it look like its about to work and then after it loads up you get a error saying "Firmware.xml Is Missing From The Package" obviously this package was not made to be used with Heimdall 1.3.0.
So can somebody here create a proper firmware.xml file and place it inside the rom package? I would but it's a bit too complicated for me to understand. Maybe a developer with the right knowledge be able to do this.
Thank you so much people
Not having a windows computer at my disposal really keeps me behind on all these updates lol
Click to expand...
Click to collapse
If you can find a good, working heimdall package I can take a look at the firmware.xml file and figure out how it works for you.
FBis251 said:
If you can find a good, working heimdall package I can take a look at the firmware.xml file and figure out how it works for you.
Click to expand...
Click to collapse
The Heimdall Firmware Package format (and subsequently firmware.xml) is detailed in Heimdall's README. Refer to the Appendices.
dualkiller said:
So can somebody here create a proper firmware.xml file and place it inside the rom package? I would but it's a bit too complicated for me to understand. Maybe a developer with the right knowledge be able to do this.
Click to expand...
Click to collapse
The README contains instructions that explain how to build a Heimdall Firmware Package. You just need to fill out the "Flash" tab as if you were performing a custom flash (see the README). Then instead of pressing the "Start" button go to the "Create Package" tab and fill out the details there.
If you're not sure how the partitions and file names match you can go to the Utilities tab and run the "Print Pit" action. This will output the PIT information in a human readable format so that you can match partition names to their "default" filename. I say "default", because unlike Odin, Heimdall places no restriction on what filenames can be used.
jager555 said:
Run vmware and try odin
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
that is quiet bad idea.
sharljimhtsin said:
that is quiet bad idea.
Click to expand...
Click to collapse
:what: Dead thread resurrection
Sent from my Maybach s 4g
Help
Benjamin Dobell said:
The Heimdall Firmware Package format (and subsequently firmware.xml) is detailed in Heimdall's README. Refer to the Appendices.
The README contains instructions that explain how to build a Heimdall Firmware Package. You just need to fill out the "Flash" tab as if you were performing a custom flash (see the README). Then instead of pressing the "Start" button go to the "Create Package" tab and fill out the details there.
If you're not sure how the partitions and file names match you can go to the Utilities tab and run the "Print Pit" action. This will output the PIT information in a human readable format so that you can match partition names to their "default" filename. I say "default", because unlike Odin, Heimdall places no restriction on what filenames can be used.
Click to expand...
Click to collapse
Hi, guys. I'm a simple guy. I just want to update my phone.
As you can imagine, I want to click on something and hit next a few times and wait patiently while a progress bar tires to lower my anxiety level.
So far I have installed Odin on my windows virtual machine with no luck and now this Heimdall program so kindly made by the open source comunity.
I have not the brains, time, aptitude or inclination to read a README file nor the IQ to create an XML file, however well explained the tutorial might be.
Any chance anybody can help me hit "next" a few times and get my phone to upgrade without having to learn, understand or figureout anything?
I have a Galaxy Note (the old one)
Much obliged.
Oh jeeze...
Let me save you some pain. I won't comment on the "I don't have the time..." statement and, with luck, nobody else here will either.
You should post in the Galaxy Note forums -- they are probably in much better position to save you from your rush.
Before you do leave, you might want to read the "Before you flash anything..." sticky.
never mind
alessioaguirre said:
Hi, guys. I'm a simple guy. I just want to update my phone.
As you can imagine, I want to click on something and hit next a few times and wait patiently while a progress bar tires to lower my anxiety level.
So far I have installed Odin on my windows virtual machine with no luck and now this Heimdall program so kindly made by the open source comunity.
I have not the brains, time, aptitude or inclination to read a README file nor the IQ to create an XML file, however well explained the tutorial might be.
Any chance anybody can help me hit "next" a few times and get my phone to upgrade without having to learn, understand or figureout anything?
I have a Galaxy Note (the old one)
Much obliged.
Click to expand...
Click to collapse
I installed windows. Never mind. Thanks

[ROM] ROM for recovery G2X under the NVFLASH

ROM for recovery G2X under the NVFLASH
This method necessary!
If the device is not loaded and not firmware in other ways! (If you downloaded the wrong firmware in the device)
I took the unpacked program files KDZ and added to them NVFlash and created BAT file!
Download ROM: http://www.mediafire.com/?wfokxjxi7rfoaey
Mirror: http://www.megaupload.com/?d=C5LBU3DS
Download APX driver: http://www.mediafire.com/?k559zgjlqkd5ted
Installation Instructions:
Download both files
Unpack it to the C drive to their respective folder
Remove the battery
Hold Vol Up/Down (and keep them held)
Insert the USB cable
Install APX driver from the your APX folder
For windows 7(and vista? please confirm):
Open Device Manager in Windows and you should see "APX Device" listed with an error
Right click on the APX device
Select 'Update driver software'
Select 'Let me pick...'
Select 'Have disk'
Browse to directory you extracted the APX Driver
Select the *entire* 'APX Driver' folder
Accept any warnings, including the big red alert (you may need to disable UAC)
Now in Device Manager under 'USB Controllers' you should have an 'NVIDIA USB Boot-recovery driver for mobile devices'
If not, uninstall the driver, reboot, rinse and repeat
Unplug everything
Hold Vol Up/Down (and keep them held)
Insert USB cable
open your ROM folder:
Run Flash.bat file and wait for the process
After the logo appears on the LG phone
Unplug USB cable
Insert the battery
enjoy!
After that, I recommend to firmware device with help programms KDZ or LG Mobile Update
I'm confused as to what this is? I'm guessing stock rom flash through nv flash? Kind of like odin for samsung phones?
Sent from my LG-P999 using XDA App
Can't wait to check this out when I get home later. Regarding the kdz file, what exactly were you able to unpack from it? I've been able to extract 2 files (a very large .wbd file and a .dll file) but I couldn't figure out how to unpack them further, specifically the .wdb file.
ILUHA_89 said:
I took the unpacked program files KDZ and added to them NVFlash and created BAT file!
Click to expand...
Click to collapse
Can you post the DLL for the G2X so we can use the LG Utilities to unpack KDZ files for this device please. So far we have been unable to get the proper DLL that enables us to unpack these files. If you unpacked the KDZ you must have the DLL unless you used another method to extract the files from the KDZ. Please elaborate on how you accomplished this. Both phburks and I have been working on this and so far we have had no success.
Smallsmx3 said:
I'm confused as to what this is? I'm guessing stock rom flash through nv flash? Kind of like odin for samsung phones?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
It is for people that have mucked up their phones to the point where LG Updater and KDZ Flash are not possible. This can be caused by many issues including, but not limited to, people flashing the O2X baseband to a G2X device. This method is purported to flash the entire Gingerbread ROM at the lowest possible hardware level. Hopefully this method is legit, but nobody has confirmed they have done it yet with the exception of the OP. Yes it is similar to ODIN for the Samsung but operating at an even lower level. With the NVFlash capability Tegra2 devices are virtually unbrickable.
jboxer said:
Can you post the DLL for the G2X so we can use the LG Utilities to unpack KDZ files for this device please. So far we have been unable to get the proper DLL that enables us to unpack these files. If you unpacked the KDZ you must have the DLL unless you used another method to extract the files from the KDZ. Please elaborate on how you accomplished this. Both phburks and I have been working on this and so far we have had no success.
It is for people that have mucked up their phones to the point where LG Updater and KDZ Flash are not possible. This can be caused by many issues including, but not limited to, people flashing the O2X baseband to a G2X device. This method is purported to flash the entire Gingerbread ROM at the lowest possible hardware level. Hopefully this method is legit, but nobody has confirmed they have done it yet with the exception of the OP. Yes it is similar to ODIN for the Samsung but operating at an even lower level. With the NVFlash capability Tegra2 devices are virtually unbrickable.
Click to expand...
Click to collapse
You described it right!
This method has helped resurrect my device!
ZeroT| Demented said:
So the point of this utility if it works is to make the g2x un f***able like even if u do u can fix?
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Yes. It is almost as good as JTAG flashing the device. For Galaxy S devices using ODIN you still have to have the 'software download' mode working in the ROM and it is possible to brick a Galaxy S beyond the point of even getting this mode to be accessible leaving you the only way to fix the device through disassembling it and flashing via the JTAG pads. Using the NVFlash method you are flashing directly to the hardware through they Hynix flashing chip. I had another phone with a similar capability (I-Mobile i858 - Yuhua Touchstone device) and no matter how badly I F'd it up (I was developing custom roms for it) I had the similar low level flashing tool that could reflash the phone to stock so I could start over with a clean slate. If this method is legit, this is a big boon to the dev community for this device.
jboxer said:
Can you post the DLL for the G2X so we can use the LG Utilities to unpack KDZ files for this device please. So far we have been unable to get the proper DLL that enables us to unpack these files. If you unpacked the KDZ you must have the DLL unless you used another method to extract the files from the KDZ. Please elaborate on how you accomplished this. Both phburks and I have been working on this and so far we have had no success.
It is for people that have mucked up their phones to the point where LG Updater and KDZ Flash are not possible. This can be caused by many issues including, but not limited to, people flashing the O2X baseband to a G2X device. This method is purported to flash the entire Gingerbread ROM at the lowest possible hardware level. Hopefully this method is legit, but nobody has confirmed they have done it yet with the exception of the OP. Yes it is similar to ODIN for the Samsung but operating at an even lower level. With the NVFlash capability Tegra2 devices are virtually unbrickable.
Click to expand...
Click to collapse
After trying to firmware device with program KDZ or LG Mobile Update in folder C: \ ... \ Aplication Data \ folder appears "LGMOBILEAX" which contains the firmware files!
That's All
ILUHA_89 said:
After trying to firmware device with program KDZ in folder C: \ ... \ Aplication Data \ folder appears "LGMOBILEAX" which contains the firmware files!
That's All
Click to expand...
Click to collapse
So you got them after the LG Updater extracted the KDZ into its component files. phburks and I didn't get that far as we didn't want to connect our already updated devices to the updater. To get to the point you did where you could grab the individual files you would have had to click the start update button. Good work.
I have 7-zip on my computer but I am unable to open up the file I just downloaded. Can you put it in another format and upload to megaupload or mediafire please? I don't want to go through that Russian site again as I got an invalid download. Also, please post the baseband file as a separate download.
jboxer said:
So you got them after the LG Updater extracted the KDZ into its component files. phburks and I didn't get that far as we didn't want to connect our already updated devices to the updater. To get to the point you did where you could grab the individual files you would have had to click the start update button. Good work.
I have 7-zip on my computer but I am unable to open up the file I just downloaded. Can you put it in another format and upload to megaupload or mediafire please? I don't want to go through that Russian site again as I got an invalid download. Also, please post the baseband file as a separate download.
Click to expand...
Click to collapse
I downloaded the 7-zip file to the sdcard on my phone but I won't be home to try opening it for several hours because I'm at seaworld. Lol
Hopefully you guys can get this sorted out. Sounds promising so far.
phburks said:
I downloaded the 7-zip file to the sdcard on my phone but I won't be home to try opening it for several hours because I'm at seaworld. Lol
Hopefully you guys can get this sorted out. Sounds promising so far.
Click to expand...
Click to collapse
I won't be able to look at it until tomorrow as it is 11:31 p.m. here and time to go to bed. :-O ZZZzzzzz
How about posting a mirror???? the site will not let me download.... unless i visit a sponsor and purchase something... lol
i'll try it out and report back
........... Works like a charm
here mirror link
http://www.megaupload.com/?d=C5LBU3DS
What we really need is for someone to tell us how to create the config files for NVFlash so we can flash the baseband only. The new baseband is there and named 'P999_MDM.bin' if I am remembering correctly. No reason to flash an entire ROM when all someone wants is the updated baseband. If we can get the older baseband file also this tool could be used to revert the baseband also, if someone wanted to do that.
web_ninja said:
How about posting a mirror???? the site will not let me download.... unless i visit a sponsor and purchase something... lol
Click to expand...
Click to collapse
You don't have to buy anything. You just click on one sponsor site and it opens a new window. Thirty seconds later it will enable a download link. You need to click download two or three times if I remember correctly. I am at work now. I can mirror it in about ten hours if nobody else has done it yet. I looked at the files briefly and it looks legit.
Is this supposed to have a command interface? Or are you still typing in commands yourself?
I edited a cap!
Changed link to Mediafire
omarsalmin said:
Is this supposed to have a command interface? Or are you still typing in commands yourself?
Click to expand...
Click to collapse
Good question - that is what I am looking for rather then having to mess with the nvflash commands directly.
Update - this setup is similar to Paul's stock ROM recovery setup on modeco.com. As with his, you only have to "Run Flash.bat file and wait for the process". When I could not get off of the LGupdater screen by any other means, I ran this file from his post and it ran flawlessly - but of course I ended up with a 990's device. I tried to get back with other tools and firmware, but was never able to do it.
If this works OK, you would be able to restore your data, apps, or a nandroid and you are back in business.
I spent a week trying to restore my original (and best device as it turns out), so I am not going to fool with this right now myself. I did compare the config files from bot Paul's and this firmware and they are different - which looks real promising, as they are different.
HELP! I tried to use this and the tool failed, now I am getting ZERO response from the device. I can't even boot to APX. I'm freaking out right now!
EDIT: I managed to get the process restarted and the phone is in the process of rebooting. Hoping for the best.
EDIT 2: Phone booted up and it was all restored but for some reason the baseband was not updated :\
Did you run by using the flash.bat file? Did you hold volume up and down for the entire flash process?
Sent from my LG-P999 using Tapatalk
AimanF said:
HELP! I tried to use this and the tool failed, now I am getting ZERO response from the device. I can't even boot to APX. I'm freaking out right now!
EDIT: I managed to get the process restarted and the phone is in the process of rebooting. Hoping for the best.
EDIT 2: Phone booted up and it was all restored but for some reason the baseband was not updated :\
Click to expand...
Click to collapse
Did you have old of new baseband on before flashing? What was the state of your G2X before running this?
UPDATE: It appears that this works - but would like to 100% confirm. After all the disasters that occurred from running the LGupdater tool, this would be an important fix and should be stickied at some point. Current members know of the updater problems, but new buyers and member may not - so many may still have this problem down the road.
Therefore, I believe this is an important enough item to bring to closure and make readily available.
U saved my phone's life
THANK YOU THANK YOU
followed instructions restored completley to stock just like how i got phone out of box 2 weeks ago.
I was running eaglesblood v8 and had altered the vold.fstab file to switch mounts
from sdcard to internal and after that point i rebooted and media scanner said damaged sd card well i figured it just to be like an extension of a permission of sorts. and thought if formated it would the paths would switch no problem.
im actually kind of having a hard time rembering exactly what steps i did take to **** it up royally. but went into clockwork 5 to flash another rom from internal storage or same i cant rember now and did factory reset then all hell broke loose .
couldnt mount nothing except for system i tried formating sd card even though i dont have one probally ended up formating internal lol. formated system,
re flashed all recoverie versions including stock. i was getting so mad i called google HA by the way they got some pretty good music when u have to hold.
only thing i didnt try was to load up a rom on sd card and mount that but i really doubt it would have worked and plus i couldnt even use phone to do it lol
i need to go buy drive saved me some serious cash I would say this should be enough confirmation!!

[Q] Heimdall ROMs?

[whoops - tried to update and blew away my original. Sorry!]
I've run into some problems using Unbrickabe Resurrector with my (modded but currently bricked sgs4g.
If I do the following, I can get my Unbrickabe-modded sgs4g into download mode from a hard brick
install / startup Unbrickabe Resurrector (ubuntu box)
then at the phone
unplug USB
remove battery
replace battery
plug USB in
back at the PC, click 'Resurrect' the moment Unbrickabe Resurrector shows that it's detected a S5PC110 (be quick!)
My current issue is that, if I unplug the USB, even with a battery in, the phone drops out of download mode, goes back to being hard bricked (lsusb shows nothing if I plug it back in)
...and I can't find a for-Heimdall ROM for this phone. There are some one-click, but these fail, due to the downloaded PIT being different and re-partition not being specified.
So, got a pointer to a for-Heimdall ROM (2.3.x preferred), or a way to get one-click to repartition?
Thanks!
bobkoure said:
I've run into some problems using Unbrickabe Resurrector with my (modded but currently bricked sgs4g.
So, on to Heimdall - only there don't seem to be any Heimdall 2.3.x ROMs.
Click to expand...
Click to collapse
It's my understanding that Heimdall is an open source alternative to ODIN, which means you should be able to flash ROMs with it fine. I've not used it, though, but I'm sure there's something in the forums about it.
So, a bit more reluctantly, on to Odin. Got a copy of sgs4g-OfficalGB2.3.6-NOCIQ-Edition.zip from this forum (Raver's work if I remember correctly).
I put the phone in dl mode (adb reboot download) and on a windows xp box, ran Odin, specified PDA and this ROM. It reported FAIL.
Click to expand...
Click to collapse
That is a CWM-flashable ROM. You shouldn't have done that from ODIN. That's why it failed.
Sigh
Re-tried a couple of times. No luck.
The phone had the 'shoveling andy' and 'do not turn off' warning
Well, eventually, I had to shut it off (what do you do?) - and it hard bricked.
I then moved the phone to a linux box with Unbrickable Resurrector installed.
The phone is detected as a S5PC110 - which is good - for about five seconds. Not long enough to enter my password, so I ran this logged in as root (I'm also enough of a Linux noob to not know how to sudo a .JAR file).
And... so long as I have a cursor over the 'Perform Resurrection' button, I could plug in the USB, get detected as a S5PC110, click the button and get a 'success' dialog box - and the graphic in Unbrickable Resurrector turns into 'shovelling andy'. If I run lsusb, the device now reports as a Samsung phone. Good!
I then tried installing / running a 'one click' from bhundven to get back to stock.
It failed - and the phone stopped showing up in lsusb.
OK, back to Unbrickable Resurrector, do the same routine - only now it shows a success dialog box, but NO 'andy shovelling', and lsusb shows nothing at all.
From the name of the library being loaded, I guessed that Unbrickable Resurrector might have been picking up the one-click library (both were \tmp).
So I rebooted, let Linux clear \tmp, and tried again.
Still the same issue with Unbrickable Resurrector (says it succeeded but no download mode).
And here I'm stuck.
Any suggestions?
Thanks!
PS: sorry for being so wordy, but I'm not sure which parts of this are important for the problem I've got and which are not. And I still may have missed something important. I'd be glad to add whatever's needed, just ask.
Click to expand...
Click to collapse
Being wordy is a good thing Help me understand the current state of the phone, though. Can you get it into download mode? If so we can probably ODIN a ROM onto it and get you going again.
My current state is I'm in download mode but can't disconnect from the Ubuntu box, so it's Heimdall (which I'd like to use if I can, anyway).
The one-click stuff http://forum.xda-developers.com/showthread.php?t=1358498
looks to be using Heimdall one-click - and so does the Unbrickable Resurrector (just from looking at what gets left in /tmp).
When I try to run the one-click (after running rm -r /tmp/rootH* BTW, as the two apps seemed to getting crossed up - but maybe not) I get
Local and device PIT files don't match and repartition wasn't specified!
And my phone drops out of download mode and I then need to re-run Unbrickable Resurrector as above.
I'm appending the output from the one-click, if that's of any help.
Thanks!
%%%%%%%%%%%%%%%%%%%%%
Operating System: Debian Based i686
Found Heimdall Version: v1.3.1
Connect your device in Download Mode to procede.
Device Connected. Awaiting package preparation.
SMS-KJ6 (v0.0.2d) Stock-Rom with Bootloaders UVKJ6 is ready for your device.
Repartition was requested but bootloaders are not to be flashed.
Omiting Bootloaders.
KERNEL RECOVERY FACTORYFS DATAFS CACHE MODEM
Heimdall v1.3.1, Copyright (c) 2010-2011, 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...
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: 0
Downloading device's PIT file...
PIT file download sucessful
Local and device PIT files don't match and repartition wasn't specified!
Ending session...
Rebooting device...
Re-attaching kernel driver...
Device not connected.
%%%%%%%%%%%%%%%%%
BTW, yes, I see
Repartition was requested but bootloaders are not to be flashed.
Omiting Bootloaders.
...but the 'flash bootloader' option is greyed out.
I hear ya on staying with Heimdall. I'm just not really knowledgeable of it. I guess I need to learn
I'm downloading the one-click you're trying to use so I can see what it looks like, does, etc. It might take me a few (downloading, gotta reboot into Linux, mount Windows, etc.) but I'll get back to you as soon as I can.
---------- Post added at 01:06 PM ---------- Previous post was at 12:13 PM ----------
Yeah, I'm not totally sure man. We need someone that's Heimdall smart to help us out here.
I read through some of the one-click docs, the one-click page by Adam (the creator of the one-click Heimdall), but I don't want to throw something at you that might not work or make it worse.
When you run the .jar, the files are extracted to a directory in /tmp that is prefixed with your Linux user name+HeimdallOneClick+a random suffix. So all of the files you would need to manually try to flash with Heimdall are there if you can get the right command from someone to flash from the command line.
Sorry I wasn't able to help, though.
I made this for heimdall a while back. Try it it might work:
http://sourceforge.net/projects/tea..._kh2_with_kg4_kernel_heimdall.tar.gz/download
Extract the 7zip file and load the tar with heimdall. I'm not sure if the command line version can load heimdall firmware packages, but I know the frontend does so consider using that.
It should get you on KH2, and it comes with bootloaders, from there you can just get into download mode and flash KJ6. I'll get around to making a heimdall version of stock KJ6 eventually though.
Thanks! I'll give it a shot as soon as I get home (had to run off to a client who's having probs with a win 2k8 server).
At this point, I'm not too worried about trying something that might mess me up. I've been hard bricked three or four times now, and, now that I have a notion of what's needed, I can get back to d/l mode.
I was looking at the Heimdall doc pack earlier today; building the xml file it needs (looks like it's basically a manifest) looks fairly straightforward.
I'll report back...
bobkoure said:
Thanks! I'll give it a shot as soon as I get home (had to run off to a client who's having probs with a win 2k8 server).
At this point, I'm not too worried about trying something that might mess me up. I've been hard bricked three or four times now, and, now that I have a notion of what's needed, I can get back to d/l mode.
I was looking at the Heimdall doc pack earlier today; building the xml file it needs (looks like it's basically a manifest) looks fairly straightforward.
I'll report back...
Click to expand...
Click to collapse
Yeah kind of annoying to do it by hand. I was looking into it also, but the frontend builds it for you. The file I linked you to comes with the xml file it built.
I saw that option in the frontend. You just point it at an Odin ROM and tell it to build the XML? Doesn't sound totally right as I'm pretty sure Heimdall expects everything in a single file (no hierarchy) and Odin's the other way.
Have to look at it later...
As a side issue, why do folks stick with Odin? Is there some functionality it has that Heimdall doesn't?
bobkoure said:
I saw that option in the frontend. You just point it at an Odin ROM and tell it to build the XML? Doesn't sound totally right as I'm pretty sure Heimdall expects everything in a single file (no hierarchy) and Odin's the other way.
Have to look at it later...
As a side issue, why do folks stick with Odin? Is there some functionality it has that Heimdall doesn't?
Click to expand...
Click to collapse
My only reason is because it was the first program I found when trying to flash my first ROM. I've stuck with it as I've not had a reason to not use it, you know? I need to get Heimdall smart though as I've read it has more/better/easier functionality.
Fortunately dorking around with my phone has renewed my interest in Linux again. I'm getting back up to speed there & wanting to dig into Android a bit. Now if I could just get the kids to take care of themselves.....LOL
Yeah, I just recently got back to Linux. Was a unix guy in the '70's, got hooked on PCs (all assembler at the time) and have only been back sporadically.
I installed Ubuntu 11.10 to do this - that UI seems a bit... not ready for prime time. Ah, well.
BTW, if you're in the Boston area, I have a client who's getting rid of six or seven p4 boxes. They'd make IMO fine linux boxes. Want one, or several?
You should try ubuntu 10.04. The UI's been going downhill since.
Not in that part of the country, but thanks I only used with Ubuntu here and there. I'm currently running Fedora and it's not bad. The UI on this is a bit different. Given that you're from the UNIX world you probably are like me and appreciate the command line better, anyway. Then again, maybe I just like doing things the hard way. LOL
It gets annoying when the UI makes it hard to use the command line. Switching apps in the latest ubuntu has been like that for me. I only use it in a virtual machine but it's nice to have it there when I need to work with tar files. Never liked using the windows commandline, even with cygwin. It feels so old.
No Joy.
I have had the phone repeatedly in download mode:
'andy shovelling' on screen
lsusb shows a samsung phone
From Heimdall, I can download my PIT file, but whether I use this file or the one with the ROM (with repartition enabled) I get communications errors.
Either PIT failed no EOF (sorry, didn't write this one down) or ERROR: failed to receive response.
Beats me what's going on in there. This behavior makes me wonder if I have a bad uart. Hoping it's a software issue...
BTW, should I be able to read a PIT as a text file? I tried with the two I downloaded from the phone, and they're not readable. Or maybe these don't have EOFs - does that matter in linux?
Thanks for all the help so far!
You should be able to see filenames as plain text inside a pit file, followed by binary data. For example, the first few bytes of my PIT say IBL+PBL and boot.bin followed by more ascii characters with null bytes.
Most of it is filled with null bytes though.
Do you have a different USB cable you can try to flash with? You should try it.
I've tried a few USB cables with the same results.
Sounds like the PIT files I have in my phone are bad - or aren't downloading, in spite of what Heimdall thinks.
[edit]
not just different usb cables, but all the different usb ports on the linux box
[/edit]
I'm wondering if I should re-ask this question, but with a title something like "unrecoverable SGS4g with unbrickable mod", and the current state of things - or should I just change the title of this one (if that's even do-able)? Or is either of those things considered 'rude' here at xda?
The more I look at this the more I think, for whatever reason, Adam's Unbrickable Resurrector isn't getting the entire HIBL.bin loaded, or something like that's going on. His app shows 'success' one time in five or six tries, and a large proportion of these are white-screen bricks. In either case, it's a download mode that doesn't download. On a semi-positive note, it's got me grovelling through the code to hibl.bin, with an ARM reference manual. It's a pretty cool architecture, actually. I used to write assembler for both the 8086 and the 6502, so I can sort of stumble through it.
bobkoure said:
I'm wondering if I should re-ask this question, but with a title something like "unrecoverable SGS4g with unbrickable mod", and the current state of things - or should I just change the title of this one (if that's even do-able)? Or is either of those things considered 'rude' here at xda?
The more I look at this the more I think, for whatever reason, Adam's Unbrickable Resurrector isn't getting the entire HIBL.bin loaded, or something like that's going on. His app shows 'success' one time in five or six tries, and a large proportion of these are white-screen bricks. In either case, it's a download mode that doesn't download. On a semi-positive note, it's got me grovelling through the code to hibl.bin, with an ARM reference manual. It's a pretty cool architecture, actually. I used to write assembler for both the 8086 and the 6502, so I can sort of stumble through it.
Click to expand...
Click to collapse
I just had to comment on that...6502 assembler. I was teaching myself that on my Commodore many moons ago.
Many moons indeed...

[Q] Am I bricked? :(

My infuse when turned on goes to a screen that looks like phone ! pc with the message "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". So this happens even when I try and go to download mode or recovery mode. Basically as soon as I hit the power button. I'm really freaking out. It was rooted and I was doing following this link: http://forum.xda-developers.com/showthread.php?t=1613523
Then the problems started when my computer didn't recognize the phone in download mode. and then it was recognized so I started the Odin flash. Then it froze at cache.rts (I believe that's what Odin said, I can't get to it anymore)...So I uninstalled and reinstalled the drivers and did it again and it got to factoryfs.rfs before it froze there for a really long time. So I unplugged it and tried to do GTG Ultimate Unbrick...but I can't get the .zip file to open. My computer keeps telling me "Can Not Open ____ as archive". I re-downloaded it and same result. Is there anything I can do to save my phone? I'm a real idiot and this kind of stuff always happens to me no matter how much I read up on something and make sure I'm doing it right. I would really appreciate a little help though, thanks!
I actually got it downloaded and followed Rammstein874's video on youtube on how to do it and I am once again stuck on factoryfs.rfs :-(
What can I do at this point? It is still stuck at the Phone-!-PC screen when I try to go to download mode. Please help, I'm starting to get pretty worried about this...
When your screen is phone!computer, that's an alternative version of download mode. You can either use ODIN or heimdall back to stock. Just plug it in via usb, allow odin/heimdall to recognize it and start flashing.
This is correct....if you see those pic on your phone that is a form of download...i would run the one click method...
sfgiants2010 said:
Rammstein874's video on youtube
Click to expand...
Click to collapse
Can you PM me the link to Rammstein874's video? I didn't realize he still had this, and I've since updated my packages and how-to.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
jscott30 said:
Can you PM me the link to Rammstein874's video? I didn't realize he still had this, and I've since updated my packages and how-to.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Lemma know if that's the one..pm sent...
Sorry I was at work all day.
This is the video link I used: http://www.youtube.com/watch?v=y1HgcZrYR_4
I am also looking at the following one-click method posts:
- http://forum.xda-developers.com/showthread.php?t=1331381
- http://forum.xda-developers.com/showthread.php?t=1524081
* I used the above link (or tried) and it didn't seem to work either. I downloaded Heimdall Suite for Windows 64bit and then installed the drivers and plugged in my phone in download mode. But then I was unable to get it started...I used the "Stock_SGH_I997_UCLB3_Repartition-One-Click.jar" file I found on mediafire (because all of these posts link to mediaupload which is no longer working). Anyway, so I tried to run Heimdall-frontend.exe on windows and once it opened up I connected my phone (nothing turns green like the post says) and hit browse. I chose the jar file aforementioned and it said "tar header contained invalid file size."
So if someone could point me toward a more up to date thread if I'm using the wrong one and kind of explain to me how to get around the other problem I'm having with the jar file then I would be forever appreciative
Not sure what you did...not saying you did something wrong but here is what I do, below are how i perform using qkster's method...
The USB + Volume Down + Volume Up Method: Download mode (Noticeable by an Android robot digging with a shovel) is reached by taking everything out (Battery, SIM, MicroSD). plug in the USB cable to your computer and phone then putting in battery at the same time Holding the volume buttons both up and down, (Don't press the power button at all in this method).
How to INSTALL:
1. Put your phone into Download Mode.
2. If you have not used Heimdall, you will need to set up the driver for device recognition.
3. Once your device is connected, the DEVICE STATUS should show: CONNECTED. The long FLASH bar will also turn on for flashing.
4. Click on the FLASH button. (In my opinion: I recommend that you do this in a safe environment. Do not disturb your phone will flashing this firmware. Turn off Antivirus. Do not run any other programs, upload/download/youtube/burning DVD etc)
5. Once it has completed, your phone will reboot. You will hopefully see the ATT logo and reboot into STOCK UCLB3.
6. If it did not work, you will have to put it back into DOWNLOAD mode and reflash a second time, with the FLASH BOOTLOADER box checked. This is more likely if you never had proper Gingerbread bootloaders on your phone, if you are coming from FROYO or if you never had Odin a Gingerbread leak to get your bootloaders.
download this file for your one click to stock...and using above directions...
once that is done and you want to put CWM mod on for flashing a custom ROM, same directions to get in to download mod...
download this file to use the one click to put CWM mod on your phone
here is the link where i took all this...
http://forum.xda-developers.com/showthread.php?t=1524081
Right, I did those things from that link itself. I think the problem is actually with how I'm using Heimdall. I downloaded the suite version from here: http://www.glassechidna.com.au/products/heimdall/
I also downloaded Microsoft Visual Studio C++. So I feel like it should be working...but the problem comes when I hit browse to attach the jar file you linked to. It says the "tar header file size was incorrect"...so am I doing something wrong in the way that I'm attaching the jar file to go back to stock? Could you or someone else please confirm that process and/or check the jar file for me to make sure it's still up-to-date? Sorry for the trouble, I'm just not sure what I can do at this point if I can't get Heimdall working. I can't flash after I attach the jar file with the error message either, it doesn't recognize my phone when it is attached in download mode (which is coming up just fine now without the phone!pc thing for some reason).
sfgiants2010 said:
Right, I did those things from that link itself. I think the problem is actually with how I'm using Heimdall. I downloaded the suite version from here: http://www.glassechidna.com.au/products/heimdall/
I also downloaded Microsoft Visual Studio C++. So I feel like it should be working...but the problem comes when I hit browse to attach the jar file you linked to. It says the "tar header file size was incorrect"...so am I doing something wrong in the way that I'm attaching the jar file to go back to stock? Could you or someone else please confirm that process and/or check the jar file for me to make sure it's still up-to-date? Sorry for the trouble, I'm just not sure what I can do at this point if I can't get Heimdall working. I can't flash after I attach the jar file with the error message either, it doesn't recognize my phone when it is attached in download mode (which is coming up just fine now without the phone!pc thing for some reason).
Click to expand...
Click to collapse
why are you using these other programs...idk,
I just click on the one click file it an executable design to open and run itself...you say attach the jar file...why the suite version of heimdall...?
did you download the links i provided and just use those...?
sfgiants2010 said:
Right, I did those things from that link itself. I think the problem is actually with how I'm using Heimdall. I downloaded the suite version from here: http://www.glassechidna.com.au/products/heimdall/
I also downloaded Microsoft Visual Studio C++. So I feel like it should be working...but the problem comes when I hit browse to attach the jar file you linked to. It says the "tar header file size was incorrect"...so am I doing something wrong in the way that I'm attaching the jar file to go back to stock? Could you or someone else please confirm that process and/or check the jar file for me to make sure it's still up-to-date? Sorry for the trouble, I'm just not sure what I can do at this point if I can't get Heimdall working. I can't flash after I attach the jar file with the error message either, it doesn't recognize my phone when it is attached in download mode (which is coming up just fine now without the phone!pc thing for some reason).
Click to expand...
Click to collapse
Is your phone still stuck on the phone-!-pc ?
did you read the last post he had regarding the actual heimdall program suite...
not sure what he had going on...I believe he has download mode capability...
thx ''Goshujin-sama'' qkster
Yeah..that's where I wasn't sure what sf was doing.
the jar file is self executable. When you click on the jar file, there is a load up delay.
Then should be be ready.
You then hook up the phone.
I've not seen in tar header file size error.
Sf should not be trying to stick the 1-click file into heimdall front-end.
It's a single self executable jar file..the is no other dependencies...the only other situation I can think of is maybe putting the 1-click jar file onto a different PC and try running it there.
qkster said:
Yeah..that's where I wasn't sure what sf was doing.
the jar file is self executable. When you click on the jar file, there is a load up delay.
Then should be be ready.
You then hook up the phone.
I've not seen in tar header file size error.
Sf should not be trying to stick the 1-click file into heimdall front-end.
It's a single self executable jar file..the is no other dependencies...the only other situation I can think of is maybe putting the 1-click jar file onto a different PC and try running it there.
Click to expand...
Click to collapse
that's when I started to question him on these other programs...due to the one clicker is self sustained as a exe...idk...but believe he log off...i will monitor and holler at you if required thank you...
Oh man I had no idea...I was so mixed up by trying to educate myself with so many posts about using Heimdall. I thought I had to download Heimdall separately and attach the jar file or something. But okay so I ran the one-click. It failed the first time (expected) and then I checked the flash bootloaders box and hit flash again. Then it stopped at installing drivers and prompted me to install the drivers on the following prompt. So I did that and then it said installed drivers successfully and I hit close. Then nothing happens. So what do I do at this point? I'm probably being an idiot again but I really appreciate you guys trying to help me out. And I hope you realize I'm trying my best to not waste anyone's time.
The device status was a green Connected before I started by the way. At this point what I do? It seems to just break at the installing drivers part...?
It should of rebooted it self the phone...
Btw you are not wasting my time...wife is watching cup cake wars...so ....rather help you...lol
sfgiants2010 said:
Oh man I had no idea...I was so mixed up by trying to educate myself with so many posts about using Heimdall. I thought I had to download Heimdall separately and attach the jar file or something. But okay so I ran the one-click. It failed the first time (expected) and then I checked the flash bootloaders box and hit flash again. Then it stopped at installing drivers and prompted me to install the drivers on the following prompt. So I did that and then it said installed drivers successfully and I hit close. Then nothing happens. So what do I do at this point? I'm probably being an idiot again but I really appreciate you guys trying to help me out. And I hope you realize I'm trying my best to not waste anyone's time.
The device status was a green Connected before I started by the way. At this point what I do? It seems to just break at the installing drivers part...?
Click to expand...
Click to collapse
Once the connected bar is on, you click flash. It should complete it's routine. the phone reboots. you should click on the boot loader box. you disconnect. let it finish. set it back into donwload mode and flash again.
you can try different usb port or data cord or different pc
Plus you have my master...qkster here...cuz you lost me on the programs you were using...so i called in the jedia master!
As long as your screen has that Phone! Computer sign, it's not bricked yet. I recommend you to search some how to videos online so you can see the exact instructions on how to use heimdall because it's that easy. If possible maybe one of our awesome contributors can make a how to video for heimdall.
I believe he is tracking now qkster is providing....thx

[Q] All links down, need T839UVKJ2 SK4G stock rom

so after looking for 3-4 hours i'm convinced that almost all the links for files related to the SK4G are expired/down/DL limit reached. i had to wipe my HDD and can't find my backup anywhere!?!? if anyone has the stock firmwares (any and all) could you pretty pretty please send them to me? i'm stuck in a buggy version of glorious overdose and just need my phone to work right again. respond for e-mail or just post ***NEW*** link in this thread.
P.S. so when the mods say "wrong thread" or "duplicate" i looked i searched and found nothing newer than 2013 so i started a fresh one......... that and i just signed up and it keep telling me "NO" in what seemed like the correct forum.
P.S.S i'm assuming there's legal reasons but whats up with a file repository on or at least paired with XDA to hold all the files posted here. shooting in the dark but maybe Kimdotcom will provide a mega account to serve as a repo?!?!?!?
I have the One-Click KG2 ODIN Java app that may be able to restore your SK to t839-Sidekick4G-UVKG2. Here's the README:
If you brick your phone, well you're lucky because it can't get any easier to fix. This is pretty much a one-click version of ODIN that is OPERABLE AND EXECUTABLE on ANY operating system that has Java installed. Self-explanatory, but if you don't have Java installed yet, you probably should go get it installed now.
(Credits go to Ayoteddy for the following post) :
To get into download mode (if you can't) pull the battery out of your phone, the USB cord (if connected), the SIM card, and the SDCard. Now...in a position where your one hand is able to access the Trackball and - volume key, hold them both at the same time and with your other free hand, insert the battery, after a second or two, you should see an Android on screen with a logo saying DOWNLOADING..you're ready to advance.
After you install Java, double-click the .jar file in this folder.
Hit "flash" and if all is well, it'll work without any hassles and you'll be back to the stock ROM like the day you got your Sidekick (factory reset).
If it says driver was not found, a window will popup with an administrative prompt if you are running Windows 7, allow it to run.
On the new Zadig window, go to Options>List all devices.
You should now see SAMSUNG COMPOSITE DRIVER, make sure the box to the immediate right says WinUSB and then hit the install button.
You should be on stock after performing these steps...if not and YOUR MODEM fails to upload, check "Flash Bootloaders" and the modem should flash just fine and you'll be back on stock ROM soon enough.
Thanks to AdamOutler for Heimdall!
His thread is here if you want to thank him properly!
http://forum.xda-developers.com/showthread.php?t=1350060
I also have Odin3+v1.61 with sk4g pit. Let me know if you want me to upload these.
marathonjon said:
I have the One-Click KG2 ODIN Java app that may be able to restore your SK to t839-Sidekick4G-UVKG2. Here's the README:
I also have Odin3+v1.61 with sk4g pit. Let me know if you want me to upload these.
Click to expand...
Click to collapse
Please re-upload these to sammobile.com, samsung-firmware.org, MEGA, Android File Host, or similar where the files can live on longer.
Sorry, I got rid of my SK a couple years ago and all the files that went with it.
marathonjon said:
Sorry, I got rid of my SK a couple years ago and all the files that went with it.
Click to expand...
Click to collapse
Is there anyone out there that still has this? Please re-upload.

Categories

Resources