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:
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
I recently upgraded my phone to EMUI 2.3 to EMUI 3.1 (Android lollipop 5.1), and installed CWM and rooted it. Two days ago I have downloaded cerebus app from Rom manager app and it installed by rebooting into recovery. Then a couple of minutes after rebooting the phone keep on crashing and shutting down randomly and when I tried to reboot it won't reboot but stuck for sometime at the Honor logo and since then I've tried every possible flashing and resetting I found here on XDA.
I still have access to fastboot and that is how I am able to flash ROM s and when I am trying to use the three button method it is stopping at 90 %. I couldn't even access it if my phone is not connected to my PC.
Now I've exhausted all the procedures in here and some other sites.
Somebody please suggest me something, help me.
Thank you.
Follow these steps to get it back to stock:
Download your phone's latest firmware and extract system.img, boot.img, recovery.img, cust.img from UPDATE.APP using Huawei Update Extractor tool.
Boot into bootloader mode by switching off the phone then pressing only the Vol DOWN button, and connecting it to PC simultaneously.
Flash recovery first, using this command.
Code:
fastboot flash recovery recovery.img
Flash all other extracted files similarly firing these commands.
Code:
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img
After doing this put that very UPDATE.APP from which you extracted the files in dload folder of your external SDCARD.
Switch off your phone, and press Vol UP + Vol DOWN + Power button simultaneously.
Your device will now get to the full stock firmware.
NOTE: If the manual flashing doesn't works or you get any errors, then first try only the force update method, i.e Putting the UPDATE.APP from which you extracted the files in dload folder of your external SDCARD and pressing Vol UP + Vol DOWN + Power button simultaneously after switching off your phone.
Thanks Brother.
I have tried to flash Recovery through fastboot and the following error is occurring
F:\Android\Honor root\H60-L04>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (13780 KB)...
OKAY [ 1.451s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.482s
Thanks again for helping me out,.
yessasikiran said:
I have tried to flash Recovery through fastboot and the following error is occurring
F:\Android\Honor root\H60-L04>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (13780 KB)...
OKAY [ 1.451s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.482s
Thanks again for helping me out,.
Click to expand...
Click to collapse
I have the same problem with a H60-L12.
I noticed, that I get that error when I try to flash a boot.img from a different EMUI version pack.
In my case, the phone had EMUI3.0 and I can write any of the EMUI3.0 boot.img's, but cannot write a boot.img from an EMUI 3.1 or EMUI4.0 update.app
yessasikiran said:
I have tried to flash Recovery through fastboot and the following error is occurring
F:\Android\Honor root\H60-L04>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (13780 KB)...
OKAY [ 1.451s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.482s
Thanks again for helping me out,.
Click to expand...
Click to collapse
Which recovery image are you using?
Sent from my PLK-L01 using Tapatalk
yessasikiran said:
I have tried to flash Recovery through fastboot and the following error is occurring
F:\Android\Honor root\H60-L04>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (13780 KB)...
OKAY [ 1.451s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.482s
Thanks again for helping me out,.
Click to expand...
Click to collapse
Try
download adb.zip
http://www.mediafire.com/download/o5ruw752ked884u/adb+H60.zip
extract adb.zip
download
TWRP_2.8.7.0_EN_EMUI_4.0_v4.img
https://drive.google.com/drive/folders/0By4NGNfKPDLBMW9jTy1fOHBGTm8?tid=0By4NGNfKPDLBQTZ2S0licGhjNmc
copy TWRP in adb folder
put the devices in fastboot mode
run cmd.exe as administrator and type this command
fastboot devices
fastboot flash recovery TWRP_2.8.7.0_EN_EMUI_4.0_v4.img
fastboot reboot
If does not work, try to reinstall HiSuite or install the lastet version
http://consumer.huawei.com/minisite/HiSuite_en/index.html
Nexus H791 using Tapatalk
Thnks you for replying so quickly.
I'm using "Honor 6_Firmware_H60-L04_Android 6.0_EMUI 4.0_C675B822_India_Flipkart India"
which is the latest stock firmware for Honor 6 H60-L04.
I have tried to force update with the thee button method and it worked (completed 100%)but unfortunately the phone is now in bootloop. This definitely made the phone a little better but once it got to the EMUI update screen its restarting again.
Thanks again man I though nobody would reply for this. its been so long since ive posted this.
Thank you for replying so quickly.
I'm using "Honor 6_Firmware_H60-L04_Android 6.0_EMUI 4.0_C675B822_India_Flipkart India"
which is the latest stock firmware for Honor 6 H60-L04.
I have tried to force update with the thee button method and it worked (completed 100%)but unfortunately the phone is now in bootloop. This definitely made the phone a little better but once it got to the EMUI update screen its restarting again.
Thanks again man I though nobody would reply for this. its been so long since ive posted this.
Thanks man, I'll get back to you once ive done this.
Nah man, Same thing again.
F:\Android\Honor root\TWRP>fastboot flash recovery TWRP_2.8.7.0_EN_EMUI_4.0_v4.i
mg
target reported max download size of 471859200 bytes
sending 'recovery' (14468 KB)...
OKAY [ 1.507s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.535s
Thank you for guiding me through.
yessasikiran said:
Thank you for replying so quickly.
I'm using "Honor 6_Firmware_H60-L04_Android 6.0_EMUI 4.0_C675B822_India_Flipkart India"
which is the latest stock firmware for Honor 6 H60-L04.
I have tried to force update with the thee button method and it worked (completed 100%)but unfortunately the phone is now in bootloop. This definitely made the phone a little better but once it got to the EMUI update screen its restarting again.
Thanks again man I though nobody would reply for this. its been so long since ive posted this.
Click to expand...
Click to collapse
You have to use that last Lollipop package which you were on before, try the three button method with that and report.
DigiGoon said:
You have to use that last Lollipop package which you were on before, try the three button method with that and report.
Click to expand...
Click to collapse
Hey,
Yeah man I'll do that now and will get bact to you.
Thanks man
DigiGoon said:
You have to use that last Lollipop package which you were on before, try the three button method with that and report.
Click to expand...
Click to collapse
Yeah man, I've tried to flash recovery of the last Lollipop Rom and still the same message FAILED (status read failed (Too many links)).
Is there any other way that we can try to unbrick the device?
Thank you man.
yessasikiran said:
Yeah man, I've tried to flash recovery of the last Lollipop Rom and still the same message FAILED (status read failed (Too many links)).
Is there any other way that we can try to unbrick the device?
Thank you man.
Click to expand...
Click to collapse
Have you used Honor Multitool? http://forum.xda-developers.com/honor-7/general/honor-7-multi-tool-t3281176
zinko_pt said:
Have you used Honor Multitool? http://forum.xda-developers.com/honor-7/general/honor-7-multi-tool-t3281176
Click to expand...
Click to collapse
Yes sir,
Same output and stopping after trying to flash recovery while using the in brick option.
Thank you.
yessasikiran said:
Yes sir,
Same output and stopping after trying to flash recovery while using the in brick option.
Thank you.
Click to expand...
Click to collapse
When you flashed manually, did you used the same IMG files from the last installed ROM?
You can´t extract and flash IMG files of a LP ROM in a last installed MM ROM and vice versa.
yessasikiran said:
I have tried to flash Recovery through fastboot and the following error is occurring
F:\Android\Honor root\H60-L04>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (13780 KB)...
OKAY [ 1.451s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.482s
Thanks again for helping me out,.
Click to expand...
Click to collapse
bro type fastboot devices and check how many available devices it shows...if it shows more than 1 device then stop the other device...if thr is only device then try stopping adb.exe and fastboot.exe(if thr)....then again type command "fastboot devices"
yessasikiran said:
Yes sir,
Same output and stopping after trying to flash recovery while using the in brick option.
Thank you.
Click to expand...
Click to collapse
Try using the latest version of the developer ROM
chetan_dua said:
bro type fastboot devices and check how many available devices it shows...if it shows more than 1 device then stop the other device...if thr is only device then try stopping adb.exe and fastboot.exe(if thr)....then again type command "fastboot devices"
Click to expand...
Click to collapse
Check in task manager to see if you have adb.exe running. Stop all and try again.
Still bricked or have u fixed it yet?
goldfinv said:
Try using the latest version of the developer ROM
Check in task manager to see if you have adb.exe running. Stop all and try again.
Click to expand...
Click to collapse
bro i was trying to help another person that was solution according to me for him
Sry if it looks like question...
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. I unlocked bootloader and flashed twrp via fastboot, but when I try to boot into it, the phone gets stuck at "your phone is booting now". The stock recovery no longer works. The phone's never been updated, still on Android 6.0 and EMUI 4.0. I tried several twrp versions with the same effect. What am I doing wrong? Can dm-verity be somehow interfering with twrp? Any ideas? Thanks in advance.
Code:
fastboot flash recovery twrp-3.0.2-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22020 KB)...
OKAY [ 0.701s]
writing 'recovery'...
OKAY [ 0.129s]
finished. total time: 0.830s
Months later I tried the same, also NXT-L29
Endless:
"Your device has been unlocked and can't be trusted....."
Your device is booting now...
Any solution please?
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