I just got my Captivate last Friday. Hadn't done anything complicated with it, basically I just used "Unleash the Beast" to root and sideload the thing. Ended up with some sort of weird permissions issue going on with the SuperUser app that had been installed with it, I was getting permission request loops. So I used Odin to reset it. At this point there wasn't anything really wrong, USB worked and the device appeared to the computer. So I just rebooted the Captivate into download mode using adb reboot download and went on.
So later on I grabbed SuperUser 2.3.4(?) or whatever the latest one I found online was, loaded that to do adb pull /system/apps since I realized that Unleash the Beast just deleted everything and I honestly hadn't even seen what it removed yet on the phone itself besides the list on the web site. So after the backup I odin'd again and then grabbed the files from SuperUser 2.3.4 replaced the existing files in Unleash the Beast with it. Actually ended up working perfectly for a while.
I'd used the phone for a few days, no issues, finally got my 16GB SD card from my Raphael and inserted it, had been downloading apps left and right. Well all of a sudden the phone seemed to have it's USB stop working for anything but charging. I recall plugging it into a charger or computer when I first got it and it would ask if I wanted to mount the SD cards for use, then I would just see the battery indicator charging. and I'd toggled developer usb a half billion times trying to get access and fix it.
The computer didn't see it, device manager didn't even flinch(Win7 x64) like it normally does when you plug in and unplug a USB device. Tried it with another computer and same issue. So I rebooted into recovery mode and tried that, the first several times around nothing was detected. Well my finger slipped and ended up hitting the Clear user data and cache option in the recovery mode.
At this point when it boots up, i still dont have usb access, I'm stuck in a force close loop, I can't install apps, can't seem to get it to reboot into download mode via the key commands, and installing apps is impossible since browser and market crash on start.
I've spent the night rebooting and trying to get into download mode for odin, I used to be able to get into recovery mode everytime I tried, eventually I started to see an "uknown device" show up in device manager, which I googled some info from it and all I could tell was it was Microsoft's dummy driver for devices that couldn't be found. Another weird response, it seems to be beginning to hang on the charging battery thing from time to time now.
At this point, its been under a week and I'd trade it in. Except the thing is with enough struggling you can see the apps installed. Most of them were removed but Market Access and Superuser are still in the apps list, and I'm worried about AT&T spotting that, figuring out what I've done and rejecting the claim.
just under half the time now, it boots, the other over-half of the time I get the spinning "battery loading" icon that shows up before the battery thing gets loaded, but not spinning. It pops up, and disappears, from time to time goes to show me my battery status instead of booting, even when not plugged in.
I'd like to think I haven't tried everything? quite obviously i can't run update.zip files from my 16gb sd card since it gets mounted at /sdcard/sd, and I've lost the file browser to move anything around. I've tried rewiping but that doesn't do a thing.
I hadn't gotten to the rom manager stuff yet since I wasn't planning on playing with roms if at all. and at this point that doesn't appear to be an option anymore.
Any suggestions? I was getting to continuing to reboot it till the battery thing comes up 100% of the time then goto ATT and see what they say.
So long that you can get to download mode you SHOULD be good. When you plug in the usb..you need to pull the home dropdown..select usb and tell it to mount. I may be telling you what you already know but download mode is hold both volume buttons from the battery screen...one black screen...att screen...black screen and release pwer but hold buttons. I had problems with this so what I did was unplug the usb...volume buttons...hold power and see att boot screen...(plug in usb)...black screen...att boot...black screen and release power til u see download mode. You can use Odin and set back to stock from there normally.
If the PC is showing unknown device..you are kind of stuck til you fix the driver issue. Maybe remove and reinstall or something not sure on that but that's the first order of business. Go to the dev forum and try reinstalling from there. (One click Odin downloader has teh drivers)
If your phone boots or can get into recovery or download mode you are ok. I ran into the problem where I couldnt even power it on.
Well by now I know that download mode is the holy grail to get things fixed. Recovery mode, I used to be able to get to, but didn't show up. I'm wandering if somehow my USB port got shorted or something.
The drop down option to make it mount is why this all began, it disappeared and never came back.
Trying your steps specifically, first couple times would just end up back at the battery screen. I eventually ended up at recovery mode. Did I end up at recovery mode for releaseing early or late?
I've reinstalled the Captivate drivers a couple times now and tried clearing all past installs of it. Still unknown device. At the moment I have it in recovery mode, so I've rebooted my tower into Ubuntu(Which has the sdk, but never tested with it). Since I've kept reading that Linux doesn't need drivers. Well ./adb start-server and ./adb devices still show nothing...
I can grab a fresh computer that never connected to this thing to try, but I'm kinda doubting it will do this trick at this point. I'll download the odin w/ drivers on it and try that.
hmm.... just ran over to one of the computers here that had absolutely nothing to do with android on it, no drivers, no sdk, no software, nothing.
Went to
[STOCK ROM] Odin3 One-Click Downloader and Drivers(new user=no links)
Downloaded the Windows X64 drivers, installed and rebooted
Plugged the phone in after it rebooted and I'm getting
Unkown Device, I'd pull some info from the Device Manager, but all it is reporting is scewed due to it being a usb device and Windows installed dummy drivers.
All I've got left for testing is my brother's Win7 x32 laptop, granted all I've been able to try with here has been x64 so far. Also on the first computer I was doing all this with. The drivers DID work, they WERE installed and functioning. Previously I could ADB to my hearts desire and I've used odin before. I used the same USB port, used different USB ports, tried different cables.
I had some strange issues on mine. When I would try to go to download mode. All of my USB stuff (KB and mouse) froze up and I had to plug in via PS2. I had the unknown device issue and Not sure how I fixed it. I downloaded and installed the Samsung Kies program and I also downloaded the driver. Ultimatly after banging on it for a bit it worked..not a Unknown device but it was some king of...Gadget Driver or some stuff was messing with me. Try installing Kies and see if that does anything...also make sure you remove the drivers before installing. It acted really squirrly to me too tho. From what you say..it sounds like a borked driver. Im on 32bit XP and took it home to my 64 Vista and got it working whne the 32 was jacking me around.
Just had a chance to try with Kies real quick, I'm not so much thinking i killed my drivers but that somehow the cell phone changed it's id calls. I'm going to give it a shot with kies on a fresh Vista x32 system at work. I still can't seem to get it into downloader mode, but I'm getting more consistent with Recovery and getting the thing to boot back up. If I consider the Battery screens to be your blank screens then I can get it to go recovery or "normal" boot. But still can't seem to get download mode at all.
Up until recently, I didn't get Unkown device showing up even when the system was in "normal" boot. Before, originally it would only show up in device manager in recovery mode, and then it would be the unkown device.
Just out of curiosity could you spare the driver specs for your setup so I can compare? Like Date, Version, and any Hardware IDs? I'm wandering what hardware IDs this thing is giving off since windows wont show me.
Well not sure what suddenly happened. But after enough reboot--attempts, recovery mode is finalyl appearing on my office computer as SAMSUNG Android USB Composite Device. Win Vista x32, only installed Kies and download SDK(speaking of, adb still doesn't see devices). Just finished redownloading odin(wish i'd had a thumbdrive on me when i was at home) and am about to see if I'm going to be lucky by vista somehow.
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
jonscapri said:
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Well that thought has occured, that and magnets lol
I think i might have found a clue to the cause. I think it was tied to the whole usb thing. When it appeared to show up at all first time around, i had tapped the menu button while in recovery. And the natural way I'd been holding it applied just a little pressure on the usb cable. Well I got the phone to finally show all the notifaction tab options for debug and storage when i held down the usb plug in the phone down a little bit. I'm guessing that the pins for power are fine but maybe the data pins, or maybe one of the data pins is loose and thus it's an unkown device since it's not responding correctly.
I didn't have time to finish trying to fix it at work, and i'm stuck in class now. I'm'a see if i can get admin access on my terminal here and download everything while the teacher does his orientation. Otherwise i think i can fix it once i'm home now.
=====EDIT=====
Well getting the phone into Download Mode was a bit easier with Ubuntu via ADB since I don't have to wait for Windows to load the driver. Then just rebooted the box into windows for Odin. Long painful story short, I didn't setup Rom manager to be able to undo my changes when the USB port went bad/inconsistent and didn't expect those changes to complicate the recovery without USB. So I'm making sure it's a rather provable issue and going down to ATT with it. 7 Days from receiving the phone, and I'm goin in for an exchange due to bad USB. Funny.
Related
After spending my entire Saturday trying in vain to get my win 7 laptop to recognize my captivate I've decided I need to reach out for some help.
Right when I gore my phone, without too much hassle I did the superoneclick root via my pc with great success. Did the lagfix after that and all was well. Go me right?
I used my phone for a little bit and decided that it was time to but sonera music and pictures on it. This is where it all went wrong.
For background, I have done up to this Point: tried both driver sets that are floating around (and exe and the version most often linked to in help threads with a simple setup file), Ive tried kies, I've tried going into device manager to manually locate the divers. Nada.
At this point the drivers with the setup file will no longer install because the install of the exe screwed up at some point. Windows is only showing the device as us composite hub or as a unknown device. I can sometimes get it to say Samsung android usbb device but it shows that it is in error and it still wot see the phone. Someone else asked me if I had used the mount option when I comes up in my notifications bar which I haven't because it never gives me the option. I've tried disabling launcherpro, undoing the root, undoing the lagfix, formatting and wiping user data on the phone, still nada. I've tried all usb modes. Nada.
First things first, can someone explain to me exactly what I should do in device manager to get the drivers in order? I'm pretty sure this is the root of my problem. Any idea on how to get rid of the erroneous drivers that are causing the driver setup to fail?
Any help would be great :S
Need to try and manually remove three old drivers, then try and re install. Id suggest using the ones design gears posted on his one click back to stock post
Sent from my SAMSUNG-SGH-I897 using XDA App
I snipped this from one of my old posts in the Vibrant section...
For those of you having a problem with Windows 7 recognizing your Vibrant ... here is how I fixed it on my system.
*Note: You do not need to load any special USB drivers for your phone to be recognized in Mass Storage mode in Windows 7.
*Warning: You follow these instructions at your own risk ... no screaming at me if you try it and something gets screwed up!
1) Navigate your way into the Device Manager / Universal Serial Bus Controller
2) Uninstall the device(s) "USB Root Hub" (My system had 2 listed)
3) You will lose mouse and keyboard control (because you just removed the USB Hubs)
4) Reset your PC and allow Windows to boot normally.
5) Go back to the device manager and wait for all of the "!" marks to go away as windows re-installs the USB Hubs and reinitializes all of your devices.
6) Make sure your Vibrant is in mass storage mode and has USB debugging OFF
7) Plug in your Vibrant via the USB cable and be amazed as windows recognizes your device and assigns the drive letters. After you select the mount option on your phone you will have normal access via windows explorer.
Hope this helps some of you out there !!!
~Stresa
Sent from Samsung Vibrant
thanks for the good responses guys but both of those have failed. Odin cant even see my phone, same issue with superoneclick root. I even just tried on an enitrely different PC and got the same "device could not start" message.
tried deleting all the drivers for the USB devices. nada. still no connection
Subrock said:
After spending my entire Saturday trying in vain to get my win 7 laptop to recognize my captivate I've decided I need to reach out for some help.
Right when I gore my phone, without too much hassle I did the superoneclick root via my pc with great success. Did the lagfix after that and all was well. Go me right?
I used my phone for a little bit and decided that it was time to but sonera music and pictures on it. This is where it all went wrong.
For background, I have done up to this Point: tried both driver sets that are floating around (and exe and the version most often linked to in help threads with a simple setup file), Ive tried kies, I've tried going into device manager to manually locate the divers. Nada.
At this point the drivers with the setup file will no longer install because the install of the exe screwed up at some point. Windows is only showing the device as us composite hub or as a unknown device. I can sometimes get it to say Samsung android usbb device but it shows that it is in error and it still wot see the phone. Someone else asked me if I had used the mount option when I comes up in my notifications bar which I haven't because it never gives me the option. I've tried disabling launcherpro, undoing the root, undoing the lagfix, formatting and wiping user data on the phone, still nada. I've tried all usb modes. Nada.
First things first, can someone explain to me exactly what I should do in device manager to get the drivers in order? I'm pretty sure this is the root of my problem. Any idea on how to get rid of the erroneous drivers that are causing the driver setup to fail?
Any help would be great :S
Click to expand...
Click to collapse
kies or mass storage?
for kies debugging in settings>aplications must be disabled. i dont remember what works better ask on connection or to have connection type preset in settings>applications>usbsettings. im on froyo which works a million times better, kies on jf6 was like a 90% fail rate. it just didn't work for me.
for mass storage you need to mount the phone from a message in the notification bar, even if it asks the connection type and you tick mass storage it will not be mounted, you still need to mount from the notification bar.
you can also mount the sdcards from the notification bar in debugging mode which bypasses the connection type setting in settings>applications>usbsettings.
i tend to leave debugging on in case i need adb to fix my phone, i only turn it off to use kies which is useful to fix my contacts when i have multiples (it's alot easier to fix 200+ contacts on a computer screen using a mouse and keyboard), or install an update if i choose to run the phone stock.
tried in every combination of modes, cant get it connect any possible way. I also dont get the option to mount it from the notification bar so perhaps I have a hardware issue.
Are you using the stock usb cable? I've had problems with some but not all generic cables.
Sent from my SAMSUNG-SGH-I897 using XDA App
may not be what you want to hear
I actually had a similar problem, though not the same. My phone charges and I can use mass storage without issue, but I could not get Odin One Click updaters to ever "see" my phone. I tried every USB port on my box, tried several different driver sets (including the ones DG recommends). Eventually, I tried on a different computer. Odin saw it fine, updated no problems, first time out of the gate.
I know, I know, not everyone has access to two computers, and furthermore there "should" be no reason it can't work on a particular one, but for me, short of formatting my PC and reinstalling OS, I tried everything else I could think of.
Good luck, either way!
post moved to new thread
I don't think there should be a logical reason as to why this would ever work, but Windows (and computers in general sometimes) has a tendency to surprise me like that... but what if you try removing the drivers by whatever automatic means you are provided with, and then check and remove them manually (if necessary), and finally run CCleaner or some other program with registry cleaning capabilities to give your PC that last little enema.
Then use DG's drivers and install them in whatever way he recommends (been a while since I installed the drivers). That's really all I can think of on the PC side... maybe putting a cheap little USB hub between your phone and your PC if you have one laying around as another mostly futile attempt.
Fair warning, it is possible for CCleaner to mess up your PC... any program that messes with the registry can potentially do so. I've never seen the program cause harm, but it is possible.
I've had the same problem with my Crappy from day one. I still somehow got SuperOneClick to Root my phone through multiple attempts. But if all you need to do is transfer files from your phone to PC, and vice versa. I would recommend Android Sync Manager. It can read most of the file systems in the phone, and transfers at a decent speed.
same here
One of my PCs recognizes Cappy with the same cable, OS, drivers. Other one doesn't.
So I ended up using "ADB Wireless" from Market. It works pretty good, slower than USB, but works.
Also - if you are willing to make your PC work - try fresh reinstall of Windows 7SP1 and disable driver update from Internet.
Since your just trying to put music and pictures on the phone, try Kies Air from the market. Install it on your phone then you can transfer files wirelessly with the browser from your computer.
USB Cable
gbrown2036 said:
Are you using the stock usb cable? I've had problems with some but not all generic cables.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Definitely check the USB cable. I had this exact issue before. I checked drivers, did a bunch of un-installing and manual installing of drivers. Finally I tried my stock USB cable and all worked perfectly!
Just spent the last couple hours going through the rooting process, except for I never got the chance to flash CWM. The volume down button is not working to bring it into download mode. I know the button works when the phone is on, so it's not a mechanical issue.
I installed/uninstalled the Samsung drivers a handful of times, even grabbed the official file from Samsung's site. Restarted, didn't restart, ran Odin as admin and not, tried several USB cords, and several USB ports, and still nothing. I got it to go once, held til the COM port showed up in Odin, but then the phone randomly disconnected and got an error from Windows says drivers not installed correctly.
Any other ideas to try? I am coming from a rooted OG Droid, so it isn't my first time, but I am by no means an expert.
Thanks in advance.
Download terminal emulator and allow su permissions
Just type su, allow, restart app.
Type su, then reboot download
rolandpee said:
Just spent the last couple hours going through the rooting process, except for I never got the chance to flash CWM. The volume down button is not working to bring it into download mode. I know the button works when the phone is on, so it's not a mechanical issue.
I installed/uninstalled the Samsung drivers a handful of times, even grabbed the official file from Samsung's site. Restarted, didn't restart, ran Odin as admin and not, tried several USB cords, and several USB ports, and still nothing. I got it to go once, held til the COM port showed up in Odin, but then the phone randomly disconnected and got an error from Windows says drivers not installed correctly.
Any other ideas to try? I am coming from a rooted OG Droid, so it isn't my first time, but I am by no means an expert.
Thanks in advance.
Click to expand...
Click to collapse
The Charge is kind of touchy about download mode, I've noticed.
Here's what you can do.
1) Turn the phone off completely, unplugged off the charger.
2) When it is off completely, plug in the the USB cord and hit the volume down button at the same time. Hit the volume down button constantly many times until download mode finally kicks in.
ALTERNATIVELY -
You can download "Quick Boot (Reboot)" from the market. This will allow you to boot into Download Mode or Recovery straight from the app. Only if you're rooted though.
why not try another computer? also, are you using a laptop or a desktop. if you are using a laptop, make sure it is plugged into an outlet. (If on Vista or 7) Make sure your power settings are set to balanced or high performance (not sure if this affects USB ports but it may).
In addition to all that, what version of ODIN are you using?
I'll just tell you what I know works from experience.
#1: Turn the phone off and wait 15 seconds(it needs to completely shut off)
#2: Remove the battery
#3: Open Odin
#4: Plug the phone with no battery into the back USB port of your desktop(if you have a laptop just use any port)and while its plugged in just hold the Down volume control for a few seconds until a yellow triangle pops up on your screen but DONT let go until one of the rectangle ports in Odin turns yellow as well, then you can let go of the Down volume button.
If that doesn't work then I can't help ya D:
streetlightman said:
why not try another computer? also, are you using a laptop or a desktop. if you are using a laptop, make sure it is plugged into an outlet. (If on Vista or 7) Make sure your power settings are set to balanced or high performance (not sure if this affects USB ports but it may).
In addition to all that, what version of ODIN are you using?
Click to expand...
Click to collapse
I am using Windows 7 desktop so I'll check my power settings tonight.
Odin should be v1.3 IIRC. Laptop had the same issue which is also running 7 so I'll need to check settings on that as well.
Sent from my SCH-I510 using XDA App
Thanks for the other replies as well. Tonight will be attempt 2. Touchwiz is unfortuantely growing on me, but having the bloatware is really annoying me. Will probably run stock for a bit then flash gummy charged.
Sent from my SCH-I510 using XDA App
Got it working finally. Had to have the battery in the whole time otherwise it just kept failing.
I am now rooted and nearly debloated! Thanks for the tips.
Alrighty,
So I keep trying to update my g2x through LG but I continuously get an error message that says, "Problem with communication between cell phone and PC", and then it never goes past 4%. Yes, I've downloaded the proper drivers, and have followed the prompts of disconnecting the phone, removing the battery, powering back and pressing restart (countless times). None of it works though. And no, my phone isn't bricking up on the SW update, so that thread doesn't really help me.
I've been doing some research and it seems that it just doesn't work for some phones, but I'm wondering if anyone here has been able to successfully troubleshoot this.
Yeah, I'm one of the unfortunate ones that got a bad phone a while ago, so I'm hoping I can find a way to make it work...
Thanks in advance!!
I have had the same problem. I have a G2x that I got off ebay. It was un-moded, running stock Froyo 2.2.2. I went to the T-Mobile / LG update site and followed the steps. The program actually worked the first time, it went through the whole update procedure and said it was complete. The phone restarted, but when it restarted it no longer recognizes the SIM card and there is a question mark for the battery symbol. When I go into the settings, it does not show a baseband version. I have tried to re-install using the update program, but it stops after 36% saying "Problem with communication between cell phone and PC". Any ideas?
npo123 said:
Alrighty,
So I keep trying to update my g2x through LG but I continuously get an error message that says, "Problem with communication between cell phone and PC", and then it never goes past 4%. Yes, I've downloaded the proper drivers, and have followed the prompts of disconnecting the phone, removing the battery, powering back and pressing restart (countless times). None of it works though. And no, my phone isn't bricking up on the SW update, so that thread doesn't really help me.
I've been doing some research and it seems that it just doesn't work for some phones, but I'm wondering if anyone here has been able to successfully troubleshoot this.
Yeah, I'm one of the unfortunate ones that got a bad phone a while ago, so I'm hoping I can find a way to make it work...
Thanks in advance!!
Click to expand...
Click to collapse
Mine did this the first time. This is where the phone is never commanded to boot into S/W update mode so at least this is not a step where it can be bricked, as no update has actually occurred yet.
This is how I fixed it and got mine to update. Use a different USB port on your computer. Yes there are different as some are on internal hubs. The update must have a direct USB port with no hubs in between. I also reinstalled the drivers through the LG Update program and not from the LG website. When I did this and plugged in my phone about eight new devices were detected and installed as opposed to about two the first time around. Also, make sure your phone is in debug mode in Android application settings.
Then make sure you disable any anti-virus programs and turn off the Windows firewall. Then use ctrl-alt-delete and close down any programs running. Also go to the taskbar and click on the up arror (if Windows 7) and right click on each icon and see if you can close it down. Also, unplug all other USB devices (even a mouse if you don't need it) as they can interfere with communications between the updater program and your phone. The only USB device I left connected to my computer was the keyboard.
The LG Updater must be run in Admin mode. If when you run it you get a Windows warning asking you if it is ok for this program to make changes to your computer then it is launching in Admin mode. If not right click the LG Updater icon by clicking Start>All Program>LGMobile Support Tool>LGMobile update. Right click the last item and run it in admin mode. Again this is assuming you are running Windows 7. Admin mode is not necessary for Windows XP.
If all the drivers get loaded properly and you are not on a flakey USB port then at 4% the updater instructs the phone to reboot into S/W Update mode and that is where the real magic happens if you are lucky.
coreycollins3066 said:
I have had the same problem. I have a G2x that I got off ebay. It was un-moded, running stock Froyo 2.2.2. I went to the T-Mobile / LG update site and followed the steps. The program actually worked the first time, it went through the whole update procedure and said it was complete. The phone restarted, but when it restarted it no longer recognizes the SIM card and there is a question mark for the battery symbol. When I go into the settings, it does not show a baseband version. I have tried to re-install using the update program, but it stops after 36% saying "Problem with communication between cell phone and PC". Any ideas?
Click to expand...
Click to collapse
Use another USB port and try again. At various points in the update the updater resets the phones usb port and it has to reconnect. If it doesn't connect don't do a battery pull. Just try removing the USB cable and reinserting it. If you hear the computer beep wait a bit and then click restart on the updater. Hopefully it should see the device this time and continue the update.
Back in June, I turned on my TF700 with the dock attached, it started as usual.. I turned on my wifi, opened up my browser to look up plane tickets, then it restarted. I didn't think much of it, and when it loaded up again, I tried to look up tickets again, and it did the same thing. I gave up, closed it and zipped it up in my sleeve. It was a few hours before I got home, and when I took it out of the sleeve, it was quite warm! It was constantly rebooting and there was no way to turn if off. I left it out of the sleeve and let the battery die. I didn't use my tablet for a few days, and when I went to turn it on again, the same thing happened, and has been happening ever since. I have tried to start the tablet while connected to the dock, the wall charger, without the dock, with wifi on, with wifi off, etc. The tablet gets to the lock screen, I unlock it, and I only have about 10 seconds before it freezes and restarts. I am unable to turn off the device, because when I choose "shut down" from the menu, it shows that it's in the process of slowing down, but then the spinning wheel freezes and it vibrates and restarts before it can fully shut itself off. Since I can boot into android, I thought it was something that the tablet is trying to run upon startup that was causing problems. I was able to quickly get to settings and apps, to uninstall several apps, but nothing has helped. I used to have a task manager widget on the home screen, and uninstalled that too.
After doing research into the problem, I found that most people who have boot loop issues or constant restarting, are rooted and are experiencing difficulties with a new ROM. I am 100% stock. I have held down power and volume down. It gives me RCK, Android and Wipe. I have tried cold booting into android, but the same restart loop after 10 seconds occurs. I thought it might have been a bad firmware update that went through unbeknownst to me. So I downloaded the firmware file from ASUS, renamed and flashed it sucessfully. However, no change in the reboot problem. I am running the following version: US-epad-10.6.1.14.8-20130514. I know there's a new version out, but wasn't sure if I should try to flash that yet.
I am willing to try absolutely anything to fix the problem, with the EXCEPTION of wiping data. I know that would be the easy way to go, but I have photos and videos from my best friend's engagement and they are the only copies. If I am able to get my tablet to be stable enough to copy those off, I would then be willing to wipe and have a fresh start. I have tried connecting my tablet to my computer, and it is recognized. After it boots up and I unlock it, then the tablet begins to mount (I'm on windows 8). However, I still only have 10 seconds or so before the tablet restarts, and that's not enough time to even view the folders from the tablet.
It's been 3 months since this started, and I have done lots of research and tried lots of things, but nothing has helped yet. Since I haven't delved too deeply into the dev side of android (I've only rooted my S3) there is lots of android speak that I don't understand fully, or have experience with, like ADB. If someone is willing to offer suggestions on what to try, I am very good at following directions! Thank you for any help or leads you can offer.
Wow - you're in a difficult situation...
You being on stock I can only imagine the bootloop is caused by something you installed.
So if you can access settings and are able to uninstall apps, just keep doing it until you are back to the original stock setup.
Are you sure the files you are trying to save are still on the SD card? Don't know how you flashed 10.6.1.14.8, but flashing a complete firmware package ususally erases /data - although your persisiting bootloop indicates it didn't...... if the bootloop is caused by an app. And I can't imagine what else would cause it.
You could try to do a factory reset in Backup&Restore but you will loose the contents of your /data partition...
You can flash the 10.6.1.14.10 firmware file, but most likely you will also loose your data.
The only way I can think of to replace your bootloader and firmware without data loss is if you try to find a copy of the 10.6.1.14.10 dlpkgfile. That is the OTA update file Asus pushes out to users. It's a patch file, meaning it only replaces/updates new files and leaves everything else alone.
If you find the dlpkgfile on some forum you would have to place it into your /cache directory and reboot - and I don't know if you can copy it to your tablet before it bootloops again.
Unfortunately the reason for your bootloop is probably an app on the same partiton with the data you don't want to loose. Unless you manage to uninstall the culprit I don't see much hope....
Good luck!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Try getting adb access, this should allow us to diagnose the problem you are experiencing.
Tablet side: go to settings, developer options (if it is not visible, tap the build number 7 times), enable USB debugging
Computer side: no idea, they say Windows 8 is a bit tricky to get the drivers installed correctly.
When you have adb running, do "adb pull /proc/last_kmsg" and post the downloaded file - it should contain valuable info about your reboots.
_that6042401 said:
Try getting adb access, this should allow us to diagnose the problem you are experiencing.
Tablet side: go to settings, developer options (if it is not visible, tap the build number 7 times), enable USB debugging
Computer side: no idea, they say Windows 8 is a bit tricky to get the drivers installed correctly.
When you have adb running, do "adb pull /proc/last_kmsg" and post the downloaded file - it should contain valuable info about your reboots.
Click to expand...
Click to collapse
He's bootlooping..... How does he go into settings and turn on USB debugging?
I think the best option maybe to flash a stock Asus ROM from their site but that will wipe all data including those photos......
zanadoo22 said:
Back in June, I turned on my TF700 with the dock attached, it started as usual.. I turned on my wifi, opened up my browser to look up plane tickets, then it restarted. I didn't think much of it, and when it loaded up again, I tried to look up tickets again, and it did the same thing. I gave up, closed it and zipped it up in my sleeve. It was a few hours before I got home, and when I took it out of the sleeve, it was quite warm! It was constantly rebooting and there was no way to turn if off. I left it out of the sleeve and let the battery die. I didn't use my tablet for a few days, and when I went to turn it on again, the same thing happened, and has been happening ever since. I have tried to start the tablet while connected to the dock, the wall charger, without the dock, with wifi on, with wifi off, etc. The tablet gets to the lock screen, I unlock it, and I only have about 10 seconds before it freezes and restarts. I am unable to turn off the device, because when I choose "shut down" from the menu, it shows that it's in the process of slowing down, but then the spinning wheel freezes and it vibrates and restarts before it can fully shut itself off. Since I can boot into android, I thought it was something that the tablet is trying to run upon startup that was causing problems. I was able to quickly get to settings and apps, to uninstall several apps, but nothing has helped. I used to have a task manager widget on the home screen, and uninstalled that too.
After doing research into the problem, I found that most people who have boot loop issues or constant restarting, are rooted and are experiencing difficulties with a new ROM. I am 100% stock. I have held down power and volume down. It gives me RCK, Android and Wipe. I have tried cold booting into android, but the same restart loop after 10 seconds occurs. I thought it might have been a bad firmware update that went through unbeknownst to me. So I downloaded the firmware file from ASUS, renamed and flashed it sucessfully. However, no change in the reboot problem. I am running the following version: US-epad-10.6.1.14.8-20130514. I know there's a new version out, but wasn't sure if I should try to flash that yet.
I am willing to try absolutely anything to fix the problem, with the EXCEPTION of wiping data. I know that would be the easy way to go, but I have photos and videos from my best friend's engagement and they are the only copies. If I am able to get my tablet to be stable enough to copy those off, I would then be willing to wipe and have a fresh start. I have tried connecting my tablet to my computer, and it is recognized. After it boots up and I unlock it, then the tablet begins to mount (I'm on windows 8). However, I still only have 10 seconds or so before the tablet restarts, and that's not enough time to even view the folders from the tablet.
It's been 3 months since this started, and I have done lots of research and tried lots of things, but nothing has helped yet. Since I haven't delved too deeply into the dev side of android (I've only rooted my S3) there is lots of android speak that I don't understand fully, or have experience with, like ADB. If someone is willing to offer suggestions on what to try, I am very good at following directions! Thank you for any help or leads you can offer.
Click to expand...
Click to collapse
I have not use this method but you could try.
You need a boot OS tool on your external sd and run it from your external sd so you can access to your internal sd to copy files from there. You can search on the internet and you should find more information on how to use them depending on what boot os you are using.. Good luck.
zanadoo22 said:
and I only have about 10 seconds before it freezes and restarts.
Click to expand...
Click to collapse
sbdags said:
He's bootlooping..... How does he go into settings and turn on USB debugging?
Click to expand...
Click to collapse
Preferably FAST.
---------- Post added at 07:51 PM ---------- Previous post was at 07:51 PM ----------
LetMeKnow said:
You need a boot OS tool on your external sd
Click to expand...
Click to collapse
What is a boot OS tool?
_that said:
Try getting adb access, this should allow us to diagnose the problem you are experiencing.
Tablet side: go to settings, developer options (if it is not visible, tap the build number 7 times), enable USB debugging
Computer side: no idea, they say Windows 8 is a bit tricky to get the drivers installed correctly.
When you have adb running, do "adb pull /proc/last_kmsg" and post the downloaded file - it should contain valuable info about your reboots.
Click to expand...
Click to collapse
I was actually able to get usb debugging turned on. It took me quite a few tries, but I did it!
I've never used adb, but here's what I've done so far.. I downloaded the Android SDK and ASUS Pad PC Suite (which contains Asus Sync).
I was able to use the command prompt to navigate to the platform-tools folder and open adb, however when I type in adb devices, it doesn't recognize my device. What steps to do I take from here to be able to use adb to see my device, so I can pull the file to diagnose what's going on? How do I know if I have the right drivers installed so my computer can see my tablet? All I did was install the asus suite. Do I need to do anything further on that end?
zanadoo22 said:
I was actually able to get usb debugging turned on. It took me quite a few tries, but I did it!
I've never used adb, but here's what I've done so far.. I downloaded the Android SDK and ASUS Pad PC Suite (which contains Asus Sync).
I was able to use the command prompt to navigate to the platform-tools folder and open adb, however when I type in adb devices, it doesn't recognize my device. What steps to do I take from here to be able to use adb to see my device, so I can pull the file to diagnose what's going on? How do I know if I have the right drivers installed so my computer can see my tablet? All I did was install the asus suite. Do I need to do anything further on that end?
Click to expand...
Click to collapse
What Windows version do you have on your PC?
You can check your drivers in Device Manager. Open it, look for your tablet under Portable Devices and check if the driver has a yellow exclamation mark next to it. You should be able to update/install/uninstall the driver from here.
Try to find out if there is a setting in your Windows version to only allow Microsoft signed drivers and disable it.
Sent from my DROID4 using Tapatalk 2
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
JaimeZX said:
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
Click to expand...
Click to collapse
Interesting problem. I have bricked my phone a bunch of times and have always been able to get back to at least "download Mode". The method I use to go to "Download Mode" is With the usb cable plugged into the computer only, power off the phone. If phone wont power off, or stay powered off, pull battery, then put battery back in. Now hold vol down and vol up buttons only, keep holding these buttons as you plug the usb cable into the phone. In 3 seconds the download screen should appear. I hope this helps you get your phone back.
JaimeZX said:
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
Click to expand...
Click to collapse
This sounds like a time where a jig would be helpful. Any chance you can have your wife order one, and send to you? http://www.youtube.com/watch?v=D7I4dFX_iJ4
This should put you straight into download mode, and you can then flash.
Thanks, guys. I continued fiddling and got the phone into DL mode.
I also noted that when plugging and unplugging the phone, it would show up in zadig as "unknown device."
I tried to load the drivers on that, but (a) it still shows up as "unknown device" and (b) when I run HOC it doesn't see the phone under the list of compatible devices.
So.... still kind of stuck.
Any more ideas?
Oop. duplicate post
It's been awhile since I've played with the one clicks, but, "serial gadget" is what I remember seeing when I used them.
Right. MORE messing around later and "Serial Gadget" is it.
That said, I still think I have a driver issue. I have tried uninstalling and reinstalling the zadig-recommended drivers for Serial Gadget several times. I also tried manually installing the drivers from Super One Click.
Anyway, now when I load up HOC I get the green <<connected>> at bottom; but then sometimes it wants me to install the drivers (again) and sometimes it gets past that part, but then goes to
Flashing Kernel: 0%
...hangs there for about 10 seconds and then
Failed!
So... driver thing you think?
Thanks again,
If you reboot the phone after the 0% hanging for 10 seconds, does it go to the yellow exclamation mark screen? If so, just reflash again and you should be back to working... both my and my wife's phone always did that when I had to flash a kernel.
That's just another download screen that theraze is describing.
Exacatly. But the alternate download screen always came up after restarting the phone after a 'failed' flash where it stayed at 0% where it was successfully communicating through the cable. That just meant to not break the drivers or unplug anything... just reboot fast and finish up quickly.
Okay - I can definitely try that! It had not occurred to me to try and reboot the phone right then.
Question, though - when I get the "Failed!" Then HOC essentially hangs, when it says something along the lines of "ending session..." and never progresses from there. So how do you "restart quickly?" Because I have to like, close and reopen HOC. I guess I will see if it succeeds at ending the session when I reboot.
I will try it again. Strange though, sometimes HOC accepts the existing driver (I managed to DL the Samsung driver installer) and sometimes it wants to reinstall "WinUSB." does that make sense? Is the WinUSB an acceptable one?
The winusb is the right driver for heimdall, it doesn't like the Samsung driver.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Samsung drivers and the one click drivers clash. Yes, uninstall Samsung completely if you want to use the one click.
Hm. Thanks for that - might be part of the problem.
Dunno what I did differently, if anything, but last night I tried flashing again and this time it went through! I was very glad to see the whole HOC process completed successfully!
So anyway - thanks so much for the help, guys.