Unable to boot to TWRP (L21 with B340) - Honor 5X Questions & Answers

Hello, fellow Android hackers.
Short: I am trying to install CM on a L21, but fail booting into TWRP (getting only stock recovery).
What I did, working with a brand-new phone:
Unlock bootloader.
Flash TWRP 3.0.2.
Boot to TWRP. It worked.
Try flashing CM, which failed due to some failed assert. Googling revealed a thread on these forums which suggested I had to do a stock update to Marshmallow first.
Downloaded the update through EMUI's updater.
The updater booted to TWRP which aborted the installation because of a failed zip signature check.
I disabled signature checking and ran the installation again. It succeeded.
Tried to directly install CM over it. I got the error message stating I couldn't flash on top of incompatible data.
At this point, I probably should just have wiped system and flash CM, but for some reason I decided to boot to stock.
Here is where it all seems to have gone wrong.
Try to flash and boot to TWRP, like in steps 13 to 18.
Push the B340 UPDATE.APP to /sdcard/dload.
Start the phone using power + vol down + vol up.
I have verified that the phone is on B340 and the builtin updater won't find further updates.
(I have repeated this step and the following ones countless times.)
Boot to bootloader and flash TWRP. Yes, the command succeeds.
Code:
…$ sudo fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.418s]
writing 'recovery'...
OKAY [ 0.641s]
finished. total time: 2.059s
fastboot reboot
adb reboot recovery # boots to stock recovery
Boot to bootloader and flash TWRP.
Hold power + vol up
I read that the duration holding the keys matters, so I tried this very often, but I always got to one of two different stock recoveries.
Factory reset and cache wipe with one of the two stock recoveries.
I also considered crushing the phone on the wall on multiple occasions, but then decided it would not help me with my goal.
Okay.
L21 with B340, how u boot to TWRP? -_-
Also, the two stock recoveries have the menu options "Download latest version and recovery, Reboot, Shutdown" and "Reboot, Wipe data/factory reset, Wipe cache partition".
I humbly thank everyone in advance who might have some contributions to share.

ok . as i understand ,
First Charge Ur Phone Up To 50%+
Second : Go Back To Stock L 5.0.1
Third : download The latest Nightly Version OF CM + Recovery Rom | Recovey
Forth : Flash Recovery Only Throw ADB if u got any error please Attach here if success Go to step 5
Fifth : Shut Down And HOLD Volume-up + Power As soon u see Honor logo Release Power But Keep Volume Rocked Pressed !
Last : Install The Cm After U already copy To SD Card .
Gd Luck ! .

i will presume that you are on stock recovery,
now go to honor 5x repository and download b320 firmware
now place it in dload folder and flash
now boot to bootlader and try flashing twrp
then do not directly boot to revovery
just do fastboot reboot
then now do adb reboot recovery
youl be with twrp and forst things first ,compulsarily do a backup
then now assuming that you have transfered layest cm to sd card,
first goto wipe , then select all except internal and external sd cards , then wipe
now install, you should be good to go,
i had your issue when i was on b34p, but b320 is a great base and supports all custom roms..try it

(I am sorry for not answering sooner, but I have a lot on my plate right now. :/ )
Thanks for the replies.
Romiui said:
ok . as i understand ,
First Charge Ur Phone Up To 50%+
Second : Go Back To Stock L 5.0.1
Third : download The latest Nightly Version OF CM + Recovery Rom | Recovey
Forth : Flash Recovery Only Throw ADB if u got any error please Attach here if success Go to step 5
Fifth : Shut Down And HOLD Volume-up + Power As soon u see Honor logo Release Power But Keep Volume Rocked Pressed !
Last : Install The Cm After U already copy To SD Card .
Gd Luck ! .
Click to expand...
Click to collapse
2: As I understood it I only had to upgrade to M in the first place to be able to install CM. The downgrade will not undo whatever happened there?
3: I am not sure that I understand what you're trying to say, but I know of no way to flash recoveries via ADB. The point is that, as posted in the OP, flash via fastboot allegedly succeeds and as soon as I boot to the recovery, I'm back to stock.
thilak devraj said:
i will presume that you are on stock recovery,
now go to honor 5x repository and download b320 firmware
now place it in dload folder and flash
now boot to bootlader and try flashing twrp
then do not directly boot to revovery
just do fastboot reboot
then now do adb reboot recovery
youl be with twrp and forst things first ,compulsarily do a backup
then now assuming that you have transfered layest cm to sd card,
first goto wipe , then select all except internal and external sd cards , then wipe
now install, you should be good to go,
i had your issue when i was on b340, but b320 is a great base and supports all custom roms..try it
Click to expand...
Click to collapse
Thanks. I actually tried the dload method with B140 after writing this post, but it doesn't seem to work—same with B330 (the repo doesn't contain a B320 for L21). As far as I can tell, the dload install appears pretends to work fine: I'm getting a successful archive verification, an install meter and no error message. But the OS is not replaced.
I am uncertain if I need an actual microSD card—different sources seem to suggest different things here—but I generally would assume that, if there was no valid image in the right place, I would be getting an error message.
I am fine with whatever suggestion that wouldn't result in a brick. Data loss is fine, there's nothing on it.

