[SOLVED] fastboot: "FAILED (remote: Write Fail)" - Samsung Galaxy Nexus

I've never experienced the fastboot error below and I am not sure about how to proceed.
The error is on the third to last line.
I am attempting to flash the Google factory image: yakju-jwr66y-factory-09207065
to my maguro.
Code:
sending 'bootloader' (2308 KB)...
OKAY [ 0.224s]
writing 'bootloader'...
OKAY [ 0.290s]
finished. total time: 0.518s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: 0149BD310A01D011
--------------------------------------------
checking product...
OKAY [ 0.008s]
sending 'boot' (4376 KB)...
OKAY [ 0.416s]
writing 'boot'...
OKAY [ 0.526s]
sending 'recovery' (4924 KB)...
OKAY [ 0.468s]
writing 'recovery'...
OKAY [ 0.600s]
erasing 'system'...
OKAY [ 0.018s]
sending 'system' (479248 KB)...
OKAY [ 44.424s]
writing 'system'...
[B][COLOR="Red"]FAILED (remote: Write Fail)[/COLOR][/B]
finished. total time: 46.532s
Press any key to exit...
Edit:
I locked and then unlocked the bootloader and re-downloaded and verified the factory image before flashing. After doing this I was able to successfully flash the factory image.

Related

[Q]

Dear all,
I had problems with Lollipop and therefore, decided to go back to kitkat.
I tried to flash the Razor version 4.3 (JSS15Q):
sending 'bootloader' (3911 KB)...
OKAY [ 0.206s]
writing 'bootloader'...
OKAY [ 1.425s]
finished. total time: 1.631s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.15
Baseband Version.....: none
Serial Number........: 08f243ea
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (6880 KB)...
OKAY [ 0.317s]
writing 'boot'...
OKAY [ 0.377s]
sending 'recovery' (7424 KB)...
OKAY [ 0.358s]
writing 'recovery'...
OKAY [ 0.283s]
sending 'system' (603447 KB)...
OKAY [ 22.106s]
writing 'system'...
OKAY [ 26.637s]
erasing 'userdata'...
OKAY [ 20.993s]
erasing 'cache'...
OKAY [ 0.446s]
rebooting...
The tablet started and stalled @ the starting screen (a cross?).
As the system would not progress, I tried another version:
4.4.4 (KTU84P)
sending 'bootloader' (3911 KB)...
OKAY [ 0.159s]
writing 'bootloader'...
OKAY [ 1.543s]
finished. total time: 1.702s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.04
Baseband Version.....: none
Serial Number........: 08f243ea
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7182 KB)...
OKAY [ 0.287s]
writing 'boot'...
OKAY [ 0.357s]
sending 'recovery' (7768 KB)...
OKAY [ 0.304s]
writing 'recovery'...
OKAY [ 0.299s]
sending 'system' (799293 KB)...
OKAY [ 26.031s]
writing 'system'...
OKAY [ 36.367s]
erasing 'userdata'...
OKAY [ 23.253s]
erasing 'cache'...
OKAY [ 0.489s]
rebooting...
Again, the system stalled @ the starting screen for Kitkat 4.4.4 (flying balls, if I am not wrong) ... Finally, I tried to go back to Lollipop 5.0.2 (LRX22G)
< waiting for device >
sending 'bootloader' (3911 KB)...
OKAY [ 0.159s]
writing 'bootloader'...
OKAY [ 1.364s]
finished. total time: 1.523s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 08f243ea
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7050 KB)...
OKAY [ 0.281s]
writing 'boot'...
OKAY [ 0.360s]
sending 'recovery' (7598 KB)...
OKAY [ 0.301s]
writing 'recovery'...
OKAY [ 0.297s]
sending 'system' (736772 KB)...
OKAY [ 24.134s]
writing 'system'...
OKAY [ 32.387s]
erasing 'userdata'...
OKAY [ 20.154s]
erasing 'cache'...
OKAY [ 0.426s]
rebooting...
finished. total time: 78.366s
The system again stalls at the start screen (four collored dots, yellow, red, green and blue).
Please, observe that in all cases I received the messages:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
Would be this the problem? Am I doing something wrong during the flashing process?
Thank you for your help
Cheers,
Eduardo

