Database Users

[Q] Help! secure boot: image SOS checksum fail!

i try to upgrade my A500 but failed, when i tried to update it again I got this message in the upper left corner:
secure boot: image SOS checksum fail!
but if i turn it on normally, i can still i can run the machine and use it without any problem.
i thought something might went wrong with the boot.img, so i tried to push the boot.img, but got another message when i turn on the A500 as:
secure boot : image LNX checksum fail!
now i am totally lost, once i turn it on, it will show the LNX thing, if i tried to flash it, it will show the sos thing.
unfortunetely i did not back up my recovery.img.
who can help me on this? thanks in advance!

Uh oh....that sounds like some major brickage.......sc2k is your only hope now.

So I really hope u got your UID.
If so I can instruct you how to unbrick.
Please contact me via PM with your UID.

thank you so much!
but i did not record my UID, is there anyway out? or my A500 really become a brick now?

Try if this still works:
TRY FIRST WITHOUT CONNECTING THE DEVICE VIA USB
2.c Windows (alternative method)
Download this tool (download link is nearly at the end of the page): http://www.nirsoft.net/utils/usb_devices_view.html
- Open the tool - Sort after VendorID - Check all devices with VendorID = 0502 and ProductID = 3325 . There is also a "Serial Number" column.

i downloaded this software and open it quite well. it shows my A500 in the device name, there are 3 A500 devices under different descriptions.
i found the serial number column and read it. is this UID for my A500?

Please PM me the value of the field. Should be a numer with 15-16 digits.

Did you have any luck in fixing the device.?
Sent from my HTC HD2 using XDA Premium App

i am learning from sc2k now, hopefully i can fix it.

Awesome let me know how it goes if you can
Sent from my HTC HD2 using XDA Premium App

I had the exact same thing happen with my first Iconia while trying to get around the locked bootloader (in the early pre-recovery method days).
Acer was kind enough to offer to replace it for free under warranty if I shipped it to them, but best buy replaced it for me on the spot.

I had the same prob
just download an update.zip put in ur sdcard and flash it by pressin volum down when u restart.
Gl.

hitvan said:
I had the same prob
just download an update.zip put in ur sdcard and flash it by pressin volum down when u restart.
Gl.
Click to expand...
Click to collapse
"Image SOS" is a bricked recovery, so no update.zip can be flashed. You must be thinking of "Image LNX" which is just a soft brick and can be recovered with update.zip
One or the other at a given time is ok. Both is bad.

ohh sry my bad...didnt read properly

brain117 said:
i try to upgrade my A500 but failed, when i tried to update it again I got this message in the upper left corner:
secure boot: image SOS checksum fail!
but if i turn it on normally, i can still i can run the machine and use it without any problem.
i thought something might went wrong with the boot.img, so i tried to push the boot.img, but got another message when i turn on the A500 as:
secure boot : image LNX checksum fail!
now i am totally lost, once i turn it on, it will show the LNX thing, if i tried to flash it, it will show the sos thing.
unfortunetely i did not back up my recovery.img.
who can help me on this? thanks in advance!
Click to expand...
Click to collapse
I has this two days ago, its easy to fix, please PM

I'm in a similar boat, but I at least have my UID and all my backups. What's the procedure, pretty please?

brain117 said:
i try to upgrade my A500 but failed, when i tried to update it again I got this message in the upper left corner:
secure boot: image SOS checksum fail!
but if i turn it on normally, i can still i can run the machine and use it without any problem.
i thought something might went wrong with the boot.img, so i tried to push the boot.img, but got another message when i turn on the A500 as:
secure boot : image LNX checksum fail!
now i am totally lost, once i turn it on, it will show the LNX thing, if i tried to flash it, it will show the sos thing.
unfortunetely i did not back up my recovery.img.
who can help me on this? thanks in advance!
Click to expand...
Click to collapse
In order to fix BOOT.img problems just flash an entire update.zip from here
http://forum.xda-developers.com/showthread.php?t=1113878
full firmware update.zip contains it own boot.img
this is how I fix this same problem

Alejandrissimo said:
In order to fix BOOT.img problems just flash an entire update.zip from here
http://forum.xda-developers.com/showthread.php?t=1113878
full firmware update.zip contains it own boot.img
this is how I fix this same problem
Click to expand...
Click to collapse
Again, one of the op's problems is an image SOS checksum fail, which is a bad recovery image. No update.zip can be flashed without recovery.
I'm curious to see if recovery from bad SOS AND bad LNX is possible, since I couldn't get into adb, recovery, or the OS when both went bad on me. Any updates from the op?

