Help, Error verifying Code Group 33 checksums - Defy Q&A, Help & Troubleshooting

I flashed the 3.4.3-33-1 sbf, and it didn't boot at all =| It always boots into bootloader, which says:
Phone[0000]: Code Group 32 checksums match.
Phone[0000]: Error verifying Code Group 33 checksums. File:0xAB80, Phone: 0xD9D1
[...]
Failed flashing process. Phone[0000]: Error getting subscriber unit checksum. Device API Error: 0xE003003F. Command: RQRCS (0xE403203F); phone connected
Click to expand...
Click to collapse
While on the phone's screen there is the following message:
SW Update
In progress...
Click to expand...
Click to collapse
It does not boot, going straight to bootloader and no futher, regardless of the buttons I'm pressing.
I tried to change cable and use other sbf, but anything's not works!
Please help me with it problem,

Wat version of rsd do u have??
Sent from My Mind using the Brainwaves...

nogoodusername said:
Wat version of rsd do u have??
Sent from My Mind using the Brainwaves...
Click to expand...
Click to collapse
rsd - 5.3.1, drivers - 5.2.0

All this time I tried to fix it problem, but all attempts are failed, I use another computer, reinstall drivers, use second cable, nothing helps
Maybe someone know how fix this problem?
Thanks!

plz tell me
JimJack01 said:
All this time I tried to fix it problem, but all attempts are failed, I use another computer, reinstall drivers, use second cable, nothing helps
Maybe someone know how fix this problem?
Thanks!
Click to expand...
Click to collapse
Hi , plz i want to ask you, what you did to your phone with this problem, because this is happening to me now and i don't know what i should do

Related

XDA Terra stuck on wellcome screen

during upgrade, the xda terra stuck on wellcome screen, and when i want to run a rom, it goes to 1% and gives error: vender ID error.
please guys, what should i do?
btw, i tried to run the original rom, but the same. is there any utility to run with the upgrade to avoid the vender ID error?
thanks for all
Please use Forum Search before posting this, because it is mentioned a LOT in this forum. But it means that your phone is vender locked, wich means that your device is software locked. So you own a brick now...
rassien said:
during upgrade, the xda terra stuck on wellcome screen, and when i want to run a rom, it goes to 1% and gives error: vender ID error.
please guys, what should i do?
btw, i tried to run the original rom, but the same. is there any utility to run with the upgrade to avoid the vender ID error?
thanks for all
Click to expand...
Click to collapse
It is locked for all RUUs out there. It is locked by Model-ID = you can only flash a Terra RUU (and that is not the same as a Herlad RUU) YOu have to wait for an O2-Update. and that can take a long time....

3 Colour screen - no USB connection - Help!