A dumb question but do you disconnect the phone from PC or Mac after flashing twrp, firing fastboot reboot and quickly press power and vol up to boot to twrp.
If you already did that, try unlocking command once more and then try flashing it...
You can also try
Fastboot boot twrp_kiwi.img
To boot directly to twrp without flashing.
Hope any of it works.

ksdug said:
(I am sorry for not answering sooner, but I have a lot on my plate right now. :/ )
Thanks for the replies.
but I know of no way to flash recoveries via ADB.
D
Click to expand...
Click to collapse
All recoveries can be Flashed throw Fast-boot ADB Boss .

ksdug said:
(I am sorry for not answering sooner, but I have a lot on my plate right now. :/ )
Thanks for the replies.
2: As I understood it I only had to upgrade to M in the first place to be able to install CM. The downgrade will not undo whatever happened there?
3: I am not sure that I understand what you're trying to say, but I know of no way to flash recoveries via ADB. The point is that, as posted in the OP, flash via fastboot allegedly succeeds and as soon as I boot to the recovery, I'm back to stock.
Thanks. I actually tried the dload method with B140 after writing this post, but it doesn't seem to work—same with B330 (the repo doesn't contain a B320 for L21). As far as I can tell, the dload install appears to work fine: I'm getting a successful archive verification, an install meter and no error message. But the OS is not replaced.
I am uncertain if I need an actual microSD card—different sources seem to suggest different things here—but I generally would assume that, if there was no valid image in the right place, I would be getting an error message.
I am fine with whatever suggestion that wouldn't result in a brick. Data loss is fine, there's nothing on it.
Click to expand...
Click to collapse
glad you did it

thilak devraj said:
glad you did it
Click to expand...
Click to collapse
I rephrased that part as it was unclear. I didn't manage to pull off a downgrade.
muradulislam said:
A dumb question but do you disconnect the phone from PC or Mac after flashing twrp, firing fastboot reboot and quickly press power and vol up to boot to twrp.
If you already did that, try unlocking command once more and then try flashing it...
Click to expand...
Click to collapse
I did, but to no avail. Reunlocking had no effect either.
muradulislam said:
You can also try
Fastboot boot twrp_kiwi.img
To boot directly to twrp without flashing.
Hope any of it works.
Click to expand...
Click to collapse
I love you. I had totally forgotten about that. Using the boot command I managed to install CM, but I still cannot replace the stock recovery. Maybe I'll try letting CM write its own recovery with its next update, but I guess I'll leave it at that. The only downside is that my dad now needs me for doing updates. :/
Thanks very much.

ksdug said:
I rephrased that part as it was unclear. I didn't manage to pull off a downgrade.
I did, but to no avail. Reunlocking had no effect either.
I love you. I had totally forgotten about that. Using the boot command I managed to install CM, but I still cannot replace the stock recovery. Maybe I'll try letting CM write its own recovery with its next update, but I guess I'll leave it at that. The only downside is that my dad now needs me for doing updates. :/
Thanks very much.
Click to expand...
Click to collapse
wait......
you couldnt make it?? ok right now were are you at??

how to boot Honor 5x into TWRP
I know this is an old post, but since I tried for nearly a week to get my Honor 5x to boot in TWRP when pushing volume up + power button, I just wanted to post how I finally got it working, just in case anyone else should have the same problem...
1. First, I downloaded the latest stock rom. On my Honor 5x Android 5 (Lollipop) was installed, so I downloaded an Android 6 (marshmallow) stock rom. Make sure to get the correct version for your region (e.g. C432 for Europe). I found the correct rom file by simply googeling. If you are in a boot loop or do not have a working android on your phone, read instructions below.
2. I un-zipped the rom file and copied the update.app to my sd card to folder "dload"
3. I booted regularly into Android and started the update installation from the settings, where I could select option to install from SD card.
4. once that was done, i enabled USB debugging in developer tools and booted into TWRP from ADB with command
fastboot boot twrp-3.1.0-0-kiwi.img
5. Then, I installed SuperSu (SuperSU-v2.82-201705271822.zip)
6. Then, I flahed TWRP directly FROM TWRP. To do so, I clicked "Install" button, clicked "Install Image" and then selected TWRP file (which i copied to my SD card earlier). BE CAREFUL TO FLASH TWRP as Revovery (NOT boot). Actually, I first flashed twrp-3.0.0-0-kiwi.img, then directly after flashed twrp-3.0.2-0-kiwi.img and then I flashed twrp-3.0.0-1-kiwi.img (you see I was kind of desperate...). After that, from TWRP I booted into bootloader and again flashed twrp image from PC using adb:
fastboot flash recovery twrp-3.1.1-0-kiwi.img
7. from ADB, I again booted into TWRP
fastboot boot twrp-3.1.1-0-kiwi.img
8. ... where I once more installed TWRP.
After that I clicked reboot and selected to boot into Recovery. Then it finally worked.
After endless tries to get my phone to boot into TWRP when pushing volume up and power button, I am not sure which of the above steps made the difference. I think the important part is to update to the latest android version.
BTW: my first problem was I bricked my phone by trying to install lineageos from TWRP 3.1.1.1 and was in an endless bootloop. Here is how I got a regular android running:
I booted into bootloader (power + vol DOWN) and flashed the following files from adb (i got the files by extracting an android stock rom with Huawei Update Extractor (HuaweiUpdateExtractor_0.9.9.3.zip)):
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
Hope this helps...

