I got in a SK4g for my wife intent on upgrading her current phone. I own a 4g myself, and have Rooted/ROM'd it with no issues, we we thought it best to get her the same phone for ease of use/manipulation.
I got the phone in and used superoneclick to root it, then went through the process of putting CWM in place and installing GenericGinger_2.0_SK4G. The process ran smooth as glass (as expected) until it got to reboot. On reboot it hung up on the sidekick screen. After about an hour of waiting I pulled the battery and restarted the machine.
It came back up in recovery mode with the stock recovery (blue) text. Since then I haven't been able to get it to do anything but restart into that recovery screen. Odin doesn't see the phone in download mode and t839-Sidekick4G-UVKG2-One-Click does nothing. It shows it uploading, reboots the phone, and I'm back at the blue text. flashing the bootloaders with One-Click shows success on everything *except* uploading the bootloaders. If I tell it to re-install packages I get a 'cannot validate signature' response. I've tried using android commander to push CWM's recovery file to the phone and get 'permission' denied.
I've done a lot of searching on this site, trying most suggested fixes I've come across with no luck.
what can be done with this phone to get it back in operating condition?
Thanks in advance!
try installing kies odin wouldnt see my phone until i installed it
Kies installed and Odin saw the phone. excellent, thanks!
now, the next issue... lol
I used Odin to push KD1OdinSTOCK onto the phone. it's doing more than it was (going to the initial sidekick screen then dumping to recovery). Now it'll load through the sidekick and samsung splash screens, then reset and do it again. The same thing happens when I tried StockKG2ODIN. I'm using the sk4g.pit that I pulled from this site, could that have anything to do with it/is there another one around that I could try? Anybody have thoughts or ideas on what to do next? I've tried using t839-Sidekick4G-UVKG2-One-Click again, but it nuked the drivers kies put into place and dropped the phone back to what it was doing before.
okay, I did some light reading of this thread here
and followed the directions closely. I also went through sduvick's list of things to do with the following results:
Black screen, no logo.
1. Get into download mode by using VolDown+Touchpad+Power
2. flash full sk4g.tar.md5 as posted.
device will boot through the logo and splash screens, then repeat. note: if I leave the USB cable plugged in on reboot it will go to the battery screen, otherwise it just boot loops.
_________________________________
logo only
1. Download mode
2. Flash full package
device boot loops
_________________________________
Can't flash recovery/boot/sbl
1. Download mode
2. use PIT only, run with repartition checked
3. reboot/reDownload mode
4. run the full image in Odin.
PIT only returns a black screen on the device. running the full image in afterward returns to the boot loop.
_________________________________
Anything else
1. Download mode
2. Full tar.md5 flash in Odin
3. Ask if it doesn't work
okay, so I'm asking...
I'm still able to boot into recovery mode (blue text).
I've noted a bit of strange behavior when trying to boot into download mode. holding vol down + trackball + power does nothing. however, if I plug the phone in while powered down while holding down the trackball it'll boot into download mode, no power or vol down required.
If you can't flash with Odin, you may have a hardware problem.
Judging from your issue with installing Kies, you had a driver problem previously.
Seems that you are bumbling in the dark here. Once again, people need to be better prepared to Odin their devices before they start modding them.
In fact, getting Odin working should be the first thing a person should do with their phone after rooting and installing CWM.
Anyhow, try a different version of Odin. If that doesn't clear up your problem, I suspect some bad blocks in your flash memory are responsible here. It's a dorment issue that would really only be a problem when you flashed the device. If that's the case, you have a new paperweight.
Good luck.
i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda
I don't think the problem is that I can't flash with Odin, but that the device isn't loading the ROM that's flashed. poking around in the filestructure with android commander after a fresh load shows that the system makes it onto the phone.
Speaking of poking around with Android Commander, I've noted that the device is software rooted, but not hardware rooted. the default.class file shows ro.debuggable set at 0 where it should be 1. this is keeping me from just pushing the CWM recovery onto the system and restoring the backup I made before getting into this mess. Anybody want to help me pull/edit/flash the image to change that?
As for a driver issue, that's a good possibility given that the one-click uses a driver set, kies mini uses another, kies has a different one yet and we (as a community) started screwing with the t839's using vibrant drivers. I've got them all. thusfar the only drivers I've found that work with both flavors of Odin I have (1.61 and 1.85) would be those that came with the Kies (thanks for the tip pmp326).
On bumbling in the dark, yes, yes I am. There isn't much of an instruction manual for Odin past what's written here, and 90% of that is 'put your phone in download mode, connect Odin, plug the pit in pit and the tar in PDA make sure only auto-reboot is checked and hit start'. to be honest I haven't had to use the program previously as the stock one-click actually worked on my T839. This new device is being ... difficult.
the dormant bad blocks issue you spoke about, was this something found in new-out-the-box phones? I haven't seen a lot about that in the threads, can you point in at more info, please?
at any rate, it doesn't matter which version of Odin I use, I got the same result from both. I tried using a different cable/different USB port as well. I haven't tried using a different system (yet), but don't want to go through all the trouble of setting up everything on another box. Win7 is finicky enough, trying to get everything operating on Server2k3 would most likely end up a challenge. *lol*
I'll try repartitioning with KG1 when I get back to the house.
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin
orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
I've gotta pop the debug lock in the default.class to be able to push anything into the system folders with Android Commander. I've found a nice walk-thru to do this, it just requires a little knowledge of c++ and some patience. with any luck I should be able to pull default.class out of its img, edit it and flash that back (most likely with Heimdall since it can do itemized flashing).
pmp326 said:
i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda
Click to expand...
Click to collapse
tried it, no joy.
pmp326 said:
also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin
Click to expand...
Click to collapse
tried this, brings me back to the boot loop.
orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
currently I'm running into issues with getting ADB to push onto the system as the system is claiming it isn't rooted. Is there a way I haven't read about or found to root the phone without getting into the actual O/S (i.e. from the blue recovery screen)?
If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)
rpmccormick said:
If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)
Click to expand...
Click to collapse
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
I like turtles.
Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
Even the end... I mean, your not trying to odin a "tar.md5" are you?
rpmccormick said:
Even the end... I mean, your not trying to odin a "tar.md5" are you?
Click to expand...
Click to collapse
No....
Sorry man. I've never had to ODIN (this phone). I say check the md5 to make sure you downloaded a good copy, and maybe try a different USB cable. The ADB method seems nutz... if it doesn't boot after a successful ODIN, the phone is probably a paperweight.
Good luck!
Related
Yesterday my phone started acting up. All running process crashed and not many was able to start. I had to constantly click "force close". I think this started after I installed the Google+ app, but not sure.
I have tried uninstalling all unnecessary apps, without luck. I then tried wiping to factory settings by using the Android menu, but without any changing. I then tried by holding vol+ and power, going in to recovery and wiping both to factory and app cache. This doesn't change anything either. By googling I can see some suggests to hold vol- and power, to get to a another wiping-functionality but this just boots my Nexus S to normal state - no menu appears.
Has anybody an idea of what I can do?
Edit: more info; if I click "Report" and investigate the message sent to Google, I see that error has something to do with SQLite-relatet classes. Which makes some sense, alot of my changes are reset each time the phone is rebooted. For instance did I miss a call a couple of hours before the phone went crazy - this is shown at each boot in the notification area eventhough I clear the area and/or goes to missed call section
Factory reset via menu does delete all your "custom" apps, so I'd say it's not one of the existing apps causing problems.
The way you describe function after your factory reset sounds like factory reset didn't work properly.
If you feel safe I'd recommend rather flashing 2.3.4 again using either Odin or the OTA zip from Google (requires open bootloader).
I think you're right that factory reset doesn't do what is expected. Once I click it, the phone reboots and shows the Android guy next to an unwrapping package. This lasts only 2 seconds, then it reboots itself again and goes into normal phone mode (where all the app-crashing starts again).
I have not flashed or rooted my phone before, but I will consider this now since my NS is pretty much a brick. Thank you for your swiftly response.
Edit: Shouldn't I get a menu, when I push and hold vol- button, while turning on the device? Right now it just boot as normal.
Before you use odin....try going into rom manager a reflashing clockwork! Ive had that android dude on my screeen but reflashibg via rom manager always fixed it. Try that
Sent from my Nexus S using XDA Premium App
Wow my Nexus has totally shut me out.
I cannot use ClockworkMod unfortunately since I am not able to root my phone. It is not detectable via USA (when I use vol+/pwr and connect USB). I am unable to check the USB Debugging option on the phone. Each time I check it, go to home-screen and back to the menu, it has de-selected it again. Also I noticed when I read the info that is sent to Google for all those app-crashes I get, I see SQLiteException and error in an SQLite.java file. So it seems like some database layer is broken.
I read one could copy the ClockWork.img to my phone and use the standard recovery option to flash the img (I think). But when I go into the recovery menu, the file is gone. When I boot the phone again, it has deleted the .img file - eventhough if I copy it to several different folders, they are all gone :-(.
I feel pretty screwed at the moment. How can I else wipe all data?
I'd recommend to check if your device is correctly identified in windows. Missing USB drivers might cause problems. Get the latest drivers and a guide from here.
If you succeed booting into fastboot properly (vol up and power) you can follow this guide. Get the latest cwm recovery.img here.
Last option would be to boot into download mode (vol up + vol down + power + plugging in usb cable) and use Odin from samfirmware.com
--
All options require correctly working USB drivers.
I managed to unlock the bootloader, by quickly turning on USB-debugging (before any processes started to crash) and install the drivers from this post:
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
A reboot later, I got this message:
"System UIDs Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Right below was a button saying "Im feeling lucky" (??)
I installed ClockworkMod using fastboot and tried "Fixing permissions" with no luck. I will try some ROM later on, and hope it will bring my phone back
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
rentaric said:
Normally this error happens when you have a faulty app ruining your system, formating/deleting whole sdcard does usually fix this.
Click to expand...
Click to collapse
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
DennisRP said:
I can safely mount USB-storage and format the whole bunch?
I been sweating over this stupid issue all day now, all I want is a fac-reset :´(
Edit: "format /sdcard" using CWM didn't do anything
Click to expand...
Click to collapse
See I'm no expert on this whole thing. At this point I'd just flash a whole new system via Odin. Prolly not the smartest or safest option, but that's what I'd do because I don't know better. If that wouldn't fix it either, I'd return the phone on warranty
I was looking at Odin from the start, since nothing else seemed to be working.
So right now I got started on Odin. Followed the .pdf steps and flashed the bootloader at first succesfully. I was asked to remove the battery and re-connect my NS. Began downloading "pda" and "phone", but at around 10% a big fat red "fail" message appeared and now I just see the Google-logo on startup. I still cant flash any roms via fastboot.
Im too tired too right now, been working with this for 14 hours straight. I will look at it tomorrow evening. Thanks for your help rentaric
Weird, you're not the first one who had trouble running Odin using their guide.
Overall it's pretty simple.
Enter download mode. Vol up vol down and power at the same time while plugging in the USB cable. Start Odin, should show a yellow colored box with a port number. Uncheck everything but reset timer and auto reboot. Unzip the correct zip file from samfirmware.com (check if you got i9020 or i9023 and get the universal Odin exe), apply file from the folder accordingly. Bootloader and bootloader. Phone and modem. Pda and pda. Csc can remain empty (will change carrier info in fastboot).
Double check md5 hash to avoid broken files.
Sent from my Nexus S using XDA App
rentaric said:
Weird, you're not the first one who had trouble running Odin using their guide.
Click to expand...
Click to collapse
Of course I did not go to bed, how should I be able to sleep with a broken phone .
The firmware suggested on samfirmware.com for my phone, was 2.3.3 and some other version (my phone was 2.3.4.2/GRJ22 or something similar, I suspect that might be the cause. Also I unchecked everything, that might also have been of importance). The flash will always fail when everything was downloaded - it then said something about "remote" and "Loke" and then fail. But as I mentioned, I had succesfully flashed boot.img (2.3.3) thus no boot occured now. I googled the correct bootloader, used fastboot and was booting succesfully again.
I began looking more into the sdcard, as error-messages was leading me this way. To compress 4 hours of investigations into a few lines, it seems as my PBA is malfunctioning as other xda-members have experinced. Only solution is sending the phone to Samsung for a PBA replacement. I purchased the phone in Bestbuy USA and the danish Samsung partners are not too joyfull about this - I will contact Samsung and hope they can help me.
I experinced the exact same thing as this poor guy - http://forum.xda-developers.com/showthread.php?t=993403
Every thing you try to do to /sdcard is worthless.
Formatting (USB/using CWM/using adb shell linux commands) says "Succes" but nothing happens.
Copying files says "Succes" but nothing happens. If I boot phone into CWM, mount usb and upload new rom/apk/whatever and try to do a "install update.zip" it fails with some mounting errors.
Im ready to go cry in a corner - I really want this to be fixable via software, but I probably have to realize that this is a hardware issue.
Apparently Samsung doesn't offer worldwide warranty for cellularphones :´(. God it sucks to pay repair-expenses on a 1 month old mobile.
So I rooted my phone a few months ago but there weren't many mods out yet, so I waited until just today. I saw this one http://forum.xda-developers.com/showthread.php?t=1157593
I followed everything until I got to the part where I had to go into recovery mode, but before I was supposed to reinstall packages to get into CWM I accidently clicked on delete all user data and delete cache date because I misunderstood. So I got into CWM after and followed it and rebooted but nothing happened and the SGS4G screen just goes on and off. I didnt know what to do so I gave this a try. http://forum.xda-developers.com/showthread.php?t=1001759
I thought it would bring my phone back to stock and rooted because I couldnt recover or restore anything. It just put me in a more confused situation. When I reboot in recovery or just turn the power button on, the SGS4G screen goes on and off still.
So all I can do is this. Go to recovery. reboot,reinstall,delete user data or cache data. It says "signature verification failed" then "installation aborted" when I reinstall packages. And like I said, when I reboot the system all it does is the SGS4G screen problem.
Is there a way to start me fresh to a stock and rooted point? I dont think I have any files or anything on my phone anymore(if that is possible). I wanted to try this over again, but correctly obviously
Thanks for any help. I really need my phone soon
Were you in download mode when you used Odin? It should have worked. Make sure that it shows a yellow symbol with the android alien holding a shovel.
Sent from my SGH-T959V using XDA App
Thanks for the reply! And yeah i was in download mode. Odin said it went through and it lead my phone into recovery phone. After that I rebooted but I'm still experiencing the SGS4G screen going on and off still. Nothing else loads.
How did you set up Odin? You got the correct file loaded into the PDA box?
Sent from my SGH-T959V using XDA App
mrchovee said:
So I rooted my phone a few months ago but there weren't many mods out yet, so I waited until just today. I saw this one http://forum.xda-developers.com/showthread.php?t=1157593
I followed everything until I got to the part where I had to go into recovery mode, but before I was supposed to reinstall packages to get into CWM I accidently clicked on delete all user data and delete cache date because I misunderstood. So I got into CWM after and followed it and rebooted but nothing happened and the SGS4G screen just goes on and off. I didnt know what to do so I gave this a try. http://forum.xda-developers.com/showthread.php?t=1001759
I thought it would bring my phone back to stock and rooted because I couldnt recover or restore anything. It just put me in a more confused situation. When I reboot in recovery or just turn the power button on, the SGS4G screen goes on and off still.
So all I can do is this. Go to recovery. reboot,reinstall,delete user data or cache data. It says "signature verification failed" then "installation aborted" when I reinstall packages. And like I said, when I reboot the system all it does is the SGS4G screen problem.
Is there a way to start me fresh to a stock and rooted point? I dont think I have any files or anything on my phone anymore(if that is possible). I wanted to try this over again, but correctly obviously
Thanks for any help. I really need my phone soon
Click to expand...
Click to collapse
signature verificaton failed means u dont have a modified recovery record
u can get that out of the cwm final thread and push it to system/bin folder overwrite the one dont replace it that will solve that issue for u
I did exactly what the thread for Odin said. I already had the 64bit drivers installed. I downloaded the link that was provided for the ROM and then Odin. The rom took a while to download but it finally did. After that I held both volume buttons and then plugged in the usb and then it went into download mode. After that I opened odin and then clicked on PDA. The only thing that I could click on was the non-extracted rom that I downloaded aforementioned above.Gave it time to download and it said successful. Then I rebooted once it sent me to recovery mode. It also states to try and do it without sim and sd card in the phone which i just tried. It went through as well, but still has the SGS4G going on and off
RaverX3X said:
signature verificaton failed means u dont have a modified recovery record
u can get that out of the cwm final thread and push it to system/bin folder overwrite the one dont replace it that will solve that issue for u
Click to expand...
Click to collapse
I would try that but idk how i would be able to push it into the system/bin folder when all my phone is letting me do is go into recovery mode
Did u flash ext4 yet?
A suggestion for you.
If you can get into Down load mode which it sounds like you can, I would use ODIN to flash KC1 with its pit, PDA, Phone and CSC files and let it fully load up. Then ODIN Whitehawk's deoxed KD1 + root and try to flash your other ROM again.
It is very hard to hard brick these phones. Always take care to make sure the mount points in recovery are set to unmount, mount, mount and finally unmount when instructed to do so.
If your getting stuck with the ext4 section which causes this boot loop alot, what I have done is to disable voodoo lagfix, reboot into the newly flashed ROM then go back into recovery and enable voodoo. Has always worked for me.
This is my first post so I apologize if I don't make any sense lol. I develop android apps for a medical software company and I'm wanting to start creating ROMs to help out this great community.
I forgot to mention: http://forum.xda-developers.com/showthread.php?t=1117554 - [REF]{BIBLE} Galaxy S 4G (7/24/11) <5:00pm cst> is your best friend
icbinb is a great rom. you will definitely have to odin, as bytesfree says. you should use kc1 by raver. after you odin kc1, boot up normally and let the rom settle in for 10 minutes. then get a root manager, such as super manager or root explorer. download the 2 files from krylons final cwm thread. move both to the proper location using the root manager. make sure the recovery file is named properly. if it has the extra .bin extension in the filename, remove it. then shut down the phone, reboot into recovery, go to reinstall packages and the orange cwm will load. once that loads up, factory reset, wipe cache, go to mounts and check the mounts (u,m,m,u), go to install from sd card, flash the ext4 converter immediately followed by icbinb. all of these zip files should be on the root of your sd. let me know how it goes.
if you get it to flash, remember to leave the phone sitting for 10-15 minutes in order for it to settle in.
also, bytefree, welcome to xda. glad to have you contributing.
As Jager said, ICBINB and others such as Black Ice are great ROMS with lots of tweaks and features. The guys that create these ROMs are awesome in their intellect and programming abilities. Mrchovee, once you get the hang of the steps required to flash a ROM it becomes second nature, just keep at it and don't let a gimped flash bring ya down man. As I said before, these little phones are hard to brick.
Hey everyone!
So I flashed a ji6 tar through SGS kernel flasher to get 2e recovery. I think it managed to do so successfully because now I have CWM when I boot into recovery. HOWEVER, when recovery pops up it goes to the CWM screen and FREEZES! I cannot select any options including reboot system. I also now cannot startup my phone normally! What can I do? I have ODIN but it won't detect my phone when it's connected (tried this about 20 times). I'm running a mac so I guess there aren't very many options. The only way out of anything int his mess is to pull the battery. SOMEONE PLEASE HELP! My phoen is now useless for all purposes. I tried factory reset, etc. On normal bootup my phone is stuck on the startup screen and never progresses past. Help please!
well odin doesnt run on mac.
search for heimdall. (same thing but for all OS) [PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite ...
heimdall / odin use download mode not recovery, you know that right? hard to tell by your message.
Instructions for download mode:
plug USB cable into computer
have phone shut off
hold both volume buttons
plug USB into phone
let go of buttons when you see an android digging "down"
Click to expand...
Click to collapse
or get VMware or another virtual machine and install windows. http://www.utorrent.com http://torrentz.eu/search?f=vmware http://torrentz.eu/search?f=windows+7
THanks for the tips.
I've been using (or trying to) Odin in Download mode but it will not detect my device. Recovery in CWM freezes, 2e recovery leading to the CWM screen is fine but when I hit'reboot now' or startup regularly using the power button, it's stuck on the boot up logo page. But I'm investigating Heimdall hopefully that helps or I am totally at my wit's end! Been working on this for a couple hours using everything I can think of! (And Google and XDA forums of course!)
Gave Heimdall a whirl, it just says failed to confirm end of PIT file transfer. HELP!!!
NewbDroid said:
Gave Heimdall a whirl, it just says failed to confirm end of PIT file transfer. HELP!!!
Click to expand...
Click to collapse
Any chance you have access to a Windows based system? I've never used Heimdall, so I can't help you there.
Are you 100% sure you're in Download mode? Yellow shovel guy. Were you using Odin with VMware Fusion or something similar? Try different USB ports if it's a G5 or something, doesn't apply if a Macbook.
Heimdall is open source and it works on all platforms...
It's BETTER!
studacris said:
Heimdall is open source and it works on all platforms...
It's BETTER!
Click to expand...
Click to collapse
I don't doubt that at all. I flash to stock so seldom now that using Odin once ever 3 or 4 months doesn't bother me.
NewbDroid said:
Gave Heimdall a whirl, it just says failed to confirm end of PIT file transfer. HELP!!!
Click to expand...
Click to collapse
unfortunately i know nothing about heimdall, even though im the one that suggested it. studa! help a man out! i gave you your 900
here is a link to a 1 click heimdall package, which also has a prerooted version i suggest you get that as this a transitory os and rooting is part of the process of getting 2e recovery WITHOUT flashiing a stock kernel that will make your phone unbootable.
if you have connection issues refer to THIS THREAD
once that is completed, refer to THIS THREAD to MANUALLY replace 2recovery.
then to make sure it wasn't a wonky cwm file you had that made it freeze(actually now that i think about it you could use adb to push this to the root of /mnt/sdcard FIRST to see if its the cwm file. adb should work in recovery) grab the attached update.zip
Had a similar situation and had to order the USB jig to get out of it. It is pretty easy to make or if you want an easy (and clean) option, order one. Once you have that, remove the battery, SIM and SD. Reinsert the battery and then insert the USB jig. It will go right into download mode and then from there use Odin to flash it back to stock.
Hello everyone, before I start, I want to let everyone know I have searched endlessly for a fix, etc.
I have a SideKick 4G that I purchased maybe a month ago, and yesterday I went ahead and tried to flash a custom ROM on it. Now my issue is, I was hap-hazardly strolling through the menus and doing the procedure so I didn't back anything up or check the mounts etc.
My issue is, I have Odin and the sk4g.pit file, but I can't find the KD1OdinSTOCK.tar or KG2OdinSTOCK.tar files, because the file hosts are down... permanently.
I also do not know if I have the KD1 or KG2 firmware, what the difference is, and if any problems could be caused by flashing one or the other onto my device. I'm pretty new to the whole process and I was only looking to make my phone faster and less clunky.
If I get the files, a quick walk-through for my specific situation would be very highly appreciated.
Thanks in advance!
EDIT: I found a newer firmware for the SideKick 4G, called KH1, Not KD1, KG2, or KJ1.
To get the file:
1) Go to SamFirmWare.com and make an account
2) Search T839UVKH1
3) Make sure you find the firmware for this model. "SGH-T839"
4) Download it
5) Make sure to look for what password you'll need to open the file (This one is marked with "##")
6) Input password when extracting the file to wherever you want to put it (The password for this one is samfirmware.com)
That should be it.
My issue now is that Odin isn't recognizing my device. It's in download mode and I have the factory cable but I must be doing something wrong as I can set the PIT file and the PDA file, tick boxes etc. but I can not for the life of me get my device detected.
Alright, later update.
I got Odin to recognize my phone, and now I'm trying to flash it.
I don't seem to be having any negative impact with my firmware (KH1) and sk4g.pit, however it always fails at write boot.sbl OR, it gets stuck at Set PIT file.
My phone changed from the Downloading... mode to the Phone - ! - PC picture, however, I was told I can still flash from this mode. I've been continuing to flash with different settings in hopes of reaching recovery, and so far what has NOT worked:
Auto Reboot
Auto Reboot + Re-Partition
Auto Reboot + Re-Partition + F. Reset Time
I don't believe I've tried Auto Reboot + F. Reset Time without Re-Partition, or Re-Partition with F. Reset Time.
Any advice or comments?
Update #2.
http://forum.xda-developers.com/showthread.php?t=1350060&page=6
This thread seems to have a link to a oneclick stock recovery as well as KG2 firmware, judging by the 254 MB download (THAT WORKS BY THE WAY.)
Hopefully after I download this, I can get the phone running. Will post later to inform a yay or nay.
Edit: I almost successfully flashed to stock KG2 Firmware. All went well (Kernal, Recovery, etc) Except it failed at the modem.
It rebooted after failing modem and now I'm stuck at sidekick boot logo. It's better than having Phone - ! - PC though.
EDIT 2: Seems that it keeps failing at Modem, part 3 of 6. along with that, it does restore the phone to Download mode rather then the broken sync picture. Odin now does not recognize the phone, but I think that's due to the other drivers the oneclick method prompted me to install. I'm going to try to disable those drivers temporarily and see what odin thinks about it.
Update #3.
I discovered the drivers downloaded to run the oneclick as provided by the link in the previous update did infact block connection to odin with the same device.
Uninstalling the driver got the connection going again. Every time in Odin, I fail at writing either boot.sbl or cache.rfs.
I took the files from the KG2 firmware and compiled my own .tar out of them and when I flashed using my compiled tar, that's when I got the cache.rfs write error. Phone has shown no signs of improving or deteriorating. I can go back to oneclick recovery and get the phone out of broken sync picture mode, and back into Download mode. However, here are my 2 issues flashing.
In Odin:
I either have no connection, or
I can't write boot.sbl or cache.rfs and fail.
In Heimdall One-Click KG2:
I need the driver Odin doesn't like, and
I flash almost all the way through, but fail halfway through uploading MODEM.bin.
It's giving me the opportunity to flash Boot Loaders along with KG2 kernal, recovery, modem, etc. It's the only thing I haven't tried yet.
Update #4.
I'm about to flash bootloaders. Wish me luck
EDIT: I'm about to cry :') I THINK IT WORKED. I'm loading boot screen.. got animation and now got samsung screen, waiting for the phone to boot. got a fully successful oneclick and it's looking well at the moment
YEAH!!!!!!!!!!!!!!!!!!!! HOME SCREEN!!!!!
Nice monologue.
Thank you sir. What do you think of the things I did to get my phone working again? Anything you think I shouldn't have done? o_o''
I hope there is a way for me to fix this. I am a noob but, I have been successful flashing things a few times in the past (and not so lucky a few times). This time I had flashed my Infuse back to stock 2.2 Froyo UCKD5 after having Zues w/ Aries HellFire running for a couple weeks. I decided to try another ROM because I was bored. Then I screwed something up thinking I knew more than I do. As I was trying to clean things up in my files to get ready to do a back-up,something happened and about half of my apps,factory and 3rd party had no files or ?? They didn't show any MB in cache / data,in TIBU or App Mgr, only "computing...", and obviously things didn't work right. So I hit the phone's Factory Reset,went into Odin3 thinking I would try doing something I never tried before,stupid me, and installed through the PDA button, zimage root tar file, success, saw the Fugu fish and then reset Odin, turned off/ on. Pulled battery from phone, usb jig to download mode, because three button method wasn't working. I thought it had something to do with the residual kernel or bootloader from Zeus. The kernel that was running is 2.6.32.9 and I don't know what that is. Any way I thought I would install KF1 .tar Odin3 installed it but it got stuck on the Samsung power-up screen,black background white Samsung letters. I usb jigged into download mode , thinking maybe I had the wrong drivers possibly and did the Heimdall Zadig driver install, nothing changed. So, I thought that I better just reflash to stock using GTG's Ultimate Unbrick, used the UCKD5 tar and it passed. Then I unplugged the phone when it shut off to reboot, it booted into blue recovery and I hit reboot and it came right back into blue recovery. I am able to get into download mode or into the ever looping blue recovery<3e>,but nothing else. No programs,Odin, Kies, Heimdall,GTG's, recognize the phone,the laptop does and says the device may not work correctly..., but I did notice what the fails were in the recovery boot-up. So I snapped pics with my Captivate and uploaded them and I will paste them here (I think XDA lets idiots like me paste in this area?). they are readable, but if I need to type everything out I can, but not until someone asks so as to keep this already lengthy story a bit shorter. Thanks in advance,KK13/khkaiser13. sent in using my Rooted Captivate on APEX12 through XDAPremium View attachment 899419
View attachment 899420
Did you try clicking flash in Heimdall, sometimes it looks like it doesn't see the phone, but you click flash and it works. Also, have you tried clearing user data and cache? (I know you said you had factory reset at one point but now that you are stuck might be worth a try.) Looks like a boot loader issue, not sure why Heimdall doesn't see the phone, I've had good luck in the past with it.
I'm tempted to tell you to format the internal sd and try heimdall again, but maybe someone with more experience would have a better idea.
khkaiser13 said:
I hope there is a way for me to fix this. I am a noob but, I have been successful flashing things a few times in the past (and not so lucky a few times). This time I had flashed my Infuse back to stock 2.2 Froyo UCKD5 after having Zues w/ Aries HellFire running for a couple weeks. I decided to try another ROM because I was bored. Then I screwed something up thinking I knew more than I do. As I was trying to clean things up in my files to get ready to do a back-up,something happened and about half of my apps,factory and 3rd party had no files or ?? They didn't show any MB in cache / data,in TIBU or App Mgr, only "computing...", and obviously things didn't work right. So I hit the phone's Factory Reset,went into Odin3 thinking I would try doing something I never tried before,stupid me, and installed through the PDA button, zimage root tar file, success, saw the Fugu fish and then reset Odin, turned off/ on. Pulled battery from phone, usb jig to download mode, because three button method wasn't working. I thought it had something to do with the residual kernel or bootloader from Zeus. The kernel that was running is 2.6.32.9 and I don't know what that is. Any way I thought I would install KF1 .tar Odin3 installed it but it got stuck on the Samsung power-up screen,black background white Samsung letters. I usb jigged into download mode , thinking maybe I had the wrong drivers possibly and did the Heimdall Zadig driver install, nothing changed. So, I thought that I better just reflash to stock using GTG's Ultimate Unbrick, used the UCKD5 tar and it passed. Then I unplugged the phone when it shut off to reboot, it booted into blue recovery and I hit reboot and it came right back into blue recovery. I am able to get into download mode or into the ever looping blue recovery<3e>,but nothing else. No programs,Odin, Kies, Heimdall,GTG's, recognize the phone,the laptop does and says the device may not work correctly..., but I did notice what the fails were in the recovery boot-up. So I snapped pics with my Captivate and uploaded them and I will paste them here (I think XDA lets idiots like me paste in this area?). they are readable, but if I need to type everything out I can, but not until someone asks so as to keep this already lengthy story a bit shorter. Thanks in advance,KK13/khkaiser13. sent in using my Rooted Captivate on APEX12 through XDAPremium View attachment 899419
View attachment 899420
Click to expand...
Click to collapse
Before you go any further,
Read my how to..click on the first link on my sigs.
Read through several times.
There is a BIG difference b/t download mode and recovery.
Thanks, I did clear Data/Cache. I also did format the sd as a last resort but, it didn't help. I don't know if you looked at the screenshots I posted but, it says Checksum Fail and Movinand Checksum Fail. I dont know what either of those are but, willing to bet if someone knows it might be repairable. Thanks Again, to both, enochpc and qkster for the helpful info which I did not know before. khkaiser13/ kk13
khkaiser13 said:
Thanks, I did clear Data/Cache. I also did format the sd as a last resort but, it didn't help. I don't know if you looked at the screenshots I posted but, it says Checksum Fail and Movinand Checksum Fail. I dont know what either of those are but, willing to bet if someone knows it might be repairable. Thanks Again, to both, enochpc and qkster for the helpful info which I did not know before. khkaiser13/ kk13
Click to expand...
Click to collapse
Put your phone in download mode. Odin or heimdall back to stock and start over.
Don't worry about anything else as long as you can get into dl mode
Hey, thanks for responding. I know the difference b/t recov. and dload. I am stuck in recovery<3e> blue, it just returns the recovery screen no matter if I press reboot, clear cache, or clear data, or try install zip. But if I usb jig it, it goes into download mode. Thats it. What I have and don't know what or how to fix is during the reboot attempt (you can read it if you click on my screenshots) it says Checksum Fail, Movinand Fail, and lfs undone. I'm gonna try to find out more about those files ( I guess thats what those would be ???) Thanks Bro.
khkaiser13 said:
Hey, thanks for responding. I know the difference b/t recov. and dload. I am stuck in recovery<3e> blue, it just returns the recovery screen no matter if I press reboot, clear cache, or clear data, or try install zip. But if I usb jig it, it goes into download mode. Thats it. What I have and don't know what or how to fix is during the reboot attempt (you can read it if you click on my screenshots) it says Checksum Fail, Movinand Fail, and lfs undone. I'm gonna try to find out more about those files ( I guess thats what those would be ???) Thanks Bro.
Click to expand...
Click to collapse
You borked something in the ROM. That's why it won't boot. Files mismatch and don't add up. That's why you're in blue recovery.
You've to get into dl mode and flash a stock ROM img. Then start over.
qkster said:
You borked something in the ROM. That's why it won't boot. Files mismatch and don't add up. That's why you're in blue recovery.
You've to get into dl mode and flash a stock ROM img. Then start over.
Click to expand...
Click to collapse
Just to add this to what qkster said! I know you said you know the difference but be sure to have proper drivers installed I personally used GTG’s Ultimate Unbrick with 100% success. If there is any doubt about bad drivers I would also suggest reinstalling them there is a very easy to use Utility called usbdeview that lets you uninstall drivers and start fresh.