Am I done with my phone? - Huawei Ascend Mate 2

Long story short, I tried to flash new rom on my Mt2-L02 mate2 and failed and its bootlooping (at Huawei Ascend screen and keep rebooting) now. using the SDcard udload to load new rom don't work either. I cannot go into recovery, or boot into system.
My phone is bootloader unlocked, so I tried to flash (extract from a rom) boot.img, recovery.img and is ok but when flashing system.img, it stucked in writing 'system'... for long time.... so I tried fastboot erase system -w and get FAILED (remote: Command not allowed)... why is it so? my phone is already unlocked. I tried unlock again and flash the system.img, same problem.
So... I'm screwed?

You're not screwed. Impatient maybe. Try on a different computer if you have one. If not, update drivers and try a different port on the existing computer. Are you flashing an MT2-L02 ROM?

kimtyson said:
You're not screwed. Impatient maybe. Try on a different computer if you have one. If not, update drivers and try a different port on the existing computer. Are you flashing an MT2-L02 ROM?
Click to expand...
Click to collapse
Only have 1 pc, yes, I'm flashing MT2-L02 ROM, tried alot of version but discovered only these version rom (b408, b603, b606, b607) able to write the system.img, original out of box android version for my phone is 4.4.2. but still bootlooping after flashing boot.img, recovery.img and system.img. I think only custom recovery can save now, but there is none for this model... or maybe there is no hope for my phone? Maybe my phone got some system modified lock so that I'm not able to erase using flashboot?
C:\adb>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
C:\adb>fastboot erase data
erasing 'data'...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
If I'm able to erase those, I'm might solved the bootlooping problem..

Try using this thread as reference, http://forum.xda-developers.com/asc...to-fix-soft-bricked-phone-using-twrp-t2886630. It's for a different model so just use your stock ROM in place of the L03 ROM. I'm not sure how to help beyond that. There has to be a way to return to stock on the L02.

Maybe this message is late, pls try following
http://pan.baidu.com/s/1dDpc4eP
http://www.huaweirom.com/rom/mate2/2619.html
usb flash instructions:
http://www.huaweirom.com/guide/2621.html
You may need to use google translate since all the info is in Chinese
Basically they are saying you should use B117 if B4xx not working.

Related

REQUEST: correct RECOVERY.IMG

Guys, how far you are with correct recovery.img? The one existing is not fully working.
Erasing and cleaning tools doesnt work.
Thanks
I am also not able to fully access Unlocked phone even via fastboot commands:
C:\>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.002s
We understand that you want a custom recovery. However, you have to stop posting it in the development section.

Error Booting CWM

Hi Everyone,
First I apologize if this isn't the right place to post this, please move it to the correct forum if it's not.
I have a Asus TF700 (running the latest Asus firmware) the, warranty just ran out so I figured it was time to unlock and play with some custom roms.
I got it unlocked using the Asus bootloader tool, I went to install CWM using fastboot and it seemed to go OK but then when I went to reboot the bootloader it failed giving me a write failure. Now when I try to boot up recovery it briefly shows the android guy in working mode then goes to the error with the android laying on his back.
Here is my commands with fastboot:
C:\adb>adb reboot bootloader
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (6688 KB)...
OKAY [ 2.483s]
writing 'recovery'...
OKAY [ 2.409s]
finished. total time: 4.893s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\adb>adb reboot bootloader
error: device not found
And that's it, I'm a bit stumped not sure how to fix it so I can move onto installing the roms, any help would be greatly appreciated.
Anyone?
DId you install the Google USB driver?
If don't,please install the Android SDK and install all.
packyy said:
DId you install the Google USB driver?
If don't,please install the Android SDK and install all.
Click to expand...
Click to collapse
Yes, if I hadn't then I wouldnt have been able to use fastboot or install CWM.
No one? I thought this was the android super stars forum.
Can someone at lease suggest another forum with people willing to help?
Not a single person willing to help me out? Wow, thanks.

[Q] Moto E Indian soft brick

