Hi all,
I'm trying to install Havoc OS on my P20 lite (2018 model - ANE-LX1 8.0.0.0.135(C432)). My current version of EMUI is 8.0. So I need to install a A version of ARM and NOT AB.
The system image is
Havoc-OS-v3.1-20200202-ARM64A-GSI.img
I have TWRP 3.4.0 installed and working. PS, I have also tried this via fastboot (fastboot flash system Havoc-OS-v3.1-20200202-ARM64A-GSI.img.xz) with the same results
Before flashing the ROM and my GAPPS file (open_gapps-arm64-10.0-nano-20200808.zip). Via TWRP I wipe Dalvik/Cache/System/Data
Then I installed the ROM via TWRP install and selected .img install, there are no errors and the screen output says it is installed correctly.
Then I flashed the GAPPS mentioned above. After that I wipe Dalvik/Cache again.
And reboot....nothing happens. The phone boots back up and goes straight to TWRP again. It's like the ROM is not being initialized at all.
Any help would be appreciated.
MayhemIam said:
Hi all,
I'm trying to install Havoc OS on my P20 lite (2018 model - ANE-LX1 8.0.0.0.135(C432)). My current version of EMUI is 8.0. So I need to install a A version of ARM and NOT AB.
The system image is
Havoc-OS-v3.1-20200202-ARM64A-GSI.img
I have TWRP 3.4.0 installed and working. PS, I have also tried this via fastboot (fastboot flash system Havoc-OS-v3.1-20200202-ARM64A-GSI.img.xz) with the same results
Before flashing the ROM and my GAPPS file (open_gapps-arm64-10.0-nano-20200808.zip). Via TWRP I wipe Dalvik/Cache/System/Data
Then I installed the ROM via TWRP install and selected .img install, there are no errors and the screen output says it is installed correctly.
Then I flashed the GAPPS mentioned above. After that I wipe Dalvik/Cache again.
And reboot....nothing happens. The phone boots back up and goes straight to TWRP again. It's like the ROM is not being initialized at all.
Any help would be appreciated.
Click to expand...
Click to collapse
Hi,
1. On Oreo use this TWRP
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
2. You have to extract system.img (cca 1,2GB) from .xz package (unpack it on PC), then transfer it to SD .
Reboot to the TWRP > Wipe > Format Data > go back > Wipe > Advanced > Dalvik/Cache/System/Data > go back > flash system.img
Go back > Reboot> Recovery and do factory reset from Stock recovery (se the note bellow!)
P.S.: it's recommended install TWRP over eRecovery:
Copy downloaded TWRP file to the SD card, and also copy to card Stock ramdisk_recovery , download here: (for EMUI 8 only! )
https://mega.nz/#!04dG0JBb!hEgTk6DMKVDffttHiXGqa_YR_zG5UYwTMEi41KTkZi8
Since A8 and above you can not install TWRP over eRecovery from fastboot, follow instructions:
- install TWRP from fastboot , reboot to TWRP, select install image, and flash TWRP over eRecovery, go back, find recovery_ramdisk330 and flash it over recovery. Reboot system. After the boot screen appears in the recovery with the inscription "Your device is booting now ..." press and hold Volume Up
for 3 sec, device will boot to TWRP.
-Alf- said:
Hi,
1. On Oreo use this TWRP
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
2. You have to extract system.img (cca 1,2GB) from .xz package (unpack it on PC), then transfer it to SD .
Reboot to the TWRP > Wipe > Format Data > go back > Wipe > Advanced > Dalvik/Cache/System/Data > go back > flash system.img
Go back > Reboot> Recovery and do factory reset from Stock recovery (se the note bellow!)
P.S.: it's recommended install TWRP over eRecovery:
Copy downloaded TWRP file to the SD card, and also copy to card Stock ramdisk_recovery , download here: (for EMUI 8 only! )
https://mega.nz/#!04dG0JBb!hEgTk6DMKVDffttHiXGqa_YR_zG5UYwTMEi41KTkZi8
Since A8 and above you can not install TWRP over eRecovery from fastboot, follow instructions:
- install TWRP from fastboot , reboot to TWRP, select install image, and flash TWRP over eRecovery, go back, find recovery_ramdisk330 and flash it over recovery. Reboot system. After the boot screen appears in the recovery with the inscription "Your device is booting now ..." press and hold Volume Up
for 3 sec, device will boot to TWRP.
Click to expand...
Click to collapse
Hi Alf my man
So I am having a bit of trouble with your instructions. I am very sure it is my own fault! I just want to clarify the steps please. I have downloaded the 2 provided files you gave in the link.
1
Install TWRP via
"fastboot flash recovery_ramdisk TWRP-oreo-smart.img"
2
Boot into newly flashed TWRP and flash the 2 files again as specified
"....flash TWRP over eRecovery, go back, find recovery_ramdisk330 and flash it over recovery...."
3
Reboot after step 2 and go into TWRP again and perform the system.img install as per instructions via TWRP
"Reboot to the TWRP > Wipe > Format Data > go back > Wipe > Advanced > Dalvik/Cache/System/Data > go back > flash system.img
Go back > Reboot> Recovery and do factory reset from Stock recovery"
I take it that I need to install my GAPPS package as well in this stage?
4
After factory reset from stock recovery the OS should boot and initiate...
Thanks again man for your help!
MayhemIam said:
Hi Alf my man
So I am having a bit of trouble with your instructions. I am very sure it is my own fault! I just want to clarify the steps please. I have downloaded the 2 provided files you gave in the link.
1
Install TWRP via
"fastboot flash recovery_ramdisk TWRP-oreo-smart.img"
2
Boot into newly flashed TWRP and flash the 2 files again as specified
"....flash TWRP over eRecovery, go back, find recovery_ramdisk330 and flash it over recovery...."
3
Reboot after step 2 and go into TWRP again and perform the system.img install as per instructions via TWRP
"Reboot to the TWRP > Wipe > Format Data > go back > Wipe > Advanced > Dalvik/Cache/System/Data > go back > flash system.img
Go back > Reboot> Recovery and do factory reset from Stock recovery"
I take it that I need to install my GAPPS package as well in this stage?
4
After factory reset from stock recovery the OS should boot and initiate...
Thanks again man for your help!
Click to expand...
Click to collapse
I have done as instructed yet there is am issue at the last step. I can boot into stock recovery but when I try and do a Factory Reset via the menu the reset only goes to 9% and gives a large orange/red exclamation mark.....so it did not finish. When I try and reboot and load the OS it goes into a boot loop and that is it.
MayhemIam said:
I have done as instructed yet there is am issue at the last step. I can boot into stock recovery but when I try and do a Factory Reset via the menu the reset only goes to 9% and gives a large orange/red exclamation mark.....so it did not finish. When I try and reboot and load the OS it goes into a boot loop and that is it.
Click to expand...
Click to collapse
Okay, reboot system. You can perform factory reset later (if needed).
---------- Post added at 19:17 ---------- Previous post was at 18:56 ----------
Please provide me the link where you downloaded Havoc OS
-Alf- said:
Okay, reboot system. You can perform factory reset later (if needed).
---------- Post added at 19:17 ---------- Previous post was at 18:56 ----------
Please provide me the link where you downloaded Havoc OS
Click to expand...
Click to collapse
No it's stuck on a bootloop Alf :crying:
MayhemIam said:
No it's stuck on a bootloop Alf :crying:
Click to expand...
Click to collapse
Don't panic! IMO it's time to clean your phone , download Service ROM
https://androidhost.ru/5NX
Unpack .zip package, find dload file and copy it to the SD card (without unpacking it!). Then turn off the phone and flash ROM using three button combo.
(instruction can be found in file ReleaseDoc).
Important: the process will erase all your data and will lock again the bootloader!
I will now try to install Havoc 3.1A and I will let you know, okay?
-Alf- said:
Don't panic! IMO it's time to clean your phone , download Service ROM
https://androidhost.ru/5NX
Unpack .zip package, find dload file and copy it to the SD card (without unpacking it!). Then turn off the phone and flash ROM using three button combo.
(instruction can be found in file ReleaseDoc).
Important: the process will erase all your data and will lock again the bootloader!
I will now try to install Havoc 3.1A and I will let you know, okay?
Click to expand...
Click to collapse
Well I can still dload back to my old EMUI 8.0 OS! I just did it again and it works. I can get back into my OS no probs. I have done this about 6 times today, lol. I really do not want to lock my bootloader again as it took me a long time to get it unlocked!
Thnx for the reply!
MayhemIam said:
Well I can still dload back to my old EMUI 8.0 OS! I just did it again and it works. I can get back into my OS no probs. I have done this about 6 times today, lol. I really do not want to lock my bootloader again as it took me a long time to get it unlocked!
Thnx for the reply!
Click to expand...
Click to collapse
Also just for me to understand. I have EMUI 8.0 running then I can't upgrade to a Android 9 Custom ROM?
MayhemIam said:
Also just for me to understand. I have EMUI 8.0 running then I can't upgrade to a Android 9 Custom ROM?
Click to expand...
Click to collapse
I'm not sure I fully understand your question, you cannot upgrade to A9 , you can flash Custom ROM based on A9 (which requires A8 OS).
Btw, I tried flash Havoc 3.1, 3.0, tried several TWRP, no luck. Flashed system.img from fastboot, nothing. It seems A-only version doesn't work on ANE. I have no idea what the problem is...
(hehe, R.I.P. English )
-Alf- said:
I'm not sure I fully understand your question, you cannot upgrade to A9 , you can flash Custom ROM based on A9 (which requires A8 OS).
Btw, I tried flash Havoc 3.1, 3.0, tried several TWRP, no luck. Flashed system.img from fastboot, nothing. It seems A-only version doesn't work on ANE. I have no idea what the problem is...
(hehe, R.I.P. English )
Click to expand...
Click to collapse
OK I can't upgrade to EMUI 9 but I can upgrade to a custom ROM which has Android 9 (through AB partition)?
"...you can flash Custom ROM based on A9 (which requires A8 OS)." Which means I can upgrade to any custom ROM which has Android 9 / 10?
What is the difference then between the following?
ARM64A
ARM64AB
-Alf- said:
Okay, reboot system. You can perform factory reset later (if needed).
---------- Post added at 19:17 ---------- Previous post was at 18:56 ----------
Please provide me the link where you downloaded Havoc OS
Click to expand...
Click to collapse
Oh snap man, I only saw the last part of your post now.
I tried the following ROMS.
Most of them was downloaded from SourceForge man.
Havoc-OS-v3.0-20191225-ARM64A-Unofficial.img.xz
Havoc-OS-v3.1-20200202-ARM64A-GSI.img
I have tried others as well but they were ARM64AB....
MayhemIam said:
OK I can't upgrade to EMUI 9 but I can upgrade to a custom ROM which has Android 9 (through AB partition)?
"...you can flash Custom ROM based on A9 (which requires A8 OS)." Which means I can upgrade to any custom ROM which has Android 9 / 10?
Click to expand...
Click to collapse
For example:
Pixel Experience, ROM for the Huawei P20 Lite
Contributors
DarkJoker360
Source Code: https://github.com/DarkJoker360
ROM OS Version: 9.0 Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8 unlocked bootloader & twrp
MayhemIam said:
OK I can't upgrade to EMUI 9 but I can upgrade to a custom ROM which has Android 9 (through AB partition)?
"...you can flash Custom ROM based on A9 (which requires A8 OS)." Which means I can upgrade to any custom ROM which has Android 9 / 10?
What is the difference then between the following?
ARM64A
ARM64AB
Click to expand...
Click to collapse
What is the difference then between the following?
ARM64A
ARM64AB
OK so the answer is
Use ARM64xA - when your phone is using Android 8.0 (EMUI 8.0)
Use ARM64xAB - when your phone is using Android 9 (EMUI 9.1)
-Alf- said:
For example:
Pixel Experience, ROM for the Huawei P20 Lite
Contributors
DarkJoker360
Source Code: https://github.com/DarkJoker360
ROM OS Version: 9.0 Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8 unlocked bootloader & twrp
Click to expand...
Click to collapse
Hi Alf,
I have abandoned ship to get HavocOS on my device
But I'm trying now the following AOSP Android 10 Q
https://www.getdroidtips.com/android-10-huawei-p20-lite/
I'm going to try and use this TWRP (twrp-3.4.0-0-anne.img)
Will let you know how it goes!
MayhemIam said:
Hi Alf,
I have abandoned ship to get HavocOS on my device
But I'm trying now the following AOSP Android 10 Q
https://www.getdroidtips.com/android-10-huawei-p20-lite/
I'm going to try and use this TWRP (twrp-3.4.0-0-anne.img)
Will let you know how it goes!
Click to expand...
Click to collapse
Getdroidtips? Really reliable source
I finally installed Havoc 3.8ab (latest version), I'm disappointed . No Music player, no Sound recorder (=no call recording) , no email client, Calendar etc. etc....
I think you should upgrade to EMUI 9.1 and try AB versions , hm?
-Alf- said:
Getdroidtips? Really reliable source
I finally installed Havoc 3.8ab (latest version), I'm disappointed . No Music player, no Sound recorder (=no call recording) , no email client, Calendar etc. etc....
I think you should upgrade to EMUI 9.1 and try AB versions , hm?
Click to expand...
Click to collapse
I would have really like to test an earlier version then which did not have all those missing features! It seemed to me that customization was very good on the ROM....
facepalm on Get Droid Tips....because the only tip I got from them is more than 12 hrs of trying to implement their crappy advice!
Ok I will upgrade to EMUI 9 then Alf.
Thanks for all the advice man and flashing along side me
Try Havoc 2.9 for Oreo , the Rom is just perfect . (own experience, tested on 8.0.0.126 )
INSTALL ON CLEAN OS (if your current OS is Custom ROM, flash stock ROM).
Download and unpack on your PC Havoc 2.9 arm64a:
https://sourceforge.net/projects/ha...90914-phhgsi_arm64_a-Official.img.xz/download
Flash extracted Havoc.img from fastboot using command
fastboot flash system (file name).img
Before booting up the ROM, you will need to perform a factory reset in stock recovery!!!
Reboot system.
In the Phh-Treble Settings-Huawei features, select fast charge 4000mA and Enable blurry UI workaround
If you want to install GAPPs or Magic (Magic v20.3 works without problems) , use TWRP by "ascuccio" (own experience), download link:
https://mega.nz/#!EsdTgYqZ!2QX9wgAhA653Dp2MkDTLPHa3tmFdNqmC5CDDHB-7f5Y
Screenshots:
https://mega.nz/#!1tlnlSyS!3SdAkZwf9miFVMkEXiq5Ypy3PcTOhuuohywk1ta-eXI
MayhemIam said:
Hi all,
I'm trying to install Havoc OS on my P20 lite (2018 model - ANE-LX1 8.0.0.0.135(C432)). My current version of EMUI is 8.0. So I need to install a A version of ARM and NOT AB.
The system image is
Havoc-OS-v3.1-20200202-ARM64A-GSI.img
I have TWRP 3.4.0 installed and working. PS, I have also tried this via fastboot (fastboot flash system Havoc-OS-v3.1-20200202-ARM64A-GSI.img.xz) with the same results
Before flashing the ROM and my GAPPS file (open_gapps-arm64-10.0-nano-20200808.zip). Via TWRP I wipe Dalvik/Cache/System/Data
Then I installed the ROM via TWRP install and selected .img install, there are no errors and the screen output says it is installed correctly.
Then I flashed the GAPPS mentioned above. After that I wipe Dalvik/Cache again.
And reboot....nothing happens. The phone boots back up and goes straight to TWRP again. It's like the ROM is not being initialized at all.
Any help would be appreciated.
Click to expand...
Click to collapse
You have tried to decrypt the data?
https://forum.xda-developers.com/honor-7x/development/mod-decrypt-data-emui-8-t3765403
Dego02 said:
You have tried to decrypt the data
Click to expand...
Click to collapse
No comment...
Related
Hi,
I'm trying to migrate from CM 14.1 to LineageOS 14.1 official nightly on a OnePlus 3.
Here is what I currently have on the phone:
TWRP version 3.0.3-0
CM 14.1 nightly: cm-14.1-20161216-NIGHTLY-oneplus3.zip
OpenGapps: open_gapps-arm64-7.1-nano-20170211.zip
I'm doing the following:
1.) Reboot to recovery (to TWRP).
2.) Wipe everything (cache, system, data, Dalvik cache).
3.) Select in TWRP: Advanced -> ADB Sideload
4.) From computer: adb sideload lineage-14.1-20170207-nightly-oneplus3-signed.zip
5.) Here's what TWRP complains about:
...
Installing zip file '/sideload/package.zip'
Comparing TZ version TZ.BF.4.0.1-76917 to TZ.BF.4.0.1-00287.2
assert failed: oppo.verify_trustzone("TZ.BF.4.0.1-76917") == "1"
Updater process ended with ERROR: 7
Any clues on why that error shows up?
Thanks!
Has anybody else encountered this problem?
Can anyone help me please?
Hi,
Had this problem migrating from dev cm13->los14.1 this morning.
Seems like your firmware is not to the correct version. Install OxygenOS 4.0.2 (maybe 4.0.3 is working) first, maybe you'll need to flash the OxygenOS recovery first.
Then, boot at least once to the system (might be slow), then start again the process to install Lineage
Good luck!
You need to do following in the below order.
1. Flash official twrp 3.0.4 from fastboot command
2. Format complete internal storage in twrp, this will delete all user data, so make a backup.
3. Transfer all below files to internal storage in MTP mode in twrp.
4. Flash OxygenOS 4.0.3 firmware and modem zip
5. Flash lineageos 1402 nightly
6. Flash opengapps arm64 of ur choice
7. Boot and enjoy
nitz2889 said:
You need to do following in the below order.
1. Flash official twrp 3.0.4 from fastboot command
2. Format complete internal storage in twrp, this will delete all user data, so make a backup.
3. Transfer all below files to internal storage in MTP mode in twrp.
4. Flash OxygenOS 4.0.3 firmware and modem zip
5. Flash lineageos 1402 nightly
6. Flash opengapps arm64 of ur choice
7. Boot and enjoy
Click to expand...
Click to collapse
I could only find TWRP 3.0.3-0 on the official TWRP site: https://dl.twrp.me/oneplus3/
Is there somewhere else where I could get 3.0.4 from?
Also, where can I get modem.zip from?
Thank you!
Use twrp from, https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391.
And firmware and modem from, https://www.androidfilehost.com/?fid=673368273298930071.
Hit thanks if it helps
nitz2889 said:
Use twrp from, https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391.
And firmware and modem from, https://www.androidfilehost.com/?fid=673368273298930071.
Hit thanks if it helps
Click to expand...
Click to collapse
Thanks! I'll give it a try and come back with a reply on how it went.
Worked just fine. Thank you again!
MatrixInside said:
Worked just fine. Thank you again!
Click to expand...
Click to collapse
Welcome mate. Can u please tell me if slow motion working in lineageos default snap camera??
Mine force closes the camera app.
Hello,
Since MIUI 10.3.1.0 (PEIMIXM) was launched, I tried to update my device. After the update, when the smartphone rebooted it kept stuck in Mi logo sreen (Android loading wasn't also appearing). I tried to use MiFlash to reflash the ROM and the same happended.
Thinking it was a random problem of MIUI I decided to move to Pixel Experience because I had used it before and I liked. In the same day of MIUI 10.3.1.0 (PEIMIXM) launch, Pixel Experience also launched a new whyred version (in the beggining of June, i think).
I did what was needed to successfully install the ROM according to the dev's thread:
-I downloaded all the needed files (MIUI 10.3.1.0 PEIMIXM firmware, Pixel Experience ROM, recommended modified TWRP version of the developer);
-Initially, I installed TWRP via fastboot mode;
-I flashed the firmware;
-I wiped the partitions Cache Dalvik / ART, System, Cache, Data, vendor;
-I flashed Pixel Experience ROM;
-I wiped Internal Storage;
-I rebooted the device.
After those steps, I couldn't get access to my "homescreen". Basically, my phone stays stuck at the Mi logo screen. And nothing happens.
Considering it could be a recovery problem, I tried to use Pitch Black Recovery (the latest version available for whyred) that supports Oreo and Pie. I used TWRP to flash this one, and after that I made all the steps above again and the same happened.
I'm now only available to flash MIUI (if it is Android 8.1). I can only flash Pixel experience versions that were released before the MIUI Pie stable for this device.
I really appreciate if you could help me!
Hi,
Copy:
- the full name of the firmware file you used
-The full name of the rom file you use
-The full name of the recovery file you use/intend to use.
The name and version of current recovery installed.
Cheers,
htchd2sucks said:
Hi,
Copy:
- the full name of the firmware file you used
-The full name of the rom file you use
-The full name of the recovery file you use/intend to use.
The name and version of current recovery installed.
Cheers,
Click to expand...
Click to collapse
Firmware file: fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0
ROM: PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL
Recovery I wanna use: PitchBlack-whyred-2.9.0-20190501-1030-OFFICIAL
Recovery I have installed to install the previous one: twrp-3.3.1-0-whyred.img
floater3 said:
Firmware file: fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d2c9f2aa_9.0
ROM: PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL
Recovery I wanna use: PitchBlack-whyred-2.9.0-20190501-1030-OFFICIAL
Recovery I have installed to install the previous one: twrp-3.3.1-0-whyred.img
Click to expand...
Click to collapse
You have a problem because of the firmware (likely).
The order was supposed to be something like this, from an OREO recovery and OREO FW:
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom (PixelExperience_whyred-9.0-20190604-1615-OFFICIAL.zip at time of writing). Do not reboot
Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip. It will automatically reboot into recovery again.
I would:
-Flash the orange fox recovery from here (OrangeFox-R10.0_1-Stable-whyred.zip):
https://forum.xda-developers.com/re...ment/twrp-orangefox-recovery-project-t3837547
It's supposed to support both oreo and pie. It should reboot in recovery again after flashing.
-Flash the FW (fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d 2c9f2aa_9.0.zip), hit reboot to recovery
-Flash your PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL.
Reboot into system and check.
If not, I would try reflashing the recovery with a proper OREO firmware and then
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom. Do not reboot
Flash Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip (pie) or V10 which is supposed to be oreo/pie. It will automatically reboot into recovery again.
Based on whatever mess it is now, you might have to do some wipes, try first the above then report.
htchd2sucks said:
You have a problem because of the firmware (likely).
The order was supposed to be something like this, from an OREO recovery and OREO FW:
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom (PixelExperience_whyred-9.0-20190604-1615-OFFICIAL.zip at time of writing). Do not reboot
Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip. It will automatically reboot into recovery again.
I would:
-Flash the orange fox recovery from here (OrangeFox-R10.0_1-Stable-whyred.zip):
https://forum.xda-developers.com/re...ment/twrp-orangefox-recovery-project-t3837547
It's supposed to support both oreo and pie. It should reboot in recovery again after flashing.
-Flash the FW (fw_whyred_miui_HMNote5Global_V10.3.1.0.PEIMIXM_d4d 2c9f2aa_9.0.zip), hit reboot to recovery
-Flash your PixelExperience_caf_whyred-9.0-20190709-1819-OFFICIAL.
Reboot into system and check.
If not, I would try reflashing the recovery with a proper OREO firmware and then
In the recovery flash Pie firmware MIUI V10.3.1.0.PEIMIXM first and hit reboot to recovery. (so that firmware is really updated)
Now flash latest PIE rom. Do not reboot
Flash Flash OrangeFox-R9.0-2-whyred-MIUI-Pie.zip (pie) or V10 which is supposed to be oreo/pie. It will automatically reboot into recovery again.
Based on whatever mess it is now, you might have to do some wipes, try first the above then report.
Click to expand...
Click to collapse
Hummm. it's happening a suspect thing! I made all the steps above, and I'm now flashing the ROM itself, and recovery is stuck at "Unpacking the original boot image".
floater3 said:
Hummm. it's happening a suspect thing! I made all the steps above, and I'm now flashing the ROM itself, and recovery is stuck at "Unpacking the original boot image".
Click to expand...
Click to collapse
Wait a bit maybe.
Just to make sure, verify the checksum of your downloaded files or redownload them again and compare the size. Just to be sure you have the proper files and they are completed.
htchd2sucks said:
Wait a bit maybe.
Just to make sure, verify the checksum of your downloaded files or redownload them again and compare the size. Just to be sure you have the proper files and they are completed.
Click to expand...
Click to collapse
It's everything right with files.
I'm still waiting... And it's strange because it's stuck on "Unpacking boot image" and the problem I was facing was associated with booting the system.
floater3 said:
It's everything right with files.
I'm still waiting... And it's strange because it's stuck on "Unpacking boot image" and the problem I was facing was associated with booting the system.
Click to expand...
Click to collapse
Can you check /tmp/recovery.log? ideally copying that in a pastebin.
We should look into doing the proper cleaning from recovery as well, (wipe, advanced wipes).
Do you have any data to save or can you clean flash all without problem?
htchd2sucks said:
Can you check /tmp/recovery.log? ideally copying that in a pastebin.
We should look into doing the proper cleaning from recovery as well, (wipe, advanced wipes).
Do you have any data to save or can you clean flash all without problem?
Click to expand...
Click to collapse
I can flash all. The need files are on the SD card. How do I check /tmp/recovery.log?
floater3 said:
I can flash all. The need files are on the SD card. How do I check /tmp/recovery.log?
Click to expand...
Click to collapse
You're supposed to adb pull /tmp/recovery.log.
Might not be needed, if you can simply do a wipe/advanced wipe, and a format of /data.
Note: it might not be necessary and you will delete things, it's just " the fastest way".
then you have to go through the flashing, again, I would even redo the fw as described earlier.
htchd2sucks said:
You're supposed to adb pull /tmp/recovery.log.
Might not be needed, if you can simply do a wipe/advanced wipe, and a format of /data.
Note: it might not be necessary and you will delete things, it's just " the fastest way".
then you have to go through the flashing, again, I would even redo the fw as described earlier.
Click to expand...
Click to collapse
I could flash the ROM but, still in bootloop... But it's curious! If I let my smartphone turned off for 10-15 minutes and then turn it on, Pixel Experience works and boots successfully but after some minutes of using, starts crashing, and reboots, again in bootloop
floater3 said:
I could flash the ROM but, still in bootloop... But it's curious! If I let my smartphone turned off for 10-15 minutes and then turn it on, Pixel Experience works and boots successfully but after some minutes of using, starts crashing, and reboots, again in bootloop
Click to expand...
Click to collapse
Hm it is indeed strange, as if something is corrupted...
What's the status now?
Any changes?
htchd2sucks said:
Hm it is indeed strange, as if something is corrupted...
What's the status now?
Any changes?
Click to expand...
Click to collapse
Still the same.... I tried again, with other recoveries.... Always the same thing! Bootloop.
But if I let it turned off for some time I can boot it (but after some minutes it automatically restarts and gets in bootloop again )
floater3 said:
Still the same.... I tried again, with other recoveries.... Always the same thing! Bootloop.
But if I let it turned off for some time I can boot it (but after some minutes it automatically restarts and gets in bootloop again )
Click to expand...
Click to collapse
It's clearly not related to recovery, at least, not directly.
-Check what "wipes" you have done, and ideally do all of them + format data (you can always reencrypt later). Then, reboot, and redo the flashing of everything.
-Another option would be to flash with "miflash" which I think will also restore some boot things. In that scenario, you are on your own because I don't know about ARB in your case and all potential issues.
I can only say that I did a "miflash" when I used to have ARBv3, and it went fine (I had to redo the recovery, etc... after).
Hi,
today I tried to install TWRP.
After exiting TWRP with reboot button, my phone reboots but is stuck on Mi logo (no Android logo in the bottom).
I have access to TWRP and to fastboot, but due to the fact that I'm really new to this, I don't know what I have to do.
TWRP was "twrp-3.0.2-2-kenzo.img"
Redmi Note 3 Pro (KATE)
In another thread I read, that I should use twrp 3.3.1 official, unfortunately I don't know if its possible to flash another twrp without having access to the phone -_-
Can somebody help me?
(I wanted to flash Lineage OS to have a newer Android version with actual Android security patch level)
InfectFTW said:
Hi,
today I tried to install TWRP.
After exiting TWRP with reboot button, my phone reboots but is stuck on Mi logo (no Android logo in the bottom).
I have access to TWRP and to fastboot, but due to the fact that I'm really new to this, I don't know what I have to do.
TWRP was "twrp-3.0.2-2-kenzo.img"
Redmi Note 3 Pro (KATE)
In another thread I read, that I should use twrp 3.3.1 official, unfortunately I don't know if its possible to flash another twrp without having access to the phone -_-
Can somebody help me?
(I wanted to flash Lineage OS to have a newer Android version with actual Android security patch level)
Click to expand...
Click to collapse
U using old. Use latest 3.1.1 latest twrp from official twrp site.
Put favourite rom and gapps in external sd card
Format data
Wipe data
Flash rom
Flash gapps
Reboot.
Black_Stark said:
U using old. Use latest 3.1.1 latest twrp from official twrp site.
Put favourite rom and gapps in external sd card
Format data
Wipe data
Flash rom
Flash gapps
Reboot.
Click to expand...
Click to collapse
Thank you for your answer, but how can I get the new twrp on the phone?
Last time I did it via my pc and command terminal, but I think this won't work now because I can't "see" the phone in Windows
InfectFTW said:
Thank you for your answer, but how can I get the new twrp on the phone?
Last time I did it via my pc and command terminal, but I think this won't work now because I can't "see" the phone in Windows
Click to expand...
Click to collapse
Download this latest twrp img. It works for both kenzo and kate.
https://dl.twrp.me/kenzo/twrp-3.3.1-0-kenzo.img
Go to ur current twrp.
Click install and Select image
Select image file
It will ask u where to install
Select "recovery" partition
Swipe to Install
Reboot to recovery
Now u have new latest twrp
.
---------- Post added at 02:16 PM ---------- Previous post was at 02:01 PM ----------
Download this Aex Pie Rom
https://drive.google.com/open?id=1gl4S9tMZP0QR8EgrtoVs810LUTt2gwJp
It comes with google playstore. So no need to install gapps. Separately.
Download and copy this Pie rom zip in external sd card.
Now boot in twrp.
First go to wipe.
Click format data
Type YES to format
It will decrypt ur data partition and format data partition.
Now go to wipe - advanced wipe
Select all system, data, cache, dalvik, internal sd and wipe. But Do not select microsd card. :laugh:
Now go to install option
Browse to micro sd storage and select Aex pie rom zip
Swipe to install pie rom zip.
Wait patiently.
And reboot it will take 3 to 4 mins to boot pie rom.
Black_Stark said:
Download this latest twrp img. It works for both kenzo and kate.
Go to ur current twrp
Click to expand...
Click to collapse
But how can I access my current TWRP?
InfectFTW said:
But how can I access my current TWRP?
Click to expand...
Click to collapse
U said u already have access to twrp.
To boot into twrp .
Press volume up and power together.
Press and Hold both buttons together. When phone vibrates immediately release both button with first vibration.
Phone will boot in twrp.
Black_Stark said:
U said u already have access to twrp.
To boot into twrp .
Press volume up and power together.
Press and Hold both buttons together. When phone vibrates immediately release both button with first vibration.
Phone will boot in twrp.
Click to expand...
Click to collapse
Sorry, it was a wrong information of my side.
With volume up and Power I boot in Mi flash.
InfectFTW said:
Sorry, it was a wrong information of my side.
With volume up and Power I boot in Mi flash.
Click to expand...
Click to collapse
If u cant boot into twrp. Then u have flash fastboot kate rom using Pc.
But u need to confirm if u have kenzo or kate.
Kenzo is rn3 pro
http://bigota.d.miui.com/V10.2.1.0....XM_20190114.0000.00_6.0_global_8a48e54fe3.tgz
Kate is rn3 special edition.
http://bigota.d.miui.com/9.3.28/kate_global_images_9.3.28_20190328.0000.00_6.0_global_7f425d08d9.tgz
Black_Stark said:
If u cant boot into twrp. Then u have flash fastboot kate rom using Pc.
But u need to confirm if u have kenzo or kate.
Kenzo is rn3 pro
http://bigota.d.miui.com/V10.2.1.0....XM_20190114.0000.00_6.0_global_8a48e54fe3.tgz
Kate is rn3 special edition.
http://bigota.d.miui.com/9.3.28/kate_global_images_9.3.28_20190328.0000.00_6.0_global_7f425d08d9.tgz
Click to expand...
Click to collapse
Okay I just checked it.
Volume Up + Power --> MI-Recovery 3.0
Volume Down + Power --> Fastboot
I have definitively Redmi Note 3 KATE.
Can you tell me how to flash the image I just downloaded (the KATE version)?
InfectFTW said:
Okay I just checked it.
Volume Up + Power --> MI-Recovery 3.0
Volume Down + Power --> Fastboot
I have definitively Redmi Note 3 KATE.
Can you tell me how to flash the image I just downloaded (the KATE version)?
Click to expand...
Click to collapse
First check if ur phone is unlocked or relocked.
Connect to pc.
Put phone in fastboot mode.
Type this commamd
fastboot oem device-info
If unlocked = true then ur phone is unlocked
If unlocked = false then its relocked.
Check it first.
---------- Post added at 06:52 PM ---------- Previous post was at 06:22 PM ----------
Use this guide.
This will give link and procedure to flash fastboot rom.
U already downloaded fastboot firmware.
U only need to download miflashing tool.
https://xiaomiflashtool.com/tutorial/use-xiaomi-flash-tool
Extract the fastboot rom zip on pc.
Put phone in fastboot mode and connect to pc.
Run miflash tool. U must have win 64bit pc.
In miflash tool u Browse and select fastboot extracted main folder.
Select "clean all" option which u see in bottom corner of miflash tool.
Now click flash.
And wait for flashing process to finish.
Then disconnect cable and power ur device to boot.
@Black_Stark
wow, good news, it worked
Thank you very much!!!
I have now MIUI 10 Global 9.3.28 Beta on my phone with Android 6.0.1 MMB29M and Android security patch level 2018-07-01
I want to give this smartphone my grandmother, but I think it would be better, if there would be a newer Android security patch level.
That's why I wanted to install Lineage OS 17 (with this youtube video: https://www.youtube.com/watch?v=diC5UfAWcEU)
What do you say about that, and which OS would you prefer to get a newer Android security patch level?
InfectFTW said:
@Black_Stark
wow, good news, it worked
Thank you very much!!!
I have now MIUI 10 Global 9.3.28 Beta on my phone with Android 6.0.1 MMB29M and Android security patch level 2018-07-01
I want to give this smartphone my grandmother, but I think it would be better, if there would be a newer Android security patch level.
That's why I wanted to install Lineage OS 17 (with this youtube video:
)
What do you say about that, and which OS would you prefer to get a newer Android security patch level?
Click to expand...
Click to collapse
Lineage sucks.
If u giving to grandma then stay on miui.
Black_Stark said:
Lineage sucks.
If u giving to grandma then stay on miui.
Click to expand...
Click to collapse
No worries about Android Security Patch Level from 2018?
Hi @Black_Stark,
I want to flash the new official MiUI version V10.2.1.0.MHRMIXM (https://*************/download/redmi-note-3-se/)
Do I need the fastboot or recovery ROM?
How should I flash it?
First install newest TWRP 3.3.1.0 (https://eu.dl.twrp.me/kenzo/) and then flash the new image via TWRP?
InfectFTW said:
Hi @Black_Stark,
I want to flash the new official MiUI version V10.2.1.0.MHRMIXM (https://*************/download/redmi-note-3-se/)
Do I need the fastboot or recovery ROM?
How should I flash it?
First install newest TWRP 3.3.1.0 (https://eu.dl.twrp.me/kenzo/) and then flash the new image via TWRP?
Click to expand...
Click to collapse
There is no 10.2 version for kate.
U already are on latest version.
This might help you after realizing that you want to install custom ROM again after upgrading to android 11 MIUI but you cannot install android 10 or 11 based ROM and stuck with either boot loop or android rescue party.
WARNING: This might wipe every writable partition. Charge your phone at least 20% or more to prevent from destroying these partitions.
Instructions:
1. Download firmware from here
2. Download full ROM (either recovery or fastboot) from here
3. Save the firmware zip file it in either internal storage or sdcard. Reboot to TWRP afterwards
4. Tap install and find the zip file in your storage and install. Wait for a couple of seconds to get done.
To install full ROM
Recovery
1. After installing firmware from recovery mode, don't reboot. If you reboot the system it will fail to boot. Boot to fastboot if you fail this step and flash a recovery image. Proceed with next step.
2. Install full ROM flashable zip from sdcard or internal storage.
3. Format /data. Reboot.
Using fastboot
1. Boot from fastboot mode
2. Extract full ROM fastboot zip file.
3. Open miflash and locate the fastboot folder.
4. Choose flash_all. Click start.
5. The phone reboots itself. Boot to recovery mode and wipe data.
All done. The phone is now downgraded from android 11 back to android 10.
Note: I got 2 anti triggered when attempting to downgrade the phone using recovery and fastboot without installing firmware zip file first. RIP me I guess I voided my warranty anyways so doesnt matter as I already applied some insurance for my device.
TL;DR: Installed Recovery will get erased as I mentioned in WARNING. Please don't skip every step.
Edit: since it made confusion, I split steps for recovery and fastboot mode.
Has anyone tried this procedure?
Im on 12.0.6.0(EU). Bootloader locked (wait 3days) so no TWRP. Want downgrade to 12.0.8.0(EU) and flash Pixelexperience ROM.
It will work?
I'm a bit confusing... Links inserted in first 2 points seem to be the same link. So what I've to download exactly?
I'm on 12.0.7.0 Android 10 but I'm curious to try 12.0.6.0 Android 11 stable beta released some days ago...
PYCON said:
I'm a bit confusing... Links inserted in first 2 points seem to be the same link. So what I've to download exactly?
I'm on 12.0.7.0 Android 10 but I'm curious to try 12.0.6.0 Android 11 stable beta released some days ago...
Click to expand...
Click to collapse
Its not the same. First one is cca. 80MB of size while full rom is 2.4GB for recovery and 4.4GB for fastboot.
I did this method yesterday and its working. No problems whatsoever.
The only thing i would add is you need both versions of rom - recovery and fastboot. Recovery when you flash for the first time in recovery and fastboot when you flash with Mi flash.
And my advice is, android 11 miui is really bad. Its not finished, it stutters a lot, u can't use third party launchers with gesture navigation (at least in my case, Nova lanucher), performance is bad.
Not worth any time.
Steelrock said:
Its not the same. First one is cca. 80MB of size while full rom is 2.4GB for recovery and 4.4GB for fastboot.
I did this method yesterday and its working. No problems whatsoever.
The only thing i would add is you need both versions of rom - recovery and fastboot. Recovery when you flash for the first time in recovery and fastboot when you flash with Mi flash.
And my advice is, android 11 miui is really bad. Its not finished, it stutters a lot, u can't use third party launchers with gesture navigation (at least in my case, Nova lanucher), performance is bad.
Not worth any time.
Click to expand...
Click to collapse
Ok, ok, good to know. I'm just curious... I'll remain with A10 till when A11 will be good enough to be used as a daily driver
Hi. Does this method requires unlocked bootloader? Thanks
hi. this method not working for me !
*phone is unlocked !
ar-rabbiar said:
hi. this method not working for me !
*phone is unlocked !
Click to expand...
Click to collapse
This error is normal because ur phone is unlocked....but the phone should reboot normal in the new ROM. It did not happen this way?
Alin45 said:
This error is normal because ur phone is unlocked....but the phone should reboot normal in the new ROM. It did not happen this way?
Click to expand...
Click to collapse
reboot with bootloop and again. and just miui 12 a11 or rom with selinux permissive working for flash.
The same in here. Bootloop, bootloop....
But if flash the a11 rom it works.
ar-rabbiar said:
hi. this method not working for me !
*phone is unlocked !
Click to expand...
Click to collapse
did you try to flash firmware file from twrp recovery first? also that error means that a checkpoint failed which you need to disable or remove in configuration settings.
tourofeio said:
The same in here. Bootloop, bootloop....
But if flash the a11 rom it works.
Click to expand...
Click to collapse
did you tried recovery or fastboot flashing? and did you installed firmware first before installing full rom?
endva3 said:
Has anyone tried this procedure?
Im on 12.0.6.0(EU). Bootloader locked (wait 3days) so no TWRP. Want downgrade to 12.0.8.0(EU) and flash Pixelexperience ROM.
It will work?
Click to expand...
Click to collapse
i only tried recovery method and it works fine after days of trying. 12.0.6 android 11 is still buggy and miui needs to fix it a lot. most of apps are not well optimized for this flavor.
Today unlocked bootloader. Flashing 12.0.8.0 (i have 12.0.6.0 A11).
Everything work perfect. No bootloop, bootloader relock and works fine
People are probaly skipping some steps.
1. Download Firmware small size files
2. Download full Firmware, both - fastboot and recovery (put it on SD card, small and recovery)
3. Install Twrp or Orangefox recovery (download it from somewhere)
4. Enter into recovery and install small firmware FIRST, dont reboot, install big firmware (recovery version) SECOND
5. do not reboot
6. format data
7. Now reboot into fastboot
8. Extract fastboot firmware zip into new folder on desktop
9. Start Mi flash, select that folder where u extracted files and tick "clean only" on the bottom of the Mi flash if u want to leave bootloader unlocked and from drop down menu near that pick "flash_all.bat".
Thats how i did it.
Steelrock said:
People are probaly skipping some steps.
1. Download Firmware small size files
2. Download full Firmware, both - fastboot and recovery (put it on SD card, small and recovery)
3. Install Twrp or Orangefox recovery (download it from somewhere)
4. Enter into recovery and install small firmware FIRST, dont reboot, install big firmware (recovery version) SECOND
5. do not reboot
6. format data
7. Now reboot into fastboot
8. Extract fastboot firmware zip into new folder on desktop
9. Start Mi flash, select that folder where u extracted files and tick "clean only" on the bottom of the Mi flash if u want to leave bootloader unlocked and from drop down menu near that pick "flash_all.bat".
Thats how i did it.
Click to expand...
Click to collapse
i did the same, but looking to partitions of system, product and vendor, i understand that flashing the files via recovery and fastboot they dont write in that partitions.
looks like the partitions are read only. thanks
I try to flash a custom rom like arrows os via recovery , the rom shows the boot logo of arrows rom, and then bootloop.
tourofeio said:
I try to flash a custom rom like arrows os via recovery , the rom shows the boot logo of arrows rom, and then bootloop.
Click to expand...
Click to collapse
Most probable, u forgot to do a Format data (yes) before reboot to system.
endva3 said:
Today unlocked bootloader. Flashing 12.0.8.0 (i have 12.0.6.0 A11).
Everything work perfect. No bootloop, bootloader relock and works fine
Click to expand...
Click to collapse
Did you flash it from the built-in recovery or with MiFlash? (My 167 hour waiting period ends tomorrow)
Solved people. change the version of the Mi Flash.
Hello all,
It's a long time that's i haven't post a thread here but i have a question.I have a Poco with MIUI Global 9.6 Stable (9.6.25.0) for ROM with a Android Version 8.1.0 OPM 171019.011 with root acces, unlocking bootloader and TWRP 3.3.0-0 installed.
I would upgrade my phone to something "newer" (A ROM with Android 12 if possible) and conserv the root access and my apps.
I have read that now ,we should have 3 files to do that (firmware,system and vendor) to make a wipe and install new ROM with TWRP.
So my question:
-Is it possible to upgrade Android 8.1.0 to Android 12 witn a new ROM? (i have read something about kernel in Android12 but haven't understand all)
-Have i missed some steps or just download files,boot TWRP,wipe and install newer ROM+firmware and vendor appropriate is good?
-Which ROM do you recommend?
Thanks for the previous answers.
devil1 said:
Hello all,
It's a long time that's i haven't post a thread here but i have a question.I have a Poco with MIUI Global 9.6 Stable (9.6.25.0) for ROM with a Android Version 8.1.0 OPM 171019.011 with root acces, unlocking bootloader and TWRP 3.3.0-0 installed.
I would upgrade my phone to something "newer" (A ROM with Android 12 if possible) and conserv the root access and my apps.
I have read that now ,we should have 3 files to do that (firmware,system and vendor) to make a wipe and install new ROM with TWRP.
So my question:
-Is it possible to upgrade Android 8.1.0 to Android 12 witn a new ROM? (i have read something about kernel in Android12 but haven't understand all)
-Have i missed some steps or just download files,boot TWRP,wipe and install newer ROM+firmware and vendor appropriate is good?
-Which ROM do you recommend?
Thanks for the previous answers.
Click to expand...
Click to collapse
It's not possible to switch from stock ROM to custom without doing clean install. You will have to root again.
First update to latest Official Stock ROM, then take backup of your files to your PC or to SDCard (if you have one) , flash to latest Official TWRP and check my POCO F1 Ultimate Collection & Guides. You can find everything there. I have awarded recommended ROMs in my collection.
Feel free to ask if you have any question regarding the guides.
Thanks for the answer.I have begin to read your guides.
If i understand good,it's not possible to conserv my root,unlock bootloader and twrp when i upgrade to android 12? Automaticaly i should root again my phone and restore with titanium backup my files,contact,....?
devil1 said:
Thanks for the answer.I have begin to read your guides.
If i understand good,it's not possible to conserv my root,unlock bootloader and twrp when i upgrade to android 12? Automaticaly i should root again my phone and restore with titanium backup my files,contact,....?
Click to expand...
Click to collapse
First you need to take backup of your files to PC or External SDCard.
Then you should update to latest version of MIUI via OTA if it's possible or via TWRP (you can use the stock recovery rom to do it via twrp). (You can also use my guides for clean install stock rom)
Then you should unlock your bootloader if it's not already unlocked.
Then flash latest Official TWRP.
Then flash latest firmware (not vendor) just to make sure you are on the latest. (You should be on latest firmware after updating to the latest MIUI version)
Then Wipe everything + format data according to my guides and flash the ROM you want. If you choose A12 Pixel Experience or crDroid keep in mind that these ROMs use their own recovery because these are encrypted by default ROMs and TWRP can't handle the decryption of A12 encrypted ROMs yet. So to make OTA updates and that stuff work correctly devs of these ROMs decide to use their own recovery which can handle the decryption of encrypted roms and as result to make OTA update work fine. Check the installation instructions of these roms in their threads. (Afterwards you can use adb sideload to flash stuff using these recoveries)
After that, flash Magisk since you want root.
Then you can restore titanium backup if you want.
OK i follow your instruction.Thanks
Hello retrial,
I have now updating my phone to MIUI Global 12.0.3 Stable with Android Version 10QKQ1.My phone is not yet rooted and now he is encrypted.The recovery is now Mi-Recovery 3.0
I have unlock again my bootloader.
Now to follow your instruction,i should flash the latest TWRP.
I have take TWRP-3.6.0_9-0-berylium in your guide.
I think i should do Fastboot Method because i'm now in Mi-Recovery?i'm right?
No problem with the encryption?
Thanks.
i have find this video.This is not the good phone but i think that the installation is the same:
devil1 said:
Hello retrial,
I have now updating my phone to MIUI Global 12.0.3 Stable with Android Version 10QKQ1.My phone is not yet rooted and now he is encrypted.The recovery is now Mi-Recovery 3.0
I have unlock again my bootloader.
Now to follow your instruction,i should flash the latest TWRP.
I have take TWRP-3.6.0_9-0-berylium in your guide.
I think i should do Fastboot Method because i'm now in Mi-Recovery?i'm right?
No problem with the encryption?
Thanks.
Click to expand...
Click to collapse
Yes use Fastboot Method to flash TWRP. No problem with encryption.
After that follow my clean install custom rom guide to flash the ROM you want. Also please check the instructions in the threads of ROMs you want to flash. A12 crDroid and PE use their own recoveries.
Basically tell me which ROM you want to flash to help you exactly with steps.
Hello retrial,
i have a problem to install TWRP-3.6.0-9-0 on my pocophone.Everything working fine but in step 8 of your guide,i can't find my twrp.img that i have copied in 2 different case to test :
8. Boot into Recovery by typing in cmd: fastboot boot <recovery_filename>.img (The file may not be named identically to what stands in this command, so adjust accordingly and write the full path of it, check the example below).
This command will not flash permantly the recovery, it will just temporary boot into it and afterwards you will flash permantly the twrp.img you copied into your Internal Storage or SDcard in recovery partition.
For example: fastboot boot C:\Users\Retrial\Desktop\twrp-3.5.2_9-0-beryllium.img
Have you an idea to why i cannot find my twrp.img in the boot mode?
devil1 said:
Hello retrial,
i have a problem to install TWRP-3.6.0-9-0 on my pocophone.Everything working fine but in step 8 of your guide,i can't find my twrp.img that i have copied in 2 different case to test :
8. Boot into Recovery by typing in cmd: fastboot boot <recovery_filename>.img (The file may not be named identically to what stands in this command, so adjust accordingly and write the full path of it, check the example below).
This command will not flash permantly the recovery, it will just temporary boot into it and afterwards you will flash permantly the twrp.img you copied into your Internal Storage or SDcard in recovery partition.
For example: fastboot boot C:\Users\Retrial\Desktop\twrp-3.5.2_9-0-beryllium.img
Have you an idea to why i cannot find my twrp.img in the boot mode?
Click to expand...
Click to collapse
Send a screenshot what you type in cmd and where you have the twrp.img
Or you mean you can't find it in your device while you are booted on TWRP?
i cannot find the twrp.img in my device.The step 8 of your tutorial.
I have copied the files but cannot find it in the cases.I have take TWRP-3.6.0-9-0
The link of the files: https://eu.dl.twrp.me/beryllium/twrp-3.6.0_9-0-beryllium.img.html
devil1 said:
i cannot find the twrp.img in my device.The step 8 of your tutorial.
I have copied the files but cannot find it in the cases.I have take TWRP-3.6.0-9-0
The link of the files: https://eu.dl.twrp.me/beryllium/twrp-3.6.0_9-0-beryllium.img.html
Click to expand...
Click to collapse
Are you sure you select Install Image?
ok i have download an other twrp.img and this time it's ok.i can go to the end of the tutorial but when i reboot my device mi-recovery 3.0 come back.I have tried 2 times but all the time mi-recovery3.0 come back
Have you an idea?
Should i take a additional command like in the video i have send you in the thread "fastboot flash recovery"?
devil1 said:
ok i have download an other twrp.img and this time it's ok.i can go to the end of the tutorial but when i reboot my device mi-recovery 3.0 come back.I have tried 2 times but all the time mi-recovery3.0 come back
Have you an idea?
Should i take a additional command like in the video i have send you in the thread "fastboot flash recovery"?
View attachment 5549731
Click to expand...
Click to collapse
I have all the steps on my guide. Please read it carefully. It boots back to mi recovery because you haven't flash TWRP yet just booted into. After boot into TWRP u need to flash twrp in recovery section so it will stay after reboot.
Please read the steps.
Download portable Minimal ADB and Fastboot and latest Official TWRP recovery.
Open cmd from minimal adb and fastboot and write:
fastboot boot and the path you have TWRP.
Example:
Code:
fastboot boot C:\Users\Retrial\Desktop\twrp-3.6.0_9-0-beryllium.img
Then proceed with the rest steps in my guide. Connect ur device to pc while u are booted into TWRP and copy TWRP.img to your device. Then in TWRP press Install Image and select the twrp.img u just copied into ur device. Select recovery and done.
I have made a video to show you what happened (sorry for the bad quality and the moove) :
I think a video is easyest to understand my problem.For information my bootloader is unlock and usb debugging ok.
devil1 said:
I have made a video to show you what happened (sorry for the bad quality and the moove) :
I think a video is easyest to understand my problem.For information my bootloader is unlock and usb debugging ok.
Click to expand...
Click to collapse
Hmm strange, probably of MIUI. Anyway since you are going to flash custom rom, when u flash twrp in recovery go back and select wipe and wipe everything (read my clean install guide), go back press format data type yes, and then reboot to TWRP.
EDIT: I just saw u rebooted to system. That's not what we want. Press reboot to recovery.
i reboot first to bootloader after have flash the twrp.img in recovery.That's only the second time that i reboot to system to use the normal mode of the phone and reboot after to recovery mode to show you that mi recovery is back.
devil1 said:
i reboot first to bootloader after have flash the twrp.img in recovery.That's only the second time that i reboot to system to use the normal mode of the phone and reboot after to recovery mode to show you that mi recovery is back.
Click to expand...
Click to collapse
The TWRP flashed correctly. You overlap it again by pressing reboot to recovery from MIUI updater.
Don't do that...do the combination to boot to TWRP after flashing it. Power+Volume Up.
And continue with clean install steps in my guide to flash custom rom.
In my guide I write nowhere to boot to MIUI and press from MIUI Updater reboot to recovery, please stick to my guide and you will be fine.
Poco f1 update not