hey everyone, im having a little trouble with my galaxy2.
its the canadian bell hd lte version, unrooted, running gingerbread 2.3.3. obviously i want to upgrade.
im comfortable with the rooting process using odin...etc.
heres my issue, ive done some looking but couldnt find anybody with the same issue or a solution.
upon attempting to enter download mode, with the phone off, using the vol down + home + pwr key, it does just that, totally skipping the "warning!" screen.
ive also found that odin will not recognize my phone, though the computer does, i am unsure if this is because of the bypass of the warning screen? maybe its time for a jig?
tldr phone will go into download mode, but odin will not recognize, no warning about custom os displayed.
thanks for looking.
Only reason I can think of for it not showing the warning screen before going directly into download mode is because you are holding down all the buttons for so long that it uses that as the "up" which it needs to go from the warning screen straight into download mode. *Like if you need to hold for 5 seconds to get into DL mode, try holding for 4.5 seconds so that you know it's booting into DL mode, but that you're certain you're not stilling holding down the UP button prematurely, so that it's going by the warning screen too quickly for you to notice -- if you really care enough at all*
What's most likely going on with ODIN not recognizing your device is that your Phone's Drivers has for some reason not installed correctly on your PC. That's not too rare of an occasion (happened to my brothers phone the other week when I tried to root it - wouldn't install drivers on my pc [thus not showing up in odin], so we had to use his computer (where they were already installed). What you can do (assuming this is the problem) is 1) Try using a different computer, and if you plug the phone in and the drivers do not start installing within the first minute and a half of connection then you can either look at the device option of windows (device and printer or w.e - see if there's an option for drivers, or uninstalling drivers [so that you can re-install] or something like that), or try downloading Kies (now used for official samsung updates), as I believe there is an option there to install your phone's drivers. Hope that helps, lemme know the results. I'm like 80% sure the problem you're having is the Drivers not being installed proplery on the comp.
dub_lyfe said:
hey everyone, im having a little trouble with my galaxy2.
its the canadian bell hd lte version, unrooted, running gingerbread 2.3.3. obviously i want to upgrade.
im comfortable with the rooting process using odin...etc.
heres my issue, ive done some looking but couldnt find anybody with the same issue or a solution.
upon attempting to enter download mode, with the phone off, using the vol down + home + pwr key, it does just that, totally skipping the "warning!" screen.
ive also found that odin will not recognize my phone, though the computer does, i am unsure if this is because of the bypass of the warning screen? maybe its time for a jig?
tldr phone will go into download mode, but odin will not recognize, no warning about custom os displayed.
thanks for looking.
Click to expand...
Click to collapse
Seems a little odd that it's skipping the warning but don't think it's a big issue.
As for the drivers I would suggest downloading the latest Kies software and installing any updates that should install all necessary drivers
I would then reboot computer and not launch Kies or anything else before opening Odin, Whenever I flash my phone I always run Odin from a fresh reboot just so I know that Kies isn't running or anything else to interfere with flashing process.
*Make sure Kies isn't running in the background when flashing things in Odin or strange things happen and flashing can get interrupted leading to possible bricked device.*
Also make sure USB debugging is enabled on your phone when you use Odin.
thanks for the reaponses!
it is wierd that its skipping the warning.
if a person puts the phone in dl mode, and at the warning screen chooses no, what happens? does the phone still go into dl mode or just reboot?
as for odin i cant check at the moment but ill try that, i have a feeling that the warning may have something to do with it, if someone wants to try to confirm my suspicions above?
will get back on the odin issue when i get a chance.
"ive done some looking but couldnt find anybody with the same issue or a solution." ... then look harder.
yea download the kies drivers or install a temporary cwm on your phone and go through that.
still have yet to get to a computer but messed with the device a bit.
it boots in recovery fine, still no warning for download mode.
also, if i dont continue to hold the dl mode button sequence till it goes straight into.dl.mode, the phone boots as normal.
so the theory of holding the buttons too long seems unlikely.
dub_lyfe said:
still have yet to get to a computer but messed with the device a bit.
it boots in recovery fine, still no warning for download mode.
also, if i dont continue to hold the dl mode button sequence till it goes straight into.dl.mode, the phone boots as normal.
so the theory of holding the buttons too long seems unlikely.
Click to expand...
Click to collapse
Alright I mean if you can get into recovery mode at this point (and download mode seems to work anyway, just doesn't give warning) shouldn't be a problem. If you do try getting the drivers from kies and use download mode then you can figure out if it's bonkers. If not, just use recovery to flash something and all should be well. That's quicker and easier anyway
Also, you should probably note that since you said you have the "canadian bell hd lte version", that you PROBABLY do not have a GT-I9100. So don't go flashing random stuff from the forum (which is for the I9100) - else I can almost guarantee you will run into problems.
(refer to this article, and this post)
If you are right about having the HD LTE version of the Galaxy S II, I'm betting you actually have the SGH-I757M. (you can verify this by looking on the label under the battery)
That phone (the SGH-I757M) doesn't have a dedicated forum, unfortunately. Your best bet is to search XDA for that model number, like this.
I was feeling generous, so I did a bit of legwork for you. The current latest Samsung official version is still 2.3.6. You can get it from sammobile.com. That will offer only minor updates from your current version of 2.3.3.
There IS the CyanogenMod9 custom ROM for your device, if you want to go that route. It'll be listed on the xda site search for your model number that I linked above.
In any case, I must warn you again against flashing anything that is meant for the i9100 Galaxy S II.
EDIT to add: the fact that the model is different from an I9100 could also explain the lack of a warning screen before download mode. There was no warning screen on my girlfriend's old Captivate prior to download mode, so maybe there isn't one on the SGH-I757M, either.
Related
Hi everyone. I have a samsung galaxy s vibrant on android 2.2. I am a total noob with any modifications but am going overseas next month and wanted to unlock my phone. After looking into rooting etc. I downloaded odin and darky's ROM resurrection edition. I followed the prompts to go into recovery and wipe etc. and remove battery and turn back on. After using odin and restarting my phone now just flashes the start screen showing galaxy s GT-I9000. I can't enter recovery mode just download mode. I'm unsure what to do and even tried mounting another recovery file on odin which lead me to the same point. Any help would be greatly appreciated.
Try re-flashing it and see if that works, sometimes that's all it takes. It's possible you just had a bad flash.
I've tried about 5 times now and it seems to keep failing to boot after flash and sticking on the initial boot screen and flashing on and off. Is there a way to download and flash an original ROM and mount on odin to start over?
Try getting into download mode. Hold and continue to hold up & down volume controls while holding in the power button. When the Vibrant logo comes up release only the power button. If you do get into recovery that way scroll down to install zip from sd card and install whatever rom you've got on there that you want to use. Let me know if that works or not.
I can still only get into download mode. I've tried flashing again with both ROMs I have and they both are doing the same thing. Holy frustrating lol
Spike84 said:
I can still only get into download mode. I've tried flashing again with both ROMs I have and they both are doing the same thing. Holy frustrating lol
Click to expand...
Click to collapse
Look for a hard surface... concrete for example.. now take your phone and throw it as hard as you can... Just kidding don't do that, that's a permanent reboot. I know the frustration, I've been there many times. You may want to go back and read through the noob guide, I'm not sure what else to suggest. Hopefully someone else will read this and have a better suggestion. Good luck.
haha yeah the thought crossed my mind. I appreciate your help. I'm still reading through the forum. Most instructions seem to require me to reach recovery mode or usb debugging. My phone is no longer being recognized on the computer but odin is obviously still recognizing so I'm going to try a fresh 2.2 on odin and see if that works.
Good luck, I'm rooting for ya. If that does not work and your close to a T-mobile store I'd just run it in and have them check it out, they may have to replace it.
Thanks again. I'm actually in Canada and using a sub provider from bell "virgin mobile".
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Remove Kies and reinstall see if it picks the phone up and installs the drivers .
jje
OperationIvy85 said:
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Click to expand...
Click to collapse
That kernel is for the Epic touch 4g is that your phone or do you have the international version? If you flashed the wrong kernel it could cause problems.
Yes it's an Epic touch 4g from sprint.
EDIT: Uninstalled Kies, reinstalled Kies, restarted computer, still no kind of recognition of my phone in any state (powered off, at "Firmware upgrade encountered" screen it boots into, or in download mode). Starting to get nervous, I used to at least hear a sound when plugging my phone into my comp. It is like there is nothing on the other end of the USB cable.
More things I have tried:
-All of the above steps on a different computer
-Sweet talking it
-Talking dirty to it
Am I brick'd? I figure not, since I can at least get into download mode. Not sure what else I can do though. I'd go see what the Sprint store can do for me, but on the download mode screen it lists my custom binary download count as 5, I understand they will see that and tell me I'm out of luck?
OperationIvy85 said:
More things I have tried:
-All of the above steps on a different computer
-Sweet talking it
-Talking dirty to it
Am I brick'd? I figure not, since I can at least get into download mode. Not sure what else I can do though. I'd go see what the Sprint store can do for me, but on the download mode screen it lists my custom binary download count as 5, I understand they will see that and tell me I'm out of luck?
Click to expand...
Click to collapse
Try to reset your binary counter with a usb jig.
you could try and download the drivers again from here and see if it then connects
http://modem-techno.blogspot.com/2010/09/epic-4g-usb-driver-download.html
I also had a similar problem once with an old i9000 and what worked was doing this and then connecting the phone first and then opening Odin.For some reason opening Odin first and connecting wouldnt find the phone.If nothing else works try wipeing the bin counter with the jig and send it back.Youll have to say that kies crashed while updating on Win7 64bits.Samsung know that before the September 30th kies update kies wasnt fully functional with 64bit drivers and they had a few phones replaced under warranty because of crashing kies updates on Win7 64bits.
Thanks for the replies everyone.
I made a USB jig but it had no result. I checked the resistance with a multimeter and I am connected across pins 4 and 5 of the usb dongle I bought. I plug it in and nothing happens.
I can still get into download mode by the usual means, just no recognition from my computer, odin, or kies. Very frustrating. Am I going to have to buy a new one or is there another way to reset the bin counter?
EDIT: Got the USB jig to work! I was using a bad diagram and was on pins 1/2 instead of 4/5. Now I can't boot, can't get to recovery, can't get any PC to recognize my phone in download mode.. but at least my download screen says "Custom binary download: NO." So if nothing else works before tomorrow evening I'm gonna bring this thing back to the Sprint store and tell them what cooza said about kies crashing on win7 64 bit. Thanks everyone! Also I just realized there is a specific forum for Epic 4G touch.. sorry >.>
The good thing is that your bin counter is at "0" again.The Kies thing is the real deal as there are also posts here on XDA of the same thing happening.I also know its true from first hand experience as it has happened to me and when i told them about the Win7 64bit driver problem (this happened to me a couple of months back too) they had no option but to accept it cos they know its true.Also i offered to e-mail links from forums with other complaints from users on 64bit PCs but they didnt even dought my storey and in 4 days it was back in my hand.I told them that when the update finalized the programe froze and the phone rebooted to a black screen.Had to pull the battery cos it appeared to be dead and refused to reboot again.Important to say that you where on Kies prior to the update I mentioned.Ived update to the latest Kies and it works fine now on my Win7 64bit so be carefull there that date is important
Thanks cooza I really appreciate your help. I do have a couple questions though.
1. Is the update you are referring to an update to Kies software.. or an update to the Galaxy S2? Reason I ask is because my phone is the Epic 4G Touch (accidentally posted in this forum >.>), will they still believe my story?
2. Not sure if you will know the answer to this one, but should I go through Samsung tech support or can I take it back to the Sprint store where I bought it?
3. Just trying to get clear on the story I should tell them. I was using Kies to update my phone on a Win7 64bit computer, but I accidentally used the version of Kies from before the Sept. 30 update? And then the phone crashed resulting in it's current state. Correct? Anything else I should watch out for?
4. With the problem you are describing with Win7 x64, does the phone go into a soft brick where it won't boot up?
Thanks again.. you've been very helpful
OperationIvy85 said:
Thanks cooza I really appreciate your help. I do have a couple questions though.
1. Is the update you are referring to an update to Kies software.. or an update to the Galaxy S2? Reason I ask is because my phone is the Epic 4G Touch (accidentally posted in this forum >.>), will they still believe my story?
2. Not sure if you will know the answer to this one, but should I go through Samsung tech support or can I take it back to the Sprint store where I bought it?
3. Just trying to get clear on the story I should tell them. I was using Kies to update my phone on a Win7 64bit computer, but I accidentally used the version of Kies from before the Sept. 30 update? And then the phone crashed resulting in it's current state. Correct? Anything else I should watch out for?
4. With the problem you are describing with Win7 x64, does the phone go into a soft brick where it won't boot up?
Thanks again.. you've been very helpful
Click to expand...
Click to collapse
Kies via to its Sep 30th update was not fully compatable with 64bits and gave a lot of problems to a lot of people.I had a few problems with it when I got a new laptop (HP Win7 64bit) so started searching the web for solutions and found that kies was designed mainly to support the windowsXP versions 32bit and had caused Samsung to accept various repairs under warranty because of crashing Kies updates mainly on android running phones.For some reason Bada didnt seam to affected.Maybe cos there arnt to many around like android.In the 4G forum there is post from someone who has bricked their phone using Kies to update and a reply from another with the same problem.Take it into where you bought it to start with and if its not there problem then they might send it back to Samsung for you.All you need to say is that you where updating your firmware via kies and on completion it froze and the phone booted to a black screen like mine did.You had to pull the battery and restart your PC to close Kies cos it wouldnt close or minimize or anything.Tell them that you searched on the net for possible causes and found what i told you about Kies and since you have a Win7 64bits PC then thats most likely to have been the cause.Your bin counter is at 0 so there is no way they can counter-attack your story.
OperationIvy85 said:
Hi all. I have searched for this problem and found some similar ones, but nothing quite like this.
The problem first started when I tried flashing Zedomax Kernel v3 via Odin. Odin reported a successful flash, but when it went to reboot it sat at the Galaxy S2 splash screen with yellow triangle for about 45 mins. I figured something was wrong so rebooted to CWM. I was able to get into both CWM and download mode at this point.
No matter what I tried I could not get the phone to boot up, so I thought I would try flashing a factory image to get back to out of the box settings. In the middle of this Odin got stuck on a step and then failed out after a good 10-30 minutes (sorry for lack of detail, this was pretty late last night).
Now, when I try to boot into recovery mode I see the [phone]....!....[computer] screen with the message "Firmware upgrade encountered" (part of this screen is cut off on the right, and appears to overflow to the left side? weird). I can boot into download mode, but Odin doesn't see my phone when I plug it in. The device doesn't show up in device manager either.
Things I have tried:
-Different USB port
-Kies "Resolution connection errors" button, which seems to reinstall the drivers
-Reboot computer after above step
-Remove battery from phone and replace
After these steps I still can't get my computer to see my plugged in phone in any way. I'm getting kinda nervous but the only thing giving me hope is that I can get it into download mode. Any ideas on how to get Odin to see it again?
Click to expand...
Click to collapse
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Who told you that the exclamation point means you voided your warranty?
bajaber said:
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Click to expand...
Click to collapse
The exclamation point on a normal boot up screen (Galaxy S II splash screen) means there is a custom rom installed. This can be removed with a USB jig, which will also reset your custom binary counter.
I have absolutely no idea still what [phone]....!....[computer] means though. I ended up taking my phone back to the Sprint store and they replaced it for a small service charge while telling me next time I won't be so lucky. My next step was going to be to try calling Samsung with the story cooza suggested. I told that same story to the people at Sprint but they definitely didn't buy it, but you may have better luck with Samsung. If you get this resolved I'd be curious to hear how, but I am not optimistic for you
bajaber said:
I also have this same problem now. Except that....I cannot even get into download mode. My phone is stuck at the [phone]....!....[computer] screen, but without any message. I am told that the exclamation mark tells Samsung that warranty is voided.
Is there anyway I can do anything to save my phone?
Click to expand...
Click to collapse
The sign you see means that your phone is semi-bricked and that you needed a jig to force the phone to boot into download mode.You can buy one on ebay for a couple of bucks.Best you do cos it could may mean that your warranty is void.Let me explain,no one can actually say that your warranty is void because of this sign but being only "semi-bricked" the service centre are still able to enter the phone and see the bin counter.So if you semi-bricked flashing a non official firmware or you have done so earlier and your bin counter is not at 0 then YES your warranty is void.Semi-brick is not so bad as you can normally fix it yourself but Hard-brick is a dead phone and you gotta pay for a jtag .In your case buy a jig force the phone into download mode and re-flash it yourself.You shouldnt need to go anywhere.Semi-bricking is something you save yourself.Just wait till the jig arrives in the mail.
EDIT:there have been posts of people pulling the battery for 10min and re-trying and it has booted to download.They say they have had to do so 4 or 5 times for it to finally work but if youve got time on your hands then give it a try.
---------- Post added at 04:48 PM ---------- Previous post was at 04:22 PM ----------
OperationIvy85 said:
The exclamation point on a normal boot up screen (Galaxy S II splash screen) means there is a custom rom installed. This can be removed with a USB jig, which will also reset your custom binary counter.
I have absolutely no idea still what [phone]....!....[computer] means though. I ended up taking my phone back to the Sprint store and they replaced it for a small service charge while telling me next time I won't be so lucky. My next step was going to be to try calling Samsung with the story cooza suggested. I told that same story to the people at Sprint but they definitely didn't buy it, but you may have better luck with Samsung. If you get this resolved I'd be curious to hear how, but I am not optimistic for you
Click to expand...
Click to collapse
Well at least you got a phone now hope they didnt charge to much!!!!Good on ya mate
Update on my issue....
It turns out the problem is because I tried to flash an I1900 firmware while my phone is a G variant (I900G).
After using the right firmware, it worked.
OperationIvy85 said:
Thanks for the replies everyone.
I made a USB jig but it had no result. I checked the resistance with a multimeter and I am connected across pins 4 and 5 of the usb dongle I bought. I plug it in and nothing happens.
I can still get into download mode by the usual means, just no recognition from my computer, odin, or kies. Very frustrating. Am I going to have to buy a new one or is there another way to reset the bin counter?
EDIT: Got the USB jig to work! I was using a bad diagram and was on pins 1/2 instead of 4/5. Now I can't boot, can't get to recovery, can't get any PC to recognize my phone in download mode.. but at least my download screen says "Custom binary download: NO." So if nothing else works before tomorrow evening I'm gonna bring this thing back to the Sprint store and tell them what cooza said about kies crashing on win7 64 bit. Thanks everyone! Also I just realized there is a specific forum for Epic 4G touch.. sorry >.>
Click to expand...
Click to collapse
Hi, I'm having an exactly same problem with you and I just got a USB jig in mail, but even though I am following the instructions for the USB jig the counter is still not going back to 0 :/
This is the instruction I followed: take battery out for like a minute -> put the battery in but don't turn phone on -> put the usb jig in -> it's supposed to boot up with 0 flash count?
Mine still says 4... Can anyone please help?
sfoksn said:
Hi, I'm having an exactly same problem with you and I just got a USB jig in mail, but even though I am following the instructions for the USB jig the counter is still not going back to 0 :/
This is the instruction I followed: take battery out for like a minute -> put the battery in but don't turn phone on -> put the usb jig in -> it's supposed to boot up with 0 flash count?
Mine still says 4... Can anyone please help?
Click to expand...
Click to collapse
Is yours a i9100? If so is your firmware the latest 2.3.5 KI3 or KI8?
Could be your device has the new bootloader. If so check intratechs original firmware thread in original development section and install his old bootloader via Odin. Have a read while your there to get the latest info.
Good luck
Sent from my GT-I9100 using XDA App
aceofclubs said:
Is yours a i9100? If so is your firmware the latest 2.3.5 KI3 or KI8?
Could be your device has the new bootloader. If so check intratechs original firmware thread in original development section and install his old bootloader via Odin. Have a read while your there to get the latest info.
Good luck
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yeah, I got stuck while flashing 2.3.5 Gingerbread... Yeah I think it has a new bootloader, as I remember Odin updating the bootloader section before messing up.
Is there any way I can get the USB jig to work? My phone is no longer recognized by the USB anymore so I can't even flash another bootloader or anything.
Is there anythign I could do to make the USB jig work without connecting it to the computer?
Can you get into download mode using the buttons?
Volume down+home+power
If so try and flash another Rom from intratechs thread to get back to stock.
If that works you can try again.
Sent from my GT-I9100 using XDA App
i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
machv5 said:
i was trying to root a phone for someone and after odin completed it said it had failed.
the phone is a telus samsung t959d running froyo.
I followed the instructions from (I would post the url for the link but i am not allowed to.)cyanogenmod's wiki, after it failed I rebooted the phone and it got stuck on the screen in the attached pic. I have tried to boot back into download mode to no avail. From the screen it's stuck on I cannot get any tool to register the device as being present, adb, heimdall, zdiag, etc... I even tried fastboot out of desperation.Before I used odin I tried to get the phone to boot into the bootloader but it only ever went to either recovery or a normal boot and I tried every button press combo I could think of and found and nada.
Even running adb reboot bootloader just made the device boot normally. I think that if I could get it to boot to fastboot usb i could then try fastboot. I am new to rooting devices and have successfully rooted my HTC EVO3D and got s-off and simlock removed for any carrier. So I do know how to follow instructions properly, why flashing the recovery.bin failed I don't know and every fix I seem to find says BOOT TO DOWNLOAD MODE. if I could do that I wouldn't be having this problem lol. Anyway can someone please help me figure this out. Thanks. ANd if you need any further info please let me know. I don't want to have to give my friend my phone due to a software issue.
And YES I did pick PDA not anything else.
Click to expand...
Click to collapse
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
machv5 said:
I kept reading other threads and sadly I din't pully the battery first before disconnecting the usb and repartition may have been checked as I see that it does the as default for my version. Also i turned off ODIN as I was hoping a reboot of my computer might help. I will keep trying to find an answer till someone gets back to me. this post may not even show up if I can't do a second post if no one has replied first.
Everyone was a nub at one time wasn't it FUN hahahahahaha sob cry
Click to expand...
Click to collapse
I tried a jig and that didn't work. There must be some way of getting the device to give up on completing a task i no longer can give it due to ODIN being shut off.
Why is it that the "how to root/unlocks" never have the "if x fails then do these steps etc..." Had the how to had "pull the battery before disconnecting USB and don't reset or shut off ODIN" I wouldn't be in this mess. I realize that it's user beware but a few important steps like that in case of a fail would go a long way to you guys not shaking your heads. Instead of "silly nub hahahahahaha". No offence but I get that a lot and try to remember that when I teach someone how to use a computer. I am new at phones not at everything.
Further Developments Please can someone help?
I was giving someone a new memory card and they had a Samsung SGH-I896 it has an EB575152VA battery and the one I have the T959D has an EB575152VU battery. I exchanged my battery for hers by accident somehow and when I plugged my phone in it didn't go to the phone triangle computer logo screen it booted to recovery and said it couldn't charge the battery and kept rebooting to recovery. I got my battery back and it booted back to the phone triangle computer logo again. Grrrr....
The other thing I saw while the recovery screen was an error message that said
Code:
E:/data/fota not accessible
(may not be 100% accurate I don't have the battery to check right now but can get it again if need be) anyway I now see that there may be some light at the end of the tunnel. i have the correct stock firmware for the device I tried flashing it while in recovery but the phone kept rebooting before anything got done. My question is how can I get the dang phone to stop asking for Odin and go to recovery so I can flash stock firmware and ROM back to it? As I cannot as far as I know give it what it wants because I reset Odin and nothing seems to see that the phone is connected to the computer. I am going to try the other battery on a full charge to see what that does.
I am new at all this and want to get it fixed. I cannot afford to send it off to a service center and besides that I want to do it myself as I want to become a developer and droid technician. I would gladly donate to anyone but am still trying to get Google to accept my pay-as-you-go credit card and I don't have PayPal either. Which is really frustrating when it comes to giving back. I posted a Q&A on how to without PayPal or CC but as of the last time I checked no one has gotten back to me about it.
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
The CyanogenMod guide is flat out WRONG. I've tried to change it, but anything I do is reverted in an instant. I also tried to use it to install the ROM only, ended up bricking my phone and it took me hours to unbrick. That's how I became acquainted with XDA.
So, to get this straight:
1. you're using the stock USB cable
2. you remove the battery
3. you hold volume down
4. you plug in the usb cable
5. after a few seconds, you release volume down
6. the screen does not display a yellow triangle with an android
Posted from my Galaxy Tab with CM10
Click to expand...
Click to collapse
That is correct. If you think that my idea below is a bad one or if I downloaded the wrong firmware package please let me know and /or you have a fix that will work? ty
I have though come up with an idea that may work. I am going to charge the "wrong" battery in erm the right phone lol and then use it to trick the device into booting into recovery instead of the cellphone triangle computer (CTC, for want of a better acronym) The I896 battery ends in a V not an ? (sorry can't rem don't have it on me) from the I896 model I think it is, plugging it into USB with the power off sends it to recovery with the "battery cannot be charged " message instead of the CTC screen.
I tried it but the charge in the battery was too low and rebooted. I am hoping that with a full charge (as long as I don't power on the phone first as this will make it go to CTC logo again.
I am hoping that I can install the update.zip that I made by first unzipping the T959UVJFD_firmware.tar I downloaded then unpacked and then repacked into an update.zip as I don't think that it will read the package as a tar file and if it's not called update.zip The recovery is still stock. If I get the phone working I am not going to try unlocking and rooting it again. I will just post two separate adverts one as a carrier locked device and the other one (higher of course to cover buying the unlock from Telus) as carrier unlocked and then I will buy the unlock code if the blah blah you get the drift. sorry for rambling on.
oh and I can't rem if I said this or not, In recovery it "E:/data/fota not accessible" I don't know what that means yet I have been busy with other things and haven't looked it up yet.
Since you can get into at least some version of recovery, your bootloader is intact and you should be able to unbrick it. You ought to be able to get into download mode using a download jig. You can get one on ebay for a few bucks or you can make one yourself. There's a guide floating around here somewhere that lets you make one from a microusb cable.
Posted from my Galaxy Tab with CM10
Is my Samsung Galaxy Note 2 Bricked ?
I got the phone from Ebay on July 6,2015 everything was great
But on the morning of Sep 21st looking at my gallery pictures, I found they deleted themselves?
not knowing what that meant I went looking for recovery software "Wondershare Dr.Fone for Android"
it was not working so I had to root(?) my phone, so I went to the google play store and found a root app that seem
to have high reviews, tried it and did not work out right the phone restated saying "Samsung's firmware upgrade encountered an issue" so the next day did some research first before trying anything. I downloaded Odin3 and entered download mode & flashed the Samsung it restarted had it on for 3-4 hours
then turned it off & turned it on later to find it would not go pass the Samsung logo so I went to hold the off button shutting the phone off that happen 2 times and on the 3rd try turning it on It did not come on at all. Went to see if google had anything on this some say it is bricked and need to use a jig so I got one from a USA seller on ebay and returned it because it did not work at all. Not the phone still won't come on & I can't enter download mode, how do I fix this, is it a boot loader problem? is it hard bricked? do I need to take it to someone if so who & how much would that cost? you think.
Other Info of the phone
70% of battery is on the phone
It's factory Unlocked
Root Software I tried to use was (Kingo SuperUser)[Root]
I found they deleted themselves?
not knowing what that meant I went looking for recovery software "Wondershare Dr.Fone for Android"
it was not working so I had to root(?) my phone, so I went to the google play store and found a root app that seem
to have high reviews, tried it and did not work out right "UNQUOTE"...........What was the reasoning behind the rooting your phone for lost pictures??? if had wanted to get into the stock 3E recovery of your phone, all you had to do was, rocker up on Volume,pwr on, and menu key......dr phone may have flashed the wrong Bootloader, which makes you extremely lucky it even turned on to Odin it.....the problem your facing with it not turning on at all could be either [1] you have the wrong primary boot loader on it, which means its hard bricked, but im thinking you have a bad battery, because you were able to restart it after you flashed what exactly with Odin??......what did you flash with Odin??...an entire ROM, a bootloader file, or a kernel file by wrong chance, whatever it was we need to know... your not giving out enough info here, to determine if it was the correct SW for the phone you have, also what did you tick or not tick with Odin??.... extremely weak or going bad battery's cause abnormal voltages and abnormal symptoms as well...you might have a battery that finally went completely bad!!....there's usually only 3 things that cause a phone to not power on!...1] flashing wrong firmware, corrupting the primary bootloader...2]bad internal/failed hardware...3] a bad battery either its causing abnormal voltages or producing nothing from being totally dead!!...you state you cant power on anything, nothing visually illuminates, plus your saying it wont go into DL mode....volume rocker down, menu button and the pwr button all together will get you into DL mode, if you can power on a DL mode to the phone it is NOT HARDBRICKED!!...that means a softbrick situation= SW corruption....we need further more detailed info here!!...BTW YOU POSTED THIS QUESTION IN THE WRONG FORUM, THIS IS DISCUSSION FORUM , OTHER FORUM IS FOR TROUBLESHOOTING, WHICH IS WHAT YOUR TRYING TO DO HERE!!!
dseldown said:
I found they deleted themselves?
not knowing what that meant I went looking for recovery software "Wondershare Dr.Fone for Android"
it was not working so I had to root(?) my phone, so I went to the google play store and found a root app that seem
to have high reviews, tried it and did not work out right "UNQUOTE"...........What was the reasoning behind the rooting your phone for lost pictures??? if had wanted to get into the stock 3E recovery of your phone, all you had to do was, rocker up on Volume,pwr on, and menu key......dr phone may have flashed the wrong Bootloader, which makes you extremely lucky it even turned on to Odin it.....the problem your facing with it not turning on at all could be either [1] you have the wrong primary boot loader on it, which means its hard bricked, but im thinking you have a bad battery, because you were able to restart it after you flashed what exactly with Odin??......what did you flash with Odin??...an entire ROM, a bootloader file, or a kernel file by wrong chance, whatever it was we need to know... your not giving out enough info here, to determine if it was the correct SW for the phone you have, also what did you tick or not tick with Odin??.... extremely weak or going bad battery's cause abnormal voltages and abnormal symptoms as well...you might have a battery that finally went completely bad!!....there's usually only 3 things that cause a phone to not power on!...1] flashing wrong firmware, corrupting the primary bootloader...2]bad internal/failed hardware...3] a bad battery either its causing abnormal voltages or producing nothing from being totally dead!!...you state you cant power on anything, nothing visually illuminates, plus your saying it wont go into DL mode....volume rocker down, menu button and the pwr button all together will get you into DL mode, if you can power on a DL mode to the phone it is NOT HARDBRICKED!!...that means a softbrick situation= SW corruption....we need further more detailed info here!!...BTW YOU POSTED THIS QUESTION IN THE WRONG FORUM, THIS IS DISCUSSION FORUM , OTHER FORUM IS FOR TROUBLESHOOTING, WHICH IS WHAT YOUR TRYING TO DO HERE!!!
Click to expand...
Click to collapse
Should I post this in the Troubleshooting Forum?
The pictures I took on the phone disappeared all 300+ pictures disappeared .I am the only one using the Samsung
and it was on my table all that day. So I went to google to find a photo recovery software & found a software called
Wondershare Dr.Fone for Android (you can find videos on youtube) & using the software it can do 2 things, auto root the phone to find the photos and bring it back to normal or you Have to have your phone rooted. The auto root setting was not working on the Wondershare Dr.Fone for Android software so I went to the google play store on my Samsung and found a root app that a lot seem to like as it was 4.4 stars, went to install that the app stated I should have "Kingo SuperUser" on my computer so had that put on the went to root the phone & it did not work.
I got a screen on the Samsung saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Youtube had a video on this same problem so I went to Sammobile's site and download the firmware what was
"2014-06-11 USA(Verizon) Version 4.4.2 PDA (I605VRUFND7) Kies. After I downloaded that I downloaded Odin3_v3.10.6 opened it had auto "Reboot & F.Reset Time" selected and added the firmware MD5 file add in the "AP" secion then Entered Download mode on the Samsung & hooked it up to my computer
then I hit start about 30min later it Passed with a green light and everything seem back to normal 3 hours later I went to turn the Samsung off and latter that night when I went to turn it on it got stuck at the Samsung logo that happen 2 times and on the third time it did not come on & so can't "enter download mode" and the "usb Jig" did not
work. What happen & what do I need to next. Do I take the phone to someone to fix this.
Short version of the story
.Pictures I took 300+ disappeared so when looking for recovery software
.Found a software called "Wondershare Dr.Fone for Android" (the software had "2" Options for recovering. 1 the software would
Auto Root and bring the Samsung back to normal after recovering the pictures or I would have to had the phone already rooted.
. When to the google play store with the Samsung, found a root app download that & "It stated I should download "Kingo SuperUser" to my computer so I did that.
.It failed & got a screen on the Samsung Saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
.Went to Sammobile's site and download Firmware 2014-06-11 USA(Verizon) Version 4.4.2 PDA (I605VRUFND7) Kies
.Download Odin3_v3.10.6 had auto "Reboot & F.Reset Time" selected and added the firmware MD5 file add in the "AP" secion
Entered download mode & the Samsung passed
.Everything was back I had it on for 3-4 hours then shutdown the phone later that night went to turn on and it got stuck
at the Samsung logo 2 times and on the 3rd time it would not turn on nor enter "Download Mode"
.Got a "usb Jig" & that did not work and now I am here wondering what do next & what happen to my Samsung Galaxy Note 2 do I need to take to someone to fix it ?
Samsung Galaxy Not 2 Unlocked
SCH-I605V version (Verizon)
my battery was %70 full
You may have a possible hardware problem then= a bad motherboard and possible replacement!!!....Can you power it on in anyway shape or form??...meaning can you toggle it into recovery??...can you toggle it into DL mode??....does it pwr on to the bootloader screen and continuously loop???.....if you can do any of those things then its not hardbricked, which means you need to reconstuct the SW and then see if the Hardware holds stable....If it doesn't....then it could be a severe HW problem!!!....For the future be advised that, you completely took the wrong road to achieving blindly what you intended to do!!...meaning ....you should've completely took control of the situation and been totally proactive in your rooting and unlocking the bootloader...you wrongly turned to 3rd party APP's when you should've read first...educated yourself completely on what you were to embark on, and then set everything up with 3 different choices of rooting/unlocking..again depending on what ROM version your operating on, before engaging!!.....NEVER TRUST 3rd party APP's to do something only you should have step by step control of = lazy!!!.....I personally wouldve 1st tried to get to the stock 3e recovery, and attempt a nandroid backup of the phone as it was...then afterwards try to get the phone detected on my computer, so as to access the file containing the photos, transferred them to the computer safely... then flash the phone to a stock ROM with root already baked in or not = equals totaly factory stock.. doesnt really matter!!!.... and then set up the phone again, and see what it WILL!!! or WONT!!! do!!...point is, easter-egging a problem carelessly, will cause you to either install the wrong stuff or go completely outta proper sequence and either hose the SW, or worst case scenario....corrupt the primary Bootloader and hardbrick it!!....if you can power it into DL mode!!!.... Then, 1st BEFORE YOU DO ANYTHING!!.... go get Odin 3.07....then get the Samsung drivers for your computer to detect the phone...then DL the Pit file "sch-1605-16gb.pit"....then the proper stock ROM..4.1.1...4.1.2 in .TAR files only, BTW there is a stock 4.1.2 with rooted already in it!!....and then flash your phone using Odin with the pit file and then tick the PDA .tar file of whatever ROM. you choose.....I suggest 4.1.2 as a base to start with and reconstruct it, re-root it if necessary, that's if you choose the one W/O rooted baked into the ROM and unlock it with advice above using ghetto root, do not use adams outlers unlocker, there seems to be problems with it, triggering KNOX, and YOU DO NOT WANT THAT TO HAPPEN!!....relying on 3rd party app's will FK you up....use your head...not your heart!!...and yes you really should post NEXT time in the trouble-shooting forum, but for now leave it here!!...for your benefit!!
dseldown said:
You may have a possible hardware problem then= a bad motherboard and possible replacement!!!....Can you power it on in anyway shape or form??...meaning can you toggle it into recovery??...can you toggle it into DL mode??....does it pwr on to the bootloader screen and continuously loop???.....if you can do any of those things then its not hardbricked, which means you need to reconstuct the SW and then see if the Hardware holds stable....If it doesn't....then it could be a severe HW problem!!!....For the future be advised that, you completely took the wrong road to achieving blindly what you intended to do!!...meaning ....you should've completely took control of the situation and been totally proactive in your rooting and unlocking the bootloader...you wrongly turned to 3rd party APP's when you should've read first...educated yourself completely on what you were to embark on, and then set everything up with 3 different choices of rooting/unlocking..again depending on what ROM version your operating on, before engaging!!.....NEVER TRUST 3rd party APP's to do something only you should have step by step control of = lazy!!!.....I personally wouldve 1st tried to get to the stock 3e recovery, and attempt a nandroid backup of the phone as it was...then afterwards try to get the phone detected on my computer, so as to access the file containing the photos, transferred them to the computer safely... then flash the phone to a stock ROM with root already baked in or not = equals totaly factory stock.. doesnt really matter!!!.... and then set up the phone again, and see what it WILL!!! or WONT!!! do!!...point is, easter-egging a problem carelessly, will cause you to either install the wrong stuff or go completely outta proper sequence and either hose the SW, or worst case scenario....corrupt the primary Bootloader and hardbrick it!!....if you can power it into DL mode!!!.... Then, 1st BEFORE YOU DO ANYTHING!!.... go get Odin 3.07....then get the Samsung drivers for your computer to detect the phone...then DL the Pit file "sch-1605-16gb.pit"....then the proper stock ROM..4.1.1...4.1.2 in .TAR files only, BTW there is a stock 4.1.2 with rooted already in it!!....and then flash your phone using Odin with the pit file and then tick the PDA .tar file of whatever ROM. you choose.....I suggest 4.1.2 as a base to start with and reconstruct it, re-root it if necessary, that's if you choose the one W/O rooted baked into the ROM and unlock it with advice above using ghetto root, do not use adams outlers unlocker, there seems to be problems with it, triggering KNOX, and YOU DO NOT WANT THAT TO HAPPEN!!....relying on 3rd party app's will FK you up....use your head...not your heart!!...and yes you really should post NEXT time in the trouble-shooting forum, but for now leave it here!!...for your benefit!!
Click to expand...
Click to collapse
I guess it's the hardware? as It won't come on nor enter Download mode.
Now what, Do I take it somewhere? to fix it what ever it is ?
http://mobiletechvideos.com/
bigmike35 said:
Are you saying I can take it to them to fix it ?
Click to expand...
Click to collapse
SamsungNoteFan said:
bigmike35 said:
Are you saying I can take it to them to fix it ?
Click to expand...
Click to collapse
You cant take it but you can mail it. They unbricked my phone awhile back when something happened. It was good service. I rec'
Click to expand...
Click to collapse
Hey all,
First i'd like to tell my phone was 'working' as it was able to go to download mode.
Im not really an expert, but when I used Google to find a solution for my error I read about using Odin.
(In case you need the error, I will try to edit the thread and add this asap!)
I followed a tutorial about using Odin and tried to get my phone up back and running.
I downloaded the following file for my Samsung J5:
sammobile.com/firmwares/galaxy-j5/SM-J500FN/PHN/download/J500FNXXS1BQG3/181971/
After using the Odin software it somehow got interrupted while installing. (cable came loose I guess, I heard the connect/disconnect sound shortly after each other)
Also I noticed there was a small red text on the screen complaining about the available size on the phone.
Even though the phone installation was interrupted, the phone was still able to get into download mode.
Next up, I decided to place a micro SD card to get extra storage space and retried the Odin process. The final result was a "PASS" (see screenshot)
i.imgur.com/WzFJLaQ.jpg
After the update was done 'succesfully' the phone screen immediately turned to black.
There were no signs of life anymore, not even accessing boot mode / recovery mode no nothing.
I've bought an USB JIG, but sadly also with the JIG I had no luck.
Is there any way to get my phone back and running? or can anyone give me some advice?
I really hope someone can help me out!
Sounds like a hard brick ?
This happens when you try to upgrade or downgrade, some devices don´t allow this or the firmware is not matching.
Pull out battery if it is removable for some minutes then try normal method, if not....
Here the correct method to do a jig by your own or maybe it´s better to buy one (it´s not expensive) to made sure that is correctly made http://www.instructables.com/id/USB-JIG-to-give-life-to-your-Bricked-mobile/
Also you can try with Smart Switch https://youtu.be/y8AZyalTf5Y
Sands207 said:
Sounds like a hard brick ?
Click to expand...
Click to collapse
Can you check your pm's?