Database Info

[Q] Nexus 5 stuck at boot, "google screen", will not flash anything

I am trying to fix my bootlooped nexus 5, but I can't flash any factory images, and factory resetting my phone does nothing. I have tried flashing roms directly from my recovery, but that doesn't work either. NOTHING IS WORKING. PLEASE HELP.
Snippet of log from flash-all batch:
Code:
flash-all
target reported max download size of 1073741824 bytes
sending 'bootloader' (2579 KB)...
OKAY [ 0.208s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.414s
rebooting into bootloader...
OKAY [ 0.088s]
finished. total time: 0.089s
< waiting for device >
target reported max download size of 1073741824 bytes
sending 'radio' (45521 KB)...
OKAY [ 1.573s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.804s
rebooting into bootloader...
OKAY [ 0.079s]
finished. total time: 0.082s
< waiting for device >
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
Cannot read image.
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
--------------------------------------------
Bootloader Version...: HHZ12d
Baseband Version.....: M8974A-2.0.50.2.22
Serial Number........: 03760f5f43803fbf
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.097s]
checking version-baseband...
OKAY [ 0.097s]
sending 'boot' (8852 KB)...
OKAY [ 0.497s]
writing 'boot'...
OKAY [ 0.742s]
sending 'recovery' (9552 KB)...
OKAY [ 0.553s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 2.592s
Press any key to exit...

same situation here if solmeone can help us...

bhlam2 said:
I am trying to fix my bootlooped nexus 5, but I can't flash any factory images, and factory resetting my phone does nothing. I have tried flashing roms directly from my recovery, but that doesn't work either. NOTHING IS WORKING. PLEASE HELP.
Snippet of log from flash-all batch:
Click to expand...
Click to collapse
wil123 said:
same situation here if solmeone can help us...
Click to expand...
Click to collapse
Don't use the flash-all script.
Use the Method 2 from the first post at http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Edit: read the first post completely before you do anything

/cache and /sdcard can't mount

So my phone recently had problems with the power button, and I decided to take it to a phone repair shop and they fixed it. However, now I'm having problems with a bootloop that I can't figure out.
I was running the Android M developer preview. I have tried many times to flash the 5.1.1 factory image, but it fails every time. It comes up with a writing failure for each part of the image (system, bootloader, recovery, etc.). I can go into fastboot and recovery mode, but in recovery I can not do anything, as it cannot mount the /cache and /sdcard... I tried formatting the cache many times, and it just doesn't seem to be helping...
Does anyone have any insight on how to get this to work?
I execute the flash-all.bat and this is what I get
C:\Users\reiga_000\Desktop\hammerhead-lmy48b>fastboot devices
041eda5e251e9726 fastboot
C:\Users\reiga_000\Desktop\hammerhead-lmy48b>flash-all.bat
target reported max download size of 1073741824 bytes
sending 'bootloader' (3119 KB)...
OKAY [ 0.313s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.531s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.578s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.828s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.031s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
--------------------------------------------
Bootloader Version...: HHZ12h
Baseband Version.....: M8974A-2.0.50.2.26
Serial Number........: 041eda5e251e9726
--------------------------------------------
checking product...
OKAY [ 0.110s]
checking version-bootloader...
OKAY [ 0.094s]
checking version-baseband...
OKAY [ 0.094s]
sending 'boot' (8980 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.750s]
sending 'recovery' (9696 KB)...
OKAY [ 0.547s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 2.625s
Press any key to exit...
Click to expand...
Click to collapse

My phone stopped working all of the sudden

Hello,
Yesterday around midnight my phone suddenly stopped working. I wasn't using it, it was just sitting on my desk and had been for at least half an hour.
When I boot it, it stays stuck on the boot animation.
Until yesterday it was running a custom built version of CM12.1 (from this thread: http://forum.xda-developers.com/goo...unofficial-cm12-cmhammerhead-nexus-5-t2938502)
With a ElementalX-N5-4.09 kernel.
I tried:
Reflashing the ROM
Wiping and Reflashing the ROM
Wiping and Reflashing the ROM, without ElementalX
Wiping and Flashing an older version
Wiping and formating of user data too + Reflashing
complete reset by doing fastboot oem lock/unlock
flashing of the factory image of Android 6
Each time the result is the same.
When the phone was still running cyanogen I had adb while it was booting (that's no longer the case) and I saw nothing striking ... it would have one (pc) screen worth of log (logcat) and then nothing it would just stop.
I couldn't spot anything in kernel logs either (dmesg/last_kmsg).
The recovery is working fine ... I was able to start an ssh server and use it... it's just android that won't boot...
any idea to turn my expensive paperweight back into a phone?

*Update*
I flashed Ubuntu touch and it's working fine.. flashed back Android and it's been showing me the boot animation for 30 minutes now...

After flashing stock ROM, are you erasing userdata and flashing userdata.img?

I've been using the flash-all.sh script so yes.
Here is the output after flashing LMY48M (5.1.1):
Code:
[email protected]:/.../hammerhead-lmy48m$ ./flash-all.sh
target reported max download size of 1073741824 bytes
sending 'bootloader' (3119 KB)...
OKAY [ 0.319s]
writing 'bootloader'...
OKAY [ 0.533s]
finished. total time: 0.852s
rebooting into bootloader...
OKAY [ 0.134s]
finished. total time: 0.134s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.711s]
writing 'radio'...
OKAY [ 3.111s]
finished. total time: 4.823s
rebooting into bootloader...
OKAY [ 0.137s]
finished. total time: 0.137s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12h
Baseband Version.....: M8974A-2.0.50.2.26
Serial Number........: ****************
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8916 KB)...
OKAY [ 0.510s]
writing 'boot'...
OKAY [ 0.757s]
sending 'recovery' (9632 KB)...
OKAY [ 0.554s]
writing 'recovery'...
OKAY [ 0.807s]
erasing 'system'...
OKAY [ 1.053s]
sending 'system' (1021824 KB)...
OKAY [ 33.345s]
writing 'system'...
OKAY [ 68.316s]
erasing 'userdata'...
OKAY [ 6.439s]
[COLOR="Teal"]formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
sending 'userdata' (137318 KB)...
writing 'userdata'...
OKAY [ 14.056s][/COLOR]
erasing 'cache'...
OKAY [ 0.548s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 1.982s]
rebooting...
finished. total time: 129.192s

After using the script, try booting into stock recovery and performing another factory wipe of data and cache.
Or, before the first boot, try erasing and reflash img userdata.img file, boot into recovery, wipe again, and boot.

I tried that and it didn't work ...
However ... I flashed a kitkat factory image (4.4.4 KTU84P to be precise) ... and it works ...
Tomorow I'll try 6.0 again.

Still not much progress.
Kitkat is working but with no service ...
In kernel logs I can see this kind of things:
Code:
<3>[ 24.333162] pil-q6v5-mss fc880000.qcom,mss: mba: Failed to locate mba.mdt
<3>[ 24.333211] smd_pkt_open failed on smd_pkt_dev id:0 - subsystem_get failed for modem
<3>[ 44.848682] pil-q6v5-mss fc880000.qcom,mss: mba: Failed to locate mba.mdt
<3>[ 44.848937] smd_pkt_open failed on smd_pkt_dev id:0 - subsystem_get failed for modem
but I have no connectivity issue in ubuntu.
Also I noticed the hardware clock is set to 1970. I though this may be an issue.
I tried to set it to the correct date but it won't work:
Code:
localhost / # hwclock -w
hwclock: RTC_SET_TIME: Invalid argument
I tried this on a galaxy nexus and the hwclock is set at the correct date/time and the hwclock -w command works.

f4kill said:
Still not much progress.
Kitkat is working but with no service ...
In kernel logs I can see this kind of things:
Code:
<3>[ 24.333162] pil-q6v5-mss fc880000.qcom,mss: mba: Failed to locate mba.mdt
<3>[ 24.333211] smd_pkt_open failed on smd_pkt_dev id:0 - subsystem_get failed for modem
<3>[ 44.848682] pil-q6v5-mss fc880000.qcom,mss: mba: Failed to locate mba.mdt
<3>[ 44.848937] smd_pkt_open failed on smd_pkt_dev id:0 - subsystem_get failed for modem
but I have no connectivity issue in ubuntu.
Also I noticed the hardware clock is set to 1970. I though this may be an issue.
I tried to set it to the correct date but it won't work:
Code:
localhost / # hwclock -w
hwclock: RTC_SET_TIME: Invalid argument
I tried this on a galaxy nexus and the hwclock is set at the correct date/time and the hwclock -w command works.
Click to expand...
Click to collapse
Seems to me you now own an Ubuntu Phone. :silly:
Are you on the latest bootloader? I have a silly idea but it just might work. Install multiROM on your phone and try to install a custom stock based marshmallow rom, either as a primary or as a secondary. Good luck!

I had a nexus 5 with a broken screen, I salvaged the motherboard and now have a fully functional nexus in my pocket.
I also salvaged the camera because it was doing slightly better shots.
The second phone has a broken screen but still working so it would be nice to have it run android too
However I wanted to turn it into a small server, and had already done so with a chroot trick ... but now I'm thinking Ubuntu touch might be better suited for that
I might try tge multiROM option but I'm not too optimistic about it.
btw the hwclock thing was nothing, the other n5 had its clock in 1970 too and the same error.

Nexus 5 D820(H) hang on marshmallow logo try to flash give error plz help

see report
Code:
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.297s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.500s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
< waiting for device >
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.578s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 1.672s
rebooting into bootloader...
OKAY [ 0.063s]
finished. total time: 0.063s
< waiting for device >
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
Cannot read image.
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
--------------------------------------------
Bootloader Version...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.28
Serial Number........: 04ac884b0a74a859
--------------------------------------------
checking product...
OKAY [ 0.094s]
checking version-bootloader...
FAILED
Device version-bootloader is 'HHZ12k'.
Update requires 'HHZ20f'.
finished. total time: 0.500s
Press any key to exit...
try to update bootloader give error
Code:
C:\Documents and Settings\Miss my love\Desktop\fastboot_MOB30H>fastboot oem unlo
ck
...
OKAY [ 4.859s]
finished. total time: 4.859s
C:\Documents and Settings\Miss my love\Desktop\fastboot_MOB30H>fastboot flash bo
otloader bootloader-hammerhead-hhz20f.img
sending 'bootloader' (3120 KB)...
OKAY [ 0.203s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.406s
C:\Documents and Settings\Miss my love\Desktop\fastboot_MOB30H>
try to flash this file
hammerhead-mob30h-factory-66d165e6
or
BIN_LGD820AT-00-V10d-NXS-XX-DEC-11-2013-KOT49H-USER-16G
but not success plz guide me
how to solved

Is the bootloader unlocked? Does it stay unlocked after rebooting into fastboot?

...i have the same issue, now i am looking for a working mainboard.... i think that you have emmc failure, your flash memory is dead and there is no software solution... sorry man...

audit13 said:
Is the bootloader unlocked? Does it stay unlocked after rebooting into fastboot?
Click to expand...
Click to collapse
no after reboot again lock
it's me EMMC chip problem ..?

Umm try flashing Twrp and then a custom rom!
Unlock ur bootloader 1st then flash twrp...

If the bootloader locks itself when the phone is rebooted, the emmc is damaged or defective.

Not being able to install ROM LOS 17. 1, stuck in TWRP

HI All , I need some help . Since I did manage to get a new battery for my broken n5, I decided to get onboarded with LOS17.1 .
Managed to get the 3.4 TWRP HH from @z3DD3r and followed the repartition process. However I am not able to enable adb, nor can I abd sideload , everytime I try to sideload I get an error 7.
Furthermore I cannot mount data partition , nor does the OTG cable work i.e. nothing comes up in my comp. I did install Google drivers / CWM USB drivers, and I do see Google nexus ADB interface popping up in the device manager(win10) however nothing gets listed as a storage/MTP device. I did try searching but not being able to get the solution . I am not able to move beyond this .
N5 doesnt have a sdcard slot either . Can any one advise how to get the LOS zip and gaps into the storage ? Only thing which is working is TWRP HH recovery from @z3DD3r. I will appreciate any help . Let me know if I need to post this in another thread. Thank you

I am not able to mount /cache and /system - it says failed when I wipe or format them .
I only have /data which can be mounted . I have searched and have seen that its to do with partition tables. Any way to get back the partition table done ?
I have checked the following links -
https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
and
https://forum.xda-developers.com/go...o-repairing-corrupted-data-partition-t2577447

quest2012 said:
I am not able to mount /cache and /system - it says failed when I wipe or format them .
(...)
Click to expand...
Click to collapse
Wipe -> Advanced Wipe -> Check "Cache" -> Repair or Change File System -> Repair File System
If that doesn't help, do it:
Wipe -> Advanced Wipe -> Check "Cache" -> Repair or Change File System -> Change File System
If your cache partition does not have ext4, set ext4.
If your cache has ext4, change it to FAT and restore it to ext4 when finished.
If something succeeds, repeat the steps for the system partition.
Good luck with the repair. :good:

Did You manage to find the solution?

Thanks , however with TWRP I get error 16 unable to repair system , same thing with cache , neither can I change the filesystem , since I think the partitions dont exist

Enteb27 said:
Did You manage to find the solution?
Click to expand...
Click to collapse
Nope, need a way to repartition as per stock .

I tried looking into various places and used the following site to get into the partition table using parted .
https://iwf1.com/how-to-re-partitio...ll-options-included-change-size-fs-type-etc/2
I followed instructions and found that cache, crypto and system partition were missing . Created the partitions and also managed to change the fs for two of them .
I referred to this page as well to know what partitions are available and what are their usual sizes.
https://forum.xda-developers.com/go...guide-repartition-nexus5-to-increase-t3509880
After all - I did a flash-all , it went through luckily . However somehow I am stuck in bootloop. Then I tried flashing twrp again , and my partitions are gone . Parted doesnt recognize my disk at all .
So close by yet so far
Log of flash all -
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.308s]
writing 'bootloader'...
OKAY [ 0.518s]
finished. total time: 0.830s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.012s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 2.036s]
writing 'radio'...
OKAY [ 3.126s]
finished. total time: 5.165s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.005s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 29146718208
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7115898
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1782368 inodes and 155902/7115898 blocks
Creating filesystem with parameters:
Size: 769654784
Block size: 4096
Blocks per group: 32768
Inodes per group: 7840
Inode size: 256
Journal blocks: 2936
Label:
Blocks: 187904
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/47040 inodes and 6087/187904 blocks
--------------------------------------------
Bootloader Version...: HHZ20h
Baseband Version.....: M8974A-2.0.50.2.30
Serial Number........: 0c35d79d02
--------------------------------------------
checking product...
OKAY [ 0.099s]
checking version-bootloader...
OKAY [ 0.099s]
checking version-baseband...
OKAY [ 0.099s]
sending 'boot' (9156 KB)...
OKAY [ 0.509s]
writing 'boot'...
OKAY [ 0.778s]
sending 'recovery' (10014 KB)...
OKAY [ 0.576s]
writing 'recovery'...
OKAY [ 0.828s]
erasing 'system'...
OKAY [ 1.486s]
sending 'system' (1020657 KB)...
OKAY [ 33.072s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 81.015s
Press any key to exit...

Finally managed to get into and redo parted , changed user fs to ext4. Ran flash all - boot.sig, recovery.sig, vendor img missing , however it ran successfully .
Tried to reboot , it booted up but got stuck at boot , the android 6 factory boot animation came up , but got stuck and switched off . Any workaround ?

Went into parted again - removed userdata partition and redid i.e. made a partition and changed the filesystem to ext4, then came out and flash-all stock , stuck in bootloop , is there any problem with the installation ?
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
OKAY [ 0.522s]
finished. total time: 0.832s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.017s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 1.630s]
writing 'radio'...
OKAY [ 3.129s]
finished. total time: 4.764s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.012s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 29146718208
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7115898
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1782368 inodes and 155902/7115898 blocks
Creating filesystem with parameters:
Size: 769654784
Block size: 4096
Blocks per group: 32768
Inodes per group: 7840
Inode size: 256
Journal blocks: 2936
Label:
Blocks: 187904
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/47040 inodes and 6087/187904 blocks
--------------------------------------------
Bootloader Version...: HHZ20h
Baseband Version.....: M8974A-2.0.50.2.30
Serial Number........: 0c35d79d02ba
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.097s]
checking version-baseband...
OKAY [ 0.097s]
sending 'boot' (9156 KB)...
OKAY [ 0.518s]
writing 'boot'...
OKAY [ 0.783s]
sending 'recovery' (10014 KB)...
OKAY [ 0.580s]
writing 'recovery'...
OKAY [ 0.823s]
erasing 'system'...
OKAY [ 1.433s]
sending 'system' (1020657 KB)...
OKAY [ 33.932s]
writing 'system'...
OKAY [ 68.950s]
erasing 'userdata'...
OKAY [ 13.845s]
sending 'userdata' (139105 KB)...
OKAY [ 4.599s]
writing 'userdata'...
OKAY [ 9.379s]
erasing 'cache'...
OKAY [ 0.668s]
sending 'cache' (13984 KB)...
OKAY [ 0.659s]
writing 'cache'...
OKAY [ 1.111s]
rebooting...
finished. total time: 138.050s
Press any key to exit...

Finally got all partitions working, being able to wipe all partitions through twrp.
All partitions are mounting
Factory image not booting, so trying crdroid 7.1.2
Installs pretty quickly the 350mb file.
However stuck with Google logo, not moving to the boot animation.
Any help will be appreciated.

Need to check power button , since that is also another issues which N5 users have faced and boot loop or getting stuck at boot solution has been replacing the power button/ switch

Closing the thread - Motherboard issue , thanks everyone for your help.