WishRyder said:
Again, one of the op's problems is an image SOS checksum fail, which is a bad recovery image. No update.zip can be flashed without recovery.
I'm curious to see if recovery from bad SOS AND bad LNX is possible, since I couldn't get into adb, recovery, or the OS when both went bad on me. Any updates from the op?
Click to expand...
Click to collapse
I'd like to know, too. I'm sitting here with a dead Iconia.

jimbobtexas said:
I'd like to know, too. I'm sitting here with a dead Iconia.
Click to expand...
Click to collapse
only hope i see is that you may find a working nvflash version.
but i remember that s2ck said if you have your usb id you are able to recovery such failures

[Q] stuck at verifying SBK

After verifying my cpuid from 2 method, I went to vache's sbk generator and got a result.
But then the sbk verification returned with an error. I tried just the 15 cpuid digits, then with a 0 in front, and with 0x0 in front and it all generated the same SBK number. And I'm pretty sure the cpuid I got is correct because there's no way I could have downgraded from 3.2 to 3.0.1 with a wrong cpuid.
Any help here?
By the way, after doing the nvflash --bootloader.img --sbk x x x x --sync thing, it returned with an error and then my tablet gets disconnected and I need to hold power to turn off then turn it on and then have it enter apx mode again. Is this normal?

bryan_mmx said:
After verifying my cpuid from 2 method, I went to vache's sbk generator and got a result.
But then the sbk verification returned with an error. I tried just the 15 cpuid digits, then with a 0 in front, and with 0x0 in front and it all generated the same SBK number.
Click to expand...
Click to collapse
Any leading "0x" is discarded (it's just telling us it is a hex string).
What verification?
bryan_mmx said:
By the way, after doing the nvflash --bootloader.img --sbk x x x x --sync thing, it returned with an error and then my tablet gets disconnected and I need to hold power to turn off then turn it on and then have it enter apx mode again. Is this normal?
Click to expand...
Click to collapse
What is the error message?

eppeP said:
Any leading "0x" is discarded (it's just telling us it is a hex string).
What verification?
What is the error message?
Click to expand...
Click to collapse
I see what you did there.
Anyway, the verification I'm saying is thatprocess of checking if SBK number is correct. You know, the nvflash --bootloader.img --sbk x x x x --sync command.
And the error?
rcm version 0X4
Command send failed (usb write failed)

bryan_mmx said:
nvflash --bootloader.img --sbk x x x x --sync command.
Click to expand...
Click to collapse
could try a500 manager to see if it can extract it to check?
But the error says usb write failed not usb connection failed,
which leads me to think the sbk is ok just something else not working like it should...
not sure what else to tell you, what are you trying to flash?
try this....instead of --sync at the end put --go

dibb_nz said:
could try a500 manager to see if it can extract it to check?
But the error says usb write failed not usb connection failed,
which leads me to think the sbk is ok just something else not working like it should...
not sure what else to tell you, what are you trying to flash?
try this....instead of --sync at the end put --go
Click to expand...
Click to collapse
after switching to a 32bit windows, everything worked, flashed unlocked ICS bootloader in 5-10 minutes.
thanks for trying to help.

I dont follow you , were you running 64 bit ? or Linux? because I can get it to work through 64 bit and Linux?

Vintage144 said:
I dont follow you , were you running 64 bit ? or Linux? because I can get it to work through 64 bit and Linux?
Click to expand...
Click to collapse
had me a bit confused to Vin - still going strong m8

Hey Dibb!! I know you already seen this , but for anyone else in here , your cpuid and sbk is a breeze now with this http://forum.xda-developers.com/showthread.php?t=1675939

Stuck in APX Mode and Need Help!

Alright, I have been trying to get my A500 out of APX mode for a couple weeks now and have run out of ideas. I am hoping someone here will be able to offer a suggestion I haven't tried. I have read every thread I could find on the subject and it isn't my first time stuck in APX mode and have used the EUU once and Timothy's Root-3.2.1 tool to recover previously. This time something is different though, I have tried 2 different factory EUUs, AfterOTA, APX Flash Tool, Timothy's Root-3.2.1 EUU, nvbat tools, BadSector and possibly more that I am missing, all hangup except the EUUs which error out when the tablet switches to download mode.
I would be greatly appreciative of any ideas anyone may have to save this thing, it is out of warranty and seems to just be an expensive coaster at this point.

The Same Here

The same here too...
Sent from my Galaxy Nexus using xda app-developers app

It sucks, if I can't figure it out within the next couple weeks I think I will take my anger out on it with firearms. I'll pull the battery first but after that rounds will fly.

ponypowerracin said:
It sucks, if I can't figure it out within the next couple weeks I think I will take my anger out on it with firearms. I'll pull the battery first but after that rounds will fly.
Click to expand...
Click to collapse
heck, you can almost get your money back by "parting" it out. Dincdoesme is looking for a front display assembly
Ok, as I sent you the link in PM, for the rest of you folks, here's some things to try.
Note This. I am NOT a brickmaster. I'm just lucky getting things running again for a lot of people. So if these methods don't work, well, don't shoot the cook! I've never been stuck in APX mode, but I've cooked some bootloader's before.
There are a few things that causes this.
1. Your PC is playing tricks. You should disable anti-virus and such. And sometimes, using a different PC can make a difference.
2. Your USB cable. They are not all created equal, as a pin layout may be different. I use my HTC Desire's USB cable and never had an issue. My camera's cables act like they will work, but always produce errors.
3. You have corrupted or damaged memory blocks where the bootloader resides. In this case, the MB will more than likely need replaced.
So with that said, I will give you a link. Now, this zip has one of the very early NVFlash bootloader apps. I couldn't find my original pure NVFlash setup, but I've used this one often in the past. It may be more tolerant.
http://d-h.st/32X
Unzip the contents to a folder.
Have your SBK number ready. You should already have this from your UID number.
Power off your tab. Then manually put it in APX mode, by pressing and holding the pinhole rest, then press and hold PWR. After 4 seconds, release PWR, then 1 second later release pinhole. Your display should be black with a white PWR button. If not try it again or reverse the switches (been a long time)
Start the NVFlash application. DO NOT DOWNLOAD ANY BUNDLES. Plug your tab in when prompted. Always select Auto.
Ignore any windows messages. If it looks like it stops stating no APX devices, just continue.
There are 2 bootloaders and a CWM package. 1 bootloader is for the 500, the other for the 501. They are identicle except for the logo. Just choose one.
Now, note that this is a version 3 unlocked bootloader. It's ok.
At the end, you may or may not get some red ebt message. Ignore it. Just reboot it into CWM.
Hoping this works for you guys.
In the meantime, I'll still look for my original NVFlash which will rule out windows apps and conflicts.
MD

ponypowerracin said:
Alright, I have been trying to get my A500 out of APX mode for a couple weeks now and have run out of ideas. I am hoping someone here will be able to offer a suggestion I haven't tried. I have read every thread I could find on the subject and it isn't my first time stuck in APX mode and have used the EUU once and Timothy's Root-3.2.1 tool to recover previously. This time something is different though, I have tried 2 different factory EUUs, AfterOTA, APX Flash Tool, Timothy's Root-3.2.1 EUU, nvbat tools, BadSector and possibly more that I am missing, all hangup except the EUUs which error out when the tablet switches to download mode.
I would be greatly appreciative of any ideas anyone may have to save this thing, it is out of warranty and seems to just be an expensive coaster at this point.
Click to expand...
Click to collapse
jancarlos1597 said:
The Same Here
Click to expand...
Click to collapse
sebone02 said:
The same here too...
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
For you guys stuck in apx - please provide a screenshot of your error messages!!
there are way too many things it COULD be and is difficult to help without physically having the tab in hand!!!! Pictures!!! post some pictures
Running nvFlash,
Go in and edit the .bat file and delete all lines beginning with 'cls' close and save, then run it...and post the error here - not saying you can be fixed but at least all error codes will be in one place.
Depending which error you have will determine whether yr tab needs to be sent to acer for repair...or something far more simple like uninstalling and reinstalling BOTH sets of drivers....
IF apxFlashv4 or timmydeansv4 or MD's suggestion above does not fix you, then yr motherboard is toasted and will need replacement
sebone02 said:
The same here too...
Click to expand...
Click to collapse
@sebone02 -
yr a bit different as u rec'd yr tab stuck in apx, so we dont know what rom was on there b4 this happened....But the bootloader tools definitely wont work from HC3.2 -
first thing to do is make sure you have both sets of drivers installed
the acer ones and the android sdk ones. Then connect to your pc
is the apx device showing and/0r the acer boot/recovery drivers
Try to perform a hard reset to format the cache and userdata
1) Turn off your tablet,
2) Rotation lock to your left;
3) Press Vol+ (which is to a rotation lock) and power on simultaneosly
4) As soon as the tablet vibrates you can release the power on button and you should start to switch rotation lock left and right till you see
Erasing Userdata...
Erasing Cache...
Vol+ is still pressed;
5) The tablet starts to format
6) Your tablet will be as clean as it can be.
Then run timmydeansv4.

