I've just spent many hours trying to revive my AT&T I777 phone that was running CM9 until I tried to flash it back to bone stock GB, then ICS.
First, I used ODIN to flash the standard default UCKH7 Gingerbread ROM from Sammy via One-Click "I777_UCKH7_OCD_No_BL.7z". After performing the ODIN, the phone flashed successfully and rebooted into a boot loop "Rethink Possible".
I searched for hours to find a solution, but one solution lead to another problem, and so on...
Currently:
- I cannot get into recovery mode, but it boots reliably into download mode. Tried the 3 button tango in EVERY way, but it will only go into DL mode.
- I've tried many different ODIN flashable images per recommendation in this forum, even the one that contains all of the extra files (recommended by creepyncrawly). All flashed fine, but none fixed the boot loop issue.
- Most recommendations say to "wipe/factory reset" to fix the bootloop issue, but I can't do that since I can't get into recovery.
- Tried to do ADB REBOOT RECOVERY, but can't get the driver to connect and list the device. The install guide says to enter "debug mode", but I can't even boot the phone.
- Tried Kies and the phone was not recognized in either DL mode or boot loop. Was hopeful Kies could reinstate the firmware.
I have a physically PERFECT SGS2 I want to sell, and unless I can fix this boot issue, it's nothing but a brick now. Any advice is much appreciated! Pulling my hair out so far...
tone_la said:
I've just spent many hours trying to revive my AT&T I777 phone that was running CM9 until I tried to flash it back to bone stock GB, then ICS.
First, I used ODIN to flash the standard default UCKH7 Gingerbread ROM from Sammy via One-Click "I777_UCKH7_OCD_No_BL.7z". After performing the ODIN, the phone flashed successfully and rebooted into a boot loop "Rethink Possible".
I searched for hours to find a solution, but one solution lead to another problem, and so on...
Currently:
- I cannot get into recovery mode, but it boots reliably into download mode. Tried the 3 button tango in EVERY way, but it will only go into DL mode.
- I've tried many different ODIN flashable images per recommendation in this forum, even the one that contains all of the extra files (recommended by creepyncrawly). All flashed fine, but none fixed the boot loop issue.
- Most recommendations say to "wipe/factory reset" to fix the bootloop issue, but I can't do that since I can't get into recovery.
- Tried to do ADB REBOOT RECOVERY, but can't get the driver to connect and list the device. The install guide says to enter "debug mode", but I can't even boot the phone.
I have a physically PERFECT SGS2 I want to sell, and unless I can fix this boot issue, it's nothing but a brick now. Any advice is much appreciated! Pulling my hair out so far...
Click to expand...
Click to collapse
From powered off, how long are you holding power and vol+ and vol- to get into recovery? On both mine and my wife's phones, I have to hold all three down until the second time the Sammy logo flashes up on the screen. Most people seem to get it after the first time, but I've heard of a few others like mine...
Sent from my SGH-I777 using Tapatalk 2
dandrumheller said:
From powered off, how long are you holding power and vol+ and vol- to get into recovery? On both mine and my wife's phones, I have to hold all three down until the second time the Sammy logo flashes up on the screen. Most people seem to get it after the first time, but I've heard of a few others like mine...
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
When I hold down the 3 buttons, it never actually shows the Sammy logo. It takes about 8-12 seconds and shows the Download prompt that says "press volume up" to continue to enter DL mode; "press volume down" to cancel/restart. Both of these work fine. If I ignore the prompt and continue holding the 3 buttons, it never does anything else. Thanks for your post.
tone_la said:
When I hold down the 3 buttons, it never actually shows the Sammy logo. It takes about 8-12 seconds and shows the Download prompt that says "press volume up" to continue to enter DL mode; "press volume down" to cancel/restart. Both of these work fine. If I ignore the prompt and continue holding the 3 buttons, it never does anything else. Thanks for your post.
Click to expand...
Click to collapse
Unplug the USB when you do that
Sent from my Galaxy Nexus
Stop using brick. It turns on it is not a brick
Sent from my GS4 running CM11 Kandy Kane
Pirateghost said:
Unplug the USB when you do that
Click to expand...
Click to collapse
It does the same thing whether the USB cable is plugged in or not. However, you gave me an idea...
This phone has been sitting in the drawer for a few months since I got my GNex. When I charged it up, after unplugging the charger the icon stayed with a "plug" symbol on the notify bar as if it was still connected to the charger.
Is it possible the phone is stuck thinking there's a cable plugged in and that's why I can't 3-button boot to recovery? Seems like I've read about other people having connector issues. Does this sound plausible? And if so, what's the best remedy?
tone_la said:
It does the same thing whether the USB cable is plugged in or not. However, you gave me an idea...
This phone has been sitting in the drawer for a few months since I got my GNex. When I charged it up, after unplugging the charger the icon stayed with a "plug" symbol on the notify bar as if it was still connected to the charger.
Is it possible the phone is stuck thinking there's a cable plugged in and that's why I can't 3-button boot to recovery? Seems like I've read about other people having connector issues. Does this sound plausible? And if so, what's the best remedy?
Click to expand...
Click to collapse
A simple Google search is the best remedy. This is one of the most asked questions on this forum.
tone_la said:
It does the same thing whether the USB cable is plugged in or not. However, you gave me an idea...
This phone has been sitting in the drawer for a few months since I got my GNex. When I charged it up, after unplugging the charger the icon stayed with a "plug" symbol on the notify bar as if it was still connected to the charger.
Is it possible the phone is stuck thinking there's a cable plugged in and that's why I can't 3-button boot to recovery? Seems like I've read about other people having connector issues. Does this sound plausible? And if so, what's the best remedy?
Click to expand...
Click to collapse
Could be...Sounds like a symptom of bad or dirty usb port. Try cleaning gently with tooth brush and rubbing alcohol. Dry with canned air if you have some.
Sent from my SGH-I777 using Tapatalk 2
Phalanx7621 said:
A simple Google search is the best remedy. This is one of the most asked questions on this forum.
Click to expand...
Click to collapse
I've tried very hard to not "waste" anyone's time by doing my research, searching, and thinking; BEFORE posting. My question above is not so much "how" to clean the port, but "does this symptom I'm experiencing sound like a 'bad port' issue?". Believe me, I've done tons of searching to try to solve this problem before posting so that I can be worthy of receiving assistance.
And to the guy who says, "don't use the term brick". Sorry I said "Apparent brick"; just looking for some neighborly help to get my phone working again. At any rate, I very much appreciate any advice to help me get this fixed.
Trying hard to keep the forum clean and think for myself when possible!
dandrumheller said:
Could be...Sounds like a symptom of bad or dirty usb port. Try cleaning gently with tooth brush and rubbing alcohol. Dry with canned air if you have some.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thanks so much for this post, I will do this and post again with the results. Much appreciated!
tone_la said:
Thanks so much for this post, I will do this and post again with the results. Much appreciated!
Click to expand...
Click to collapse
I should elaborate a little for safety's sake - probably a no brainer, but in case - TAKE YOUR BATTERY OUT BEFORE CLEANING THE PORT. Don't know if it matters or not, but I wouldn't want you to short stuff during cleaning - rubbing alcohol IS part water.
Adb wait-for-device reboot recovery
Plug in your phone and let it attempt to boot. If you need adb, use the link in my signature for adb portable. It includes batch files to reboot to download or recovery modes.
This issues the reboot command if at any point in the boot process your phone is detected.
You might want to install the android sdk and ensure you have the nexus drivers installed.
Sent from my SGH-I777 using xda premium
Red_81 said:
Adb wait-for-device reboot recovery
Plug in your phone and let it attempt to boot. If you need adb, use the link in my signature for adb portable. It includes batch files to reboot to download or recovery modes.
This issues the reboot command if at any point in the boot process your phone is detected.
You might want to install the android sdk and ensure you have the nexus drivers installed.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Well, I cleaned the heck out of the USB port with rubbing alcohol and a toothbrush, followed by a thorough drying with compressed air. Yes, battery removed during the process; thanks for that! Unfortunately, same exact symptom. Only goes into DL mode and boot loop.
I'll now try your portable adb suggestion and see if I can get a connection.
Does anyone else have any thoughts on what may have gone wrong and/or anything I can flash via ODIN to fix the issue? Many thanks!
Installed your portable adb and followed your instructions. Ran the recovery_mode batch file and adb initialized (daemon not running, starting daemon...) followed by red text "Waiting for your device to be detected". I already installed the Android SDK yesterday and the following modules are installed: Android SDK Tools, Android SDK Platform-tools, and Google USB Driver
Powered on the phone and after a few seconds the "Rethink Possible" logo showed up and shortly thereafter, I heard the computer beep indicating it connected with the phone. Win7 device manager shows "SAMSUNG Mobile USB Modem" under the Modems category.
However, the portable ADB continues to show "Waiting for your device to be detected" and the boot loop continues. Did the same thing in DL mode, same result.
I reinstalled the Samsung I777 driver from Samsung's site. Going to reboot my PC now to see if that makes a difference.
Reboot did not help. Seems like the phone is not being identified as "Android Composite ADB Interface", and therefore ADB cannot see the phone. I've looked for other drivers, but no matter what I've tried, the SGS2 I777 shows as "SAMSUNG Mobile USB Modem" under the Modems category in Win7 Device Manger.
Any advice on ADB here? Doing the best I can, but keep running into stops. Thank you
tone_la said:
Reboot did not help. Seems like the phone is not being identified as "Android Composite ADB Interface", and therefore ADB cannot see the phone. I've looked for other drivers, but no matter what I've tried, the SGS2 I777 shows as "SAMSUNG Mobile USB Modem" under the Modems category in Win7 Device Manger.
Any advice on ADB here? Doing the best I can, but keep running into stops. Thank you
Click to expand...
Click to collapse
Try in Linux? Make yourself an ubuntu live CD and go from there? As long as you have the most current drivers, it should work in Win - unless the problem is a totally hosed USB port??
Tried these? http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-II-i777-USB-Driver-for-AT-T.shtml
dandrumheller said:
Try in Linux? Make yourself an ubuntu live CD and go from there? As long as you have the most current drivers, it should work in Win - unless the problem is a totally hosed USB port??
Click to expand...
Click to collapse
Why would it work better in Linux? I'm willing to try this, but fairly unfamiliar with Linux.
Phalanx7621 said:
Tried these? http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-II-i777-USB-Driver-for-AT-T.shtml
Click to expand...
Click to collapse
I used the Samsung drivers. Kinda leary of these drivers from softpedia. They download as SETUP.EXE and seem like inauthentic/spyware.
After many many hours of frustration and dead ends, I've finally recovered my phone! YAYYYYY!!!!!
Here's how I got it done...
- No matter what I flashed, I kept getting the boot loop. This was really throwing me for a "loop" when I thought I was flashing standard original Sammy full ROM with ODIN; yet that wasn't enough to recover the phone.
- Something was missing with the boot process, so I started looking for CWM that I could flash via ODIN. Most sites had the zip CWM file, but only a few had the TAR file. Finding a valid file proved more difficult than I thought with all the download sites that went offline for legal reasons. But I did find one!
http://www.mediafire.com/?bjhx33o4viz8tza
The above link is for file name: SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar
- Once I installed the above via ODIN, all of a sudden ADB recognized the phone and I was able to run: ADB REBOOT RECOVERY
It's very possible that the 3-button recovery may have worked too, but when I saw the device show up on ADB, I didn't want to take the chance.
- The device then rebooted and entered RECOVERY mode! FINALLY!!!!
- I then did a factory reset / wipe and rebooted the phone. It came up just fine, NO MORE BOOT LOOP!
Thanks to those who replied to this thread. The responses helped me think hard about what was going wrong and ultimately I dug up a solution.
Related
Hey Guys, could sure use your help... i updated my 10.1 le yesterday and that went thru fine. Later on i was playing and watching youtube and it sent my tablet into a boot loop and i cant seem to fix it. any help would be appreciated thanks in advance.
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
LovellKid said:
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
Click to expand...
Click to collapse
right now im having problems with adb listing the devices. adb is installed. it keeps saying that i need some APX drivers???
Drivers are here:
http://www.samsung.com/us/support/owners/product/GT-P7510UWYXAR
I had the same problem. This is what i did. Since I had already rooted my tablet, I already had in my laptop ADB and the driver for the tablet. If you don't have these 2 things, I suggest you go to the development section of this forum, look for the insrltructions on how to root, and download what you need.
I connected my tablet then went into cmd mode (DOS MODE), then typed adb reboot recovery. From there the tablet rebooted into recovery. I then wiped data and cache. Then I rebooted and it went fine, no more bootloop. In settings I noticed that it had reverted back to 3.0.1 so I just did update again. Since then my tablet has been smooth as butter.
Sent from my GT-P7510 using XDA Premium App
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
kdietze3 said:
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
Click to expand...
Click to collapse
THANK YOU!! Your suggestion of installing PDAnet saved me! I was having a hell of a time trying to get the right drivers so my computer would recognize the tablet has an adb device. After installing PDAnet, it was a cinch. Then I reflashed everything, wiped userdata and cache, and rebooted (I followed the instructions found here: http://forum.xda-developers.com/showpost.php?p=14600617&postcount=111) Now my tab is working again and I was getting ready to ship it off to Samsung so they could re-flash it for me.
Follow this steps
The steps are this:
http://forum.xda-developers.com/showpost.php?p=15084897&postcount=123
Obviously I have installed adroid-sdk and download fastboot from HTC page.
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
engljeff said:
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
Click to expand...
Click to collapse
Edit:
After trying just about everything, I have concluded there are two hurdles I still cannot pass. First, if I fastboot my device, and select the USB icon, my device is appearing in my windows device list. However, I cannot run any fastboot commands in cmd.exe window. Not sure why or what else is needed. Second, I successfully installed SDK and tried to enter recovery mode through ADB, but I cannot find the magic trick to have my device appear in ADB. ODINing back to stock did not make a difference. If I can get past either of these hurdles I am confident I can progress, so any suggestions are appreciated.
fastboot commands never seem to work for me. Always says waiting for device.
ericc191 said:
fastboot commands never seem to work for me. Always says waiting for device.
Click to expand...
Click to collapse
Which makes me wonder if I am doing something wrong. I can't even get fastbook command to be recognized. It's as if there is some fastboot software needed so that my pc knows what to do when I type fastboot. I hoped SDK was enough, took a stab with a fastboot.exe from htc I found on another forum, neither worked. How did you get your pc to look for your device from fastboot in the first place?
Sent from my SGH-T959 using XDA App
Hi .. I have the same problems before
I found out that the new ADB has moved the directory to "platform-tools"
This renders the fastboot useless "winapiadb.dll"(or something) file not found pop up window
I got that ridiculous bootloop issue right in the middle of the flight! thought I bought a $$$ junk lol
use the fastboot -w option to recover .. but it resets the whole tablet back to OE (original everything)
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Clyde_Frog said:
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Click to expand...
Click to collapse
Ok, well if you are running a "stock" IO bootloader, then you should have fastboot and download modes accessible to you by using the volume down and power button combo.
Have you ever gotten to this menu before? If not, then you just aren't doing it right. Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear. If you have an IO bootloader, then you are going to go into fastboot mode, and then use fastboot to get your recovery booted. Once you get CWM booted, you can flash a stock ROM, load up stock recovery and wipe this sucker back to factory, and then fastboot your CWM recovery and install Task650's latest rom and be bootloop free. Let me know if you need further help.
Alright, first things first. Yes, this tablet is 100% stock, and I've done one major Android update, but it was not the one that broke everyone's wireless.
----------
So going step by step:
you should have fastboot and download modes accessible to you by using the volume down and power button combo. Have you ever gotten to this menu before?
So, I did once get to what I believe was the "fastboot" menu. I had four options available to me, the first one was something like "repair boot process" which I selected, because I was having a boot problem. It did nothing, and now I cannot get back to that menu.
I did get to the USB upload screen once by accident, when I was trying to get back to the boot menu, but not knowing what to do at that point. I had to shut it off.
Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear.
Which Samsung logo? If I press both the power button and volume up or down, I get nothing. Nothing happens. If I press the power button first and then two seconds later start holding down the volume button, then eventually I get the blue swirly samsung screen. At the end of that, the samsung logo is clear. But waiting a bit longer, after about 30 seconds of blank screen, a pulsing white Samsung logo comes up, and I've never known which samsung logo to stop holding the power button. I believe I've tried every combination imaginable, and none of them work.
If you have an IO bootloader Do you mean Google I/O Stock bootloader? If not, I have no idea what this is in reference to.
Once you get CWM booted No idea what that is.
you can flash a stock ROM Where do I get that?
-------------
My bootloop might be different from everyone else's. Everyone else says "shut off the device, and then turn it on with the volume down/up held down. The problem with mine is that it NEVER shuts off! So, I can only do about 2 tests per day, because the only way I can shut it off is to let the battery run dead.
Mine switches from boot loop, and if I force that off, by holding down the power button for 10-15 seconds, then it immediately boots back up into "going into upload mode, cause unknown" If I force that screen off, it boots into the boot loop, so I can never boot from a "powered off" mode, again, unless I let the battery run dead.
I've tried every button pressing boot sequence I can think of with no luck. Can't I just upload something to the device in "upload mode" ? I don't need any data off this device, I just want it to be reset back to day 1, so that I can turn it on and use it.
Thanks so much for your help. As you might imagine, this is a very frustrating problem.
bootloop
can someone please help me ,i have a samsung galaxy tab 2 10.1 ,and its on boot loop ,always showing smsung galaxy tab 2 logo,i've tried restoring factory settings ,,didn't work ,i tried to install receovery from internal sd card says not found ,some one pleeaaase send me the steps of what to do
OK, here the story. My SGS2 started acting up a few days ago, it thinks it's charging all the time now. I searched and found that this seems to be a common problem with the port, so I cleaned the contacts on the microUSB connector, but it's not helping. I decided today that I'll just take it in since it's still under warranty, and I'd like to do it after work today since I live almost an hour away from the AT&T Store near the hospital. Problem was, I'm running AOKP on it and I don't have access to a computer with Odin on it where I can restore it to stock. Then I find the thread that details how I can download the .tar file and flash on the phone with Mobile Odin. Seems to work great, but it goes into a bootloop afterwards. One member posted that he had the same problem, but it was solved by booting into recovery and doing a full wipe. Here's where I have a problem now.
I can only boot into Odin mode, and it gives me the choice where it's asking me if I'm sure I want to load a custom binary or cancel and reboot. When I click that I want to load the binary, I get to the Odin mode screen; it reads
Custom Binary Download: No
Current Binary: Samsung Official
Downloading...
Do not turn off target!!
That's it. If I reboot normal, it goes into bootloop. Otherwise, it sits there with the battery logo showing, whether it's plugged in or not.
I'm pretty sure when I get home tonight, I can plug it in and get something going on my desktop, but I'd like to hit up the store before I head home. Anyone got any ideas or suggestions?
If you can't boot into recovery using the three button method, I'm not aware of any way to put it into recovery mode without a computer. You didn't say, but I assume you used vol+, vol-, & pwr?
creepyncrawly said:
If you can't boot into recovery using the three button method, I'm not aware of any way to put it into recovery mode without a computer. You didn't say, but I assume you used vol+, vol-, & pwr?
Click to expand...
Click to collapse
Yup, and that's what comes up. I'm thinking it has something to do with the fact that the phone thinks it's plugged in. I guess I'll just have to plug it in my desktop when I get home and work on it from there. Worst case scenario is that I just take it to AT&T tomorrow as it is, tell them about the false charging problem, and when I tried to do factory reset to see if it would fix things, this is where it's stuck.
I can't believe I spent the first 30 years of my life without a cell phone and now I don't feel right if it won't work for a day or two.
creepyncrawly said:
If you can't boot into recovery using the three button method, I'm not aware of any way to put it into recovery mode without a computer. You didn't say, but I assume you used vol+, vol-, & pwr?
Click to expand...
Click to collapse
I'm having the same problem after trying to install S-Voice. You indicate that there is a way to get into recover using a computer. Can you explain?
Thanks.
drjim said:
I'm having the same problem after trying to install S-Voice. You indicate that there is a way to get into recover using a computer. Can you explain?
Thanks.
Click to expand...
Click to collapse
need adb.
adb reboot recovery
Google
Update:
I actually managed to catch it when it didn't think it was plugged in and do full wipe. It worked after that, sorta. It didn't think it was plugged in all the time, but it was still real funky; like the power usage curve started high, had a sudden big drop, then went up from there. Plus, when it was off, it would flash between a grey battery with a circle and a green on, back and forth. And I couldn't power it on unless it was plugged in. Once I showed them that, AT&T gave me a new SGS2. It's rocking Shostock2 now, so problem solved.
Verizon SGS3. This is my first Samsung, so I have no doubt that it was something I did - been running my OG Droid since it came out and I'm not very familiar with the Samsung setup.
I followed this thread
http://forum.xda-developers.com/showthread.php?t=1762204
The forum won't let me post my question there, due to my low post count, so I put it here...
I used Odin to flash the image in the PDA field. Right after that, without checking to see if the phone was working properly, I used ADB to put CWM on there. The phone was turned on (not in Odin mode) when I pushed the recovery. Now I can't get the phone to turn even turn on, much less get into Odin mode to reflash....(yes, I've pulled the battery).
My computer recognizes when I plug my phone in (it give the "you plugged something in" tone), but it doesn't register in Windows explorer.
Any ideas...?
Not sure if this will be any help but..
I was flashing the same rom as you and my computer randomly blue screened in the middle of it and my phone wouldn't boot. I tried just flashing it again with odin right over it, but same problem.
I had to do a factory reset, flash the Samsung stock rom (which unrooted), I think I did another factory reset, and finally re flashed the root 66 rom. I also booted up the phone and did the initial setup before pushing recovery over with adb, but I'm not sure if that makes a difference.
Good Luck!
I can't even get into Odin, though. Nothing happens when I try to power on....so no getting into Odin or Recovery....very frustrating.
letinsh said:
I can't even get into Odin, though. Nothing happens when I try to power on....so no getting into Odin or Recovery....very frustrating.
Click to expand...
Click to collapse
Was your battery full/plenty of charge when you first flashed through ODIN? What happens when you try to turn it on? No luck with download mode? Are you getting any feedback whatsoever from holding the power button?
Which recovery did you download and flash? I ask because I did this same thing last night and had the same issue. I used the touch recovery (TWRP 2.2.0) from HERE but the direct download link is bad. It gets you the wrong recovery if you download it directly to push via ADB or terminal. You need this one HERE
I hope im wrong but it sounds like a brick. If you can get into download mode your fine.
Battery was 100% (charged it overnight).
Nothing happens when I try to power it on....no lights, no vibration, no noise. Screen doesn't come on, no backlight...nothing.
No feedback whatsoever.
That's interesting. I pulled the battery and plugged in my USB to computer (I'm at work and don't have a regular charger) and the red "charging" LED just came on, but still unresponsive to any button push.
letinsh said:
Battery was 100% (charged it overnight).
Nothing happens when I try to power it on....no lights, no vibration, no noise. Screen doesn't come on, no backlight...nothing.
No feedback whatsoever.
That's interesting. I pulled the battery and plugged in my USB to computer (I'm at work and don't have a regular charger) and the red "charging" LED just came on, but still unresponsive to any button push.
Click to expand...
Click to collapse
Have you battery pulled already besides just now? If you pull the battery hold the power button after you pull for a few seconds, put it back in and then try to power on.
adb doesn't see the device, even though windows registers something as plugged in (tone thru speakers when plugged/unplugged)
mustbepbs said:
Have you battery pulled already besides just now? If you pull the battery hold the power button after you pull for a few seconds, put it back in and then try to power on.
Click to expand...
Click to collapse
Tried this just now. No joy.
....can a mod please verify my account so I can post more often than every 5 minutes...it's very frustrating.
bump
letinsh said:
bump
Click to expand...
Click to collapse
That's really odd that you're getting no life out of it after pushing CWM. What version did you push? When did you push it? You did it via the command prompt or on the actual device?
mustbepbs said:
That's really odd that you're getting no life out of it after pushing CWM. What version did you push? When did you push it? You did it via the command prompt or on the actual device?
Click to expand...
Click to collapse
I worked off of this thread:
http://forum.xda-developers.com/showthread.php?t=1756885
and followed it's directions to a "t"
letinsh said:
I worked off of this thread:
http://forum.xda-developers.com/showthread.php?t=1756885
and followed it's directions to a "t"
Click to expand...
Click to collapse
Sorry, that's not entirely true. I followed those instructions but used the root66 image from this thread
http://forum.xda-developers.com/showthread.php?t=1762204
The CWM file i used was from the [ROOT] [RECOVERY] SCH-i535 thread
After some searching, this same sort of brick seems to be happening when dudes are flashing roms coded for other carriers....but I've got an i535 and have only used i535 files....hmm.
Shot in the dark
This is really just a shot in the dark, but have you tried power,home and volume button?
-SmithTech- said:
This is really just a shot in the dark, but have you tried power,home and volume button?
Click to expand...
Click to collapse
Yes, both vol up and vol down. I've tried every iteration I can think of. I'm waiting to hear back from Josh @ MobileTechVideos to get me an address. I'll be driving out there to have him give it a crack at unbricking...
i am not sure about fixing it, but a good rule of thumb is verify your MD5 on your files always!
I downloaded the same root66 because it was a torrent verifed md5 before I even attempted flashing it.
nosympathy said:
i am not sure about fixing it, but a good rule of thumb is verify your MD5 on your files always!
I downloaded the same root66 because it was a torrent verifed md5 before I even attempted flashing it.
Click to expand...
Click to collapse
+1. Always make sure to verify MD5's before flashing anything, especially in our case. Hopefully you can get that fixed, OP. That's really bizarre.
Possible Fix
Curious.... when you you type ./adb devices does it list any devices there? (Windows its just adb device)
I have seen this happen on Samsung Vibrants and it sounds like your device has forgotten what the hardware keys actually do. If adb works, you can reboot to download it it doesn't a resistor can be built with a Micro usb end to trick the device into download mode. Some were made for the Vibrants and should be able to find them on the forums over there. I believe Team Whiskey built them
I just recently downloaded SlimBean 3.1 and was trying to upgrade to that from 3.0. So I did my usual procedure: wipe, clear cache, format /system. Then I proceeded to installing Slimbean 3.1, then the kernel (Semaphore_JB_2.6.5sv) and finally the gapps for SlimBean. But the boot animation was taking too long (>10 minutes), when it usually doesn't when I install a SlimBean ROM, so I pulled the battery and repeated the process. Now I realized that once in a while (about 10 seconds) it would give a small vibration and on occasion when I retried to install, it would give me a 'Whoop' sound (when that happens, it's about every ~5 minutes). Anyone know what the problem is so I can fix it? Thanks!
Did you try getting it to boot, then go back and flash kernel?
I've felt the vibrations but never any sound. Don't know why that would happen.
I am Jack's smirking revenge.
samsgun357 said:
Did you try getting it to boot, then go back and flash kernel?
I've felt the vibrations but never any sound. Don't know why that would happen.
I am Jack's smirking revenge.
Click to expand...
Click to collapse
Yeah I've tried getting it to boot many times.. I just tried flashing the Semaphore kernel over the ROM in CWM, no good. Still stuck at the SlimBean boot animation as always and there's still the vibrations every 10 or so seconds.
I'm trying to use Heimdall for the first time now to see if it can help solve my problem. I've just done the zadig thing, but now I'm not quite sure how to proceed, I don't know what to put in the Heimdall Firmware Package.
EDIT: S**t, I tried flashing a kernel via Heimdall, failed for some reason, and now it's bricked with the 'phone ! pc' icon, can't get into download mode with 3 button combo. I just keeps going back to the 'phone ! pc' icon, I think it might be hard bricked. Odin isn't reading my device. No luck with one click unbrick either...This is not my day..
Pull battery, connect USB then hold button combo while popping battery back in. (With Odin on obviously)
I am Jack's smirking revenge.
samsgun357 said:
Pull battery, connect USB then hold button combo while popping battery back in. (With Odin on obviously)
I am Jack's smirking revenge.
Click to expand...
Click to collapse
Thanks for the reply. I tried doing that, still a no-go. Popped battery out, removed sd card/sim, put usb in, held vol. up and down keys, popped battery in. It keeps going back to the 'phone ! pc' screen and Odin's still not reading my device. I really am afraid that this might be a hard brick rather than a soft brick..
You aren't hard bricked, if you were you'd see nothing. The goal now is to try and get DL mode.
Have you tried to run Odin even though it doesn't give com port? Don't know if that will work but try it.
Try only vol up or only vol down and see if that works.
I am Jack's smirking revenge.
^ what he said. Try the up button only after you plug in the USB.
Sent from my Galaxy Nexus using Tapatalk 2
tylerxian said:
Thanks for the reply. I tried doing that, still a no-go. Popped battery out, removed sd card/sim, put usb in, held vol. up and down keys, popped battery in. It keeps going back to the 'phone ! pc' screen and Odin's still not reading my device. I really am afraid that this might be a hard brick rather than a soft brick..
Click to expand...
Click to collapse
I had better success with this one - Pull out battery, wait 10 sec, reinsert. Connect USB to PC port. While holding vol up & down, connect USB to the phone.
Are you on Froyo or GB bootloader?
samsgun357 said:
You aren't hard bricked, if you were you'd see nothing. The goal now is to try and get DL mode.
Have you tried to run Odin even though it doesn't give com port? Don't know if that will work but try it.
Try only vol up or only vol down and see if that works.
I am Jack's smirking revenge.
Click to expand...
Click to collapse
I sure hope so.. I've tried inserted the stock eclair PDA in Odin, along with the s1_odin_20100512.pit file, clicked start and was presented with "<OSM> All threads completed. (succeed 0 / failed 0)". I think one of the reasons why Odin isn't recognizing my Vibrant is because of the drivers (even before the brick). I'm always presented with "The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." The drivers I downloaded were the latest from Samsung's site.
I tried both, still went into the 'phone ! pc' screen. Also tried using USBDeview to uninstall the Samsung drivers, and then, as always, when I plug in the Vibrant, it gives me the message mentioned above where Windows doesn't recognize the device. It'll install some Unknown Device's drivers, which don't work. I thought it might have been the zadig thing I did for Heimdall, but I guess not.
ioancr said:
I had better success with this one - Pull out battery, wait 10 sec, reinsert. Connect USB to PC port. While holding vol up & down, connect USB to the phone.
Are you on Froyo or GB bootloader?
Click to expand...
Click to collapse
Just tried, still went into the 'phone ! pc' screen. I believe I'm on the GB bootloader, it's been a while since I flashed a bootloader so I'm not quite sure, but since I managed to install SlimBean 3.0 before(required the GB bootloader), I'm assuming it's that.
tylerxian said:
I tried both, still went into the 'phone ! pc' screen...
Just tried, still went into the 'phone ! pc' screen. I believe I'm on the GB bootloader, it's been a while since I flashed a bootloader so I'm not quite sure, but since I managed to install SlimBean 3.0 before(required the GB bootloader), I'm assuming it's that.
Click to expand...
Click to collapse
Then you changed also the way you get to download mode. Instead of pressing both vol up & down, use ONE only, the volume up button. Don't give up, you will have to retry many times to get there, your phone is still OK.
Have you tried the Heimdall One-Click package? It was the only one that saved me many times (and long time ago, fortunately).
ioancr said:
Then you changed also the way you get to download mode. Instead of pressing both vol up & down, use ONE only, the volume up button. Don't give up, you will have to retry many times to get there, your phone is still OK.
Have you tried the Heimdall One-Click package? It was the only one that saved me many times (and long time ago, fortunately).
Click to expand...
Click to collapse
I couldn't get only vol. up or down to work. I have the one-click packager downloaded, but I don't know what to do with it. From the start it says 'Select a Heimdall tar.gz for one-click".
Heimdall One-Click has everything built-in, it doesn't ask anything. Go get it here, the official thread http://forum.xda-developers.com/showthread.php?t=1278683
Make sure it shows "package designed for SGH-t959" when open.
ioancr said:
Heimdall One-Click has everything built-in, it doesn't ask anything. Go get it here, the official thread http://forum.xda-developers.com/showthread.php?t=1278683
Make sure it shows "package designed for SGH-t959" when open.
Click to expand...
Click to collapse
That was the same thread I got mine, however the download links didn't work anymore in the OP's post. So I got mine here: http://forum.xda-developers.com/showthread.php?t=1278683&page=6, first post of the sixth page.
tylerxian said:
That was the same thread I got mine, however the download links didn't work anymore in the OP's post. So I got mine here: http://forum.xda-developers.com/showthread.php?t=1278683&page=6, first post of the sixth page.
Click to expand...
Click to collapse
It's not the one I have. It should be 280 Mb at least. I'll try to upload it somewhere, now I'm busy, sorry.
ioancr said:
It's not the one I have. It should be 280 Mb at least. I'll try to upload it somewhere, now I'm busy, sorry.
Click to expand...
Click to collapse
Thanks, I'd really appreciate it if you did. Hopefully before Tuesday, if I can't get anything to work in getting the Vibrant to boot to download mode, I might just have to ship it over to mobiletechvideos or something to install the unbrickable mod. That's also when I get my usb jig, so if that doesn't work either I'll send it in.
Try this link
It's 198 Mb jar file.
ioancr said:
Try this link
It's 198 Mb jar file.
Click to expand...
Click to collapse
Thank you! Though, it's not recognizing the phone, still shows disconnected. Then again, it might be a problem with my computer drivers not seeing my device/installing incorrect drivers (i.e 'Unknown device' and 'Port Failed'. This will definitely prove useful if I do get it to go to download mode or for future problems, if I manage to get it fixed.
tylerxian said:
Thank you! Though, it's not recognizing the phone, still shows disconnected. Then again, it might be a problem with my computer drivers not seeing my device/installing incorrect drivers (i.e 'Unknown device' and 'Port Failed'. This will definitely prove useful if I do get it to go to download mode or for future problems, if I manage to get it fixed.
Click to expand...
Click to collapse
Try to uninstall the current USB drivers, reboot PC and then use Zadig from Heimdall suite (1.3 or 1.3.1) to install them. It perhaps will not recognize it as a phone, don't bother, it's enough to make it just visible to PC (check search all devices or something like that in preferences of Zadig).
ioancr said:
Try to uninstall the current USB drivers, reboot PC and then use Zadig from Heimdall suite (1.3 or 1.3.1) to install them. It perhaps will not recognize it as a phone, don't bother, it's enough to make it just visible to PC (check search all devices or something like that in preferences of Zadig).
Click to expand...
Click to collapse
I uninstalled all the drivers related to the Vibrant using USBDeview, like the blank unnamed driver and the 'Port reset' one, then rebooted. But it's still not visible as a device. I'll post a screenshot of this.
Here's what usually happens. If you take a look at the last line in USBDeview, that's usually what the Vibrant comes out to be, just a blank line with no description.
Hello, I have searched through the forum and it appears that my Note 2 has SDS.
But I just hoping someone would be kind enough to help verify my assumation. My
phone will not boot pass the samsung screen and it will not boot into recovery.
But the phone will boot into download mode and this is the info that appears
on the screen:
Odin Mode
Product Name:
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
But with the phone in download mode and connected to my computer, the coumputer
and Odin is no longer recognizing that my phone is plugged in.
My phone was running CM10.1 with TWRP recovery.
Any and all help will be greatly appreciated
Well there are a few things that could be going on. The first, you may need to manually go into your device manager on your computer and remove all Samsung drivers I know it sounds crazy but it works, getting rid of that "unknown device id" you get when you connect your phone to the computer. Now there are some hidden drivers that you have to enter a command only once to be able to see, I'll try to get a link posted to a guide on how to do it.
With your phone in download mode plug it back to your computer now make sure that your computer is disconnected from the Internet because windows will ignore the driver you want and just grabs one. But you will have to download the usb driver you need to your computer first so after the deletion of all other Samsung drivers it will be the only one windows can install. I will see if I can get you all the links for the computer command and for the driver.exe. /This is the guide to remove your old drivers.
http://www.petri.co.il/removing-old-drivers-from-vista-and-windows7.htm Here is the driver link, and I hope this helps you out. http://teamuscellular.com/Forum/topic/3619-if-you-are-having-the-hardware-id-missing-error/#
M.A.D.NoTe.||
Thank you so much for the reply. I did as you instructed and removed all
of the previous installs/verisons of the Samsung drivers, downloaded the
new verison of drivers, unplugged my pc's network cable to disable the
internet and installed the new drivers. But as I was doing this, I realized
that I didnt explain my problem well enough. My apologies. The problem
is that when I connect my phone to my pc, the pc acts as if nothing has
been plugged into the usb port. By the way I did complete your instructions
in hopes that it would still correct my problem but unfortunately no luck. I
even tried using my notebook pc that I havent ever used with the phone
and installed the Samsung drivers but both the desktop and notebook
act as if nothing is being plugged into the usb port. Hope this makes
sense.
Again, thank you every much for you help and any other suggestions
will be greatly appreciated.
Have you tried a different version of odin? I actually use the gs3 version for my note2 and it works perfect. Can you get into recovery at all? And are you familiar with running adb commands from your computer? Also try a different usb cable and then try different usb ports on your computer. Its very odd that odin won't see it while in download mode¿
M.A.D.NoTe.||
The only two verisons of Odin that I have use are Odin3 v3.07 SGSIII and Odin3 v1.85.
With the phone plugged into the usb port, anything I try in both versions of Odin returns:
"<OSM> All threads completed. (succeed 0 / failed 0)"
When I try to boot into recovery, by "Vol up, Home, Power" the phone goes to the
Samsung Galaxy Note II screen. if I continue to hold "Vol up, Home, Power" the
phone will go to the Same Samsung screen for about 2 seconds, then goes blank
for a second, then back to the same Samsug Galaxy Note II screen and will
continue this cycle as long as I hold the buttons.
Yes, I have very basic knowledge of adb commands but only in regards to pulling
and pushing some files to my other android devices.
One other bit of infomation I just noticed about the phone is that, with the phone
being powered off and then plugging the phone to charge, the battery icon appears
but its gray, no power % or anything. I do have a second Note2 and if I swap
batteries, both batteries are around 80% charged. Not sure if this litttle bit of info
is helpful.
Again thank you so much and I truly appreciate your help.
I finally gave up and used an available upgrade to get a new phone which works on all fronts. Now if I could just solve this bricked phone, maybe I could sell it...or blow it up.
Oh_wow said:
I finally gave up and used an available upgrade to get a new phone which works on all fronts. Now if I could just solve this bricked phone, maybe I could sell it...or blow it up.
Click to expand...
Click to collapse
Well is it a note 2 or what kind? Thats bricked? If you want to get rid of it pm me and we'll talk.
M.A.D.NoTe.||
Droidjava said:
The only two verisons of Odin that I have use are Odin3 v3.07 SGSIII and Odin3 v1.85.
With the phone plugged into the usb port, anything I try in both versions of Odin returns:
"<OSM> All threads completed. (succeed 0 / failed 0)"
When I try to boot into recovery, by "Vol up, Home, Power" the phone goes to the
Samsung Galaxy Note II screen. if I continue to hold "Vol up, Home, Power" the
phone will go to the Same Samsung screen for about 2 seconds, then goes blank
for a second, then back to the same Samsug Galaxy Note II screen and will
continue this cycle as long as I hold the buttons.
Yes, I have very basic knowledge of adb commands but only in regards to pulling
and pushing some files to my other android devices.
One other bit of infomation I just noticed about the phone is that, with the phone
being powered off and then plugging the phone to charge, the battery icon appears
but its gray, no power % or anything. I do have a second Note2 and if I swap
batteries, both batteries are around 80% charged. Not sure if this litttle bit of info
is helpful.
Again thank you so much and I truly appreciate your help.
Click to expand...
Click to collapse
I'm having this same exact issue as you. Can't find a fix at all. Will probably have to head into Verizon and grab a new phone. :crying:
When you are booting this particular phone into recovery you know the right way BUT just as you see the first Logo take your finger off the power button while still holding volume up and home and see if that will work.
Also on a side note if you have a micro sd adapter then you might be able to get a recovery image on it from your computer and put it back into the phone and try to push it in with fastboot, you say you were running cm10. what, (if none of the above works), were you doing at the time of this problem? Flashing, turning on, or what?
You may want to check this out too if you haven't done so already.
http://galaxynote2root.com/
M.A.D.NoTe.||
mad96 said:
When you are booting this particular phone into recovery you know the right way BUT just as you see the first Logo take your finger off the power button while still holding volume up and home and see if that will work.
Also on a side note if you have a micro sd adapter then you might be able to get a recovery image on it from your computer and put it back into the phone and try to push it in with fastboot, you say you were running cm10. what, (if none of the above works), were you doing at the time of this problem? Flashing, turning on, or what?
You may want to check this out too if you haven't done so already.
M.A.D.NoTe.||
Click to expand...
Click to collapse
I actually got it fixed, problem I was having was even though Samsung Drivers were installed on my desktop, Odin still would not recognize(phone would make the connection noise on my PC and show "Serial Android"). So first thing this morning as I came into work, installed drivers and phone was detected by Odin. Flashed .PIT/PDA files and got it working again. :good:
Cool man good deal!
You may want to post a Fix solution for the problem you were having in case others don't know what to do and panic and send their device in on a insurance claim. Kudos
M.A.D.NoTe.||
mad96 said:
Well is it a note 2 or what kind? Thats bricked? If you want to get rid of it pm me and we'll talk.
M.A.D.NoTe.||
Click to expand...
Click to collapse
It's another VZW Note 2 and I'm still going to try for a solution. When that gets old, I'll definitely pm..
The problem with the phone occurred sometime between plugging it in to charge Sunday
night and Monday morning. The phone appeared to be fine that night but when I woke up
and looked at the phone, it was at the Samsung Galaxy Note 2 screen. The phone is
plugged into a surge protector/battery backup. The one my pc is plugged into. So I don't
believe it was a power surge but who know.
I believe I'm coming to the conclusion that either the phone's usb/power port or the phone
itself is defective. No matter what I try, none of the computer will even act as if anything is
plugged into the pc's usb port. All adb commands pretty much return a <waiting for device>.
I tried to boot into recovery the different way you suggested but unfortunately no luck. The
phone just gets to the Samsung screen and stops. I think the biggest issue is that the
computers act as if nothing is plugged into the usb ports. This prevents Odin or adb commands
from working. Which eliminates all options that I have tried. I have tried different usb cables
and other phones with the different usb cable and they all seem to work correctly.
At this point, I think tomorrow, I'm going to have to look into getting some kind of replacement
phone if I can't get something to at least see that the phone is actually plugged into the usb port.
I want thank you Mad96 for giving me all the help, suggestions and options. If you do have
anymore that you think might work, I would greatly appreciate them but for the life of me, I
can't figure out why all of the computers act like the phone isn't plugged into the usb ports.
I'll see if I can get some other info from friends of mine, new ideas if so I will gladly let you know.
M.A.D.NoTe.||
Droidjava said:
The problem with the phone occurred sometime between plugging it in to charge Sunday
night and Monday morning. The phone appeared to be fine that night but when I woke up
and looked at the phone, it was at the Samsung Galaxy Note 2 screen. The phone is
plugged into a surge protector/battery backup. The one my pc is plugged into. So I don't
believe it was a power surge but who know.
I believe I'm coming to the conclusion that either the phone's usb/power port or the phone
itself is defective. No matter what I try, none of the computer will even act as if anything is
plugged into the pc's usb port. All adb commands pretty much return a <waiting for device>.
I tried to boot into recovery the different way you suggested but unfortunately no luck. The
phone just gets to the Samsung screen and stops. I think the biggest issue is that the
computers act as if nothing is plugged into the usb ports. This prevents Odin or adb commands
from working. Which eliminates all options that I have tried. I have tried different usb cables
and other phones with the different usb cable and they all seem to work correctly.
At this point, I think tomorrow, I'm going to have to look into getting some kind of replacement
phone if I can't get something to at least see that the phone is actually plugged into the usb port.
I want thank you Mad96 for giving me all the help, suggestions and options. If you do have
anymore that you think might work, I would greatly appreciate them but for the life of me, I
can't figure out why all of the computers act like the phone isn't plugged into the usb ports.
Click to expand...
Click to collapse
Sorry if youve already answered this, have you tried a second PC to see if it can detect it? Sounds similar to my issue.
1.Tried unlocking bootloader using Casual.
1a. Casual fails on recovery and doesnt reboot.
2. Battery pull, samsung bootloop every second or so.
2a. Plug device into second computer, will install driver automatically (takes a few min)
2b. Access device with odin off external HDD
2c. Flash PIT/PDA Restore files and reboot.
Should solve the issue of logo reboot. Basically factory Reset is what your doing. You'll be on stock unrooted device.
Yes, unfortunately I have tried multiple pc's with windows, linux and
even a Mac. I have a Droid Razr Maxx that I wasn't using so I'll just
use it until I decide if I'm going to use the insurance or if I'll just
wait and buy one of the new phones I've been considering.
Again, I want to thank you for all of your help but I'm going to put
the Note2 up for now.
The problem exists with Windows XP, as the latest updates from Samsung have changed the drivers and are not supported on XP anymore in order to do it.
Interesting I have a VZW Note 2 that won't even allow me to put it into Download Mode so that I can Odin to it.
Any clues?
HI! I have the same issue with my wife's N7105 (stock fw) - it happened after leaving it charging overnight with only 5% battery left. Only difference is that I can no longer get into the stock recovery. The screen only shows white lines when I try to fire it up normally or try to enter stock recovery. However screen is fine when I go into download mode.
When I tried to flash the fw, it says no PIT partition found. Everytime I try to flash the PIT via odin, it always fails. I tried 4 different versions of odin, tried it on winxp and win7, and basically tried the steps listed in this thread.
You think this is already a hopeless case?
jolex_sp said:
HI! I have the same issue with my wife's N7105 (stock fw) - it happened after leaving it charging overnight with only 5% battery left. Only difference is that I can no longer get into the stock recovery. The screen only shows white lines when I try to fire it up normally or try to enter stock recovery. However screen is fine when I go into download mode.
When I tried to flash the fw, it says no PIT partition found. Everytime I try to flash the PIT via odin, it always fails. I tried 4 different versions of odin, tried it on winxp and win7, and basically tried the steps listed in this thread.
You think this is already a hopeless case?
Click to expand...
Click to collapse
Flash the PIT with a rom, like Root66 or the Alternative Restore rom in droidstyles thread, and see if that helps.
You have tried different USB cords correct?
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
Flash the PIT with a rom, like Root66 or the Alternative Restore rom in droidstyles thread, and see if that helps.
You have tried different USB cords correct?
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah, I already tried different usb cords.. Regarding droidstykle's thread, I noticed that it's for the VZW SCH-I605 variant.. will it work for the international N7105 variant? or did I miss another thread for the N7105?