Good evening XDA Developers Forum,
I am trying to figure out how to install LineageOS 14.1 on a Huawei Honor 5X without getting into too much hassle. (If you are not interested in my chit-chat, I recommend reading only the bold text.)
Why do I need help? I tried to install LineageOS 14.1 right after buying a fresh new Honor 5X following the instructions at the LineageOS-Wiki*, but things didn't went as expected. After 5 days of macgyvering the (suspectedly) bricked phone I managed to get it running again, but not yet with LinageOS. So I wanted to share my experiences to help others having similar problems and I want to avoid too much stress with the next steps. (* I wanted to link to the Wiki, but due to being a new user, I am not allowed to. You may follow the kiwi-Install-Instructions in the LineageOS-Wiki.)
Kind of disclaimer: I've modified my mobile devices a few times in the past years. I rooted and installed CyanogenMod 12.1 and later an XDA-Dev-built Android 7.1.2 on a Nexus 7 3G 2012. I rooted and installed CyanogenMod 12.1 and later 13.0 on a Nexus 5. I stumbled over some problems, but after some trial and error everything worked. Therefore I thought I was a bit experienced and could easily do that stuff with a phone that is listed as "supported"... I didn't ignore mandatory steps of the LineageOS Wiki. I did RTFM and read this forum. I often found questions being close to my problems, but sometimes I didn't understand the answer or often the answers didn't work for me. I hated to see how this forum tried to help new users that didn't reply on questions and how some new users neither followed the instructions nor posted their solution. I promise not to let the thread die before I summarize a solution. As soon as I'm allowed to, I'll link all the files I used to their source, I kept track of them all.
You may skip the history passage if you're not interested in the pre-story or if you don't want to profit of my trial and error experience. So here comes what I did until today:
Update Google USB drivers, already have adb and fastboot installed
Buy a new Huawei Honor 5X
Check its attributes: It's a KIW-L21 with a Huawei version of Android installed, version 5.1.1 and EMUI 3.1. This device is called "kiwi".
Successfully receive unlock code via Huawei
Root the phone via fastboot, until the fastboot & rescue mode screen says "OEM Unlocked, FRP Unlocked"
Flash TWRP 3.1.1.0 (kiwi) to recovery
Push lineage-14.1-20170809-nightly-kiwi-signed.zip to /sdcard on the phone
Wipe cache, system and data
Start install of the above LineageOS .zip file in TWRP
Installation getting aborted with "assert failed: kiwi.verify_trustzone(...) ==1" and ending with an "Error 7"
Learn from the forums that I should have installed "stock MM" first. "MM" seems to be Marshmallow, also known as Android 6.0
Search for images of "stock MM", end with a complete mess of gigabytes of dozens of images, differing by region (Arab/Europe/Americas/etc.), build numbers, firmware stuff, model numbers... oh crap, I don't understand a word
Extract different "stock recoverys" from multiple firmware packages, try to combine them with all kinds of firmwares
Flash stock recovery "recovery_l21_b130.img" to recovery, put SD card with /dload/UPDATE.APP (KIW-L21C432B130CUSTC432D005.dload.modaco.zip) into phone, reboot with Volume-up + power button, start factory reset, end with "data and cache format failed"
Flash stock recovery "recovery_l21_b130.img" to recovery, put SD card with /dload/UPDATE.APP (08_Huawei_KIW-L21_Firmware_C432B130CUSTC432D005_Android 5.1_EMUI 3.1_Finland.zip) into phone, reboot with Volume-up + power button, start factory reset, end with "data and cache format failed"
Flash stock recovery "RECOVERY.img" (from Extracted_L21_B130.zip) to recovery, put SD card with /dload/UPDATE.APP (08_Huawei_KIW-L21_Firmware_C432B130CUSTC432D005_Android 5.1_EMUI 3.1_Finland.zip) into phone, reboot with Volume-up + power button, start factory reset, end with "data and cache format failed"
All of the issues resulted in a boot loop
Wife getting mad because I bricked her new phone and wasted nights for it
Finally find this nice file depot of the Honor 5X in this forum but do not understand all the different headers or the structure of the list
Find out that the used firmware versions may have been too old (although I thought I should have used "stock" and therefore the oldest ones)
Try my luck with flashing L21_B130\RECOVERY.img (from Extracted_L21_B130.zip) to recovery, used "KIW-L21 C432B350 - D003" from the file depot to copy its UPDATE.APP to /dload/ at the external SD card, held both volume buttons and the power button until reboot
The Honor reboots into an autorecovery mode, installing the file from UPDATE.APP automatically and for the first time not cancelling the process
Great success!
I feel myself like I "unbricked" the phone
I am now holding a running Huawei-crippled Android 6.0.1 in my hands
My current situation is a running Huawei Honor 5X with a Huawei-branded Android 6.0.1, EMUI 4.0, build KIW-L21C432B350, custom version CUSTC432D003, fastboot & rescue mode screen saying "PHONE Unlocked". Unfortunately – you may have noticed – that is not LineageOS 14.1, which I actually wanted to install. How do I do that? Should I just follow the wiki instructions? Do I now have a "stock MM installed"? Doesn't it become uninstalled when I wipe system in TWRP before I install LineageOS?
When I try to read information of the phone via "fastboot getvar all", I just get an empty value after "all:". Why is that?
Rather than struggling over anything else when I try to follow the LineageOS wiki install guide again: What should I do or check first? I do not want to get a "kiwi.verify_trustzone" error again. How do I avoid that?
Thanks for your patience in advance!
You're on B350 and it's a good firmware to go (my phone was using it before 'conversion'). Flash twrp via fastboot, clear system/data/caches (backup your and app data first! if you want) and just flash Lineage + gapps (at once, no reboot between). You should be fine.
You are good to go
I have the problem that i cant get MM on it. I am still on b160.
I copied the dload folder for b330 on it and went to updater, menu, local update, update.app and press install
My phone reboots into twrp and nothing happens. I also cant boot into stock recovery. When i press vol up, vol down and power, my phone restarts over and over again. When i release the Buttons it just boots into android.
How do i get b300+ on it?
Activehannes said:
I have the problem that i cant get MM on it. I am still on b160.
I copied the dload folder for b330 on it and went to updater, menu, local update, update.app and press install
My phone reboots into twrp and nothing happens. I also cant boot into stock recovery. When i press vol up, vol down and power, my phone restarts over and over again. When i release the Buttons it just boots into android.
How do i get b300+ on it?
Click to expand...
Click to collapse
You can't flash stock images with twrp. You'll have to revert recovery back to stock one (extract image from b160) and then try to update.
ok that was a little bit to fast. do i need to download stock recovery and flash it via adb? because i got TWRP on it this way.
Activehannes said:
I have the problem that i cant get MM on it. I am still on b160.
Click to expand...
Click to collapse
Please do not steal my thread topic. I am trying to complete a tutorial.
you literally had the same problem I have. You had TWRP on it and tried to get stock recovery back to install MM. wouldn't it be part of a tut to explain how you did that? And since you know the answer, cant you tell me?
It worked! I finally got LineageOS working. Thanks to ShadySquirrel and PalakMi for your verification of my installation!
So here is my ultimate tutorial how to install LineageOS 14.1 (= Android 7.1.2) on a brand new Huawei Honor 5X KIW-L21 that comes originally with a Huawei branded Android 5.1.1:
Step 0: Preparation
You have up to date Google USB drivers installed
adb and fastboot are working
You know how to check checksums
You checked your device: It's a KIW-L21 with a Huawei version of Android installed, version 5.1.1 and EMUI 3.1. Your device is called "kiwi".
With your detailed device information, you ordered an unlocking password from Huawei (except your phone is already rooted)
Step 1: Install Stock MM (= Marshmallow = Android 6.0)
Root the phone via fastboot until the fastboot & rescue mode screen says "OEM Unlocked, FRP Unlocked"
You can reach the fastboot & rescue mode screen by plugging your phone via USB to a PC and keep volume-down + power buttons pushed until you see the Honor logo
Download the following images and its checksums and check them to avoid corrupted files:
- Stock recovery image from Extracted_L21_B130.zip: L21_B130\RECOVERY.img
- Stock MM from this nice file depot of the Honor 5X in this forum: KIW-L21 C432B350 - D003
Flash the stock recovery to the phone with fastboot when you are at the fastboot & rescue mode screen: "fastboot flash recovery RECOVERY.img"
Copy the UPDATE.APP of the above file to /dload/ at an external SD card and put it into the phone
Hold both volume buttons and the power button until reboot
The Honor reboots into an autorecovery mode, installing the file from UPDATE.APP automatically
Wait until it's ready and be happy about your Honor 5X with Stock MM
Check if you are at this status: Huawei Honor 5X with a Huawei-branded Android 6.0.1, EMUI 4.0, build KIW-L21C432B350, custom version CUSTC432D003, fastboot & rescue mode screen saying "PHONE Unlocked"
Step 2: Install LineageOS
Download the following images and its checksums and check them to avoid corrupted files:
- TWRP 3.1.1.0 recovery image for the Honor 5X (kiwi): twrp-3.1.1-0-kiwi.img
- LinageOS 14.1 nightly build for kiwi devices: lineage-14.1-20170816-nightly-kiwi-signed.zip
- Open GApps package for ARM64 / Android 7.1 (in my case I choose "pico" to have the calendar and Google Play): open_gapps-arm64-7.1-pico-20170819.zip
Place the files where you can reach them from your adb/fastboot-console
Connect phone via USB to PC
Keep volume-down + power buttons pressed until phone restarts and shows Honor logo, release buttons; "Fastboot & Rescue Mode" screen should appear
On PC, check with "fastboot devices" if phone is connected and ready to go (should list an ID and the state "fastboot")
Flash recovery with "fastboot flash recovery twrp-3.1.1-0-kiwi.img"; should report sending and writing with two "OKAY" messages and a "finished"
Try to start recovery mode by keeping volume-up + power buttons pressed until Honor logo appears, release buttons and wait ~ 20 seconds
In my case, this started the Huawei eRecovery – you don't want that (and it's not part of the LineageOS wiki)
Navigate with the volume buttons to "Reboot" and press the power button; phone should boot normally
Once your old Android is up again, activate USB-debugging
Check if adb is connected to your PC with "adb devices"; you must allow access to the device on your phone when prompted, the device should appear with the serial number and the state "device"
Restart into the recovery mode you really want with "adb reboot recovery" and wait until TWRP boots; allow writing on its first start
Check if adb is connected to your PC with "adb devices"; the device should appear with the serial number and the state "recovery"
Push LineageOS image and Google apps to phone with "adb push lineage-14.1-20170816-nightly-kiwi-signed.zip /sdcard/" and "adb push open_gapps-arm64-7.1-pico-20170819.zip /sdcard/"; both should report transferred size and time
Do not forget to push the md5 checksums if you are paranoid like me
Backup everything to an external SD card from the Backup menu in TWRP (needed 4021 MB of space and took ¼ hour in my case)
Seriously, backup! Even though you haven't done anything with the phone yet. You have a running firmware, that's worth a lot
In TWRP, select "Wipe" and then "Advanced Wipe"
Check "Cache", "Data" and "System" and swipe to wipe
Go "Back" to return to main menu, then select "Install"
As you have backed up to an external SD card, "Select Storage" to "Internal Storage"
Navigate to "/sdcard", select lineage-14.1-20170816-nightly-kiwi-signed.zip and swipe to confirm flash; should not take more than a minute
When it's done, do not reboot but navigate back to "Install" and install Google apps by selecting open_gapps-arm64-7.1-pico-20170819.zip and swiping to flash
Once installation has finished, return to the main menu, select "Reboot", and then "System"; the Honor logo will appear shortly
LineageOS 14.1 is now being initialized
Disconnect phone from PC
Profit!
I'll provide links to the images as soon as this forum allows me to.
Activehannes said:
you literally had the same problem I have. You had TWRP on it and tried to get stock recovery back to install MM. wouldn't it be part of a tut to explain how you did that? And since you know the answer, cant you tell me?
Click to expand...
Click to collapse
You are right, sorry, I was being too harsh. I'd like to post the link to the recovery image I've had success with, but I am not allowed to do so. Maybe you'll find it when you look for it and follow the instructions of my last post (Step 1). Does it work?
Et tu said:
It worked! I finally got LineageOS working. Thanks to ShadySquirrel and PalakMi for your verification of my installation!
So here is my ultimate tutorial how to install LineageOS 14.1 (= Android 7.1.2) on a brand new Huawei Honor 5X KIW-L21 that comes originally with a Huawei branded Android 5.1.1:
Step 0: Preparation
You have up to date Google USB drivers installed
adb and fastboot are working
You know how to check checksums
You checked your device: It's a KIW-L21 with a Huawei version of Android installed, version 5.1.1 and EMUI 3.1. Your device is called "kiwi".
With your detailed device information, you ordered an unlocking password from Huawei (except your phone is already rooted)
Step 1: Install Stock MM (= Marshmallow = Android 6.0)
Root the phone via fastboot until the fastboot & rescue mode screen says "OEM Unlocked, FRP Unlocked"
You can reach the fastboot & rescue mode screen by plugging your phone via USB to a PC and keep volume-down + power buttons pushed until you see the Honor logo
Download the following images and its checksums and check them to avoid corrupted files:
- Stock recovery image from Extracted_L21_B130.zip: L21_B130\RECOVERY.img
- Stock MM from this nice file depot of the Honor 5X in this forum: KIW-L21 C432B350 - D003
Flash the stock recovery to the phone with fastboot when you are at the fastboot & rescue mode screen: "fastboot flash recovery RECOVERY.img"
Copy the UPDATE.APP of the above file to /dload/ at an external SD card and put it into the phone
Hold both volume buttons and the power button until reboot
The Honor reboots into an autorecovery mode, installing the file from UPDATE.APP automatically
Wait until it's ready and be happy about your Honor 5X with Stock MM
Check if you are at this status: Huawei Honor 5X with a Huawei-branded Android 6.0.1, EMUI 4.0, build KIW-L21C432B350, custom version CUSTC432D003, fastboot & rescue mode screen saying "PHONE Unlocked"
Step 2: Install LineageOS
Download the following images and its checksums and check them to avoid corrupted files:
- TWRP 3.1.1.0 recovery image for the Honor 5X (kiwi): twrp-3.1.1-0-kiwi.img
- LinageOS 14.1 nightly build for kiwi devices: lineage-14.1-20170816-nightly-kiwi-signed.zip
- Open GApps package for ARM64 / Android 7.1 (in my case I choose "pico" to have the calendar and Google Play): open_gapps-arm64-7.1-pico-20170819.zip
Place the files where you can reach them from your adb/fastboot-console
Connect phone via USB to PC
Keep volume-down + power buttons pressed until phone restarts and shows Honor logo, release buttons; "Fastboot & Rescue Mode" screen should appear
On PC, check with "fastboot devices" if phone is connected and ready to go (should list an ID and the state "fastboot")
Flash recovery with "fastboot flash recovery twrp-3.1.1-0-kiwi.img"; should report sending and writing with two "OKAY" messages and a "finished"
Try to start recovery mode by keeping volume-up + power buttons pressed until Honor logo appears, release buttons and wait ~ 20 seconds
In my case, this started the Huawei eRecovery – you don't want that (and it's not part of the LineageOS wiki)
Navigate with the volume buttons to "Reboot" and press the power button; phone should boot normally
Once your old Android is up again, activate USB-debugging
Check if adb is connected to your PC with "adb devices"; you must allow access to the device on your phone when prompted, the device should appear with the serial number and the state "device"
Restart into the recovery mode you really want with "adb reboot recovery" and wait until TWRP boots; allow writing on its first start
Check if adb is connected to your PC with "adb devices"; the device should appear with the serial number and the state "recovery"
Push LineageOS image and Google apps to phone with "adb push lineage-14.1-20170816-nightly-kiwi-signed.zip /sdcard/" and "adb push open_gapps-arm64-7.1-pico-20170819.zip /sdcard/"; both should report transferred size and time
Do not forget to push the md5 checksums if you are paranoid like me
Backup everything to an external SD card from the Backup menu in TWRP (needed 4021 MB of space and took ¼ hour in my case)
Seriously, backup! Even though you haven't done anything with the phone yet. You have a running firmware, that's worth a lot
In TWRP, select "Wipe" and then "Advanced Wipe"
Check "Cache", "Data" and "System" and swipe to wipe
Go "Back" to return to main menu, then select "Install"
As you have backed up to an external SD card, "Select Storage" to "Internal Storage"
Navigate to "/sdcard", select lineage-14.1-20170816-nightly-kiwi-signed.zip and swipe to confirm flash; should not take more than a minute
When it's done, do not reboot but navigate back to "Install" and install Google apps by selecting open_gapps-arm64-7.1-pico-20170819.zip and swiping to flash
Once installation has finished, return to the main menu, select "Reboot", and then "System"; the Honor logo will appear shortly
LineageOS 14.1 is now being initialized
Disconnect phone from PC
Profit!
I'll provide links to the images as soon as this forum allows me to.
Click to expand...
Click to collapse
Hi I want the same kind of tutorial for KIW-L22 also. I tried almost every methods to flash any custom ROM. But all ended up as a failure. WhatI did was, I was in KIW-L22C675B360 version of EMUI. I unlocked the bootloader the official way, flashed twrp as proposed by TWRP site (fastboot flash recovery my-twrp.img). I booted into recovery successfully. I BackedUp all my partitions (Thank god that I did this). Then I wiped my Data, Dalvik-Cache, Cache, System, Android Secure. Then I flashed the latest Lineage OS (lineage-14.1-20170816-nightly-kiwi-signed.zip) and flashed the latest Open Gapps nano. Then I rebooted. There was no problem with the installation. Then the boot animation started loading and I was waiting to see LineageOS. :crying: :crying: But all of a sudden, the boot animation freezes and the phone starts rebooting. This was happening all the time no matter how many times the phone rebooted. I thought it might be a ROM problem and i went back to twrp by holding power up when the phone rebooted. Wipes all as before and flashed certain other ROMs like AospExtended, MIUI 8 (PatchRom), etc but neither of them booted. I don't know what to do after that and I restored my old TWRP backup and now I'm on stock EMUI KIW-L22C675B360. I would be thankful if I get a solution to solve this problem. Waiting eagerly for answers.
Uvneshkumar said:
Hi I want the same kind of tutorial for KIW-L22 also. I tried almost every methods to flash any custom ROM. But all ended up as a failure. WhatI did was, I was in KIW-L22C675B360 version of EMUI. I unlocked the bootloader the official way, flashed twrp as proposed by TWRP site (fastboot flash recovery my-twrp.img). I booted into recovery successfully. I BackedUp all my partitions (Thank god that I did this). Then I wiped my Data, Dalvik-Cache, Cache, System, Android Secure. Then I flashed the latest Lineage OS (lineage-14.1-20170816-nightly-kiwi-signed.zip) and flashed the latest Open Gapps nano. Then I rebooted. There was no problem with the installation. Then the boot animation started loading and I was waiting to see LineageOS. :crying: :crying: But all of a sudden, the boot animation freezes and the phone starts rebooting. This was happening all the time no matter how many times the phone rebooted. I thought it might be a ROM problem and i went back to twrp by holding power up when the phone rebooted. Wipes all as before and flashed certain other ROMs like AospExtended, MIUI 8 (PatchRom), etc but neither of them booted. I don't know what to do after that and I restored my old TWRP backup and now I'm on stock EMUI KIW-L22C675B360. I would be thankful if I get a solution to solve this problem. Waiting eagerly for answers.
Click to expand...
Click to collapse
The problem is with the B360, you should have been on an update before b360
PalakMi said:
The problem is with the B360, you should have been on an update before b360
Click to expand...
Click to collapse
Now after flashing the rom, I flashed a zip called "BaPatch.zip" and after that Lineage booted successfully.
Uvneshkumar said:
Now after flashing the rom, I flashed a zip called "BaPatch.zip" and after that Lineage booted successfully.
Click to expand...
Click to collapse
Good to know :highfive:
@Et tu, Brute? : mate, I followed your instructions but the device ended up in bootloop. Any help?
m on twrp 3.2.2.0
Lineage OS v14.1 (29th Jun build)
Gapps 7.1 x64 pico
There are a number of generic installation guides for custom roms eg https://www.xda-developers.com/how-to-install-custom-rom-android/
However this one is specifically for the LG G6 and tested using the US997 model. It worked for me, but I welcome comments on how to improve it.
Create a folder on the PC for all the downloads and files
Download phone driver from LG website
https://www.lg.com/us/support/help-library/lg-mobile-drivers-and-software-CT10000027-20150179827560
Download ADB/Fastboot https://developer.android.com/studio/releases/platform-tools (You need to unzip once downloaded)
(I had an error "adb server version (31) doesn't match this client (41) killing". I searched my PC and found an older version which I had used for another phone and deleted the folders and reinstalled from the download)
Ensure the phone is backing up. (Google backup is working, you have all your photos music etc downloaded) the next steps will wipe the phone
Remove the PIN/Password/Fingerprints from the phone so it will boot without any security.
Unlock the bootloader
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
The phone will then reboot and do a complete wipe so you need to wait a while for Android to setup.
Telegraph has the latest news on LG G6 ROMs and Recovery. From here I got the links for SHRP recovery which seems more up to date for LG G6 than TWRP. (https://web.telegram.org/#/[email protected])
https://sourceforge.net/projects/pa-g6/files/Releases/SHRP/20.07.2020/US997/
I named the downloaded file "recovery" (You need the .img file not the ZIP)
There are lots of active ROMS for LG G6 I have Lineage installed on another phone which works really well, but Havoc seems the most popular on the G6.
Download the ROM and Gapps https://opengapps.org/ (I used Nano, remember G6 is 64bit)
You will also need to update the bootloader. This was the latest I found for the US997
https://androidfilehost.com/?fid=1899786940962575226
(I missed the bootloader the first time and Gapps will not flash, I was helped by the LG G6 community on Telegram https://web.telegram.org/#/[email protected])
Now you have downloaded all you need
Then connect the phone to the PC and ensured you have ADB debug on in developer options and boot the phone into fastboot
On the PC open a command prompt in the folder you have all the files:
adb reboot bootloader
To load the recovery to the phone :
Fastboot flash recovery recovery.img
YOU MUST NOW BOOT DIRECTLY TO RECOVERY. Do not reboot to Android as this will automatically reset recovery to the stock version.
Unplug the USB cable and reboot to recovery (hold volume down + power button).. continue holding until phone reboots...
As soon as you see the LG logo on the screen.. let go of the power button then quickly press it again (never letting go of volume down).
Keep holding until you see the Factory Reset screen. Click thru the factory reset screens using the volume buttons to move up/down and power button to select. Choose "Yes" twice (saying you want to reset the phone it should boot into your new recovery. Despite what the screen says it won't actually factory reset/wipe your data... as long as you've installed a custom recovery and have not booted into Android since then.
Most likely you will be asked the password to decrypt the data folder. I tried my phone PIN and other default passwords suggested on the internet. I eventually found that this is a known issue and you need for cancel out of this screen and go and "FORMAT DATA"
Reboot directly to recovery (select reboot recovery in Skyhawk), this time you should not be asked for the decryption password.
I recommend you backup your current setup before making changes. If you hit issues you can use the recovery to restore. My SD card slot is broken (Poor LG design) so I plugged a USB thumb drive into the USB C slot and did a full backup. (No data since I just formatted it).
Wipe the partitions before you flash
Full wipe ("The only option you ever need")
Select Advanced and wipe system partition.
FLASH (You need to put the ZIP files either on the USB drive as I did, or copy to your SD card, or you can use ADB sideloader from the PC to push the files to the phone). The USB drive seems the easiest since you can plug it into your PC to load the files then plug it into the phone to read them.
Flash in the following order
Bootloader
ROM
Gapps
After Installing wipe cache and Davik
Reboot
It will do lots of processing while setting up. Ensure it stays cool (remove case and leave it plugged in with the screen off)
Donate to the developer of your new ROM at the end when it works.
I have been running my LG G6 on Android 10 for a few weeks and thought I would share my observations, I am using Havoc 3.7 installed with Skyhawk, I did not root the phone.
Likes : Very smooth experience, phone feel like it is running much faster. Very stable, I had one surprise reboot in the time I have used it. No issues (so far) with installing or using any apps including banking. Much lower use of storage, I have 6GB free.
Same : Battery life is about the same as before.
Gaps : Cannot encrypt, VOLTE doesn't work (which may become a big issue for T-Mobile and AT&T soon), when being used the phone gets much warmer than it did before and the wifi setting randomly turns off.
Next Steps: I am going to try Lineage which has released some fixes for the WIFI issue and report back.
I'm trying to follow the instructions as per this guide for the tmo version of G6 (H87220g) and I'm running into a roadblock on the recovery flash:
[[email protected] tmp]$ mkdir skyhawk
[[email protected] tmp]$ cd skyhawk && 7z x ../SHRP_v2.3.2_us997-233920072020.zip
[[email protected] skyhawk]$ fastboot flash recovery recovery.img
Sending 'recovery' (36936 KB) OKAY [ 1.252s]
Writing 'recovery' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
I downloaded the Skyhawk zip from the PA download link, unzipped it and used the recovery.img file found inside the zip as part of the fastboot command. Is this incorrect ?
Yes, you need the recovery.img file to flash via fastboot. Have you successfully unlocked the boot loader? You cannot replace recovery without unlocking.
You also need to ensure you have the appropriate files for your phone I have a US997 but as you have H872 you would need skyhawk for the H872 in the notes above you are still using US997.
bootloader is unlocked as per:
https://forum.xda-developers.com/tmobile-g6/how-to/unlock-bootloader-tmo-t3578099
fastboot flash is failing and I'm not the only one it seems like based on comments here and reddit...
I gonna try out @runningnak3d guide and see if that works...
This guide is for the US997. The H872 has a much more complicated process to install recovery : https://forum.xda-developers.com/tmobile-g6/how-to/root-h872-to-including-11g-t3775518
Hi, I have a semibrick on my X3 Superzoom (Global), and I can't seem to restore the original firmware. When it was working properly, I think the phone was updated to the latest version available in Europe (RMX2081EU_11.A.50), hence Realme UI 1.0.
I do not remember very well what I did, it's been a few weeks since my "screw up", I must have flashed an untrusted firmware, the thing is that when rebooting the screen looks black and goes into a continuous bootloop, but allows to enter fastboot mode with power + Vol down (I know because I can launch fastboot commands). Curiously, when it goes into bootloop you don't see the Realme logo, I discovered that the logo is there but with the screen illumination at minimum, and you can only glimpse a little if you put it under a lamp. Very strange.
Since it can go into fastboot mode I have tried flashing several firmwares for my phone, RMX2086 and none of them repair brik. I have tried always by command line because with MsmDownloadTool I don't have login access and with Realme Flash Tool always shows error "cannot find central directory", I have tried also with QFil and I can't get it to stay stable on the port.
I flash with command line with "fastboot flash" all .img files of super, recovery, boot, boot, dtbo, vbmeta (in that order) but it does nothing. Furthermore, I have tried with several ofp files like for example the following file from realmefirmware.com, which seems to be the last released full version of Realme UI 2.0 (I have tried also with Realme UI 1.0 versions):
RMX2086GDPR_11_C.11_2022011318270168.zip (I decrypt the ofp file inside to extract the .img files.).
Interestingly, I can flash TWRP Recovery (it works, and you see the screen with normal TWRP recovery) and from the recovery I can flash a Custom Recovery like PixelPlusUI. The phone boots (no logo visible) in CustomROM normally, but after a while of use the screen turns off but working ROM.
What should I do? Although I have some flashing experience, I'm pretty much stuck. Can anyone give me any suggestions?
Sorry with making it so long, but I wanted to explain this as best as possible so it is well understood.
When you already upgrades to Android 11, you can not flash custom rom, otherwise it bricks, because all the custom roms required android 10 ROM system, you may downgrade using flash tool (I tried but failed to flash any stock rom using any tool, only able to flash using fastboot commands)
bernarbernuli said:
Hi, I have a semibrick on my X3 Superzoom (Global), and I can't seem to restore the original firmware. When it was working properly, I think the phone was updated to the latest version available in Europe (RMX2081EU_11.A.50), hence Realme UI 1.0.
I do not remember very well what I did, it's been a few weeks since my "screw up", I must have flashed an untrusted firmware, the thing is that when rebooting the screen looks black and goes into a continuous bootloop, but allows to enter fastboot mode with power + Vol down (I know because I can launch fastboot commands). Curiously, when it goes into bootloop you don't see the Realme logo, I discovered that the logo is there but with the screen illumination at minimum, and you can only glimpse a little if you put it under a lamp. Very strange.
Since it can go into fastboot mode I have tried flashing several firmwares for my phone, RMX2086 and none of them repair brik. I have tried always by command line because with MsmDownloadTool I don't have login access and with Realme Flash Tool always shows error "cannot find central directory", I have tried also with QFil and I can't get it to stay stable on the port.
I flash with command line with "fastboot flash" all .img files of super, recovery, boot, boot, dtbo, vbmeta (in that order) but it does nothing. Furthermore, I have tried with several ofp files like for example the following file from realmefirmware.com, which seems to be the last released full version of Realme UI 2.0 (I have tried also with Realme UI 1.0 versions):
RMX2086GDPR_11_C.11_2022011318270168.zip (I decrypt the ofp file inside to extract the .img files.).
Interestingly, I can flash TWRP Recovery (it works, and you see the screen with normal TWRP recovery) and from the recovery I can flash a Custom Recovery like PixelPlusUI. The phone boots (no logo visible) in CustomROM normally, but after a while of use the screen turns off but working ROM.
What should I do? Although I have some flashing experience, I'm pretty much stuck. Can anyone give me any suggestions?
Sorry with making it so long, but I wanted to explain this as best as possible so it is well understood.
Click to expand...
Click to collapse
Have you found solution? I have exactly the same problem!
maskalicz said:
Have you found solution? I have exactly the same problem!
Click to expand...
Click to collapse
It's been over a year since it happened, I didn't find a solution on my own, and since it was still under warranty, I sent it to the official technical service and a couple of weeks later I received it back with the firmware working.
Hey community,
I have been running Poco F1 with twrp and PixelExperience for the last 2 years. Considering the past record of the OS and my experience with the OS, I decided recently to upgrade to the newer PE12 for Poco F1 (maintained by Lakshay Garg). It went smooth initially and after the last OTA update, the phone started behaving weirdly.
Long story short,
This morning the phone went into an automatic restart and is now stuck in a boot loop. It boots and reaches the "G" logo and reboots. However, the weird part is,
Code:
fastboot flash
and
Code:
fastboot boot
are not available, throwing errors. The device is visible in
Code:
adb devices
and
Code:
fastboot devices
. This problem occurs when the phone is not plugged in. Once plugged in, the phone runs fine and everything just works. TWRP is not accessible, as if it is not there anymore and the only recovery that I can reach is the pixel recovery which has no option to flash any custom recovery (newbie, so not sure if something like this should exists or not).
I've tried various threads here and wasn't able to find any solution. Let me know what commands/outputs you guys might need from the device to help me in this.
Thanks in advance. Hope this gets fixed soon.
tysonX5653 said:
Hey community,
I have been running Poco F1 with twrp and PixelExperience for the last 2 years. Considering the past record of the OS and my experience with the OS, I decided recently to upgrade to the newer PE12 for Poco F1 (maintained by Lakshay Garg). It went smooth initially and after the last OTA update, the phone started behaving weirdly.
Long story short,
This morning the phone went into an automatic restart and is now stuck in a boot loop. It boots and reaches the "G" logo and reboots. However, the weird part is,
Code:
fastboot flash
and
Code:
fastboot boot
are not available, throwing errors. The device is visible in
Code:
adb devices
and
Code:
fastboot devices
. This problem occurs when the phone is not plugged in. Once plugged in, the phone runs fine and everything just works. TWRP is not accessible, as if it is not there anymore and the only recovery that I can reach is the pixel recovery which has no option to flash any custom recovery (newbie, so not sure if something like this should exists or not).
I've tried various threads here and wasn't able to find any solution. Let me know what commands/outputs you guys might need from the device to help me in this.
Thanks in advance. Hope this gets fixed soon.
Click to expand...
Click to collapse
Seems to be a battery problem. How old is it? You may need to replace it.
However make sure you followed the clean install method before you come on a conclusion. Also try to not use any Magisk modules.
Best Clean Install method:
Backup all your data. All your data into Internal Storage will be lost during this process.
Download latest Official TWRP Recovery, Pixel Experience build.
Create one Folder and move all the files you downloaded there.
Reboot to Fastboot Mode
Connect your device to PC and Boot into to TWRP via ADB or Minimal ADB and Fastboot:
Code:
fastboot boot <recovery_filename>.img
Example:
Code:
fastboot boot C:\Users\Retrial\Desktop\twrp-3.6.1_9-0-beryllium.img
Select Wipe > Advanced Wipe -> Select Dalvik / ART Cache, System, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe.
Go back and select Wipe > Format Data > type yes
While you are in TWRP, transfer the Folder with the files you downloaded above.
Flash Pixel Experience ROM.
Flashing the ROM will replace TWRP with PE Recovery so OTA updates can be installed without problems since TWRP currently doesn't support decryption on A12 encypted ROMs - If you need in future to change ROM just fastboot boot to twrp via adb and flash img of twrp to recovery partition.
Done! Reboot to system.
Thanks, turns out that it was a battery problem after all. After battery replacement everything is working just fine. I also installed Awaken OS as Pixel Experience was removing the TWRP recovery each time I flashed it. Now as for my fastboot, initially it was not working; it was showing this error whenever I tried to flash TWRP recovery or any stock recovery:
Sending 'boot.img' (38640 KB) FAILED (Write to device failed (Cannot send after transport endpoint shutdown)) fastboot: error: Command failed
After this, the fastboot mode was diconnected and my phone was showing this Error:
Press any Key to Shut Down
It was resolved by running this bat file (as admin) :
https://bit.ly/31T2LcB
After running this file, there was no error and I was able to flash the twrp Recovery smoothly. So thanks for all the help really appreciate it.
tysonX5653 said:
Thanks, turns out that it was a battery problem after all. After battery replacement everything is working just fine. I also installed Awaken OS as Pixel Experience was removing the TWRP recovery each time I flashed it. Now as for my fastboot, initially it was not working; it was showing this error whenever I tried to flash TWRP recovery or any stock recovery:
Sending 'boot.img' (38640 KB) FAILED (Write to device failed (Cannot send after transport endpoint shutdown)) fastboot: error: Command failed
After this, the fastboot mode was diconnected and my phone was showing this Error:
Press any Key to Shut Down
It was resolved by running this bat file (as admin) :
https://bit.ly/31T2LcB
After running this file, there was no error and I was able to flash the twrp Recovery smoothly. So thanks for all the help really appreciate it.
Click to expand...
Click to collapse
Did you face the problem again?
I am using PE11 since last 2 years but suddenly i started facing the same problem. When plugged in, works fine. When I unplug it, works until screen is on and when I use power button to lock or unlock, phone goes into bootloop. I opend it in twrp where it can work as long as battery lasts, that's why I am not sure if it's a battery problem or something else