I've been trying the root method listed here:
http://forum.xda-developers.com/showpost.php?p=19792563&postcount=1
I followed the instructions to the letter, though when in came to selecting a file it never let me choose... only gave me a choice of internal and external SD. It's been 45 minutes that I'm staring at the "Downloading... Do not turn off target!!!" screen and I'm beginning to worry.
Any advice from others who've gone this route would be helpful. Thanks.
Sounds like your in ODIN mode (not recovery.) That doesn't make much sense when it gave you a choice with internal/external, however.
At which point in the steps provided in the linked post did you start to see that "downloading..." screen? Is your device attached to your PC with the data/charging/usb cable? Was it attached when you performed step 4 of the linked thread? If it IS attached, is KIES running? If KIES is running, is it doing anything?
Gary
Thanks for the follow up, Gary. This is all a bit new to me after dumping a rooted Noot Tablet that wasn't cutting it. It sounds like I did slip into Odin mode (?) for I remember seeing some similar mention in a terminal-like text in the top left corner of the screen.
I was able to shut it off, reboot, and all came back normal (sigh of relief). Considering the number of things you mention, I will have to brave the process again, as I can't remember all that was involved.
Couple of notes... I am on a Mac, though I have both Win7 and WinXP-SP3 virtualized. I have been having terrible problems getting Kies to pick up on the tab while in either VMed Win environs. Very on and off, and the Mac ver of Kies sucks! Any advice would be helpful.
Also... will rooting gain me write access to the external SD? As of now, the only file manager that can do this is the native one that came with the tab. I much prefer some the market FMs.
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.
OK so here is a complete and simple rundown of the events that led to the demise of the USB nonsense. i think... Honestly, I do not have a definite answer or clue as to the cause of this, directly or indirectly. :/
First, Lets get the redundancies and silly questions out of the way first before they can be asked. I believe in the expedition of things for faster service and for clarity.
System Specs for reference:
HP Pavilion DV6780SE Laptop
Partition 1:..................................Partition 2:
Windows 8.1 Professional (64-bit) / Linux Mint 17 (64-bit with 4gb swap partition)
4GB RAM
128GB SSD
1. I have freshly installed 4.4.2 via ODIN with a FULL WIPE TAR file. like FIVE minutes ago as of this post timestamp.
2. USB Works while using ODIN but not when i boot into the OS. Safe Mode and regular make no difference to this effect.
3. I have all the proper drivers, ADB versions and what not preinstalled on my computer, AND i am only using USB 2.0 (i know better than to use 3.0) Drivers are provided by universal naked driver here on XDA, and i have previously used the USB successfully with this phone.
4. Finally, regarding the successful usage of the USB while booted, it ONLY worked before i upgraded to 4.4.2. i had full access in 4.3 and below. Now only ODIN works. Is there any process or explanation which fixes this issue? its really annoying to use Kies Air with a less than adequate router and its only 54 Mbps... thats 9 times slower than USB which is 480 Mbps.
Alright. On to questions... What would cause a previous version of android for this device to have a fully functioning USB subsystem and after the upgrade, stop working. I'll mention once more, i'll FULLY wiped the phone using an original stock TAR file aimed for 4.4.2 android AND used the PIT file for this device and corresponding capacity, just in case the partitions were messed up somehow.
We should discount any factors pertaining to hardware issues because I've already proven that it works in ODIN, and multiple stations and USB cables have been used with the same result. Only ODIN works.
Upon booting, for a split second i see my device manager light up something, but it says "unknown device (bad descriptor request)" and disappears. this happens exactly twice before the boot sequence commences. AND, it only happens coming from ODIN mode, and not during a reboot, to my knowledge. I've tried going into ODIN mode with the cable still plugged in, and then rebooting with a battery pull and a press and hold power attempt, and still nothing. This has worked for some, but not for me. Its simply baffling... When the phone is fully booted, nothing shows up in device manager. the list does not refresh or show any uninstalled devices as it normally would with other USB devices i own. Insertion or removal or any device warrants a visual list refresh. The whole device tree normally collapses and expands again on its own at this point.
I request some major help with this. this whole thing is quite the nuisance. I cannot do anything with my phone at all, even ADB usage which I need in the hopes of moving to a custom ROM or otherwise. The option simple isn't possible at this time.
Any suggestions? ANY!? :crying::fingers-crossed:
I tried to sort out a never used Tab A (2019) that had a locked build (MDM, no access to system). I used Odin to install a ROM image which I believed at the time to be correct. It didn't seem to go right, halted at Param. Eventually i had to close Odin and now the Tab A will only charge and, when i do power+vol up+home all I can get is the red error message and the lightening bolt even though it's not charging. When I connect to my PC it is not detected.
I have searched for previous questions like this and watched Youtube vids but no-one seems to have a solution for my example. Thanks
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!