Thank you to those trying to help.
A couple errors when trying a couple different manual commands with nvflash
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nvbat error
EUU error, same thing happens with factory EUUs and root-3.2.1, this error comes up as soon as the tablet switches to apx download mode
Bad Sector error
Sticks in Afterota at flashing recovery
All versions of APX Flash tool hang at the same spot

Yeah, my bag of tricks is empty at the moment. I see in the posts above you, where jazzyjames and a couple others are in the same boat. Everything points to an unrecoverable error in the boot loader partition.
Maybe those guys will stumble onto something, or skirlaz_cz will have some input.
On the 700/701/510 we had the issue right at the start when the first cwm's were couurupting the data partitions when wipes or restores were done. Samsung s3 had the same bug that bricked the partitions. The lead dev in the 700 forum got his own stuck in apx mode for some unknown reason. End result are main board changes for all of them including mine.
On the 70x, they found several hidden partitions, so am hoping that mess is sorted out now.
MD

thanks for posting the pix - i see each tool reports different errors - not sure why this would be, all i can tell you is i have had a couple of nvflash errors along with the EUU update failed screen and the display showing "reboot the device", (all at the same time) which never went away no matter how many times i rebooted....somehow though thru multiple tries over many days i got a working tab again...
I'm sure that in the end the apxflash tool finally recognised my tab in apx mode,
once that happened i manually flashed a bootloader.bin and recovery.img -
you can try this if you have tdv4, use the .img files in there to manually flash via apxflash tool
also, if u have access to linux - running nvflash command from it has helped others...
finally lcd047 ran nvflash directly from tdv4 (his was a partition error):
lcd407; said:
* I downloaded timmyDean's root-3.2.1-V4.7z
* I booted the tablet (in APX mode) and I connected the USB cable to it
* in the directory root-3.2.1/Image I run the command
Code:nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX --go
* without rebooting, I flashed the v7 bootloader and recovery as per the bootloader thread; since the partition table was restored at the previous step, the operation now succeeded;
* I rebooted the tablet in recovery, and proceeded to wipe the data and flash a ROM the usual way.
As I already noted, I lost all the data from the internal sdcard. I'm not sure if that was the result of the re-creation of partitions, or I inadvertently did that while messing with nvflash, the bottom line is all files are gone. In turn, restoring the CWM backup didn't do much good, because most apps will fail in interesting ways without the sdcard data, so I'll probably just start from scratch and reinstall the apps from a Titanium backup. But I have a working tablet again.
Click to expand...
Click to collapse
another good thread to take a look at, although i got lost after page1!!!!
No access to ROM or Recovery its the only fix i have seen that addresses the problem and provides a solution - its a shame i cannot understand it, lol
from what i've seen on the boards the ebt issue is damn near unrecoverable,
partition errors seem a little easier??
bct errors can sometimes be recovered from using the dump my bct option in apxflash 0.4 IF you can get the tool to recognise yr tab...
If tdv4 fails then its a bit of a lottery in finding something else that works
ensuring that an apx device is recognised by yr pc is fundamental in getting any of the automated tools to work....
I do wish you all the best in finding a solution, and please keep us all posted on how u ALL get on with this....
rgds dibb

