Related
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.
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.
Hi All I wonder if some kind soul can help with a problem I have with a Samsung Galaxy Tab 4 10.1. (SM-T530) when switched on it displayed the Samsung banner after this the pretty Samsung logo appears with like coloured spots flying around it, I have not seen this Samsung log before and I wonder if this is some indication of the software it is trying to run.
After a short while a screen appears with a message in "SPANISH" which translated says. "data partition is damaged. need to reset your device to factory defaults. so all data will be cleared" at this time the up down volume seems to work as should, and displays the slider graphic. Other things seem to work OK with this screen when buttons are pressed they make the squishy noise.
I have tied to get into the boot recovery screen but get a graphic of the Android for a second then the Android on its back with flap open and the triangle then the thing reboots.
I can enter Odin mode but when I try to recover the device with a load everything seems OK with the initialisation until the start of the flash then I see "MMC: mmc_write fail" on the Tab.
I have tried different PCs, different MS platforms, different USB leads and ports. Kies sees the tab seems happy downloads latest software then same thing again "MMC: mmc_write fail" I have no idea what software was on the Tab, I also think that there is more info available on the USB port which I cannot see.
When I plug the Tab into the USB port of my Linux pc it is seen in "Places" as Samsung tab but when you double click on it an error message comes up on the PC "unable to mount file" could some one with some engine room knowledge pleas help.
Try to flash stock firmware with 4 files & with pit too , if no luck then center services its better for you ..
Good luck ,,
Hi Thereassaad, Thank you very much for you reply to my post. I have tried your suggestion and this has failed to fix my problem, I also tried to run the .pit file in Odin but still the same results, I did suspect that my problem could be a hardware issue as I have read in other posts that there may be a problem with memory damage under some types of memory write operation although I am not sure that this applied to SM-T530.
I obtained this Tab from ebay as a project in self learning and I have had plenty of fun tinkering with it already. I have found that there is not much in-depth information on the web about the architectural structure of the firmware on Samsung devices but I shall continue to tinker. The Tab I have has no indication of being tampered with ether by attempts to root it or tampering with the innards. I only want to return it to stock Samsung firmware eventually. I do feel that the firmware is unable to write enable the flash and I am still not sure whether this is a firmware or hardware issue.
I am going to try a comms program to see what information is available at the usb connector as there is quite a lot going on which we do not see with Odin and Kies such as serial number confirmation, firmware versions, etc. I may try to use my comms program as a sniffer when Odin or Kies talks to the Tab on initialisation.
If you or anyone else has any good ideas, I would love to hear
Thanks again for your help.
Hi there. I've been trying to get my SM-N920T fully functional with LineageOS for a few months now. I originally followed the "EASY STEPS" guide pinned at the top of the forum and flashed noble kernel, TWRP, and LineageOS on to the device. Everything seemed to work fine at first, but after a few days I noticed some issues:
No audio in phone calls (VoIP worked fine)
No USB connection with computers
After seeing a lot of threads and guides like this one in my research, I determined that I had somehow failed to properly root the device.
I have a Windows 10 machine and a Pop!_OS 20.10 (System76 Ubuntu variant) machine that I've tried connecting to the phone. Prior to today, both machines could make the initial connection to the device, but could not mount anything for file transfer. Windows made its audible "boop" but nothing else happened. Linux put a "Galaxy Note 5" icon in the dock, but clicking it did nothing. I queried some errors from the syslog and found this post, which led to a StackOverflow discussion that indicates some USB3 issues connecting to devices like the Note 5 on Linux. Unfortunately, my System76 laptop has only USB3 ports, so I may never be able to connect it to my Note 5.
Today I decided to try the whole "EASY STEPS" guide again. However, after flashing the noble kernel again, my phone no longer gets past the "KERNEL IS NOT SEANDROID ENFORCING Samsung Galaxy Note 5 powered by Android" boot screen, and I am unable to restart into recovery mode. If I try to restart into recovery, I get the battery charging screen with "KERNEL IS NOT SEANDROID ENFORCING" still in the corner.
The Windows machine is able to recognize the device in download mode (the ID:COM box turns blue in Odin 3.13.1 and 3.10.7) so I am using that for my flashing. I've tried flashing with both versions of Odin and neither seems to make a difference.
At this point, I am mostly flailing, because the links in the pinned resource thread are broken due to the Xenforo migration, and the domain for the images in the "EASY STEPS" guide has expired, so I can't even compare what I'm seeing to the guide visually. There are a lot of conflicting and expired guides out there, and I'm still very inexperienced at this, so I'm not sure what information to trust. I'd like to avoid bricking this device if possible, assuming I haven't already done that. I have a backup device, but I'm not touching it until I get some input from somebody who knows what they are doing at least a little more than I do!
Thanks very much in advance for your help!
Over the past 1 year I have purchased a total of 7 Samsung Galaxy A32 5G. One for myself (Development) and one each for my children and wife. They were (are) decent devices for the price. I’m a licensed Android Developer (among a-lot of certs and licenses) and I have tried everything. I explain this so we can skip the basic concepts.
One night one of my device wouldn’t charge properly (no water damage) I turned it off to see if it charges correctly while off.
Instead the device enters a boot loop. I noticed an error on the bottom. Seems like it said “Kernel Dump” or “KDump” but the message was too fast to read. I even attempted taking video and pausing it on that frame but it was so quick it’s blurry. I was able to read it a bit better though and It does look like it says Kernel Dump (kdump) though. I can boot into Download Mode , I cannot boot into recovery or Fastboot however. I have tried many options (Kies , Odin) and while Odin is absolutely 100% completing successfully with no issues the device continues to go into a boot loop and show this Kernal dump. . I know Linux in general has a Kdump which creates a log when the Kernal crashes. Naturally I can’t think of a way to see that log. Is there something I’m missing? Is there a solution that works?
Thank anyone for any suggestions.
Innovatorsww said:
Over the past 1 year I have purchased a total of 7 Samsung Galaxy A32 5G. One for myself (Development) and one each for my children and wife. They were (are) decent devices for the price. I’m a licensed Android Developer (among a-lot of certs and licenses) and I have tried everything. I explain this so we can skip the basic concepts.
One night one of my device wouldn’t charge properly (no water damage) I turned it off to see if it charges correctly while off.
Instead the device enters a boot loop. I noticed an error on the bottom. Seems like it said “Kernel Dump” or “KDump” but the message was too fast to read. I even attempted taking video and pausing it on that frame but it was so quick it’s blurry. I was able to read it a bit better though and It does look like it says Kernel Dump (kdump) though. I can boot into Download Mode , I cannot boot into recovery or Fastboot however. I have tried many options (Kies , Odin) and while Odin is absolutely 100% completing successfully with no issues the device continues to go into a boot loop and show this Kernal dump. . I know Linux in general has a Kdump which creates a log when the Kernal crashes. Naturally I can’t think of a way to see that log. Is there something I’m missing? Is there a solution that works?
Thank anyone for any suggestions.
Click to expand...
Click to collapse
Have you tried booting in to safe-mofe or adb booting an image, a/b slots, etc. Make sure clear data (sucks)
Not much help, I'm sure you've covered all this, and well, the basics. Good luck
I had the same issue with my A32 5G and i found a solution to this. Plug the phone in and make sure it is charging and then power it on and set it aside and let it go into the boot loop. (plugging it in is to ensure it wont die) Eventually, after a few hours, the boot loop will stop and the phone will open android recovery and allow you to facotry reset the phone. After the reset it should boot again. Not sure what the exact cause of this is but this is what worked for me. Good luck!