[SOLVED] Can't install TWRP on Xiaomi Redmi note 4 :'( - Xiaomi Redmi Note 4 Questions & Answers

Hi everyone !
I'm a little stuck now, so i really need your help !
I want to install LineageOS on my Xiaomi redmi note 4. So i followed the installation instructions on official Lineage website.
At the step "Install TWRP recovery" i'm stuck.
Here are the logs :
Code:
> $ fastboot flash recovery twrp-3.1.0-0-mido.img
target reported max download size of 134217728 bytes
sending 'recovery' (26840 KB)...
OKAY [ 1.328s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 1.331s
So after searching on the web I tried splitting img into chunks with the following command :
Code:
> $ fastboot flash -S 20M recovery twrp-3.1.0-0-mido.img
Invalid sparse file format at header magi
sending sparse 'recovery' (20476 KB)...
OKAY [ 1.015s]
writing 'recovery'...
FAILED (remote: sparse image size span overflow.)
finished. total time: 1.019s
I choosed 20M for my chunks randomly (inferior to recovery image of 26840KB).
Other informations :
I can't boot to origin system
I can access to fastboot
I can use adb but my device is in sideload mode
Please feel free to answer if you have any idea.
You're great! Thanks.

Did you already unlock the bootloader? It seems not yet..

crok.bic said:
Did you already unlock the bootloader? It seems not yet..
Click to expand...
Click to collapse
Yes I did !
Code:
> $ fastboot getvar all
...
(bootloader) unlocked: yes
...

Are you sure you have Mido and not Nikel? Is your SoC is Snapdragon or MTK?
And why are you flashing *not* the latest version (3.1.0.0 instead of 3.1.1.0)?
Use this Minimal ADB if you are not using this one:
https://forum.xda-developers.com/showthread.php?t=2317790
And use this TWRP instead the one you are trying to use if you really have a Mido phone:
https://dl.twrp.me/mido/twrp-3.1.1-0-mido.img.html

crok.bic said:
Are you sure you have Mido and not Nikel? Is your SoC is Snapdragon or MTK?
And why are you flashing *not* the latest version (3.1.0.0 instead of 3.1.1.0)?
Use this Minimal ADB if you are not using this one:
https://forum.xda-developers.com/showthread.php?t=2317790
And use this TWRP instead the one you are trying to use if you really have a Mido phone:
https://dl.twrp.me/mido/twrp-3.1.1-0-mido.img.html
Click to expand...
Click to collapse
I'm not sure if it's Mido or Nikel.
Do you have a link for Nikel ? Because it doesn't appear in twrp list :\
For adb i've downloaded with
Code:
sudo apt-get install android-tools-adb
I've tried with 3.1.1-0-mido and same error than 3.1.0 :\

@crok you really rock !
I've tried with this link of Nikel : https://xiaomifirmware.com/downloads/twrp-custom-recovery-redmi-note-4-mtk/
And I'm having the recovery mode!
I continue the tutorial !

Great news. Please mark the thread [solved] just to help people who has the same trouble and seeking for info/solution.

Related

[RECOVERY][cherry2] TWRP 3.1.0.0 for Honor 4X

Team Win Recovery Project 3.X+, or twrp3for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface,but you can use hardware buttons too.The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Features
All Normal functions of TWRP
Now Support 3rdimage and OEMINFO partition
Battery stats, etc
Since 3.1.0.0 a lot more features (which i can't test since i don't have the 4X anymore)
Supported Devices
Works for Honor 4X (Che2-XX)
any based Kirin 620 model
some user tried on G620s and didn't flash, so i can't assure for the che1 too
Installation Guide
Install fastboot tools (Android) from google's Sdk on your PC
Reboot in Fastboot mode, pressing volume - and USB cable into the pc
Enter the command : fastboot flash recovery twrp-3.1.0-0-cherry.img (I suggest to rename the file, for to example twrp.img, so you just write fastboot flash recovery twrp.img)
write : fastboot reboot, and when the phone is starting, only press volume+ and you will enter to TWRP
Download
https://dl.twrp.me/cherry/
Creator
Paul O'Brien
Source Code:https://github.com/TeamWin/android_device_huawei_cherry
Version Information
Status: Stable
Current Stable Version: 3.1.0.0
Stable Release Date: 2016-06-30
Created 2016-06-30
Last Updated 2016-03-11
Updated with 3.1.0.0 (And works for any 4X)
panchovix said:
Updated with 3.1.0.0 (And works for any 4X)
Click to expand...
Click to collapse
I tried to install and appears to me this error.
target reported max download size of 266338304 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.943s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 1.015s
andrejicd said:
I tried to install and appears to me this error.
target reported max download size of 266338304 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.943s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 1.015s
Click to expand...
Click to collapse
Weird, che1 or che2?
Enviado desde mi 6045B mediante Tapatalk
G620s-lO1
@andrejicd it is rare since the twrp itself was made to the g620s/che1, but it just worked on che2 too, well thanks for the info then
Yes, FAILED (remote: size too large)
It is 24.5M, really too large???
And the twrp-3.0.2-0-cherry.img has the same problem.
It this twtp 3.1.0.0 work for che2-l11 marshmello honor 4x b505 ? Be sure before response
Kireto00 said:
It this twtp 3.1.0.0 work for che2-l11 marshmello honor 4x b505 ? Be sure before response
Click to expand...
Click to collapse
It will work.
i have a che2-L11 B363
and when i tried flashing this im stuck at honor logo screen. what should i do?
raven731 said:
i have a che2-L11 B363
and when i tried flashing this im stuck at honor logo screen. what should i do?
Click to expand...
Click to collapse
What exactly u did?
Hi,
I have the exactly same problem. This is what I did.
My phone: Che2-L11
1. unlooked bootloader
2. flashed twrp-3.1.1-0-cherry.img and twrp-3.0.2-0-cherry.img from dl.twrp.me/cherry/
3. power of an boot to recovery ends in stucking with "honor" bootlogo.
thanks for any hints
panchovix said:
Team Win Recovery Project 3.X+, or twrp3for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface,but you can use hardware buttons too.The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Features
All Normal functions of TWRP
Now Support 3rdimage and OEMINFO partition
Battery stats, etc
Since 3.1.0.0 a lot more features (which i can't test since i don't have the 4X anymore)
Supported Devices
Works for Honor 4X (Che2-XX)
any based Kirin 620 model
some user tried on G620s and didn't flash, so i can't assure for the che1 too
Installation Guide
Install fastboot tools (Android) from google's Sdk on your PC
Reboot in Fastboot mode, pressing volume - and USB cable into the pc
Enter the command : fastboot flash recovery twrp-3.1.0-0-cherry.img (I suggest to rename the file, for to example twrp.img, so you just write fastboot flash recovery twrp.img)
write : fastboot reboot, and when the phone is starting, only press volume+ and you will enter to TWRP
Download
https://dl.twrp.me/cherry/
Creator
Paul O'Brien
Source Code:https://github.com/TeamWin/android_device_huawei_cherry
Version Information
Status: Stable
Current Stable Version: 3.1.0.0
Stable Release Date: 2016-06-30
Created 2016-06-30
Last Updated 2016-03-11
Click to expand...
Click to collapse
on my Che2-L11 I can Arrive until 3.0.2.0 up to that version doesnt work...anyone can help?
Lballarini said:
on my Che2-L11 I can Arrive until 3.0.2.0 up to that version doesnt work...anyone can help?
Click to expand...
Click to collapse
Yup same with me( che1-l04). In adb it says file is too large.
Hi Guys,
I am trying to push it and install but I have this error below. BTW, the phone is per-unlocked. It already has a warning red sign "PHONE Unlocked"
target reported max download size of 471859200 bytes
sending 'recovery' (25034 KB)...
OKAY [ 0.594s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.594s
.
Enviado do meu ALE-L21 através de Tapatalk
size of image is larger than target device.
G620s
andrejicd said:
I tried to install and appears to me this error.
target reported max download size of 266338304 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.943s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 1.015s
Click to expand...
Click to collapse
use minimal ADB program for flashing
I can't flash it on a che2-l11.
Flash gone fine [SUCCESS] but continues to reboot into stock recovery. Why?
Marcyvee said:
I can't flash it on a che2-l11.
Flash gone fine [SUCCESS] but continues to reboot into stock recovery. Why?
Click to expand...
Click to collapse
The same here
# fastboot flash recovery twrp-3.2.3-0-cherry.img
target reported max download size of 471859200 bytes
sending 'recovery' (25136 KB)...
OKAY [ 0.796s]
writing 'recovery'...
OKAY [ 1.014s]
finished. total time: 1.810s
At the end power and vol+ but and stock "Huawei eRecovery" start and not twrp. I'm using Che2-L11_V100R001C432B310.

failed to install soft bricked honor 8 lite oreo

frnds,
when i try to install twrp for my honor 8 lite oreo with cmd it shows like this;
(i unlocked oem and phone)
c:/adb>fastboot flash recovery RECOVERY-V2.img
target reported max downlod size of 471859200 bytes
sending 'recovery' (9100 KB)...
OKAY [ 0.313s]
writing ' recovery'....
FAILED (remote: partition length get error )
finished. total time: 0.322s
now i lost my stock recovery. how will i solve this problem .
i'm using a windows 10 pc
when i try to install a twrp the cmd shows this failed message
plzzz help me to solve this problem.
i hope you will find a solution for this.
frnds,
when i try to install twrp for my honor 8 lite oreo with cmd it shows like this;
(i unlocked oem and phone)
c:/adb>fastboot flash recovery RECOVERY-V2.img
target reported max downlod size of 471859200 bytes
sending 'recovery' (9100 KB)...
OKAY [ 0.313s]
writing ' recovery'....
FAILED (remote: partition length get error )
finished. total time: 0.322s
now i lost my stock recovery. how will i solve this problem .
i'm using a windows 10 pc
when i try to install a twrp the cmd shows this failed message
plzzz help me to solve this problem.
i hope you will find a solution for this.
alisonpoulose said:
frnds,
when i try to install twrp for my honor 8 lite oreo with cmd it shows like this;
(i unlocked oem and phone)
c:/adb>fastboot flash recovery RECOVERY-V2.img
target reported max downlod size of 471859200 bytes
sending 'recovery' (9100 KB)...
OKAY [ 0.313s]
writing ' recovery'....
FAILED (remote: partition length get error )
finished. total time: 0.322s
now i lost my stock recovery. how will i solve this problem .
i'm using a windows 10 pc
when i try to install a twrp the cmd shows this failed message
plzzz help me to solve this problem.
i hope you will find a solution for this.
Click to expand...
Click to collapse
You need to make this command :
fastboot flash ramdisk "patched_ramdisk.img"
Until yours [emoji846]
failed to install twrp
fastboot flash ramdisk "patched_ramdisk.img"
where did i get this file? did i need to rename the twrp.img to patched_ramdisk.img.
failed to install twrp
i renamed twrp.img to patched_ramdisk.img then thake cmd and typed like this;;;
c:/adb>fastboot flash ramdisk patched_ramdisk.img
error: cannot load 'patched_ramdisk.img
what will i do now plz help me to find a solution:::::
failed to install twrp
now i tried it again now it shows likes this
c/adb>fastboot flash ramdisk patched_ramdisk.img
target reported max downlod size of 471859200 bytes
sending 'ramdisk (31572 KB)...
OKAY [ 1.084s]
writing 'ramdisk'....
FAILED (remote: partition error)
finished. total time: 1.095s
here the failed message changed
in previous it is (remote: patition length error)
but now it changed to remote: partition error
bro plz help me to find a solution
i hope u can clarify it
thankyou
fastboot flash ramdisk "patched_ramdisk.img"
thanku brooooo it workssssss thanks alot
:good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good:
my twrp is red in colour others are blue
bro is there is any problem with my twrp
can i change it to blue colour
plz help me

I have a problem

Hi guys
I have a problem. XIAOMI REDMI NOTE 4 SNAPDRAGON
I had unlock phone and installed [email protected]
I have tried some ROM and everything works great but the battery went fast so i decided to try: Lineage os 160-20210205 nighty santoni
-Transfer it on sd card
-Wipe system data cache dalvik storage?
And they to flash new ROM but it went failed.
I thought need to get TWRP and got :
-TWRP 3.5.0_9-0- santoni
After I connected to my PC Linux Pop os
Used terminal :
fastboot flash recovery '/home/mati/Downloads/twrp-3.5.0_9-0-santoni.img'
target reported max download size of 536870912 bytes
sending 'recovery' (25004 KB)...
OKAY [ 0.842s]
writing 'recovery'...
OKAY [ 0.191s]
finished. total time: 1.033s
[email protected]:~$ fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
[email protected]:~$ boot into recovery mode
Command 'boot' not found, did you mean:
command 'toot' from deb toot (0.27.0-1)
command 'hboot' from deb lam-runtime (7.1.4-6build2)
command 'boom' from deb doomsday (2.2.2+ds1-1)
command 'boom' from deb prboom-plus (2:2.5.1.7um+git89-1)
command 'booth' from deb booth (1.0-205-gc9e90fe-1)
command 'bolt' from deb bolt-lmm (2.3.4+dfsg-2build1)
command 'brot' from deb fortunes-de (0.34-1)
Try: sudo apt install <deb name>
[email protected]:~$
It doesn't work it says
The system has been destroyed.
I am only on fastboot mode and can't do anything
zenon9 said:
Hi guys
I have a problem. XIAOMI REDMI NOTE 4 SNAPDRAGON
I had unlock phone and installed [email protected]
I have tried some ROM and everything works great but the battery went fast so i decided to try: Lineage os 160-20210205 nighty santoni
-Transfer it on sd card
-Wipe system data cache dalvik storage?
And they to flash new ROM but it went failed.
I thought need to get TWRP and got :
-TWRP 3.5.0_9-0- santoni
After I connected to my PC Linux Pop os
Used terminal :
fastboot flash recovery '/home/mati/Downloads/twrp-3.5.0_9-0-santoni.img'
target reported max download size of 536870912 bytes
sending 'recovery' (25004 KB)...
OKAY [ 0.842s]
writing 'recovery'...
OKAY [ 0.191s]
finished. total time: 1.033s
[email protected]:~$ fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
[email protected]:~$ boot into recovery mode
Command 'boot' not found, did you mean:
command 'toot' from deb toot (0.27.0-1)
command 'hboot' from deb lam-runtime (7.1.4-6build2)
command 'boom' from deb doomsday (2.2.2+ds1-1)
command 'boom' from deb prboom-plus (2:2.5.1.7um+git89-1)
command 'booth' from deb booth (1.0-205-gc9e90fe-1)
command 'bolt' from deb bolt-lmm (2.3.4+dfsg-2build1)
command 'brot' from deb fortunes-de (0.34-1)
Try: sudo apt install <deb name>
[email protected]:~$
It doesn't work it says
The system has been destroyed.
I am only on fastboot mode and can't do anything
Click to expand...
Click to collapse
that's incompatible twrp
You need to download a compatible twrp for mido

Please help with P20 lite , can not flash fw, board sw booting OK

Hi,
Can someone please help me with fix of my P20 lite dual?
I try to fix it for 50 hours in total, I downloaded about 150Gb of files ☹
The begining of my problem started from full working state one day, next morning I got error "your device has failed verification and may not work properly"
Phone was running stock ANE-LX1 9.1.0 C432 E6R1P7
Factory reset and cache wipe did not help.
Any attempt to SD or USB update via recovery failed, always got "Install failed"
So I tried flashing file update.app using MRT from some higher version of stock sw in fastboot, then in stock recovery, later in TWRP.
No luck, phone was in fastboot mode only or bootloops.
Then I found huawei flash tool IDT 2.0.0.9 and factory board sw 1.0.0.40 using test point (HUAWEI COM 1.0)
With this one the phone fully boots in factory firmware, but phone info says model HAT, has bootlogo ASCEND and android logo , IMEIs in menu are OK.
So how the hell can I get it back to official stock state with ANE-LX1 in "About phone"?
Any attempt of flashing ANE-LX1 sw from menu or stock recovery gives me Flash failed message.
From what I found, I probably need 3 file firmware FullOtaMF for HwOta tool, but nowhere can be found.
Or is there some easy way to flash to official ?
Or did I messed up some system files that need to be fixed?
PS: while flashing hundred of files I found one TWRP version, that can change BL lock code, so I changed it to 111111111111111 for easier unlock in future attempts.
Can be this a problem? (I hope not)
Thank you for any ideas !
hdano said:
From what I found, I probably need 3 file firmware FullOtaMF for HwOta tool, but nowhere can be found.
Click to expand...
Click to collapse
HwOTA will won't help you - it cannot identify the device in this state...
(model HAT, EMUI 4.1, Marshmallow, RAM 2.1GB )
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
-Alf- said:
HwOTA will won't help you - it cannot identify the device in this state...
(model HAT, EMUI 4.1, Marshmallow, RAM 2.1GB )
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
C:\adb>fastboot oem get-build-number
...
(bootloader) :ANE-BD 1.0.0.40(log)
OKAY [ 0.011s]
finished. total time: 0.013s
C:\adb>
C:\adb>fastboot oem get-product-model
...
(bootloader) ANE
OKAY [ 0.011s]
finished. total time: 0.013s
C:\adb>
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.022s
C:\adb>
C:\adb>fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: The reason of failed input oem_nv_item error!)
finished. total time: 0.018s
C:\adb>
C:\adb>fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.021s
hdano said:
any ideas
Click to expand...
Click to collapse
maybe the following will help you:
- Download TWRP Service ROM oeminfo and
Recovery_ramdisk for Oreo
- Unpack Service ROM package, find dload folder and transfer it to the SD card WITHOUT UNPACKING IT.
- Also copy to the SD card downloaded recovery_ramdisk oeminfo file and TWRP
- Install TWRP over eRecovery (only read the principle, not download links)
- boot into TWRP , select Install image , find oeminfo file, mark 'oeminfo' and flash it.
- Go back to the main TWRP's menu, select Reboot and Turn off.
- Use three button combo and try to install Service ROM .
Note: you do everything at your own risk, I hope that's clear
Hi Alf,
thanks for reply,
worked like a charm !
Phone booted in official rom, was working well.
But..
If I try to download OTA update from menu, it shows me update to ANE-LX1 8.0.0.174(C432)-FULL size 2.92GB ,
but after downloading phone shows install error.
I did factory reset and cache clear, same result, can not install.
So I downloaded to SD card latest sw Huawei P20 Lite ( Nova 3e ) ANE-L21 ANE-L01 hw eu Anne-L01 9.1.0.370(C432E7R1P7T8) Firmware EMUI9.1.0 05014YXU [androidhost.ru].zip
but verify goes 5% then 6% then back to 5%, then 6% then shows "install failed"
After attempt to update by *#*#2846579#*#* from menu, phone did the same, 5% 6% 5% 6% "install failed", but after reboot I have attached photo error :-(
Now not booting again, stuck in this error.
So how can I update to some new sw ?
Do I have to use some special version to go higher?
Or is it some other problem?
BTW, fastboot shows now Phone Locked and FRP locked, but I did not add any google account yet :-O
hdano said:
BTW, fastboot shows now Phone Locked and FRP locked, but I did not add any google account yet
Click to expand...
Click to collapse
Yes, service ROM lock the bootloader , it's normal.
hdano said:
FRP locked,
Click to expand...
Click to collapse
You can unlock FRP manually in Developer options - "Enable OEM unlock".
Run again fastboot commands and post results.
C:\adb>fastboot oem get-build-number
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.011s]
finished. total time: 0.012s
C:\adb>fastboot oem get-product-model
...
(bootloader) ANE-LX1
OKAY [ 0.009s]
finished. total time: 0.010s
C:\adb>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.010s
C:\adb>fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.020s
C:\adb>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.012s]
finished. total time: 0.013s
hdano said:
C:\adb>fastboot oem get-build-number
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.011s]
finished. total time: 0.012s
C:\adb>fastboot oem get-product-model
...
(bootloader) ANE-LX1
OKAY [ 0.009s]
finished. total time: 0.010s
C:\adb>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.010s
C:\adb>fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.020s
C:\adb>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ANE-LX1 8.0.0.126(C432)
OKAY [ 0.012s]
finished. total time: 0.013s
Click to expand...
Click to collapse
Okay, now boot into eRecovery (not Recovery) and select option Download latest version and recovery.
This ***** sucks :-(
hdano said:
This ***** sucks
Click to expand...
Click to collapse
Try to install .174 Service ROM via dload method.
If you get Install failed error again, then you need unlock bootloader (if it's possible) and flash some partitions in fastboot.
You can use this tutorial . Use downloaded .174 ROM. Extract and flash
- kernel
-ramdisk
- recovery_ramdisk
- system
- cust
Note: cust.img can be found in update_ane-L21_hw_eu
Reboot and turn off the phone, then flash .174 Service ROM or try update via eRecovery.
C:\adb>fastboot flash kernel KERNEL.IMG
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.893s]
writing 'kernel'...
OKAY [ 0.388s]
finished. total time: 1.286s
C:\adb>fastboot flash ramdisk RAMDISK.IMG
target reported max download size of 471859200 bytes
sending 'ramdisk' (16384 KB)...
OKAY [ 0.602s]
writing 'ramdisk'...
OKAY [ 0.075s]
finished. total time: 0.681s
C:\adb>fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (32768 KB)...
OKAY [ 1.208s]
writing 'recovery_ramdisk'...
OKAY [ 0.169s]
finished. total time: 1.381s
C:\adb>fastboot flash system SYSTEM.IMG
target reported max download size of 471859200 bytes
sending sparse 'system' 1/8 (460799 KB)...
OKAY [ 19.946s]
writing 'system' 1/8...
OKAY [ 3.866s]
sending sparse 'system' 2/8 (424020 KB)...
OKAY [ 17.042s]
writing 'system' 2/8...
OKAY [ 2.164s]
sending sparse 'system' 3/8 (458375 KB)...
OKAY [ 18.384s]
writing 'system' 3/8...
OKAY [ 2.219s]
sending sparse 'system' 4/8 (460418 KB)...
OKAY [ 18.557s]
writing 'system' 4/8...
OKAY [ 2.213s]
sending sparse 'system' 5/8 (425536 KB)...
OKAY [ 17.164s]
writing 'system' 5/8...
OKAY [ 2.157s]
sending sparse 'system' 6/8 (457971 KB)...
OKAY [ 19.231s]
writing 'system' 6/8...
OKAY [ 2.855s]
sending sparse 'system' 7/8 (460016 KB)...
OKAY [ 19.003s]
writing 'system' 7/8...
OKAY [ 3.147s]
sending sparse 'system' 8/8 (192362 KB)...
OKAY [ 7.791s]
writing 'system' 8/8...
OKAY [ 1.015s]
finished. total time: 156.792s
C:\adb>fastboot flash cust CUST.IMG
target reported max download size of 471859200 bytes
sending 'cust' (139283 KB)...
OKAY [ 5.096s]
writing 'cust'...
OKAY [ 0.794s]
finished. total time: 5.894s
C:\adb>fastboot reboot
rebooting...
Now the only I can get is this, no way to get in eRecovery
hdano said:
Now the only I can get is this, no way to get in eRecovery
Click to expand...
Click to collapse
Chinese??? Wow...
As I said before,
-Alf- said:
turn off the phone, then flash .174 Service ROM
Click to expand...
Click to collapse
Have you tried bro?
-Alf- said:
Chinese??? Wow...
As I said before,
Have you tried bro?
Click to expand...
Click to collapse
how? I can not get in eRecovery, only that chinese recovery or what it is....
hdano said:
how? I can not get in eRecovery, only that chinese recovery or what it is....
Click to expand...
Click to collapse
Service ROM has nothing to do with eRecovery.
As the bootloader got locked, I had to do the whole procedure again,
Board sw 1.0.0.39 , and
-Alf- said:
Download TWRP Service ROM oeminfo and
Recovery_ramdisk for Oreo
- Unpack Service ROM package, find dload folder and transfer it to the SD card WITHOUT UNPACKING IT.
- Also copy to the SD card downloaded recovery_ramdisk oeminfo file and TWRP
- Install TWRP over eRecovery (only read the principle, not download links)
- boot into TWRP , select Install image , find oeminfo file, mark 'oeminfo' and flash it.
- Go back to the main TWRP's menu, select Reboot and Turn off.
- Use three button combo and try to install Service ROM .
Click to expand...
Click to collapse
But I can not get it to work state, 3 button combo always fails.
Can I just simply flash all needed files by fastboot ot TWRP ?
What are all the necessary files for phone to boot up?
- kernel
-ramdisk
- recovery_ramdisk
- system
- cust
what else?
Can I just simply flash some custom ROM that will boot up after TWRP flash ?
BTW, why it should not be possible to directly flash erecovery from fastboot?
For me worked..
C:\adb>fastboot flash erecovery_ramdisk TWRP-oreo-smart.img
target reported max download size of 471859200 bytes
sending 'erecovery_ramdisk' (24790 KB)...
OKAY [ 0.660s]
writing 'erecovery_ramdisk'...
OKAY [ 0.128s]
finished. total time: 0.796s
hdano said:
what else?
Click to expand...
Click to collapse
Nothing.
But keep in mind, that "writing OKAY" does not mean that the file is actually installed (it is too long story to tell why...).
hdano said:
BTW, why it should not be possible to directly flash erecovery from fastboot?
For me worked..
Click to expand...
Click to collapse
Running working stock firmware it's impossible.
hdano said:
Hi,
Can someone please help me with fix of my P20 lite dual?
I try to fix it for 50 hours in total, I downloaded about 150Gb of files ☹
The begining of my problem started from full working state one day, next morning I got error "your device has failed verification and may not work properly"
Phone was running stock ANE-LX1 9.1.0 C432 E6R1P7
Factory reset and cache wipe did not help.
Any attempt to SD or USB update via recovery failed, always got "Install failed"
So I tried flashing file update.app using MRT from some higher version of stock sw in fastboot, then in stock recovery, later in TWRP.
No luck, phone was in fastboot mode only or bootloops.
Then I found huawei flash tool IDT 2.0.0.9 and factory board sw 1.0.0.40 using test point (HUAWEI COM 1.0)
With this one the phone fully boots in factory firmware, but phone info says model HAT, has bootlogo ASCEND and android logo , IMEIs in menu are OK.
So how the hell can I get it back to official stock state with ANE-LX1 in "About phone"?
Any attempt of flashing ANE-LX1 sw from menu or stock recovery gives me Flash failed message.
From what I found, I probably need 3 file firmware FullOtaMF for HwOta tool, but nowhere can be found.
Or is there some easy way to flash to official ?
Or did I messed up some system files that need to be fixed?
PS: while flashing hundred of files I found one TWRP version, that can change BL lock code, so I changed it to 111111111111111 for easier unlock in future attempts.
Can be this a problem? (I hope not)
Thank you for any ideas !
Click to expand...
Click to collapse
I’ve exactly the same as your issue.
But I’ve no service and dual iemis are right!
What could be the problem, did you solve yours?
Or even were you having same no service issue while you were on this case?
My device originally is nova 3e ANE l-LX1 c185 dual sim and flashed oeminfo for c185 by editing the oeminfo for c432 and by using oeminfo tools.
Also using howta8 to change oeminfo.
It was changed ok to c185 but still no service and software not installed.
I used build 160 because it’s the only have 3 files, it was installed from hisuite document/hisuite/rom folder

Anti Rollback

Hi everyone, couldn't find anything relevant on the internet and the forum about the rollback problem, there is any way to install custons ROMs with that anabled? since i bought my moto g8 power mid last year i never could install any custom rom because of that, fastboot always give me anti-rollbakc warning and won't flash some partitons so it always ended up bootlooping and i go back to stock, there is any way to disable that feature? or bypass, how can i solve this problem?
Below is the fastboot log of what usually happens.
Code:
writing 'vbmeta_a'...
(bootloader) WARNING: vbmeta_a anti rollback downgrade, 10 vs 14
OKAY [ 0.007s]
finished. total time: 0.017s
Here are the full version of the previous log i posted, i was trying to install the HavocOS via fastboot
Code:
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 805261312 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.519s]
writing 'boot_a'...
OKAY [ 1.058s]
finished. total time: 2.579s
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash product product.img
target reported max download size of 805261312 bytes
sending sparse 'product_a' 1/3 (720896 KB)...
OKAY [ 17.117s]
writing 'product_a' 1/3...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.121s
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash system system.img
target reported max download size of 805261312 bytes
sending sparse 'system_a' 1/2 (720896 KB)...
OKAY [ 17.125s]
writing 'system_a' 1/2...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 17.129s
C:\Users\henri\Documents\Minimal ADB and Fastboot>fastboot flash vbmeta vbmeta.img
target reported max download size of 805261312 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ 0.009s]
writing 'vbmeta_a'...
(bootloader) WARNING: vbmeta_a anti rollback downgrade, 0 vs 14
OKAY [ 0.011s]
finished. total time: 0.020s
You definitely are in fastboot d? Not just the bootloader?
When you are flashing the inages, if you have a green robot and some text down the bottom, that is fastboot/bootloader.
Fastboot d is different, you will definitely know if you are in fastboot d.
Beetle84 said:
You definitely are in fastboot d? Not just the bootloader?
When you are flashing the inages, if you have a green robot and some text down the bottom, that is fastboot/bootloader.
Fastboot d is different, you will definitely know if you are in fastboot d.
Click to expand...
Click to collapse
That was on bootloader, i searched about the fastboot d but couldn't find any explanation/tutorial how to enter it, i tried the command fastboot reboot fastboot but it gives unknown fastboot target, can you help me?
Fastboot reboot fastboot is the correct way from the bootloader.
You need to update your platform tools.
Also you need to be on android 10 for these roms to boot.
One of the guys helped me out with this earlier. After you've unlocked your boot loader and if your on android 11.
Use rescue & smart assistant to backup your stock rom, it will tell you what kind it is too....
Then go download the android 10 stock version.
Then use moto tools by vache and load the android 10 stock rom into it. Just follow the directions and place it in bootloader.
after that flash whatever puppy of your choosing. Also I'd advise against flashing twrp just boot it. Also if you do use twrp, make sure you don't reboot from side B! you will brick your device....
Beetle84 said:
Fastboot reboot fastboot is the correct way from the bootloader.
You need to update your platform tools.
Also you need to be on android 10 for these roms to boot.
Click to expand...
Click to collapse
That solved all the problem i was facing, thanks
revengesrage said:
One of the guys helped me out with this earlier. After you've unlocked your boot loader and if your on android 11.
Use rescue & smart assistant to backup your stock rom, it will tell you what kind it is too....
Then go download the android 10 stock version.
Then use moto tools by vache and load the android 10 stock rom into it. Just follow the directions and place it in bootloader.
after that flash whatever puppy of your choosing. Also I'd advise against flashing twrp just boot it. Also if you do use twrp, make sure you don't reboot from side B! you will brick your device....
Click to expand...
Click to collapse
Thansk for the tips, it is really important to set the partitions, i was struggling a lot to boot system since twrp redirected things to side B while A was set, i don't know why but now everthing is running flawlessly

Categories

Resources