[Q] Help, stuck in bootloader - Defy Q&A, Help & Troubleshooting

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

Related

Do I broke my HD Mini?

Hello,
I have serious problem with my phone. I bought HTC with windows mobile and some time ago I have installed Android from this topic http://forum.xda-developers.com/showthread.php?t=1455555 I chose nand-boot option so windows had been deleted from hard memory. Then 5days ago I decided to do an upgrade of Android. Downloaded new version of Android and tried to install it from old Android, system crashed and I can’t do anything in bootloader know. It's only this message:
nand id: 0x5500bcec maker=0xeo device=0xbc
press VOLUME UP for RECOVERY
press VOLUME DOWN for FASTBOOT
flash_read_image: failed (319 errors)
ERROR: Cannot read recovery_header
flash_read_image: failed (5056 errors)
ERROR: Cannot read kernel image verting to fastboot mode.
ENTERING FASTBOOT MODE
udc_start()
Click to expand...
Click to collapse
When I press Volume Up or Down nothing happens. So I decided back to windows but I have problem with install it. When I try to install original ROMs have this ERROR 294 -> Invalid vendor id. When try to install custom ROM with using SSPL I have other ERROR [262] -> Update error. I tried to installation from SD card but nothing happens in 3 colors bootloader.
Please help me…
http://forum.xda-developers.com/wiki/RUU_Errors#ERROR_.5B294.5D_:_INVALID_VENDOR_ID
are you sure you followed the steps correctly when you tried to install from sd card?(explain what you did and nothing happened)
tzacapaca said:
http://forum.xda-developers.com/wiki/RUU_Errors#ERROR_.5B294.5D_:_INVALID_VENDOR_ID
are you sure you followed the steps correctly when you tried to install from sd card?(explain what you did and nothing happened)
Click to expand...
Click to collapse
Hi I've the same problem, I don't know what to do, is there anyone who has got an hint?
I cannot reinstall the ROM because the damn INVALID VENDOR, I canno use SSPL_RUU.exe as suggested in this forum because it must be run from WM and not from the coloured strips screen..
is there a solution? please!
you should try your original WM ROM, or for android these aren't any problem.. it's because bad installation,
i broke my bootloader too. cant enter recovery or something else. someone an idea? :/
reinstall recovery from windows>usb>htcHDmini

I need a help!! milestone 2 A953

