Database Users

[Q] Help, stuck in bootloader

I have two Defys. One flashed ok and works fine. But not the other one. I flashed stock 2.2 (can't remember which exactly), but on the second phone it was somewhat unstable, slow, throwed UUID inconsistency errors... It was rooted just after flashing, so I don't know exactly if it was problem of sbf or root. And I couldn't get into recovery menu to wipe. Since on the first phone everything worked fine, I thought something went wrong and re-flash will help. So I flashed the same sbf, and it didn't boot at all =| It always boots into bootloader, which says
Code:
Bootloader
09.10
Code Corrupt
Battery OK
Ok to Program
Transfer Mode:
USB
Tried other firmwares, but RSD Lite says
Code:
Phone[0000]: Code Group 32 checksums match.
Phone[0000]: Error verifying Code Group 33 checksums. File: 0x9D6, Phone: 0x4805
[...]
Failed flashing process. Phone[0000]: Error getting subscriber unit checksum. Device API Error: 0xE003003F. Command: RQRCS (0xE403203F); phone connected
While on the phone's screen there is the following message:
Code:
SW Update
In progress...
Tried to flash just bootloader, same errors... Tried to change cable and even computer — no luck =[
So I'm pretty confused =| Is it software or hardware problem? Can I send it back to seller to fix it? What can be done?

Hey me too!
I'm also stuck in here...
I hope that there are some method to solve this ploblem

If something went wrong and you stuck in a bootloop etc, shutdown the system (if possible) or pull out the battery.
-Go into the system recovery with "vol down + power".
-Then when you see the android update guy press vol down + vol up at the same time.
-Wipe your phone + factory reset.
-Reboot and hold "vol up + power"
-You are now into bootloader mode, reflash the system with RSD Lite and a sbf you like
-Your Defy is back in biz

ifu said:
If something went wrong and you stuck in a bootloop etc, shutdown the system (if possible) or pull out the battery.
-Go into the system recovery with "vol down + power".
-Then when you see the android update guy press vol down + vol up at the same time.
Click to expand...
Click to collapse
nothing happens here pressing vol+/- at the same time... if I tap the lower right corner I see the normal recovery, it's what you're referring to?
ifu said:
-Wipe your phone + factory reset.
-Reboot and hold "vol up + power"
-You are now into bootloader mode, reflash the system with RSD Lite and a sbf you like
-Your Defy is back in biz
Click to expand...
Click to collapse

ifu said:
If something went wrong and you stuck in a bootloop etc, shutdown the system (if possible) or pull out the battery.
-Go into the system recovery with "vol down + power".
-Then when you see the android update guy press vol down + vol up at the same time.
-Wipe your phone + factory reset.
-Reboot and hold "vol up + power"
-You are now into bootloader mode, reflash the system with RSD Lite and a sbf you like
-Your Defy is back in biz
Click to expand...
Click to collapse
This act I know...but not in this case
Firstly I can't go to recovery mode moreover..(even I hold vol down + power how long..)
Then I can't go on the step as you listed...
I just stuck in Bootloader mode automatically when i put in the battery..
Is there any reset solution or some method to fix the "Error verifying Code Group xx checksums"?
Thanks

kix_k9 said:
This act I know...but not in this case
Firstly I can't go to recovery mode moreover..(even I hold vol down + power how long..)
Then I can't go on the step as you listed...
I just stuck in Bootloader mode automatically when i put in the battery..
Click to expand...
Click to collapse
Exactly. It does not boot, going straight to bootloader and no futher, regardless of the buttons I'm pressing.
But one day the miracle has happened I routinely connected the phone to my laptop, preparing to flash it one more time. Inserted half-charged battery from my second phone, just as usual. But before I started RSD I was shocked by vibration meaning my "bricked" phone had booted just fine!
I launched Clockwork recovery and installed its recovery system. However, when I tried to boot into it, it didn't and booted as usual. I tried once more with the same result. Then I tried to boot into default recovery menu (power + volume down) and succeded. As I had those UID errors messages, I decided to wipe as those messages suggested. After that completed and my phone booted successfully (being a triumph as I considered it to be dead), I still got those UID errors =\
I booted into bootloader to see if there is still "Code corrupt" error, and to my pleasure, it wasn't. Nothing to lose, I thought, and tried to flash 3.4.3-11 SBF. And... now I'm back in bootloader with "Code corrupt" error and without any idea what's happening =| But at least I know the phone can boot (and can't figure out how to make it do so =)) Will do more research soon.
P.S. Curiously, RSD couldn't detect "resurrected" phone unless in bootloader (my second phone is deteted even being not in bootloader), and I don't remember exactly, but I think I couldn't turn it into USB mass storage mode — it just reverted back to Motorola Phone Portal mode.
Any ideas?

Hi Shevchuk
I had the same problem a couple of weeks ago that my defy stuck on that screen and I wasn't able to flash it.
As my Defy was rooted I tried it to fix it at my own. I tried a lot, different PCs with different OS and different versions of RSD but nothing worked. So I decided one day to call the motorola support hotline and told them that it got stuck on that screen without mentioning that it was rooted and that I tried to flash it. Finally, they told me to send it in.
After two weeks I got my Defy back and it was working. They said that something was broken and exchanged that part

Code Corrupt is not a pds problem... but a simple "bad flash" problem
pds one will reboot the device after logo...
for pds problem :
if you have 2 defys you can maybe do it...
first you need to flash the same SBF on both devices
then with adb shell (as root) you need to extract the fully working system partition (with the signature flag) :
dd if=/dev/block/system of=/sdcard/CG39.ext3.smg
this image will be mountable (and modifiable) on a linux machine :
mkdir ~/system
mount -o loop -t ext3 CG39.ext3.smg ~/system
cd ~/system
you will be able to install bootmenu inside the image, then repack a sbf with this "tuned" CG39... and to lock boot before the /pds check, which can reboot device
and with bootmenu, you can flash cm7 with the recovery

I have the same problem code corrupt but nothing to ay

crub55 said:
I have the same problem code corrupt but nothing to ay
Click to expand...
Click to collapse
Did anyone of you ever find a solution I have the exact same problem.

I have same problem
Epsylon3 said:
Code Corrupt is not a pds problem... but a simple "bad flash" problem
pds one will reboot the device after logo...
for pds problem :
if you have 2 defys you can maybe do it...
first you need to flash the same SBF on both devices
then with adb shell (as root) you need to extract the fully working system partition (with the signature flag) :
dd if=/dev/block/system of=/sdcard/CG39.ext3.smg
this image will be mountable (and modifiable) on a linux machine :
mkdir ~/system
mount -o loop -t ext3 CG39.ext3.smg ~/system
cd ~/system
you will be able to install bootmenu inside the image, then repack a sbf with this "tuned" CG39... and to lock boot before the /pds check, which can reboot device
and with bootmenu, you can flash cm7 with the recovery
Click to expand...
Click to collapse
I have same problem and i can't slove it please help me follow this quote.
I have one defy and I don't know how to do it.

Please ask all questions in the Q&A section. Thread moved there.

Worked For Me
Shevchuk said:
I have two Defys. One flashed ok and works fine. But not the other one. I flashed stock 2.2 (can't remember which exactly), but on the second phone it was somewhat unstable, slow, throwed UUID inconsistency errors... It was rooted just after flashing, so I don't know exactly if it was problem of sbf or root. And I couldn't get into recovery menu to wipe. Since on the first phone everything worked fine, I thought something went wrong and re-flash will help. So I flashed the same sbf, and it didn't boot at all =| It always boots into bootloader, which says
Code:
Bootloader
09.10
Code Corrupt
Battery OK
Ok to Program
Transfer Mode:
USB
Tried other firmwares, but RSD Lite says
Code:
Phone[0000]: Code Group 32 checksums match.
Phone[0000]: Error verifying Code Group 33 checksums. File: 0x9D6, Phone: 0x4805
[...]
Failed flashing process. Phone[0000]: Error getting subscriber unit checksum. Device API Error: 0xE003003F. Command: RQRCS (0xE403203F); phone connected
While on the phone's screen there is the following message:
Code:
SW Update
In progress...
Tried to flash just bootloader, same errors... Tried to change cable and even computer — no luck =[
So I'm pretty confused =| Is it software or hardware problem? Can I send it back to seller to fix it? What can be done?
Click to expand...
Click to collapse
I know i might sound stupid. But i had the same problem, i kept my phone untouched for a few days. And after that i usually came to try another SBF file but my phone Turned on magically, I still dont know how it happened, but it did. There is some way to fix it, but cant figure out how.

Did anyone find a solution to this problem??

[Q] a problem withe recovery "ERROR: ERROR: Cannot read ramdisk image"

Hello,
I am running android 2.3.7 [typhone v3.6.9- magldr]. I wanted to upgrade my rom, so I got into magldr and then to recovery, but when I choose "ad recovery" I get an error massage in red "ERROR: ERROR: Cannot read ramdisk image "
plese help ...
How can I solve this problem ?
thank's

Reflash recovery and then see it it's reproduces or not.

If you have do a task29,you have to reflash MAGLDR and the recovery who is needed for this ROM.Task29 delete MAGLDR and Recovery.

Maybe you need reflash your device recovery.

You really don't have to task29 your device.
Just download HD2 Toolbox, connect your HD2 to your PC and hit update in the left corner.
Thats it

[Q] unable to flash new roms

Hi All,
I have this device for a long time and I have flashed many roms...
Suddenly it's not possible to enter the "AD Recovery" in Magloader ClockworkMod Recovery.
it stuck after "1234 GO GO GO!"
I have tried the following:
1) Re-flash MAGLDR1.13.
2) Repartition with HD2Toolkit (I have European device so I repartition to 200)
Any suggestions?

Flash win mobile 6.5 and then flash magldr again
Sent from my HTC HD2 using Tapatalk 2

Hi All,
I m trying to go back from android to winmobile and my device is stuck...
In bootloader (3 colors) i have the following error: "upgrade rom code error please try again"
I have tried to flash different winmobile roms include RUU_Leo_S_HTC_WWE_3.14.405.2_Radio_15.42.50.11U_2. 15.50.14_LEO_S_Ship and i have tried to flash HAED SPL 4 and i received error in device id...
In bootloader it appears correctly with SPL-2.08.HSPL 8G XE, and in the white eare it write Serial in in the begining and when I try to flash it change to USB.
The main problem is that I have tried to flash Energy.Leo.21916.Sense2.5.Jul.04 above android it stuck on 4% and I can't reflash anymore, when i try to reflash it stuck on 0% no matter what I do.
In bootloader (3 colors) i have the following error: "upgrade rom code error please try again"
Please advice...

sagytb said:
I have this device for a long time and I have flashed many roms...
Suddenly it's not possible to enter the "AD Recovery" in Magloader ClockworkMod Recovery.
it stuck after "1234 GO GO GO!"
Click to expand...
Click to collapse
Been having the exact same problem (http://forum.xda-developers.com/showthread.php?p=29868470#post29868470) still noone with any ideas how to fix this?

After Flashing android 4.3 ERROR com.andorid.phone stopped

the problem is with Pepephone spanish carrier, i found a fix
http://www.elgrupoinformatico.com/s...droid-phone-android-con-pepephone-t16852.html
[SOLVED]
hi all, i flash latest paranoid android rom, andorid 4.3 , first thing i notices is the first boot, i stuck on boot logo, and i need to reboot, when phone start , i put sim card pin, and errror appear , com.android.phone stopped, i asking for advice in PA page on g+ , all people say reflash... wipe... i do all thing posible, so i tried to flash other rom, stock rom, and i have one more time the first boot problem, (stuck in boot logo) and then com.andorid.phone ERROR
please i need help what can i do??

orti13 said:
hi all, i flash latest paranoid android rom, andorid 4.3 , first thing i notices is the first boot, i stuck on boot logo, and i need to reboot, when phone start , i put sim card pin, and errror appear , com.android.phone stopped, i asking for advice in PA page on g+ , all people say reflash... wipe... i do all thing posible, so i tried to flash other rom, stock rom, and i have one more time the first boot problem, (stuck in boot logo) and then com.andorid.phone ERROR
please i need help what can i do??
Click to expand...
Click to collapse
Ok i had similar issue with stuck on boot logo. Here is fix. ITS SUPER SIMPLE
1. Go download newest SDK developer dot android dot com/sdk/index.html (New on forums so i can't post links)
2. Unzip sdk and naviagte to sdk/platform-tools
3. Use the fastboot and adb program in this folder to fastboot over your new rom.
For me I was rooted on 4.2.2 AOKP and everytime i flashed rom it would succeded but then fail to boot. Read somewhere on google that using old version of fastboot/adb can cause the issue. Updated and eveything worked flawlessly.

dhruvb14 said:
Ok i had similar issue with stuck on boot logo. Here is fix. ITS SUPER SIMPLE
1. Go download newest SDK developer dot android dot com/sdk/index.html (New on forums so i can't post links)
2. Unzip sdk and naviagte to sdk/platform-tools
3. Use the fastboot and adb program in this folder to fastboot over your new rom.
For me I was rooted on 4.2.2 AOKP and everytime i flashed rom it would succeded but then fail to boot. Read somewhere on google that using old version of fastboot/adb can cause the issue. Updated and eveything worked flawlessly.
Click to expand...
Click to collapse
Thanks i will try , bit my principal problema now is when i flash stock ROM i lost CMW recovery so now i have android 4.3 without root without recovery and with android.phone error ... And i dont know exatcly what to do????
I really need help

orti13 said:
Thanks i will try , bit my principal problema now is when i flash stock ROM i lost CMW recovery so now i have android 4.3 without root without recovery and with android.phone error ... And i dont know exatcly what to do????
I really need help
Click to expand...
Click to collapse
This is easy. Turn on phone with power and vol down buttom pressed. When on the bootloader screen plugin to computer and use fastboot to sideload custom recover.
(./fastboot sideload ziptosideload.zip)

Big Trouble, phone bricked no solution found...

Hello!
I am a new to this forums so bare with me please
i have bricked my phone badly.., i tried to install the ota update for P10 Plus (VKY-L29C432B123) with FlashFire and in the middle of the update the phone went black and my problems began getting worse.
i rebooted the phone and got into Error mode Func No: 11 (recovery image) and Error No: 2 (boot faild in recoveryboot mode!).
so i followed a guide and reinstalled twrp to attemp to restore the system somehow, so i kept following the guide and i went into twrp --> wipe --> format data and here my real problems began..
i did many attemps to install any firmware both stock and roms but i got into system mount problem and i can't do anything to transfer files to system i have tried adb but it can't find my device, tried adb sideloaded doesn't work eaither.
so i am stuck in no where..
the phone and frp are unlocked.
but i have missed to enable USB debugg mod
so now i wonder if there is any solution for me in this case?
greatly thankfull if anyone can help me with this big mess.

Try this https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page47

gm007 said:
Try this https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page47
Click to expand...
Click to collapse
Thanks i had already checked that thread.
i solved the problem by restoring the stock recovery and used eRecovery and funkyhuawei to download firmware and it just went perfectly.

forati89 said:
Thanks i had already checked that thread.
i solved the problem by restoring the stock recovery and used eRecovery and funkyhuawei to download firmware and it just went perfectly.
Click to expand...
Click to collapse
You can use that HWOTA method to recovery FullOTA rom no need to use FunkyHuawei.

forati89 said:
Hello!
I am a new to this forums so bare with me please
i have bricked my phone badly.., i tried to install the ota update for P10 Plus (VKY-L29C432B123) with FlashFire and in the middle of the update the phone went black and my problems began getting worse.
i rebooted the phone and got into Error mode Func No: 11 (recovery image) and Error No: 2 (boot faild in recoveryboot mode!).
so i followed a guide and reinstalled twrp to attemp to restore the system somehow, so i kept following the guide and i went into twrp --> wipe --> format data and here my real problems began..
i did many attemps to install any firmware both stock and roms but i got into system mount problem and i can't do anything to transfer files to system i have tried adb but it can't find my device, tried adb sideloaded doesn't work eaither.
so i am stuck in no where..
the phone and frp are unlocked.
but i have missed to enable USB debugg mod
so now i wonder if there is any solution for me in this case?
greatly thankfull if anyone can help me with this big mess.
Click to expand...
Click to collapse
could you tell me how did you get rid of this error message? im not able to boot into the bootloader, or not completely because the device is not recognized in fastboot.. everytime i turn it off, it turns automatically on and end in, it looks like the bootloader, but with that two error messages, so im not able to do anything..

m_adnan said:
could you tell me how did you get rid of this error message? im not able to boot into the bootloader, or not completely because the device is not recognized in fastboot.. everytime i turn it off, it turns automatically on and end in, it looks like the bootloader, but with that two error messages, so im not able to do anything..
Click to expand...
Click to collapse
To boot into bootloader mode you have to plug the usb and hold volume down while booting.

gm007 said:
To boot into bootloader mode you have to plug the usb and hold volume down while booting.
Click to expand...
Click to collapse
i try that so many times.. but it doesn't work.. as soon as the phone has power, im not able to turn it off.. it start automatically again, and i can press what ever i want, vol down power (with/without usb), vol up power, it always ends in the same:
ERROR MODE
Attention!
Please update system again
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)

m_adnan said:
i try that so many times.. but it doesn't work.. as soon as the phone has power, im not able to turn it off.. it start automatically again, and i can press what ever i want, vol down power (with/without usb), vol up power, it always ends in the same:
ERROR MODE
Attention!
Please update system again
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
Click to expand...
Click to collapse
That's a big problem if you can't access fastboot or erecovery.
Seems you messed up the 2 recoveries.

gm007 said:
That's a big problem if you can't access fastboot or erecovery.
Seems you messed up the 2 recoveries.
Click to expand...
Click to collapse
yes it looks like.. i mean, it wouldn't be a problem to flash recovery again, but i can't get the device to boot into the bootoader so i can work with fastboot..

m_adnan said:
yes it looks like.. i mean, it wouldn't be a problem to flash recovery again, but i can't get the device to boot into the bootoader so i can work with fastboot..
Click to expand...
Click to collapse
Maybe you still have twrp installed?
Volume up + power without connecting usb.

gm007 said:
Maybe you still have twrp installed?
Volume up + power without connecting usb.
Click to expand...
Click to collapse
already tried, but without success.. it always end in that error mode..

forati89 said:
Thanks i had already checked that thread.
i solved the problem by restoring the stock recovery and used eRecovery and funkyhuawei to download firmware and it just went perfectly.
Click to expand...
Click to collapse
how you managed to restore stock recovery? with frp only reading is allowed in fastboot i thought?
same probs here with my p10 vtr-l09 but cant get to one of the recoverys .. how can i tell the frp lock that everything is fine with my fastboot commands?
Sent from my HUAWEI HUAWEI GRA-L09 using XDA Labs

hi, did you manage to solve this problem?