It is showing a small round mobile phone, 2 dots, a ! inside an orange triangle, 2 more dots, and a computer.
This is the first time I'm seeing this screen.
Edit: Just to give some insight as to what I was doing...
I was using a SGT7 build of CM9, and I noticed USB Tethering wasn't working (native nor Wired Tether 1.4 worked). I had to run to a friends house for the night real fast, so I figured I'd just go back to Stock firmware and use that for a few hours just so my desktop could get Internet.
I am also using Windows 8 Release Preview. Odin could see my device fine, but upon pressing Start to start the flashing process, it did nothing (I'm guessing Odin or Samsung's drivers don't work well on W8RP). No progress was made on either Odin or my tab for about 5 minutes. Since nothing was done, I figured I could close Odin, and restart my Tab. Now I only get this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I immediately went to the "How To Unbrick Your Galaxy Tab!" thread, but didn't find mention of the screen I described in this post, and then I made this post in panic.
When I went back to Windows 7, Odin was able to reflash my tab successfully, and USB Tethering was working fine. So perhaps Windows 8 has some weird incompatibility with Samsung Drivers? In any case, this might serve as a warning to anyone trying to use Odin in Windows 8.
I think it was mentioned in a few threads.
Many confirmed that it is another download mode.
You just have to make sure it is fully charged, and keep trying Odin restocking. It will go through.
(I never experienced it myself)
Edit: many reference, just search in here fore "phone exclamation pc"
Yea it would seem it's another download mode. I was able to flash with Odin just fine in Windows 7, so all is well again
i have said this in many threads. this is the result of faulty flashing. just use the latest version of odin
please thank me if you found this helpful
Related
Sorry if this comes off as noobish but is there anyway to flash over to stock Gingerbread (and eventually to a custom rom) w/o the use of Odin? I've tried to search but didn't really see anything that clarified this for me. My phone just doesn't want to work with ODIN at all...it will pick it up every once in awhile but only when the phone is powered completely on. I've installed, deleted, reinstalled drivers/kies etc. Thanks in advance to anyone that can help me resolve this issue!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
you can give heimdall a try, but if you are talking about a cwm flash then no, you cannot. flashing bootloaders in cwm is WAY more risky than using odin or heimdall.
My main issue is that I cant keep my laptop to recognize my phone in the first place...like I said earlier, I tried various drivers including the ones from Samsung and Softpedia...And whenever I do get it to respond, it wont recognize it in download mode at all...thanks though...the only thing that I haven't really tried was a new cable...will be purchasing one later...I feel so left behind on my roms lol. I was able to flash Froyo with no prob...now its so many out that I can't get my hands on...
I would try thee drivers from dg (designgears ) thread in development. It also might recognize better from stock also.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
could there be problems with NET framework 4?
jgotti107 said:
My main issue is that I cant keep my laptop to recognize my phone in the first place...like I said earlier, I tried various drivers including the ones from Samsung and Softpedia...And whenever I do get it to respond, it wont recognize it in download mode at all...thanks though...the only thing that I haven't really tried was a new cable...will be purchasing one later...I feel so left behind on my roms lol. I was able to flash Froyo with no prob...now its so many out that I can't get my hands on...
Click to expand...
Click to collapse
I'm in the same situation from time to time on my work laptop. Not sure it's gonna mather for your situation but i found that if i undock and redock the computer Odin then recognize the phone again when it goes foobar. (I only use the laptop usb port and not the docking station ones).
HI,
Well last night i tried updating my note to ICS 4.0.
Downloaded the 4.0 german update and started up and tried to flash it.
Then came the problem.
After about 3 minutes i get this message
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And from there i am stuck.
hope someone could help me out!
It looks like the drivers for your phone are not installed. Under the fail box it should say Something like com 6 in yellow if you had the drivers installed and phone connected. Try installing the drivers for the phone again and when its connected to odin you should see a yellow box and you will be ready to flash then.
Sent from my GT-N7000 using xda premium
Install drivers throught Kies. Its one of options whn doing connection rroubleshooting. After reinstall reboot pc. For next steps keep kies closed. It looks also like you did not go into download mode.
Press volume button down, homekey and powerbutton at same time quickly after powering up device. May need couple of tries. Its tricky. Reconnect if not done so phone to pc.
Press volume up to confirm. Now you can flash do not disconnect phone, be patient and wait till device powers back up.
Sent from my GT-N7000 using Tapatalk 2
Thanks guys!
Had to upgrade the driver , installing it now.
sof2champ said:
Thanks guys!
Had to upgrade the driver , installing it now.
Click to expand...
Click to collapse
Aside that...
fired up PC Odin n load the "PDA" file, put ur phone in "Download" mode THEN u connect to ur PC....
most of the time ur PC will detect ur phone n install some more drivers other than the drivers u had updated previously
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Background:
Captivate was running SlimICS 4.1. I had trouble connecting to the PC and ramdom widgets crashing. Decide to give Milestone 6 a try while I wait for JB. I flashed Glitch 20120520.1522 before I flashed M6 (to avoid Status 7 error), then realized that kernel had TWRP, Rom installation freezes. Restarted, stuck on Glitch splash screen.
Troubleshooting so far:
Odinf Oneclick and Odin 3 both show yellow in fort box.Tried flashing Speedmod kernel, so I could flash custom ROM. OidnOneClick or Odin3 do not get beyond SetupConnection. Heimdall on Ubuntu also rcognizes the phone, but does not get beyong loading kernel. Now phone is in Phone /!\PC screen, but the problems persist. I have tried uninstalling and re-installing drivers, from all different choices (Samsung, KIES, AIO Toolkit. Nothing seems to work.
I have been up for almost 26 hours. I hope someone finds a solution and shares it with me. I am sure I'm missing something,due to my lack of sleep.
Please help me.
Edit: Looking over my post, I can tell it's difficult to even tell that my problem is. I apologize, I was falling asleep at the keyboard last night. I took a screen shot of my problem with Odin.
Odin does not go beyond SetupConnection and just hangs there indefinately. Has anyone had this problem before? How did you solve it?
See the Captivate Connection Issues and Download Mode Help Stickied Thread in the General Forum.
Sent from my SAMSUNG-SGH-I897 using xda premium
I have solved the problem. I uninstalled all drivers, ran CCCleaner, and used Ubuntu to flash Official KB2 by AdamOutler. I guess that I was so tired last night and desperate (I was falling asleep at my desk while trying to restore the phone) that I was not going through all the motions. Anyway, thanks a lot for the help 4-2ndtwin. Haven't seen much from you since the Illuminance days. Hope everything is well!
Yep...Still around...try to lend a helping hand when i can...
Glad u got it going !
Sent from my SAMSUNG-SGH-I897 using xda premium
nexus 6 marshmallow root using mac osX - error message! - device is currupt -
wanting better optimization for my Nexus 6 with marshmallow build MRA58R, i started the process of unlocking BL and going for root access following this guide:
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
right in the beginning already im stuck. i unlocked bootloader fine, had toggled on in the device, checked through terminal. everything fine. started root process and as soon as i ran CF-Auto-Root it started its thing and rather pretty quickly a new screen came up reading in red letters "Device is corrupt. It can't be trusted and may not work properly." for maybe one second before shutting off. i can briefly get it to power up, only to get that same screen. a couple times i did have it back in bootloader mode through ADB from the terminal. but nothing since. the few times i did get bootloader up i tried a recovery process from the site referred by the error screen itself here: https://support.google.com/nexus/answer/6185381?p=verified_boot&rd=1
but when i ran fastboot oem unlock it now says it cannot find device and tells me to go into device and change OEM setting in developer tools. kind of tough when it wont boot up. i sure would love a solution to this one, id appreciate any help..
added: on the device in bootloader mode it reads USB connected but on the laptop will not recognize any connected devices?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am no expert, but it seems like you are having the exact same problem that this person had. It seems that the guide will not work on 6.0, but luckily, he seems to have found a solution.
ICStevenC. said:
I am no expert, but it seems like you are having the exact same problem that this person had. It seems that the guide will not work on 6.0, but luckily, he seems to have found a solution.
Click to expand...
Click to collapse
dear Lord baby Jesus, thank you. only on step 2 and its further then ive been in hours. :good:
Okkaayy guys, so, i'll take you to the end of the whole thing which is, I installed and downgraded 2 versions in stock rom, which was V12.5.1.0 worked like a charm, then I updated the version with Xiaomi's original it's own system updater to newer version and it was still fine then I updated it to Android 12, MIUI 13 and it bootlooped.
So, I wasn't able to get into recovery, trieedd soo many times and neither I was able to get in to fastboot mode. What did I do? Flashed it again with Format All + Download option. I got the bar and everything but I waited a bit and nothing happened. I'm like, is this working? And I did the mistake. I pulled the plug. And here I am. Surely I've 60+ battery. Besides that I charged it for more than 15 minutes. No power button works, no fastboot, no recovery. Nothing "HAPPENS". Literally. No matter what I do, how long I press to any button, device won't turn on in any sort of way. Libusb still detects it as Mediatek driver but I can't use SP Flash Tool because simply device won't turn on. Bypass utility stays like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Held power button for 5 min (literally I did) nothing happened
No fastboot or recovery
SP Flash Tool simply can't do the trick because device doesn't turn on
I have 60+ battery %100 surely.
USBLIB still able to detect the port.
What do? Is it even possible to rescue this poor guy? It was my main phone btw...
EDIT - UPDATE: I have no idea how but I was playing around with SP Flash Tool, trying to do some things, nothing was actually happening but like after few minutes phone just gone back into bootloop, It turned on, I genuinely don't know how and just for confirmation, after I installed stock rom back my charge is %73 so surely it wasn't related to my battery. IDK this devices are weird. Sorry for the topic mods..