Hi,
I was trying to flash stock rom to my Moto E Indian version. It was running Cm 12 but suddenly it stopped detecting sim card. so I used this script to flash the stock firmware
mfastboot.exe oem lock begin
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe oem lock
pause
mfastboot.exe reboot
but flash wasnt successful and its now stuck at recovery loop. If I try to flash any custom rom from recovery it says unable to mound data and system. Tried everything I know but doesnt help.
when I flash the above script it shows CM boot logo and gets stuck there
Using this stock firmware RETAILDSDSALL_XT1022_4.4.4_KXC21.5-40_cid7_CFC
C:\MotoTool\ADB>"Retail+lock.bat"
C:\MotoTool\ADB>mfastboot.exe oem lock begin
...
(bootloader) Ready to flash signed images
OKAY [ 0.089s]
finished. total time: 0.092s
C:\MotoTool\ADB>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.028s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.577s
C:\MotoTool\ADB>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1669 KB)...
OKAY [ 0.099s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.574s
C:\MotoTool\ADB>mfastboot.exe flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (460 KB)...
OKAY [ 0.083s]
writing 'logo'...
OKAY [ 0.144s]
finished. total time: 0.233s
C:\MotoTool\ADB>mfastboot.exe flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.391s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.101s
C:\MotoTool\ADB>mfastboot.exe flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.399s]
writing 'recovery'...
OKAY [ 1.757s]
finished. total time: 2.161s
C:\MotoTool\ADB>mfastboot.exe flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (243072 KB)...
OKAY [ 7.676s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.348s
C:\MotoTool\ADB>mfastboot.exe flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (257254 KB)...
OKAY [ 8.128s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.197s
C:\MotoTool\ADB>mfastboot.exe flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (201709 KB)...
OKAY [ 6.381s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.447s
C:\MotoTool\ADB>mfastboot.exe flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (46132 KB)...
OKAY [ 1.507s]
writing 'modem'...
OKAY [ 4.589s]
finished. total time: 6.101s
C:\MotoTool\ADB>mfastboot.exe erase modemst1
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.013s
C:\MotoTool\ADB>mfastboot.exe erase modemst2
erasing 'modemst2'...
OKAY [ 0.022s]
finished. total time: 0.025s
C:\MotoTool\ADB>mfastboot.exe flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (649 KB)...
OKAY [ 0.106s]
writing 'fsg'...
OKAY [ 0.127s]
finished. total time: 0.237s
C:\MotoTool\ADB>mfastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.366s]
finished. total time: 0.369s
C:\MotoTool\ADB>mfastboot.exe erase userdata
erasing 'userdata'...
OKAY [ 1.415s]
finished. total time: 1.419s
C:\MotoTool\ADB>mfastboot.exe oem lock
...
(bootloader) sst lock failure!
OKAY [ 0.043s]
finished. total time: 0.046s
C:\MotoTool\ADB>pause
Press any key to continue . . .
C:\MotoTool\ADB>mfastboot.exe reboot
rebooting...
finished. total time: 0.002s
C:\MotoTool\ADB>
Hi, even I'm experiencing the same issue, it started after installing 2nd soak test. I tried downgrading but it showed few errors like you. Now my phone is stuck at 'M' logo, please let ne know if you have got any solution.
rizzee said:
Hi, even I'm experiencing the same issue, it started after installing 2nd soak test. I tried downgrading but it showed few errors like you. Now my phone is stuck at 'M' logo, please let ne know if you have got any solution.
Click to expand...
Click to collapse
Try the 5.1 factory images
please provide me the link of 5.1 if you have.
Here you go : Link
rizzee said:
please provide me the link of 5.1 if you have.
Click to expand...
Click to collapse
Why u all gave lock command at first?
Flashed with 5.1 stock image, now phone is booting in recovery mode and 'failed to validate system image' is flashing in pink color. Please help
rizzee said:
Flashed with 5.1 stock image, now phone is booting in recovery mode and 'failed to validate system image' is flashing in pink color. Please help
Click to expand...
Click to collapse
@abhi98228 You probably messed up the partitions. You ran useless commands which were not meant to be run. Never blindly download any script and run it without knowing what you are doing, be careful. Those unnecessary lock commands messed up your system. I don't know how to fix your partitions but try this.
Run each command ONE BY ONE in the order given below manually via command prompt. Don't download some stupid script from the internet and run it.
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Now see if it works.
nilanko said:
@abhi98228 You probably messed up the partitions. You ran useless commands which were not meant to be run. Never blindly download any script and run it without knowing what you are doing, be careful. Those unnecessary lock commands messed up your system. I don't know how to fix your partitions but try this.
Run each command ONE BY ONE in the order given below manually via command prompt. Don't download some stupid script from the internet and run it.
Code:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Now see if it works.
Click to expand...
Click to collapse
tried, not working. it is the primary phone of my younger brother. if possible reach me on whatsapp 8986834888
rizzee said:
tried, not working. it is the primary phone of my younger brother. if possible reach me on whatsapp 8986834888
Click to expand...
Click to collapse
Sorry I was talking to the OP. Can you tell us what did you do just before this problem started? Which commands did u run?
nilanko said:
Sorry I was talking to the OP. Can you tell us what did you do just before this problem started? Which commands did u run?
Click to expand...
Click to collapse
phone was running on 5.0.x soak test 1, i downloaded soak test 2 and updated it with system update. Updating went fine, but the phone got stuck at 'M' Logo after booting. Tried recovery and cleared cache and restored factory but in vain. then I tried downgrading with stock firmware 4.4.4 but nothing happened. Phone was still getting stuck at 'M' logo while booting. then I downloaded the 5.1 stock firmware from the link given above, used the commands you mentioned every thing during the process went ok but after completion thing got worse. when I try to turn it on it enters fastboot mode directly and shows "failed to validate system image".
rizzee said:
phone was running on 5.0.x soak test 1, i downloaded soak test 2 and updated it with system update. Updating went fine, but the phone got stuck at 'M' Logo after booting. Tried recovery and cleared cache and restored factory but in vain. then I tried downgrading with stock firmware 4.4.4 but nothing happened. Phone was still getting stuck at 'M' logo while booting. then I downloaded the 5.1 stock firmware from the link given above, used the commands you mentioned every thing during the process went ok but after completion thing got worse. when I try to turn it on it enters fastboot mode directly and shows "failed to validate system image".
Click to expand...
Click to collapse
Okay, the thing I am going to tell you is extremely important... So listen to me carefully:
1) Download TWRP and flash it using fastboot flash recovery recovery.img
2) Now reboot into recovery from the bootloader mode
3) after entering TWRP, Select Wipe, Advanced Wipe and Select all Partitions EXCLUDING your SD Card
After that is done, go to the Home menu of TWRP and select Reboot, Power Off
A warning will come saying no OS is installed and to fix root etc... Select DO NOT INSTALL, and your phone will power off.
Now boot into the bootloader mode, and flash the 5.1 image i gave you, executing each command as @nilanko told you to.
I have attached TWRP below:
Download
Rohitagni said:
Okay, the thing I am going to tell you is extremely important... So listen to me carefully:
1) Download TWRP and flash it using fastboot flash recovery recovery.img
2) Now reboot into recovery from the bootloader mode
3) after entering TWRP, Select Wipe, Advanced Wipe and Select all Partitions EXCLUDING your SD Card
After that is done, go to the Home menu of TWRP and select Reboot, Power Off
A warning will come saying no OS is installed and to fix root etc... Select DO NOT INSTALL, and your phone will power off.
Now boot into the bootloader mode, and flash the 5.1 image i gave you, executing each command as @nilanko told you to.
I have attached TWRP below:
Click to expand...
Click to collapse
I'm confused which one to download and install, there are many different versions available.
rizzee said:
I'm confused which one to download and install, there are many different versions available.
Click to expand...
Click to collapse
I made a correctin to the previous post
rizzee said:
phone was running on 5.0.x soak test 1, i downloaded soak test 2 and updated it with system update. Updating went fine, but the phone got stuck at 'M' Logo after booting. Tried recovery and cleared cache and restored factory but in vain. then I tried downgrading with stock firmware 4.4.4 but nothing happened. Phone was still getting stuck at 'M' logo while booting. then I downloaded the 5.1 stock firmware from the link given above, used the commands you mentioned every thing during the process went ok but after completion thing got worse. when I try to turn it on it enters fastboot mode directly and shows "failed to validate system image".
Click to expand...
Click to collapse
You currently have the 5.0.2 booloader. Maybe your bootloader and gpt needs to be upgraded and since it's the old one, it's failing to validate the newer 5.1 system. This is just a wild guess. If it shows that message with a green dead android, its not the fastboot mode. That image is inside the logo.bin of the 5.1 system. So nothing has changed, you are still stuck at the logo only, the difference being, the old logo.bin didn't show that the system validation was failing but this time it's showing up because of the upgraded logo.bin that's it.
You should also try unlocking your bootloader, maybe that will bypass the validity checks for originality. After unlocking, try flashing the firmware again. If still doesn't work, you gotta be brave and flash motoboot.img and gpt.bin as well. I DO NOT TAKE ANY GAURANTEE AND PLEASE DON'T BLAME ME IF ANYTHING GOES WRONG AFTER FLASHING BOOTLOADER AND GPT. DO IT AT YOUR OWN DISCRETION. I JUST TOLD YOU ABOUT SOME POSSIBILITIES, NOT ASKING YOU TO FOLLOW THEM.
nilanko said:
You currently have the 5.0.2 booloader. Maybe your bootloader and gpt needs to be upgraded and since it's the old one, it's failing to validate the newer 5.1 system. This is just a wild guess. If it shows that message with a green dead android, its not the fastboot mode. That image is inside the logo.bin of the 5.1 system. So nothing has changed, you are still stuck at the logo only, the difference being, the old logo.bin didn't show that the system validation was failing but this time it's showing up because of the upgraded logo.bin that's it.
You should also try unlocking your bootloader, maybe that will bypass the validity checks for originality. After unlocking, try flashing the firmware again. If still doesn't work, you gotta be brave and flash motoboot.img and gpt.bin as well. I DO NOT TAKE ANY GAURANTEE AND PLEASE DON'T BLAME ME IF ANYTHING GOES WRONG AFTER FLASHING BOOTLOADER AND GPT. DO IT AT YOUR OWN DISCRETION. I JUST TOLD YOU ABOUT SOME POSSIBILITIES, NOT ASKING YOU TO FOLLOW THEM.
Click to expand...
Click to collapse
Maybe you're right... He does have the 5.0.2 bootloader... So, flashing the 5.1 gpt.bin won't do any harm.
At least that is what I think
Rohitagni said:
Okay, the thing I am going to tell you is extremely important... So listen to me carefully:
1) Download TWRP and flash it using fastboot flash recovery recovery.img
2) Now reboot into recovery from the bootloader mode
3) after entering TWRP, Select Wipe, Advanced Wipe and Select all Partitions EXCLUDING your SD Card
After that is done, go to the Home menu of TWRP and select Reboot, Power Off
A warning will come saying no OS is installed and to fix root etc... Select DO NOT INSTALL, and your phone will power off.
Now boot into the bootloader mode, and flash the 5.1 image i gave you, executing each command as @nilanko told you to.
I have attached TWRP below:
Download
Click to expand...
Click to collapse
Hi, I downloaded TWRP from the like you provided. Now, please guide me the steps to flash it.
rizzee said:
Hi, I downloaded TWRP from the like you provided. Now, please guide me the steps to flash it.
Click to expand...
Click to collapse
Rename the file you have downloaded to recovery.img (ignore the img part if it is already present).
Now go to the bootloader mode of your phone, and then connect to your computer.
Open up the command prompt and type in fastboot flash recovery recovery.img.
On your phone something will appear like Partition Size mismatch or something. Ignore it.
Then when you get the message "OKAY" in the command prompt, disconnect your phone and USING ONLY the Vol Down button navigate to Recovery and press vol up.... Now u should be greeted with the TWRP screen.
Do this and tell me....
Rohitagni said:
Rename the file you have downloaded to recovery.img (ignore the img part if it is already present).
Now go to the bootloader mode of your phone, and then connect to your computer.
Open up the command prompt and type in fastboot flash recovery recovery.img.
On your phone something will appear like Partition Size mismatch or something. Ignore it.
Then when you get the message "OKAY" in the command prompt, disconnect your phone and USING ONLY the Vol Down button navigate to Recovery and press vol up.... Now u should be greeted with the TWRP screen.
Do this and tell me....
Click to expand...
Click to collapse
failed bootloader preflash validation failed
rizzee said:
failed bootloader preflash validation failed
Click to expand...
Click to collapse
It won't work unless you unlock your bootloader.
http://forum.xda-developers.com/showthread.php?t=2753110

