Related
So heres the synopsis on what my issue is:
first of all-
phone: Samsung Captivate build 1010
current OS: (botched install of Darky 8)
problem: no recovery menu capability, stuck in reboot loop (will not go past ATT Logo), can go into download mode but odin does not see the phone
I botched a Darky 8 install. I attempted to install the rom to my captivate via rom manager but to no avail. I then decided to give the install a try via clockwork and had luck. the rom was not to my liking so I went to mount the internal sd and proceeded to delete all files internally to make a fresh odin install possible (as I always do). It was at the time of restarting my phone that I realized the rom I install was accidently the I9000 rom on my captivate, thus forth being a possible source of my issue. Currently I have a phone that is stuck in a reboot loop any time I plug it into a power source, or attempt to power it on. While in said loop the phone will not go past the ATT logo, and as it cycles, at the I9000 screen a robot voice pops up saying restore system. Ive attempted to reflash back to stock with the stock captivate odin3 OCD, but I am having no luck with the phone being recognized by odin (run as admin). I am currently running Mac OSX 10.6 with windows vista on Virtual Box 4.0, and have had luck previously with flashing the phone back to stock after I decided to try new versions of cognition. Currently my phone can only go into download mode and not recovery due to the boot loop. please help asap, this my only means of communication with my family on the other side of the states
Try multiple USB ports/different computers if possible. I had a similar issue after flashing an i9000 rom. I could get into recovery but the power button wouldn't work for selections and in download mode my computer wouldn't recognize it. I just kept at it and eventually it worked.
CB650 Wolf said:
Try multiple USB ports/different computers if possible. I had a similar issue after flashing an i9000 rom. I could get into recovery but the power button wouldn't work for selections and in download mode my computer wouldn't recognize it. I just kept at it and eventually it worked.
Click to expand...
Click to collapse
going to try, redoing my virtual box in hopes that it was something stupid, and also trying the other usb port on my macbook.
Have you tried using a different cable? I had the same issue with a bad flash and Odin would not pick up my phone. If it did, it would nit complete the flash back to stock. I switched cables and it worked fine.
Sent from my SGH-I897 using XDA App
butchatbg said:
Have you tried using a different cable? I had the same issue with a bad flash and Odin would not pick up my phone. If it did, it would nit complete the flash back to stock. I switched cables and it worked fine.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
cable is fine considering I am still able to bring up the gadget serial on my virtual box with the phone.
s0n1cm0nk3y said:
cable is fine considering I am still able to bring up the gadget serial on my virtual box with the phone.
Click to expand...
Click to collapse
Try using ADB..
Edit...misread
rickysa2000 said:
Try using ADB..
Click to expand...
Click to collapse
sadly I wished that work, I tried using adb reboot recovery, and in the attempt, the phone was not able to be detected. Should this be done in hopes to catch it at the right time in the boot loop or in download mode. Ive tried both.
So can you still get into Download mode? If so I would suggest finding another computer to use. For some reason, last week, my PC that I have been using to flash for months decided not to recognize my phone in download mode.
So I switched to my laptop, loaded the ROM. I tried reinstalling drivers and all kinds of stuff but nothing worked. I backed up my PC and re-imaged it and it's working again.
Another person on here had to go and manually remove all references to the USB Driver and re-install it.
I would say just try re-installing (with the phone in DL Mode) the USB drivers with the phone plugged in and see what happens then. Hopefully the OS will detect the phone and you should be golden.
And that mechanical voice is voodoo... need to be careful what folders your deleting even if you are going to flash ODIN.
avgjoegeek said:
Another person on here had to go and manually remove all references to the USB Driver and re-install it.
I would say just try re-installing (with the phone in DL Mode) the USB drivers with the phone plugged in and see what happens then. Hopefully the OS will detect the phone and you should be golden.
And that mechanical voice is voodoo... need to be careful what folders your deleting even if you are going to flash ODIN.
Click to expand...
Click to collapse
Odd I was told your perfectly fine to do so, and then from there do an odin flash. Ive done it before, but oddly enough I think what screwed me was because I did it during while in the rom, vs while in 2.1. I just wanted to try to get a clean slate. doing the master clear code from samsung never really deletes the left overs from say clockwork and such on my internal sd.
problem was the virtual machine, plugged it into a friends computer and all was done within a couple of mins. leave it to emulation falling short :/
Hi
My brother (a no-geek) has a captivate, and lives in a different city (I donot have physical access to the phone). He visited me few weeks ago and I installed CM-7 on his phone, i know my bad. Some of his videos were not working, so i asked him to update to the latest CM-7 build. He download the build, saved it on int sd_card and used ClockWork Recovery to install the selected ROM. Upon reboot it entered in never-ending splash screen. I found couple of odin ROMs, and posted him link, we tried to flash them, but no good.
Status --
The COM ports are detected, but the process at times halts at <SET PARTITION> at times at <SET UP>... at times all thread completed successful would show up as soon as hitting START.
I dont have a captivate, can someone please suggest a sure shot solution and post me a link for ODIN, with a root rom. I am using Team Whiskey on my Vibrant, and I prefer stable modified ROM because of its features and power.
I can explain him the process on skype using desktop sharing, but the ROM should be good. Thankyou very much in advance.
if he can access recovery, try wiping everything thru recovery then start again
Phone is in Soft Brick state.
Phone is in Soft Brick state. So i cannot boot into the phone and go to CW recovery.
What he needs is just a stable usb connection that's how he got to this point, bad communication between the phone and computer. On cm7 I beleive you need the nexus s drivers installed. Also make sure it's plugged into a usb port that's attached directly to the motherboard (back of pc, port 1 on laptop)
@studacris
I think the drivers are already installed good. The connection is also good, as i can the COM port detection in the ODIN, with one of the boxes changing its colour from NO-COLOUR to YELLOW-COLOUR.
I think the ROM builds are not good. They go action-less during flashing, actually nothing (progress bar) comes on phone, it keeps showing the Downloading screen, endlessly. Odin usually is stuck at at <SET PARTITION> at times at <SET UP>...
Can someone post a link for a test one click odin. Well i would prefer one click.
You did try DG's JF6 one click, thats the only one I use, how are you establishing dowload mode on the phone or are you even doing this.
REMY4223 said:
I would suggest to Odin back to stock then update to Froyo via Kies.
Click to expand...
Click to collapse
if you could do all that, why would you need to send back for a new phone ? If you could do any of that, the OP wouldn't be in a non-functioning predicament
Ragin Caucasian said:
if you could do all that, why would you need to send back for a new phone ? If you could do any of that, the OP wouldn't be in a non-functioning predicament
Click to expand...
Click to collapse
+1 If you read the OP the problem is he can't flash back to stock he is having problems flashing anything period, @ the OP correct me if I'm wrong but I have a strong hunch that you are leaving out some pretty crucial steps, I have a feeling that you are not putting the phone into download mode, I also believe that you are gonna need to make a jig and pay a visit to your brother to help him out especially if its bricked the same way mine just was flashing with cm7 roms. But if you are getting a com port to show without having to put in download mode then you are farther along in the boot process. If this is the case you may be able to adb into recovery do a full wipe excluding /boot and reflash. Will the PC recognize the phone with it in its current boot locked state? If so then recovering should be somewhat of a breeze.
http://forum.xda-developers.com/showthread.php?t=829392 read this post it may help otherwise there are tons others
- I am getting to downloading mode by
--- pressing the "vol +" and "vol -" buttons and then connecting the usb cable to the computer.
--- then removing the cable, after the phone enters the download mode. Then, start the odin and connect the phone through usb cable again. The odin detects the phone on one of the COM port.
- I havent tired wiping the phone through recovery. But i need to get to recovery first. I dont know in a soft brick state if i can get into recovery.
- regarding getting back to 2.1... i would like to flash to the latest version. Kies update is not an option for me, as i not in US.
This phone was purchased from craiglist, i used one click root method to root it and the same script an option to get the unlock codes. After that i experimented a lot on the phone with various scripts. Last i was using congnition on it. Then saw CM7, i liked it on my vibrant, so i flashed it on my captivate (which i got for my brother). Now i have to get back to some stable modified ROM... I am thinking about trying Srendipity or cog ROM... but before than i have to install a rooted stock ROM.
That is the story and issue... but thanks a lot for help. Any more suggestions.
viveksharma2108 said:
- I am getting to downloading mode by
--- pressing the "vol +" and "vol -" buttons and then connecting the usb cable to the computer.
--- then removing the cable, after the phone enters the download mode. Then, start the odin and connect the phone through usb cable again. The odin detects the phone on one of the COM port.
- I havent tired wiping the phone through recovery. But i need to get to recovery first. I dont know in a soft brick state if i can get into recovery.
- regarding getting back to 2.1... i would like to flash to the latest version. Kies update is not an option for me, as i not in US.
This phone was purchased from craiglist, i used one click root method to root it and the same script an option to get the unlock codes. After that i experimented a lot on the phone with various scripts. Last i was using congnition on it. Then saw CM7, i liked it on my vibrant, so i flashed it on my captivate (which i got for my brother). Now i have to get back to some stable modified ROM... I am thinking about trying Srendipity or cog ROM... but before than i have to install a rooted stock ROM.
That is the story and issue... but thanks a lot for help. Any more suggestions.
Click to expand...
Click to collapse
Try putting the phone into download mode after you open Odin. Which version of Odin is this? Also, installing the nightly build of CM7 again often fixes the boot loop on the newer builds. I would try that if you can get to recovery.
Sent from my SGH-I897 using XDA Premium App
No firmware and USB problem
I have a large problem, my wifes galaxy s won't go by the first screen (says GALAXY S GT-I9000)
So i thought i'd fix it using odin using the 3 button combo. But that isn't working anymore.
Luckily i have a usb jig which gets me to the download mode ...... but !
When i connect the pc cable (tried 2 OE samsung ones) i get device not recognized so i can't use odin to fix it.
What can i do, or do i have to send it to a repair centre to be resurrected ?
I have searched and searched but not found any topics with the same issues i have on her phone.
Need a bit more info i.e were you flashing the phone??if so which rom?
Then phone was playing up so i flashed darkys 10.4.2.
However the usb connection wouldn't work so i flashed it to standard JVT
using mobile odin.
Then i rooted it and went to go into recovery mode and it wouldn't turn on.
I tried to help the gentleman , but no luck . From what he told me , phone turns on after battery insertion , and It is not recognised by usb => so odin not usable .
If you can get to download mode but the phone isn't recognized by your computer then i'd say it's a driver issue. Install your phone's drivers again. To do that, just installing kies is enough BUT be sure to open task manager in windows and kill any process that has kies in it's name before opening odin.
If that still isn't flying i'd try using different USB ports and even with a different computer.
Extra advice:
- try not to flash bootloaders for now. That means picking a rom that has no bootloaders included but matches your phone's current bootloader. If you were using gingerbread flash a gingerbread rom, if you were using froyo, flash a froyo rom.
phone not starting up past first screen (GALAXY S GT-I9000 in white on black screen), phone not recognized neither by pc nor laptop ( usb drivers installed ) , phone turns on after battery insertion without pressing anything.
This manual is from a German board
Take the battery out, then hold the 3 keys combo for download and put the battery back on. Now you should start the download mode.
If not, then try it with a jig.
Good luck!
GOT A JIG. WORKS FINE.
But pc wont recognize it !!
Have you double checked that you have the right drivers installed? I know you have to use the Nexus S drivers for CM9, not sure about Darky's ROM.
Drivers
Download drivers 64 bit | 32 bit from here and install.
It is NOT the drivers as my other galaxy s connects fine every time.
Drivers have been removed and installed repeatedly.
I would suggest a different computer, maybe a different cable. I have this same issue with my infuse, hope you get this resolved.
Sent from my Desire HD using XDA App
Already tried that as well
You could try Adam outler's unbrickable mod.
Pasted from other thread:
I just wrote a wall of text b4 and my browser crashed GG
Well, here we go again, i will only tell what I did/the process
I did a nandroidbackup, then i wiped all data (data+cache+dalvik), installed CyanogenMod 9 (Build 16), it rebooted automaticly, so I entered recovery again, installed Google Apps from there, wiped data and cache (no dalvik), rebooted.
Ended up looping at the Samsung screen (not animation), and I couldnt do the 3-button-combo, so the NANDroid backup is useless.
I can enter the download thing, but i dont even know what it does.
Tried plugging it in the charger (after letting it dry out during the night), and only the loop thing appears. Cant do anything.
I see that theres something called odin (Since my download thing is working (VolDown+Home+Power) if its that you mean.
If its possible to fix my phones state, please tell me how, since I startedrooting, flashing and stuff yesterday (Gotta start at some point) and followed HDTechVideos tut (On his website)
woolf clubs said:
You could try Adam outler's unbrickable mod.
Click to expand...
Click to collapse
I have nowhere near enough ability for that. Pity though.
Your problem is most likely the USB port. Maybe cleaning it might help. It happened to me for a few months then when I got the S2 I stopped using it. Began to use it as my home 3g wifi modem and kept it on charge the whole time. A few weeks later tried connecting it to the computer and it worked first go. Ever since it has worked perferctly. I suspect the problem possibly started by a rain drop getting into the port.
Mind you, even when it wasn't being recognised by the PC, I would constantly connect, remove, reconnect, reboot PC and phone etc and it would sometimes get recognised. Other times it wouldn't connect but Odin still recognised it.
Sounds silly but try leaving it on charge as I did and maybe, just maybe you'll be lucky like I was.
Sent from my GT-I9100T
Well as of today it is away to the O2 repair centre.
Its under warranty (unless the find out it was rooted etc) so fingers crossed.
Well had a text back today to say my phone has been despatched, so here is hoping that its fixed.
It came back from the repair centre yesterday with a note saying a part had been replaced,
no costs for me, yippeeeeeeee.
I had Android 4.0.3 (IceCream Sandwich) on my Galaxy S GT-I9000B (I did install it through Odin, nothing went wrong), but is was laggish (too much for it to handle, I think) and after a few months, I decided to roll it back to 2.3.3 (Gingerbread).
I started the process to install the firmware through Odin3 v1.85 - the file I download (from sammobile.com/firmware, had only one file that I used on the PDA space.
Odin recognized my phone and I started to install it, but after a while my phone was stuck on the downloading screen (2 hours of installation, I tought that something went wrong).
I then turned my phone off to try and install again, but when I turned it on, there were a Phone - exclamation mark - Computer Symbol.
I can get it to dowlonad mode (Volume Down+Home+Power), but when I plug it to the pc, it says "unknown device" and it can't find drivers for it.
I think I have the latest drivers from Samsung (I had from Kies and I re-downloaded a file somewhere from this forum named SAMSUNG_USB_Driver_for_Mobile_Phones_1_5_6_0.exe).
It appears that since windows can't install the drivers, Odin doesn't recognize the device - it was recognizing it before, when I was installing the firmware.
Now I'm stuck - I tried anything I saw in this forum and in other places - I did even pray for a miracle, but it didn't work
I know that there must be a way, but I don't know how.
Before I forget, I'm using Windows 7 Ultimate x64.
If you can get it in download mode everything should be fine, I've had a problem like this, my pc couldn't see the phone in download no matter what. Try to use another USB port, better another PC. Also I've heard that x64 doesn't get along well with Odin. If possible you can try Linux and Heimdall, after all Android is Linux too.
KainFromNod said:
I know that there must be a way, but I don't know how. Before I forget, I'm using Windows 7 Ultimate x64.
Click to expand...
Click to collapse
Ok, k4Z3666, has given you a starting point...the phone is still in download mode but without a booting ROM, so its OK, the problem is your PC, USB cable or USB port. If you want to be quick about it, just try on a lap top..if not a simple Reboot of PC ( after removing power cord) and Phone (after a battery Pull), and a switch to a different USB port at the back of PC can solve this for some...for other solutions try these http://forum.xda-developers.com/showpost.php?p=27205737&postcount=4571 anything else you may need can be found on My Android collections., link below
k4Z3666 said:
If you can get it in download mode everything should be fine, I've had a problem like this, my pc couldn't see the phone in download no matter what. Try to use another USB port, better another PC. Also I've heard that x64 doesn't get along well with Odin. If possible you can try Linux and Heimdall, after all Android is Linux too.
Click to expand...
Click to collapse
I tried other USB Ports and also rebooting. It was working just fine - it seems like a driver problem to me.
My notebook is dead, but I'll try using someone else computer.
Does Odin runs in Windows XP? I might try it in my virtual box - I doubt that it will work, but it is the best thing I have to do untill tomorrow.
I got it working in my mother's notebook - should I try something different? I only have the PDA, should I try a PIT?
I don't know what those do, but I read somewhere that PIT is used to recover bricked phones.
EDIT: I installed only the PDA, it worked fine on the 2nd time (first time, it got stuck but I could make it work changing the usb port and cable).
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
KainFromNod said:
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
what ROM did you use? Did you do any wipes?
Opps..you got an i900B, so make sure you are only using I9000B ROMS as i9000 is not compatible with your phone
Follow guidelines from here
http://forum.xda-developers.com/showthread.php?t=919219
http://forum.xda-developers.com/showpost.php?p=22941192&postcount=300
KainFromNod said:
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
Assuming that you're on the right rom for your phone can you enter recovery mode? Try reinserting battery, and enter recovery with [vol+, menu button, power on]
KainFromNod said:
I got it working in my mother's notebook - should I try something different? I only have the PDA, should I try a PIT?
I don't know what those do, but I read somewhere that PIT is used to recover bricked phones.
EDIT: I installed only the PDA, it worked fine on the 2nd time (first time, it got stuck but I could make it work changing the usb port and cable).
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
Yep if u want to back to stock u need pit file because ICS use different system file
Why u don't like ICS ? Its way better and faster than sammy ROM even its more stable , I think u should try it again with devil kernel with oc to 1.2 it will fly u can add some live oc which will give more fluidity
Sent from another galaxy powered by CM10 & Syiah
Ok, I'm posting it here just to leave a reply and reference for future generations, as my problem was solved.
xsenman said:
what ROM did you use? Did you do any wipes?
Opps..you got an i900B, so make sure you are only using I9000B ROMS as i9000 is not compatible with your phone
I used a firmware from my country (available here: sammobile.com/firmware/?page=3&model=GT-I9000B&pcode=ZTO&os=1&type=1#firmware) and I wiped the cache (I'm not sure what this means, but I believe it is the 2 options on volume up+menu+power)
Follow guidelines from here
http://forum.xda-developers.com/showthread.php?t=919219
http://forum.xda-developers.com/showpost.php?p=22941192&postcount=300
Click to expand...
Click to collapse
k4Z3666 said:
Assuming that you're on the right rom for your phone can you enter recovery mode? Try reinserting battery, and enter recovery with [vol+, menu button, power on]
Click to expand...
Click to collapse
I was entering recovery mode, but it was giving me some error when I tried to wipe the 2 things that I forgot the name =/
yahyoh said:
Yep if u want to back to stock u need pit file because ICS use different system file
Why u don't like ICS ? Its way better and faster than sammy ROM even its more stable , I think u should try it again with devil kernel with oc to 1.2 it will fly u can add some live oc which will give more fluidity
Sent from another galaxy powered by CM10 & Syiah
Click to expand...
Click to collapse
ICS wasn't faster here - it was laggish and always crashed some common apps (gallery, music player). I believe that the firmware wasn't completely "done" as it was being adapted from another version (my phone is brazilian) and some functionalities that it has (i.e. digital TV) wasn't available.
What I done to correct the boot was simple (I found a tutorial in a brazilian site, so it had all the roms that I needed).
1) Used a PIT and a stock rom to get it back to factory version;
2) Upgraded to Froyo (original) - That was kind of a mistake, the tutorial said to do it because then KIES would update it automatically to Gingerbread. The phone was fully functional, but KIES said that it couldn't update it (it recognized the phone and everything).
The tutorial stoped there, but since I had the ROM, I used Odin to install Gingerbread (the one that was looping) and it was done.
Now I need to remember how to root it because there are some dumb apps who can't get away (i.e. Orkut app, some demo games).
Thank you all for the help!
KainFromNod said:
I was entering recovery mode, but it was giving me some error when I tried to wipe the 2 things that I forgot the name =/
Click to expand...
Click to collapse
From recovery you can always try to flash another kernel, that would probably resolve things too. Anyways the problem's solved, glad to help
First of all, i'm new here, so if I make a mistake, no hate please.
So I was trying to install Xbean onto my Galaxy S GT-I9000.
This phone has a broken USB port, and as such, I had to root and flash Clockwordmod Recovery mod onto it without a computer. I managed to get into CWM Recovery and went to flash the Xbean.zip file I had on the internal SD card, and when I did, it lasted maybe 3 seconds, then turned off and back on. It's now hanging at the "Galaxy S GT-I9000" first boot screen. For some reason, the 3 button combo doesn't work for either recovery or download.
Anyone have any ideas on how I can fix this issue?
P.s. I have already taken the battery out and placed it back in multiple times.
same here. I have a galaxy s I9000 with a broken usb port and I can get into download mode but no recovery. because of the usb port can not use odin. searched a lot but I could not find a solution. without odin it seems it is not possible to fix the phone. One repair center guy told me that there is a chip or something on the motherboard that regulates the usb connection. that thing is damaged because of imporperly charging. I have a bricked phone.(though I have still download mode)
both of u. if ur on GB. n u success to boot to recovery before da problem occur, u need to flash cm9 stable first to gain da cwm not direct custom ROM. then first flash will bootloop. juz take out battery, n use 3 combo button to go back to recovery again. its da matter of releasing da combo button. release it RIGHT AFTER u see da first bootsplash n wait. if failed. try again. n if it still fail. it means da kernel doesnt even flashed inside system.so u need to flash back to firmware using odin.
note: first flash will install cwm n kernel only as upgrading partition.
second flash will install da ROM.
try to boot to recovery again.
Sent from my GT-I9000 using xda app-developers app
RenegadeTe said:
First of all, i'm new here, so if I make a mistake, no hate please.
So I was trying to install Xbean onto my Galaxy S GT-I9000.
This phone has a broken USB port, and as such, I had to root and flash Clockwordmod Recovery mod onto it without a computer. I managed to get into CWM Recovery and went to flash the Xbean.zip file I had on the internal SD card, and when I did, it lasted maybe 3 seconds, then turned off and back on. It's now hanging at the "Galaxy S GT-I9000" first boot screen. For some reason, the 3 button combo doesn't work for either recovery or download.
Anyone have any ideas on how I can fix this issue?
P.s. I have already taken the battery out and placed it back in multiple times.
Click to expand...
Click to collapse
Usually the way to fix this would be to use the adb shell to force download mode, or using a USB jig to go back to stock. However neither of them would work because you have a broken USB port... :/
durkaya said:
same here. I have a galaxy s I9000 with a broken usb port and I can get into download mode but no recovery. because of the usb port can not use odin. searched a lot but I could not find a solution. without odin it seems it is not possible to fix the phone. One repair center guy told me that there is a chip or something on the motherboard that regulates the usb connection. that thing is damaged because of imporperly charging. I have a bricked phone.(though I have still download mode)
Click to expand...
Click to collapse
Again, best way to do this would be to use download mode and flash in a stock rom. Bu tif the USB port is broken... :/
I think the only thing you guys can do would be to get the USB port repaired somehow. Most methods (although do try @compacity's method, it may work) rely on the USB port and a USB connection.
Sent from my GT-P7510 using Tapatalk HD
was struggling with the same problem for 2 weeks until I had to give up and send it in.
In my case though, it was not like the support guy said a broken chip but abrasion of the connector in the middle of the USB Port. Obviously plugged it in too often.
Sent it to W-Support, they replaced the small plate in the middle of the connector and everything is working nicely again. So probably a piece of hope for you that maybe some support can still revive your phone. Unfortunately afaik there is no way to recover it w/o reflashing. Was within warranty so no clue what the price would be.
Some people are reporting that removing the battery for like one night made the bootloop disappear.. desperate times etc. wo why not give it a shot
Soryuu said:
Usually the way to fix this would be to use the adb shell to force download mode, or using a USB jig to go back to stock. However neither of them would work because you have a broken USB port... :/
Again, best way to do this would be to use download mode and flash in a stock rom. Bu tif the USB port is broken... :/
I think the only thing you guys can do would be to get the USB port repaired somehow. Most methods (although do try @compacity's method, it may work) rely on the USB port and a USB connection.
Sent from my GT-P7510 using Tapatalk HD
Click to expand...
Click to collapse
As I said before donwload mode is ok but conection can not be done due to broken usb port (even after fixing the usb port two times). So I guess there is something wrong with the main board. Anyway thanks to all...May be if there is a way to boot from an external sd (like installing ubuntu from usb stick) if not I have dead phone....