OK, challenge for you. I have been saying how brilliant this site is, so a colleague has given me his prophet to fix.
It is stuck in the bootloader screen and only says "IPL 2.10.0001" and "SPL 2.G3" - yes I have identified the problem here as it is a G4 device...
However, I can't get the PC to recognise the device through the USB cable, so I'm not sure what else I can do. I have hard reset the device and got activesync running on the PC, but now I'm stuck...
Ramsfan_Jim said:
OK, challenge for you. I have been saying how brilliant this site is, so a colleague has given me his prophet to fix.
It is stuck in the bootloader screen and only says "IPL 2.10.0001" and "SPL 2.G3" - yes I have identified the problem here as it is a G4 device...
However, I can't get the PC to recognise the device through the USB cable, so I'm not sure what else I can do. I have hard reset the device and got activesync running on the PC, but now I'm stuck...
Click to expand...
Click to collapse
hey.... sorry for my previous post... ( I had it edited.)
your G4 device seems to be flashed with a G3 image.
Your device needs a heart transplant. (we cannot revert the wrong SPL flash with software tool at the moment.)
OK, I've been through that thread http://forum.xda-developers.com/showthread.php?t=353547 in full (I admit I stopped reading the first time when it said use Activesync).
I also discovered it only seems to flash from USB ports on one side of my laptop and not the other?!
I downloaded and tried PVTemp: I get ERROR [300] INVALID UPDATE TOOL
I tried http://v-dog.net/XDA/RUU_Prophet_220734_2207114_024721_NVID.zip NVID for Prophet: I get to 80% updating, then it stops with ERROR [326]: INVALID COMMAND - This NBF file cannot be used for your PDA Phone. Please check you NBF file.
I tried Upgrade HardSPL_G4: I get ERROR [300].
I tried RUU_Prophet_220734_2207114_024721_NVID utility. I get to 80% again - same problem ERROR [326].
Any more ideas?
Ramsfan_Jim said:
OK, I've been through that thread http://forum.xda-developers.com/showthread.php?t=353547 in full (I admit I stopped reading the first time when it said use Activesync).
I also discovered it only seems to flash from USB ports on one side of my laptop and not the other?!
I downloaded and tried PVTemp: I get ERROR [300] INVALID UPDATE TOOL
I tried http://v-dog.net/XDA/RUU_Prophet_220734_2207114_024721_NVID.zip NVID for Prophet: I get to 80% updating, then it stops with ERROR [326]: INVALID COMMAND - This NBF file cannot be used for your PDA Phone. Please check you NBF file.
I tried Upgrade HardSPL_G4: I get ERROR [300].
I tried RUU_Prophet_220734_2207114_024721_NVID utility. I get to 80% again - same problem ERROR [326].
Any more ideas?
Click to expand...
Click to collapse
hey.... sorry for my previous post... ( I had it edited.)
your G4 device seems to be flashed with a G3 image.
Your device needs a heart transplant. (we cannot revert the wrong SPL flash with software tool at the moment.)
dioxda2 said:
hey.... sorry for my previous post... ( I had it edited.)
your G4 device seems to be flashed with a G3 image.
Your device needs a heart transplant. (we cannot revert the wrong SPL flash with software tool at the moment.)
Click to expand...
Click to collapse
Is there a reason for this? Just to aim my understanding, the device has presumably at some point been flashed with incorrect software (there is no known hardware issue), so shouldn't it just be a question of re-flashing with the correct software?
I am used to working on mainframe and PC software, so pardon my ignorance when it comes to mobile technology. Isn't it just a case of rebuilding the operating system somehow?
dioxda2 said:
hey.... sorry for my previous post... ( I had it edited.)
your G4 device seems to be flashed with a G3 image.
Your device needs a heart transplant. (we cannot revert the wrong SPL flash with software tool at the moment.)
Click to expand...
Click to collapse
I'm in the sames circunstances than the post before.
Heart transplant the only solution? Some new updated proccess for recovery?
I'm very worried.
hi,
Yesterdayi I was dealing with the same problem.
I've got i-mate Jamin.
I solve it by flashing my pda with thisrophet_PV_Temp.
http://rapid+share.com/files/156034341/Prophet_PV_Temp.rar.html
Your pda will turn to wm5 rom. Than you can upgrade to wm6 Roms.
Hope this can be helpfull.
Note: rapid+share = rapidshare

[Q] Need HELP, tried to flash nordic sbf, defy only goes to boot loader

