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 guys, I have a problem with this phone.
First I flashed the euro+fastboot kdz... The phone booted and worked awesome but It wasn't showing recovery or LG logo.
Somewhere on this forum I read that you had to flash v10c and then v20B to fix this.
I did so, v10c failed, but v20B flashed correctly, but it didn't boot up.
I'm still stuck here, the phone is completely dark, but when I connect it to the pc I can see it with ADB, It just doesn't go into fastboot mode (because of v20B I guess). But flashing the euro kdz won't work anymore, and I'm stuck in ADB without fastboot.
Hope you guys can help me,
Juxter.
Juxter said:
Hello guys, I have a problem with this phone.
First I flashed the euro+fastboot kdz... The phone booted and worked awesome but It wasn't showing recovery or LG logo.
Somewhere on this forum I read that you had to flash v10c and then v20B to fix this.
I did so, v10c failed, but v20B flashed correctly, but it didn't boot up.
I'm still stuck here, the phone is completely dark, but when I connect it to the pc I can see it with ADB, It just doesn't go into fastboot mode (because of v20B I guess). But flashing the euro kdz won't work anymore, and I'm stuck in ADB without fastboot.
Hope you guys can help me,
Juxter.
Click to expand...
Click to collapse
Try again.
First refer to this thread:
dont see recovery and boot logo - http://forum.xda-developers.com/showthread.php?t=825173
And the original post by: Feuerbard
#22 - http://forum.xda-developers.com/showpost.php?p=9457010&postcount=22
Thumbs up solution to get logo
solution from 4PDA
flash first french firmware _hxxp://csmg.lgmobile.com:9002/swdata/WEBSW/GT540/ANEUBK/V20a_00/V20A_00.kdz
(you must make kdz flasher fullscreen and change right option to CS_EMERGENCY)
dont boot android , remove accu reinsert them and press vol - and plug usb cable into port on mainboard - you must get in download mode )
flash firmware with fastboot (i use CIS _hxxp://narod.ru/disk/26675062000/V20B_00.kdz.html)
boot android and flash this firmware _hxxp://narod.ru/disk/25473801000/out.kdz.html
after this you must see all logo ( LG , Motion LG , Android )
after this flash firmware you like (custom fastboot e t с)
maybe some point is not needed but this tutorial work 100% and tested by myself
Click to expand...
Click to collapse
And the post by namco:
in post -- #45 - http://forum.xda-developers.com/showpost.php?p=10241289&postcount=45
namco said:
So after 4 5 6 or maybe 10 times, it will finally become working, that's what you're saying?
This is really odd, something's wrong with these phones lol
Okay, i'll load myself with a ton of patience and repeat the steps as per the instructions. This is *exactly* how i am doing it, with all the details:
1) Using the French v20A ROM - http://csmg.lgmobile.com:9002/swdata/WEBSW/GT540/ANEUBK/V20a_00/V20A_00.kdz and this Russian one - http://narod.ru/disk/25473801000/out.kdz.html
2) Take out the battery, SIM card and SD card
3) While holding the Vol - button, plug USB into phone so that the phone goes into Download Mode
4) Run the KDZ Updater, put it into CS_Emergency mode
5) Select the French V20A rom and flash it
6) When it's finished (immediately after the DOWNLOAD MODE letters vanish), i pull out the USB plug from the PC, so that the phone doesn't boot.
7) Again hold Vol - and reinsert USB to put the phone back in Download Mode
8) In KDZ Updater (still in CS_Emergency mode) select out.kdz and flash it
9) Let the phone boot into Android
At this point i STILL don't have a boot animation, should i keep doing this until i see one appear?
When it (if) finally appears, i just flash my own ROM, do a factory reset and it should stay that way, correct?
I guess my impossibility to access recovery mode also has something to do with this...
Click to expand...
Click to collapse
Note: For above step: 1) Using the French v20A ROM
-- as long as you have the ROM of v20 with fastboot option, it doesn't really matter.
================
For out.kdz file alternate download link by fisher:
#59 - http://forum.xda-developers.com/showpost.php?p=10426771&postcount=59
Originally Posted by fishears
Try this:
http://www.mediafire.com/?u2mhgrbva8dr5cm
================
Hope this helps.
Thanks for the reply, I actually fixed it following this:
hxxp://modaco.com/topic/329863-how-to-raise-gt540-from-the-dead/
Once I got fastboot with that cwm.kdz I reflashed a fastboot rom, and from that one I could use the KDZ updater again, following the French kdz procedure...
The phone now is fully working recovery and bootanimations again
hello
i messed up with my device and i can't mount any of the partitions nor unable to enter into the download mode to flash stock rom...
Even "adb reboot download" too not working...
Fastboot mode is working...
Can flash into twrp but unable to mount partitions.... So unable to flash custom roms...
please help me...
Thank You....
princemouli said:
hello
i messed up with my device and i can't mount any of the partitions nor unable to enter into the download mode to flash stock rom...
Even "adb reboot download" too not working...
Fastboot mode is working...
Can flash into twrp but unable to mount partitions.... So unable to flash custom roms...
please help me...
Thank You....
Click to expand...
Click to collapse
Press VOL UP along with POWER KEY and release power key once the lenovo logo shows, while still pressing the VOL UP. This will boot into DOWNLOAD MODE
sasukay said:
Press VOL UP along with POWER KEY and release power key once the lenovo logo shows, while still pressing the VOL UP. This will boot into DOWNLOAD MODE
Click to expand...
Click to collapse
Thanks for ur reply...
I tried it but still unable to boot into download mode...
princemouli said:
Thanks for ur reply...
I tried it but still unable to boot into download mode...
Click to expand...
Click to collapse
Brother, I'm not exactly a expert in this case, but I cam suggest you a few hit n trials.
Boot into recovery, go to mount and click on system, data, cache, dalvik, etc.
If you've tried doing so, then go to advanced, then to terminal and type in "mount /system" and others. If still this doesn't work. Then better try the cwm recovery. The unable to mount system has happened to me, and that time CWM came to my rescue.
sasukay said:
Brother, I'm not exactly a expert in this case, but I cam suggest you a few hit n trials.
Boot into recovery, go to mount and click on system, data, cache, dalvik, etc.
If you've tried doing so, then go to advanced, then to terminal and type in "mount /system" and others. If still this doesn't work. Then better try the cwm recovery. The unable to mount system has happened to me, and that time CWM came to my rescue.
Click to expand...
Click to collapse
Can you please send me the link for CWM recovery...
Thank you
princemouli said:
Can you please send me the link for CWM recovery...
Thank you
Click to expand...
Click to collapse
HERE IT IS
is the download mode only available on lenovo stock rom ?
sasukay said:
HERE IT IS
Click to expand...
Click to collapse
Getting this error "FAILED (remote: dtb not found)"
princemouli said:
Getting this error "FAILED (remote: dtb not found)"
Click to expand...
Click to collapse
Try this instead:
Code:
fastboot boot cwm.img
sasukay said:
Try this instead:
Code:
fastboot boot cwm.img
Click to expand...
Click to collapse
did same....
still error...
princemouli said:
did same....
still error...
Click to expand...
Click to collapse
Bro, I did some research but couldn't find anything useful.
Have you tried booting into download mode by pressing VOL UP + POWER KEY and releasing power key once the logo shows up.
And, which recovery (with version) are you using.
sasukay said:
Bro, I did some research but couldn't find anything useful.
Have you tried booting into download mode by pressing VOL UP + POWER KEY and releasing power key once the logo shows up.
And, which recovery (with version) are you using.
Click to expand...
Click to collapse
Still unable to flash the stock rom....
try :
Code:
adb reboot bootloader
of course usb debugging must enabled and pc authorized.
sasukay said:
Try this instead:
Code:
fastboot boot cwm.img
Click to expand...
Click to collapse
brother tried many methods but non of them worked....
can you please upload the drivers u have used to flash the stock rom
also is there any method to restore this menu to enter into download mode (see the image in attachment) using fast boot mode....
princemouli said:
brother tried many methods but non of them worked....
can you please upload the drivers u have used to flash the stock rom
also is there any method to restore this menu to enter into download mode (see the image in attachment) using fast boot mode....
Click to expand...
Click to collapse
Bro I'll suggest you to get a twrp backup from somewhere and then restore it. I don't have bandwidth left, so you should ask some other user for this.
Also, you never told, how this all even started.
get the adb tools this link:
http://forum.xda-developers.com/lenovo-a6000/how-to/root-root-lenovo-a6000-plus-lollipop-t3199532
---------- Post added at 12:02 PM ---------- Previous post was at 12:02 PM ----------
get the adb tools this link:
http://forum.xda-developers.com/lenovo-a6000/how-to/root-root-lenovo-a6000-plus-lollipop-t3199532
sasukay said:
Bro, I did some research but couldn't find anything useful.
Have you tried booting into download mode by pressing VOL UP + POWER KEY and releasing power key once the logo shows up.
And, which recovery (with version) are you using.
Click to expand...
Click to collapse
Brother thanks for ur help , now iam able to enter into download mode ,
Now Can you please provide me the direct download link to the stock firmware which can be flashed through downloader 1.0.2...
princemouli said:
Brother thanks for ur help , now iam able to enter into download mode ,
Now Can you please provide me the direct download link to the stock firmware which can be flashed through downloader 1.0.2...
Click to expand...
Click to collapse
Glad to hear that.
I hope you are following THIS GUIDE at boycracked. All the drivers and other softwares are listed there along with the download links.
Do note, that you have to flash the ROW Firmware (after extracting) and not the Stock ROM. The ROW firmware is available for A6000 only (and not A6000 plus), so you have to use that only, FROM THIS LINK. You can choose any of the ROW firmware. Flashing A6000s firmware won't affect anything except that your recent app cleaner will show 1GB of total RAM (only for display...actually the whole 2GB is used).
Later. after you recover your phone, you can flash the stock ROM or any other custom ROM or maybe leave it like that...
sasukay said:
Glad to here that.
I hope you are following THIS GUIDE at boycracked. All the drivers and other softwares are listed there along with the download links.
Do note, that you have to flash the ROW Firmware (after extracting) and not the Stock ROM. The ROW firmware is available for A6000 only (and not A6000 plus), so you have to use that only, FROM THIS LINK. You can choose any of the ROW firmware. Flashing A6000s firmware won't affect anything except that your recent app cleaner will show 1GB of total RAM (only for display...actually the whole 2GB is used).
Later. after you recover your phone, you can flash the stock ROM or any other custom ROM or maybe leave it like that...
Click to expand...
Click to collapse
Brother still unable to write firmware ...
flashing started but it too not able to write firmware...
used both qpst and downloader
qpst given message that flashing is successful
and downloader got hanged after flashing start
but still unable to boot the phone....
princemouli said:
Brother still unable to write firmware ...
flashing started but it too not able to write firmware...
used both qpst and downloader
qpst given message that flashing is successful
and downloader got hanged after flashing start
but still unable to boot the phone....
Click to expand...
Click to collapse
Did you followed each and every step as in the tutorial I mentioned...??
The key point is that you should have correct drivers installed and your device in download mode should be detected in device manager on PC as Qualcomm Preloader Diagnostic Mode whatever...
And keep im mind that you have to extract the 7z ROW Firmware file.
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?
my phone boot only in this screen mode http://imgur.com/a/rMcO7. this is not my pic but error is: error mode attention. please update system again. error. func no 14 (iom3 image) error no: 1 (security verify failed).
What can I do to revive my phone. not working fastboot, bootloader, dload method to force flash of rom ecc... THx
I've similar situation..i'm not able to flash any kind of image..
Wire1122 said:
my phone boot only in this screen mode http://imgur.com/a/rMcO7. this is not my pic but error is: error mode attention. please update system again. error. func no 14 (iom3 image) error no: 1 (security verify failed).
What can I do to revive my phone. not working fastboot, bootloader, dload method to force flash of rom ecc... THx
Click to expand...
Click to collapse
Friend, if you want to re-cover phone, do this steps.
1. Connect your phone to PC and fast press volume down and power button (phone needs to be off)
2. You will be now on Bootloader & rescue mode.
Now you search for mega Thread and there will be unbricking section! UW!
RootingPro-18 said:
Friend, if you want to re-cover phone, do this steps.
1. Connect your phone to PC and fast press volume down and power button (phone needs to be off)
2. You will be now on Bootloader & rescue mode.
Now you search for mega Thread and there will be unbricking section! UW!
Click to expand...
Click to collapse
Thancks, but my phone is already in huawei assistance.