[Q] Problems while flashing Firmware

Dear all,
I had problems with Lollipop and therefore, decided to go back to kitkat.
I tried to flash the Razor version 4.3 (JSS15Q):
sending 'bootloader' (3911 KB)...
OKAY [ 0.206s]
writing 'bootloader'...
OKAY [ 1.425s]
finished. total time: 1.631s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.15
Baseband Version.....: none
Serial Number........: 08f243ea
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (6880 KB)...
OKAY [ 0.317s]
writing 'boot'...
OKAY [ 0.377s]
sending 'recovery' (7424 KB)...
OKAY [ 0.358s]
writing 'recovery'...
OKAY [ 0.283s]
sending 'system' (603447 KB)...
OKAY [ 22.106s]
writing 'system'...
OKAY [ 26.637s]
erasing 'userdata'...
OKAY [ 20.993s]
erasing 'cache'...
OKAY [ 0.446s]
rebooting...
The tablet started and stalled @ the starting screen (a cross?).
As the system would not progress, I tried another version:
4.4.4 (KTU84P)
sending 'bootloader' (3911 KB)...
OKAY [ 0.159s]
writing 'bootloader'...
OKAY [ 1.543s]
finished. total time: 1.702s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.04
Baseband Version.....: none
Serial Number........: 08f243ea
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7182 KB)...
OKAY [ 0.287s]
writing 'boot'...
OKAY [ 0.357s]
sending 'recovery' (7768 KB)...
OKAY [ 0.304s]
writing 'recovery'...
OKAY [ 0.299s]
sending 'system' (799293 KB)...
OKAY [ 26.031s]
writing 'system'...
OKAY [ 36.367s]
erasing 'userdata'...
OKAY [ 23.253s]
erasing 'cache'...
OKAY [ 0.489s]
rebooting...
Again, the system stalled @ the starting screen for Kitkat 4.4.4 (flying balls, if I am not wrong) ... Finally, I tried to go back to Lollipop 5.0.2 (LRX22G)
< waiting for device >
sending 'bootloader' (3911 KB)...
OKAY [ 0.159s]
writing 'bootloader'...
OKAY [ 1.364s]
finished. total time: 1.523s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 08f243ea
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7050 KB)...
OKAY [ 0.281s]
writing 'boot'...
OKAY [ 0.360s]
sending 'recovery' (7598 KB)...
OKAY [ 0.301s]
writing 'recovery'...
OKAY [ 0.297s]
sending 'system' (736772 KB)...
OKAY [ 24.134s]
writing 'system'...
OKAY [ 32.387s]
erasing 'userdata'...
OKAY [ 20.154s]
erasing 'cache'...
OKAY [ 0.426s]
rebooting...
finished. total time: 78.366s
The system again stalls at the start screen (four collored dots, yellow, red, green and blue).
Please, observe that in all cases I received the messages:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
Would be this the problem? Am I doing something wrong during the flashing process?
Thank you for your help
Cheers,
Eduardo
Did you do a factory reset in recovery?

Cannot install stock rom: FAILED (remote: data too large)

