Database Users

[Q] stuck in manaul guideBack to the Future [XBmod-Yuki] [7720 ready]

i don't know what to do
in step 13
when i press 's' i got error messege in red
error:
update device fa9e0019 - adfd74d6 - ea5e52ec - 3b39c693 complete with error code: 80188222, error message: Phone Update Agent Error: The preinstallation update package <or sperpackage> isn't valid
i carfully do step by step ... what i should do?

Flashing failes everytime I try to flash. Rsdlite error included

This was my first time.
I did all what was required.
But when I started the flash through RSD lite after just 1 min it showed me FAIL
It went from 1% to 100% once, and then it showed FAIL
Now when I unplugged the USB and remove the battery and insert it back again it automaticaly goes into bootloader and then I tried to flash again which gave me same result.
This is my phone status.
The screen shows
Code Corrupt
Battery OK
OK to Program
Trasnfer Mode:
USB
This is what the Rsdlite Error log file has.
22:32:29, May 13, 2012
Line: 537
ERROR: AP Die ID: 1140010e560368010000dcff0200
22:32:29, May 13, 2012
Line: 544
ERROR: BP Die ID: 0000000000000000000000000000
22:32:29, May 13, 2012
Line: 551
ERROR: AP Public ID: 785fdd0a961a8e4b1e6a0497d703ee271d20c5c0
22:32:29, May 13, 2012
Line: 558
ERROR: BP Public ID: 0000000000000000000000000000000000000000
22:32:29, May 13, 2012
Line: 709
ERROR: Phone[0000]: Error erasing subscriber unit. Device API Error: 0xE0030040 Command: ERASE
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\ErasingOp.cpp
Device ID: 0
22:32:29, May 13, 2012
Line: 1195
ERROR: Phone[0000]: Flash failed.
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\PST_FP_FlashThread.cpp
Device ID: 0
22:32:29, May 13, 2012
Line: 610
ERROR: Flash failure: Phone[0000]: Error erasing subscriber unit. Device API Error: 0xE0030040 Command: ERASE (Error Code: e0030040),
Detailed Error Details: Direction of the Error=2000, Command Value=100000, Code Group Number=No Codegroup
File: D:\GitProjectsReleases\hdt_windows_flash\flash\code\flashdll\FlashHdlr.cpp
Device ID: 0
Click to expand...
Click to collapse
Please someone reply asap.

use the recommened rsdlite version...i have seen many other version of rsdlite gives such errors..i actually dont remember the exact version ..haven't used it for a while..
do a search in this forum..
All the best

I have read few other places and it said to use RSDLITE 4.9, which I did.

try version 3.4.8 if m not wrong..

Which one do you used for flashing?

i think the above version only..i have recommended the same version to many people and it works like a charm in past..search this forum for rsdlite stable version by experience of people..

I did successfully flash my Defy+ with RSDLite v5.6 (search the forum or google)
Maybe there's something wrong with your sbf-file? Just a wild guess, don't know if the error message tells actually something different...

Thanks for your time guys. I was trying to flash on my Desktop with no avail.
Tried on my lappy and Bingo its all done perfectly.
Happy I have finally upgraded to CM7 its really nice and fast.

[Q] Officially Bricked?

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??

[Q] Carrier Unlock enable Wifi Tethering

I've had this phone since launch, and am really frustrated that I can't do Wifi tethering with it since the Mango udpate was supposed to enable it.
I'm now running 7.8 and was wondering if Carrier unlocking would allow wifi tethering.
I'm running firmware version 402... which is different than the 403... listed on the forums. I tried installing 403... using cab sender, but it always failed (can't remember the error code off the top of my head). I've also seen reference to a 405... firmware, but never found a download link.
Any help/insight would be great.
Thanks