Hi All
i need some help if anyone could give me some advice it would be much appreciated.
i have tried to flash my defy with nordic sbf.
followed the instructions,
1. download drivers, rsd lite 4.7 and 4.9 (tried with both), nordic sbf
2 installed drivers and rsd lite
3 unzipped nordic sbf
4 started rsd lite and selected nordic sbf file
5 pluged in defy via usb and clicked start
as it was flashing, it came up with fail!
"error verifying code group 39 checksums. file: 0x558B, Phone: 0xF0C3( 0x4007031);"
now my defy only goes to a black screen with bootloader at the top "09.10"
is there anything i can do????can any please give me some advice please
Your sbf file could-be corrupted.
I suggest you to download a new one and flash it with rsd 4.9.
Hope it can help you.
thnaks for your reply
thanks for your reply MisterWB
i have tried other sbf files already. still no luck
it saids something about HAB error 0x8D
also my defy screen saids Criticalerror: DEA1
really freaked out now!
seeker3000 said:
thanks for your reply MisterWB
i have tried other sbf files already. still no luck
it saids something about HAB error 0x8D
also my defy screen saids Criticalerror: DEA1
really freaked out now!
Click to expand...
Click to collapse
um... if you can extract the zip, it seems the sbf is not corrupted.
maybe you could go to stock recovery first (volume down+power),
wipe data and wipe cache, reboot.
try to flash sbf again.
ive tried that...
i think now its totally BRICKED...
there is no response from it, when i plug usb it charges but thats it.
man...looks like i need a phone
http://modmymobile.com/forums/31-rizr-z3/51338-critical-error-dea1.html
there you'll find another couple of links for Mac Gyver's remedies.. but they're for other moto phones, not specific for Defy, so i actually don't know what you can do.
Someone in that site wrote:
DEA1
'' CRITICAL ERROR DEAD '' means ur phone chip flash died , so u cant flash any more
Click to expand...
Click to collapse
Bad luck, but what about the warranty?
Despite your Defy is not "original" anymore i would try to send it to moto's assistance. Many of the times they just replace the bricked phone w/o many investigations..
Hi, today i was trying the same. Nordic sbf with rsd lite 4.9 and it could not be flashed till end... "Error verifying Code Group..." and similars in log file.
I dont have any critical error or HAB error yet.
Any further idea?
Battery charged?
If yes, then go to recovery (power button + volume down) wipe data/wipe cache and reflash nordic sbf with rsd lite.
Nordic sbf: LINK
vazzz said:
Battery charged?
If yes, then go to recovery (power button + volume down) wipe data/wipe cache and reflash nordic sbf with rsd lite.
Nordic sbf: LINK
Click to expand...
Click to collapse
Yes battery up, but recovery mode does not accessible!
I have also downloaded the same nordic sbf with rsd lite.
talabzs said:
Yes battery up, but recovery mode does not accessible!
I have also downloaded the same nordic sbf with rsd lite.
Click to expand...
Click to collapse
not accessible? why? black screen?
vazzz said:
not accessible? why? black screen?
Click to expand...
Click to collapse
I press volume down first, then power button. It remains black, however i see the backlight is turned on after i press power on of course. If i release power first, the same screen appears as mentioned (bootloader 09.10, code corrupt, ... USB), this one is the normal bootloader mode by the way (power on, while pressing volume up). So and if i release volume down first, of course it happens nothing, backlight is still on.
I think the flash is corrupted somewhere, as assumed RSD Lite log:
"
15:27:30, May 08, 2011
Line: 527
ERROR: AP Die ID: 0da000040b8860010000d8ff2100
15:27:30, May 08, 2011
Line: 534
ERROR: BP Die ID: 0000000000000000000000000000
15:27:30, May 08, 2011
Line: 541
ERROR: AP Public ID: 71879d82f813f8d2c553dd35e1ad10e2bb4fe225
15:27:30, May 08, 2011
Line: 548
ERROR: BP Public ID: 0000000000000000000000000000000000000000
15:34:28, May 08, 2011
Line: 1263
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE003003F Command: RQRCS
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
15:34:28, May 08, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 33 checksums. File: 0x1F42, Phone: 0x4805
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
15:36:53, May 08, 2011
Line: 1263
ERROR: Phone[0000]: Error geting subscriber unit checksum. Device API Error: 0xE0030040 Command: RQRCS
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
15:36:53, May 08, 2011
Line: 1309
ERROR: Phone[0000]: Error verifying Code Group 34 checksums. File: 0xAB80, Phone: 0x4805
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\FlashOp.cpp
Device ID: 0
"
hey...
i have the same exact problem as you have/had..
did you get a fix??
i'm still trying..
http://www.megaupload.com/?d=C7DMWX8S
Here you have RSD Lite v5 (the last 1 i think) and motorola drivers....both of them are working (tested myself).....install these then try to reflash nordic
I guess no1 of you had gingerbread installed (leaked GB not miui or cm7)
just got JORDN_U3_97.21.51 to work.. with a fresh download and a fresh pc!!
that just made my day!
but... when i tried to wipe everything and then flash the Nordic rom suggested.. i get a black screen and nothing to work..
any ideas?
None of you guys ever heard of the flashing downgradability issues??
That is not only between froyo and eclair: if you flash a newer froyo sbf, you can't flash the old after and would likely get black screen or boot loops.
Flashing a new signed sbf is not a game and you should learn a few things first.
This seems like good place to ask my question. After my phone bricked and would only go to the bootloader screen like the guys above I took it to Motorola who said I needed a new motherboard.The new motherboard had 2.2 already loaded, now I would like to go to the Nordic rom but I am worried that my 2.2 will be newer and I will end up with the dreaded black screen our stuck on the Moto logo if I try to flash Nordic. Is there something I can look at to determine if I can go to Nordic from my current rom?
Sent from my HTC Desire using XDA Premium App
vazzz said:
Battery charged?
If yes, then go to recovery (power button + volume down) wipe data/wipe cache and reflash nordic sbf with rsd lite.
Nordic sbf: LINK
Click to expand...
Click to collapse
jst a quick question ... is it GB or Gingerbread and if i flash it ... .can i get back to stock 2.2.2 froyo ? cause i m already running stock GB by shadow 134 built ..... so please tell me if i can go back to 2.2.2 or not after i flash it ....
i know its basic but maybe someone forgot it.
when you flash with rdslite make sure the sbf's name is not too long because then the software cant flash the sbf properly
joydeep1985 said:
jst a quick question ... is it GB or Gingerbread and if i flash it ... .can i get back to stock 2.2.2 froyo ? cause i m already running stock GB by shadow 134 built ..... so please tell me if i can go back to 2.2.2 or not after i flash it ....
Click to expand...
Click to collapse
if u have flashed an GB sbf then u r stuck..if u have done nand backup then sure u can go back..
but i heard there is special eclairs sbf which can be flashed over leaked sbf..google around
arpith.fbi said:
if u have flashed an GB sbf then u r stuck..if u have done nand backup then sure u can go back..
but i heard there is special eclairs sbf which can be flashed over leaked sbf..google around
Click to expand...
Click to collapse
no its a nanodroid backup that i am pretty sure i can go back. but not sure which rom is this . is it a Custom GB rom or else its a froyo (custom) rom . so thats why asking . cause some people over here flashed cm7 over nordic froyo and they are getting amazing battery life around 4 days . though not sure if this is link only which he mentioned above as per the discussion.. sorry for being little off topic !!

