I've got a Mate7 (MT7-L09) that I bought used, from the look of it, it's been previously unlocked (which is good, since I've been unable to get an unlock code from Huawei for it), and is running the latest L09 factory rom (See attached screen shot, yep, says unlocked.)
Unfortunately, when I try to flash CWM, I get the following:
[email protected]:~/android-sdk-linux/platform-tools$ sudo ./fastboot flash recovery recovery_h60.img
target reported max download size of 471859200 bytes
sending 'recovery' (9386 KB)...
OKAY [ 1.790s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.795s
Attempting to flash the stock recovery works just fine. I've downloaded a couple of different copies of CWM and they all fail with the same error. I've also tried under Windows with the same error.
I've also tried flashing the factory image from the SD card to return the phone to 'stock' before again trying to flash CWM, this also did not fix the problem.
Any ideas?
Thanks!
Justin
Turbo4V said:
I've got a Mate7 (MT7-L09) that I bought used, from the look of it, it's been previously unlocked (which is good, since I've been unable to get an unlock code from Huawei for it), and is running the latest L09 factory rom (See attached screen shot, yep, says unlocked.)
Unfortunately, when I try to flash CWM, I get the following:
[email protected]:~/android-sdk-linux/platform-tools$ sudo ./fastboot flash recovery recovery_h60.img
target reported max download size of 471859200 bytes
sending 'recovery' (9386 KB)...
OKAY [ 1.790s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.795s
Attempting to flash the stock recovery works just fine. I've downloaded a couple of different copies of CWM and they all fail with the same error. I've also tried under Windows with the same error.
I've also tried flashing the factory image from the SD card to return the phone to 'stock' before again trying to flash CWM, this also did not fix the problem.
Any ideas?
Thanks!
Justin
Click to expand...
Click to collapse
man who told u flash that crap cwm which is not even for mate 7 ???
where did u get that crap.. thats for honor 6 or p7..
check mate 7 forum (general) and ull find PROPER recovery cwm for mate 7 !
i think i gave u lots of clues..
And if u tried to flash other CWMs ten u have old flash adb fastboot files..
u need latest ones supports higher sizes
Simona Simmy said:
man who told u flash that crap cwm which is not even for mate 7 ???
where did u get that crap.. thats for honor 6 or p7..
check mate 7 forum (general) and ull find PROPER recovery cwm for recovery_h60.imgmate 7 !
i think i gave u lots of clues..
And if u tried to flash other CWMs ten u have old flash adb fastboot files..
u need latest ones supports higher sizes
Click to expand...
Click to collapse
This is actually a recovery for the HAM7, not the Honor6/P7. Recovery_h60.img is just what the recovery was initially called (check the thread http://forum.xda-developers.com/mat...custom-recovery-tool-mt7-l10-l10-mt7-t3022424). I got the CWM file from that thread.
I've also tried the updated version posted in the same thread (MT7_CWM_CN_EN.img) with the same results.
sudo ./fastboot flash recovery MT7_CWM_CN_EN.img
target reported max download size of 471859200 bytes
sending 'recovery' (9390 KB)...
OKAY [ 1.800s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.805s
Finally, I have the latest adb/fastboot from the latest android SDK (for linux). As I mentioned, I also tried it under Windows with the included adb/fastboot with no differences.
Thanks for you help!
Turbo4V said:
This is actually a recovery for the HAM7, not the Honor6/P7. Recovery_h60.img is just what the recovery was initially called (check the thread http://forum.xda-developers.com/mat...custom-recovery-tool-mt7-l10-l10-mt7-t3022424). I got the CWM file from that thread.
I've also tried the updated version posted in the same thread (MT7_CWM_CN_EN.img) with the same results.
sudo ./fastboot flash recovery MT7_CWM_CN_EN.img
target reported max download size of 471859200 bytes
sending 'recovery' (9390 KB)...
OKAY [ 1.800s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.805s
Finally, I have the latest adb/fastboot from the latest android SDK (for linux). As I mentioned, I also tried it under Windows with the included adb/fastboot with no differences.
Thanks for you help!
Click to expand...
Click to collapse
jeezz
download thiiis alright ? and REPORT success ! To ME
https://www.sendspace.com/file/u5jkys
Simona Simmy said:
jeezz
download thiiis alright ? and REPORT success ! To ME
https://www.sendspace.com/file/u5jkys
Click to expand...
Click to collapse
I just tried flashing your file, and get the same result:
sudo ./fastboot flash recovery MATE7_CWM.img
target reported max download size of 471859200 bytes
sending 'recovery' (9390 KB)...
OKAY [ 1.790s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.795s
Just for grins, I compared your file to the one that I was flashing before, and they are identical.
diff -s MATE7_CWM.img MT7_CWM_CN_EN.img
Files MATE7_CWM.img and MT7_CWM_CN_EN.img are identical
Any more ideas?
Thanks!
Jsutin
Turbo4V said:
I just tried flashing your file, and get the same result:
sudo ./fastboot flash recovery MATE7_CWM.img
target reported max download size of 471859200 bytes
sending 'recovery' (9390 KB)...
OKAY [ 1.790s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.795s
Just for grins, I compared your file to the one that I was flashing before, and they are identical.
diff -s MATE7_CWM.img MT7_CWM_CN_EN.img
Files MATE7_CWM.img and MT7_CWM_CN_EN.img are identical
Any more ideas?
Thanks!
Jsutin
Click to expand...
Click to collapse
U still want idea ?? u have NOT get it already?? where did u purchased it from ?? and u already thinking WHY someone got rid of it ??
Does the phone normally working ???
Did u install huawei latest drivers?
Simona Simmy said:
U still want idea ?? u have NOT get it already?? where did u purchased it from ?? and u already thinking WHY someone got rid of it ??
Does the phone normally working ???
Did u install huawei latest drivers?
Click to expand...
Click to collapse
Purchased from Swappa, device works perfectly besides not being able to flash recovery.
I've been able to put the stock Huawei firmware on an SD card and flash that. (127)
I suppose you could be correct, maybe there's something wrong with the device, but that seems unlikely given that everything else works. One thing I'm thinking is that the phone is not actually unlocked (even though it says it is on the recovery screen). Wish I could get an unlock code for this thing to try re-locking and unlocking it.
Thanks for your help.
Turbo4V said:
Purchased from Swappa, device works perfectly besides not being able to flash recovery.
I've been able to put the stock Huawei firmware on an SD card and flash that. (127)
I suppose you could be correct, maybe there's something wrong with the device, but that seems unlikely given that everything else works. One thing I'm thinking is that the phone is not actually unlocked (even though it says it is on the recovery screen). Wish I could get an unlock code for this thing to try re-locking and unlocking it.
Thanks for your help.
Click to expand...
Click to collapse
I posted already procedure how to unlock phone..
U need tools for it ..
But now am going to bed.. so check out mine threads or posts .. it is here..
Simona Simmy said:
I posted already procedure how to unlock phone..
U need tools for it ..
But now am going to bed.. so check out mine threads or posts .. it is here..
Click to expand...
Click to collapse
Thanks, I've tried using the tools, and the code generated ends up not working on the Huawei web site. (See attached). Additionally, I've tried requesting the code from Huawei, and they say that unlocking is not available for the L09
From Huawei:
Huawei Dear user:
Hello, Thank you for using Huawei's products. MT7-L09 is currently not supported by the application unlock code if you want to brush Root or third-party systems, you can go online to search to see if there is a corresponding method. After the phone Root, though not affect the warranty, but if it is due to appear Root performance was a result of failure or system problems may affect your warranty love machine, specifically whether the warranty is to be detected by the service network, then you careful consideration! THX!
Huawei Customer Service Center
Thanks again for your help, just wanted others to see the process incase they were encountering similar problems.
Justin
Turbo4V said:
Thanks, I've tried using the tools, and the code generated ends up not working on the Huawei web site. (See attached). Additionally, I've tried requesting the code from Huawei, and they say that unlocking is not available for
Click to expand...
Click to collapse
You can try Y300-100 or something like or try to relock
Simona Simmy said:
You can try Y300-100 or something like or try to relock
Click to expand...
Click to collapse
Tried that one too (and a few other models), same message.
Thanks,
Justin
Turbo4V said:
Tried that one too (and a few other models), same message.
Thanks,
Justin
Click to expand...
Click to collapse
only one thing ..
get vroot : http://forum.xda-developers.com/showthread.php?t=2434453
root it ...
download flashy : https://play.google.com/store/apps/details?id=com.cgollner.flashify
flash super su (first copy it into your sc card)
delete vroot ..
download install su :https://play.google.com/store/apps/details?id=eu.chainfire.supersu
Simona Simmy said:
You can try Y300-100 or something like or try to relock
Click to expand...
Click to collapse
Thanks again for the ideas, but that root method looks a bit sketchy (malware etc). I guess I'll just leave things 'as-is' for now, hopefully I'll be able to figure out the whole lock/relock thing one day!
Justin
Turbo4V said:
Thanks again for the ideas, but that root method looks a bit sketchy (malware etc). I guess I'll just leave things 'as-is' for now, hopefully I'll be able to figure out the whole lock/relock thing one day!
Justin
Click to expand...
Click to collapse
doont worry .. just root it .. i had it and all was ok . .u will have it just for 5-10 mins.. by that time nothing will happen.
forgot to mention.. after installing flashy flash recovery (CWM) that flashy provides download and flash..
then after installing CWM go there and flash super su
Have the same problem and my Mate7 TL7-09 also has unlocked bootloader (verified with fastboot oem getinfo-bootloader) just cannot get CWM to flash.
djpharoah said:
Have the same problem and my Mate7 TL7-09 also has unlocked bootloader (verified with fastboot oem getinfo-bootloader) just cannot get CWM to flash.
Click to expand...
Click to collapse
Here.... the same problem
Use FLASHIFY that's how I bounce back and forth with recoveries.
Turbo4V said:
I just tried flashing your file, and get the same result:
sudo ./fastboot flash recovery MATE7_CWM.img
target reported max download size of 471859200 bytes
sending 'recovery' (9390 KB)...
OKAY [ 1.790s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 1.795s
Just for grins, I compared your file to the one that I was flashing before, and they are identical.
diff -s MATE7_CWM.img MT7_CWM_CN_EN.img
Files MATE7_CWM.img and MT7_CWM_CN_EN.img are identical
Any more ideas?
Thanks!
Jsutin
Click to expand...
Click to collapse
Sounds like your boot loader is still locked or has be relocked again. That's the error you get when boot loader is locked and fast boot can't flash to the partition. Hence the "remote failure" error you're getting.
---------- Post added at 01:38 PM ---------- Previous post was at 01:34 PM ----------
Simona Simmy said:
doont worry .. just root it .. i had it and all was ok . .u will have it just for 5-10 mins.. by that time nothing will happen.
forgot to mention.. after installing flashy flash recovery (CWM) that flashy provides download and flash..
then after installing CWM go there and flash super su
Click to expand...
Click to collapse
Regardless how long you think you may have "vroot" on tour device , there's no telling what type of malware will remain hidden on it. Or what its communicating back to where ever
Hi,
I recently want to root my Honor 8 FRD-L09 on N 7.0.
So i unlock the bootloader, and flash the recovery.
But i never could do it, I always got an error with fastboot
C:\Users\Hugo\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.386s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.392s
I don't know what to do.
are you sure you dont have FRP lock activated?
well thats why it wont flash. BL unlocked means nothing if you're FRP locked. you have 2 choices. try removing all security options and accounts / factory reset and hope FRP lock is removed, or use dload method to reflash stock rom. you wont be able to flash twrp otherwise, well, unless u use some of those "pay to remove FRP lock" tools
hypnotik8systeme said:
are you sure you dont have FRP lock activated?
well thats why it wont flash. BL unlocked means nothing if you're FRP locked. you have 2 choices. try removing all security options and accounts / factory reset and hope FRP lock is removed, or use dload method to reflash stock rom. you wont be able to flash twrp otherwise, well, unless u use some of those "pay to remove FRP lock" tools
Click to expand...
Click to collapse
Yes i got frp lock i will try To see tomorrow
ImEraaz said:
Yes i got frp lock i will try To see tomorrow
Click to expand...
Click to collapse
Did it work? If, can you tell me how you did it?
ImEraaz said:
Hi,
I recently want to root my Honor 8 FRD-L09 on N 7.0.
So i unlock the bootloader, and flash the recovery.
But i never could do it, I always got an error with fastboot
C:\Users\Hugo\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.386s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.392s
I don't know what to do.
Click to expand...
Click to collapse
FRP lock and system security triggers in bootloader itself cause that some partition/blocks are unaccessible even when there is a "full" unlocked bootloader, but full unlocked bootloader option is not as it should be.
Security options while flashing some partition and the system flashing boot loops security option enables this well known security feature.
ImEraaz said:
Hi,
I recently want to root my Honor 8 FRD-L09 on N 7.0.
So i unlock the bootloader, and flash the recovery.
But i never could do it, I always got an error with fastboot
C:\Users\Hugo\Desktop\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.386s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.392s
I don't know what to do.
Click to expand...
Click to collapse
Enable OEM unlock.... In developer setting
EDIT: Guys it worked. Some weird **** happened first, keyboard wasn't working on stock rom and everything was buggy but after an update with HiSuite and a factory reset everything works fine. Thank you for all your support.
I bricked my Honor 8 (FRD-L09) while trying to go back to stock rom. I can only acces eRecovery and Fastboot, when I try to access normal recovery, the screen just freezes at "Your device is booting now". After reading multiple guides, I tried unbricking with the Huawei Multitool but I always get these errors:
sending 'boot' (15464 KB)...
OKAY [ 0.334s]
writing 'boot'...
OKAY [ 0.371s]
finished. total time: 0.710s
target reported max download size of 471859200 bytes
sending 'cust' (433554 KB)...
OKAY [ 9.343s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 9.358s
target reported max download size of 471859200 bytes
sending 'recovery' (36996 KB)...
OKAY [ 0.794s]
writing 'recovery'...
OKAY [ 0.883s]
finished. total time: 1.682s
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (435393 KB)...
OKAY [ 10.280s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 10.327s
I'm desperate and I don't know what to do.
EDIT: I HAVE MANAGED TO INSTALL RR BUT STILL CAN'T GO BACK TO STOCK.
Rommco05 said:
Hi, what about twrp u loos access?
Click to expand...
Click to collapse
I have regained access to twrp. I have installed a custom rom, but still can't install stock rom.
Rommco05 said:
Your hole model number is? U try yo flash stock rom via twrp?
Click to expand...
Click to collapse
FRD-L09. I haven't flashed stock rom via TWRP. I tried the huawei extractor method right now, I'm probably doing something wrong, I'll look more into it . I'm calm now that I managed to install a custom rom.
Rommco05 said:
Ok, so if still without luck try to download full stock fw B360 or B381 (2 zips)
Click to expand...
Click to collapse
Ok.. I will try that. My phone is stuck at "your device is booting up" screen after flashing stock recovery.
Note that there is also recovery2 in first update.zip when you extract it via Huawei Multitool. Thats probably why recovery never boots up, it's not all. Try to send the first basic ones - boot, recovery, recovery2, erecovery, and so on (don't exactly remember which). Then you should be fine to dload or flash the rest through fastboot (if possible). And remember to always use full-ota-mf-pv version of software (like FRD-L09C432B381) with about 2.37 GB total (2 zip files).
Rommco05 said:
You can flash back twrp?
Click to expand...
Click to collapse
Yes, I can.
So, did it work?!
PalakMi said:
So, did it work?!
Click to expand...
Click to collapse
I'm at work now. I'll try after a few hours.
Radu Florin said:
I'm at work now. I'll try after a few hours.
Click to expand...
Click to collapse
Good luck, I hope it works after all
Guys it worked. Some weird **** happened first, keyboard wasn't working on stock rom and everything was buggy but after an update with HiSuite and a factory reset everything works fine. Thank you for all your support.
Radu Florin said:
Guys it worked. Some weird **** happened first, keyboard wasn't working on stock rom and everything was buggy but after an update with HiSuite and a factory reset everything works fine. Thank you for all your support.
Click to expand...
Click to collapse
Great , your device is back :highfive:
Hi All,
I need some help please with (soft?) bricked Note 7 pro. I have the global version and installed e. foundation ROM which is a fork of LineageOS. This was working well until I loaded the latest version last week. Now the phone seems to be softbricked.
I can get into fastboot. I have downloaded TWRP violet and when I run "fastboot flash recovery twrp-3.3.0-0-violet.img" I get:
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.723s]
writing 'recovery'...
OKAY [ 0.370s]
finished. total time: 2.093s
However when I try to boot into that recovery it wont work. (I just see the "Redmi by Xiaomi" screen with the "unlocked" detail at the bottom.
I also tried to run "fastboot boot twrp-3.3.0-0-violet.img" but that leads to a "system has been destroyed" message.
I downloaded the Mi unlock tool and tried to unlock again, just in case, but that tool reported that the phone is unlocked already.
I should point out that I get the same result with twrp-3.3.1-0-violet.img
Does anyone have any suggestions as to what I can try next? I am reluctant to remove the back from the phone.
Thanks
jimmy987654321 said:
Hi All,
I need some help please with (soft?) bricked Note 7 pro. I have the global version and installed e. foundation ROM which is a fork of LineageOS. This was working well until I loaded the latest version last week. Now the phone seems to be softbricked.
I can get into fastboot. I have downloaded TWRP violet and when I run "fastboot flash recovery twrp-3.3.0-0-violet.img" I get:
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 1.723s]
writing 'recovery'...
OKAY [ 0.370s]
finished. total time: 2.093s
However when I try to boot into that recovery it wont work. (I just see the "Redmi by Xiaomi" screen with the "unlocked" detail at the bottom.
I also tried to run "fastboot boot twrp-3.3.0-0-violet.img" but that leads to a "system has been destroyed" message.
I downloaded the Mi unlock tool and tried to unlock again, just in case, but that tool reported that the phone is unlocked already.
I should point out that I get the same result with twrp-3.3.1-0-violet.img
Does anyone have any suggestions as to what I can try next? I am reluctant to remove the back from the phone.
Thanks
Click to expand...
Click to collapse
Use Peter's twrp or flash fastboot rom with miflash
urstrulynaveen said:
Use Peter's twrp or flash fastboot rom with miflash
Click to expand...
Click to collapse
Thanks. Ive never heard of Peters TWRP so I'll try that next. Cheers.
jimmy987654321 said:
Thanks. Ive never heard of Peters TWRP so I'll try that next. Cheers.
Click to expand...
Click to collapse
Thanks urstrulynaveen, that worked a treat. I'm very grateful. All back up and running now.
jimmy987654321 said:
Thanks urstrulynaveen, that worked a treat. I'm very grateful. All back up and running now.
Click to expand...
Click to collapse
Were you able to lock your bootloader
Hello guys !
I know there is like 88 thousand threads on this kind of problem, but bellieve me i've read them all and none of them worked !
I have a serious problem, it's been a week now since i'm looking for a solution, looking at hundreds of guide and threads and different websites... still no results !
I have a Huawei P8 Lite 2017. That i wanna root using the magisk and twrp method (from Pokémon GO Spoofing ; [Android] All the working Android methods 2020) on reddit
I have my phone Unlocked
FRP unlocked
OEM enabled
USB deboging enable
Automatic system update disabled
This is what my bootloader screen says
"Phone Unlocked"
"FRP Unlocked"
i have managed to flash my phone with my twrp.img
C:\adb>fastboot flash recovery_ramdisk twrp.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (26226 KB)...
OKAY [ 1.003s]
writing 'recovery_ramdisk'...
OKAY [ 0.348s]
finished. total time: 1.366s
Click to expand...
Click to collapse
But impossible to access the recovery ! always says "command not allowed"
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 1.056s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 1.072s
Click to expand...
Click to collapse
(I have the exact same problem using the commands from the platform tool folder, and my adb drivers are updated (via ADBDriverInstaller)
I've downloaded this TWRP ; twrp-3.1.1-0-grace.img (for huawei P8) (Note that version twrp-3.1.0-0 and twrp-3.0.2-0 do not work either)
I have already tried to access the recovery screen manually right after the flash (using vol Up + Power button on huawei) and i got this error
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
I have N.O idea where is the problem !
If you can please help a man in need ^^
Thank you guys !
Anyone ?