So, I believe I bricked my phone. I will explain in as much detail as I possibly can as to what I had done in hopes that someone can inform me of a way to save my poor Sidekick 4G.
I have rooted and installed custom ROMs on 3 other phones (T-Mobile G1, T-Mobile MyTouch Slide 3G, and a Verizon Samsung Continuum). I'm not entirely new to the process. I got a Sidekick 4G and decided to root it and attempt to get CWM on there so I could install a custom ROM. So, here is what I had done.
I used a program I believe is called SuperOneClick to gain root access to the phone. I opened up a file managing program that was also able to see root folders. I put a modified recovery.bin on the root of my SD card and used the file manager program to move and overwrite the recovery.bin in my system/bin folder. Instead of overwriting it, it just put it in there as recovery - COPY.bin. I attempted to rename it to recovery.bin and it didn't want to do it. I attempted to move recovery - COPY.bin back to my SD card and it failed. Whatever. Time to try a different file managing program. I open a new file managing program and it asks to use Bluetooth. It hangs up for about 3 minutes, at which time I went to the home screen and went back to the app. It is still hung up trying to turn on Bluetooth. I decide I should go ahead and help out, so I go back home, go to settings, and try to turn on bluetooth. It sits there and does nothing for about 3 minutes. My phone locks up, so I pull the battery out and put it back in to restart the phone.
"Dammit, Jessica. You ruined your phone." It doesn't start back up. It starts into the standard recovery mode. None of the four options available allow my phone to go past recovery.
So, super smart girl I am decides to use ODIN and try to flash stock Sidekick OS back to the phone. ODIN stops at about 10%-15% every single time and doesn't move forward. If I try to start the phone now, I don't even get recovery.
Anyone have any ideas that don't involve me throwing my phone into a rock quarry?
check if have any kies services running, or try flash in other pc
kelvyn1995 said:
check if have any kies services running, or try flash in other pc
Click to expand...
Click to collapse
kies services? Excuse my ignorance, but what are those?
windows task manager, processes and search for processes who have kies in the name and close it, or just try in another pc.
can u get into download mode?
Sent from my SGH-T839 using XDA App
if u can get it into download mode u the hiemdall method its on the dev of he sidekick 4g forums
I definitely can get it into download mode. When I get home from work tonight I will try this, thank you all so much! <3
no problem glad we can help. and next time u can go to the sk4g forum and you questions there. you will get a faster answer.
Sent from my SGH-T839 using XDA App
Tried a different computer. Still failure. Gonna try the hiemdall thing here in a moment.
Hiemdall failed the first time. Then I went at it a second time by flashing the bootloaders. My phone works again. Thank you all SOOOO much. <3~~
Np
Sent from my SGH-T839 using XDA App
starlitjessi said:
So, I believe I bricked my phone. I will explain in as much detail as I possibly can as to what I had done in hopes that someone can inform me of a way to save my poor Sidekick 4G.
I have rooted and installed custom ROMs on 3 other phones (T-Mobile G1, T-Mobile MyTouch Slide 3G, and a Verizon Samsung Continuum). I'm not entirely new to the process. I got a Sidekick 4G and decided to root it and attempt to get CWM on there so I could install a custom ROM. So, here is what I had done.
I used a program I believe is called SuperOneClick to gain root access to the phone. I opened up a file managing program that was also able to see root folders. I put a modified recovery.bin on the root of my SD card and used the file manager program to move and overwrite the recovery.bin in my system/bin folder. Instead of overwriting it, it just put it in there as recovery - COPY.bin. I attempted to rename it to recovery.bin and it didn't want to do it. I attempted to move recovery - COPY.bin back to my SD card and it failed.
Click to expand...
Click to collapse
I did the exact same thing up until that part. I had overwritten it, and rebooted the phone and attempted to install a custom rom. When i did so I had a robotic woman voice repeating "Convert system partition; System unavailable."
I googled that error, and found someone saying to use odin one click, and the one click I used apparently was for a different type of phone. And to make matters even worse, I unplugged my phone before it was completely finished, believing it had already finished. Now, when power is applied to my phone, (plugged into the computer, holding power button) All it does is make the screen light up a bit. I dont get a logo, i cant put it into download mode, I cant do anything, whatsoever. Any help?
Related
Welp, tried to root the Nexus S 4g.
On rebooting, it gets stuck at the Nexus S bootscreen, pauses, keeps going, etc.
Got CWM 3.0.0.5, and can fastboot, get into CWMRecovery.
From there, I'm at a loss. Tried to restore Nandroid backup, but it says a whole bunch of stuff, basically saying E: failed to find "cache" partition, Can't mount /cache/recovery/last_log, etc.
Tried to apply zip from CWM backup, it says "No files found."
Tried going into mounts/storage to mount USB storage, but nothing appears on desktop of either Mac or PC, so I can't get move files onto the SD card.
Now, when I just power up, it just says "Google," and there's a unlock icon at the bottom. Nothing else.
Anyone have any solutions?
Yeah stop using that old version. Of ClockworkMod recovery
Seriously use 3.0.2.4. Its in the clockwork thread in the dev section.
Sent from my Nexus S using XDA App
Would if I could, but I can't get anything on the SD card!
Trying to mount USB storage from CWM-- no drive shows up on Mac or PC for me to move stuff onto it.
Boot into fastboot by turning off phone, turn back on while holding volume rocker up. Leave it at the screen where you could select reboot, recovery etc. Download the above mentioned clockwork recovery image from the thread to your computer. Flash using fastboot command. No need to copy anything to SD card.
Sent from my Nexus S using XDA App
Having the exact same issue. Nothing appears in the nandroid folder now either after replacing the recovery image with 3.0.2.4 and I can't mount the USB storage or get anything onto the SD card. Phone won't boot. Unsure of the folder structure on this phone to try pushing a file with adb or fastboot.
Same issues here. I was able to flash CWM recovery 3.0.2.4, but when I go to "mounts and storage" and "mount USB storage", I the drive does not appear on both Mac and PC. I'd like to transfer the stock NS4G image onto the phone so I can install the zip from the sdcard...
When I try to use the command, "adb push", it can't find the SD card.
Same problem
I flashed it , and since then i cannot mount the device , i have a good image to push but the device is not opening up the storage for me to push the image.
I had the same problem. Got it all fixed up.
peabody42 said:
Welp, tried to root the Nexus S 4g.
On rebooting, it gets stuck at the Nexus S bootscreen, pauses, keeps going, etc.
Got CWM 3.0.0.5, and can fastboot, get into CWMRecovery.
From there, I'm at a loss. Tried to restore Nandroid backup, but it says a whole bunch of stuff, basically saying E: failed to find "cache" partition, Can't mount /cache/recovery/last_log, etc.
Tried to apply zip from CWM backup, it says "No files found."
Tried going into mounts/storage to mount USB storage, but nothing appears on desktop of either Mac or PC, so I can't get move files onto the SD card.
Now, when I just power up, it just says "Google," and there's a unlock icon at the bottom. Nothing else.
Anyone have any solutions?
Click to expand...
Click to collapse
I had the same problem this morning:
I posted a workaround that worked well for me in Post #35
http://forum.xda-developers.com/showthread.php?t=1072698&page=4
If it works for you click 'Thanks'
Figured it out
Alright , this is what i did to fix the problem, i booted up the system with the bad image i had, connected to wifi and downloaded the Nexus S 4G deoxed image that is out there directly from the internet to the phone. Then i moved it from the download folder to the root using file manager.
I rebooted into recovery and was able to wipe and then flash the recovery image and reboot. Once i rebooted i regained control over the usb and memory card. hope it helps you guys.
How Do I Fix "REALLY" Bricked and DEAD Nexus S4g?
All posts on this thread presuppose a working Nexus S 4g. When I use the term bricked, I mean dead. About a month ago I followed directions on one of these threads on how to easily and with one click route my jellybean running phone. For some reason the process never completed, and all I was able to accomplish was unlocking the phone. When I ran the check to see if it was truly rooted, the response showed the phone was still unrooted. About 30 days later it was deader than a brick. Somewhere I read that Jellybean on Sprint might be the culprit. Anyway, I have a dead phone. Sprint wouldn't even check it because the screen was cracked. Fortunately, I bought a new one, new to me anyway, on eBay for $37. It is still running android 2.3.7(Gingerbread), and the phone is attempting to push the Ice Cream Sandwich update. I am fighting the update until I figure out what killed my phone.
Just wondering whether there is anything I can do with my old phone, even if I only use it like an old iTouch for music and surfing via Wi-Fi. Anyone?
I attempted the one click method described here, but my desktop cannot find any devices. So it truly is dead. Comments appreciated. I have used several different cables, unsuccessfully.
sexynexy said:
All posts on this thread presuppose a working Nexus S 4g. When I use the term bricked, I mean dead. About a month ago I followed directions on one of these threads on how to easily and with one click route my jellybean running phone. For some reason the process never completed, and all I was able to accomplish was unlocking the phone. When I ran the check to see if it was truly rooted, the response showed the phone was still unrooted. About 30 days later it was deader than a brick. Somewhere I read that Jellybean on Sprint might be the culprit. Anyway, I have a dead phone. Sprint wouldn't even check it because the screen was cracked. Fortunately, I bought a new one, new to me anyway, on eBay for $37. It is still running android 2.3.7(Gingerbread), and the phone is attempting to push the Ice Cream Sandwich update. I am fighting the update until I figure out what killed my phone.
Just wondering whether there is anything I can do with my old phone, even if I only use it like an old iTouch for music and surfing via Wi-Fi. Anyone?
I attempted the one click method described here, but my desktop cannot find any devices. So it truly is dead. Comments appreciated. I have used several different cables, unsuccessfully.
Click to expand...
Click to collapse
Hi,
What method did u use to root? What thread? Cuz it may need to newest version of the recovery.
anyways...
Try charging up a battery on newer phone and put in dead phone... but instead if turning on normally, boot into recovery.
If it worked then use a back up to flash it back to stock. Assuming u were able to back it up b4 root.
If not plug into computer. See if it turns on or can go into either recovery or boat loader mode and if so perhaps computer will recognize it.
Vs Nexus S4G using tapatalk2
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.
Well I was caught my the new MIUI ROM i saw this morning and decided to switch from Bionix. I have flashed many phones and farmiliar with the process. I left my phone alone while the install occured. I watched it wipe data and cache. Now when it powers up, the samsung logo appears for 2 seconds and a quick I9000 logo flashes for like .25 of a second. The 3 button method to force it into recovery. I dont have a usable copy of windows to boot camp from my mac so ODIN is currently not an option.
I can get the phone into download mode so i know its not a lost sailor, i just need a mac solution without booting windows. I really dont want a refurb replacement from warranty either
You want heimdall.
Yup. heimdall rocks
samsung screen of death...
LinuxBozo said:
You want heimdall.
Click to expand...
Click to collapse
SO here goes...
first off i am rooted, have all appropriate drivers, etc, have used dab to root.
I am a total newb, and was experiencing issues flashing a new ROM. when trying to install the zip through cwm the phone said "signature verification failed" or something to that extent. so being the deductive thinker that I am, I formatted everything: boot, system, sd, etc. After doing this, I realized that I totally wiped out all the files on the internal sd.
so i downloaded the heimdall one click- it connects but fails regardless of whether i flash boot loader.
i can access blue 3e recovery and download mode.
now. i want to know if it is possible to push or even install a ROM through adb. I've been playing around with it all day and have gotten nowhere.
i thought maybe i could load up a rom to an external sd but obviously you can't mount an extsd in cwm.
am i screwed?
ill gladly donate through paypal if someone can help me get my baby up and running again. i do not want to be using my nokia from middle school anymore!!
thank you in advance for ANY help you can give me.
Rob
Been trying to Root this phone for a couple of days. Finally manged to do it!
Its the Rogers Samsung Galaxy Rugby. The (GT-S5690R) model.
I had to add the (R) in the updater script. Thats how I got it too root.
1. Put the file on your sd-card Universal_GB_ROOT_v5_patched_for_S5690.zip
2. Turn phone off
3. Boot in to Recovery ( press Power, Vol-up, and center button on bottom of phone all at same time. The samsung logo will appear, keep holding all buttons, then the logo will dissapear then re-appear, when it comes back let go of the power button only. The phone should boot into the 3e recovery)
4. use vol keys to navigate through menu, and use center button on the bottom of the phone to select.
5. Select install update from sd card.
6. press on the Universal_GB_ROOT_v5_patched_for_S5690.zip
7. phone should install root, wait till the 'Success' appears, then reboot.
You should find Superuser app when your phone reboots. You are Rooted!!
Now im just trying to figure out how to get a custom recovery!!
Perfect!
This zip file worked perfectly on my Rogers Galaxy Rugby. Many thanks!
Happy to hear
Sent from my GT-S5690R using xda premium
Big problem now though....
So the root went swimmingly, but I got a little too excited removing pre-installed apps. I backed up and removed Samsung Home, and removed and NOT backed up SNS 1.0. The phone will now refuse to boot unless I wipe data/factory reset in recovery mode, but after that it just ends up crashing during the Android wizard start up....
This is a brand new phone, what can I do to restore those apps, and get it back to the way I received it earlier today?!
There is a way to boot into safe mode, head Google mod2extreme and I find the forum for our phones (currently the only one) find advise there
Sent from my GT-S5690R using xda premium
Thanks for the name of that forum! I've found the guide someone posted here: http://www.mod2xtreme.com/showthread.php?t=12386 and I've decided to try it.
I'm using the first firmware listed in this thread: http://www.mod2xtreme.com/showthread.php?t=11744 (S5690XXKL1 2.3.6 2011 December S5690OXFKL1) mostly because under Country/Carrier it has nothing, so I'm assuming it's more generic than the others. I'm also keeping in mind this is for the 5690, not the 5690R, so it may not work at all. But, worth a shot since my only other recourse is to break down and cry in front of a Rogers attendant to see if he can give me a new one. "Root? What's root? Like ginger?"
I'm using v.1.83 of Odin3, which is listed as supported the 5690.
Downloaded KIES 2.0 from http://www.samsung.com/my/support/usefulsoftware/KIES/JSP - It gave me two DLL registration (COM) errors during installation on Windows. Uncertain if this will end up screwing me over or not.
Be right back, rebooting now that KIES is installed... will edit this post when there's more to report.
EDIT: Yeah, so I ended up trying both Odin version 1.83 and 1.85, with the Marvell .pit file, and the firmware from that thread. I learned that I had to put the phone into Download Mode, NOT Recovery Mode while trying Odin. Even still, nothing worked. I've given the phone up to Rogers and they will try to replace the original ROM, hopefully they won't notice that I've rooted it and really mucked everything up. They said if it doesn't work they'll send it off to Samsung to get it repaired. Anyone know if they find out I rooted it, I'd have to pay for voiding a warranty or anything?
i have the same device hae you manage to get clockworkmod recovery on it?
Does this method erase all personal data/downloaded apps from phone?
Great it worked perfectly...
did you success in installing different firmware?
Thanks again
Thanks a lot, worked like a charm.
Is there a way I can install Clockwork Mod? Rom manager doesn't recognise the s5690r. It gives me the option of selecting the Epic4G or the GalaxyS i9000. will either of these work?
Also, once I get that figured out, is there any roms compatible with the s5690r? I've scoured the webs with no luck. Not a very popular phone, eh?
Thanks again.
markdexter said:
Been trying to Root this phone for a couple of days. Finally manged to do it!
Its the Rogers Samsung Galaxy Rugby. The (GT-S5690R) model.
I had to add the (R) in the updater script. Thats how I got it too root.
1. Put the file on your sd-card Universal_GB_ROOT_v5_patched_for_S5690.zip
2. Turn phone off
3. Boot in to Recovery ( press Power, Vol-up, and center button on bottom of phone all at same time. The samsung logo will appear, keep holding all buttons, then the logo will dissapear then re-appear, when it comes back let go of the power button only. The phone should boot into the 3e recovery)
4. use vol keys to navigate through menu, and use center button on the bottom of the phone to select.
5. Select install update from sd card.
6. press on the Universal_GB_ROOT_v5_patched_for_S5690.zip
7. phone should install root, wait till the 'Success' appears, then reboot.
You should find Superuser app when your phone reboots. You are Rooted!!
Now im just trying to figure out how to get a custom recovery!!
Click to expand...
Click to collapse
Good Day, I am also working on the Bell Canada Version of the Rugby. It is the GT-s5690m model. I am now stuck in a bootloop and don't know how to fix it. I have played around with the root and unroot zip files that have been floating around but I am certain that the bootloop is due to not being able to clear the Delvik Cache. As you are aware Clockworkmod recovery is not supported on our devices. I am unsure how to get it to work. Until then I just keep trying different things to hopefully get this phone up and working. It is quite a rugged device and would be great with a custom rom and recovery. Could you explain to me in layman's terms how I might create a flashable clockwork image to flash via Odin or even through stock recovery. I would love to get this phone up and working. Thanks in advance
Sasktel Rugby
Hi there. I am working on the Sasktel version of this phone as well. I tried to change the model from R to M because this phone is the same as the bell model version but it would not install it. I found it on the external SD card but it will not run the zip file from the 3e recovery. Any ideas why this might be happening?
Thanks,
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!