Hello, i'm a big problem for my motorola milestone 2 A953, I apologize for my language and my mistakes.
Hello, I recently purchased from eBay Milestone 2 has an English menu and is purchased in the UK, I wanted to upload to the new software CM9 best unless it can not be CM7, and right now I have a problem namely
I have bootloader 70.13, upload the file to the memory card from the CM9 and GAPPS bootloader fires (up arrow + power) via USB to the PC turn on RSD lite version 5.x choose the file with the extension *. SBF and then kicks me out of 100% and I turned on the phone once again turn to the new bootloader and shows the pass. My next step holds the power and turn off phone and then I hit 'x' + power and shows me a screen with an exclamation point in a triangle and android humanoids press volume + camera and then a magnifying glass on the keyboard and nothing happens no fires are no menu is the same I'll do it but as I press the @ button on the keyboard or anything, no menu: (
I did everything the instructions that I found on forum
http://forum.xda-developers.com/show....php?t=1338183
1) Install Bootstrap Recovery Droid2
2) Boot into recovery
3) OPTIONALLY: create a backup of your data
4) Choose Install zip from sdcard -> Choose zip from sdcard and select downloaded ZIP file.
5) OPTIONALLY: install Google Apps the same way
6) Wipe data / factory reset
7) Wipe cache partition
8) Reboot and enjoy
9) OPTIONALLY: use attached Baseband app switcher if you have troubles with phone signal.
all worked out, but when I went passed the phone rebote motorola logo and nothing else happens. I do not know how to solve this problem.
I can not run the recovery menu. I can only enter the bootloader version is 70.13.
I would like to upload the software from the Polish language.
Thanks for help.
lukasz0318 said:
Hello, i'm a big problem for my motorola milestone 2 A953, I apologize for my language and my mistakes.
Hello, I recently purchased from eBay Milestone 2 has an English menu and is purchased in the UK, I wanted to upload to the new software CM9 best unless it can not be CM7, and right now I have a problem namely
I have bootloader 70.13, upload the file to the memory card from the CM9 and GAPPS bootloader fires (up arrow + power) via USB to the PC turn on RSD lite version 5.x choose the file with the extension *. SBF and then kicks me out of 100% and I turned on the phone once again turn to the new bootloader and shows the pass. My next step holds the power and turn off phone and then I hit 'x' + power and shows me a screen with an exclamation point in a triangle and android humanoids press volume + camera and then a magnifying glass on the keyboard and nothing happens no fires are no menu is the same I'll do it but as I press the @ button on the keyboard or anything, no menu: (
I did everything the instructions that I found on forum
http://forum.xda-developers.com/show....php?t=1338183
1) Install Bootstrap Recovery Droid2
2) Boot into recovery
3) OPTIONALLY: create a backup of your data
4) Choose Install zip from sdcard -> Choose zip from sdcard and select downloaded ZIP file.
5) OPTIONALLY: install Google Apps the same way
6) Wipe data / factory reset
7) Wipe cache partition
8) Reboot and enjoy
9) OPTIONALLY: use attached Baseband app switcher if you have troubles with phone signal.
all worked out, but when I went passed the phone rebote motorola logo and nothing else happens. I do not know how to solve this problem.
I can not run the recovery menu. I can only enter the bootloader version is 70.13.
I would like to upload the software from the Polish language.
Thanks for help.
Click to expand...
Click to collapse
From the bootloader you can flash the original firmware again and get your phone back to life.
Get your firmware from here: http://sbf.droid-developers.org/umts_milestone2/list.php
Keep in mind that you need to have a fully charged battery before flashing, and you can only flash a firmware that is the same version or newer that the original in the phone (newer is always better)
Work?
Enviado de meu MotoA953 usando o Tapatalk 2
[BRA] Giovani said:
Work?
Enviado de meu MotoA953 usando o Tapatalk 2
Click to expand...
Click to collapse
it works, I've done first so I have uploaded the rds lite software on this page sbf.system-ready.org/umts_milestone2/?C=M;O= D Unfortunately, it was the android version 2.3.6 but went to decorate it root, then I have uploaded to the sD card CM9 with google alikacjami droid2bootstap installed and I have uploaded to the card-v2 Bootmenu_v0.8.6 phone then ran again and continue with bootmenu it's instructions. works great thanks for your help. :good:
Same problem for me: would appreciate help
Hello !
It seems like I am having the same problem as lukasz0318, but I don't know how to solve it, even based on what has been said before. That's why I am posting here.
To summarize it : I am not able to boot into Recovery Mode anymore on my Milestone 2, so my phone is soft-bricked. I am able to boot into Bootloader Mode.
I already posted my problem on the Android StackExchange (android.stackexchange.com/questions/27553/how-do-i-enter-recovery-mode-on-my-motorola-droid-2-global-to-unbrick-it), but as I have had no answer there in 8 days, I suppose XDA-Developers will be a more appropriate forum. Anyway, let me recap the problem. Hold on, since it is quite an explanation. You may jump to the last paragraph.
I own a Motorola Droid 2 Global, also called Milestone 2. It used to have Android 2.3 with Motoblur middleware. I don't know what firmware version it had, but it was updated earlier this year by the manufacturer. I bought my phone in France independently from any phone carrier (so it was not bought from Verizon for instance). I rooted it, installed ROM Manager, Droid 2 Global Recovery Bootstrap and ClockworkMode Recovery. From ROM Manager, I could successfully reboot my phone into Recovery mode, allowing me to back-up my data for instance. Until this stage everything went fine.
What lead to my problem : I also wiped the cache and installed CyanogenMod 7.2 and the Google apps from ZIP files and from the Recovery Mode interface. But now my phone is broken. When it now boots, it shows the stylised M logo, but then switches to an entire black screen. The phone is still on so I have to pull the battery to shut it down.
I would like to reboot into Recovery Mode but this doesn't work : I am never able to see the Recovery Mode logo (a warning sign with a little android). How should I do it ?
What I have tried : I tried to boot while holding the Power and the 'X' button, as adviced on different forums. This still leads to the black screen. At this state, pressing the Search hardware button does nothing. Holding the Power and the Volume Up button has no more effect. I am able to enter Bootloader Mode by holding Power and Up Arrow. Procedure suggested by Verizon
I also tried to use a Slitaz live CD with ezSBF on it, that I*downloaded from www droidforums net/forum/droid-2-global-hacks/170060-tool-ezsbf-d2g.html#post1726853. But I get errors in the process and then my phone reboots in Bootloader mode and shows the following error:
Code:
Critical Error:
FEBE 0047
After that I still cannot get to Recovery Mode.
I also took a look at Caesarivs' link (sbf.droid-developers.org/umts_milestone2/list.php) but I don't know which SBF to pick and I don't understand lukasz0318's answer to it. Which is a pity since the link was successful to him.
Could you please give me some details on the procedure to follow ? Additionaly, could you post me a link to your favorite and up-to-date tutorial on how to restore the Recovery Mode ?
Thank you very much !
1) A Milestone 2 is not the same as the D2G. If you bought your phone in france, its a Milestone 2.
2) You flashed the ZIPs on moto's recovery, not ClockworkMod recovery.
Try this:
1) Flash this SBF: http://sbf.droid-developers.org/umt...MILE2GBRTFR_P012_A006_HWp2a_Service1FF.sbf.gz You can flash it with RSDLite on windows or sbf_flash in linux.
2) Root it with Doomlord's one click root.
3) Download droid2bootstrap (NOT the global one) bootstrap recovery, and flash bootmenu (attached to this post)
4)Reboot once normally, reboot again, and press the volume down key when the LED flashes blue.
5) Flash CM7.2, the google apps, wipe data/factory reset.
6) Fix baseband (if you have problems with 3G or signal) with Milestone2 Baseband switcher v2: http://forum.xda-developers.com/showpost.php?p=29580375&postcount=696
Hope it helps you :good:
Lean946 said:
1) A Milestone 2 is not the same as the D2G. If you bought your phone in France, its a Milestone 2.
2) You flashed the ZIPs on moto's recovery, not ClockworkMod recovery.
Try this:
1) Flash this SBF: sbf.droid-developers.org/umts_milestone2/MILS2_U6_4.1-22_SIGNED_UCAMILESTONE2B1B80E1014.0R_USXMILE2GBRTFR_P012_A006_HWp2a_Service1FF.sbf.gz You can flash it with RSDLite on windows or sbf_flash in linux.
Click to expand...
Click to collapse
Thank you very much, Lean946. I didn't know there was a difference between Milestone 2 and Droid 2 Global. My mistake.
As I use Ubuntu 12.04, I tried to use sbf_flash but this brought up an error:
Code:
SBF FLASH 1.23 (mbm)
opticaldelusion.org
=== MILS2_U6_4.1-22_SIGNED_UCAMILESTONE2B1B80E1014.0R_USXMILE2GBRTFR_P012_A006_HWp2a_Service1FF.sbf ===
Index[1]: Unexpected chip 32
Index[2]: Unexpected chip 32
Index[3]: Unexpected chip 32
Index[4]: Unexpected chip 32
Index[5]: Unexpected chip 32
Index[6]: Unexpected chip 32
Index[7]: Unexpected chip 32
Index[8]: Unexpected chip 32
Index[9]: Unexpected chip 32
Index[10]: Unexpected chip 32
Index[11]: Unexpected chip 32
Index[12]: Unexpected chip 32
Index[13]: Unexpected chip 32
00: RDL03 0x82000000-0x8204CFFF F8E4 AP
01: CG31 0xB0280000-0xB02847FF 9EAD AP
02: CG32 0xC7B00000-0xC7B207FF 65A6 AP
03: CG33 0xB2100000-0xB2EC07FF 437B AP
04: CG34 0xB0700000-0xB07047FF 46C7 AP
05: CG35 0xB1100000-0xB18FFFFF 27C9 AP
06: CG39 0xB3400000-0xC7AC07FF 097D AP
07: CG42 0xB0800000-0xB083FFFF AC60 AP
08: CG45 0xB0C00000-0xB0F007FF 2254 AP
09: CG47 0xB1900000-0xB20FFFFF 0EAB AP
10: CG61 0xB0B00000-0xB0B7FFFF 87CD AP
11: CG64 0xB0000000-0xB00047FF 0841 AP
12: CG65 0xB0180000-0xB01847FF 130F AP
13: CG66 0xD4400000-0xE43FFFFF BB26 AP
>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
-- OK
>> uploading CG31: 100.0%
-- OK
>> uploading CG32: 100.0%
-- OK
>> uploading CG33: 11.8%usb_bulk_read 0
!! unexpected response
-- ACK ADDR
RX ADDRB22A0000A7 B22A0000A7
>> uploading CG33: failed at b22a0000/b2ec0800
!! failed
>> rebooting
usb_bulk_read 0
My phone now shows the Bootloader Mode with
Code:
SW Update
In progress…
It has been so for several minutes. I'll wait a little longer and if there is positive evolution I will edit my post.
Anyway, is this the expected behavior*?
I'd try waiting a few more minutes, if sbf_flash is still frozen, try unplugging and pulling the battery out and trying again, if it still won't work i'd take it to a windows pc, I never had any issues flashing with RSD, and I tried Milestones, Milestone 2s and Defy's.
Good luck.
Lean946 said:
I'd try waiting a few more minutes, if sbf_flash is still frozen, try unplugging and pulling the battery out and trying again, if it still won't work i'd take it to a windows pc, I never had any issues flashing with RSD, and I tried Milestones, Milestone 2s and Defy's.
Good luck.
Click to expand...
Click to collapse
Thank you very much ! I found a Microsoft Windows machine, found a download of RSD Lite (which was not very easy) and finally installed the SBF you pointed at. It worked very well to unbrick my phone ! It is now back to Motorola's ROM.
I will now try your following points in order to install CyanogenMod. Whether everything works fine or not, I will post an update.
Lean946 said:
1) A Milestone 2 is not the same as the D2G. If you bought your phone in france, its a Milestone 2.
2) You flashed the ZIPs on moto's recovery, not ClockworkMod recovery.
Try this:
1) Flash the right SBF. You can flash it with RSDLite on windows or sbf_flash in linux.
2) Root it with Doomlord's one click root.
3) Download droid2bootstrap (NOT the global one) bootstrap recovery, and flash bootmenu (attached to this post)
4)Reboot once normally, reboot again, and press the volume down key when the LED flashes blue.
5) Flash CM7.2, the google apps, wipe data/factory reset.
6) Fix baseband (if you have problems with 3G or signal) with Milestone2 Baseband switcher v2
Hope it helps you :good:
Click to expand...
Click to collapse
I think I did exactly what was indicated here: step 1 to successfully unbrick the phone, then step 2 to 4.
Step 4 lead me to an interface called "Android Bootmenu" (different from the Bootloader Mode). From there I could not flash any ZIP, but I could launch the Custom Recovery. In my case, ClockworkMod Recovery. From there I wiped data/factory reset, then I flashed CM7.2 and the Google Apps, and rebooted.
But now my phone doesn't boot properly anymore. The stylized M logo keeps appearing and disappearing. As the LED regularly becomes blue, I can enter the Android Bootmenu, and then the two Recoveries (ClockworkMod Recovery and Android Stock Recovery).
What should I do now to finish the install of CM7.2 ?
Might the reason be that I installed the wrong ROM (or the wrong Gapps) ?
I tried the following ROMS :
cm-7.2.0-droid2we.zip from get.cm/?device=droid2we&type=stable
cm-7.2.0-umts_sholes.zip from github.com/nadlabak/android/downloads
The first one gave me no error output during its installation in ClockworkMod Recovery.
The second one gave me an error :
Code:
E:Error in /sdcard/update.zip - (Status 7)
.
Do you have any suggestion or a link to your favorite tutorial ?
Finally, the following ROM did work, with the same procedure as I used to do :
CM9-NIGHTLY-120815-milestone2-eu.zip from forum.xda-developers.com/showthread.php?t=1623385
I ran into another final small problem (I could not close the Setup Wizard), but that was easily solved with the "Four corners method".
Thank you for your help and wish me good luck on my new operating system !