ponypowerracin said:
Thank you to those trying to help.
A couple errors when trying a couple different manual commands with nvflash
Sticks in Afterota at flashing recovery
All versions of APX Flash tool hang at the same spot
Click to expand...
Click to collapse
I know its been a while for you facing this problem, but I'm seeing the exact smae problem now.
Did you have any luck getting this fixed?

mandar_h said:
I know its been a while for you facing this problem, but I'm seeing the exact smae problem now.
Did you have any luck getting this fixed?
Click to expand...
Click to collapse
My A500 had a bad memory module and I ended up sending it back to Acer for repair. I was about a month out of warranty but by contacting them through Twitter they went ahead and fixed it for free.

ponypowerracin said:
My A500 had a bad memory module and I ended up sending it back to Acer for repair. I was about a month out of warranty but by contacting them through Twitter they went ahead and fixed it for free.
Click to expand...
Click to collapse
I'm way out of warranty. So I doubt if they will entertain my case at all.
Thanks for the reply.

Try Acer m8 they have been known to repair these faulty out if warranty tabs. That's if you're certain its the chip....See this http://forum.xda-developers.com/showthread.php?t=2738138
Sent from my HTC_PN071 using Tapatalk

A500 Full Brick Unsolved...

Hello All,
To you I come, for acer tablet A500, I Think ... What is briquée
I resume,
The tablet has planted in full play, then reboot extinction impossible, stuck on screen acer ....
To access the Recovery Not Originally.
Horizontal shelf only thing I press the volume button on the top left button + power shelf displays a few lines that looks like some sort of flash marked:
Cache update before erasing sd
SD update cmd: recovery
udate package sd card: update.zip
booting recovery kernel image
Follows, the progress bar under the blue android (lying in a carafe with red triangle ...) is blocked ...
then decanted or android supine red triangle and no progress bar and reboot after 5 minutes on the screen acer ...
The tab was under ICS UPDATED OTA ... I do not know any more I never had access to this tablet ...
apx mode when the tablet is recognized as acer picasso USB boot-recovery-driver
I of valid command line:
nvflash - bct flash.bct - setbct - configfile flash.cfg - create - odmdata 0xb00d8011 - bl bootloader.bin - go
the tab is the deco pc and nothing happens ...
This is tough.
then this app (Universal Android AIO Flasher Tool$) looks at the top, it is clear that communicates fastboot mode with the tablet, it offers the tab flash through fastboot mode, but (and yes always a but) the tab does not looks like ....
she displays two red lines
fastboot: command not in the carrier lock mode ....
See the photo.
In fast boot mode, open calls in c: sdk / platform tools ....
fastboot oem unlock I hit okay result ...
I type fastboot update update.zip behind I get error: update package has no android info.txt and android product.txt
Well, I summarized a bit
If I want to use flash apx I have no cpuid ...
If I want to use A500Manager the tablet is not detected ...
If I want to use Fastboot mode ca communicates yesterday, orders launch code but multiple errors on the shelf ... but nothing concrete results ...
If I want to use nvflash commands to launch but device not found ...
If I want to use topo Android_AIO_Flasher same cate with the fastboot command ....
I think my hope lies between fastboot and apx apx but I would need it .... ****ing cpuid
I raked French and foreign internet board but without success, the tablet does not rise and so I can not make it the only thing feasible is apx mode ...
I therefore appeal to your precious skills ....
Thank you for your help ...
Sincerely,
Laboulisti.

