Related
Hello,
I'm trying to install 4.4.2 Rom http://forum.xda-developers.com/showthread.php?t=2607249 by arrrghhh.
when I try to install twrp I get the following error:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
y openrecovery-twrp-2.6.3.4-hammerhead.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (13272 KB)...
OKAY [ 0.997s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
FAILED (remote failure)
finished. total time: 1.238s
Also the green android with the open belly appears and I stopped it by holding powerbutton, and now it says Fastboot reason: Flash failure in the screen.
I tried installing goomanager and install twrp from there, but it didn't seem to work.
Please advice how to get the twrp to install correctly so I can flash the rom.
Thanks,
Stani
soulmethod said:
Hello,
I'm trying to install 4.4.2 Rom http://forum.xda-developers.com/showthread.php?t=2607249 by arrrghhh.
when I try to install twrp I get the following error:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
y openrecovery-twrp-2.6.3.4-hammerhead.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (13272 KB)...
OKAY [ 0.997s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
FAILED (remote failure)
finished. total time: 1.238s
Also the green android with the open belly appears and I stopped it by holding powerbutton, and now it says Fastboot reason: Flash failure in the screen.
I tried installing goomanager and install twrp from there, but it didn't seem to work.
Please advice how to get the twrp to install correctly so I can flash the rom.
Thanks,
Stani
Click to expand...
Click to collapse
Why are you trying to install TWRP for the hammerhead (Nexus5)[email protected]??
That could cause SERIOUS damage. Please install a recovery for your device.
If you want to use GooManager, you need to be rooted. Regardless, you need to have your bootloader unlocked to install any custom recovery.
didn't find one
Wow,
I must have miss downloaded it, browsing threads...
Can you give a link to one that is for photon Q ?
The bootloader is unlocked, but I couldn't install superSU yet.
To be honest I'm kinda lost reading all those different threads.
At the same time I want to try your 4.4.2 )
Thanks,
Stani
http://forum.xda-developers.com/showthread.php?t=1887070
Helps to stick to the Photon Q section
Twrp for Photon Q
Ok, found one that is for photon Q,
here is link : http://goo.im/devs/OpenRecovery/asanti
Thread: http://forum.xda-developers.com/showthread.php?t=1887070
Trying again and will post results
it worked!
Superb,
managed to install and GUMMY 4.4.2 is loading )) and it booted, loool ))
Thanks arrrghhh for your fast response!!!
I will play around with it and will donate once I get my salary )
Keep up the good work and lots of laughs and harmony,
Thanks,
Stani
i have also try ..... .
soulmethod said:
Ok, found one that is for photon Q,
here is link : http://goo.im/devs/OpenRecovery/asanti
Thread: http://forum.xda-developers.com/showthread.php?t=1887070
Trying again and will post results
Click to expand...
Click to collapse
i have also try but not bootable in recovery.....
please suggest mee.....
avisingh736 said:
i have also try but not bootable in recovery.....
please suggest mee.....
Click to expand...
Click to collapse
What's your issue?
The thread you are jacking, the OP originally tried flashing a recovery for the hammerhead (n5).
Is that your problem to? If so, just use a recovery posted in the Photon Q section. It'll work much better.
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
Hey there Guys, first of all thanks for takeing the time and reading through this post.
I have used the search function on this board and on google to an unhealthy extend the last 5 Days because no matter what i try there is always something in the way of every method i have tried to the extend that i almost accept the fact that my phone might be Hardbricked in terms of internal memory.
So lets get on with some data.
Im using the Honor 8 FRD-L09 with currently no OS whatsoever.
The Device is:
-Rooted
-Fully Unlocked (Bootloader, OEM, FRP, Debugging Mode (Enabled before Brick)
I Bricked my Honor 8 when i tried to use the Backup function of TWRP to later change the OS from EMUI 5 to AICP
The first try to change to AICP failed, saying for whatever reason that i cannot install this Update on a EVA-L09 Device, (which is strange since the Phone clearly says FRD-L09 on the back aswell as responding good to all past upgrades that i did , which were all for FRD-L09), so i chose to rollback to the Backup, however the Backup was corrupted in the process somehow and so the phone is currently without any OS as i couldnt reinstall the original Backup.
Ok so now for stuff i have tried and the errors i recieve while doing that.
ERecovery
After ERecovery is connected to any WIFI it spits out the error that no Packages can be found.
Fastboot Flashing
I have tried to install the Stock EMUI 4 Boot.img and then use the Huawei Update Extractor to extract the files from the UPPDATE.APP after i made sure that i have the correct firmware downloaded (The oldest possible, FRD-L09C432B101).
I can flash the boot and recovery images just fine, but the System and Cust images throw me the following errors:
System.img Error
fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (427769 KB)...
OKAY [ 9.631s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 9.666s
Cust.img Error
flash cust CUST.img
target reported max download size of 471859200 bytes
sending 'cust' (416830 KB)...
OKAY [ 8.920s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 11.151s
I have furthermore tested all other FRD-L09 Firmwares up to 130 and even the new B320 for EMUI 5 (for which i installed the EMUI 5 Boot.img) aswell as trying to use:
ZIP Flashing
I have tried to use the following command:
fastboot flash zip UPDATE.APP , which spits out the following error:
fastboot flash zip UPDATE.APP
target reported max download size of 471859200 bytes
sending 'zip' (81444 KB)...
OKAY [ 1.746s]
writing 'zip'...
FAILED (remote: Command not allowed)
finished. total time: 1.761s
I have then tried to lock and unlock the OEM to fix the Command not allowed issue which however did not work out.
MicroSD Updating
I have tried the method of using a MicroSD to install the above Update.APP's in a dload folder in the Root of the card with the stock recovery, however no matter what firmware or what Boot.img or what Stock Recovery.img i use, i always get the Software Incompatibility error.
TWRP Direct Recovery and ADB Sideloading
I have tried the method of directly installing or Sideloading the files through ADB with the help of TWRP, but i get the errors that either /data or /system or /internalstorage cannot be mounted.
I have tried the solution suggested on a few promising youtube videos to simply try a combination of formating to a different type and then back aswell as repairing and then trying again, which worked for /system and /internalstorage, but /data is still not able to mount.
So as you can see i have pretty much tried every trick in the book to get my Phone unbricked, however non of those methods work and im getting desperate.
If any of you have more ideas as to what i could try, please post them here.
Go onto MoDaco honor 8
Google it.
There is a guy called Paul O'Brien on there he will help you sort it out
@ newsupast
have you found a solution?
I have same problem with my FRD-AL10.
Also have checked MoDaCo, but help is very rare.
I've written to Huawei-Support to ask for a rollback-package, but they told me to ask my local support.
The have not replied my question.
Well guys, I think I did it. I think I really did brick my Honor 8.
Phone details: New Honor 8, Model is FRD-AL10.
It came with the Chinese ROM, locked. What I did was to unlock it with DC unlocker, flash TWRP as custom recovery and root it.
Later, I had some problems with installing Open Gapps so I decided that I will flash a custom ROM unto it. What I chose was this RROS. I followed all of the instructions, made sure my EMUI was up to date, deleted all of my fingerprints (although I did not disable the PIN lock). I performed a factory reset using TWRP, flashed RROS and started facing errors.
Trying to power up the phone I found out it was going into bootloop, not able to start up. Only recovery available was not TWRP, but the default Huawei eRecovery, that lets you restore the phone using the Wi-Fi to download the needed files. Panicking for my new phone, I tried to restore my phone this way, only when it completed the download it failed restoring.
I have tried to unbrick my phone using the Honor 8 Multi-Tool: flashing BOOT.img, CUST.img, Recovery, USERDATA.img and SYSTEM.img. The firmware I downloaded and extracted UPDATE.app from is this: FRD-AL10_C00B135_Firmware_China_Nonspecific_Android 6.0_EMUI 4.1_05013LBP.zip.
The Multi-Tool's log is this:
Code:
12:51:55: All images are found, everything is ready for the unbricking process.
12:52:01: Unbricking started. Your computer may freezes during the process.
12:52:01: flash boot "C:\Users\Mark\Desktop\Honor 8\Unbrick\boot.img"
12:52:03: The Boot image is flashing successfully
12:52:03: flash system "C:\Users\Mark\Desktop\Honor 8\Unbrick\system.img"
12:55:09: target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (413881 KB)...
OKAY [ 30.117s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 30.164s
12:55:09: Error#1
12:55:09: flash cust "C:\Users\Mark\Desktop\Honor 8\Unbrick\cust.img"
12:55:28: Error! You are trying to flash the wrong image!
12:55:28: flash recovery "C:\Users\Mark\Desktop\Honor 8\Unbrick\recovery.img"
12:55:31: The Recovery image is flashing successfully
12:55:31: flash userdata "C:\Users\Mark\Desktop\Honor 8\Unbrick\userdata.img"
12:55:38: target reported max download size of 471859200 bytes
sending 'userdata' (143361 KB)...
OKAY [ 4.183s]
writing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.275s]
finished. total time: 5.458s
12:55:38: Error#1
12:55:38: Completed
12:55:38: Something went wrong (((
As you see, SYSTEM.img cannot be written for some reason, and CUST.img is for some reason the wrong file.
I also tried to flash UPDATE.app using a microSD card and the Volume up+Volume down+Power combination, but it fails after 5%, Saying:
Code:
Software install failed!
Incompatibility with current version.
Please download the correct update package.
So either my phone is completely dead, or I am missing something here.
Can anyone help me restore my phone to normal function?
you need to find the rollback package, you had android 7 but you're trying to flash android 6
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