[Q] Need to unbrick Defy+ - Strange problems

Edit: All happy now, a change of pc solved the problem of not detecting the device!
Hi all! I have another challenge for you!
Right, I've got myself in a tizz with my Defy +. While updating between CM10.1 versions I found myself in a situation where I couldn't get past the boot animation. So I loaded the TWRP restore I had made prior to updating...
Except it wouldn't, instead it came up with 'Failed' each time I tried any of the TWRP backups I had created. So the next step was to wipe partitions and start flashing various ROMs until I found one what worked. Except they didn't work either. Eventually I thought the best idea would be to just turn the phone off and see where I was with booting.
So power on, boot logo, blue light, red light then... nothing. Just the boot logo static. Went into the custom bootloader to go into recovery again, nothing. Pressing Custom recovery simply loops back to the top bootloader screen.
Ok next step, flash .sbf and start from scratch. So into the Moto bootloader it is to plug in and flash except... it's no longer detected by my computer.
"Ok" I think, "We'll just flash files from the SD card after I use an external SD card reader.
Except now when I enter Moto recovery to flash the TWRP recovery I get:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verifiaion failed
Installation aborted
So to recap:
1) Tried to flash and update, failed
2) Tried to recover, recoveries wouldn't write (I think this is becaue I'd changed to EXT4 on /data and /cache and had forgotten to go back to EXT3 before trying to recover)
3) Tried to boot, epicly failed
4) Tried to flash .sbf, Defy+ won't appear in RSDLite 5.7 with latest driver
5) Tried to flash from SD card, sig verification failed
6) Googletastic for the last four days
Notes:
a) I CAN charge the Defy+ using the wall charger but I get '?' for the battery level indicator but...
b) In Cmod bootloader 2.1 (Which I can use a little) it shows the correct battery level
c) I /was/ getting some errors with not being able to mount /cache from the moto recovery but I've since used the cmod bootmenu 2.1 to set it back to ext3 and it's all happy now, those errors aren't appearing
d) Plugging in my Defy red lens I get W8 x64 detecting the correct portal drivers and such but when I go to moto bootloader this device also doesn't appear in RSDLite
e) Both devices prompt windows to install a Motorola Flash Interface driver in Device Manager when plugged in in moto bootloader mode and neither device appears in RSDLite despite the fact the program is running in Admin mode
f) Looking at the logs in bootloader, it appears that I might not have formatted anything from ext4 to 3, everything I select in the cmod bootmenu returns .E:Error in /system/... , (Result: Invalid arguement) , Done..
So at the moment I think I need to acheive one of the following:
1) Find a file that allows me to write any useful data to /system like a recovery or some of those bootmenu files that passes the signature verification
2) Find a way to troubleshoot RSDLite so I can actually flash .sbf and get out of this hellhole
Many regards!
Alexis
If your custom recovery is not working, then you cannot do anything other than flash an sbf(nothing except data and cache wipe can be done via stock recovery): this is due to the locked boot loader(recoveries cannot be simply flashed from the stock recovery as you're trying to do)
Sent from my MB526 using Tapatalk 2
Success (ish)!
Yes I swapped to a different machine and then upgraded the version of RSD Lite installed on it from 4.7 to 6.1.5
[URL="http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239"]http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239
And flashed the 'lower' of the two .sbf's from the links on this forum for the British variant. After a DEA1 error (Phone is dead, code corrupt and all the bad things) I managed to flash the file.
As of yet I've not managed to get out of the bootloop but I've not carried out the requisite steps as mentioned in the "So you think you've bricked your Defy/Defy+" thread.
Lessons learned:
1) Motorola drivers and RSD Lite are pennickety, you will probably need to mix them up in order to get them to behave properly
2) If all else fails, use a different computer
3) You will probably need to flash over and over, while making every effort to not muck them up. Be aware the efuse system only has limited uses before it's useless though...
My saga continues, from no USB support hopefully to a fully working device again
In the end switching PC then doing the factory reset from moto recovery let the phone boot, all standard but the dodgy USB stuff at the first post is what sent me away from the right track.

