Hi guys, I'm totally going crazy with my Nexus in last few days, the problems I'm encountering are the following:
1) There's no way to connect it to my pc, the battery charges, but the pc just can't see the device, I tried with different cables and with other computers, unsuccessfully.
2) My CWM Recovery has problems too: it says "no command" and I can't do anything there.
3) I decided to take advantage of the warranty but first I need to lock the bootloader... here's another problem: my nexus isn't rooted so I can't use applications from play store to do that and, obviously i can't use the cable because of point "1)".
Anyone has an idea? Is there anything I can do except going to the shop and buying another one? Thanks
Mode Odin, Clean and flash stock Android.... It's the only thing i can say....
So I have to follow this guide???
I follow the guide i link above. Then I can use fastboot and I lock bootloader. Now I have only the problem of "no command" recovery and the wall charging!
Thanks frimpasi for the help!!!
Try to reinstall the recovery or try other recovery. And what is the "wall charging"?
Enviado desde mi Galaxy Nexus usando Tapatalk 4
Ok, ghe recovery si ok.
Now there's only one problem: when phone si off I plug USB cable to the battery charger and I see the charging icon. Few seconds later I see another time the same icon. Otherwise if the fone is on and I charge it notthing append. So I can charge the phone only with che computer usb port, but it doesn't comunicate with computer.
WTF? I don't have any idea of what it could be....
Maybe the pc don't recognize the phone because the pc hasn't the drivers... It's an option, but I'm not sure,it's a weird issue....
No, driver went fine! The problem is the same discuss in this thread: http://forum.xda-developers.com/showthread.php?t=2442698
Related
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Sorry to hear that. This is something I learned (second hand, thank god) when I had my Galaxy S1. Odin can simultaneously be the best and worst tool you use.
Sent from my Galaxy Nexus
ericaraj said:
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Click to expand...
Click to collapse
There is a chance it's not totally bricked, that happened to me on an other samsung device while i was flashing with odin. U pulled the battery too early.i also had that black screen with the yellow pc and exclamation mark, try another usb port in ur pc and try to flash again with odin, if not, take the battery out and keep it out for a while (i don't know, 30min for example) then try odin again... u should be able to enter download mode somehow despite the screen u got now.
Sent from my Galaxy Nexus using xda premium
ericaraj said:
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Click to expand...
Click to collapse
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
rayiskon said:
There is a chance it's not totally bricked, that happened to me on an other samsung device while i was flashing with odin. U pulled the battery too early.i also had that black screen with the yellow pc and exclamation mark, try another usb port in ur pc and try to flash again with odin, if not, take the battery out and keep it out for a while (i don't know, 30min for example) then try odin again... u should be able to enter download mode somehow despite the screen u got now.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
iCaptivate said:
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
Click to expand...
Click to collapse
I had a feeling that it wasn't truly bricked, but since my phone's USB driver (or whatever aspect of USB data transfer) was malfunctioning I couldn't do anything about it. I think of it this way: if in that state my phone had a 5% chance of being recognized by Odin, and if my phone already had less than a 20% chance of being recognized before the soft-brick, then I had a 1% chance or less that it would even show up in Odin and even lower odds at a successful flash. Regardless, Verizon agreed to send me a warranty replacement.
iCaptivate said:
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
Click to expand...
Click to collapse
Same here with the vibrant. IIRC there was a special way to get your phone to recognize Odin when it happened. Something like plugging in the phone to the computer and then pulling the battery. Odin even worked when I borked a flash and the screen wouldn't even turn on. I would think the nexus could be brought back similarly.
But if the USB port is on the fritz I'm not sure I would want to bring it back.
As far as I'm concerned Odin is the worst thing you can hook up to your devce. No single program has bricked more devices than Odin.
______________
Just Flash It !!!
on my old SGS1 there was chance get back bricked device by method called "JIG"..(its hardware way get back download mode) but i dont study it more...
I don't think its bricked, I once restore my phone from a black screen that Odin still recognized as download mode. The drivers can get iffy, do you have a third comp that you can install fresh drivers on. Also is your USB jack on the Nexus loose? Sometimes it really is due to your PC's USB connection. I also had issues with cheap blackberry cables and had to use higher quality ones.
Did you try going into download mode by connecting it to the PC while with battery removed and hold (whatever buttons to boot it into download mode), then insert the batteries. Or try entering using a jig.
Also a bit lazy of me (on phone), but can someone point me to where to get Odin images for the Nexus?
try to use another cable to connect ur phone to pc
just flash stock via odin, it's not bricked.
My s2 sometimes has that problem when i flash stock
eksasol said:
I don't think its bricked, I once restore my phone from a black screen that Odin still recognized as download mode. The drivers can get iffy, do you have a third comp that you can install fresh drivers on. Also is your USB jack on the Nexus loose? Sometimes it really is due to your PC's USB connection. I also had issues with cheap blackberry cables and had to use higher quality ones.
Did you try going into download mode by connecting it to the PC while with battery removed and hold (whatever buttons to boot it into download mode), then insert the batteries. Or try entering using a jig.
Also a bit lazy of me (on phone), but can someone point me to where to get Odin images for the Nexus?
Click to expand...
Click to collapse
I appreciate the advice but I no longer have that phone. My replacement should come today.
With regards to the drivers, I was referring to the drivers on the phone not on the computer. I honestly don't know if there are USB drivers on the phone (I would think there are) or even if those drivers were causing the malfunction.
The first thing I'm doing this afternoon is plugging my replacement phone into my computer. If the new one doesn't work right then I'll have to make a trip to the Apple store because the problem will almost certainly be my laptop. I'll also owe a big apology to Verizon.
Hi there! First of all I don't speak english very well.
My Galaxy Nexus hard bricked yesterday.
tl;dr no boot animation, no recovery mode, no download mode, no response from computer.
I thought it had just a low battery level, I found it turned off. So I tried to recharge it but it gave no signals, no battery icon, nothing.
After an all night long recharge I tried to turn it on, to enter in download mode or in recovery mode but nothing works. I also tried to connect it with my computer with and without battery, no response, no "OMAP" device found, no sound from Windows for plugging it in, nothing.
I found this thread here in xda, many people has been redirected to it and found their solution to the brick problem.
I tried to follow all the steps but when I plug in the phone and start the .bat file nothing happens, just stuck on "Waiting for device".
The phone is unlocked and rooted. I'm running AOKP JB-MR1 Build 2 and Franco Kernel for a month, never had problems with them, never installed other ROMs after that.
What should I do now? Should I try to do something or just bring it to a support center? The phone is still in warranty, there would be any problem because it has a non-stock ROM?
I've red about a jig to force the Odin mode, should I buy it? (I found this one)
Thanks for the help.
Have you tried booting into Odin mode
ntb81 said:
Have you tried booting into Odin mode
Click to expand...
Click to collapse
Yes, it doesn't work.
have you your warranty on it?
return it and get a new one
It's hard bricked and a JTAG unit may force it into download mode, if you send it in for warranty, chances are it won't be accepted as it was obviously tampered with and they would find out that your bootloader is unlocked and charge you more money than the device is actually worth to fix it.
I don't understand how it could of bricked if nothing has changed on the phone for a month or longer. Nothing was flashed recently so how can you hard brick the phone?
Beauenheim said:
It's hard bricked and a JTAG unit may force it into download mode, if you send it in for warranty, chances are it won't be accepted as it was obviously tampered with and they would find out that your bootloader is unlocked and charge you more money than the device is actually worth to fix it.
Click to expand...
Click to collapse
Yeah, that's why I'm not sure to send it in for warranty. So have I to try with a JTAG first?
[bman123] said:
I don't understand how it could of bricked if nothing has changed on the phone for a month or longer. Nothing was flashed recently so how can you hard brick the phone?
Click to expand...
Click to collapse
I'm not understanding that too, I don't know what happened. Suddendly it stopped working. Maybe is just a battery problem, I'll try to use another one before bringing it to the shop where I bought it.
same happened to me, but I have an untouched phone with stock android. it worked well for over an year until today.
I see a lot of people having same issue, but they say that when connected to PC over USB the phone is recognized as OMAP.
for me the PC doesn't do anything...
any help? thanks
---------- Post added at 06:12 AM ---------- Previous post was at 06:02 AM ----------
galiganu said:
same happened to me, but I have an untouched phone with stock android. it worked well for over an year until today.
I see a lot of people having same issue, but they say that when connected to PC over USB the phone is recognized as OMAP.
for me the PC doesn't do anything...
any help? thanks
Click to expand...
Click to collapse
so right after I wrote that I plugged my phone into USB of my PC without battery. when I inserted the battery it started showing me the battery sign and I could started the phone. 3 minutes later it went black again, but the trick didnt work again.
any ideas? thanks
Try This !!
Arrange a 4 ohm resistor and try to attach it in ur usb plug port of phone ..it 'll force the phon eto go in download mode or say Fastboot mode.
then follow a tutorial to flash any rom..
its quite easy else ping me !!
Tech.Nik said:
Arrange a 4 ohm resistor and try to attach it in ur usb plug port of phone ..it 'll force the phon eto go in download mode or say Fastboot mode.
then follow a tutorial to flash any rom..
its quite easy else ping me !!
Click to expand...
Click to collapse
Please could you explain a bit more how to go about this? I have a Verizon Galaxy Nexus in a somewhat similar condition. This one is recognised as an OMAP 4430 device. I downloaded OMAP Flasher, installed drivers and tried to bring it back to life but after running the batch file I get this error: Operation FAILED (Remote: : Driver init error 0x00FF8080 - MMC CONFIG FAILURE). Can the resistor trick work on this and if yes, how can I go about it? I am not faint-hearted; I think I can handle it if given the right instructions.
After I tried everything i could from the internet, I went to a shop and tested to see if the USB is broken - and indeed it was. I replaced the USB component of the phone and after that it started.
Thanks guys
galiganu said:
After I tried everything i could from the internet, I went to a shop and tested to see if the USB is broken - and indeed it was. I replaced the USB component of the phone and after that it started.
Thanks guys
Click to expand...
Click to collapse
Yeah, the faulty USB port is a very common issue.
Hello everybody.
First I want to say is that I'm sorry for my english. It's not my native language.
And now lets go to my problem:
It started like few days ago when I updated my phone to the newest franco.kernel. After flashing that, my phone began to behave strangely and it didn't want to go tho nexus logo. It just always crashed.
So I decided to plug my phone to PC for flashing stock kernel or older version and what happened.. PC didn't recognize that phone is connected. I tried use Universal Naked Driver, OMAPflash (its just saying "waiting for device") and it still didnt want to work. I tried to plug it in notebook and it didnt work too. Well so I could still go to recovery mode, because I'm using TWRP. I did factory reset and my phone worked again even plug in to PC still hasn't worked.
And today I decided to try flash stock kernel with boot.img via TWRP. Of course it didnt work, so I did a stupid thing and flashed older version of franco.kernel (I don't know why I did that.. Maybe I was thinking it will fix my problem with USB, because it started with flashing the newest version..eh) and then my phone can't go tho Google Logo. Well so I did factory reset again + system reset (really clever) via TWRP well then it didnt work of course (because of no ROM, system), so I remembered that I did nandroid backup before my first factory reset. So I did a restore of backup, but it still stuck at Google Logo and everything I can do now is:
Go to recovery mode (TWRP) or Odin mode (which is just saying "Downloading...")
So I can't flash my phone tho PC, cause it doesn't recognize it is plugged in and I really don't know, what can I do now. I also though that USB cable should be "bad", because I didn't use it too much (like few months ago) so I would buy new one, but I don't think it is that problem, because it worked last time when I rooted my phone with PC etc.(but as I said.. few months ago)
Well.. I hope there will be solution for that.
Thanks in advance for reply.
You can read this. The entire first post. And maybe a couple more.
http://forum.xda-developers.com/showthread.php?t=1626895
Sent from my Nexus
The problem is that my PC doesn't recognize it is connected (when I install drivers, there is "yellow triangle"). It is charging while its connected to PC, but its not working as USB device. If I could see my phone on PC, it could fix my problem and I could return to stock.
Phone is working, it can be charged, it works in recovery-mode (with TWRP) and odin mode, but it cant go tho google logo and PC doesn't recognize it is connected. That's the current status.
+ It's rooted and unlocked....So the warranty is breached and If I will send it back to shop for repair, I will pay a lot of money :-/
Tordiato said:
The problem is that my PC doesn't recognize it is connected (when I install drivers, there is "yellow triangle"). It is charging while its connected to PC, but its not working as USB device. If I could see my phone on PC, it could fix my problem and I could return to stock.
Phone is working, it can be charged, it works in recovery-mode (with TWRP) and odin mode, but it cant go tho google logo and PC doesn't recognize it is connected. That's the current status.
+ It's rooted and unlocked....So the warranty is breached and If I will send it back to shop for repair, I will pay a lot of money :-/
Click to expand...
Click to collapse
Dude, just read the thread. Uninstall all drivers and reboot before doing anything else.
Sent from my Nexus
Tordiato said:
I also though that USB cable should be "bad", because I didn't use it too much (like few months ago) so I would buy new one, but I don't think it is that problem, because it worked last time when I rooted my phone with PC etc.(but as I said.. few months ago)
Click to expand...
Click to collapse
I bought a new USB cable today (Samsung APCBU10) and it works now! So I can flash it back to stock Problem solved.
//Thanks for the help anyway bk201doesntexist
I need help, my ZF2 suddenly cannot be detected by my windows 7 laptop and pc. When I tried to plug in usb 3 port, it wont get detected. If in usb 2/1 port, it will be detected but with the yellow exclamation mark. I tried updating mtp but it wont update (shows device is up to date). I tried reinstalling ROM and factory reset thru the ROM, but still not working.
I returned to stock but still it wont get detected on my pc or laptop. I ****ed everthing up when I returned to stock since I cant root it back anymore since it wont get detected by adb.
Evereything is up to date including 15sec adb installer 1.4.2 or 1.4.3 and intel usb driver 1.10 from 1.9.
I will try to reformat thru stock recovery and see if it will work. But before doing that, any suggestion or ideas?
Does it charge while connected to the laptop?
Have you tried using other micro USB cables?
FrameCall said:
Does it charge while connected to the laptop?
Have you tried using other micro USB cables?
Click to expand...
Click to collapse
Yes, it charged when I plugged it on different port. And yes, I have tried different cables, samsung, asus and dont know brand chords. All cables only shows usb device malfunction code 43 and all charged my phone when plugged to ports.
Anybody? Suggestions? Ideas?
Anyone?
Can you check and see if fast charging works?
24imelqui said:
Anyone?
Click to expand...
Click to collapse
Which recovery you installed?
trinimike100 said:
Can you check and see if fast charging works?
Click to expand...
Click to collapse
Fast charging dont work anymore. It will take atleast 2 hrs to charge the phone.
mr_gourav2000 said:
Which recovery you installed?
Click to expand...
Click to collapse
I used to have a twrp 3.0.0-0 recover then flash .165 recovery then flash .165 stock ROM. And after reboot, still cant get detect by any port. It just charged my phone. Then I updated to .174 but still no detection.
24imelqui said:
I used to have a twrp 3.0.0-0 recover then flash .165 recovery then flash .165 stock ROM. And after reboot, still cant get detect by any port. It just charged my phone. Then I updated to .174 but still no detection.
Click to expand...
Click to collapse
Try this.
http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526
mr_gourav2000 said:
Try this.
http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526
Click to expand...
Click to collapse
I have already returned to stock rom and recovery all is good, but my problem still exist. I cant get my phone to get detect by my PC or laptop. It just charged and it show usb device malfunction code 43. I got all drivers installed since I was able to root and flash custom roms before. Im asking if hard reseting thru stock recovery will fixed my problem and if you have any others ideas please share. Like how to root my device again without using pc/lwptop.
24imelqui said:
I have already returned to stock rom and recovery all is good, but my problem still exist. I cant get my phone to get detect by my PC or laptop. It just charged and it show usb device malfunction code 43. I got all drivers installed since I was able to root and flash custom roms before. Im asking if hard reseting thru stock recovery will fixed my problem and if you have any others ideas please share. Like how to root my device again without using pc/lwptop.
Click to expand...
Click to collapse
Try this may help you -
Switch off mobile
Plug in usb and connect to laptop or pc.
Now power on your mobile.
Look what happened?
mr_gourav2000 said:
Try this may help you -
Switch off mobile
Plug in usb and connect to laptop or pc.
Now power on your mobile.
Look what happened?
Click to expand...
Click to collapse
Still usb device malfunction code 43. Thanks man
I had the same issues when my Zenfone's chip set fried - PC did not recognise the phone, phone did not recognise USB drives, fast charging not working. To be precise what happened: one day I plugged in the cable (original one, with original charger), the phone showed high temperature warning and shut down. Then after a while I turned it back on but USB wasn't working any more, except for the slow charging. Sent in for a warranty repair, it was stuck there for like 2 months before they sent me a new phone.
Had the same problem, it turned out that my zenfone 2's charging port and microphone had been damaged. Replaced the parts from a third party repair man as my warranty was void. He returned me a very well functioning and no more problematic zennie within a week
It surely isn't a software problem..
Hope it helped..
Abhishek1108 said:
Had the same problem, it turned out that my zenfone 2's charging port and microphone had been damaged. Replaced the parts from a third party repair man as my warranty was void. He returned me a very well functioning and no more problematic zennie within a week
It surely isn't a software problem..
Hope it helped..
Click to expand...
Click to collapse
j4nitor said:
I had the same issues when my Zenfone's chip set fried - PC did not recognise the phone, phone did not recognise USB drives, fast charging not working. To be precise what happened: one day I plugged in the cable (original one, with original charger), the phone showed high temperature warning and shut down. Then after a while I turned it back on but USB wasn't working any more, except for the slow charging. Sent in for a warranty repair, it was stuck there for like 2 months before they sent me a new phone.
Click to expand...
Click to collapse
I have the same problem also. Can you tell me what part needed to be replaced? I already tried replacing the usb sub board but it did not work.
trinimike100 said:
I have the same problem also. Can you tell me what part needed to be replaced? I already tried replacing the usb sub board but it did not work.
Click to expand...
Click to collapse
I went to a 3rd party repairman and he said he just replaced the flex data cable or something like that, he also said it is common for zenfone smartphone. Then my phone is detectable again.
Guys I need your help
I don't know what happened to my Note II phone.
Only thing I've done was to root it. I'm still using the same O.S. I haven't tried flashing something on it before
Here's what happened.
I was just chillin, chatting on Messenger when all of a sudden, the phone LED indicator flashes but it doesn't unlock. then the phone died and when i was trying to charge it, there was only a charge icon on the screen but it wasn't moving.
The next day i bought a new battery and now what happened was that it wasn't going through the Galaxy Note II screen (bootloop perhaps?) i tried going through recovery mode -- dead android icon then it shuts down. and i was still able to access download mode
before i was able to follow the soft brick recovery mode, all of a sudden it doesn't even go to recovery/download mode anymore
LED indicator does not turn on for charging even if i plug it into the charger.
What do i need to do? i don't have JTAG as an option
I read somewhere that I you can boot hardbricked phones using an SD card by doing something about partition stuff there will that work? :laugh::laugh::laugh: hope to get some replies from you guys :good::good:
Have you tried using a 2.0 amp charger and letting the phone charge for a few hours?
audit13 said:
Have you tried using a 2.0 amp charger and letting the phone charge for a few hours?
Click to expand...
Click to collapse
no i haven't tho the battery has a charge (i tested it on a different note 2 i booted)
phone doesn't go into recovery mode anymore. anything i can do to revive it? btw sorry for the late reply
Not much you can do if the phone can't get into recovery mode.
When connected to a computer, do any devices appear in the device manager?
I am also facing the same problem,,,,..not entering to recovery mode .......when trying to install stock firmware through odin (using windows 10)it says nand write and next step fail....i didn't even root my phone.....please friends help me....Thanks in advance....and yes it enters to download mode
Are you using the original Samsung USB cable? Tried other USB cables and all USB ports on the computer? What is the specific Odin error?
audit13 said:
Are you using the original Samsung USB cable? Tried other USB cables and all USB ports on the computer? What is the specific Odin error?
Click to expand...
Click to collapse
i don't have the samsung cable,,,,I was using the sony data cable with cylinder shapes at the ends
yes,i tried all the ports
odin says FAIL! after the Nand write start
What is the error message in Odin? You could also post the log from the log window.