Related
I have tried to flash my phone to EB13 new 2.2 Froyo. I have rooted my Epic 4g using the one click method a long time ago and never had a problem. I tried all steps on previous posts (http://forum.xda-developers.com/showthread.php?t=963652) and nothing seems to help. I have done the following to update to 2.2 Froyo:
1) I tried to do the update.zip file method. I went to recovery mode and did as you all stated and would return with errors.
2) I have tried to use the odin method (this is where my phone got broken.)
a) I have done all the steps that you guys posted; and odin would return as failed.
b) In odin i have done the following: (Odin recognizes my phone and i have the yellow box and it uses "com6")
I) made sure that the only box that should be checked is Auto Reboot (i didn't know this until the second time i ran odin so the F. Reset Time was checked by default the first time around)
II) the first time around i only placed this file (SPH-D700-EB13-8Gb-REL.tar.md5) in the PDA box. And it returned with errors. (this is where my phone got broken; i realized it when i tired to turn on my phone to call someone)
III) At this point and time i said screw 2.2 i just want my phone back up and running and tried to do your methods to return to stock using these steps (http://forum.xda-developers.com/showthread.php?t=773032)
IV) it doesn't work at all. I can still go to the Downloading section of the phone doing the #1 and then power button. and at times i can go to recovery mode (when it wants to) but nothing happens. i get these icons while trying to turn on my phone "a phone with a computer next to it"
c) in Odin i have noticed that it takes an extreme amount of time while in the Param.?? (this takes about 8 hours and than returns with a "red fail" in other occasions it gets stuck on "initializing"
d) Odin is not working for me!!!!!!
3) i have also tried the samsung update method (since odin doesn't work for me)
a) i have done all the steps that samsung says and it all passes until i get to the "start download" section.
b) after i press "start download" it stays in idle for a long time than goes to that param.?? and it wouldn't go anywhere and it stayed there for a whole day and nothing ever happened.
Please guys i have had no phone for 2 days now and i need my phone for work and i need my phone by Friday. If there is any help you guys can give me it would be appreciative or else i would have no choice but to go to sprint store and get me a new phone or have them fix this issue and i don't want to be penalized for messing with my phones OS. Please return with suggestions and help me fix this asap.
*Note: My phones Drivers are all installed using you driver download link and i am using Windows 7 64bit.
Thank you in advance!
Try again with a different USB cable. If you are sure you got the drivers installed properly
Sent from my SPH-D700 using XDA App
win 7 64 bit drivers
Here are the drivers I used to Odin my Epic with Win 7 ultimate 64-bit. I put the zip in my google documents.
https://docs.google.com/leaf?id=0B8DFupwiCOXyMGViMDJmY2MtMGU4YS00MGY5LWFkOGItNjkyMDY3MjkyNjgx&hl=en
I used the eb13 from here :
http://forum.xda-developers.com/showthread.php?t=853209
using this tar : Stock EB13 Deodexed EXT4 + CW 3.0.0.6
Also, check your usb connector. there are pins in it that can bend and prevent a good connection. I have read a few posts here on XDA where people had to straighten things out.
Good luck!!
Uh, ouch.
SPH-D700-EB13-8Gb-REL.tar.md5 is not the same file as SPH-D700-EB13-8Gb-REL.tar
Flashing the wrong file is a very good reason why your odin attempt did not work.
I will try this out im having my fingers crossed. Hopefully it works out.
Just to be clear....
I have re-downloaded the 64bit drivers for Win7.
Now in Odin what do i have to put in "PIT"?
Do i use "s1_odin_20100512.pit" for the PIT tab?
Results:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
why is this happening? I did all what u guys requested to do.
I used a new cable
Thank God! Its working!!!!!
All is working well for me Thank you so much guys and special thanks to you jdelano for your help.
My last question...
Is this rooted already?
let me know.
Thank you guys!!!!
So I just tried this because I couldn't get CW3 on my phone without it being all funky. When I would do it before I would have android flashing over the sprint bootup. This only has the android showing. Did I do it right?
Hello,
My GT-i5510 (aka Galaxy 551) is stuck in boot loop (or black screen depending on the ROM), and I'd need some piece of advice to fix it if it is possible.
I am not exactly sure what happened, I had my phone connected w/ adb shell, and I was either doing nothing (except I changed to some of the root FS'es) or I was dumping one of the mmcblk FS on the SD card (it might have happened when it broke, or it is something I did before, not when it broke). I can't exactly remember as I was actually browsing the internet when all of a sudden I noticed the screen of my phone was blinking.
So the situation is as follows:
When phone boots, I can see the white Samsung logo (on black background), and it blinks every 5-10 s. In short it is stuck in boot-loop.
I can access the download mode and emergency download mode
I can't access the recovery mode (when trying to access it, it goes to same boot-loop)
I have re-flashed latest ROM (Gingerbread) with Odin, but does not change
I have flashed older ROM (Froyo) with Odin, but it does not resolve the problem; only difference is that I have black-screen as part of the boot-loop (no white Samsung logo of any sort)
If connected by USB, the screen somehow blinks but I don't have Samsung logo
I have tried to flash with Odin with some of the Debug options, but without success:
I didn't tried the Phone EFS Clear, though as I thought it could cause further damage
I couldn't really try the "PDA Format" option as it actually crashes Odin (I am using v4.34)
Any idea what I can do?
Thanks!
Exactly like me
Hi,
Mine is a Samsung Ace, but apart from that, your situation is exactly like mine! Black blink, boot loop, have download mode, but flashing with odin didn't solve anything
So, does ANYBODY know what to do??
Could this be some virus? because I didn't flashed or anything my Ace. He was already very unstable, specially when I needed to use the Wifi...
Now, about solving this...
And did it happen all of a sudden?
(note: in my case I still haven't found a way to recover it)
Remove Battery, SIM card, SD card and attach phone to USB .Then pressing Q+power attach battery after 10 seconds
and see if odin detects it well and good
One of the main reason is bricked arm11boot.
Bricked B5510 Galaxy y pro can't enter recovery or download mode
Hi,
I can't enter recovery or download mode. After rooting (I do know how to enter download and recovery) I found this tool that could remove system applications. I used another tool to back everyting up.
Thinking I could always put the backup back, if someting went wrong. I uninstalled the dialer and other stuf/bloathware that I already had in Go Launcher EX (I like Go Launcher EX).
It did not work, but when I tried to put the backup back, THEN it warned me this could not always be done for system apps. (Little late!!)
So I can not enter recovery and download mode.
I think I know why, I am a windows programmer;
I have a Samsung account registered on my phone. (Used to recover phone when stolen)
Unfortunate I cannot remove that account from the phone. I do know the password, but the phone needs to connect to check that password or someting and it can't anymore) Strange since I have Wifi and that still works. I can't call, I can't SMS I cant remove my samsung account, but I can browse the web with my phone!
Damn how can I fix my phone just bought it!
Any suggestions welcome.....
Remi van Dongen
unclexnl said:
hi,
i can't enter recovery or download mode. After rooting (i do know how to enter download and recovery) i found this tool that could remove system applications. I used another tool to back everyting up.
Thinking i could always put the backup back, if someting went wrong. I uninstalled the dialer and other stuf/bloathware that i already had in go launcher ex (i like go launcher ex).
It did not work, but when i tried to put the backup back, then :d it warned me this could not always be done for system apps. (little late!!)
so i can not enter recovery and download mode.
I think i know why, i am a windows programmer;
i have a samsung account registered on my phone. (used to recover phone when stolen)
unfortunate i cannot remove that account from the phone. I do know the password, but the phone needs to connect to check that password or someting and it can't anymore) strange since i have wifi and that still works. I can't call, i can't sms i cant remove my samsung account, but i can browse the web with my phone!
Damn how can i fix my phone just bought it!
Any suggestions welcome.....
Remi van dongen
Click to expand...
Click to collapse
hi everybody my mobile also got bricked due to rom toolbos app now no downloading mode
no recovery mode
only works emergency download mode arm9
only ram dump mod arm9
i dont know how to unbrick my phone or is it posible to unbrick the phone in ram or emergency download mod arm 9 mod
please tell me my warranty just expired
B5510 odin stops at 50%
So I got a new B5510, and everyting had been nice then I used some ROOT font installer that also used BusyBox.
I installed a font and that bricked my new Samsung Galaxy TXT aka Samsung Galaxy y Pro. Not what I had in mind, I wanted a font change!
I found out how to get in boot mode it's easy, remove battery and any usb connector from phone. Hold Vol Down+Home then press power short and release keep holding Home+Vol Down. Then when warning appears press volume up
So I tried all ODIN version that could detect my phone.
Then I tried flashing with re-partition and luisa_0623.pit file
Best result got to 50% new phone still bricked.
I checked: Re-Partition, Auto Reboot and F. Reset Time
Added luisa_0623.pit
Added B5510XXKJ2_B5510OXFKJ1_B5510XXKJ2_HOME.tar.md5 to PHONE box
I got this output from ODIN 1.85 and it stopt at 50%:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> B5510XXKJ2_B5510OXFKJ1_B5510XXKJ2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> sbl.bin
<ID:0/009> NAND Write Start!!
<ID:0/009> Transmission Complete..
<ID:0/009> Now Writing.. Please wait about 2 minutes
<ID:0/009> Receive Response form LOKE
<ID:0/009> BcmCP.img
<ID:0/009> Transmission Complete..
<ID:0/009> Now Writing.. Please wait about 2 minutes
<ID:0/009> Receive Response form LOKE
<ID:0/009> boot.img
<ID:0/009> Transmission Complete..
<ID:0/009> Now Writing.. Please wait about 2 minutes
<ID:0/009> Receive Response form LOKE
<ID:0/009> system.img
<ID:0/009> Transmission Complete..
<ID:0/009> Now Writing.. Please wait about 2 minutes
<ID:0/009>
<ID:0/009> Receive Response form LOKE
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
DEAR SAMSUNG IF I CAN'T FLASH FIRMWARE ON YOUR DEVICE, I WILL NEVER BUY A SAMSUNG PHONE AGAIN!!!!!!! I need to be able to repair a bricked phone, it is just a software issue!!!
Why can't I flash, to unbrick????
you can use usb jig of sgs2 or ace it definately works and you can enter into factory download mode
how the problem solved?
Help me!!!!! Samsung Galaxy I5510 is Bicked...
I've bricked my gt-i5510 and trying to recover it with odin....
q+power button is not working for me But e+power button is working and odin recognizes my phone.
I choose files to be downloaded to the phone , on Odin, and press start then this message appears
<ID:0/022> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Arkas1519.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
Stuck in 'SetupConnection'
What to do to get back my phone in normal mode??
what is the suggestion????
Push
Hello,
i have the same Problem.... odin stuck in "Setup connection"
Use usb jig it works for me for my gt i5510 after using usb jig u enters in factory download mode and then you odin flash.
It is sure so checkout usb jig sgs2
Sent from my DROID2 GLOBAL using xda app-developers app
Same problem with my S5660(GIO).
Anyone knows the solution?
samsung GT-i5510 samsung logo screen only
Hii All,
Can anyone tell me ..my cell is just samsung logo screen only..
my download mode is not working q+power off button...
my emergency mode is working e+power off button...odin multi downloader detect the cell but doing anything on cell
pls anyone can help me to get back on download mode ...pls pls pls :crying::crying::crying:
and sorry for my Bad English ....
Use usb jig it works for me for my gt i5510 after using usb jig u enters in factory download mode and then you odin flash.
It is sure so checkout usb jig sgs
Sure it will pull you out from boot loop.usb jig is very cheap on ebay or you can make a search for home made in xda
bricked samsung gt-i5510
I too have the same problem.Unable to access download mode.
How ever Emergency mode is working but in odin I can't get any futhur then set up connection.
I also tries usb jig but instead of showing downloading mode, it just show samsung logo.
Please somebody help me out
Dil7nb said:
I've bricked my gt-i5510 and trying to recover it with odin....
q+power button is not working for me But e+power button is working and odin recognizes my phone.
I choose files to be downloaded to the phone , on Odin, and press start then this message appears
<ID:0/022> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Arkas1519.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
Stuck in 'SetupConnection'
What to do to get back my phone in normal mode??
what is the suggestion????
Click to expand...
Click to collapse
i have the same problem
Dil7nb said:
I've bricked my gt-i5510 and trying to recover it with odin....
q+power button is not working for me But e+power button is working and odin recognizes my phone.
I choose files to be downloaded to the phone , on Odin, and press start then this message appears
<ID:0/022> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Arkas1519.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
Stuck in 'SetupConnection'
What to do to get back my phone in normal mode??
what is the suggestion????
Click to expand...
Click to collapse
i have the same problem...
i have the same problem
may be must have JTAG before some mr.shifu come...
Ask for Help
Hello,
I updated my android using a Galaxy Y 2.3.6 Update which is for another phone, not my model.
Now my phone starts, plays the logo sound but i can't see nothing but a white display.
Is there any way i can reinstall the defalult software?
I can't boot into recovery and neither in odin download.
Kies see my device as a gt-s5360.
What can i do?
Hi,
I have a GS2 that wasnt being used so I decided to set it up in my bedroom as more of an email checker / facebook browser. I installed a JB rom, setup all my apps that I wanted & used it once or twice. A week later (yesterday) I went to pick it up, saw it was off, hit the power button & nothing. I pulled the battery & found it was stuck at the GSII screen. I am able to get into download mode, so I used Odin (I have the drivers installed already) trying to restore back to stock.
I used HOME_SPH-D710_CL852097_user.tar with Odin (a few different versions), I also used a few different cables & two different PC's. It keeps getting stuck at the same point which is boot.bin.
I tried a bunch of the other 1 clicks such as SPH-D710_GB27_1014481_Rooted_Restore & others. The results are the same.
Any ideas what else i can try?
Thanks,
Rich
Are you giving it enough time? Take about 20 minutes for mine to complete. Possibly longer with usb 1.1?
Sent from my SPH-D710 using xda app-developers app
Sounds like an EMMC failure...
Sent from my SGH-I337 using xda premium
Thanks guys, i am giving it plenty of time at this point it is collecting dust. I have tried multiple machines, multiple one clicks, multiple odin copies & restore files.
I can get into download mode but thats about it. I am at a complete loss on what to do.
There is one thing you can do... But for the life of me, I can't remember what it it called. What it does is partition your device in a way... You lose space but it fixes the issue.
Sent from my SGH-I337 using xda premium
I would be happy to give it a shot if you remember what I need to do.
Get in touch with @Stryke_the_Orc. I believe he was the one that was explaining the process to someone.
Sent from my SGH-I337 using xda premium
Uninstall your samsung drivers and kies if its installed, then reinstall your device drivers. There' two ways you can do this, one is to have the device in download mode and connect it to usb, the other is to install the drivers via an exe package found here
Once Odin recognizes your device, place the tar file found here in the PDA slot and hit start. You might also try the oneclick.exe.
If this doesn't work, let me know.
Stryke_the_Orc said:
Uninstall your samsung drivers and kies if its installed, then reinstall your device drivers. There' two ways you can do this, one is to have the device in download mode and connect it to usb, the other is to install the drivers via an exe package found here
Once Odin recognizes your device, place the tar file found here in the PDA slot and hit start. You might also try the oneclick.exe.
If this doesn't work, let me know.
Click to expand...
Click to collapse
I've tried your suggestions and am having no luck. I've tried different OCs and different cables and in different usb ports, on different computers even! I'm running out of ideas. Any help would be greatly appreciated.
I also sort of gave up. I have a paper weight on my desk & would be great to have it as a backup. Any ideas would be great!
Any way you can grab me screen shots of the process? I'd like to see what the screen is doing when it gets stuck:beer:
Slithering from the nether regions of a twisted mind and tarnished soul
I just encountered this problem myself. I downloaded rwilco's rooted oneclick nodata (which I have used a couple times in the past with flawless execution) and tried to reflash my ROM and it's stuck on the boot.bin. My phone's screen never changed from the default download screen with the ODIN count and warning messages and whatnot. This is the current ODIN log after 10 minutes of letting it sit here:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
As you can see, it never actually starts updating the firmware because it can't get past the boot part. I've tried multiple USB ports (one of which was USB3.0) and I've already tried uninstalling/reinstalling drivers. I think it's rather obvious there is some sort of communication error between my phone and my computer T_T It's also worth mentioning that Kies will not connect to the phone either. Both Odin and Kies detect that a phone is connected to my PC, but neither software seem to be able to connect to it.
I'm currently in the process of downloading the fullrestore (which I know won't work) to see if that works as well as a copy of standalone odin + the tar versions of the ROM. I will update this post with any progress/news I might have.
On the off chance that maybe someone knows a workaround for the problem that sparked my attempt at re-flashing: Today my phone froze and I held the power button to restart as I always do in such a situation. However, upon restarting my phone just sat at the "Samsung Galaxy S2" logo screen. I tried several battery pulls (with and without the SD card inserted) only to find myself staring at that same exact screen. Also, holding power+home+volup does nothing. The only screen I can access is the download screen (power+home+voldown)
Updates:
Upon trying the rooted full restore oneclick I encountered the same exact problem.
Upon trying Odin 3.09 with rwilco's rooted nodata tar file, I received the following error: <ID:0/003> SetupConnection.. <ID:0/003> Can't open the serial(COM) port.
Upon trying Odin 3.09 with the rooted nodata tar again on a different port, it started with NAND write and told me to wait a couple minutes before it gave up and just said failed.
I'm having an issue similar to this I think. I decided to reflash my phone I downloaded the oc I found on here and everything went fine but now when I press and hold the power button it don't power up. it just sits there. I can plug my charger in and it shows it is charging (the battery comes up) and I can get to DL mode but if I remove the charger and try to get to DL mode it says battery to low to enter download mode...what do I do?
update I don't know how or why but phone finaly booted into recovery for me did a factory reset and wiped cache and rebooted phone is up and running now
---------- Post added at 02:41 PM ---------- Previous post was at 02:16 PM ----------
WhyteDem0n said:
I just encountered this problem myself. I downloaded rwilco's rooted oneclick nodata (which I have used a couple times in the past with flawless execution) and tried to reflash my ROM and it's stuck on the boot.bin. My phone's screen never changed from the default download screen with the ODIN count and warning messages and whatnot. This is the current ODIN log after 10 minutes of letting it sit here:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
As you can see, it never actually starts updating the firmware because it can't get past the boot part. I've tried multiple USB ports (one of which was USB3.0) and I've already tried uninstalling/reinstalling drivers. I think it's rather obvious there is some sort of communication error between my phone and my computer T_T It's also worth mentioning that Kies will not connect to the phone either. Both Odin and Kies detect that a phone is connected to my PC, but neither software seem to be able to connect to it.
I'm currently in the process of downloading the fullrestore (which I know won't work) to see if that works as well as a copy of standalone odin + the tar versions of the ROM. I will update this post with any progress/news I might have.
On the off chance that maybe someone knows a workaround for the problem that sparked my attempt at re-flashing: Today my phone froze and I held the power button to restart as I always do in such a situation. However, upon restarting my phone just sat at the "Samsung Galaxy S2" logo screen. I tried several battery pulls (with and without the SD card inserted) only to find myself staring at that same exact screen. Also, holding power+home+volup does nothing. The only screen I can access is the download screen (power+home+voldown)
Updates:
Upon trying the rooted full restore oneclick I encountered the same exact problem.
Upon trying Odin 3.09 with rwilco's rooted nodata tar file, I received the following error: <ID:0/003> SetupConnection.. <ID:0/003> Can't open the serial(COM) port.
Upon trying Odin 3.09 with the rooted nodata tar again on a different port, it started with NAND write and told me to wait a couple minutes before it gave up and just said failed.
Click to expand...
Click to collapse
So now I'm having an issue with it not wanting to boot with out going through recoveryy then it only stays booted for a couple minuets
Sent from my C5155 using xda app-developers app
Well, this is my final update because I no longer have the phone. I was eligible for an upgrade as of the day my phone bricked so I said screw it and got a GS4 ^_^
Wish I'd seen this sooner, uninstalling kies and reinstalling your drivers should have fixed this for you. Unless you had hardware failure, which doesn't appear to have been the case.
Slithering from the nether regions of a twisted mind and tarnished soul
XxBriernxX said:
I'm having an issue similar to this I think. I decided to reflash my phone I downloaded the oc I found on here and everything went fine but now when I press and hold the power button it don't power up. it just sits there. I can plug my charger in and it shows it is charging (the battery comes up) and I can get to DL mode but if I remove the charger and try to get to DL mode it says battery to low to enter download mode...what do I do?
update I don't know how or why but phone finaly booted into recovery for me did a factory reset and wiped cache and rebooted phone is up and running now
---------- Post added at 02:41 PM ---------- Previous post was at 02:16 PM ----------
So now I'm having an issue with it not wanting to boot with out going through recoveryy then it only stays booted for a couple minuets
Sent from my C5155 using xda app-developers app
Click to expand...
Click to collapse
This sounds like a faulty battery, do the spin test on it and see if it's bloated.
Slithering from the nether regions of a twisted mind and tarnished soul
I still have my G2 & wouldnt mind using it with just wifi since I dont have sprint anymore but I am still stuck. Any suggestions on how to bring it back?
Stryke_the_Orc said:
This sounds like a faulty battery, do the spin test on it and see if it's bloated.
Slithering from the nether regions of a twisted mind and tarnished soul
Click to expand...
Click to collapse
for a second...just a split second I though you were recommending that I spin my phone around....I had a duh monet seeing as I'm at work lol. i'll give it a shot once this GB27 flash finishes...I've all but given up on my s2 and it sucks cause I really loved the lil bugger
Stryke_the_Orc said:
Wish I'd seen this sooner, uninstalling kies and reinstalling your drivers should have fixed this for you. Unless you had hardware failure, which doesn't appear to have been the case.
Slithering from the nether regions of a twisted mind and tarnished soul
Click to expand...
Click to collapse
I'm rather sure it was hardware failure. At the Sprint store, the technician attempted several times to get my phone into anything other than download mode. Needless to say, he failed every time and I told him not to bother because all my contacts were synced to my Google and/or Facebook accounts anyway. They still did me a solid and bought it back from me after pretending they never saw the issue
Anyway, I'm loving the upgrades provided by my S4 so no worries on my end! Good luck to you guys.
XxBriernxX said:
for a second...just a split second I though you were recommending that I spin my phone around....I had a duh monet seeing as I'm at work lol. i'll give it a shot once this GB27 flash finishes...I've all but given up on my s2 and it sucks cause I really loved the lil bugger
Click to expand...
Click to collapse
Did you figure out if the battery was the issue?
HI, n00b alert for starters
So went on a longer trip the other day, needed to use GPS on my rooted GNEX running AOKP 4.2.2 (its been a month plus now, but as far as I can remember, last kernel was Faux), when the device started to reboot randomly, sometimes straight from the GOOGLE logo, sometimes from within the OS, the longest it kept running being 10-20 mins. The display had sometimes a purplish hue when the system crashed, rebooted to GOOGLE logo w/ unlock icon, and booted normally. Since I thought it could be a hardware issue (remember reading GNEXs had problem with processors comming off the mainboard?), I wanted to have things back to normal/original before claiming warranty (haha, try to claim one with a broken glass), and for other reason to rule out possible FW/SW errors. Now this is where it gets tricky, since some time allredy passed: I updated via adb/GNEX TOOLKIT to the stock image of 4.3. Phone got stuck at GOOGLE logo, I was able to to get to fastboot, which I on one occasion somehow mistook for the fastboot mode, then I came across the idea of using ODIN without previous experience, and thats where things have gotten really bummed. I suppose I might have flashed wrong version, since the only thing that came up since then, is the "phone" /!\ "PC" screen. Since there was no way of getting into adb, fastboot, I decided to take a try and bring it to the dealership where a nice lady took the piece to the back room and came back with a suggestion of (equivalent of) USD 15 for repair. What a price for geting rid of such pain... When I came to pick it up, a sorry face greeting me said it all... No cigar... Never been told what they actually did, never really asked, since the symptoms were still the same. Then I let it sit for couple more weeks, then decided to have a second chance with it, since the screen comming up and at least some sort of acknowledgement by PC still gave some hope. I tried couple of ODIN methods found here as well as elsewhere, like CF-Root-GGN_YAKJU_ICL53F-v5.1, with no luck, the progress bar on display got either stuck after first 1/8", or went all the way through, but after time for settling, still just the triangle screen. Then I went to a H/W store, built a jig with MicroUSB A+301k (1% tol), which still brought me only to the yellow triangle. Then last night I started fondling around with OMAPflash: Downloaded the tuna zip file, pulled battery, started the batch, and voila all smoth, no errors, then I let the phone sit for some time only to boot to the triangle again! Tried this a couple of times more, same result. All the time, ODIN and OMAPflash, I used only 2 of my laptops USB ports. Then, for some reason, I used a port I hadnt used before, and voila, ODIN shows PASS! in 2:02 - 2:03 mins, but the thing still boots only to trisngle again! Between these tries, I randomly used the jig again to try if anything has changed, but still cant get to Download/fastboot. All this time, when I connect to pc, I keep getting various devices, mostly Samsung USB modem, with battery out and plugged in cable, the OMAP4440 device pops up intermittently to vanish after 2 secs (normal behavior as I read, OMAPflash still says its capable of downloading, gets its chore done, but then lets me sit there with the triangle again. Im slowly running out of Ideas (OK, Im tottaly out of ideas on what to do next, I came across a posting where a guy is suggested to have the JTAG done by, but it seems to me that the symptoms arent that bad to have it JTAGed. Yet. What would you suggest to do-try?
ODIN result after flashing CF-Root-GGN_YAKJU_ICL53F-v5.1.tar:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
Thanks for your energy spent on reading/answering this LONG post, any help greatly appreciated. PS: As a thank you, I am willing to spend couple bucks on charity of your choice (fund your beer yourself, there are bigger issues in this world / excuse possible typos, my keyboard sucks big time / and greetings from the Czech Republic!
To start out, some basic information. I got my SGH-T999 about 2 years ago and used it for about a year on the Stock ROM before proceeding to root the phone. The firmware version before things when went wrong was android 4.1.2. Everything was working fine until about a few days ago when the phone would stop being responsive after putting it into sleep mode, or the screen will turn black and the whole unit is unresponsive (the latter only occurring while I was in the home screen, not while running any apps. Rather, the phone would be fine while an app is running).
Troubleshoot Stage 1
Initialy, I thought there was some sort of app update that was causing this problem, and so I tried uninstalling a few apps that might have been culprits. Didn't work. On occasion, the phone would freeze up while i was trying to uninstall the app. So reading around, someone mentioned that it was possibly the TouchWiz Home that was acting up and I should, clear cache. So I rebooted into recovery (I had the clockworkmod recovery from the initial root). Cleared user data/factory reset as well as clear cache. Didn't work. At this point, the phone was restarting itself almost instantly after booting into the lock screen. I searched a bit more about why this would happen, and came across a post saying that I could be a faulty power button. I actually didn't want to physically alter my phone in any way, so I decided to try to do something with the software first before resorting to altering the physical phone.
Troubleshoot Stage 2
Next thought process was that maybe somehow an OTA was pushed onto my phone and now the firmware is screwed up because of it. So reading through many posts on XDA, I came upon this thread (http://forum.xda-developers.com/showthread.php?t=1771687) for a pre-rooted version of 4.3. I figured, if I was going to re-flash the firmware, I might as well go to the latest one. I proceed to go through the process of flashing the firmware with Odin 1.85, leaving Auto Reboot and F. Reset Time checked. Odin flashes PASS message and I unplug the phone and wait for the reset. Phone starts up all the way past all the logos and to where the home screen was supposed to be. But there was no home screen, just a black screen with only the pull down menu at the top and a message saying "Unfortunately, Settings has stopped working". This message would keep repeating even after pushing the ok button. Next thought process is, maybe TouchWiz is acting up still. So I boot to recovery, reset/format to factory, clear cache, and reboot. Now the phone wont boot past the Samsung logo. Tried to boot to recover again, phone won't boot to recovery anymore. Tried to re-flash the same exact firmware again and this time, odin had some trouble. It would sometimes stop working where it is loading the main code at which point I check the task manager to see if it is still running processes or utilizing any of the computer resources to communicate with the device. I would then have to unplug the phone and reset by removing the battery. This kept occurring about 2 more times before it successfully finished and on doing so, the original problem when I first flashed it was still there.
Troubleshoot Stage 3
Ok, maybe my phone doesn't like the pre-rooted firmware. Looked around XDA again and found this thread (http://forum.xda-developers.com/showthread.php?t=1949687) and downloaded the stock firmware. I stayed with android 4.3 because i read that I can no longer downgrade to a previous android version. Proceeded to flash the Stock firmware 4.3 using Odin 1.85. The process completed on the first try. SUCCESS!! Boot up phone, got past logo, home screen appeared. SUCCESS!! Here, I thought that I was done and my phone was finally working again. So I begin to tweak the settings for my own preferences. I didn't flash anything else or try to root the phone again. I was just plain using the Stock 4.3 firmware that I got from the thread above. After about 10 or so minutes of using the settings, the phone freezes and becomes unresponsive. Won't restart by holding the power button or return to the home screen with the home button. Only other option was to remove the batter and restart the phone. This time, the phone doesnt make it past the Samsung logo screen, and I can no longer boot into recovery. It was stuck on a boot loop and could only be turned off by removing the battery. It didn't occur to me that I should flash Clockworkmod Recovery to reset/format to factory and clear cache as I have read previously and thought that I could just re-flash the stock again. Nope, the same issue came up in Odin as it did with the pre-rooted firmware. Again, I went through the process of checking that Odin was no longer communicating with the phone before unplugging and restarting the procedures to flash the firmware. After about 3 times, the 4th time after unplugging, the screen that tells you "Firmware upgrade encountered an issue, Please select recovery mode in Kies & try again". And when I try to flash again using odin, I get the following message
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Troubleshoot Stage 4
New problem! I now no longer have a PIT partition........and reading around, I found this thread (http://www.sammobile.com/forum/showthread.php?t=15719) of someone who has the same error message coming up in Odin. Thus, I found the PIT file via this thread (http://forum.xda-developers.com/showthread.php?t=1848267&page=4) using the link given by DocHoliday77. Downloaded the T999_16GB.pit as the back panel of my phone indicated that the phone was 16GB. I begin trying to flash with Odin 1.85, checking Auto Reboot, re-partition, and F. Reset Time, including the PIT file and using the Stock 4.3 firmware. This didn't work and only came up with the following error message
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Complete(Write) operation failed.
<ID:0/012> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Tried, the same procedure with the pre-rooted 4.3 firmware, still the same message. And haven't gotten past this point since.
Looking back at what I choose to do to try an fix this shutting down problem, I realize there were a few things I could have tried before moving on. But now what I really want to figure out is whether or not my phone can be saved. What have I not tired and what is the end of end to rescue this phone or if its even worth rescuing. I read that JTAG would be the final resort, and I will take that into consideration. Any feedback on what procedures I could've missed would be great as well (for future reference). Thanks for reading this long post and I really do hope I can get this resolved.
I'll try to answer some of this but tbh, tl:dr.
I can very much appreciate a very thorough and detailed post when someone is asking for help. Don't take this the wrong way, but this was a bit much. I could've answered hours ago, but didn't have the time to read it. More importantly though, the majority of people will see how long it is and just close the thread and move on. Like I said, details are good to include, but it gets to a point where it's too overwhelming. Right now I don't even remember a good chunk of what you wrote, and I wasn't able to read it all to begin with.
Not trying to lecture you or anything, but wanted to address it in case it can help you in the future.
I'll try to answer what i can real quick... first, don't use Odin 1.85. That is a very old version. You should only use 3.07 or above. Best to stick with 3.09 or 3.10.
Try the pit file with one of those.
Put the pit file in the pit section and make sure re-partition is checked. Put the firmware in AP. F-Reset time and auto reboot should also be checked, but nothing else.
It does sound a lot like a faulty power switch probably caused all of this. The constant rebooting, crashing and boot looping can and will cause corruption. This is probably what happened to its internal pit. if so, it is very highly likely there is more corrupted data on some of the individual partitions. Depending on which ones, you may or may not be able to fix it without a jtag service.
It is also possible the memory itself could be damaged. If this is the case, the only option is a motherboard replacement. You probably won't know this for sure though unless you try a jtag repair and it fails.
I will say that if the power button is faulty, you should absolutely get that fixed before doing much else. Otherwise it could just bring you right back to where you are now.
If it were me, I would look for a device on ebay with a broken lcd, but a good motherboard with clean imei. Then swap the board. Otherwise it seems to me you'd be spending money on repairs that may or may not work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Thanks you so very much for the reply! Sorry that it was long and looking at it again, It really is TL: DR. I will keep that in mind for any future posts.
I have tried different versions of Odin 3.04, 3.06, 3.07, 3.09. The first two version also give the same message as version 1.85 while the latter two stall at initializing for more than and hour and there doesn't seem to be any progress. I will try Odin 3.10 and see what happens there.
I guess buying a broken LCD phone would be the best course of action cost-wise afterwards if Odin 3.10 doesn't work. Again I really can't thank you enough for all the help and taking the time to read my post.
Quick tip on buying used devices like that...Be Careful! Pay extra close attention to how every listing is worded. Only buy ones that say things like:
Fully functional except display
Powers on but no picture
Some will try to trip you up by using "clever" phrases, or trying to lead you to assumptions. Also, try to only but from sellers with excellent ratings and a large number of them. They will be more likely to help you if you have a problem.
Good luck!
Sent from my SGH-T999 using Tapatalk