I tried installing Cyanogenmod on a Nexus 5X, and it didn't work, so now I'm trying to install the stock rom from this site: https://developers.google.com/android/images#bullhead.
I'm doing this on Ubuntu 15.10. When I run the flash-all.sh script (on any of them), I get this output:
target reported max download size of 536870912 bytes
sending 'bootloader' (4382 KB)...
OKAY [ 0.195s]
writing 'bootloader'...
OKAY [ 0.077s]
finished. total time: 0.272s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.715s]
writing 'radio'...
OKAY [ 0.338s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: BHZ10i
Baseband Version.....: M8994F-2.6.22.0.56
Serial Number........: 00a9164559592811
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (11469 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.073s]
sending 'recovery' (12521 KB)...
OKAY [ 0.393s]
writing 'recovery'...
OKAY [ 0.092s]
erasing 'system'...
OKAY [ 0.089s]
sending 'system' (1950236 KB)...
FAILED (remote: data too large)
finished. total time: 1.210s
I'm not seeing many resources online about this error. The only thing I've seen is to update fastboot, but I've already got the latest installed with this ppa: http://askubuntu.com/questions/34702/how-do-i-set-up-android-adb
Is there anything that I can do to get it working correctly?
adanedhel728 said:
I tried installing Cyanogenmod on a Nexus 5X, and it didn't work, so now I'm trying to install the stock rom from this site: https://developers.google.com/android/images#bullhead.
I'm doing this on Ubuntu 15.10. When I run the flash-all.sh script (on any of them), I get this output:
target reported max download size of 536870912 bytes
sending 'bootloader' (4382 KB)...
OKAY [ 0.195s]
writing 'bootloader'...
OKAY [ 0.077s]
finished. total time: 0.272s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
target reported max download size of 536870912 bytes
sending 'radio' (56614 KB)...
OKAY [ 1.715s]
writing 'radio'...
OKAY [ 0.338s]
finished. total time: 2.052s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: BHZ10i
Baseband Version.....: M8994F-2.6.22.0.56
Serial Number........: 00a9164559592811
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (11469 KB)...
OKAY [ 0.406s]
writing 'boot'...
OKAY [ 0.073s]
sending 'recovery' (12521 KB)...
OKAY [ 0.393s]
writing 'recovery'...
OKAY [ 0.092s]
erasing 'system'...
OKAY [ 0.089s]
sending 'system' (1950236 KB)...
FAILED (remote: data too large)
finished. total time: 1.210s
I'm not seeing many resources online about this error. The only thing I've seen is to update fastboot, but I've already got the latest installed with this ppa: http://askubuntu.com/questions/34702/how-do-i-set-up-android-adb
Is there anything that I can do to get it working correctly?
Click to expand...
Click to collapse
the system image always is too large and usually it gets transferred in smaller pieces automatically. I'd try to flash all the images manually on a Windows mashine, following this guide (section 10).
I did it many times this way without issues.
ulxerker said:
the system image always is too large and usually it gets transferred in smaller pieces automatically. I'd try to flash all the images manually on a Windows mashine, following this guide (section 10).
I did it many times this way without issues.
Click to expand...
Click to collapse
Well, I can't get it working on Windows at all, because the driver won't install. (At least I assume that's the reason why-- The driver won't install and fastboot won't show any devices.)
I tried fixing that, but with no luck.
I did also try section 10 from Ubuntu, with the same results for the system part:
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.284s]
sending sparse 'system' (514493 KB)...
OKAY [ 12.333s]
writing 'system'...
OKAY [ 3.149s]
sending sparse 'system' (514543 KB)...
OKAY [ 12.427s]
writing 'system'...
OKAY [ 3.117s]
sending sparse 'system' (524291 KB)...
FAILED (remote: data too large)
finished. total time: 31.327s
Fastboot is too old. Remove it from system. apt remove android-tools-fastboot . Place fastboot from dl link into a folder where is your system img. Change permissions if needed and exexute it with ./fastboot
https://mega.nz/#!CYYjHYSK!yjhPZ-OYQNhFxq-0JXVibtUps7AwoFDtvk0yPu_194s
Even better is to place fastboot file into a system /bin folder from where you can execute command in any folder.
Best regards.
icrunchbanger said:
Fastboot is too old. Remove it from system. apt remove android-tools-fastboot . Place fastboot from dl link into a folder where is your system img. Change permissions if needed and exexute it with ./fastboot
https://mega.nz/#!CYYjHYSK!yjhPZ-OYQNhFxq-0JXVibtUps7AwoFDtvk0yPu_194s
Even better is to place fastboot file into a system /bin folder from where you can execute command in any folder.
Best regards.
Click to expand...
Click to collapse
My gosh, that finally worked, and I didn't believe it would. I had thought that the one I had gotten from that PPA was the newest, but, apparently not. I actually got it directly from Google (which was a chore in itself, but outside the scope of this thread).
Thank you very much. Now, let's see if I can find out how to mark this as solved...
adanedhel728 said:
My gosh, that finally worked, and I didn't believe it would. I had thought that the one I had gotten from that PPA was the newest, but, apparently not. I actually got it directly from Google (which was a chore in itself, but outside the scope of this thread).
Thank you very much. Now, let's see if I can find out how to mark this as solved...
Click to expand...
Click to collapse
Your welcome. Never trust PPA ?
I got issuse
icrunchbanger said:
Fastboot is too old. Remove it from system. apt remove android-tools-fastboot . Place fastboot from dl link into a folder where is your system img. Change permissions if needed and exexute it with ./fastboot
https://mega.nz/#!CYYjHYSK!yjhPZ-OYQNhFxq-0JXVibtUps7AwoFDtvk0yPu_194s
Even better is to place fastboot file into a system /bin folder from where you can execute command in any folder.
Best regards.
Click to expand...
Click to collapse
Bro link doesnt work, can you sent me app via email: [email protected]
suleymanov5 said:
Bro link doesnt work, can you sent me app via email: [email protected]
Click to expand...
Click to collapse
You can download android tools from Google
https://dl.google.com/android/repository/platform-tools-latest-linux.zip
Also you can check my github for some nifty scripts .
https://github.com/icrunchbanger/android

Update 7.1.1 Rooted XL to 7.1.2 Without Losing Data?

Please explain throughly and provide the download links, I've only had an android for a month and I am still learning the OS / Phone
tryfont said:
Please explain throughly and provide the download links, I've only had an android for a month and I am still learning the OS / Phone
Click to expand...
Click to collapse
Third post in the thread below. Just get the 7.1.2 full image instead of the 7.1.1 I mention in that post.
Pay attention to removing the -w from the flashall bat file. That is the key to saving your data.
And second to the last post in the thread are the​ instructions for getting root back.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
SOLVED
TonikJDK said:
Third post in the thread below. Just get the 7.1.2 full image instead of the 7.1.1 I mention in that post.
Pay attention to removing the -w from the flashall bat file. That is the key to saving your data.
And second to the last post in the thread are the​ instructions for getting root back.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
I'm on a mac, not sure how to do the last step with running the .bat file
Edit: went into the bat file and ran the equivalent commands in terminal
(fastboot flash bootloader bootloader-marlin-8996-012001-1702151126.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-marlin-8996-012901-1702171013.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-marlin-n2g47e.zip)
Here is the terminal messages I got
Last login: Mon Apr 3 18:00:13 on ttys000
Tryfons-MBP:~ tryfon$ cd /Users/tryfon/Desktop/platform-tools
Tryfons-MBPlatform-tools tryfon$ ./fastboot flash bootloader bootloader-marlin-8996-012001-1702151126.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32380 KB)...
OKAY [ 0.811s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.163s]
finished. total time: 4.974s
Tryfons-MBPlatform-tools tryfon$ fastboot reboot-bootloader
-bash: fastboot: command not found
Tryfons-MBPlatform-tools tryfon$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.046s
Tryfons-MBPlatform-tools tryfon$ fastboot flash radio radio-marlin-8996-012901-1702171013.img
-bash: fastboot: command not found
Tryfons-MBPlatform-tools tryfon$ ./fastboot flash radio radio-marlin-8996-012901-1702171013.img
target reported max download size of 536870912 bytes
sending 'radio_b' (57240 KB)...
OKAY [ 1.444s]
writing 'radio_b'...
OKAY [ 0.704s]
finished. total time: 2.148s
Tryfons-MBPlatform-tools tryfon$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.050s
Tryfons-MBPlatform-tools tryfon$ ./fastboot update image-marlin-n2g47e.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
--------------------------------------------
Bootloader Version...: 8996-012001-1702151126
Baseband Version.....: 8996-012901-1702171013
Serial Number........: HT72A0200395
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_b' (25997 KB)...
OKAY [ 0.701s]
writing 'boot_b'...
OKAY [ 0.260s]
erasing 'system_b'...
OKAY [ 0.457s]
sending sparse 'system_b' 1/4 (514854 KB)...
OKAY [ 14.106s]
writing 'system_b' 1/4...
OKAY [ 6.005s]
sending sparse 'system_b' 2/4 (524140 KB)...
OKAY [ 14.606s]
writing 'system_b' 2/4...
OKAY [ 4.937s]
sending sparse 'system_b' 3/4 (512784 KB)...
OKAY [ 14.072s]
writing 'system_b' 3/4...
OKAY [ 6.243s]
sending sparse 'system_b' 4/4 (32756 KB)...
OKAY [ 0.905s]
writing 'system_b' 4/4...
OKAY [ 0.297s]
erasing 'system_a'...
OKAY [ 0.411s]
sending sparse 'system_a' 1/4 (520579 KB)...
OKAY [ 13.904s]
writing 'system_a' 1/4...
OKAY [ 3.787s]
sending sparse 'system_a' 2/4 (521193 KB)...
OKAY [ 13.721s]
writing 'system_a' 2/4...
OKAY [ 4.103s]
sending sparse 'system_a' 3/4 (510216 KB)...
OKAY [ 14.206s]
writing 'system_a' 3/4...
OKAY [ 3.788s]
sending sparse 'system_a' 4/4 (128745 KB)...
OKAY [ 3.513s]
writing 'system_a' 4/4...
OKAY [ 1.049s]
erasing 'vendor_b'...
OKAY [ 0.154s]
sending 'vendor_b' (242238 KB)...
OKAY [ 6.003s]
writing 'vendor_b'...
OKAY [ 3.653s]
Setting current slot to 'b'...
OKAY [ 0.087s]
rebooting...
finished. total time: 131.364s
Tryfons-MBPlatform-tools tryfon$
Everything turned out fine!!!