[Q] Huawei C8815 not able to Boot "Image Signature Verify Fail"

I have Huawei C8815, I am facing the following situation
I installed the stock ROM with 3 keys method, than i unlocked the network with networkunlock.bat file.
Later I tried to install one ROM by CWM Recover and I toggled Signature Verification to OFF
When I restarted my phone, It Shows "Image Signature Verify Fail"
1. My phone is not going to Recovery Mode Menu by Vol+ and Power button.
2. My phone is not going to ADB mode by VOL- and Power button.
In both these situations my phone shows "Image Signature verify fail" Install the image with correct signatures.
3.When I try to install the stock ROM by pressing Vol+ and Vol- and Power button, after step 1 in step 2 it says Update failed.
As per my knowledge when network is unlocked the phone will not accept the stock ROM. For Relocking the network we have a tool OFFICIAL FIRMWARE.BAT but for running the bat file the phone must be loaded in ADB mode. My phone is not loading adb drivers in any situation.
It is showing only drivers Android Sooner adb interface.
In this driver environment i cannot do any adb function with my phone.
What to do? I am stuck
I dont know much about JTAG and all. If anything is possible to do with JTAG or any other method, Please guide me in this matter
This is for Motorola Defy and Defy+. You might be in the wrong section, my friend.
Have you worked it out? I flashed OEM partition carelessly with the img from g610c and get exact that you faced. btw, does your networkunlock.bat file work with the simlock ? please share if you don't mind, thanks
pragyavan said:
I have Huawei C8815, I am facing the following situation
I installed the stock ROM with 3 keys method, than i unlocked the network with networkunlock.bat file.
Later I tried to install one ROM by CWM Recover and I toggled Signature Verification to OFF
When I restarted my phone, It Shows "Image Signature Verify Fail"
1. My phone is not going to Recovery Mode Menu by Vol+ and Power button.
2. My phone is not going to ADB mode by VOL- and Power button.
In both these situations my phone shows "Image Signature verify fail" Install the image with correct signatures.
3.When I try to install the stock ROM by pressing Vol+ and Vol- and Power button, after step 1 in step 2 it says Update failed.
As per my knowledge when network is unlocked the phone will not accept the stock ROM. For Relocking the network we have a tool OFFICIAL FIRMWARE.BAT but for running the bat file the phone must be loaded in ADB mode. My phone is not loading adb drivers in any situation.
It is showing only drivers Android Sooner adb interface.
In this driver environment i cannot do any adb function with my phone.
What to do? I am stuck
I dont know much about JTAG and all. If anything is possible to do with JTAG or any other method, Please guide me in this matter
Click to expand...
Click to collapse
nothing happened, i sent back device to China and they sent new one. now working great

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?

Categories

Resources