Related
So LeEco ( LeTV or Le ) Launched Their Summer End Device AKA The One and The Only The Flagship Of This Year ( Just jk ) Le MAX 2, This phone has Killer Specs, Killer Price and Everything Which Is Clear and I Also attended the Event which happend in Sirifort India.
Today I'm Going to show You guys a Root Method of The Device, So basically TWRP 3.0.0 Recovery for LeEco Le Max 2 is already available.
Let's Start Doing It :
Firstly Download the following Files :
Download ADB Fastboot Driver : stechguide (dot) com/how-to-install-adb-and-fastboot-on-windows/
Download TWRP 3.0 : androidfilehost (dot) com/?fid=24588239633383558
Download SuperSu : download.chainfire (dot) eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip
Install TWRP on LeEco Le Max 2 –
1) First enable USB debugging from setting>developer option>. To enable Developer Options, go to About phone and tap the Build Number 7 times.
2) Now go to installation directory open ADB folder and open the command window thereby pressing and hold the ‘shift’ key and right-clicked anywhere in that folder.
3) Now connect your phone to PC and reboot the device into fastboot mode by typing
Code:
adb reboot bootloader
4) You are in Fastboot mode now to check your connection by entering below command in command prompt. It will return your device serial number means your device properly connected. Check your driver if the above command is not responding.
Code:
fastboot devices
5) Type the below command correctly in command prompt and then press enter. It starts flashing recovery on your phone.
Code:
fastboot flash recovery recovery.img
6) YAAY!, you installed the custom recovery on YOUR PHONE!
Time to root :
1) To Root LeEco Le Max 2, first, download the SuperSu zip file from above.
2) Now save the SuperSu zip file to your phone.
3) Boot your device into Recovery mode (TWRP) by pressing ‘Volume Down + Power‘ button.
4) In TWRP recovery navigate to Install Zip and select ‘SuperSu.zip’ to root.
5) Swipe to install SuperSu and reboot your device. yaay! you rooted the device!:laugh:
Enjoy!
DakshMiglani said:
So LeEco ( LeTV or Le ) Launched Their Summer End Device AKA The One and The Only The Flagship Of This Year ( Just jk ) Le MAX 2, This phone has Killer Specs, Killer Price and Everything Which Is Clear and I Also attended the Event which happend in Sirifort India.
Today I'm Going to show You guys a Root Method of The Device, So basically TWRP 3.0.0 Recovery for LeEco Le Max 2 is already available.
Let's Start Doing It :
Firstly Download the following Files :
Download ADB Fastboot Driver : stechguide (dot) com/how-to-install-adb-and-fastboot-on-windows/
Download TWRP 3.0 : androidfilehost (dot) com/?fid=24588239633383558
Download SuperSu : download.chainfire (dot) eu/897/SuperSU/BETA-SuperSU-v2.67-20160121175247.zip
Install TWRP on LeEco Le Max 2 –
1) First enable USB debugging from setting>developer option>. To enable Developer Options, go to About phone and tap the Build Number 7 times.
2) Now go to installation directory open ADB folder and open the command window thereby pressing and hold the ‘shift’ key and right-clicked anywhere in that folder.
3) Now connect your phone to PC and reboot the device into fastboot mode by typing
Code:
adb reboot bootloader
4) You are in Fastboot mode now to check your connection by entering below command in command prompt. It will return your device serial number means your device properly connected. Check your driver if the above command is not responding.
Code:
fastboot devices
5) Type the below command correctly in command prompt and then press enter. It starts flashing recovery on your phone.
Code:
fastboot flash recovery recovery.img
6) YAAY!, you installed the custom recovery on YOUR PHONE!
Time to root :
1) To Root LeEco Le Max 2, first, download the SuperSu zip file from above.
2) Now save the SuperSu zip file to your phone.
3) Boot your device into Recovery mode (TWRP) by pressing ‘Volume Down + Power‘ button.
4) In TWRP recovery navigate to Install Zip and select ‘SuperSu.zip’ to root.
5) Swipe to install SuperSu and reboot your device. yaay! you rooted the device!:laugh:
Enjoy!
Click to expand...
Click to collapse
very good how to! couldn't go wrong.! before step 4 I also check if device is connected via code: adb devices.
if device is not showing up you already know somethin's wrong.
Thank you for the guide. I pushed twrp into my phone without any error and I'm on the OTA 5.8.015S but it doesn't work. I rebooted into recovery and it still gave me the stock recovery screen.
Finally got it to work! After pushing twrp you have to type fastboot boot twrp.img and you will get a screen that looks like it's broken. Leave it alone for about 1 minute or two then the screen will turn off. Then press the power button once only to wake the screen up. From there twrp is working! Thank you to steve mars and jim262 for this tips!
Cannot mount /cust in TWRP
After trying to flash I noticed that after the wipes The failure of /cust cannot be mounted appears.
Can't get adb/fastboot to work on Windows 10
windhoarse00 said:
Can't get adb/fastboot to work on Windows 10
Click to expand...
Click to collapse
Did you ever get a solution for this?
Windows 10 can be a pain at times when it comes to drivers and stuff.
Sörnäinen said:
Did you ever get a solution for this?
Windows 10 can be a pain at times when it comes to drivers and stuff.
Click to expand...
Click to collapse
Were you asking for help or just wanted to help windhoarse00?
Amowagou said:
Were you asking for help or just wanted to help windhoarse00?
Click to expand...
Click to collapse
I don't have the phone yet - a mix of both, as I will be in a similar situation soon.
@Sörnäinen, I have no problem in getting the adb to work on my Win 10 PC although I have no intention to root or install third party ROM on my phone. I am happy with the stock Chinese 18S firmware.
Amowagou said:
@Sörnäinen, I have no problem in getting the adb to work on my Win 10 PC although I have no intention to root or install third party ROM on my phone. I am happy with the stock Chinese 18S firmware.
Click to expand...
Click to collapse
That's welcome news, cheers.
For me rooting a phone and putting a custom ROM of my choice is essential - not to speak of Titanium Backup to transfer all my stuff to the new phone.
I can use adb to reboot the phone into bootloader. But the fastboot seems not working. Anyone has idea?
nflau said:
I can use adb to reboot the phone into bootloader. But the fastboot seems not working. Anyone has idea?
Click to expand...
Click to collapse
Yep. I ended up with the exactly same issue.
Not working at all, no matter what I do.
Hm. Can anyone help? My phone is not being recognized in ADB devices. Not on my Windows 10 machine, not on my windows 7 machine, not on my Mac.
So it must be something on the phone site. Rooting as well as installation of TWRP sadly not possible this way.
Any help available?
Sörnäinen said:
Hm. Can anyone help? My phone is not being recognized in ADB devices. Not on my Windows 10 machine, not on my windows 7 machine, not on my Mac.
So it must be something on the phone site. Rooting as well as installation of TWRP sadly not possible this way.
Any help available?
Click to expand...
Click to collapse
Where did you buy it? I bought from geekbuying two weeks ago. My EUI version is 5.8.0.15S(Stable), and seems like a special build for international user with google play store.
nflau said:
Where did you buy it? I bought from geekbuying two weeks ago. My EUI version is 5.8.0.15S(Stable), and seems like a special build for international user with google play store.
Click to expand...
Click to collapse
Gearbest.
I'm already considering to just keep the EUI, but I do not trust their PlayStore installation...
Ok. For all those who run into troubles:
Windows 10 has driver issues. You need to install a separate fastboot driver via the device manager of Windows.
And the TWRP that's suggested in this thread can have issues - the TWRP von TeamSpain is less temperamental.
I also noted that adb and fastboot only worked from the minimal Adb and fastboot thread here on XDA, the 15 sec version wouldn't want to work on my Windows system.
This was a bumpy ride, heaven's sake.
Sörnäinen said:
Ok. For all those who run into troubles:
Windows 10 has driver issues. You need to install a separate fastboot driver via the device manager of Windows.
And the TWRP that's suggested in this thread can have issues - the TWRP von TeamSpain is less temperamental.
I also noted that adb and fastboot only worked from the minimal Adb and fastboot thread here on XDA, the 15 sec version wouldn't want to work on my Windows system.
This was a bumpy ride, heaven's sake.
Click to expand...
Click to collapse
Where to download the driver? Thanks!
nflau said:
Where to download the driver? Thanks!
Click to expand...
Click to collapse
No need to download. Just choose the list of drivers on the PC and take the one that's made for fastboot.
this is not real for dummies
this is what you forgot
1) after enable debug mode with tapping 7 times build you must actually enabyle usb debug in settings
2) to install the driver in win10 which dont work automatic unrar the adbsetup and then start in driver dir DPInst_x64.exe
3) after I did manage to adb reboot bootloader I got after reboot into the bootloader but then I am stuck
what is recovery image? and fastboot devices shows nothing
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
I got a very strange & interesting problem when flashing TWRP into my Redmi note 4x ,
Problem statement:
When My Redmi note 4x boot into TWRP recovery, it is black screen , nothing show up on the screen, and if I connect the phone to pc, and type command: adb devices, and the phone is on the output list, and in 'recovery' mode.
my flash steps:
https://forum.xda-developers.com/showpost.php?p=74775246&postcount=900
the phone info. & recovery log are in this post:
https://forum.xda-developers.com/showpost.php?p=74776640&postcount=905
I also have tested another 2 cases:
case #1: flash stock recovery, and type command fastboot boot stock-recovery.img, phone can boot into stock recovery successfully, the stock recovery UI show up on the screen....
then boot into fastboot mode again , type command : fastboot boot twrp_xxx.img
, the phone is black screen, if i connect phone to PC now, and type command 'adb devices' , my phone is on the list with 'recovery' ... same issue
case #2: flash TWRP recovery, and then type command: fastboot boot twrp-xxx.img, the phone is black screen, if i connect phone to PC now, and type command 'adb devices' , my phone is on the list with 'recovery' ... same issue
then boot into fastboot mode again ,type command fastboot boot stock-recovery.img, phone can also boot into stock recovery successfully, the stock recovery UI show up on the screen....
Command when you flash recovery is:
fastboot flash recovery name_recovery.img
Not
Fastboot boot recovery recovery.img <~~~ its only boot to recovery temporary...
Anyway you wrong thread
andro_diggers said:
Command when you flash recovery is:
fastboot flash recovery name_recovery.img
Not
Fastboot boot recovery recovery.img <~~~ its only boot to recovery temporary...
Anyway you wrong thread
Click to expand...
Click to collapse
thanks, i know it. i know the flash command . the point is ,even i boot to temporary twrp recovery, it does not work, it is black screen
JevonsDU said:
I got a very strange & interesting problem when flashing TWRP into my Redmi note 4x ,
Problem statement:
When My Redmi note 4x boot into TWRP recovery, it is black screen , nothing show up on the screen, and if I connect the phone to pc, and type command: adb devices, and the phone is on the output list, and in 'recovery' mode.
my flash steps:
https://forum.xda-developers.com/showpost.php?p=74775246&postcount=900
the phone info. & recovery log are in this post:
https://forum.xda-developers.com/showpost.php?p=74776640&postcount=905
I also have tested another 2 cases:
case #1: flash stock recovery, and type command fastboot boot stock-recovery.img, phone can boot into stock recovery successfully, the stock recovery UI show up on the screen....
then boot into fastboot mode again , type command : fastboot boot twrp_xxx.img
, the phone is black screen, if i connect phone to PC now, and type command 'adb devices' , my phone is on the list with 'recovery' ... same issue
case #2: flash TWRP recovery, and then type command: fastboot boot twrp-xxx.img, the phone is black screen, if i connect phone to PC now, and type command 'adb devices' , my phone is on the list with 'recovery' ... same issue
then boot into fastboot mode again ,type command fastboot boot stock-recovery.img, phone can also boot into stock recovery successfully, the stock recovery UI show up on the screen....
Click to expand...
Click to collapse
Try this :
Code:
fastboot flash recovery recoveryname.img
Next, do not disconnect your device... Instead run this command
fastboot boot recoveryname.img
Give it some time, it'll boot to TWRP.
If it's doesn't works, then this :
fastboot flash recovery recoveryname.img
Do not disconnect your device, use hardware keys to boot into TWRP.
Volume up + power key simultaneously.
Sent from my Redmi Note 4 using Tapatalk
sachin n said:
Try this :
Code:
fastboot flash recovery recoveryname.img
Next, do not disconnect your device... Instead run this command
fastboot boot recoveryname.img
Give it some time, it'll boot to TWRP.
If it's doesn't works, then this :
fastboot flash recovery recoveryname.img
Do not disconnect your device, use hardware keys to boot into TWRP.
Volume up + power key simultaneously.
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
have tried both methods already, many times, not work
JevonsDU said:
have tried both methods already, many times, not work
Click to expand...
Click to collapse
i think i found the answer for this problem:
TWRP does not support the touch screen in new made redmi note 4x (at least my note4x )
i use the adb shell connect to twrp, even no twrp ui . then use the twrp command line to flash lineageos to my note4x successfully. then reboot to lineageos, i found the touch screen does not work, it can show lineageos ui ,but no reponse to any press on the screen. then i use otg cable to connect a mouse to the phone, the mouse works, i can use the mouse to control the phone.
based on above test, i believe both twrp and latest lineageos do not support new made redmi note 4x, at least my note4x
p.s. my note4x made date is Nov 2017.
Are you sure it is Mido?
Sent from my Redmi Note 4 using Tapatalk
JevonsDU said:
i think i found the answer for this problem:
TWRP does not support the touch screen in new made redmi note 4x (at least my note4x )
i use the adb shell connect to twrp, even no twrp ui . then use the twrp command line to flash lineageos to my note4x successfully. then reboot to lineageos, i found the touch screen does not work, it can show lineageos ui ,but no reponse to any press on the screen. then i use otg cable to connect a mouse to the phone, the mouse works, i can use the mouse to control the phone.
based on above test, i believe both twrp and latest lineageos do not support new made redmi note 4x, at least my note4x
p.s. my note4x made date is Nov 2017.
Click to expand...
Click to collapse
Try redwolf recovery
prathu30 said:
Try redwolf recovery
Click to expand...
Click to collapse
tried.. not work either...
JevonsDU said:
tried.. not work either...
Click to expand...
Click to collapse
There is a new recovery Official TWRP
Stevica Smederevac said:
There is a new recovery Official TWRP
Click to expand...
Click to collapse
good ! what's new in this version ? support the ebbg display?
JevonsDU said:
good ! what's new in this version ? support the ebbg display?
Click to expand...
Click to collapse
No but who knows, maybe it'll work now.
JevonsDU said:
tried.. not work either...
Click to expand...
Click to collapse
Maybe there's something to do with firmware? Did you try the latest one?
prathu30 said:
Maybe there's something to do with firmware? Did you try the latest one?
Click to expand...
Click to collapse
actually, even twrp does not support ebbg display, i can still use it to flash 3rd rom via twrp command line. so i don't care whether twrp support ebbg display or not.
my concern is , currently seems no 3rd rom for redmi note4 support ebbg display, and i hv to use official rom, no other choice
@JevonsDU: Just for the record, would you mind to share the touch screen info of your device? Go to Settings > about phone > tap kernel version 8..10 times and go to version info then let us know the LCD and the TP info - probably we all have the same as in the video at 11sec but you have a different TP chip?
crok.bic said:
@JevonsDU: Just for the record, would you mind to share the touch screen info of your device? Go to Settings > about phone > tap kernel version 8..10 times and go to version info then let us know the LCD and the TP info - probably we all have the same as in the video at 11sec but you have a different TP chip?
Click to expand...
Click to collapse
fyi
mdss_dsi_panel_on panel_name = qcom,mdss_dsi_r63350_ebbg_fhd_video
prathu30 said:
Maybe there's something to do with firmware? Did you try the latest one?
Click to expand...
Click to collapse
i hv tried this version, still black screen on my redmi note4x, seems not support EBBG display yet.
Stevica Smederevac said:
No but who knows, maybe it'll work now.
Click to expand...
Click to collapse
tested.
not support EBBG display yet
JevonsDU said:
tested.
not support EBBG display yet
Click to expand...
Click to collapse
I'm not sure there will be a solution to your problem
Maybe selling that one and buy a global version.
Please try and report if this recovery boots with working display twrp-mido-r63350.img.
I've added some dts code to kernel reversed from latest miui builds. New displays code was added first in miui 7.5.11 and not included in kernel sources released for mido by Xiaomi. If this recovery works for this type of display I will push code to official lineage 14.1 kernel.
Hello guys,
I have a problem with installing and starting TWRP for the Mi 8 Pro Explorer Edition (Codenamed Ursa).
I have the latest version of Miui Global available for my device (MIUI 12.0.1), and I have unlocked the bootloader with the official procedure (successfully).
I followed the guide for MIUI.eu (the same with all devices to tell the truth) to install the latest TWRP available, but when TWRP starts the device remains off. I can get into fastboot or start it normally, but I can't install it despite ADB giving me positive results.I also tried to install older TWRP, but the result is the same, the device does not start the TWRP, remaining off. Anyone have a solution?
Thanks a lot to everyone
Ps. When I unlocked the bootloader I had to enter some registry keys otherwise the annoying bug came out that when connecting the device to the PC it came out of fastboot mode, opening a black page with a white writing at the top left
PPS. I want install MIUI.eu 12.5, So I'm wasting all this time
Does it show any error when you try to run these command?
fastboot flash recovery twrp.img
fastboot boot twrp.img
Click to expand...
Click to collapse
jwhan said:
Does it show any error when you try to run these command?
Click to expand...
Click to collapse
The solution is use the TWRP 3.2.3 CN by wzsx150, and work perfectly. Now I have found the solution...
THX anyway
Hey
So i was following this guide:
(update) unofficial twrp 3.5.0 for Redmi Note 9 Pro 4G - unofficial twrp
download unofficial twrp 3.5.0 root redmi note 9 pro, user who own redmi note 9 pro 4G can download latest twrp on it
unofficialtwrp.com
It was looking like everything was right but after i flashed recovery and rebooted my screen just went black. It looks like a brick but pc responds when i plug it in with usb. When i try to send any commands with adb it just says no devices/emulators found. Is there any way to fix this or it's hard brick?
I also attached logs from cmd. As for now I'm waiting for the battery to die slowly and maybe then something will happen.
Update:
DO NOT USE THIS SITE
Twrp was legit but something encrypted all my files. Thanks to twrp working i managed to wipe all data and it restored to firmware.
Hi
The phone after waiting actually "turned off" and i managed to get it to fastboot after plugging usb in and holding the volume down button. Tried to find my device with adb(adb devices command) and it says it found nothing.
SwitchOF said:
Hi
The phone after waiting actually "turned off" and i managed to get it to fastboot after plugging usb in and holding the volume down button. Tried to find my device with adb(adb devices command) and it says it found nothing.
Click to expand...
Click to collapse
I don't know what and why you want to use adb commands since you are in fastboot mode. Only fastboot commands work in fastboot mode.
Next time download twrp files from a more trustworthy source than the link from which you downloaded twrp, which is an old version of twrp anyway.
Moderator please close the thread
SwitchOF said:
Moderator please close the thread
Click to expand...
Click to collapse
As requested thread has been closed.
Regards
Oswald Boelcke