Related
This morning (2011may27-0700 PST [pacific]), I received my 1st ever update from T-Mobile for my Galaxy S 4G. It told me "Congratulations," you have an update! or something like that, then told me I wouldn't be able to use the phone for 10min, I said OK, it rebooted into a white screen, applied an update (with progress bar), and said "Update is Failed", and rebooted. Upon reboot, I have a "low on space" notification and it stays up there in the menu bar, above. I don't have any extra apps, and don't know what to do.
Can someone walk me through finding where the space is suddenly used up? I'm really going to need some hand-holding on this. Thanks
Can someone tell me how to apply the update? If I go to "Settings" -> "Software update", it says "no firmware". As far as PC's go, I use Linux, btw
Has this update worked for others? What does it update you to? 2.3.x ?
I originally posted this in the wrong forum (Vibrant forum... my old phone), and I think the answer to #3 is that it updates to KD1. Thanks, ahead of time.
http://forums.t-mobile.com/t5/Samsu...for-our-Samsung-Galaxy-S-4G-users/td-p/839425
check that out. old news.
sorry the update failed, you'll need to look around the forums for a fix. if you tried the update while rooted and/or having messed with fota files or the system in any other way, it would explain why it failed.
good luck.
there are two other threads in here about the same thing.
I'm very interested in this comment as well, the exact same thing happen to me, I figured I couldn't download the update because I rooted my phone and have titanium backup, I moved what I can to sd and deleted what I thought was safe from internal. yet the space seems to still show as used on the internal.
Thanks, nodrogkam
I checked your link that confirms my comment (that this is an update to KD1), and am currently trying to install the Mini Kies, from the T-Mobile link. What is a fota file? Also, when you said to look around the forums for a fix, were you referring to my #1 issue (low on internal storage), or for my #2 issue (how to install on Linux)? Either way, it sounds promising that the answer is here somewhere. Thanks
nodrogkam said:
check that out. old news.
sorry the update failed, you'll need to look around the forums for a fix. if you tried the update while rooted and/or having messed with fota files or the system in any other way, it would explain why it failed.
good luck.
there are two other threads in here about the same thing.
Click to expand...
Click to collapse
Kies no-go on wine
just in case anyone else wanted to try, Samsung's Windows Kies software is a no-go on the latest WINE. It was worth a shot.
I'm still curious how to find out where that space got used up, and exactly what space it is referring to, though.
matsonfamily said:
Thanks, nodrogkam
I checked your link that confirms my comment (that this is an update to KD1), and am currently trying to install the Mini Kies, from the T-Mobile link. What is a fota file? Also, when you said to look around the forums for a fix, were you referring to my #1 issue (low on internal storage), or for my #2 issue (how to install on Linux)? Either way, it sounds promising that the answer is here somewhere. Thanks
Click to expand...
Click to collapse
FOTA files means : for over the air files. this was a chunk of memory reserved for such an update (KD1 in this case). Its why the phone had such little free internal memory.
KD1 actually resolves that issue by reducing FOTA file size.
Your low memory is probably because the FOTA space was taken up and probably additional space taken up to back up apps etc. But since the update failed, the files are just sitting there instead of being erased.
As far as i know, Kies only works with Windows. Though there's probably a workaround if you want to use it on Linux.
how do you clear the fota files
If you did the fota fix most likely the update replaced the fota files that were removed to give you room on the internal rom
Modded gingerbread theme
Whitehawks kd1 deodexed with modded green dialer,modded pull down menu (favorite color is green and favorite football team greenbay packers)
FOTA location?
cool, thanks for the info! WHOOO-HOOOOOOO! Deleting the /data/fota/* files brings back LOADS of space. THANKS!
That was my biggest concern. I'd post a howto on how I did it, but I'm not sure if my actions were the wisest! I may be a stranger to Android, but not to *nix.
Thanks again
nodrogkam said:
FOTA files means : for over the air files. this was a chunk of memory reserved for such an update (KD1 in this case). Its why the phone had such little free internal memory.
KD1 actually resolves that issue by reducing FOTA file size.
Your low memory is probably because the FOTA space was taken up and probably additional space taken up to back up apps etc. But since the update failed, the files are just sitting there instead of being erased.
As far as i know, Kies only works with Windows. Though there's probably a workaround if you want to use it on Linux.
Click to expand...
Click to collapse
reboot and i think u'll get back to the space before the update fail, but less space than you see now.
unless you followed or did the same procedure as the ones listed in the developer section of this forum.
Im curious ... and I hope its cleared up.
I know im not the only one that deleted the FOTA files and am of course rooted..... but how do I go about doing this update if I go on my mac and tried using kies mini and says not supported! Also do I replace the original FOTA files and hope that it may do the update?
IF someone has a way to resolve and/or walkthrough I know we would all appreciate it!
Thanks!!!
trying through VBox, to install updates
yeah, curious here, too. I'm in the process of installing windows on a VM, using VBox (Sun/Oracle's Virtual Box). I'm just wading through the several hour interactive process of apply updates just to be able to apply other updates, and rebooting after almost each one. I'll post here if I have any luck, and how I did it.
Lvnlegendinc said:
Im curious ... and I hope its cleared up.
I know im not the only one that deleted the FOTA files and am of course rooted..... but how do I go about doing this update if I go on my mac and tried using kies mini and says not supported! Also do I replace the original FOTA files and hope that it may do the update?
IF someone has a way to resolve and/or walkthrough I know we would all appreciate it!
Thanks!!!
Click to expand...
Click to collapse
I have an N8013 and I have been trying to go to 4.3 for a while. Like illusion rom... i've tried cwm a few versions even the latest, twrp, and even philz recovery as recommended and I even deleted the updater scripts as recommended. I for the life of me can not get past the zip file failing to flash. I've downloaded the rom multiple times, used odin to go back to completely stock, factory reset.... just about everything. There is one other dude tellin me to do this....
"I have a N8013, and deleting the assert and getprops works for me 100% of the time. However, it is important to note, two things. One you have to have the N8013 version of the ROM, which is labeled N80xx, and 2, when you go to install it after you have modified the file, you will get a validation error because the zip file will no longer match the MD5 validation, you have to install anyways. Other than that it works fine on my N8013, using CWM 6.0.3.1, running official CM 10.2."
But I dont know exactly what file he is talkin about. If ANYONE can help me out with this id be forever grateful.
First thing first. I'm guessing from what you don't understand is the MD5 validation.
So let me try to explain it. Doing an MD5 check, is basically checking the fingerprint of a file to the fingerprint posted. You get an MD5 sum by running it though a MD5 hashing program. Someone that knows the terms better then me will probably jump in and correct my terminology. But the best way of saying it is that by comparing MD5 sums, you are able to see if a file is unaltered.
Second, you'll want to make sure the file you download is compete and uncorrupted. So you run it though the hasher, and get the MD5 sum to check it against the posted numbers.
For "Illusion-v2.5.alpha-UNOFFICIAL-n8013.z" the MD5 Sum is: 95eb24cadc1a7721934a508e3ce97212
For "Illusion-v2.5.alpha-UNOFFICIAL-n8000.zip" the MD5 Sum is: 7789f71ca54647b43c352837702795a3
Now as for a hashing program, if you are on Windows, I would suggest a program called HashTab. http://implbits.com/
It puts the hashing into a tab so you can just right click the file, click Properties, and then "File Hashes"
So for the next thing that you need to do to make sure everything is good, is to check the MD5 sum of the file you download (unmodified) and make sure it is a good download. If all of that is good, then something else is going off.
I will note that right now I'm running the n8000 version on my n8013. Yes there are reasons I do that, even though the GSM hardware isn't in place. But using the n8000 version makes use of VoIP phones much easier.
Niscandia said:
First thing first. I'm guessing from what you don't understand is the MD5 validation.
So let me try to explain it. Doing an MD5 check, is basically checking the fingerprint of a file to the fingerprint posted. You get an MD5 sum by running it though a MD5 hashing program. Someone that knows the terms better then me will probably jump in and correct my terminology. But the best way of saying it is that by comparing MD5 sums, you are able to see if a file is unaltered.
Second, you'll want to make sure the file you download is compete and uncorrupted. So you run it though the hasher, and get the MD5 sum to check it against the posted numbers.
For "Illusion-v2.5.alpha-UNOFFICIAL-n8013.z" the MD5 Sum is: 95eb24cadc1a7721934a508e3ce97212
For "Illusion-v2.5.alpha-UNOFFICIAL-n8000.zip" the MD5 Sum is: 7789f71ca54647b43c352837702795a3
Now as for a hashing program, if you are on Windows, I would suggest a program called HashTab. http://implbits.com/
It puts the hashing into a tab so you can just right click the file, click Properties, and then "File Hashes"
So for the next thing that you need to do to make sure everything is good, is to check the MD5 sum of the file you download (unmodified) and make sure it is a good download. If all of that is good, then something else is going off.
I will note that right now I'm running the n8000 version on my n8013. Yes there are reasons I do that, even though the GSM hardware isn't in place. But using the n8000 version makes use of VoIP phones much easier.
Click to expand...
Click to collapse
Wow, thank you sir. No one has ever explained it to me like you did. I honestly appreciate it. I have a PC running windows 7 and I also have an iMac for my music. Not saying I completely understand how to do what your telling me but it puts in to a much greater perspective and for that, thank you. I know something is going wrong. This isn't my first rodeo but I definitely don't know how to change stuff around or dissect it yet. I started rooting and modifying about a year ago. Im a tech so in interests me. But I don't all that much time to dissect yet or understand what your saying exactly. I guess I just need a good download. Maybe I'll try the N8000 version instead. I don't care about the GPS and I use VOIP a lot more than I would GPS. I'll try that I guess. But thank you for the great response and for taking a moment to help a fellow androidian out.
Thought:
Could it be that im downloading the rom to my iMac, transferring to my pc via flash drive thats corrupting it somehow? I dont have hemidal or samsung drivers on my imac but it seems to download the files faster thats why im doing that. But when it finishes its a folder not a .zip so I transfer it to my pc and compress it with 7zip.
I think other people are getting the same error tho as well so maybe not..
RussellEstridge25 said:
Wow, thank you sir. No one has ever explained it to me like you did. I honestly appreciate it. I have a PC running windows 7 and I also have an iMac for my music. Not saying I completely understand how to do what your telling me but it puts in to a much greater perspective and for that, thank you. I know something is going wrong. This isn't my first rodeo but I definitely don't know how to change stuff around or dissect it yet. I started rooting and modifying about a year ago. Im a tech so in interests me. But I don't all that much time to dissect yet or understand what your saying exactly. I guess I just need a good download. Maybe I'll try the N8000 version instead. I don't care about the GPS and I use VOIP a lot more than I would GPS. I'll try that I guess. But thank you for the great response and for taking a moment to help a fellow androidian out.
Click to expand...
Click to collapse
Well to start, would be to download the Hashtab program and install it. That gives you easy access to the MD5 sums that you'll need so you can verify downloads.
Now on your Mac, I can only tell you how to do it from the command line. Open up a terminal window and type in without the quotes "md5 filename" replacing filename with the file you want the MD5 sum for.
Hashtab is a nice user friendly version, but it is a 3rd party program. Some people don't like those. So your choice there.
I can also tell you of the only real problem I have had so far with the Illusion Rom. Bluetooth Tethering doesn't work. Now what I mean by this is using Bluetooth on a Cell Phone to give Data to the Note is problematic. DHCP doesn't work til launched manually, and DNS servers don't work. So as long as you don't use Bluetooth Tethering for your Note you'll be fine. But if you use Bluetooth tethering ( a small group of people I know) might not want to upgrade quite yet.
RussellEstridge25 said:
Could it be that im downloading the rom to my iMac, transferring to my pc via flash drive thats corrupting it somehow? I dont have hemidal or samsung drivers on my imac but it seems to download the files faster thats why im doing that. But when it finishes its a folder not a .zip so I transfer it to my pc and compress it with 7zip.
I think other people are getting the same error tho as well so maybe not..
Click to expand...
Click to collapse
Now this explains the entire problem... Your Mac is unzipping the file, and probably destroying some of the symbolic links. Rezipping it still leaves the broken links and causes problems. I don't remember how to tell OSX (Mac) not to auto unzip files. But you'll need to do that or download it on your PC.
Niscandia said:
Well to start, would be to download the Hashtab program and install it. That gives you easy access to the MD5 sums that you'll need so you can verify downloads.
Now on your Mac, I can only tell you how to do it from the command line. Open up a terminal window and type in without the quotes "md5 filename" replacing filename with the file you want the MD5 sum for.
Hashtab is a nice user friendly version, but it is a 3rd party program. Some people don't like those. So your choice there.
I can also tell you of the only real problem I have had so far with the Illusion Rom. Bluetooth Tethering doesn't work. Now what I mean by this is using Bluetooth on a Cell Phone to give Data to the Note is problematic. DHCP doesn't work til launched manually, and DNS servers don't work. So as long as you don't use Bluetooth Tethering for your Note you'll be fine. But if you use Bluetooth tethering ( a small group of people I know) might not want to upgrade quite yet.
Now this explains the entire problem... Your Mac is unzipping the file, and probably destroying some of the symbolic links. Rezipping it still leaves the broken links and causes problems. I don't remember how to tell OSX (Mac) not to auto unzip files. But you'll need to do that or download it on your PC.
Click to expand...
Click to collapse
Dont you mean how to tell a mac how to autozip the files? But again thank you. That helps a lot.
RussellEstridge25 said:
Dont you mean how to tell a mac how to autozip the files? But again thank you. That helps a lot.
Click to expand...
Click to collapse
From how it sounds your Mac is auto-unzipping. You want the Mac to leave the downloaded zip file & leave it alone. Not to unzip & rezip it up. That is what is causing trouble, the unzipping and rezipping more then likely. So disable the "expand archives". Doing a quick search try reading up on it here to get Safari to behave. https://discussions.apple.com/thread/1483114?start=0&tstart=0
Niscandia said:
From how it sounds your Mac is auto-unzipping. You want the Mac to leave the downloaded zip file & leave it alone. Not to unzip & rezip it up. That is what is causing trouble, the unzipping and rezipping more then likely. So disable the "expand archives". Doing a quick search try reading up on it here to get Safari to behave. https://discussions.apple.com/thread/1483114?start=0&tstart=0
Click to expand...
Click to collapse
Thank you thank you thank you. You answered me exactly the way I needed to hear it. :good:
RussellEstridge25 said:
Thank you thank you thank you. You answered me exactly the way I needed to hear it. :good:
Click to expand...
Click to collapse
Just needed that key piece of info. That you where rezipping the file after using your Mac to download it.
Hope it installs this time around. But I would suggest learning how to check the MD5 sums as well. Doesn't hurt to be careful.
Niscandia said:
Just needed that key piece of info. That you where rezipping the file after using your Mac to download it.
Hope it installs this time around. But I would suggest learning how to check the MD5 sums as well. Doesn't hurt to be careful.
Click to expand...
Click to collapse
I completely agree. And I plan to. Didnt know it would be that easy. Again thanks man. But you completely helped me understand. I love learning about this when there is someone willing to teach.
I just downloaded the rom on my pc and its doing what it was before. I try putting the zip file in to my internal sd on my tablet and it says "CAN NOT COPY ITEM, The device has either stopped responding or has been disconnected"
It has not I can assure you. I've tried rebooting the tablet and pc when this happened before and still with no avail. I can copy other files to my tablet no problem. I've never ran into this before.
I cant even open the zip file or extract it to my desktop right now. Seriously, what the hell.
says windows cant open it cause the file is invalid. Must be that MD5 thing your tellin me to do. So now That im doing it on my windows pc should I install that program you mentioned?
RussellEstridge25 said:
I just downloaded the rom on my pc and its doing what it was before. I try putting the zip file in to my internal sd on my tablet and it says "CAN NOT COPY ITEM, The device has either stopped responding or has been disconnected"
It has not I can assure you. I've tried rebooting the tablet and pc when this happened before and still with no avail. I can copy other files to my tablet no problem. I've never ran into this before.
I cant even open the zip file or extract it to my desktop right now. Seriously, what the hell.
says windows cant open it cause the file is invalid. Must be that MD5 thing your tellin me to do. So now That im doing it on my windows pc should I install that program you mentioned?
Click to expand...
Click to collapse
I've had that problem before with windows. Not sure exactly what causes it, my guess is some data on the usb connection is causing it. Wrong driver or something.
When it happens changing USB ports, sometimes helps. Or you can use ADB to copy the file over. Not sure if you have used ADB before or not. The third way is to pull the Micro SD card out of your Note, and use an adapter (SD to USB) to put the file directly onto it from windows.
Only options I can think of off the top of my head for that problem. But it is one I've seen before.
Niscandia said:
I've had that problem before with windows. Not sure exactly what causes it, my guess is some data on the usb connection is causing it. Wrong driver or something.
When it happens changing USB ports, sometimes helps. Or you can use ADB to copy the file over. Not sure if you have used ADB before or not. The third way is to pull the Micro SD card out of your Note, and use an adapter (SD to USB) to put the file directly onto it from windows.
Only options I can think of off the top of my head for that problem. But it is one I've seen before.
Click to expand...
Click to collapse
Great ideas! I can try the sd one tomorrow. Day 3 lol. Wish Me luck
I may have missed this part, so I apologize. Is there any reason you can't just download it directly from the tablet, saving it to the sd card? It would assuredly cut down on the headache and potential file corruption during transfer between devices.
spycedtx said:
I may have missed this part, so I apologize. Is there any reason you can't just download it directly from the tablet, saving it to the sd card? It would assuredly cut down on the headache and potential file corruption during transfer between devices.
Click to expand...
Click to collapse
Already got cm10.3 up and running. The developer gave me a nightly build that had all the files taken out already. Had to download it twice but got it after putting it on my internal memory. Thank you for your help. The note 10.1 has a good community of people.
Hello everyone, I am in need of serious help. I have the Verizon Galaxy S3 4.3 and I have hardbricked the device. The phone is completely unresponsive.
I will attempt to give all the details of how I came to this without boring everyone to death with inane facts. So here goes; I first rooted the phone around November. Used Odin, had ClockworkMod installed and even managed to teach myself (with the help of folks like you all here), how to circumvent Verizon's pesky bootloaders (both unlocked and then relocked). Everything was running smoothly until I had left my phone unattended and plugged into my computer. The Verizon updater forced 4.3 on me leaving me scrambling to figure out to to regain root access. I did manage to gain the root access (although, I'm not 100% sure how so) and once again, everything was fine.
I began using TitaniumBackup to starting removing some bloatware and moving system apps to the SD card. I decided that I had no use for the "Samsung Link" app and I removed it. Once I returned from the reboot, I noticed that the icon for the bootloader was on the screen indicating that it was unlocked. I the did a quick search and app file for the "EZ Unlock" app. I installed the file, ran the program, did and reset and DEAD. Nothing. I've sat at the PC for the better part of the last 24 hours, have read hundreds of posts and tried more methods than I care to count. So far nothing has worked.
I'm desperately hoping that I will be able to find my answers by reaching out to the community as I have no funds to send my phone anywhere and I am past the warranty period. You guys are probably my last hope. Thanks in advance to anyone who helps out. It means a lot.
TwistedPoet said:
Hello everyone, I am in need of serious help. I have the Verizon Galaxy S3 4.3 and I have hardbricked the device. The phone is completely unresponsive.
I will attempt to give all the details of how I came to this without boring everyone to death with inane facts. So here goes; I first rooted the phone around November. Used Odin, had ClockworkMod installed and even managed to teach myself (with the help of folks like you all here), how to circumvent Verizon's pesky bootloaders (both unlocked and then relocked). Everything was running smoothly until I had left my phone unattended and plugged into my computer. The Verizon updater forced 4.3 on me leaving me scrambling to figure out to to regain root access. I did manage to gain the root access (although, I'm not 100% sure how so) and once again, everything was fine.
I began using TitaniumBackup to starting removing some bloatware and moving system apps to the SD card. I decided that I had no use for the "Samsung Link" app and I removed it. Once I returned from the reboot, I noticed that the icon for the bootloader was on the screen indicating that it was unlocked. I the did a quick search and app file for the "EZ Unlock" app. I installed the file, ran the program, did and reset and DEAD. Nothing. I've sat at the PC for the better part of the last 24 hours, have read hundreds of posts and tried more methods than I care to count. So far nothing has worked.
I'm desperately hoping that I will be able to find my answers by reaching out to the community as I have no funds to send my phone anywhere and I am past the warranty period. You guys are probably my last hope. Thanks in advance to anyone who helps out. It means a lot.
Click to expand...
Click to collapse
Ok, Can you boot to Odin mode (dowload mode)?
TwistedPoet said:
Hello everyone, I am in need of serious help. I have the Verizon Galaxy S3 4.3 and I have hardbricked the device. The phone is completely unresponsive.
I will attempt to give all the details of how I came to this without boring everyone to death with inane facts. So here goes; I first rooted the phone around November. Used Odin, had ClockworkMod installed and even managed to teach myself (with the help of folks like you all here), how to circumvent Verizon's pesky bootloaders (both unlocked and then relocked). Everything was running smoothly until I had left my phone unattended and plugged into my computer. The Verizon updater forced 4.3 on me leaving me scrambling to figure out to to regain root access. I did manage to gain the root access (although, I'm not 100% sure how so) and once again, everything was fine.
I began using TitaniumBackup to starting removing some bloatware and moving system apps to the SD card. I decided that I had no use for the "Samsung Link" app and I removed it. Once I returned from the reboot, I noticed that the icon for the bootloader was on the screen indicating that it was unlocked. I the did a quick search and app file for the "EZ Unlock" app. I installed the file, ran the program, did and reset and DEAD. Nothing. I've sat at the PC for the better part of the last 24 hours, have read hundreds of posts and tried more methods than I care to count. So far nothing has worked.
I'm desperately hoping that I will be able to find my answers by reaching out to the community as I have no funds to send my phone anywhere and I am past the warranty period. You guys are probably my last hope. Thanks in advance to anyone who helps out. It means a lot.
Click to expand...
Click to collapse
I doubt you'll bore us here, after all we dwell in the minutiae and tiniest of details for fun. Hmm, from what I see you have a bootloader hard brick since you tried using EZ Unlock. TW 4.3 prevents downgrading the rom to pre-4.3, flashing an unlocked bootloader, and installing a custom recovery using 4.1.2 methods. Your best option will be to try the steps detailed in this bootloader/hardbrick thread by SpyroDazee.
buhohitr said:
Ok, Can you boot to Odin mode (dowload mode)?
Click to expand...
Click to collapse
No. Once I used EZ Unlock, I was bricked.
SlimSnoopOS said:
I doubt you'll bore us here, after all we dwell in the minutiae and tiniest of details for fun. Hmm, from what I see you have a bootloader hard brick since you tried using EZ Unlock. TW 4.3 prevents downgrading the rom to pre-4.3, flashing an unlocked bootloader, and installing a custom recovery using 4.1.2 methods. Your best option will be to try the steps detailed in this bootloader/hardbrick thread by SpyroDazee.
Click to expand...
Click to collapse
I've looked at this particular guide the most. Where I fail there is the post calls to use Win32diskimager with the unzipped debrick.bin. I cant get Win32 to recognize the file and get error code 5: need permission (or something like that) and I run the program in Admin mode.
The only file I've found so far that Win32 does actually write to my SD card is Debrick-i535.img. http://angelfirenetworks.servegame.com/XDA/S3 Debrick IMG_s/
And then I can seem to make that run either.
I also have bricked S3 different circumstances but still hard bricked. Nothing I've tried here on xda or anywhere else has worked. I'm going to try this http://www.ebay.com/itm/281217379767?ssPageName=STRK:MEWAX:IT&_trksid=p3984.m1423.l2649 . It is probably the cheapest and easiest way.
TwistedPoet said:
I've looked at this particular guide the most. Where I fail there is the post calls to use Win32diskimager with the unzipped debrick.bin. I cant get Win32 to recognize the file and get error code 5: need permission (or something like that) and I run the program in Admin mode.
The only file I've found so far that Win32 does actually write to my SD card is Debrick-i535.img. http://angelfirenetworks.servegame.com/XDA/S3 Debrick IMG_s/
And then I can seem to make that run either.
Click to expand...
Click to collapse
It usually takes a few tries to get it to work, but if you really can't then you can always send it in for a jtag repair.
Mobile tech videos will do it, and there's someone on eBay who will do it for $30. Not too expensive.
Sent from my SCH-I535 using Tapatalk 2
TwistedPoet said:
I've looked at this particular guide the most. Where I fail there is the post calls to use Win32diskimager with the unzipped debrick.bin. I cant get Win32 to recognize the file and get error code 5: need permission (or something like that) and I run the program in Admin mode.
The only file I've found so far that Win32 does actually write to my SD card is Debrick-i535.img.
And then I can seem to make that run either.
Click to expand...
Click to collapse
So I just downloaded the debrick.zip and Win32 program from my link onto my laptop. I saved the unzipped debrick folder onto my desktop and found the debrick.bin once I switched the "Files of type" to "." then I just wrote the debrick.bin to a 512 mb sdcard with no problems. I'm not going any further cuz I have no need for this though. Are you saying that Win32 doesn't find the bin file at all?
Edit: I just ran it again and it worked a second time. My backup laptop is a 2006ish (maybe older) with a very outdated version of Windows and my sdcard has been unused since 2008. I don't know what else to tell you but it worked surprisingly well for me.
SlimSnoopOS said:
So I just downloaded the debrick.zip and Win32 program from my link onto my laptop. I saved the unzipped debrick folder onto my desktop and found the debrick.bin once I switched the "Files of type" to "." then I just wrote the debrick.bin to a 512 mb sdcard with no problems. I'm not going any further cuz I have no need for this though. Are you saying that Win32 doesn't find the bin file at all?
Edit: I just ran it again and it worked a second time. My backup laptop is a 2006ish (maybe older) with a very outdated version of Windows and my sdcard has been unused since 2008. I don't know what else to tell you but it worked surprisingly well for me.
Click to expand...
Click to collapse
The Win32 program finds the debrick.bin file when I switch to "." as well. But when I click WRITE, I get an error message and the file doesnt't write to the sd card. I'm using a HP Windows 7 Pro (2009) and I have a 32gb, class 10 sd card. I will run it again to double check.
Follow Up: I figured out what I was doing wrong. I was attempting to pull the "bin" file through Win32 and should have been pulling the "zip" file instead. I was able to write the debrick.zip file onto my SD card but wasn't (on first attempt) able to load my phone. Are there any other steps I may have misunderstood or overlooked?
TwistedPoet said:
The Win32 program finds the debrick.bin file when I switch to "." as well. But when I click WRITE, I get an error message and the file doesnt't write to the sd card. I'm using a HP Windows 7 Pro (2009) and I have a 32gb, class 10 sd card. I will run it again to double check.
Click to expand...
Click to collapse
Have you tried formatting the sdcard and running the program again? Set it to Fat32. I'm thinking it may be the sdcard and not the program itself but I'm not certain.
SlimSnoopOS said:
Have you tried formatting the sdcard and running the program again? Set it to Fat32. I'm thinking it may be the sdcard and not the program itself but I'm not certain.
Click to expand...
Click to collapse
VICTORY!!!!!!! - I made several mistakes in getting to this point but i have successfully retrieved my phone from it's previous HardBrick status. The steps it took me to get to this point were, make sure the sd card is formatted (FAT32) and empty, unzip the debrick.zip file, run the Win32 program, select the unzipped debrick.bin file and upload it to the F drive, then click Write. So, more or less, exactly what the instructions told me to do. Sometimes, it's the simple things that we're most often missing or not understanding.
THANK YOU to everyone and especially SlimSnoopOS for talking me through it and SpyroDazee for making such a comprehensive guide to work with. (although, it's simplicity was too complex for me. ).
TwistedPoet said:
VICTORY!!!!!!! - I made several mistakes in getting to this point but i have successfully retrieved my phone from it's previous HardBrick status. The steps it took me to get to this point were, make sure the sd card is formatted (FAT32) and empty, unzip the debrick.zip file, run the Win32 program, select the unzipped debrick.bin file and upload it to the F drive, then click Write. So, more or less, exactly what the instructions told me to do. Sometimes, it's the simple things that we're most often missing or not understanding.
THANK YOU to everyone and especially SlimSnoopOS for talking me through it and SpyroDazee for making such a comprehensive guide to work with. (although, it's simplicity was too complex for me. ).
Click to expand...
Click to collapse
Haha I love the enthusiasm my friend! Great way to start the weekend! All it took was another perspective, it's all good. You are most definitely welcome.
Edit: and while I'm here, if you have any inquiries about TW 4.3 or want to read up on some info then here's our TW 4.3 discussion thread:
http://forum.xda-developers.com/showthread.php?t=2575661
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
Haha I love the enthusiasm my friend! Great way to start the weekend! All it took was another perspective, it's all good. You are most definitely welcome.
Edit: and while I'm here, if you have any inquiries about TW 4.3 or want to read up on some info then here's our TW 4.3 discussion thread:
http://forum.xda-developers.com/showthread.php?t=2575661
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I'm not turning away knowledge. I'm still very new to this and obviously have a hard time following directions. I was looking at the next steps on that guide and am all ready confused enough to not do anything yet.
What is your phone doing after you inserted your sdcard and what size card and class were they. If you got it to go into download mode or some call it Odin mode by pressing volume down, home button and power button then your off to a great start to bringing your phone back from the dead. If only it worked for mine
Where did you get the debrick.zip file? Every time I download the file it comes as debrick.img not a .zip
Always_Jonezen said:
What is your phone doing after you inserted your sdcard and what size card and class were they. If you got it to go into download mode or some call it Odin mode by pressing volume down, home button and power button then your off to a great start to bringing your phone back from the dead. If only it worked for mine
Where did you get the debrick.zip file? Every time I download the file it comes as debrick.img not a .zip
Click to expand...
Click to collapse
Edit: My SD Card is a 32gb class 10. Once I got Win32 to extract the file properly, I put the SD card back into the phone, put the battery in, and plugged phone into computer. Pushed the power button and the phone came back on.
When you go to download that file with Win32, change the file type to "." - then you'll be able to select the debrick.zip
All files were obtained here - http://forum.xda-developers.com/showthread.php?t=2581166
I hope that helps.
TwistedPoet;49543890. Edit: My SD Card is a 32gb class 10. Once I got Win32 to extract the file properly said:
http://forum.xda-developers.com/showthread.php?t=2581166[/url]
I hope that helps.
Click to expand...
Click to collapse
Thanks I hope it works too. Am I supposed to change the file type of the debrick.img to debrick. and or change the file type in win32
Always_Jonezen said:
Thanks I hope it works too. Am I supposed to change the file type of the debrick.img to debrick. and or change the file type in win32
Click to expand...
Click to collapse
They did exactly what I posted, which was: unzip the debrick.zip, open Win32 and change the file type to ".", find the unzipped debrick folder and select the debrick.bin, and write to the sdcard.
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
They did exactly what I posted, which was: unzip the debrick.zip, open Win32 and change the file type to ".", find the unzipped debrick folder and select the debrick.bin, and write to the sdcard.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
As stated earlier when I download the debrick file it downloads as debrick.img not a zip file am I missing something
Always_Jonezen said:
As stated earlier when I download the debrick file it downloads as debrick.img not a zip file am I missing something
Click to expand...
Click to collapse
Did you brick BEFORE 4.3? I hovered over this link in SpyroDazee's post: "Debrick if you bricked before 4.3 OTA" and that's the only one that would download as an IMG. Press "Debrick if you took the 4.3 OTA" and it will download as a zip.
Or change the browser that you're using. I downloaded it using Chrome on my MBP.
Sent from my SCH-I535 using Tapatalk 4
I did brick on 4.1.2 and I am using chrome as my default browser
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 ?
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.