have you tried Afterota_Lite_v1_09
laboulisti said:
Hello All,
To you I come, for acer tablet A500, I Think ... What is briquée
I resume,
The tablet has planted in full play, then reboot extinction impossible, stuck on screen acer ....
To access the Recovery Not Originally.
Horizontal shelf only thing I press the volume button on the top left button + power shelf displays a few lines that looks like some sort of flash marked:
Cache update before erasing sd
SD update cmd: recovery
udate package sd card: update.zip
booting recovery kernel image
Follows, the progress bar under the blue android (lying in a carafe with red triangle ...) is blocked ...
then decanted or android supine red triangle and no progress bar and reboot after 5 minutes on the screen acer ...
The tab was under ICS UPDATED OTA ... I do not know any more I never had access to this tablet ...
apx mode when the tablet is recognized as acer picasso USB boot-recovery-driver
I of valid command line:
nvflash - bct flash.bct - setbct - configfile flash.cfg - create - odmdata 0xb00d8011 - bl bootloader.bin - go
the tab is the deco pc and nothing happens ...
This is tough.
then this app (Universal Android AIO Flasher Tool$) looks at the top, it is clear that communicates fastboot mode with the tablet, it offers the tab flash through fastboot mode, but (and yes always a but) the tab does not looks like ....
she displays two red lines
fastboot: command not in the carrier lock mode ....
See the photo.
In fast boot mode, open calls in c: sdk / platform tools ....
fastboot oem unlock I hit okay result ...
I type fastboot update update.zip behind I get error: update package has no android info.txt and android product.txt
Well, I summarized a bit
If I want to use flash apx I have no cpuid ...
If I want to use A500Manager the tablet is not detected ...
If I want to use Fastboot mode ca communicates yesterday, orders launch code but multiple errors on the shelf ... but nothing concrete results ...
If I want to use nvflash commands to launch but device not found ...
If I want to use topo Android_AIO_Flasher same cate with the fastboot command ....
I think my hope lies between fastboot and apx apx but I would need it .... ****ing cpuid
I raked French and foreign internet board but without success, the tablet does not rise and so I can not make it the only thing feasible is apx mode ...
I therefore appeal to your precious skills ....
Thank you for your help ...
Sincerely,
Laboulisti.
Click to expand...
Click to collapse
i am not an expert but hv you tried the Afterota_Lite_v1_09 it is a very good tool. it might help you get your cpuid and sbk but in windows 7 u have to turn off user account control settings before running it. u will find the file in the attachments. i hope it will help