This is the error I was recieving when trying to update to 403...:
================================================
START OF UPDATEVALIDATOR ERROR MESSAGES
================================================
ERROR: The AddNode failed to add the package \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\B846875E-7FCE-49B8-B0FE-D07255E5C5A7.1.pks\operatorpkg.cab.pkg. AddNode returned HRESULT: 0x80180013
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\B846875E-7FCE-49B8-B0FE-D07255E5C5A7.1.pks\MediaShare.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.40300.502 GUID = {D0A76E3C-03D7-4405-9D2B-F44ECE1384EE}
ERROR: E_CANNOT_UPDATE_TO_HIGHEST_VERSION: CreatePaths: For package named: MediaShare cannot find a path to highest expected version of: 2250.21.40300.502
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\B846875E-7FCE-49B8-B0FE-D07255E5C5A7.1.pks\HTC_CSPOSDrivers.cab.pkg FROM Version: 0.0.0.0 TO Version: 2250.21.40300.502 GUID = {25ADC390-4241-4CF4-A6FB-6482DFFF8C9C}
ERROR: E_INVALID_SIGNATURE:
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\B846875E-7FCE-49B8-B0FE-D07255E5C5A7.1.pks\CSConn_DB.cab.pkg FROM Version: 0.0.0.0 TO Version: 7.0.2011.7281 GUID = {89C1A350-7F48-4AB3-A5F8-F0E734A4E7B7}
ERROR: UpdateOrderFromFileList: MAIN OS Update: MAIN OS Update Failed with HRESULT : 0x80180048
=====================================================================
GOOD PACKAGES AND BAD PACKAGES LIST
=====================================================================
UpdateOrderFromFileList failed with code 0x80180048
BAD PACKAGE: operatorpkg.cab.pkg ERROR CODE: 0x80180013 BAD PACKAGE: MediaShare.cab.pkg ERROR CODE: 0x80180008 BAD PACKAGE: HTC_CSPOSDrivers.cab.pkg ERROR CODE: 0x80180008 BAD PACKAGE: CSConn_DB.cab.pkg ERROR CODE: 0x80180008 Total number of Bad Packages: 4
Process Failed with code 0x80180048
UpdateValidator finished at 08:07:32 01/06/1980

[Q] Errors when attempting to SBF reset

So I Found my old Droid X earlier this week the battery was bad so I got a new one and I attempted to restore the device using tomsgt123's (RootJunky) video (I can't post links ) and RSDlite must have froze on me because it got stuck and 98% of something to do with ram (I can't find a log so I can't rely be more specific) and then I let it sit thinking it was just taking a while and I came back nothing was on the program and my device just says code corrupted battery low cannot program.
So what I am wondering is if I can retry If i can manage to get the battery charged or if this thing just became a brick
I should also mention that when I pressed start on RSDlite my battery was fully charged
Thank You in advance if you can help me.
Edit I found a log actually
2014/07/04 10:51:29 | -- | ERROR: AP Die ID: 1e300210fa903a0a0000d8ff0100
2014/07/04 10:51:29 | -- | ERROR: BP Die ID: 0000000000000000b55432890485
2014/07/04 10:51:29 | -- | ERROR: AP Public ID: 2469367a1407acd048a3f1e89f054bd90523fa08
2014/07/04 10:51:29 | -- | ERROR: BP Public ID: 040000000500000002000000ffff00002d003289
2014/07/04 11:14:29 | 0 | ERROR: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x156000 Command: ADDR ->(970)RDLOp
2014/07/04 11:14:29 | 0 | ERROR: Phone[0000]: Flash failed. ->(1195)PST_FP_FlashThread
2014/07/04 11:14:31 | 0 | ERROR: Flash failure: Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE003003F Address: 0x156000 Command: ADDR (Error Code: e003003f),
Detailed Error Details: Direction of the Error=2000, Command Value=200000, Code Group Number=257 ->(625)FlashHdlr

Motorola Drivers are not installed on windows.
Install drivers or use DX (MB810) ezSBF & Root 2.3.4/4.5.621

Ill Try
Ok, Thanks I thought I had the drivers installed already though as Ive already done some work on other motorola devices this week. But I'm ordering a battery charger should be here in a couple days and I'm going to try the live CD method Ive already burned the CD so Thanks