Bootloader isn't unlocking even after OEM unlocking and USB Debugging is enabled

Everytime I type the command 'fastboot oem unlock', the screen says;
OKAY [ 0.002s]
finished. total time: 0.002s
but then when I want to flash a recovery it says;
target reported max download size of 1073741824 bytes
sending 'recovery' (15482 KB)...
OKAY [ 0.498s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)<<< Why does this happen? -_-
finished. total time: 0.501s
Anybody has a solution for this?
Have you tried just flashing stock recovery? Does it say that for everything you try and flash? A lot of people are trying these shortcuts to try and upgrade bootloader. Though most can work the safest bet is to flash original stock recovery and upgrade from there. You might be looking at going through the hard brick guide.
seems like you locked the bootloader while you are rooted...iam stack on same step too...
Exodusche said:
Have you tried just flashing stock recovery? Does it say that for everything you try and flash? A lot of people are trying these shortcuts to try and upgrade bootloader. Though most can work the safest bet is to flash original stock recovery and upgrade from there. You might be looking at going through the hard brick guide.
Click to expand...
Click to collapse
But everything else works. And yeah, I did try flashing the stock recovery too
Fastboot oem unlock>fastboot reboot>doesn't ask about wiping
I've followed every tutorial they all say that after requesting oem unlock, you can verify the unlock was successful with fastboot oem devices-info> device tampered-false, device unlock-true, then fastboot reboot> system reboot, but it does NOT ask to wipe the data. Am I missing something?
Ubuntu_noobi said:
I've followed every tutorial they all say that after requesting oem unlock, you can verify the unlock was successful with fastboot oem devices-info> device tampered-false, device unlock-true, then fastboot reboot> system reboot, but it does NOT ask to wipe the data. Am I missing something?
Click to expand...
Click to collapse
Not necessarly.
If it 's device unlock-true , you're OK. If not...

Need help with softbrick (Xperia Z C6603)

Hello. Today i tried to flash the phone to the stock ROM twice but it didnt work probably cause unlocked bootloader and custom recovery (TWRP).
So i brick the phone and now i cant access the rom or the recovery. All i can do is access the fastboot mode. I tried to install the new recovery through fastboot but it doesnt work.
I tried the twrp 3.0.2.0 and 3.0.1.0 for yuga.
Code:
C:\Users\Kubo\Downloads\platform-tools>fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.342s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.347s
Tried various of commands that i found on google and this forum but nothing worked. I unlocked the bootloader before when i was installing various of custom roms. Could somehow stock rom affect the bootloader when i was flashing through flashtool ? I tried to only boot the recovery from the img, the command worked but the recovery did not boot.
Code:
C:\Users\Kubo\Downloads\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.341s]
booting...
OKAY [ 0.033s]
finished. total time: 0.378s
Tried to check the status of bootloader but the command is just showing ... and nothing happend. Tried to get the IMEI through fastboot getvar command but no output is given. Im desperate. Sorry for english not my native language. I'll appreciate all the help.

Categories

Resources