Please help! Boot Loader error A5,69,35,00,21 - Defy General

Help appreciated!
My Defy does not boot and shows the following error:
Bootloader
9.10
Err:A5,69,35,00,21
Battery OK
OK to Program
Transfer Mode:
USB
I have tried several SBFs (for ex. 3.4.2.177-003), always with same error. It happened after i tried to start from scratch after a CWM Recovery program corruption and a boot stuck (out of the blue). Flash with RSD-Lite 5.31 always finishes without error. I used CM7.1 over official Froyo.
Any ideas?
Daniel

Did you wipe with stock recover y?
Got a Headache? It's all in your Head.

Stock recovery wipe did not help.
After endless tries i could finally boot and restore my backup. I don't know what helps if this happens again.
Thanks for your attention.

will this help?
http://goo.gl/cR8N0

Flash correct full sbf.

Related

[Q] Help with non-booting phone

Tried a battery mod which screwed up phone. Stuck on M logo. (using stock 2.51)
Boot into recovery, says:
E: Can't open /cache/recovery/command
E: Can't open /cache/recovery/caller
so I can't find way of restoring nandroid. Tried a factory reset - no change.
Tried flashing Nordic sbf, which i realise is useless without installing Nordic nandroid first. Now gets stuck at red M logo
Now what?
flash the nordic sbf here, and it should fix ur problem as it is the whole sbf not just the boot parts http://forum.xda-developers.com/showthread.php?t=966537
before you do that follow the instructions here to get into stock revovery http://forum.xda-developers.com/showthread.php?t=855962 and do a factory reset/ wipe
Sweet, that did the trick. Thanks a million.

[Q] FAILED FLASH, please help

Hello, I flashed the new Kingdom Rom after full wiping, but I failed to see the download has actually failed and was an incomplete ROM, now my phone won't boot or go into recovery and is stuck at the splash screen. What do I do?
You sure you cannot get into recovery? A full wipe will not wipe your recovery.
Can you see your device while plugged via fastboot or adb?
Thank you, after removing battery and running fastboot, it booted. .

[Q] CWM works, but boot loop on multiple ROMs, can't revert to stock

Please help me unbrick my phone! (panicking slightly)
A few days ago I received a new XP1C, and I immediately (without ever booting it into stock) unlocked it, flashed boot.img from the newest CWM nightly, and proceeded to install cyanogen's newest nightly.
BOOT LOOP.
I've tried:
1) other ROMs (both from Cyanogenmod, and other developers). All result in boot loops.
2) using flashtool to try to return it to stock. It connects to the phone, but fails during the process.
3) connecting with ADB - device is not showing up.
when I do a wipe data/factory reset I get some errors:
Error Mounting /data!
Skipping format
...
E: unknown volume for path [/sd-ext]
...
Error mounting /sdcard/.android_secure!
Skipping format...
I would be most grateful if anyone had any ideas of things for me to try. I have been all over the forums and am totally out of ideas... :crying:
Did you backup TA partition?
Cause from what i understand you need to restore those keys before reverting to stock rom.
New Folder said:
Did you backup TA partition?
Cause from what i understand you need to restore those keys before reverting to stock rom.
Click to expand...
Click to collapse
I did not back up or change anything when I got the new phone. I just took it out of the box, plugged it in to the usb on my laptop, and did the Sony unlock process.
Flash a stock firmware in flashtool (e.g. http://forum.xda-developers.com/showthread.php?t=2768044 )
Flash stock rom using flashtool and boot into os first, then proceed to fastboot and custom rom.. You have not reboot after unlocking BL, and flashed kernel using fastboot.. Thats why u r getting this error..
Sent from my Xperia Z1 Compact

Bootloop after downgrade from L Preview..

Hey, I have an issue with my tablet after I wanted to go back to kitkat from the L Preview.
I had 4.4.4 and decided I'd like to try out the L preview
So I downloaded the img from Google and flashed it via fastboot, worked perfectly fine but not as stable in apps as it was on kk.
So, I downloaded the latest factory image from the Google Developer Site, extracted it and ran the flash_all.bat
Seemed to flash ok, no errors, rebooted and started to boot but it only goes as far as the spinning boot logo. No further.
After leaving it a good hour or so I decided it clearly wasn't going to boot I went back into the bootloader and tried to get into stock recovery mode but after rebooting it just stays at the white Google logo..
So, I tried to flash TWRP via fastboot. Again no errors, successful flashed but just like before it sticks at the Google logo and never boots the recovery..
I even tried the "fastboot boot recovery.img" but then it just freezes on the bootloader.
I've also tried the 4.4.3 img.. same happens.
Now if I reflash the L Preview img via fastboot it sticks at the Google logo and didn't even reach the boot logo!
Sounds to me like the partitions have gotten corrupt? Though the imgs are flashing successfully without error so I don't think it's that..
But.. recovery partition is broken as I can't get into recovery at all, and it freezes if I try.
Anyone any idea what could have happened?
All I did was flash the KK factory image over L, just like I flashed L over KK and it worked fine.
All the guides online do the same thing to downgrade L to KK.
Is it bricked? Can it be recovered?
I still have bootloader access with fastboot..
Any help is greatly appreciated!
I finally managed to enter the stock recovery and it appears that the /cache partition was damaged or corrupt. Strangely it would get corrupted each time I flashed the factory image, even flashing the cache.img directly..
However it seems to have fixed by doing a factory reset and /cache then formats correctly and android booted fine after this :victory::laugh:
As you see in the image, when entering recovery I was presented with a bunch of errors regarding the cache.
Tried to wipe cache but that fails.
Did a factory reset and cache seemed to format fine.
Did another wipe cache and this time it completes without the error I got before.
Then rebooted, Android began booting and thankfully it's now working fine again!

M8s stuck in bootloader

Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Hi McBad,
you could try the following. I also had some problems to access the recovery.
- Again bring the phone into fastboot, flash the 2.8 recovery and access it
- Do a wipe for factory reset, not just only cache
- after that try to flash the twrp-3.0.1-0-m8ql.img version, the other one worked for me neither
- the try to install the custom ROM LOS13
I hope this will help you.
clone
It would be great if that would work, but flashing a recovery does not work. I flash it, success message, try to access it, vibrates and bootloader pops back instantly. That is the problem.
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Have you tried sideloading twrp ?
McBad said:
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Click to expand...
Click to collapse
Did you use HTC fastboot ?
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Is there any way you could flash twrp 2.8 again? Once in that recovery you have sideloading option which you could use to transfer latest recovery onto your device. Are we talking about the same process?
McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Sideload as follows ....
McBad said:
Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Click to expand...
Click to collapse
You can't install lineage if you haven't upgraded your device with latest official update. I would try reinstaling twrp 2.8, do a wipe of cache, dalvik cache and system, Sideload CM 12; and see how it goes. As well, while in twrp I would try relocking bootloader but only after an unsuccessful attempt to flash said rom. I don't know what your experience with soft bricked devices is, but sometimes it takes a while, different usb cable or usb slot on your PC, correct files in adb folder, re-download of rom or recovery because it easily gets corrupted while downloading. And obviously a fully charged device. Let us know how it goes.

Categories

Resources