Nexus 7 2013 LTE bootloop, can't enter Recovery mode; flash write failure

My Nexus 7 2013 LTE was rooted and updated to stock Android 6.0 a year ago, no 3rd party ROM/recovery is installed. Last week while checking emails, it rebooted suddenly then remained at Google letters and unlock icon, I can enter fastboot mode by pressing power and volume- buttons together, the last line shows status unlocked; then if select "Recovery mode", it reboots then shows a dead robot with an exclamation mark only. I downloaded the latest factory image "razorg-mob30x", connect it to my PC and enter adb command "flash-all.bat" (I modified the bat file by removing -w, so it won't wipe the user data), then it shows: FAILED (remote: flash write failure)
sending 'bootloader' (3915 KB)...
OKAY [ 0.135s]
writing 'bootloader' ...
FAILED (remote: flash write failure)
finished. total time 90.811s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time 0.012s
sending 'radio' (76038 KB)...
OKAY [ 2.393s]
writing 'radio' ...
FAILED (remote: flash write failure)
finished. total time 92.549s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time 0.013s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
----------------------------------------------------
Bootloader Version...: FLO-04.08
Basedband Version...: DEB-Z00_2.44.0_0213
Serial Number................: 0879222a
----------------------------------------------------
checking product...
OKAY [ 0.005s]
checking version-bootloader...
OKAY [ 0.006s]
checking version-baseband...
OKAY [ 0.006s]
sending 'boot' (7422 KB)
OKAY [ 0.243s]
writing 'boot' ...
FAILED (remote: flash write failure)
finished. total time 90.151s
Press any key to exit...
Click to expand...
Click to collapse
What else I can do to resuce my pad? Does this mean the memory is physically damaged?
Please advise. Your help is much appreciated.
Bad motherboard, just had to replace mine with exact issue.

Categories

Resources