Hello Forum. I am trying to flash CoreDroid. I got the update for magldr 1.13 but whenever I go to execute DAF.exe I get the following statement:
An error has occurred
Read below for more information
Error Description: Config load failed.
Info: .\RSPL\RSPL.cpp (725)
Error Description: CONFIG: can't open config file
Info: .\RSPL\RSPL.cpp (304)
Can anyone tell me what this means??
Hi, can someone help me as I watched this video:
http://forum.xda-developers.com/showthread.php?t=893948
I flashed and got this error message:
An error has occurred
Read below for more information
Error Description: Config load failed.
Info: .\RSPL\RSPL.cpp (725)
Error Description: CONFIG: can't open config file
Info: .\RSPL\RSPL.cpp (304)
I am stuck on Boot Mode. What do I have to do?
go an put
Error Description: Config load failed. Info: .\RSPL\RSPL.cpp (725)
into google and read the first half dozen hits.
samsamuel said:
go an put
Error Description: Config load failed. Info: .\RSPL\RSPL.cpp (725)
into google and read the first half dozen hits.
Click to expand...
Click to collapse
Very constructive ... not
Current Status: Brick
Hi,
I tried flashing stock SBF CEE 3.4.2-179-2 (retail central Europe) from here http://sbf.droid-developers.org/umts_jordan/list.php
I get IO and checksum errors resulting in FAIL. Now the phone does not boot.
Boot Loader
Code:
Bootloader
09.10
[B]Code Corrupt[/B]
Battery OK
OK to Program
Connect USB Data Cable
With RSD Lite 5.7 on Windows XP and MotoHelper drivers MotoHelper_2.0.40_Driver_4.9.0.exe
RSD Lite log::
2012/12/20 02:05:45 | -- | ERROR: AP Die ID: 1b10000791b963010000dcff0200
2012/12/20 02:05:45 | -- | ERROR: BP Die ID: 0000000000000000000000000000
2012/12/20 02:05:45 | -- | ERROR: AP Public ID: 35bc21063d231f528e8ce8e9b9942dcd161967c5
2012/12/20 02:05:45 | -- | ERROR: BP Public ID: 0000000000000000000000000000000000000000
2012/12/20 02:09:03 | 0 | ERROR: Phone[0000]: Error verifying Code Group 31 checksums. File: 0x9A68, Phone: 0x9C68 ->(1557)FlashOp
2012/12/20 02:09:03 | 0 | ERROR: Phone[0000]: Error verifying Code Group 32 checksums. File: 0x4805, Phone: 0x4A05 ->(1557)FlashOp
2012/12/20 02:13:03 | 0 | ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE003003F Command: RQRCS ->(1511)FlashOp
2012/12/20 02:26:03 | 0 | ERROR: Phone[0000]: Error verifying Code Group 65 checksums. File: 0x2409, Phone: 0x4A05 ->(1557)FlashOp
2012/12/20 02:26:03 | 0 | ERROR: Phone[0000]: Flash failed. ->(1195)PST_FP_FlashThread
2012/12/20 02:26:03 | 0 | ERROR: Flash failure: Phone[0000]: Error verifying Code Group 31 checksums. File: 0x9A68, Phone: 0x9C68 (Error Code: 31),
Detailed Error Details: Direction of the Error=No Direction, Command Value=4000000, Code Group Number=31 ->(625)FlashHdlr
Click to expand...
Click to collapse
Based on advice from skeevy420, I tried flashing with sbf_flash on linux.
sbf_flash:
Code:
Index[1]: Unexpected chip 32
>> Verifying CG32
Chechsum error (Expected 0x4805, Got 0x4a05)
!! failed
>> Verifying CG53
usb_bulk_write -110
!! failed
>> Verifying CG65
usb_bulk_write -19
!! failed
It looks like writing (or reading) fails, resulting in checksum errors.
More Info:
Verified MD5 of all my downloads
Tried a couple of other SBF from the same version (3.4.2)
Phone is from T-Mobile USA
Can I do something to change brick status?
Do I need a different SBF version?
Does read/write error really means hardware problem, cannot be fixed by software?
Do those IO errors mean driver version problem?
New sbf not compatible with old (old was stock T-Mobile Froyo)?
Accept the fact that the phone is hopeless?
Any help appreciated!
Here's a basic tutorial to flash sbf's with Linux -- RSDLite quit recognizing my Bravo and the Linux sbf_flash tool was the only way to fix it. You may have to install the Linux adb drivers, not sure, but those instructions are on Kayant's Compile CM10 thread (first post).
After flashing, you might have to go to factory recovery and wipe data and cache in order for the phone to boot -- maybe even have to flash a 2nd or 3rd time. I once had to flash the sbf AND wipe data\cache 5 times in a row in order to get my Bravo to boot up after accidentally flashing a Defy boot.img (usually only 1 flash is needed, I do stupid things with my phones)
Thanks, I will give this a try.
Do you install linux on the drive (like dual boot) or boot from a CD? If you boot from a CD, how do you install motorola drivers?
Just did MD5 checksum of all my downloaded files and they are all good.
Tried it with linux, getting similar errors:
Code:
>> Verifying CG32
Chechsum error (Expected 0x4805, Got 0x4a05)
!! failed
>> Verifying CG53
usb_bulk_write -110
!! failed
>> Verifying CG65
usb_bulk_write -19
!! failed
Unfortunately this error has no solution that I'm aware of, it seems like a hardware issue. Though you can try selecting the ti omap blank flash checkbox while flashing from rsd
Sent from my MB526 using xda premium
Just a silly idea: is your USB cable/PC USB port OK? Try it on another PC and with another cable. Use a cable as short as possible and make sure that the phone is the only device connected to the PC via USB including the mouse.
Sent from my MB526 using xda app-developers app
thekguy said:
Unfortunately this error has no solution that I'm aware of, it seems like a hardware issue. Though you can try selecting the ti omap blank flash checkbox while flashing from rsd
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Thanks, I think you are right.
I tried the omap option, did not help. Any other tweaks I can do to RSD light?
As far as USB, its the stock motorola cable. I disconnected everything from the computer, basically a laptop with nothing around it. I dont think its the problem, I tried over 10 sbfs and they all consistently show the same errors.
I am gonna hijack this thread...
So I believe I bricked the Defy I was supposed to be fixing.
It was acting up, the battery was sometimes showing a ? mark, and the rom it was flashed with was super buggy.
I decided to flash it with this sbf
Code:
T-Mobile_MB525_6.19.0_1FF
from here (Because I had read that it was the stock 2.1 Eclair from T-Mobile, the one the one was running originally.)
Now it won't boot.
Edit: The battery was dead. The cable was faulty so it cause a problem while flashing. Managed to get back at bootloader. Re-trying again but with:
Code:
JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.0R_JORDANTMO_P022_HWp3_Service1FF.sbf
EDIT 2: The keyboard is not working so I can't logging into motoblur ._." Frustration... Going to keep flashing to see if its the screen of my phone or the actual program.
Edit 3: It appears it was the screen sensors being dirty. All solved.
-Defy MB525 GREEN LENS-
Any solution for this??
ChavitoArg said:
Any solution for this??
Click to expand...
Click to collapse
Try This
http://forum.xda-developers.com/showthread.php?t=1486731
I am having same problems flashing my defy. Tried different kinds of sbf using rsd lite but keep getting error verifying group code checksums from code 33 onwards...then flashing fails.
Any solutions??
Error Description: send d000ff partition data failed
Info: .\RSPL\RSPL.cpp (1279)
Error Description: block send fail
Info: .\RSPL\RSPL.cpp (962)
Error Description: Block is after end.
Info: .\RSPL\RSPL.cpp (704)
im getting this error when i try to install a wp7 rom with DWI in magdlr
Lord_Azeroth said:
Error Description: send d000ff partition data failed
Info: .\RSPL\RSPL.cpp (1279)
Error Description: block send fail
Info: .\RSPL\RSPL.cpp (962)
Error Description: Block is after end.
Info: .\RSPL\RSPL.cpp (704)
im getting this error when i try to install a wp7 rom with DWI in magdlr
Click to expand...
Click to collapse
did you read install tutorial?
did you set in magldr 10. Services, 4. UseLast24NAND?
also be sure you have ActiveSync (WinXP) or WMDC (Win vista, 7/8) installed...