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??
Hi everyone,
For some stupid reason a reset the file system i now I'm stuck in the LG logo.
1. I can enter in download mode - in Device manager the PC recognized as LGE AndroidNet USB Serial Port (41)
2. I can enter in recovery mode (Cyanogenmod recovery, which is very based) - in Device manager the PC recognized as Android ADB Interface
So far, so good. BUT. I'tried to flash the phone with LG FlashTool 2014 and i'm stuck at 2%. Ok, i was tried the fix with FixedDownloadcmode.bat, but when nothing is uploading on the phone (which by ADB is recognized as sideload when i'm in recovery mode and apply the ADB connection). I tried to push by ADB but nothing is uploading - error: protocol.......
LGUP recognized my phone as unknown, so this method is not working now.
Via ADB i can't send even TWRP recovery, which is so much flexible than cyanogenmod recovery.
I will be thankful for any help from your side.
Thank you in advance!
https://forum.xda-developers.com/lg-g2/general/alternative-fix-lg-flashtool-stuck-2-t3605753
Same happened to me. Try this if you can reach your storage
https://forum.xda-developers.com/showthread.php?t=2663369
https://www.youtube.com/watch?v=Lg693AYgoTo
ATT 4.4.2 KitKat:
https://mega.nz/#!n0RTUYZD!MVntiPxuyW...
ATT 4.2.2 JellyBean:
https://mega.nz/#!e5RERS4L!FjZyopcvwM...
T-Mobile 4.2.2 JellyBean:
https://mega.nz/#!qsRSBDwD!KKCETp41O1...
Modified DLL file if nothing else works:
https://mega.nz/#!f5xTGKrC!ifBCOAnK4j...
I had a very similar problem with it getting stuck at the logo after pushing supersu to the phone. I followed Supersport every single step of the way in his video. I think his links are the only valid ones online now, so just download them and reflash your phone. If your G2 is anything like mine, drivers will never appear to be installed correctly and it never restarts, only shuts down.
His method is:
1) Download and install LG drivers on PC
2) Download and install the flash tool and patch it
3) Download and load the .tot and .dll files into the flash tool
4) Enter download mode on G2 by holding volume up while connecting USB
5) Switch G2 Com port to 41 in device manager
6) Once Flash tool shows that all ports are ready, power down G2 and disconnect
7) Hold volume up and reconnect to get back into download mode
8) LG Flash tool starts flashing
9) Complete
Note: If your G2 was screwed up as bad as mine, it'll say failed but all the main system files will load to the device before it restarts and it'll even shut itself off while doing it's installation on first reboot. Mine somehow was still revived from this state with his method.
I forgot to add this but couldn't edit my post for some reason.
For D800:
Master archive of 5 files needed to do this:
https://www.androidfilehost.com/?fid=95747613655047114
Huawei nova instal update failing, "your device has failed verification etc." HELP!!!
So, i have unlocked bootloader (can l-11), and then flashed stock firmware b350. After that my device is stucked on b350. System update is failing after few % same as dload method. HiSuite says that device is updated to newest version but it isnt. Bootloader is unlocked and i cant relock it becouse its failing in adb and fastboot. After rebooting the message "your device has failed verification etc." is showing.
i tried to restore in recovery, factory reset, flashing firmware again. Nothing worked.
Please help
sorry for picking wrong forum category
plenikowski.michal said:
So, i have unlocked bootloader (can l-11), and then flashed stock firmware b350. After that my device is stucked on b350. System update is failing after few % same as dload method. HiSuite says that device is updated to newest version but it isnt. Bootloader is unlocked and i cant relock it becouse its failing in adb and fastboot. After rebooting the message "your device has failed verification etc." is showing.
i tried to restore in recovery, factory reset, flashing firmware again. Nothing worked.
Please help
sorry for picking wrong forum category
Click to expand...
Click to collapse
Did you put the update.app in a folder called dload. Then unplug phone and reset the phone holding the vol + and vol - buttons as it boots? It always fails for me if the usb is plugged in.
Cooks_08 said:
Did you put the update.app in a folder called dload. Then unplug phone and reset the phone holding the vol + and vol - buttons as it boots? It always fails for me if the usb is plugged in.
Click to expand...
Click to collapse
No, i did it after unplug
Earlier it was running on custom rom then i tried to install stock rom on my device moto g4 plus...nd i successfully installed it....later an update came and as soon as phone dowoaded update nd gone to reboot doesn't turn on after that...nothing of the screen ..only charging led blinking .....nd today i tried to do blankflash nd it was successful nd something showed up on the screen for the first time
it has these options :
start
restart bootloader
recovery mode
power off
factory
barcodes
bp tools
qcom
bootloader logs
switch tools mode
when i select recovery mode..it shows up this:
------------------------------------------------------------------
Startup failed :
your device didnt start up succesfully.
use the software repair assistant on computer to repair your device.
Ap Fastboot Mode(secure)
Fastboot Reason: Failed to intialise storage partition table
ERROR : No bootaimage found . skip to fastboot
boot up failed.
---------------------------------------------------------------------
please help me through this...i want to install stock android on my phone
Try this guide https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Your device's memory seems to be corrupted, so it doesn't recognize a recovery being present. As pointed out above, go back to Fastboot, and install the latest stock ROM.
The reason i am here is to ask for help. I have driven myself crazy in solving this complicated problem i have.
Ok
i own a moto g4 xt1624 and though about rooting it for all the reasons why people root.
Got the bootloader code unlocked the bootloader and installed twrp recovery file.
Went ahead and followed all the steps to install Lineage os 14.1 steps from their offical site.
Done all Flashed the file and the device is stuck on a screen now Saying :
Your device has been unlocked and can't be trusted.
ID:bad key
Tried every forum on here the device doesn't seem to connect to pc . No showing up in device manager also
Installed all moto usb and qualcomm 9008 drivers .
The device just doesn't enter into fastboot mode no matter what i do
Pls. suggest something .
Found the solution try and go to download mode in your phone by pressing the both volume keys simultaneously and then connect the usb already connected to pc to the phone and you will boot normally onto twrp recovery or any recovery you might have installed