Note- This is tested on BKL-L09 C675 Indian variant and BKL-L09 C432 EU variant but will work on any variant of V10.
Hi Folks,
As I shared my experience on the issues I faced while moving back to stock from custom ROMs here , in this thread, I will share the detailed steps to go back to on stock avoiding any issues.
If you are on any custom ROM i.e. with Android/EMUI 8.1 TWRP backup will not work except BKL-L04. And only way that comes handy is fastboot (haven't tested the dload method myself yet as didnt had the SD card when I faced the issue but you can follow that, it will not break anything).
So before you start moving further to stock, please have these 3 files handy-
1- Stock recovery ramdisk
2- Stock boot ramdisk
3- system.img
Case 1- Custom ROM + Stock Boot + Stock Recovery (Applicable for new Open Kirin ROMs- RR and LOS which needs stock Ramdisk and if you are not using magisk)
On custom ROM, connect your phone with USB debugging enabled. (please make sure all the drivers are installed, it will already be as you may have the same which flashing the custom ROM)
Run the command to boot to fastboot
Code:
adb reboot bootloader
On fastboot screen, you will have bootloader state as Unlocked and FRP Unlocked.
Flash System image as below, Wait for process to finish, it may take 1-2 minutes for entire flash (93 seconds in my case)
Code:
PS C:\adb> fastboot flash system BKL-C432B130_system.img or fastboot flash system <system_filename>.img
target reported max download size of 471859200 bytes
sending sparse 'system' (456507 KB)...
OKAY [ 11.572s]
writing 'system'...
OKAY [ 2.669s]
sending sparse 'system' (457797 KB)...
OKAY [ 11.722s]
writing 'system'...
OKAY [ 2.630s]
sending sparse 'system' (457585 KB)...
OKAY [ 11.793s]
writing 'system'...
OKAY [ 3.417s]
sending sparse 'system' (460798 KB)...
OKAY [ 12.008s]
writing 'system'...
OKAY [ 2.611s]
sending sparse 'system' (413494 KB)...
OKAY [ 10.682s]
writing 'system'...
OKAY [ 2.631s]
sending sparse 'system' (453913 KB)...
OKAY [ 11.785s]
writing 'system'...
OKAY [ 2.973s]
sending sparse 'system' (227740 KB)...
OKAY [ 5.856s]
writing 'system'...
OKAY [ 1.260s]
finished. total time: 93.634s
Once the system image is flashed successfully, run the command to boot but immediately remove USB and press volume up key to boot to recoevery rather than system (even if you skip, it may not boot to system)
Code:
fastboot reboot
Remove USB and press volume up key to boot to recovery.
Perform factory reset and wipe data as well.
Once completed, reboot to system.
Case 2- Custom ROM + Stock Recovery + Magisk (Root) ( applicable for New open Kirin ROMs- RR and LOS which needs stock ramdisk and if you are using magisk)
I forgot that I had magisk and had to gone through more issues as post boot, my IMEI was missing and no SIM service but if you have magisk installed, please be more careful and flash stock boot (attached for BKL-L09 EU version)
Run the command to boot to fastboot
Code:
adb reboot bootloader
On fastboot screen, you will have bootloader state as Unlocked and FRP Unlocked.
Flash the stock boot ramdisk.img as
Code:
fastboot flash ramdisk BKL-L09_ramdisk.img
Or fastboot flash ramdisk <ramdisk_File_Name>
Flash System image as below, Wait for process to finish, it may take 1-2 minutes for entire flash (93 seconds in my case)
Code:
PS C:\adb> fastboot flash system BKL-C432B130_system.img or fastboot flash system <system_filename>.img
target reported max download size of 471859200 bytes
sending sparse 'system' (456507 KB)...
OKAY [ 11.572s]
writing 'system'...
OKAY [ 2.669s]
sending sparse 'system' (457797 KB)...
OKAY [ 11.722s]
writing 'system'...
OKAY [ 2.630s]
sending sparse 'system' (457585 KB)...
OKAY [ 11.793s]
writing 'system'...
OKAY [ 3.417s]
sending sparse 'system' (460798 KB)...
OKAY [ 12.008s]
writing 'system'...
OKAY [ 2.611s]
sending sparse 'system' (413494 KB)...
OKAY [ 10.682s]
writing 'system'...
OKAY [ 2.631s]
sending sparse 'system' (453913 KB)...
OKAY [ 11.785s]
writing 'system'...
OKAY [ 2.973s]
sending sparse 'system' (227740 KB)...
OKAY [ 5.856s]
writing 'system'...
OKAY [ 1.260s]
finished. total time: 93.634s
Once the system image is flashed successfully, run the command to boot but immediately remove USB and press volume up key to boot to recoevery rather than system (even if you skip, it may not boot to system)
Code:
fastboot reboot
Remove USB and press volume up key to boot to recovery.
Perform factory reset and wipe data as well.
Once completed, reboot to system.
Case 3- Custom ROM + Custom Recovery + (Stock Ramdisk/ modified Ramdisk with Magisk) (Applicable for any custom ROM installed with TWRP and on stock boot or Magisk)
I forgot that I had magisk and had to gone through more issues as post boot, my IMEI was missing and no SIM service but if you have magisk installed, please be more careful and flash stock boot (attached for BKL-L09 EU version)
Run the command to boot to fastboot
Code:
adb reboot bootloader
On fastboot screen, you will have bootloader state as Unlocked and FRP Unlocked.
Flash the stock Recovery Ramdisk as
Code:
fastboot flash recovery_ramdisk recovery_ramdisk_bak.img
Or fastboot flash recovery_ramdisk <Recovery_File_Name>.img
If you have stock Boot Ramdisk, proceed to flashing system image and skip flashing the boot ramdisk.
If you have installed magisk, flash the stock boot ramdisk.img as
Code:
fastboot flash ramdisk BKL-L09_ramdisk.img
Or fastboot flash ramdisk <ramdisk_File_Name>
Flash System image as below, Wait for process to finish, it may take 1-2 minutes for entire flash (93 seconds in my case)
Code:
PS C:\adb> fastboot flash system BKL-C432B130_system.img or fastboot flash system <system_filename>.img
target reported max download size of 471859200 bytes
sending sparse 'system' (456507 KB)...
OKAY [ 11.572s]
writing 'system'...
OKAY [ 2.669s]
sending sparse 'system' (457797 KB)...
OKAY [ 11.722s]
writing 'system'...
OKAY [ 2.630s]
sending sparse 'system' (457585 KB)...
OKAY [ 11.793s]
writing 'system'...
OKAY [ 3.417s]
sending sparse 'system' (460798 KB)...
OKAY [ 12.008s]
writing 'system'...
OKAY [ 2.611s]
sending sparse 'system' (413494 KB)...
OKAY [ 10.682s]
writing 'system'...
OKAY [ 2.631s]
sending sparse 'system' (453913 KB)...
OKAY [ 11.785s]
writing 'system'...
OKAY [ 2.973s]
sending sparse 'system' (227740 KB)...
OKAY [ 5.856s]
writing 'system'...
OKAY [ 1.260s]
finished. total time: 93.634s
Once the system image is flashed successfully, run the command to boot but immediately remove USB and press volume up key to boot to recoevery rather than system (even if you skip, it may not boot to system)
Code:
fastboot reboot
Remove USB and press volume up key to boot to recovery.
Perform factory reset and wipe data as well.
Once completed, reboot to system.
Once booted on any of the case, you will be on full stock with unlocked bootloader. (you need to either dload to lock the bootlaoder or run the command - fastboot oem urelock <16 digit bootlaoder code> to relock the bootlaoder).
Working and tested myself and confirmed by one more user(Sandeep Dash). So, if you follow the steps correctly, you should not face any issue but in case you get stuck anywhere or not clear with steps and I will try to help as much as I can.
Attached files for BKL-L09 EU version. I will add other files as an when I get it.
Stock Ramdisk for BKL-L09 EU version - Thanks to @topjohnwu for sharing here
Stock Recovery for BKL-L04 EU version -I extracted this but thanks to @shihabsoft for sharing the step which helped me doing this.
Stock system image for BKL-L09 EU Version - Thanks to @surdu_petru for sharing here
Will these method work on bkl l09 model (indian variant)?
Really nice guide! Just one thing: Aren't you missing a
Code:
fastboot flash recovery_ramdisk <recovery_ramdisk_file>
step somewhere?
mondalakash said:
Will these method work on bkl l09 model (indian variant)?
Click to expand...
Click to collapse
Yes it will, 100%. The case 1 confirmation from Sandeep is for Indian variant only.
Smaehtin said:
Really nice guide! Just one thing: Aren't you missing a step somewhere?
Click to expand...
Click to collapse
Thanks. Nope buddy, as you already have stock recovery (for new Open Kirin ROMs) and only boot ramdisk was modified (for Magisk)
But yes, if you flashed twrp then you need it. Thanks for highlighting it, i will fix this.
shashank1320 said:
Yes it will, 100%. The case 1 confirmation from Sandeep is for Indian variant only.
Click to expand...
Click to collapse
Thanks for the confirmation...one question should i use the official twrp or the unofficial one for installing custom roms , decrypting internal storage and so on...
shashank1320 said:
Thanks. Nope buddy, as you already have stock recovery and only boot ramdisk was modified.
But yes, if you flashed twrp then you need it. Thanks for highlighting it, i will fix this.
Click to expand...
Click to collapse
Oh, I see. I was just a little confused about this part then:
shashank1320 said:
So before you start moving further to stock, please have these 3 files handy-
1- Stock recovery ramdisk
2- Stock boot ramdisk
3- system.img
Click to expand...
Click to collapse
mondalakash said:
Thanks for the confirmation...one question should i use the official twrp or the unofficial one for installing custom roms , decrypting internal storage and so on...
Click to expand...
Click to collapse
FOr me it was unofficial as I was using OpenKirin ROM as per requirement it should be stock recovery only.
for other ROMs or backup, you can try the unofficial one as official doesnt work on Android 8.1 and it will show random content or character in TWRP so you can not restore or say access the stuffs on your internal memory. I used the unofficial one given here
shashank1320 said:
FOr me it was unofficial as I was using OpenKirin ROM as per requirement it should be stock recovery only.
for other ROMs or backup, you can try the unofficial one as official doesnt work on Android 8.1 and it will show random content or character in TWRP so you can not restore or say access the stuffs on your internal memory. I used the unofficial one given here
Click to expand...
Click to collapse
Did you try dirty unicorn RC latest build?
Smaehtin said:
Oh, I see. I was just a little confused about this part then:
Click to expand...
Click to collapse
Fixed in OP. Added one more case for custom recovery users.
Thanks for valuable input buddy.
mondalakash said:
Did you try dirty unicorn RC latest build?
Click to expand...
Click to collapse
Nope buddy. Did you? Any feedback?
shashank1320 said:
Nope buddy. Did you? Any feedback?
Click to expand...
Click to collapse
using this method relocks bootloader?
mondalakash said:
using this method relocks bootloader?
Click to expand...
Click to collapse
No. It wont
Only dload or manual relock does
shashank1320 said:
No. It wont
Only dload or manual relock does
Click to expand...
Click to collapse
Thanks buddy
shashank1320 said:
No. It wont
Only dload or manual relock does
Click to expand...
Click to collapse
Same bootloader unlock can be used multiple times for unlocking? Any idea
mondalakash said:
Same bootloader unlock can be used multiple times for unlocking? Any idea
Click to expand...
Click to collapse
Yes. Code will remain the same throughout the phone lifecycle. It is based on phone serial number, product if amd IMEI which remains the same and unique for every phone
shashank1320 said:
Yes. Code will remain the same throughout the phone lifecycle. It is based on phone serial number, product if amd IMEI which remains the same and unique for every phone
Click to expand...
Click to collapse
Thanks buddy for these quick reply..I guess these recovery issues rom bootlopping issues will be fixed if huwaie gave l09 variants 8.1 update
---------- Post added at 07:07 PM ---------- Previous post was at 06:53 PM ----------
shashank1320 said:
Yes. Code will remain the same throughout the phone lifecycle. It is based on phone serial number, product if amd IMEI which remains the same and unique for every phone
Click to expand...
Click to collapse
Bro if flash system IMG of EU variant will this mean that I will on the EU update cycle?..I mean the dev pulled the system IMG from his V10 EU variant.…
mondalakash said:
Thanks buddy for these quick reply..I guess these recovery issues rom bootlopping issues will be fixed if huwaie gave l09 variants 8.1 update
---------- Post added at 07:07 PM ---------- Previous post was at 06:53 PM ----------
Bro if flash system IMG of EU variant will this mean that I will on the EU update cycle?..I mean the dev pulled the system IMG from his V10 EU variant.…
Click to expand...
Click to collapse
It will not allow to flash or wont boot.
You may need to flash the oeminfo file first and then system img. Had this been this easy, i would have rebranded to Indian version. See one of my debranding guide in signature
shashank1320 said:
It will not allow to flash or wont boot.
You may need to flash the oeminfo file first and then system img. Had this been this easy, i would have rebranded to Indian version. See one of my debranding guide in signature
Click to expand...
Click to collapse
Or I can pull my system ,boot,ramdisk by ADB since I haven't messed with the device apart from unlocking it
---------- Post added at 08:19 PM ---------- Previous post was at 08:11 PM ----------
mondalakash said:
Same bootloader unlock can be used multiple times for unlocking? Any idea
Click to expand...
Click to collapse
Using erecovery would be easier if u have fast internet and I heard it doesn't relock the bootloader
I mean the relock doesn't matter according to u as we can just use the code several times ...then I guess dload is easier only need a SD card...I mean it doesn't even matter which one of the scenarios we are in as mentioned by u in the OP.
mondalakash said:
Or I can pull my system ,boot,ramdisk by ADB since I haven't messed with the device apart from unlocking it
---------- Post added at 08:19 PM ---------- Previous post was at 08:11 PM ----------
Using erecovery would be easier if u have fast internet and I heard it doesn't relock the bootloader
I mean the relock doesn't according to u as we can just use the code several times ...then I guess dload is easier only need a SD card...I mean it doesn't even matter which one of the scenarios we are in as mentioned by u in the OP.
Click to expand...
Click to collapse
Erecovery download is difficult and give error many times.
Dload actually lock the bootloader and you will be on full stock.
In my case, i had to relock the bootloader as it was in bootloop and i knew relocking will give me erecovery to download.
Related
From my prevous thread:
Hi all. i have rooted my Asus Transformer Pad TF132CX and using TitaniumBackup Pro uinstalled some system apps, and now it freezes on asus logo. Charging working, Using VOL+ and Power Button i can acess to DROIDBOOT, here i have fastboot acess, and
i can reboot to recovery. I trayed ADB Sideload in Recovery, i am used stock firmware from Asus page, but it says: Signature Verification failed. Can anyone create backup from system in *.img format? I want to try use fastboot to flash system. Or custom recovery image (*.img) to flash this firmware.
Or something like firmware for these models, or CPUs in *.img format , and then patch with ota update.
I think TF103C and TF103CX are same.
Or any other way how to unbrick? i have lastest Firmware in system, but Bricked
Click to expand...
Click to collapse
Now, my friend buyed second TF103CX, i have rooted it and maked backup of system partition, and then unrooted.
But it have 1.75 GB, and i cannot flash that via fastboot.
C:\Users\Pavel Horniak\Desktop\Root Kit>fastboot flash system system.img
target reported max download size of 568440149 bytes
Invalid sparse file format at header magi
sending sparse 'system' (8 KB)...
OKAY [ 0.956s]
writing 'system'...
OKAY [ 0.516s]
finished. total time: 1.472s
8KB? it have 1.75GB
can anyone help me?
system.img is too large for device RAM, so i used this tool: http://forum.xda-developers.com/showthread.php?t=2749797
but i dont know how to flash theese files.
//Trayed to flash recovery recovery_philz_t00f.img, and dont working.
Now i can acess only to fastboot.
After fumbling with install twrp in order to change over to CM13 from stock, I somehow managed to install the original recovery wrong as well as completely boning the OS. Because of this, on boot, all that shows is the honor screen continuously. Of course the obvious answer to this is to reinstall twrp and restore one of my recovery files. Unfortunately trying to flash twrp through fastboot results in an "FAILED (data transfer failure (Unknown error))". Any suggestions? I can't access the phones internal storage nor the SD card either when I plug it into my PC.
Only one solution, flash a stock firmware using a PC.
PalakMi said:
Only one solution, flash a stock firmware using a PC.
Click to expand...
Click to collapse
How would I go about doing this? I would really love to get my honor working again. Would it just be using fastboot to flash the firmware?
I'd be worried about that error you're getting. It's strange.
Have you considered trying to flash stock recovery? You can extract the recovery image file from the official website update download. Or use the repository.
Or have you tried flashing a different version of TWRP recovery? Here's the official website.
Dueter1um said:
How would I go about doing this? I would really love to get my honor working again. Would it just be using fastboot to flash the firmware?
Click to expand...
Click to collapse
I don't think only fastboot is enough, but take a look at the link provided by JT-on
JT-on said:
I'd be worried about that error you're getting. It's strange.
Have you considered trying to flash stock recovery? You can extract the recovery image file from the official website update download. Or use the repository.
Or have you tried flashing a different version of TWRP recovery? Here's the official website.
Click to expand...
Click to collapse
Luckily, after trying to reflash the twrp with a different version like you suggested, there was no error message and it was completed successfully! Currently restoring as I type this. Don't know how to upload an image so text should do
C:\Users\zakpw\Desktop\Honor 5x rooting>fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.423s]
writing 'recovery'...
OKAY [ 0.694s]
finished. total time: 2.121s
Dueter1um said:
Luckily, after trying to reflash the twrp with a different version like you suggested, there was no error message and it was completed successfully! Currently restoring as I type this. Don't know how to upload an image so text should do
C:\Users\zakpw\Desktop\Honor 5x rooting>fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.423s]
writing 'recovery'...
OKAY [ 0.694s]
finished. total time: 2.121s
Click to expand...
Click to collapse
Happy for you, next time be careful
I got this same error, had to use different USB cable and different USB port.
Hi all,
I have an LG G5 H850. I'm trying to install TWRP using ADB. I've had it previously and it worked fine. I'm pretty sure the bootloader is unlocked. Anyway, when I do "fastboot flash recovery twrp-3.1.1.1-0-h850.img" I get the following output:
target reported max download size of 536870912 bytes
sending 'recovery' (19076 KB)...
OKAY [ 0.431s]
writing 'recovery'...
OKAY [ 0.345s]
finished. total time: 0.781s
To me, that looks as though thats worked fine. Now when I try fastboot boot twrp-3.1.1.1-0-h850.img I get the following:
downloading 'boot.img'...
OKAY [ 0.432s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.456s
Has anyone got any ideas on this?
Same here
I am having the same problem, please help
Had this issue a while back. I resorted to doing complete flash with LGUP to the latest version and then it worked. I had been messing around with various ROMS on different android versions.
lywyn said:
Had this issue a while back. I resorted to doing complete flash with LGUP to the latest version and then it worked. I had been messing around with various ROMS on different android versions.
Click to expand...
Click to collapse
Don't happen to know where I could get a rom that it would work with do you?
Managed to solve this. Flashed the TWRP image using fastboot flash recovery <img> via adb. Then I unplugged from USB, and got into recovery mode by doing power + volume down buttons and quickly release and repress ont he LG logo. Answered yes to both questions and got into TWRP.
Barsbeh said:
Managed to solve this. Flashed the TWRP image using fastboot flash recovery <img> via adb. Then I unplugged from USB, and got into recovery mode by doing power + volume down buttons and quickly release and repress ont he LG logo. Answered yes to both questions and got into TWRP.
Click to expand...
Click to collapse
That is the required way of doing it. You have to boot into recovery after flashing the recovery or it gets reset.
Hi,
Having a similar problem since trying to update my ROM ... and the Magisk install failed. Now I can only get to fastboot, can't get to recovery. And, tried this,
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-0-h830.img
target reported max download size of 536870912 bytes
sending 'recovery' (18644 KB)...
OKAY [ 0.439s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.461s
Help!?! ... and thanks!
to the point.. I tried flashing OREO coming from B120 firmware following this guide https://forum.xda-developers.com/honor-9/how-to/stf-l09c432-how-to-install-oreo-h9-t3707729 ... I didnt manage to rename the folder in Part2.4 of the guide because despite supersu asking if i wanted to grant root it just didnt work....the bootloader and frp are unlocked.. when i try to reflash twrp this is happening.
F:\handy\h9>fastboot flash recovery twrp-3.1.1-1-stf.img
target reported max download size of 471859200 bytes
sending 'recovery' (32028 KB)...
OKAY [ 0.681s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.693s
theres not many googlehits and none of them helped or at least I couldnt find anything useful.
I tried to flash the stock SERVICE_FULL_REPAIR_STF-L09_C432B130_Belgium_Germany_France_Netherlands_Portugal_Switzerland_Spain_Italy_Austria_Poland_Denmark_Finland_Czech_Lithuania_Romania_Serbia_Slovenia_Hungary_androidhost.ru.rar
I put the dload folder in the root of the external_sd and boot up the phone with volup+down but I'm getting an error.
I also tried unbricking with the huawei multi tool but I'm getting errors with boot und recovery partitions.
7BKDU17809009681 fastboot
target reported max download size of 471859200 bytes
sending 'boot' (16366 KB)...
OKAY [ 0.349s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.453s
target reported max download size of 471859200 bytes
sending 'cust' (148087 KB)...
OKAY [ 3.159s]
writing 'cust'...
OKAY [ 1.468s]
finished. total time: 4.628s
target reported max download size of 471859200 bytes
sending 'recovery' (41016 KB)...
OKAY [ 0.871s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 1.110s
target reported max download size of 471859200 bytes
I only want a working rom with root so i can use titanium backup. Any help is appreciated. After spending 12 hours today Im out of googlesearches and forumbrowsing ideas. Worst case check back in a week or so and I'll upload a youtube vid in which I'll destroy my practically brandnew phone with a hammer because I'm starting to lose my nerves. I really didnt expect it to be such a problem to install a new firmware and rooting my new phone. What options do I have?
regards
andru
In Oreo, recovery and boot partitions were renamed.
So, to flash recovery (TWRP in this case), you use
fastboot flash recovery_ramdisk twrp.img
Make sure you use TWRP for Oreo
to flash stock "boot", extract RAMDISK from stock oreo honor 9 firmware, and flash using
fastboot flash ramdisk RAMDISK.img
new partitions are the following:
boot = split into RAMDISK and KERNEL
recovery = split into RECOVERY_RAMDISK, RECOVERY_KERNEL, RECOVERY_VENDOR, RECOVERY_VBMETA.
eRecovery = Same as above but named erecovery
DLOAD should work...
if there are ROLLBACK firmware for Honor 9 you could try this to go back to Nougat: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
I'm not sure how different Honor 9 and Mate 9 recoveries are, but you could just flash back stock recovery if it doesn't work.
sorry for posting this in the wrong forum section. If a mod could move this would be appreciated.
ante0 said:
In Oreo, recovery and boot partitions were renamed.
So, to flash recovery (TWRP in this case), you use
fastboot flash recovery_ramdisk twrp.img
Make sure you use TWRP for Oreo
to flash stock "boot", extract RAMDISK from stock oreo honor 9 firmware, and flash using
fastboot flash ramdisk RAMDISK.img
new partitions are the following:
boot = split into RAMDISK and KERNEL
recovery = split into RECOVERY_RAMDISK, RECOVERY_KERNEL, RECOVERY_VENDOR, RECOVERY_VBMETA.
eRecovery = Same as above but named erecovery
DLOAD should work...
if there are ROLLBACK firmware for Honor 9 you could try this to go back to Nougat: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
I'm not sure how different Honor 9 and Mate 9 recoveries are, but you could just flash back stock recovery if it doesn't work.
Click to expand...
Click to collapse
thank you! I will try
andruman33 said:
thank you! I will try
Click to expand...
Click to collapse
nervermind i managed to murder the phone for good now with the dc phoenix software. bye bye honor 9
andruman33 said:
nervermind i managed to murder the phone for good now with the dc phoenix software. bye bye honor 9
Click to expand...
Click to collapse
Too bad
hey, don't worry, you were just stupid trying to flash to the wrong partitions (nougat partition names), recovery should be recovery_ramdisk and kernel is split into 2 partitions on oreo: kernel and ramdisk.
You better read everything carefully next time, its posted all around the forums here.
Regards
too bad
but you can try to update with latest version [B330]
https://romprovider.com/2017/12/b330-oreo-update-honor-9-tf-al00stf-tl10/
Before:
I just unlocked the bootloader and installed a custom ROM (LineageOS 15.1: https://forum.xda-developers.com/huawei-y6/development/lineageos-15-1-huawei-y6-2018-t3832278) on my Huawei but it won't let me flash the TWRP from adb. I tried before flashing the custom ROM and also after but no progress. I tried with 'fastboot flash recovery recovery.img' as well as 'fastboot flash boot recovery.img' because I knew some smartphones include the recovery in the boot.img but I am always getting the same error:
Code:
fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (16544 KB)...
OKAY [ 0.522s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.553s
I am not an expert but I understood that 'recovery' partition doesn't exist. I found some possible solutions online such as writing 'fastboot flash RECOVERY recovery.img' or 'fastboot flash erecovery recovery.img' (because Huawei calls the stock one 'erecovery') but they both gave me another error:
Code:
fastboot flash RECOVERY recovery.img
target reported max download size of 535822336 bytes
sending 'RECOVERY' (16544 KB)...
OKAY [ 0.522s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.528s
UPDATE: I found, maybe, the correct name of the recovery partition and it seems to work:
Code:
fastboot flash recovery_ramdisk twrp.img
< waiting for device >
target reported max download size of 535822336 bytes
sending 'recovery_ramdisk' (14026 KB)...
OKAY [ 0.443s]
writing 'recovery_ramdisk'...
OKAY [ 0.323s]
finished. total time: 0.767s
BUT it actually doesn't work properly because when I boot into recovery it boots the stock one. I tried other solutions found on the net like instantly unplug the phone after the flash and reboot it into recovery immediately but again it boots into stock one...
OTHER UPDATE: I managed to find and flash a TWRP that can boot up but it shows the internal storage 0MB not allowing me to install any .zip file. Because of that, I cannot install SuperSU to get root access.
I tried installing TWRP also with stock ROM but still showing 0MB because the phone is encrypted. To disable encryption I need to install the bluspark TWRP (As I found online), the problem is that bluspark won't boot and gets immediately overwritten by the stock ROM as it happened with the one I mentioned in the first update of the post.
Now I will try buying a microSD card and see if it shows right so that I can still flash .zip from the microSD card.
Now:
LATEST UPDATE: The SD card is working properly and I see it as around 60 GB instead of 64 but that's not the problem. I can see the .zip files I'd want to flash but when I try to do it it says me that it failed to mount every single partition and after some research I discovered that my Huawei has all the data encrypted. After other research I found that there are some TWRPs like blu_spark that could decrypt the data but every version I tried doesn't work and gets immediately overwritten by the stock recovery.
Does anyone know other methods to decrypt all the data on Huawei? Otherwise it's impossible to flash any .zip. Actually it flashes it but it fails to update the partitions state so the system doesn't recognize the changes.
Rooting Huawei is so difficult.. I will buy an OP5t as soon as I have the money XD.
Y6 2018 twrp
Any progress? I'm also looking for a version of TWRP that works with the Y6 2018.