HD2 Wont boot, need help

Hi guys,
First of all, maybe this is a hardware problem, not sure, becouse I afraid that i got broken HD2. When it came, it was powerer ON, and everything was working, but when I turned it off so I can insert my SIM Card, it dont boot any more. All I get is white screen.
What I tried allready.
1. I installed MAGLDR first time with no problem.
2. I used USB Flasher option to flash ClockWorkMod 150MB file from here http://forum.xda-developers.com/showthread.php?t=898913
3. I downloaded this rom file http://forum.xda-developers.com/showthread.php?t=769026 to my sd card, and installed it from recovery. There was no problem so far, installation was ok, but when phone rebooted, i got message Nand kernel error...
4. Then I read that i need to do task 29 first, and start all over again. I used HD2toolkit for that, downloaded it from forum, and did task 29 no problem. But affter that, a cant install MAGLDR no more. A always get error 270 - image was corupted!!!
And thats it. Now I only have white screec.
Volume down + power works, so I can enter tri colour.
I have HSPL 2.08 on phone. I tryed to reinstall it, and it works (I get message on my pc that says succsess, but on phone there is no "we hacked it", so not sure if this do anything).
Radio is 2.15.50.14.
I read 7-8 hours yasterday here, and coudn't find nothing more than this things i already tried. I found something about SPLXPLOIT but cant make it work on windows 7 (not sure should I even do this).
Help wanted.
Thank you in advanced.
in tri-color screen do you see 'usb' at bottom? you should flash mgldr in tri-color screen.do you do so?
Yes, it is first serial, but when I conect it to PC it is USB.
On the phone progres bar go from 0 to 100% instant, and then phone restart, but I just got white screen. On pc i got message from hd2Toolkit error 270 - image is corrupted.
Thanks
As always, in these cases, I suggest you reinstall the stock firmware using the SD-card trick.
Yes, it'll reset your SPL and everything else, but if it boots, then it means everything is working fine (so it's not a hardware problem), and you can start "rebuilding" your Android OS.
Also, make sure to copy Android ROM ZIP files by mounting the SD card directly to your PC, rather than use the USB option, which is known to cause corruption at times.
Any link for this?
No sure what i have and what i havent tried.
Thanks.
can you try downloading and installing toolkit.maybe some parts of it are corrupted.
I just tried sd card update to default rom, but got this message in attachemnt.
Any ideas?
vlastem said:
I just tried sd card update to default rom, but got this message in attachemnt.
Any ideas?
Click to expand...
Click to collapse
dont choose 'update from sdcard'.but ad recovery-install zip from sd-choose zip from sd- then choose your rom.zip. and reboot
Not going to work becouse I canot install even MANGLDR any more.
When I tried to do that, I Get message in attachemnt.
vlastem said:
Not going to work becouse I canot install even MANGLDR any more.
When I tried to do that, I Get message in attachemnt.
Click to expand...
Click to collapse
can you try the attached mgldr. connect phone to pc,in tri-color screen see 'usb'. unrar the attached file.right click on Rom update utility .exe. run as administrator.
Did try this right now.
In first screen it says readme.txt is missing, but I can click next.
In next screen i got this massage
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 run it as administrator. Widows 7 bussines, 32-bit
vlastem said:
Did try this right now.
In first screen it says readme.txt is missing, but I can click next.
In next screen i got this massage
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 run it as administrator. Widows 7 bussines, 32-bit
Click to expand...
Click to collapse
sorry i was wrong.you must right click on rom update utility exe when you are in tri color screen (i havent done this for a long time)
is that radio supported by MAGLDR?
Try using the 2,08 radio and see if that helps
Thank you all for help.
I tried everything that I found here, but nothing helped.
I took it to service two days ago, we will see what they will say.
Will keep you informed.
Thx
Same problem...
What did you get from them??
Share the info, plz.
Thanks in advance.
Will upload microscope pictures tonight.
Bad stuff this is.
No hope for mine, hardware, pipple put glue on motherboard, it worket for some time, but no more.
Try reflash radio with task29)
vlastem said:
Will upload microscope pictures tonight.
Bad stuff this is.
No hope for mine, hardware, pipple put glue on motherboard, it worket for some time, but no more.
Click to expand...
Click to collapse
Hi, same problem here radio bricked i think, bootloader works fine but nothing more, nothing can eb flashed, every time error 270... İm reserching 2 days but nothing has changed...

