Related
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
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:
I tried to root by flashing the patched boot image as describe in https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280. After that, the phone went into a bootloop.
When I get to the eRecovery screen, I tried 'Download latest version and recovery.' It got to 'getting package information from server' but then stopped with 'getting package info failed.'
I then tried 'Wipe data/factory reset' and it rebooted but nothing changed.
I don't know what else to try with this phone. None of the current versions of twrp would run on it. I've never bricked a device in years of rooting.
thecdn said:
I tried to root by flashing the patched boot image as describe in https://forum.xda-developers.com/ho...gisk-root-honor-view-10-mate-10-pro-t3749280. After that, the phone went into a bootloop.
When I get to the eRecovery screen, I tried 'Download latest version and recovery.' It got to 'getting package information from server' but then stopped with 'getting package info failed.'
I then tried 'Wipe data/factory reset' and it rebooted but nothing changed.
I don't know what else to try with this phone. None of the current versions of twrp would run on it. I've never bricked a device in years of rooting.
Click to expand...
Click to collapse
You need to restore your original ramdisk. Also, you have to patch your own ramdisk.img with Magisk Manager if you want to try rooting your device.
And btw, this is a development forum, not General or Q&A one. Read carefully before trying to mod this device, or you will end up with an expensive brick.
please contact me on hangouts i may be able to help [email protected]
You can download the appropriate images to restore your device below. These are for the US variant (BKL-L04)
https://drive.google.com/open?id=1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
Edit: Link updated
[email protected]_USA said:
You can download the appropriate images to restore your device below. These are for the US variant (BKL-L04)
https://drive.google.com/open?id=1kf...yiH2t-srYBBvN3
Click to expand...
Click to collapse
I"m getting a web page not found 404 when I try that link.
thecdn said:
I"m getting a web page not found 404 when I try that link.
Click to expand...
Click to collapse
Same
thecdn said:
I"m getting a web page not found 404 when I try that link.
Click to expand...
Click to collapse
freeza said:
Same
Click to expand...
Click to collapse
look like chris didnt updated the link,
bdw here you guys go https://drive.google.com/open?id=1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
I flashed the system.img and the recovery_ramdisk.img. It booted to the eRecovery screen again.
I tried 'Download latest version and recovery' and it failed with the 'getting package info failed' error again.
I then tried 'Wipe data/factory reset' and unlike before, it actually went through and said it was successfully completed. But then it rebooted twice and went back to the eRecovery screen again.
Any ideas on how to proceed from here?
ETA: When I pressed vol up/power after this it went to a screen which said 'software install failed' instead of the recovery screen I thougt it would go to. After the first time, pressing vol up/power goes to the EMUI screen with the options of 'Reboot' 'Wipe data/factory reset' and 'Wipe cache partition.'
thecdn said:
I flashed the system.img and the recovery_ramdisk.img. It booted to the eRecovery screen again.
I tried 'Download latest version and recovery' and it failed with the 'getting package info failed' error again.
I then tried 'Wipe data/factory reset' and unlike before, it actually went through and said it was successfully completed. But then it rebooted twice and went back to the eRecovery screen again.
Any ideas on how to proceed from here?
ETA: When I pressed vol up/power after this it went to a screen which said 'software install failed' instead of the recovery screen I thougt it would go to. After the first time, pressing vol up/power goes to the EMUI screen with the options of 'Reboot' 'Wipe data/factory reset' and 'Wipe cache partition.'
Click to expand...
Click to collapse
You need to restore ramdisk, not recovery_ramdisk.
Pretoriano80 said:
You need to restore ramdisk, not recovery_ramdisk.
Click to expand...
Click to collapse
I did 'fastboot flash ramdisk ramdisk.img' and it still does a couple of reboots and then goes back to the EMUI screen with the recovery/reset/reboot/shutdown options.
In summary, this morning I did:
'fastboot flash system system.img' which resulted in 7 occurances of 'sending sparse system x/7 (xxxx KB)...' - which I have never seen before but all finished with OKAY
'fastboot flash recovery_ramdisk recovery_ramdisk.img'
'fastboot flash ramdisk ramdisk.img'
Is there something else I could do or redo in a particular order?
thecdn said:
I did 'fastboot flash ramdisk ramdisk.img' and it still does a couple of reboots and then goes back to the EMUI screen with the recovery/reset/reboot/shutdown options.
In summary, this morning I did:
'fastboot flash system system.img' which resulted in 7 occurances of 'sending sparse system x/7 (xxxx KB)...' - which I have never seen before but all finished with OKAY
'fastboot flash recovery_ramdisk recovery_ramdisk.img'
'fastboot flash ramdisk ramdisk.img'
Is there something else I could do or redo in a particular order?
Click to expand...
Click to collapse
Try to also flash kernel : fastboot flash kernel kernel.img
Pretoriano80 said:
Try to also flash kernel : fastboot flash kernel kernel.img
Click to expand...
Click to collapse
No joy yet but I do appreciate all the help.
thecdn said:
No joy yet but I do appreciate all the help.
Click to expand...
Click to collapse
Did you tried a factory reset from stock recovery?
Pretoriano80 said:
Did you tried a factory reset from stock recovery?
Click to expand...
Click to collapse
I've tried two factory resets after completing the above mentioned actions. Both times reported they were successful it still won't boot to the os, goes to the EMUI screen after several boot attempts.
Same problem here on a US BKL-L04 =(
I flashed a magisk modified ramdisk.img and have been in bootloop ever since.
I've downloaded and flashed recovery_ramdisk.img, ramdisk.img, and kernel.img from the link earlier in this thread: https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
I've then did "Wipe data/factory reset" from Huawei eRecovery - no luck
$ fastboot flash ramdisk ramdisk.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.401s]
writing 'ramdisk'...
OKAY [ 0.083s]
finished. total time: 0.484s
$ fastboot flash recovery_ramdisk recovery_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 0.807s]
writing 'recovery_ramdisk'...
OKAY [ 0.164s]
finished. total time: 0.971s
sek stock2 $ fastboot flash kernel kernel.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.615s]
writing 'kernel'...
OKAY [ 0.128s]
finished. total time: 0.745s
Aside from fastboot happing very quickly (< 1 second even for 32 meg recovery_ramdisk.img) everything seems to work fine... The phone just no longer boots - it trys a few times - displaying the "Your device has been unlocked and can't be trusted" screen for quite a while and the non-animated blue honor screen briefly and then ends up in EMUI eRecovery.
Are these files still up to date? Or perhaps there were newer versions on my phone and that's why flashing the older ones isn't working?
Also worth noting, I'm flashing from a mac with Android sdk fastbook:
$ fastboot --version
fastboot version 0.0.1-4500957
Installed as /Users/sek/Library/Android/sdk/platform-tools/fastboot
Thanks for any help / tips!
akasek said:
I flashed a magisk modified ramdisk.img and have been in bootloop ever since.
I've downloaded and flashed recovery_ramdisk.img, ramdisk.img, and kernel.img from the link earlier in this thread: https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
I've then did "Wipe data/factory reset" from Huawei eRecovery - no luck
$ fastboot flash ramdisk ramdisk.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.401s]
writing 'ramdisk'...
OKAY [ 0.083s]
finished. total time: 0.484s
$ fastboot flash recovery_ramdisk recovery_ramdisk.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 0.807s]
writing 'recovery_ramdisk'...
OKAY [ 0.164s]
finished. total time: 0.971s
sek stock2 $ fastboot flash kernel kernel.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.615s]
writing 'kernel'...
OKAY [ 0.128s]
finished. total time: 0.745s
Aside from fastboot happing very quickly (< 1 second even for 32 meg recovery_ramdisk.img) everything seems to work fine... The phone just no longer boots - it trys a few times - displaying the "Your device has been unlocked and can't be trusted" screen for quite a while and the non-animated blue honor screen briefly and then ends up in EMUI eRecovery.
Are these files still up to date? Or perhaps there were newer versions on my phone and that's why flashing the older ones isn't working?
Also worth noting, I'm flashing from a mac with Android sdk fastbook:
$ fastboot --version
fastboot version 0.0.1-4500957
Installed as /Users/sek/Library/Android/sdk/platform-tools/fastboot
Thanks for any help / tips!
Click to expand...
Click to collapse
Flash stock kernel, ramdisk and recovery ramdisk for your model in fastboot and you'll be able to boot again
Rommco05 said:
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Use this tool for flash full fw
Click to expand...
Click to collapse
Thanks for the info, that tool looks interesting. Where can I get the stock files for BKL-L04 US version Honor View 10?
I have now tried flashing kernel, ramdisk, recovery_ramdisk and system from both of these sources:
- https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
- http://arter97.com/browse/v10/stock/BKL-L04/
They all appear to flash fine. I tried flashing vendor.img as well, but get an error on that:
$ fastboot flash vendor vendor.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/2 (445713 KB)...
OKAY [ 9.718s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 9.724s
It still doesn't want to boot. I end up in eRecovery each time.
I am able to flash TWRP from Pretoriano80: https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
It seems to be working properly, perhaps that helps me somehow?
Finally back up and running - Thanks Tecalote!
FYI: I am finally back up and running - Tecalote's post worked perfectly (and BKL-L04 update zips are linked earlier in the thread also): https://forum.xda-developers.com/showpost.php?p=76331841&postcount=46
akasek said:
Thanks for the info, that tool looks interesting. Where can I get the stock files for BKL-L04 US version Honor View 10?
I have now tried flashing kernel, ramdisk, recovery_ramdisk and system from both of these sources:
- https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
- http://arter97.com/browse/v10/stock/BKL-L04/
They all appear to flash fine. I tried flashing vendor.img as well, but get an error on that:
$ fastboot flash vendor vendor.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/2 (445713 KB)...
OKAY [ 9.718s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 9.724s
It still doesn't want to boot. I end up in eRecovery each time.
I am able to flash TWRP from Pretoriano80: https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
It seems to be working properly, perhaps that helps me somehow?
Click to expand...
Click to collapse
akasek said:
Thanks for the info, that tool looks interesting. Where can I get the stock files for BKL-L04 US version Honor View 10?
I have now tried flashing kernel, ramdisk, recovery_ramdisk and system from both of these sources:
- https://drive.google.com/drive/folders/1kfNAjIwiMj8wpeDuJayiH2t-srYBBvN3
- http://arter97.com/browse/v10/stock/BKL-L04/
They all appear to flash fine. I tried flashing vendor.img as well, but get an error on that:
$ fastboot flash vendor vendor.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'vendor' 1/2 (445713 KB)...
OKAY [ 9.718s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 9.724s
It still doesn't want to boot. I end up in eRecovery each time.
I am able to flash TWRP from Pretoriano80: https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
It seems to be working properly, perhaps that helps me somehow?
Click to expand...
Click to collapse
try to install twrp and then do hruupdate from twrp
get your files from firmware finder and search xda forums to how to install those files
its very easy and your system will be back in stock format
after that you can try to root and install custom rom
thecdn said:
No joy yet but I do appreciate all the help.
Click to expand...
Click to collapse
Hi, what helped you there? I have a similar situation.
"Hi,
I need some advice on what can be done with my Honor View10 as it keeps gracing a bootloop followed by fasrboot mode.
Mine is a C675 variant and I was on 190 when I decided to unroot and update the device to 218. Once that was done, I flashed a patched recovery_ramdisk boot image that was patched using magisk to support it. Worked fine. Did a reboot and it got stuck in a bootloop.
I have tried flashing other patch.imgs too, due instance tried extracting recovery.img of the current version of rom, flashed it, no luck!
Tried flashing the patched version of that, still did not help.
I am on EMUI9, any help please?
Also can anyone help me with the link of one of the latest versions of C675 update please? "
This is what happened to me
Hi,
So @Pretoriano80 's twrp_mate9_0.1.img is booting on AGS2 ! But with no internal data decryption.
https://forum.xda-developers.com/showpost.php?do=showpost&p=76362629
m::
Any better twrp I could try ?
twrp_bkl_0.6 & 0.7 got both stuck on twrp's bootscreen with AGS2.
By the way, AGS2 device are Kirin659 and EMUI8.0 .
EDIT: HuRUpdater is working fine with twrp_mate9_0.1.img on AGS2 !
oslo83 said:
Hi,
So @Pretoriano80 's twrp_mate9_0.1.img is booting on AGS2 ! But with no internal data decryption.
https://forum.xda-developers.com/showpost.php?do=showpost&p=76362629
m::
Any better twrp I could try ?
twrp_bkl_0.6 & 0.7 got both stuck on twrp's bootscreen with AGS2.
By the way, AGS2 device are Kirin659 and EMUI8.0 .
EDIT: HuRUpdater is working fine with twrp_mate9_0.1.img on AGS2 !
Click to expand...
Click to collapse
Hi @oslo83
Last Monday I bought a Huawei Mediapad T5. I like the tablet but can't find anywhere, information/tutorials about unlock the bootloader and root the tablet. Did you manage to root your tablet? If so can you help me to root mine?
Thanks in advance.
To root it you ll need to unlock bootloader.
To do that you ll need a code Huawei is not giving anymore.
Since January 15th, 3rd party seller sold it 2 times lasting each for 2 or 3 days.
oslo83 said:
To root it you ll need to unlock bootloader.
To do that you ll need a code Huawei is not giving anymore.
Since January 15th, 3rd party seller sold it 2 times lasting each for 2 or 3 days.
Click to expand...
Click to collapse
I saw this method https://cetapan.com/how-to-unlock-b...-custom-recovery-and-root-huawei-mediapad-t5/
Do you think it would work?
oslo83 said:
To root it you ll need to unlock bootloader.
To do that you ll need a code Huawei is not giving anymore.
Since January 15th, 3rd party seller sold it 2 times lasting each for 2 or 3 days.
Click to expand...
Click to collapse
As far as i understand, wireless service providers most provide devices already unlocked (at least in Canada). So if my mediapad t5 is already unlocked, how do i root it without bricking it?
Bootloader seem to be freely unlockable NOW
Hi everyone.
I have a Huawei mediapad T5 AGS2-L09. It has 2 GB RAM and 16 GB internal memory.
I updated the software and a new option in the developers optons emerged:
"OEM Unlocking" - Allow the bootloader to be unlocked
When I turn it on a dialog box pops up with a warning:
"WARNING: Device protection features will not work on this device if this setting is enabled."
You have the option to CANCEL or ENABLE.
This is it, right?
Does anyone know how to root it from here and hopefully has a custom ROM?
The build number: AGS2-L09 8.0.0.222(OCEC432)
Android security patch: September 5, 2019
Once OEM-FRP unlock is enabled, you could then unlock your device with its bootloader's unlock code when in bootloader/fastboot mode.
But, as you don't have your code to unlock your bootloader, the only option is to remove back cover and use a 3rd party paying service called 'BLK' method on your device. (Look for huawei exploits group on telegram...)
So far, to properly root : you'll need bootloader unlocked, which needs bootloader's code typed in to unlock, which need OEM-FRP switch to be enabled.
My bootloader is unlocked. I used this method.
https://forum.xda-developers.com/mediapad-t5/how-to/how-to-unlock-bootloader-t4141705
I am tyring to install Lineage OS 17 using this method, but so far no luck, I cannot get TWRP for this device. It gives me an error when I try to install TWRP
https://gearallnews.com/how-to-install-lineage-os-17-gsi-for-huawei-mediapad-t5-android-10/
heathenlife said:
My bootloader is unlocked. I used this method.
https://forum.xda-developers.com/mediapad-t5/how-to/how-to-unlock-bootloader-t4141705
I am tyring to install Lineage OS 17 using this method, but so far no luck, I cannot get TWRP for this device. It gives me an error when I try to install TWRP
https://gearallnews.com/how-to-install-lineage-os-17-gsi-for-huawei-mediapad-t5-android-10/
Click to expand...
Click to collapse
Since you are testing the TWRP...
Did you try the one for the P20 Lite?
It's Kirin 659 like the T5.
https://forum.xda-developers.com/huawei-p20-lite/development/recovery-twrp-huawei-p20-lite-t4150389
https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692
(I have no idea, just an option to try)
Kgonla said:
Since you are testing the TWRP...
Did you try the one for the P20 Lite?
It's Kirin 659 like the T5.
https://forum.xda-developers.com/huawei-p20-lite/development/recovery-twrp-huawei-p20-lite-t4150389
https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692
(I have no idea, just an option to try)
Click to expand...
Click to collapse
Tried it.. didn't work.. it says:
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (13524 KB)...
OKAY [ 0.441s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.464s
So I guess we need a custom recovery. TWRP used to have a TWRP request page, but its not supported anymore. does anyone know how to make a request?
heathenlife said:
Tried it.. didn't work.. it says:
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (13524 KB)...
OKAY [ 0.441s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.464s
So I guess we need a custom recovery. TWRP used to have a TWRP request page, but its not supported anymore. does anyone know how to make a request?
Click to expand...
Click to collapse
It worked for me, you used wrong command.
https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692
fastboot flash recovery_ramdisk TWRP.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.948s]
writing 'recovery_ramdisk'...
OKAY [ 0.325s]
finished. total time: 1.289s
Kgonla said:
It worked for me, you used wrong command.
https://forum.xda-developers.com/hu...covery-twrp-3-2-1-0-p20-lite-edition-t3800692
fastboot flash recovery_ramdisk TWRP.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.948s]
writing 'recovery_ramdisk'...
OKAY [ 0.325s]
finished. total time: 1.289s
Click to expand...
Click to collapse
I successfully flashed @Pretoriano80 's twrp_mate9_0.1.img and magisk 20.4(20400).
I wonder know how to restore stuck rom. By the way I have downloaded full package from Firmware Finder for Huawei :https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
toyspeed said:
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
Click to expand...
Click to collapse
What's the message that appears in ADB when you flash it?
toyspeed said:
I keep trying to flash t.w.r.p via adb but it keeps failing. I try orange and Peter but they don't work and make me get stuck in bootloop. Official 3.3.1 recovery flashes but then when I boot to recovery it only shows the teamwin logo and I have no options to do anything, then on reboot when I trying booting into recovery again it boots into stock recovery like I never even flashed it.
Can someone tell me what I'm doing wrong or tell me correct recovery to flash with this rom? It should be straight forward process to flash t.w.r.p, but I am having trouble for some reason. Thank you.
Click to expand...
Click to collapse
Did u unlocked the bootloader?
Sent from my Redmi Note 7 Pro using XDA Labs
Naveenthemi said:
What's the message that appears in ADB when you flash it?
Click to expand...
Click to collapse
Just usual message such as:
PS C:\platform-tools> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.112s]
writing 'recovery'...
OKAY [ 0.355s]
finished. total time: 2.474s
I tried with Black Project also, same story. I don't understand this, I just want to root but I can't!
toyspeed said:
Just usual message such as:
PS C:\platform-tools> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.112s]
writing 'recovery'...
OKAY [ 0.355s]
finished. total time: 2.474s
I tried with Black Project also, same story. I don't understand this, I just want to root but I can't!
Click to expand...
Click to collapse
Ok someone else who's facing the same problem fixed this by formatting the data partition.
But idk why don't you try reinstalling MIUI(Flashboot it through MiFlash) and then try again?
Naveenthemi said:
Ok someone else who's facing the same problem fixed this by formatting the data partition.
But idk why don't you try reinstalling MIUI(Flashboot it through MiFlash) and then try again?
Click to expand...
Click to collapse
Ok, thanks for advice I'll try formatting data partition. That's exactly what I've been doing, flashing MIUI through MiFlash everything perfect. Then I run into problems after I try flashing recovery so I can root, very weird but I will keep trying.
toyspeed said:
Ok, thanks for advice I'll try formatting data partition. That's exactly what I've been doing, flashing MIUI through MiFlash everything perfect. Then I run into problems after I try flashing recovery so I can root, very weird but I will keep trying.
Click to expand...
Click to collapse
Did it work?
Naveenthemi said:
Did it work?
Click to expand...
Click to collapse
I actually decided to flash Superior OS instead, loving it so far!