Related
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??
Hello Friends, I just upgraded my Zenfone 3 ze520kl to Nougat, but i prefer Marshmallow i try from recovery mode to flash Marshmallow, it shows error and the installation aborted. Can any one help . Thanks.
What error does it show?
Error with some numbers follows by 'install aborted'. I unable remember the error numbers. I did three times all the time with same remark.Thanks.
That's not very helpful. Can you try it again and tell us exactly what it says?
Hi,
I downgraded a few days ago, here's an overview of the steps.
WARNING, this requires a factory reset so you will lose the data on the phone, so make sure you have backups before you proceed. You do this at your own risk and I am not responsible for any damages.
I assume you have adb / drivers all configured and know to how use them.
1) download firmware file http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-13.20.10.152-user.zip and save to SD card / insert card in phone.
2) download recovery and boot img files for Z017D_WW_13.20.10.152
- https://mega.nz/#F!ok0V0RIA!5WKtHe98opzjVI3NPbM7Ww
- under the folder Z017D_WW_13.20.10.152
3) Go to fastboot mode (power + vol up)
- flash recovery.img (command: fastboot flash recovery recovery.img)
- flash boot.img (command: fastboot flash boot boot.img)
4) reboot to recovery (power + vol down)
5) install update form micro sd card.
set the file UL-ASUS_Z017D_1-WW-13.20.10.152-user.zip that you saved earlier
6) wipe cache
7) factory reset
If you don't do a factory reset and reboot, Android pretty much crashes on multiple processes on start up, it is unusable.
Regards,
TK
Credit goes to https://forum.xda-developers.com/zenfone-3/help/guide-how-to-root-zenfone-3-ze552kl-t3471524 for laying the foundation.
Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.
Same thing happened to me as well. I just went ahead to flash the RAW file (http://www.asus-zenfone.com/2016/12/asus-zenfone-3-raw-firmware-and-asus.html) and updated the software to the latest marshmallow update, followed by a factory reset.
If we Downgrade
Then we get update in future yes or no??
Sorry for bad English??
Yes.
Hi, thanks for the help. Please answer this:
Do I need to use Recovery and Boot.img the same version of ROM? Why?
Why do I need to install Boot.img?
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?
I got a Google Nexus 7 WIFI ONLY tab and it was in non operating condition by the time I received
Somehow managed to turn on by boosting the battery for a few hours. It turned on but struck on Google
in the middle of the screen and with a lock symbol at the bottom,
Then Flashed "bootloader-grouper-4.18.img" through fastboot mode and flashed the "nakasi-jdq39-factory-c317339e" factory image
it turned on and stuck at screen to unlock. I asked my friend for the password to enter the main screen,he told me what he remembered
(infact he too forgot the password). It did not work
Then flashed TWRP 3.1.1-0 through fast boot mode and then I found so many custom ROMs on this site and for any version, I am getting the error shown as Error opening '/data/media' (no such file or directory)
Please suggest me how to get back my tab back into working condition
Most unfortunate. Nobody is there to help on this ?
YOu have installed bootloader version 4.18 while the latest bootloader version for Nexus 7 is 4.23 which means you have an outdated bootlaoder installed on your device while TWRP 3.1.1 is the latest version available supporting android 7.x. I am not sure but this already might cause some issues. Additionally there were some changes in handling /data/media and /sdcard/internal/
To get out of your situation you should either install a factory image with a current (4.23) bootloader (but be aware that there are some factory images out which have a buggy bootloader (!))
Otherwise you could install a working bootloader 4.23 and TWRP 3.1.1 using fastboot and and then a custom ROM based on Android 7.x
vsrkmurthy said:
I got a Google Nexus 7 WIFI ONLY tab and it was in non operating condition by the time I received
Somehow managed to turn on by boosting the battery for a few hours. It turned on but struck on Google
in the middle of the screen and with a lock symbol at the bottom,
Then Flashed "bootloader-grouper-4.18.img" through fastboot mode and flashed the "nakasi-jdq39-factory-c317339e" factory image
it turned on and stuck at screen to unlock. I asked my friend for the password to enter the main screen,he told me what he remembered
(infact he too forgot the password). It did not work
Then flashed TWRP 3.1.1-0 through fast boot mode and then I found so many custom ROMs on this site and for any version, I am getting the error shown as Error opening '/data/media' (no such file or directory)
Please suggest me how to get back my tab back into working condition
Click to expand...
Click to collapse
The exact same thing happens to me on my redmi note 9s
What can I do?
Just Open Terminal from TWRP Recovery then open `data`. now create Media folder thats all
cd data & mkdir media
This one works for me in redmi k20 pro, Now your Internal storage mount in PC
Welcome everyone,
I am looking for solution of my issue.
TLDR : I stucked into download mode i cannot shutdown the phone - i am in the loop . - SAmsung A40
Long story i tried recover accidentally erased photos from my wife phone . Around 30% i have been able to recover, but for further getting photos I have make deep scan which also required making a root.
I quckly read some turiorals , dowload the necesary software, make the set up and go to the action.
Mostly i when through youtube tutorial from link below
Unfortunately after successfully loaded TWPR i cannot netiher turn off the phone or opne normaly
i got error message on top
Recovery : Error validation footer. (6)
Custom receovery
VBMETA A405FNXXU3BTK4, 36252767R
Please help - i need to problem ASAP
I can pay or donate money for refugees from Ukraine
OK,
i solved temporary and rom orginal android from samsung, but still i would like to root a phone,
how to flesh in odine .img file.
AS AP recovery.img , but how to load vmeta & boot file ?