LG Spirit H440N Security Error

Hello everyone,
I got this error suddenly(I tried to unlock my phone to make a call and there it was). I have already tried to flash the phone, but after completion the error remains. Also I tried to do factory restore but after final confirmation I just get android robot with red triangle... Any other suggestions that i should try or to take my phone to local service?
Thanks in advance
How exactly does the error look? Please be more descriptive. Can you take a picture of it?
Fobos531 said:
How exactly does the error look? Please be more descriptive. Can you take a picture of it?
Click to expand...
Click to collapse
When I try to boot the phone, first shows lg logo as it normally does but after a few seconds it shows again lg logo and "Security error" below. After that the phone resets and same thing goes on and on, until I remove battery...
What exactly did you try flashing? Flashing a stock firmware should usually resolve the problem.
Fobos531 said:
What exactly did you try flashing? Flashing a stock firmware should usually resolve the problem.
Click to expand...
Click to collapse
That's exactly what I tried but the problem remains after successful flashing... Anyway I left my phone to service I 'll let you know if they succeed. Thank you for replies
As I promised, just to inform you that even the guys from service haven't succeed They only told me that it's impossible to repair it...
Help me please
gagiii84 said:
As I promised, just to inform you that even the guys from service haven't succeed They only told me that it's impossible to repair it...
Click to expand...
Click to collapse
I have the same problem, I cannot enter download mode. Please find some solution?

Categories

Resources