It's better to post in a new thread, that will be more helpful for you

Related

Can't flash twrp

Recently bricked my honor 5x used fast boot to get it out of boot loop. (Because I tried to its update my phone with twrp)now when I try to re flash twrp it gets replaced by the stock recovery Everytime . Please help!
Samething happend to me... cannot flash twrp because when i restart phone after flashing twrp, it gets replaced by stock recovery.
What i do now is to boot to twrp instead of flashing using this command:
Code:
fastboot boot twrp-3.0.0-0-kiwi.img
Hopefully there is a solution for this flashing problem.
FREAK0N said:
Samething happend to me... cannot flash twrp because when i restart phone after flashing twrp, it gets replaced by stock recovery.
What i do now is to boot to twrp instead of flashing using this command:
Code:
fastboot boot twrp-3.0.0-0-kiwi.img
Hopefully there is a solution for this flashing problem.
Click to expand...
Click to collapse
you can't just reboot after flashing recovery ...you have to boot directly to twrp after the flash with power + volume up (Skip the fastboot reboot step)
the simple way is to copy kiwi_twrp_3-21_recovery.img to your sdcard
fastboot boot kiwi_twrp_3-21_recovery.img
now in twrp choose install / image / then choose kiwi_twrp_3-21_recovery.img
next choose reboot / recovery
you now have kiwi_twrp_3-21_recovery.img
from then on adb reboot recovery from android
or power + volume up will enter TWRP
clsA said:
you can't just reboot after flashing recovery ...you have to boot directly to twrp after the flash with power + volume up (Skip the fastboot reboot step)
the simple way is to copy kiwi_twrp_3-21_recovery.img to your sdcard
fastboot boot kiwi_twrp_3-21_recovery.img
now in twrp choose install / image / then choose kiwi_twrp_3-21_recovery.img
next choose reboot / recovery
you now have kiwi_twrp_3-21_recovery.img
from then on adb reboot recovery from android
or power + volume up will enter TWRP
Click to expand...
Click to collapse
Thanks alot... i wil try it later.
Too many Links is what ADB Says
RootMega said:
Too many Links is what ADB Says
Click to expand...
Click to collapse
why are you using adb ?
did you read the instructions i posted
I have the stock recovery.
I cant get into twrp.
I tried to flash then go straight to twrp which gets replaced by stock bootloader
Idk it gets replaced everytime
Okay the adb thing stopped I got into twrp by doing the fastboot thing but when i boot into recovery it goes to the stock recovery.
RootMega said:
Okay the adb thing stopped I got into twrp by doing the fastboot thing but when i boot into recovery it goes to the stock recovery.
Click to expand...
Click to collapse
I really don't know why you don't seem to get it
it's this simple
you fastboot boot kiwi_twrp_3-21_recovery.img
now while in TWRP copy kiwi_twrp_3-21_recovery.img to the phone
Also copy SuperSU-v2.64.zip (or newer) to the phone
after the files are copied choose Install / Image / kiwi_twrp_3-21_recovery.img
next choose install / SuperSU.zip
next choose Reboot / Recovery
you now have TWRP recovery and you can enter it by using power + volume up
or from an app on the phone (I use Quickboot) or from a pc with adb reboot recovery
I have the same problem, i tried with your method but the system continue to replace bootloader, impossible to keep twrp on recovery
Edit : I try to install Root Checker, it detect my phone is root but impossible to access to TWRP, very strange
clsA said:
you can't just reboot after flashing recovery ...you have to boot directly to twrp after the flash with power + volume up (Skip the fastboot reboot step)
the simple way is to copy kiwi_twrp_3-21_recovery.img to your sdcard
fastboot boot kiwi_twrp_3-21_recovery.img
now in twrp choose install / image / then choose kiwi_twrp_3-21_recovery.img
next choose reboot / recovery
you now have kiwi_twrp_3-21_recovery.img
from then on adb reboot recovery from android
or power + volume up will enter TWRP
Click to expand...
Click to collapse
Tried this on my KIW-L21, as this is the only way I did not try it yet...
Did not work, unfortunately, I assume the OP could have the same problem as I already posted in the TWRP thread:
http://forum.xda-developers.com/showpost.php?p=66678377&postcount=509
(It is a shame people spam this thread with unlocking problems, though)
EarlyMon mentioned something about dual recovery partitions here: http://forum.xda-developers.com/showpost.php?p=66838009&postcount=529
So regardless how many times I flash TWRP it wont stick until the next reboot to recovery, as it gets replaced by the stock one all the time.
I am thankful for every news on that topic and I would happily help(to the extent I am able to) getting TWRP back onto our phones :good:
P.S.: I am not quite sure if the OP has another problem in flashing the recovery, though.
Nekly said:
Tried this on my KIW-L21, as this is the only way I did not try it yet...
Did not work, unfortunately, I assume the OP could have the same problem as I already posted in the TWRP thread:
http://forum.xda-developers.com/showpost.php?p=66678377&postcount=509
(It is a shame people spam this thread with unlocking problems, though)
EarlyMon mentioned something about dual recovery partitions here: http://forum.xda-developers.com/showpost.php?p=66838009&postcount=529
So regardless how many times I flash TWRP it wont stick until the next reboot to recovery, as it gets replaced by the stock one all the time.
I am thankful for every news on that topic and I would happily help(to the extent I am able to) getting TWRP back onto our phones :good:
P.S.: I am not quite sure if the OP has another problem in flashing the recovery, though.
Click to expand...
Click to collapse
So you are booting TWRP
Installing / TWRP.Img in TWRP and Reboot recovery and your not booting to TWRP ?
Just my two cents into this thread: apparently (from my personal experience, and EarlyMon seems to back this up) the Honor 5X for whatever reason allows the installation of TWRP but still keeps Huawei's stock recovery in place, unlike most phones. What's more, it randomly (yeah, guessing it's not random obviously, but I don't have the slightest clue what the pattern might be) decides to boot into stock recovery while I use the same hardware keys that have continuously booted me into TWRP up until that point. This behavior led me to believe I had bricked my phone for a day, lol (I made a recent post about it on this forum, in case anyone cares).
Bottom line: if you can't boot into TWRP even though you made sure to install it correctly, try changing the key combo. Vol down + Power not working for you? Try Vol Up. Neither work? Try Vol Up + Down + Power. Spice it out and it might solve your problems.
clsA said:
So you are booting TWRP
Installing / TWRP.Img in TWRP and Reboot recovery and your not booting to TWRP ?
Click to expand...
Click to collapse
That is correct:
Connected Phone to PC
ADB reboot bootloader
fastboot boot kiwi.img
install image kiwi.img
reboot recovery
Tada, Stock eMUI Recovery :[
I really had hoped it would do the trick, though.
Nekly said:
That is correct:
Connected Phone to PC
ADB reboot bootloader
fastboot boot kiwi.img
install image kiwi.img
reboot recovery
Tada, Stock eMUI Recovery :[
I really had hoped it would do the trick, though.
Click to expand...
Click to collapse
what version of TWRP are you using ? whats the real file name ?
Has anyone tried flashing TWRP with TWRP Manager from the play store?
Sm0k3d 0uT said:
Has anyone tried flashing TWRP with TWRP Manager from the play store?
Click to expand...
Click to collapse
Been there and done that. Same outcome.
clsA said:
what version of TWRP are you using ? whats the real file name ?
Click to expand...
Click to collapse
The last approach was done with the one from the first post of the TWRP thread here on XDA(https://goo.gl/53xai9) "kiwi_twrp_3-21_recovery.img"
I also tried the TWRP images from https://twrp.me/devices/huaweihonor5x.html but always the same result.
I can try with a specific image, just give me a link and I'll try to flash it. :fingers-crossed:

Can't boot to bootloader after bootloader unlocked

Hi,
I unlocked my Honor 9 bootloader using the "fastboot oem unlock 'unlock key'" method.
After that it did low level reset or something of the sort and booted to Android.
After that I wanted to install TWRP using fastboot, the problem is that every time I do "adb reboot bootloader" I get a message the device cannot be trusted (see pic) and it boots to android.
I tried pressing power button, up button (this gets me to the recovery), but it always gets back to Android and not to fastboot.
What can I do???
Thank you
Return fully stock, then try again
PalakMi said:
Return fully stock, then try again
Click to expand...
Click to collapse
How do I do that, use the original recovery?
OK, I managed to get to the bootloader by turning off the phone, pressing the volume down button and connecting the USB cable.
I flashed twrp and somehow booted to the recovery I wanted to flash the supersu.zip but all the folders and file names in the sdcard were gibberish.
I rebooted and everything was ok (not gibberish) but instead of having twrp I got the original recovery back.
Since then even if I flash using fastboot the twrp recovery I keep getting the original recovery.
In the fastboot screen there's a message "Android reboot reason: bootloader NA reboot_enter_fastboot_common_func" is it normal? (see pic)
And one last question, should I use SuperSU-v2.82-201705271822.zip or Magisk-v14.0.zip to root?
UPDATE:
I managed to get twrp working.
I did fastboot oem relock, and then unlocked the bootloader again, and it booted to twrp (without re-flashing twrp).
When I tried to flash supersu all the files were gibberish (see pic), what am I missing?
If I wipe data it seems fine, but then I boot to system to copy the supersu file and once I load twrp it is gibberish again.
Also should I use SuperSU-v2.82-201705271822.zip or Magisk-v14.0.zip to root?
Appreciate any help I can get.
This mate is called encryption
Put the SuperSU zip on a SD card and you should be able to flash it without any problems if you use the latest beta release.
Magisk is another story.
Midhon58 said:
This mate is called encryption
Put the SuperSU zip on a SD card and you should be able to flash it without any problems if you use the latest beta release.
Magisk is another story.
Click to expand...
Click to collapse
yeah I figured as much.
Didn't think of using external SD, thanks, was about to try adb sideload, I assume it would have worked too.
Many thanks, the external sd did the trick

Bricked STF-L09 C185

I screwed up my phone lol, when I was updating it to oreo, I didn't know that the update.zip file was corrupted.
Now I'm stuck on
Error!
Func NO : 9 (hifi image)
Error NO : 1 (security image failed)
My version was...
STF-L09C185B170
What i tried to install that failed is...
STF-L09C185B361 (8.0.0.361)
I can still go to fastboot with everything unlocked, I can also flash a twrp recovery, but only by typing flash recovery_ramdisk(instead "recovery"), and when I try to do the update method by pressing vol up, vol down, and power, it doesnt take me to the update section, it just show me a crashed screen, then goes back to error message.
I also tried volup and power, I can't seem to go to twrp(I think booting to twrp and flashing zip files can be one of the only ways to fix this). Is there a way to go to twrp recovery using fastboot?
I've also tried flashing extracted files from update.app manually, it doesn't work. Some files can be flashed, while some can't.
Please I'm begging u guys, pls halp :crying:
also I guess the lesson here is: double check if your file is corrupted before installing/flashing
First, what is the way you took triying to update ?
(When done from system UI, official or FF, there is an integrity check of downloaded files.)
It seems you got oreo partition scheme during your failed update.
First see this guide:
https://forum.xda-developers.com/mate-8/general/fastboot-erecovery-recovery-upgrade-mode-t3543441
Try to restore using erecovery. (download and update firmware via wifi)
If not working you could use HWOTA8.
For launching recovery (stock or twrp) from bootloader type "fastboot reboot recovery".
oslo83 said:
First, what is the way you took triying to update ?
(When done from system UI, official or FF, there is an integrity check of downloaded files.)
It seems you got oreo partition scheme during your failed update.
First see this guide:
https://forum.xda-developers.com/mate-8/general/fastboot-erecovery-recovery-upgrade-mode-t3543441
Try to restore using erecovery. (download and update firmware via wifi)
If not working you could use HWOTA8.
For launching recovery (stock or twrp) from bootloader type "fastboot reboot recovery".
Click to expand...
Click to collapse
I downloaded the oreo file using a browser and installed it with HWOTA, everything got inserted into my device, but the update failed and it gave me the error when I reboot. Also I can't get to erecovery or upgrade mode(that's the crashed screen), and "fastboot reboot recovery" doesn't work, it just show me a list of commands(which I assume happens if the command is invalid).
Ok I'll try HWOTA8, but I need to configure it so it recognizes my device, only my adb recognizes it.
Do 'fastboot devices work'?
Try english hwota8.
oslo83 said:
Do 'fastboot devices work'?
Try english hwota8.
Click to expand...
Click to collapse
Nah, I figured it out, I backed up my adb folder and just merged hwota8 with it. Yes, it does work.
Btw how do I fully turn off the device? it just keeps bootlooping if i hold down the volup and power key, maybe this is the reason why I can't get into twrp recovery.
My only hope is that I can flash something on fastboot that will let me go to update mode(or erecovery) or twrp.
Like.. anything, even boot.img fails when I try to flash it. It must be stuck on oreo partition.
Also I did considered dc phoenix, but I don't have the money to pay for an account. Man, why is unbricking not free on huawei devices? That guy prolly made a fortune by now(for holding everyone with unbrick leverage lel), and it's a huge mistake for me to fiddle with a huawei device, it has so many problems with twrp and root.
If anyone can find a way to do unbrick it, like anything, that would be great.
So you didn't manage to use honor9's hwota8 ?
oslo83 said:
So you didn't manage to use honor9's hwota8 ?
Click to expand...
Click to collapse
I used it but it didn't worked, I need to be either booted in the phone's os or inside twrp recovery bec. all of the commands executed by hwota8 are adb shell, not fastboot. Like I said, I only have access to fastboot, but I'll try again tomorrow. This is taking a lot of my time and I'm having panic attacks that I may not be able to fix this lol. Oh yeah, thanks for helping out.
Note: Since Oreo, partitions names have changed ; "recovery" changed to "recovery_ramdisk" now.
Use this command to flash recovery: fastboot flash recovery_ramdisk YourStockOrTwrpRecovery.img
Use oreo stock recovery or oreo twrp.
But I thought with hwotas available for honor 9 you started from bootloader...
oslo83 said:
Note: Since Oreo, partitions names have changed ; "recovery" changed to "recovery_ramdisk" now.
Use this command to flash recovery: fastboot flash recovery_ramdisk YourStockOrTwrpRecovery.img
Use oreo stock recovery or oreo twrp.
But I thought with hwotas available for honor 9 you started from bootloader...
Click to expand...
Click to collapse
I already did that, read the OP. Like I said, I can't boot into any recovery, not twrp not stock, not even upgrade mode, nothing.
As for hwota8, nope, it doesnt start from the bootloader, it's already trying to use the adb shell commands.
Anyway I'm taking all chances, I'm trying to research oreo's partitions names, and I'm also trying to find out how to bypass this message "FAILED (remote: Command not allowed)" bec. it might be the only way I can salvage this phone.
edit: ok im trying hwota8 again, maybe i missed something, and yes it has fastboot, sorry i was rushing but im trying again now, i'll post my progress later

Can't install recovery on slot A

EDIT:
In my way of trying to apply to warranty and flashing the stock package into the phone and Windows being Windows, I had problems using the batch script, it stopped for long time and didn't do nothing forcing me to restart the phone and restart the batch, until I uninstalled the driver and make Windows reinstall it automatically (manage devices) and it finally flashed it all, actually I flashed the package three times just to be sure lol. So, in the end I wanted to turn off the friggin phone because I was very done with it (what a PITA it has been) and wanted to apply for my warranty so as there is no command in fastboot to shutdown the phone I didn't know how to shut it down so I tried pressing Power button and releasing it the moment the screen goes off but I think I didn't do it right or the phone can't be shutdown that way (this is most probably the answer), well the phone rebooted and by the grace of Zeus it booted for the first time into MIUI and now is waiting for me to configure the phone, none of the times I flashed this packaged into the phone it booted into MIUI, never, and just when I want to turn the phone this thing boots, I don't know if I'm going to venture into flashing anything again being the phone how it is but goddamnit it was a real PITA, I had to use my old Redmi Note 3.
So, tl;dr: Flashed stock package, phone booted finally, all is OK for now.
====================================================================================================
====================================================================================================
Sooo, I was having problems with flashing stuff on this phone but I solved them and I was able to flash HavocOS, it was OK and I could use my phone kinda well (some reboots but nothing serious, or so I thought). So, until 12 hours ago my phone was having problems with the File Manager (I used FX app and also the stock one), it hanged and didn't respond and made the phone reboot itself a couple times, that was weird, actually the whole time I used this ROM I was having problems with my files, it used to took long time to read some files and I was thinking that maybe my SD was bad but apparently it's not. So, after the second reboot I was able to finally open the file manager but navigating through the SDCard was buggy and the app didn't show me any file (it show me an empty list) so I rebooted my phone manually (this time wasn't done by the phone itself) and now is when the phone never passed from the Havoc logo, I waited something close to 30 min and nothing, rebooted and waited 10 min and nothing, it still hanged on the logo, went into recovery to wipe everything and re-flash all and after doing all that and tried to boot to system my phone was booting to recovery and didn't past that, tried installing stock (flash_all script) and then installing recovery and everything again and nothing, it booted to recovery always. So there is when I realized I couldn't change anything in the slot A (at least to what boot refers), I can't install TWRP nor OrangeFox, I can do it in slot B, and even if I boot into recovery on slot B I can flash the zip installer, change the slot and try to boot to recovery from slot A but it boots to the bootloader, and yes, TWRP didn't output any error when flashing the installer.
Yes, the script flashes everything OK, well not everything, system and vendor partitions (A and B) I had to flash them manually because it gave me some errors with the script (reading errors, and yes I compared checksums so it was super weird) but in the end supposedly the stock ROM must have been installed, which I couldn't try because even after flashing everything on the script the phone was booting to bootloader, I didn't give importance to this because before I was able to flash and boot HavocOS I did the same thing because my phone was bootlooping into fastboot: I ran the script, flashed manually those images because it gave me the same errors, tried to boot to system and the phone booted to bootloader, didn't give a sheat, flashed OrangeFox recovery, ROM, recovery installer, GApps, nofde patch and then I was able to boot to HavocOS. But now this time I tried to install TWRP with fastboot command but it didn't worked, fastboot doesn't throw any errors while flashing, it reported:
Sending 'boot_a' (39780 KB) OKAY [ 1.042s]
Writing 'boot_a' OKAY [ 0.208s]
Finished. Total time: 1.263s
But if I try to boot into recovery it sends me to fastboot/bootloader, if I do this in the slot B I can successfully boot into recovery and, as I said, if I flash the installer, change the slot and reboot to recovery, my phone reboots to fastboot.
This has happened to someone else?
Does anybody knows of any solution?
I still have warranty (phone has less than 3 months) so I probably can flash the stock package and lock my bootloader so I can get my phone checked as probably it is a hardware failure, probably and hopefully .
Oh, and also I have to add that the recovery was also lagging sometimes (OrangeFox). Sometimes when I was looking into files on the SD, also when I pressed the "reboot system" button it hanged for half a minute and the it proceeded to reboot, and also once when I was flashing the nofde patch the phone also hanged and rebooted into recovery by itself. So this indicates that maybe is a hardware thing right? Because there is no way that the recovery could have gotten corrupted or something just out of the blue.
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
RthurPendragon said:
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
Click to expand...
Click to collapse
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Jhon_Locke said:
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Click to expand...
Click to collapse
In my case, I wiped system and installed Evolution X ROM (OSS version) with Custom Recovery (SHRP) Then when I want to reboot into recovery again to flash Magisk, There's no recovery... It always opens with fastboot mode. I tried flashing recovery.zip from slot b. Still no result.
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Iamdchandan said:
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Click to expand...
Click to collapse
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Iamdchandan said:
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Click to expand...
Click to collapse
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
garylawwd said:
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
Click to expand...
Click to collapse
First if all reboot into fastboot mode then connect with pc then type command " fastboot flashing unlock" enter now again forcefully reboot into fastboot mode then type next command "fastboot flashing_critical unlock" now bootloader unlock.
Again reboot into fastboot mode then type command "fastboot getvar current-slot"
Now change current active slot and then type command " fastboot erase boot" . Now finally flashed twrp latest (3.4) for Android 10 with command "fastboot flash boot twrp.img" now it flash successfully then type command "fastboot reboot" and then press volume up then hit enter and it return in fastboot mode then i have again change slot and repeat all process with that slot but it again stuck in fastboot mode. After all i have changed twrp version but again same thing repeat so I flashed stock Android 10 through Mi flash and lock bootloader.
That's all whole process.
If do something wrong please help me to figure out.
Waiting for your reply ?.
Love
try sharp recovery
Sami Devo said:
try sharp recovery
Click to expand...
Click to collapse
I don't know installation process of sharp recovery.
Iamdchandan said:
I don't know installation process of sharp recovery.
Click to expand...
Click to collapse
install on the other slot... dont flash it on running rom slot... if rom running A.. chng it to B. then flash to B.. then goto recovery flash the sharp zip when sharp opens..then again chng slot to A.. running rom slot..
okk ur phn boots.

tried to flash firmware, cant do anything now

Hi all,
The story is that I had Linage flashed, but it said it was time to update the firmware, so I tried to do that.
I booted in twrp and flashed the most recent firmware. I had plenty of power on the battery. But after it finished it booted into a classic miui interface. From here it only got worse. It asked for my password which I entered several times, but it was incorrect.
What I tried was to clear the storage. But I get the same error when it boots - it boots into miui, then shortly after a google load screen and then it reboots.
I tried downloading the mi flash tool. But when I connect the phone and locate the file, the screen has just one line in the corner saying something like "press any key to reboot".
With the adb command it doesn't seem like there is actually made a connection.
I do not really care which OS you suggest I install, as long as it at least can get it up and running again.
------------------
I just got it into fastboot and it goes fine with fastboot devices where I can see that it is connected, but when I enter fastboot flash recovery twrp.img then the phone reboots with an error code in the cmd window saying:
"FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed"
Any suggestions to what I can do? Can it be the twrp image that is causing the issue?
twrp-3.3.0-0-beryllium.img 30.3mb
kitkat87 said:
Hi all,
The story is that I had Linage flashed, but it said it was time to update the firmware, so I tried to do that.
I booted in twrp and flashed the most recent firmware. I had plenty of power on the battery. But after it finished it booted into a classic miui interface. From here it only got worse. It asked for my password which I entered several times, but it was incorrect.
What I tried was to clear the storage. But I get the same error when it boots - it boots into miui, then shortly after a google load screen and then it reboots.
I tried downloading the mi flash tool. But when I connect the phone and locate the file, the screen has just one line in the corner saying something like "press any key to reboot".
With the adb command it doesn't seem like there is actually made a connection.
Any suggestions to what I can do?
I do not really care wchich OS you suggest I install, as long as it at least can get it up and running again.
Click to expand...
Click to collapse
This will work with any Android 10 custom ROM
If you want to stay unencrypted, you have to use dfe (disable force encryption). I have never used it, but if you want it try to get one without magisk.
1. 11.0.6 is the latest firmware. You can download it from here:https://xiaomifirmwareupdater.com/firmware/beryllium/
2. You have to format your internal storage.
3. Steps: go to recovery (press back when it asks for password)->wipe->format data (it will ask you to type "yes")-> wipe system, data, internal storage,cache, davlik cache
Copy firmware,rom, gapps, dfe into your internal storage, flash firmware (most ROMs include vendor but flash full firmware just to be sure), ROM, gapps, dfe and reboot.
sotosgolf said:
This will work with any Android 10 custom ROM
If you want to stay unencrypted, you have to use dfe (disable force encryption). I have never used it, but if you want it try to get one without magisk.
1. 11.0.6 is the latest firmware. You can download it from here:https://xiaomifirmwareupdater.com/firmware/beryllium/
2. You have to format your internal storage.
3. Steps: go to recovery (press back when it asks for password)->wipe->format data (it will ask you to type "yes")-> wipe system, data, internal storage,cache, davlik cache
Copy firmware,rom, gapps, dfe into your internal storage, flash firmware (most ROMs include vendor but flash full firmware just to be sure), ROM, gapps, dfe and reboot.
Click to expand...
Click to collapse
is it fastboot flash file link which you have provided above?
hondraopranav said:
is it fastboot flash file link which you have provided above?
Click to expand...
Click to collapse
Twrp!
You flash firmware as a normal zip.
I understand that twrp works for you.
If it doesn't, flash twrp through fastboot and then proceed as i mention above
Thanks for your replies.
The problem I have is that fastboot does not really seem to work.
When I try to do a fastboot command I get the error that goes:
"Sending 'recovery' (31068 KB) FAILED (Write todevice failed (Unknown error))
fastboot:error: Command failed"
Also, I just tried the Mi unlock tool and it seems that it cannot create a connection with the usb cable - so could that be the reason that I cannot flash it?
kitkat87 said:
Thanks for your replies.
The problem I have is that fastboot does not really seem to work.
When I try to do a fastboot command I get the error that goes:
"Sending 'recovery' (31068 KB) FAILED (Write todevice failed (Unknown error))
fastboot:error: Command failed"
Also, I just tried the Mi unlock tool and it seems that it cannot create a connection with the usb cable - so could that be the reason that I cannot flash it?
Click to expand...
Click to collapse
Download twrp for poco f1 from the official twrp site.
When everything is ready and you have pressed flash, THEN boot into fastboot and connect the cable
Edit: you also might have relocked your bootloader. If what I mention above doesn't work, unlock your bootloader again with the unlock file Xiaomi originally sent you.
sotosgolf said:
Download twrp for poco f1 from the official twrp site.
When everything is ready and you have pressed flash, THEN boot into fastboot and connect the cable
Edit: you also might have relocked your bootloader. If what I mention above doesn't work, unlock your bootloader again with the unlock file Xiaomi originally sent you.
Click to expand...
Click to collapse
The phone doesn't boot into a system, and currently as I load fastboot whenever the connection to the computer is made it goes to a screen saying 'press any key to turn off'.
I did notice, though, that after I from recovery wipe all data, then in the first boot it encrypts the phone. But it never manages to get the OS up and running.
------
Just downloaded the latest twrp from the official site. And when I tried to flash it I got the same error
"Sending 'recovery' (31068 KB) FAILED (Write todevice failed (Unknown error))
fastboot:error: Command failed"
kitkat87 said:
I did notice, though, that after I from recovery wipe all data, then in the first boot it encrypts the phone. But it never manages to get the OS up and running.
Click to expand...
Click to collapse
Let's get this straight m8,
Can you boot into recovery ("up"+"power")?
Yes or No?
Thanks for your replies.
sotosgolf said:
This will work with any Android 10 custom ROM
If you want to stay unencrypted, you have to use dfe (disable force encryption). I have never used it, but if you want it try to get one without magisk.
1. 11.0.6 is the latest firmware. You can download it from here:
2. You have to format your internal storage.
3. Steps: go to recovery (press back when it asks for password)->wipe->format data (it will ask you to type "yes")-> wipe system, data, internal storage,cache, davlik cache
Copy firmware,rom, gapps, dfe into your internal storage, flash firmware (most ROMs include vendor but flash full firmware just to be sure), ROM, gapps, dfe and reboot.
Click to expand...
Click to collapse
HI mate,
I wanna check how long did it take to install Android 10 on your poco?
Cuz I installed the rom for more than 30 minutes after reboot and it is not over by follow your steps.
Idk what's the problem with my poco.
------------------------------------------------------------
New update:
Finally, I completed flash the rom, and Idk what's the problem, lol
I can boot into both fastboot and recovery. The recovery is Mi-recovery 3.0. Though, in recovery it doesn't seem that I can get any connection with it.
-----------
update
Currently, when I do anything beyond fastboot devices I get the screen reading "press any key to shutdown"
sotosgolf said:
Let's get this straight m8,
Can you boot into recovery ("up"+"power")?
Yes or No?
Click to expand...
Click to collapse
I can boot into mi-recovery 3.0 but no twrp or other custom recovery.
kitkat87 said:
I can boot into mi-recovery 3.0 but no twrp or other custom recovery.
Click to expand...
Click to collapse
You most likely had your bootloader re-locked. You have to unlock it again
sorry for the late reply.
I downloaded MiFlashPro, and apparently I could flash miui 11. So far, so good. But as I tried to flash or even boot into twrp I got the same command as I used to.
Can the issue be because I maybe don't have the latest drivers installed?
kitkat87 said:
I can boot into both fastboot and recovery. The recovery is Mi-recovery 3.0. Though, in recovery it doesn't seem that I can get any connection with it.
-----------
update
Currently, when I do anything beyond fastboot devices I get the screen reading "press any key to shutdown"
Click to expand...
Click to collapse
Do you have all the drivers installed on your pc ?
ADB and Fasboot drivers. And try using usb 2.0 ports. Mi tools have issues with usb 3.0 ports. And You should be on an Intel processor. You can also try twrp 3.3.1 beta by @Reignz.

Categories

Resources