OK first, my rooted u.s. 4.0 running cm7 suddenly had a read on file system. Couldn't download anything, delete anything, or modify anything on /mnt/sdcard. So I thought I would go into Odin and restore from an old backup. In the middle of the process, Odin crashes and my device gives me a weird screen that I can't get rid of unless I remove the battery. I can't even go into cwm. The screen shows a phone and a computer with a yellow caution symbol between the them. I think it means there is an error with connection to the PC or something. I've tried to fix it with Odin but it won't recognize the device. What do I do???
Mine did this aswell. I found that although I could not get it into download mode to try and flash again, the symbol you spoke of lets it occur anyway. The issue with it not being recognised may be due driver problems so try uninstalling them compleyely then reinstalling.
Then basically, just try to reflash through odin whilst that symbol is there.
Hope I helped
Sent from my YP-G70
I've tried but it just says SetupConnection..... and stays there.
Sent from my A500 using XDA
the symbol described is a sort of default download mode that comes up when the OS i corrupted.
As others said... you are not totally out of luck yet.
Make sure you have the right drivers on you PC.
Start Odin and connect your player via USB.
Your device should now be recognized by PC if you have the correct drivers (since you were already trying to flash in the first place, you might be ok here).
Flash one of the stock roms you may find in the dev section for your player (make sure it's the right one, US or INT) and hit start. If you are not sure how to use Odin, there are some good guides you can search for also.
Your player should reboot once it's completed and you can start the rooting and flashing process again.
Good luck.
Yay fixed it. After many attempts with odin (it kept failing) it finally booted up. Thanks for the help guys
Sent from my YP-G1 using xda premium
This question has already been posted multiple times
Related
Hello,
Complete Noob here. I'm hopeful that I can get some assistance restoring my phone to a semi-useful function. I've searched these forums, and while I've found some solutions, none of them seem to work when you can get your phone past the initial boot screen when turning on the phone. Here's the story, appreciate it if you can help.
Yesterday I saw that there was an update from Samsung for the vibrant, so I installed Kies Mini on my computer and followed the instructions. It would have been nice if the program would have detected that I was running the 64 bit version of Windows 7 as a Samsung Tech person told me afterward that it wasn't compatible with that version of W7.
When Samsung heard that the screen on my phone showed a picture of a cell phone, with a orange triangle connected to a computer they said I'd need to mail them the phone and wait over a week to get a working phone. I figured I have nothing to lose at this point, and searched for a "do it yourself" solution. I found one click unbrick or something like that, and it went to work, but my phone now is stuck in the initial boot screen for the Vibrant. So all you see is "Vibrant" and "Samsung" on the phone.
I've read several posts about putting the phone into developer or restore mode, pushing combinations of the up/down vol button with the power button, etc., perhaps I'm doing this incorrectly, but nothing seems to get my computer to recognize the phone. I downloaded Odin, and the pit and pda files to start back at Eclair, but odin doesn't detect the device, nor does it have anything listed in the id-com section. I also tried the heimdall one click for the vibrant, but again it can find the device.
Couple of questions -
Can the phone be returned to a working status or should I just return it to Samsung and wait a week for the phone?
Is there any chance that I will be able to recover anything that was on the phone? I expect not, but wonder if so. I backed up my important files, but it would be nice not to have to start from scratch.
sounds like you are able to get your phone into download mode, but odin is not recognizing, which means we have a driver issue. Put your phone into download mode, and then uninstall kies on your computer, then re-install it, this will uninstall and then reinstall the drivers, I have to do this nearly every time I use odin.
Thanks for the quick response. I assume I'll need to do this on an XP machine, and not a 64 bit W7 machine? Plugged the phone into a XP machine, and now the phone is able to get to the downloading... yellow icons. I hope this means I'm making progress
Try the drivers here:
http://forum.xda-developers.com/showthread.php?p=11633550#post11633550
And stay away from Kies. It will murder you're phone.
Sent from my ZenDroid using XDA Premium App
Okay, thanks for the link. I see what I can do with that. Prior to your post, I got into download mode, download the pit file s1_odin_20100512.pit and the pda file T959UVJI6.tar. Tried to reload things on the phone. The phone now boots to a screen where it says
Android system recover (2e)
Samsung Recovery Utils
Vol up
Vol down
Power - select items
etc, given the option to reboot, reinstall packages, clear user data, or delete cache
below it says...
Movi_check Start
checksum confirmation need_checksum[0]
Not need checksum confirmation
Movi_check already executed...
movi_checking done!
update media, please wait
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdate_media: Can't mount DBDATA:
copy default media content failed
The ji6 Odin file is known for doing that. Pull the battery, get back into download mode, and use these two files in Odin.
http://www.justanotherdev.slackdev.com/T959UVJFD.tar
http://www.justanotherdev.slackdev.com/s1_odin_20100512.rar
Sent from my ZenDroid using XDA Premium App
Same thing here, but I got it finally by using an ancient version of odin to flash to stock jfd. Kies picked it up right away after that.
That said, now that I have no fear of odin there are no traces of kies left on my pc...
Do you know if those file are located some place else, the link doesn't appear to have either file?
Sorry about that. Didn't realize the links were dead.
http://www.multiupload.com/NP507B6P8A
This should have both the pit and tar files in it.
Sent from my ZenDroid using XDA Premium App
SUCCESS!!!!!
Thanks so much. It worked. Now to replace my backup files. No more Kies for me.
Hello guys,
I really really need your help, I have spend like two weeks reading articles and possible solutions to my problem and none of them worked.
My cell is the international version GT-I9100 and my PC has W7 Ultimate installed
I have my phone in USB debug mode and have installed USB drivers with KIES
2 weeks ago I was able to get to download mode by using the 3 buttons method with no problems... so I decided to try to install the latest ICS I9100XXLPQ with ODIN
Odin did recognized the cellphone and the yellow label appeared and show the message accepted... so far so good, put the I9100XXLPQ file in PDA, check the Auto Reboot and F. Reset Time options and hit the Start button but the problem started there.... it just sits at setup connection and wont do a thing. wait for more than 30 mins and nothing just sits there.
So I unplugged the cellphone from the cable thinking that it would be ok since Odin didn´t started with the flashing process (or at least that what i thought)... there´s the problem, now my cellphone does not came up and I´m not even able to get into download mode. I just get a black screen (see attachment)
I have tried with the 3 buttons, with One-Click Unbrick and with the Jig cable and none of them worked, I just keep getting the same screen.
(by the way... i tried with One-Click Unbrick but it still saying that the drivers are not installed properly so it keep installing the drivers over and over and I have not been actually able to use it.)
Odin is still able to recognized the cellphone so I tried to re-flash the cellphone doing the same thing this time it passed the connection setup and seems that it will worked but after 5 to 10 mins it failed but with no error message. I guess that it wont do anything since the cell is not in download mode.
Any ideas or suggestions would be more than appreciate!
Regards...
I once had the same problem. When odin sees the mobile even if its not in download mode. This means its connected but the bootloader is broken.
To fix this u need to use some program called hamedal or hamidal or something. I used it to unbrick my galazy tab. you can flash the boot section (bootloader image) manually thru it and it will fix your mobile.
Try to google about it and how to use it. If you don't find anything. Pm me and I will try to help u .
Sent from my GT-I9100 using xda premium
try to use a JIG,it will force the phone to enter the download mode
fearkillerr said:
I once had the same problem. When odin sees the mobile even if its not in download mode. This means its connected but the bootloader is broken.
To fix this u need to use some program called hamedal or hamidal or something. I used it to unbrick my galazy tab. you can flash the boot section (bootloader image) manually thru it and it will fix your mobile.
Try to google about it and how to use it. If you don't find anything. Pm me and I will try to help u .
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I think that you are taking about Heimdall
One Click Unbrick is the same thing.... (Heimdall One-Click project)
I tried that already... but thanks
I haven't worked much with i9000 or i777 to figure out heimdall compatibility. Your option is Odin right now.
Your only solution is a USB JIG.
shesho07 said:
I think that you are taking about Heimdall
One Click Unbrick is the same thing.... (Heimdall One-Click project)
I tried that already... but thanks
Click to expand...
Click to collapse
Just open that program, install the usb drivers for it while connecting your phone and try to flash the zimage.img into the phone manually. I believe it will work. I've fixed many bricked galaxy devices with that.
Sent from my GT-I9100 using xda premium
Hey all.... Long time lurker and reader here. I usually find all my answers through previous posts but I'm a little stuck here and cannot find the appropriate guide to help me out.
I have a GT-P7510 which has always been rooted and has had a few ROM lifes, so I'm no stranger to CWM and download mode, Odin Etc... (But I'm certainly no expert by any means)
Last week I tried a flash and ended up bricked. (Soft brick) I tried several times to flash back to stock with the current as well as last known good firmware from SamFiles, but ODIN would fail partially through the flash. I got the message "Can't open the specified file. (Line: 1876)", so I checked here: http://forum.xda-developers.com/showthread.php?t=1370433 But that didn't help me.... And now, my tab is not recognized in any of the laptops or desktops I plug it into. (WinXP, WinVista, Win7 -- Kies drivers all fresh from Samsung)
I can get into Download mode. I can get into recovery, (I have done a wipe/re-format Factory reset in recovery a few times now) but nothing seems to help. I'd be willing to learn how to probe around with ADB, but haven't tried for lack of a driver being recognized. I have a few Linux boxes here at the house and haven't tried them. I wouldn't know where to start if the device was recognized by them.
Any suggestions on how to get the device recognized? Or, maybe what I can do from CWM (Sideload?). or even if I get an ADB connection from one of my linux boxes, would I be able to re-flash the firmware?
Thanks in advance.
first thing is to check your cable, then your pc drivers, if u can get in to cwm, try a new cable and mount the usb from there, put in a new rom, and flash it.
hope this helps, dude. Good luck.
If you foobarred the tab by a failed flash using Odin as you described logic would dictate that it has absolutely nothing too do with pc drivers suddenly not being good if they worked before, same for pc and cable.
You need to reinstall using Odin as you say you can get into download, using a .pit file, ticking repartition, and a stock firmware file. If that works you can go on to play another day....
If you're not sue about stuff you're using, good version of Odin (not all versions flash the 7510 properly) for 7510 and drivers are here http://forum.xda-developers.com/showthread.php?t=1518895
I'll put a .pit file up here when I get to a computer and get yourself a STOCK rom from samfirmware to flash thro Odin and you should be good to go
Sent from my GT-P7510 using XDA Premium HD app
stinky73 said:
If you foobarred the tab by a failed flash using Odin as you described logic would dictate that it has absolutely nothing too do with pc drivers suddenly not being good if they worked before, same for pc and cable.
You need to reinstall using Odin as you say you can get into download, using a .pit file, ticking repartition, and a stock firmware file. If that works you can go on to play another day....
If you're not sue about stuff you're using, good version of Odin (not all versions flash the 7510 properly) for 7510 and drivers are here http://forum.xda-developers.com/showthread.php?t=1518895
I'll put a .pit file up here when I get to a computer and get yourself a STOCK rom from samfirmware to flash thro Odin and you should be good to go
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
That sounds great man.... THANKS! I do have the correct Odin, and I have a clean firmware from SamFiles. But I have tried looking for a pit for the 7510 and haven't had much luck. If you could post one, I'd be forever in your debt.
Here y'are
stinky73 said:
Here y'are
Click to expand...
Click to collapse
Thank you brother! I'll report back in a day or so.
Good luck!
sent from my still superb Google I/O 7510
stinky73 said:
Good luck!
Click to expand...
Click to collapse
Back to the drawing board I guess... I have a new cable on-order. However I was able to get the driver loaded by utilizing the dreaded "Plug - Unplug" routine several times until I just got lucky.
Odin can see it as COM5, and I used your pit (Again, TY!) I tried using the "P7510XABLPL_P7510UELPL" file I got from Samsung, but Odin is locked up at this point. (See screen cap)
I'll keep beating my head against this wall
:silly:
Odin 1.85 is just about the most random version of the prog when it comes to the 7510...
Try the one I have posted below (v1.3) it has never let me down (whereas 1.85 often has done to me what it is doing to you)
Worth a try
stinky73 said:
Odin 1.85 is just about the most random version of the prog when it comes to the 7510...
Try the one I have posted below (v1.3) it has never let me down (whereas 1.85 often has done to me what it is doing to you)
Worth a try
Click to expand...
Click to collapse
Yes. Sorry I forgot to mention that.
I saw your other post and did grab that 1.3 version. However, When I get the drivers loaded (When windows "sees" the tablet after plugging and unplugging numerous times) It will show up as COM3 or COM5 in any version of odin Except 1.3.
I tried various versions of Odin and when they all see the com port, 1.3 does not. Truly bizarre to me.... With 1.85 and or 1.7 I was successful in just loading the pit file, but if I try to load a PDA, it just freezes.
I installed Android SDK and started playing with ADB yesterday. I haven't had much success in addressing the Tablet. Also, I cannot get into recovery any more. It appears that the tablet is stuck in download mode, as if it's in a loop. ('the device states that it's downloading even after a reboot with no cable attached.)
My new cables will be here in a couple of days. Until then, I'm letting the battery die completely and will try again with the new cables.
P-tek said:
Yes. Sorry I forgot to mention that.
I saw your other post and did grab that 1.3 version. However, When I get the drivers loaded (When windows "sees" the tablet after plugging and unplugging numerous times) It will show up as COM3 or COM5 in any version of odin Except 1.3.
I tried various versions of Odin and when they all see the com port, 1.3 does not. Truly bizarre to me.... With 1.85 and or 1.7 I was successful in just loading the pit file, but if I try to load a PDA, it just freezes.
I installed Android SDK and started playing with ADB yesterday. I haven't had much success in addressing the Tablet. Also, I cannot get into recovery any more. It appears that the tablet is stuck in download mode, as if it's in a loop. ('the device states that it's downloading even after a reboot with no cable attached.)
My new cables will be here in a couple of days. Until then, I'm letting the battery die completely and will try again with the new cables.
Click to expand...
Click to collapse
That's an odd one for the download reboot.... As normally you should get choice of recovery or download as first step... Would tend to signal a failed download
I've often seen people say here "have you tried a different computer?" and scoffed a bit at that but maybe in your case...
However to be scientific you should only change one variable at a time so as to know where the result comes from, so start with the cable and we can see where you go from there
sent from my still superb Google I/O 7510 (xda hd)
Victorious
stinky73 said:
That's an odd one for the download reboot.... As normally you should get choice of recovery or download as first step... Would tend to signal a failed download
I've often seen people say here "have you tried a different computer?" and scoffed a bit at that but maybe in your case...
However to be scientific you should only change one variable at a time so as to know where the result comes from, so start with the cable and we can see where you go from there
sent from my still superb Google I/O 7510 (xda hd)
Click to expand...
Click to collapse
Thank you again for all your help!
My new cables arrived and appeared to be at the center of the issue. Once plugged in, the drivers properly loaded and I was successful with Odin. I used the pit you gave me for a re-partition, and the UELPL PDA from Samfiles.
It was initially stuck in a boot loop after the successful flash, but I was able to reboot to recovery, F/R, wipe and clean it up and now it's ALIVE! :victory:
Yeeee. Haaaaah!!!!
sent from my still superb Google I/O 7510 (xda hd)
Greetings all,
I am a real noob and have recently taken to playing with my android devices.
Unfortunately I am in a predicament with my old S3 I9300.
I really screwed up and failed to make a Nandroid back up when using TWRP to flash Cynagenmod 13, after following the correct procedure on my other I9300 and successfully flashing it I became cocky and made the fatal error of not having a back up. A bit of back story but perhaps unrelated it was also suffering the old "Failed to Mount EFS" message which I have recently learnt to fix on my Old Old I9100 S2 using ADB.
After flasing It was in a Cynagenmod boot loop and was not able to be recognized by my pc via download mode or recovery, so was unable to use Odin, Kies or even ADB.
After experiencing USB issues with Cynagenmod 13 on my other I9300 when the flash was successful, I decided that perhaps it would be better to flash Android Revolution as the USB connections just seem to work better. After the flash seemed to be successful and the Samsung Logo just hung around and never booted.
I played with it all day, trying to get Kies, ADB and Odin to recognize it to no avail, (I tried every little trick on Google, reinstall drivers, restart pc , restart device, plug unplug, play with the buttons and the battery etc.....) the thing is, is that Odin would recognize it in bootloop.
After growing tired of this not working, for some stupid reason I decided to flash CWM over TWRP via MicroSD, i just thought maybe I could get ADB to work or something. Anyway the flash worked and I continued to try ADB, KIES and ODIN but nothing.
To make matters worse currently when I try to go to Recovery CWM is now looping (I'm hoping its a passing phase), so with recovery gone my phone is restricted to Download mode. I really think my last chance is to get download mode communicating with Kies to get the Firmware.
Feeling frustrated and about throw my phone on the recycling heap after googling and reading so many XDA threads I decided to reach out and ask for any help or suggestions in finding a way to get my phone recognized in Download Mode.
I thank you for your time in reading this post and look forward to hearing any advice.
Cheers.
muddled said:
Greetings all,
I am a real noob and have recently taken to playing with my android devices.
Unfortunately I am in a predicament with my old S3 I9300.
I really screwed up and failed to make a Nandroid back up when using TWRP to flash Cynagenmod 13, after following the correct procedure on my other I9300 and successfully flashing it I became cocky and made the fatal error of not having a back up. A bit of back story but perhaps unrelated it was also suffering the old "Failed to Mount EFS" message which I have recently learnt to fix on my Old Old I9100 S2 using ADB.
After flasing It was in a Cynagenmod boot loop and was not able to be recognized by my pc via download mode or recovery, so was unable to use Odin, Kies or even ADB.
After experiencing USB issues with Cynagenmod 13 on my other I9300 when the flash was successful, I decided that perhaps it would be better to flash Android Revolution as the USB connections just seem to work better. After the flash seemed to be successful and the Samsung Logo just hung around and never booted.
I played with it all day, trying to get Kies, ADB and Odin to recognize it to no avail, (I tried every little trick on Google, reinstall drivers, restart pc , restart device, plug unplug, play with the buttons and the battery etc.....) the thing is, is that Odin would recognize it in bootloop.
After growing tired of this not working, for some stupid reason I decided to flash CWM over TWRP via MicroSD, i just thought maybe I could get ADB to work or something. Anyway the flash worked and I continued to try ADB, KIES and ODIN but nothing.
To make matters worse currently when I try to go to Recovery CWM is now looping (I'm hoping its a passing phase), so with recovery gone my phone is restricted to Download mode. I really think my last chance is to get download mode communicating with Kies to get the Firmware.
Feeling frustrated and about throw my phone on the recycling heap after googling and reading so many XDA threads I decided to reach out and ask for any help or suggestions in finding a way to get my phone recognized in Download Mode.
I thank you for your time in reading this post and look forward to hearing any advice.
Cheers.
Click to expand...
Click to collapse
Hey Mate,
Firstly we all are noobs here helping each other, secondly from my experience of S3, it is such a device that under any condition, if your hardware is intact, you can recover your phone from almost anything, so yeah you might have a solution to your problem.
Coming to the problem at hand, i had the same thing happen to my S3, (only twrp logo showed, couldn't access recovery, no ROM, only download mode available) the way i fixed it was using odin, now i know you say that odin is not recognizing your device, the thing is firstly Kies is useless in this situation acc. to me, it only works stock ROM and that too with difficulty, what i would say is go here - http://developer.samsung.com/technical-doc/view.do?v=T000000117
and then install the drivers to your PC, next up download the official firmware from sammobile or any other site (careful of the version you are using), now put the phone in download mod, start odin and then connect your phone. Now, hopefully odin will recognize your phone and you can flash the official firmware, also i would recommend to stay on the official firmware for like a week before returning to flashing again as i have noticed that constant flashing and wiping leads to not only errors like "unable to mount EFS" but also serious errors like "Unable to mount /system" or "Unable to mount /Data" ,which clearly sucks
Please try the method and tell me if it worked , if not we'l try something else but we sure as hell will get your device working again
If still not recognized then here is a suggestion :
Exit/uninstall from nokia/ovi suit.
Exit/uninstall bluestack. (if u r using it)
Update your drivers(phone specific)
Use correct odin version acc to ur phone
Sent from my Micromax E352 using XDA-Developers mobile app
I'm just gonna throw my 2 cents in too. I didn't read your whole thread as I'm in a slight rush right now.
But basically -
Can your PC recognise your phone when it's plugged into USB in Download Mode? If so, use ODIN to flash any stock firmware and you're back to square one (working, but stock) phone. Then go from there. Obviously try to flash the right firmware or you'll end up no further forward.
If it can't recognise it, try reinstalling the drivers, uninstalling the programs mentioned above and using another USB cable. My experience with my own S3 has shown potential wear with the USB port on the bottom of the phone presumably due to it's age and as a result it doesn't recognise many USB cables.
Regards
I've been reading posts about this same problem, but either there was no solution or the one given didn't work. My FHD10 is stuck on the Asus boot screen. I've tried factory reseting it with Droidboot, but that never leaves the boot screen either. I tried downloading the correct system from the Asus site onto an SD card with FAT32 formating (I didn't reformat it, but that's what it reports to have), but none of those files are labeled ASUS_BUNDLE.zip, which is what Droidboot says it's looking for. I tried renaming a few files with that name, but it just kept responding "Can't find image file."
Since the middle of the Droidboot screen indicates that a USB cable should be connected, I tried that. I have a Mac and also borrowed a Windows PC from a friend. When I connect it to either one, the center of the tablet screen says "Ready for Download," but I don't see it mounted on either PC anywhere I can find. If I go into the device manager, I do see it listed as "Android Phone."
So, can anyone tell me what I'm doing wrong with the SC card or tell me how I can connect to a PC? I’ve posted this question on two other forums and so far haven’t gotten any responses except to try posting here. Thanks in advance for your help.
You My boy Need to Tell Us What you want.
Don't tell me What you Did Tell me What you want.It's called Firmware.System is The folder in Firmware as /system
Your Phone is Probably Stuck on A hard Bootloop.
There is only a Few Ways To get outta That.
1:Use Odin to Flash a Hot New Baked Firmware.
2: Use Odin to flash TWRP and Flash A Custom ROM Using It(Bye Bye Stock).
3:Flash a Custom ROM using Odin on PC
4:Flash TWRP via Odin and See What's Wrong With The System Correct folder permissions,delete Corrupted Things and Done.
Sent from my Nexus 6P using Tapatalk