mahmoud_m_m said:
i am not an expert but hv you tried the Afterota_Lite_v1_09 it is a very good tool. it might help you get your cpuid and sbk but in windows 7 u have to turn off user account control settings before running it. u will find the file in the attachments. i hope it will help
Click to expand...
Click to collapse
no AfterOta does not detect the tab in apx ...... or neither fastboot and I can not demmarer to enable debugging ...

try this guide
laboulisti said:
no AfterOta does not detect the tab in apx ...... or neither fastboot and I can not demmarer to enable debugging ...
Click to expand...
Click to collapse
this guide is describing how to unbrick it with symptoms like what u mentioned.
http://forum.xda-developers.com/showthread.php?t=1585907
---------- Post added at 06:16 PM ---------- Previous post was at 06:07 PM ----------
laboulisti said:
no AfterOta does not detect the tab in apx ...... or neither fastboot and I can not demmarer to enable debugging ...
Click to expand...
Click to collapse
way above me man wish you best of luck.

mahmoud_m_m said:
this guide is describing how to unbrick it with symptoms like what u mentioned.
http://forum.xda-developers.com/showthread.php?t=1585907
---------- Post added at 06:16 PM ---------- Previous post was at 06:07 PM ----------
way above me man wish you best of luck.
Click to expand...
Click to collapse
already seen this thread but I can not follow this thread because I did not cpuid .....

Defy bootloader error..

Hello, I've got a problem with my motorola defy, after installing any rom it automatically switches to bootloader mode, after pressing vol- power it displays motorola logo and then comes bootloader with an error: err:a5,69,35,00
I'v already tried a huge number of abfs including roms from defy+
Thanks in advance for your help.

Flash dfp 231. It will get you to the Motorola logo
Sent from my MB526 using Tapatalk 2

thekguy said:
Flash dfp 231. It will get you to the Motorola logo
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Unfortunately, this is not working

Dfp231 cannot give the boot loader error, unless you have eMMC failure
Sent from my MB526 using Tapatalk 2

Sorry idon't understand you, because my english is poor.
my log from rsd lite
09/18/13 15:50:04 --------------------------------------------------------------------------------
09/18/13 15:50:04 New Log Started For Software Download.
09/18/13 15:50:10 00000694 Phone.cpp 531 0 ERROR Generic failure when sending command.
09/18/13 15:50:10 00000694 Phone.cpp 1683 0 ERROR GetPhoneID failed: ERROR.
09/18/13 15:50:20 The FlashLog key is turned off.
09/18/13 15:50:21 Multi upgrade started for 1 phones
09/18/13 15:50:21 [Device ID: 0] Flashing phone.
09/18/13 15:54:54 [Device ID: 0] Waiting for others to finish current operation.
09/18/13 15:54:55 The FlashLog key is turned off.
09/18/13 15:54:55 FlashLog file is turned off.
09/18/13 15:54:55 Multi upgrade finished.
09/18/13 15:54:55 00000694 Phone.cpp 531 0 ERROR Generic failure when sending command.
09/18/13 15:54:55 00000694 Phone.cpp 1683 0 ERROR GetPhoneID failed: ERROR.

I mean there is a hardware problem if you cannot revive your phone using dfp 231
Log shows a bad error (generic flash command failure). I don't think it can be fixed without motherboard replacement
Sent from my MB526 using Tapatalk 2

Ok ;/ thanks for help