Hi all,
I have the following problem: My Sony Xperia Z5 compact will not boot into recovery, but instead resumes a normal boot. I have unlocked the bootloader following the official instructions by Sony. The flashing of the recovery also seems to work fine:
Code:
$ sudo fastboot flash recovery ./twrp_recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (19800 KB)...
OKAY [ 0.611s]
writing 'recovery'...
OKAY [ 1.099s]
finished. total time: 1.710s
But both booting with Volume down+Power and with "adb reboot recovery" just boots/reboots into android.
So far I've tried both versions from here (recovery_v3.1.1.img and recovery_suzuran_230218.img), this and the newest from here (recovery_v3.2.1_17.02.2018.img).
I'm already thanking for any help in advance.
Cheers
orthen2112 said:
Hi all,
I have the following problem: My Sony Xperia Z5 compact will not boot into recovery, but instead resumes a normal boot. I have unlocked the bootloader following the official instructions by Sony. The flashing of the recovery also seems to work fine:
Code:
$ sudo fastboot flash recovery ./twrp_recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (19800 KB)...
OKAY [ 0.611s]
writing 'recovery'...
OKAY [ 1.099s]
finished. total time: 1.710s
But both booting with Volume down+Power and with "adb reboot recovery" just boots/reboots into android.
So far I've tried both versions from here (recovery_v3.1.1.img and recovery_suzuran_230218.img), this and the newest from here (recovery_v3.2.1_17.02.2018.img).
I'm already thanking for any help in advance.
Cheers
Click to expand...
Click to collapse
Recovery works fine. Hold Vol Down + Power when phone is completely off until you feel a vibration, then wait. There have been issues in the past where Magisk was keeping the phone from thoroughly turning off - if you have that issue - hold Vol Up + Power to force shutdown, then Vol Down + Power after a bit to boot to recovery.
trax7 said:
Recovery works fine. Hold Vol Down + Power when phone is completely off until you feel a vibration, then wait. There have been issues in the past where Magisk was keeping the phone from thoroughly turning off - if you have that issue - hold Vol Up + Power to force shutdown, then Vol Down + Power after a bit to boot to recovery.
Click to expand...
Click to collapse
I've actually already tried that. The shutdown with [Vol Up + Power] gets confirmed with 3 vibrations. Switching on with [Vol Down + Power] just boots to android again.
Flashing the recovery "on top" of another recovery with "sudo fastboot flash recovery ./twrp_recovery.img" should be no problem, since it replaces the previous recovery. Right?
orthen2112 said:
I've actually already tried that. The shutdown with [Vol Up + Power] gets confirmed with 3 vibrations. Switching on with [Vol Down + Power] just boots to android again.
Flashing the recovery "on top" of another recovery with "sudo fastboot flash recovery ./twrp_recovery.img" should be no problem, since it replaces the previous recovery. Right?
Click to expand...
Click to collapse
Actually it flashes it unto the FOTAKernel partition. Afaicr we needed to hook and chain-load the recovery after kernel launches on the Z5 line.
I flashed mine on Windows with the latest fastboot drivers and just did "fastboot flash recovery twrp.img". Your command looks okay and it passes tho so I dont suppose your mistake is there.
Here's what you can try - fastboot flash boot twrp.img
Flash it to the kernel partition and see what happens - if ur phone boots normally then the flashing never happened even if it says it did... :laugh:
trax7 said:
Actually it flashes it unto the FOTAKernel partition. Afaicr we needed to hook and chain-load the recovery after kernel launches on the Z5 line.
Click to expand...
Click to collapse
I have to admit I didn't understand very much in those to sentences.
trax7 said:
I flashed mine on Windows with the latest fastboot drivers and just did "fastboot flash recovery twrp.img". Your command looks okay and it passes tho so I dont suppose your mistake is there.
Click to expand...
Click to collapse
Any ideas where else I can look
trax7 said:
Here's what you can try - fastboot flash boot twrp.img
Flash it to the kernel partition and see what happens - if ur phone boots normally then the flashing never happened even if it says it did... :laugh:
Click to expand...
Click to collapse
So, that did work. Now the smartphone boots TWRP instead of Android. So this means I just replaced my bootloader, yes? What happens if I flash LineageOS from this TWRP? I believe flashing a ROM only writes to /system, is that right? And how to best replace the bootloader?
Anyhow, thanks
orthen2112 said:
I have to admit I didn't understand very much in those to sentences.
Any ideas where else I can look
So, that did work. Now the smartphone boots TWRP instead of Android. So this means I just replaced my bootloader, yes? What happens if I flash LineageOS from this TWRP? I believe flashing a ROM only writes to /system, is that right? And how to best replace the bootloader?
Anyhow, thanks
Click to expand...
Click to collapse
Okay, now we know flashing occurs. You can do anything u want from that TWRP. You didn't replace your bootloader, you replaced your kernel. We can't touch the bootloaders, they are a completely different story :d
Flashing is mostly done to /system - yes but it's not limited to that. That's just the most useful partition as you can already modify most of the others you would be interested in.
Flashing LineageOS will replace your firmware and your kernel.
trax7 said:
Okay, now we know flashing occurs. You can do anything u want from that TWRP. You didn't replace your bootloader, you replaced your kernel. We can't touch the bootloaders, they are a completely different story :d
Flashing is mostly done to /system - yes but it's not limited to that. That's just the most useful partition as you can already modify most of the others you would be interested in.
Flashing LineageOS will replace your firmware and your kernel.
Click to expand...
Click to collapse
Thank you very much!
I flashed the ROM, using the TWRP on /boot without problems and now I can also boot /recovery!
orthen2112 said:
Thank you very much!
I flashed the ROM, using the TWRP on /boot without problems and now I can also boot /recovery!
Click to expand...
Click to collapse
Glad I helped! The mods can close the thread now, I guess.
Okay, big problem here! Save me please :fingers-crossed:
I had the same problem : flashing twrp to recovery seemed to work but I was unable to boot on recovery while pressing voldown + power or with "adb reboot recovery", the phone would do a normal boot instead.
Seeing how trax7's suggestion solved orthen2112's problem, I tried the same. Bad luck, now I cannot boot AT ALL. The phone vibrates once but the screen remains black, it does not boot on TWRP, nor on regular android. Please tell me it is not bricked...
I can still go into fastboot mode.
EDIT:
When I try to boot directly on an image of TWRP (I tried several versions) using "fastboot boot recovery.img" I get "FAILED (remote: dtb not found)"
fetchaspade said:
Okay, big problem here! Save me please :fingers-crossed:
I had the same problem : flashing twrp to recovery seemed to work but I was unable to boot on recovery while pressing voldown + power or with "adb reboot recovery", the phone would do a normal boot instead.
Seeing how trax7's suggestion solved orthen2112's problem, I tried the same. Bad luck, now I cannot boot AT ALL. The phone vibrates once but the screen remains black, it does not boot on TWRP, nor on regular android. Please tell me it is not bricked...
I can still go into fastboot mode.
EDIT:
When I try to boot directly on an image of TWRP (I tried several versions) using "fastboot boot recovery.img" I get "FAILED (remote: dtb not found)"
Click to expand...
Click to collapse
Is your bootloader unlocked? Do you have the latest drivers + adb/fastboot installed?
trax7 said:
Is your bootloader unlocked? Do you have the latest drivers + adb/fastboot installed?
Click to expand...
Click to collapse
Thank you for your answer, sorry I did not notice.
My bootloader was indeed unlocked and I had adb + fastboot (on a linux distribution, never had to fetch specific drivers). In the end I tried to use flashtool to flash the stock Android L rom I had used for the downgrade (to backup the TA with the DRM keys before unlocking bootloader) which worked (I could not flash only the kernel image on boot). Then I tried again to boot on TWRP directly from fastboot mode without flashing anything: same error. I then downloaded a few recent stock Android N roms from xperifirm which flashtool could not unzip for some reason, then I found an Australian image elsewhere, and this time flashtool would accept it. So, back to Android N, I tried to flash TWRP again and it worked at last. I'm now running on the Lineage14.1+microG rom (so much better than stock roms I still can't believe it).
I guess TWRP, including old versions I tried, would not boot along the stock Android L rom that was currently flashed so I had to upgrade beforehand. I hope this will help people in the future.
Note for others, I thought I had the same problem as OP, but after doing as trax said with fastboot flash boot twrp.img it didnt boot at all(but did give a single vibrate). What worked for me is following Fetchaspade's instructions. For some reason it is not possible to go into recovery mode with lollipop, but having flashed with nougat I can now get into recovery mode with TWRP.
elfae said:
Note for others, I thought I had the same problem as OP, but after doing as trax said with fastboot flash boot twrp.img it didnt boot at all(but did give a single vibrate). What worked for me is following Fetchaspade's instructions. For some reason it is not possible to go into recovery mode with lollipop, but having flashed with nougat I can now get into recovery mode with TWRP.
Click to expand...
Click to collapse
Ofc that the latest recovery wont work for an Android version it wasn't made for (it would probably work on Marshmallow but Lollipop is too old). A different recovery would work there, the old zxz recovery if i remember correctly.
Also you can fastboot boot the recovery image directly.
Thanks for clarifying Trax, I was not aware that the latest version of TWRP was not backwards compatible with earlier android versions. My reason for posting is because I expect there will be more people following the instructions here; https://wiki.lineageos.org/devices/suzuran/install. They will need to downgrade to make a backup of their TA partition, and as I did probably forget to go back to a newer stock version since it is not mentioned in the lineageOS step by step guide.
elfae said:
Thanks for clarifying Trax, I was not aware that the latest version of TWRP was not backwards compatible with earlier android versions. My reason for posting is because I expect there will be more people following the instructions here; https://wiki.lineageos.org/devices/suzuran/install. They will need to downgrade to make a backup of their TA partition, and as I did probably forget to go back to a newer stock version since it is not mentioned in the lineageOS step by step guide.
Click to expand...
Click to collapse
You dont *have to* backup TA... It's only to preserve your original keys if you want. All of the custom kernels here emulate them anyway if you dont have the backup and LOS doesn't benefit from them at all.
Related
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:
I am trying to put twrp on my tablet so I can install cyanogenmod but I am running into problems.
Device: sgp311 on android 5.1.1 and bootloader is unlocked.
1. I open cmd terminal from the folder that contains the latest twrp img.
2. I boot into fastboot mode by the cmd command "adb reboot bootloader"
3. I use the command " fastboot flash boot twrp.img" and it's successful (had an image but cant link it)
4. I use the command "fastboot reboot" and nothing my device stays blank, nothing appears on screen even after holding the power and volume up buttons to do a regular reset and hard reset. When I flash android 5.1.1 back on to my device all my data is still there.
I am also trying to use flashtool to revert too android kitkat but after flashing the firmware and booting up it just stays in a bootloop at the sony logo.
Anyone have any suggestions on what to do?
BrickedXperia said:
Anyone have any suggestions on what to do?
Click to expand...
Click to collapse
you're doing it right in general, but there are some issues, though.
Sony devices, like your SGP311 don't have recovery[*] partition, like nexus or other ones.
On Sony, you need to flash kernel with the integrated recovery.
On step 3, you're flashing presumably recovery image (without kernel) to boot partition. As it is not kernel, device is is not booting, which is expectable.
So you need to flash this with CM13 kernel + CM recovery. After flashing reboot device, press VOL- to enter recovery, make necessary wipes, and install CM13 Rom zip.
P.S: With Flashtool fastboot mode, flashing is done easier and faster.
Rootk1t said:
you're doing it right in general, but there are some issues, though.
Sony devices, like your SGP311 don't have recovery[*] partition, like nexus or other ones.
On Sony, you need to flash kernel with the integrated recovery.
On step 3, you're flashing presumably recovery image (without kernel) to boot partition. As it is not kernel, device is is not booting, which is expectable.
So you need to flash this with CM13 kernel + CM recovery. After flashing reboot device, press VOL- to enter recovery, make necessary wipes, and install CM13 Rom zip.
P.S: With Flashtool fastboot mode, flashing is done easier and faster.
Click to expand...
Click to collapse
Thank you, I flashed cyanogenmod recovery with adb commands and restarted it and it worked, I now have cyanogenmod on my tablet and it looks and feels way better than the stock rom.
As BrickedXperia, I am trying to put twrp on my tablet so I can install cyanogenmod but I am running into problems.
Device: sgp321 on android 5.1.1 and bootloader is unlocked.
No root (must I?)
1. I open cmd terminal from the platform-tools folder that contains the latest twrp img.
2. I boot into fastboot mode by the cmd command "adb reboot bootloader"
3. I use the command " fastboot flash boot twrp.img" but here it fails and gives an error.
I see from Rootk1t's reply that you have to do something with kernel. Would someone care to elaborate a bit? I am new to this stuff and it's not straight forward despite all the guides around. I would appreciate any help a lot.
What does the error say?
Something like
writing 'recovery'... failed (remote command not allowed)
Svenni84 said:
Something like
writing 'recovery'... failed (remote command not allowed)
Click to expand...
Click to collapse
if it says not allowed, check that bootloader state is really unlocked.
Rootk1t said:
if it says not allowed, check that bootloader state is really unlocked.
Click to expand...
Click to collapse
When I open the hidden service menu it really does say that it is. Is it any other way to confirm this?
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
Hello, owner of the RN 5 here
After the command fastboot boot twrp.img my device do not enter the twrp, but displays the mi logo and "unlocked" status.
The same happens when I use orange fox recovery.
What might have caused that?
The device is unlocked (the official way) .
Connection (cable, drivers, etc) seems to be ok (anyhow I did unlocked the BL)
C:\redmi-unlock\platform-tools_r30.0.2-windows\platform-tools>fastboot devices
ec976afd fastboot
C:\redmi-unlock\platform-tools_r30.0.2-windows\platform-tools>fastboot boot C:\redmi-unlock\twrp-3.3.1-0-vince.img
Sending 'boot.img' (36784 KB) OKAY [ 0.778s]
Booting OKAY [ 0.143s]
Finished. Total time: 0.964s
C:\redmi-unlock\platform-tools_r30.0.2-windows\platform-tools>
Please, advice
tman_pl said:
Hello, owner of the RN 5 here
After the command fastboot boot twrp.img my device do not enter the twrp, but displays the mi logo and "unlocked" status.
The same happens when I use orange fox recovery.
What might have caused that?
The device is unlocked (the official way) .
Connection (cable, drivers, etc) seems to be ok (anyhow I did unlocked the BL)
C:\redmi-unlock\platform-tools_r30.0.2-windows\platform-tools>fastboot devices
ec976afd fastboot
C:\redmi-unlock\platform-tools_r30.0.2-windows\platform-tools>fastboot boot C:\redmi-unlock\twrp-3.3.1-0-vince.img
Sending 'boot.img' (36784 KB) OKAY [ 0.778s]
Booting OKAY [ 0.143s]
Finished. Total time: 0.964s
C:\redmi-unlock\platform-tools_r30.0.2-windows\platform-tools>
Please, advice
Click to expand...
Click to collapse
Flash OrangeFox Recovery by using the fastboot flash recovery recovery.img command
Reboot into OrangeFox by pressing the power + volume up keys, until you see the OrangeFox splash screen (the keys may be may vary on your device)
From here
Installing OrangeFox Recovery
wiki.orangefox.tech
Copy the downloaded recovery image (.img file) to the folder where you have placed your ADB and Fastboot.
Or read this
Android Tip: Boot into twrp or cwm recovery without flashing
Yes, that’s true. You can boot into any recovery of your choice on your Android phone by following this guide. No need to flash and replace the stock bootloader. Though I have tested this met…
aubykhan-wordpress-com.cdn.ampproject.org
joke19 said:
Copy the downloaded recovery image (.img file) to the folder where you have placed your ADB and Fastboot.
Or read this
Click to expand...
Click to collapse
Well, that didnt work - copying both twrp and orange recovery changed nothing (still MI logo and "unlocked" status after the command fastboot boot image_file.img).
joke19 said:
Flash OrangeFox Recovery by using the fastboot flash recovery recovery.img command
Reboot into OrangeFox by pressing the power + volume up keys, until you see the OrangeFox splash screen (the keys may be may vary on your device)
From here
Installing OrangeFox Recovery
wiki.orangefox.tech
Click to expand...
Click to collapse
Well, I am not an expert - I am just affraid of doing that while fastboot boot file.img didnt work. Is it safe?
I guess I have onlu one chance to try.. Will you help me in case I dont succeed?
tman_pl said:
Well, I am not an expert - I am just affraid of doing that while fastboot boot file.img didnt work. Is it safe?
I guess I have onlu one chance to try.. Will you help me in case I dont succeed?
Click to expand...
Click to collapse
When you download the right recovery it will work
Or ask here
[Official][Recovery][TWRP]TWRP For Xiaomi Redmi 5 Plus/Redmi Note 5
Team Win Recovery Project 3.x, or TWRP3.x for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven...
forum.xda-developers.com
Maybe this can be a problem
Maximum Path Length Limitation - Win32 apps
Maximum path length limitation.
docs.microsoft.com
OMG, I am soooo lame.
I just installed android app "Device ID" and it turned out I AM ON WHYRED codename (not venice). I was pretty sure whyred = RN5 Pro, while regular RN5 - vince...
Well, Mi forum https://c.mi.com/thread-1911812-1-1.html confirms what I thought, but...
soooo ashamed.
Now I have to read again and check everything again..
Hey all,
I have a new z5c running 32.4.A.1.54 stock.
I flash TWRP (I have tried a few different versions) using Fastboot on Ubuntu20.04, it all runs fine no errors, and appears to flash as it should.
But the phone will not load TWRP, from the phone itself, I have tried a million different ways.
The only way it loads is by
fastboot boot twrp.img
But when I do this .. android will not then start .. hangs on Sony logo
I have to reflash the stock rom to get it to work again
If I run
fastboot reboot recovery
I get:
fastboot: usage: unknown reboot target recovery
even tho:
fastboot devices
correctly identifies the device
I would like to root and use custom rom, but have not yet been able to get past this TWRP hurdle
Has anyone experience of this, or any ideas?
You've flashed TWRP in a wrong way! Please search for help in my several ROM threads.
Well, thanks for your answer, really, I appreciate it
But I have flashed it again and again and followed your threads and other threads
I'm not a newbie, i have flashed TWRP and roms to a few phones, inc Z1C and a couple of Z3Cs
I have adb, and fastboot installed
Bootloader unlocked
USB debugging
Recommended stock
I have downloaded multiple .img files, including your 3.6.1 version
I run fastboot
and
fastboot flash recovery twrp.img
The phone will not reboot into TWRP, using buttons nor fastboot, only into android, unless I then run
fastboot boot twrp.img
Then TWRP runs, but when I then reboot, I just hit the SONY logo if I have not flashed a ROM or a bootloop if I have.
And from there will not return to TWRP at all.
What am I missing?
I'm very confused as everything you're talking about is working here and for other users flawlessly.
Really, I don't know what's wrong at your side.
Berni-0815 said:
I'm very confused as everything you're talking about is working here and for other users flawlessly.
Really, I don't know what's wrong at your side.
Click to expand...
Click to collapse
Yes, that makes 2 of us!
Ugh.
Did you try what I told you in this post?
With that, LineageOS 19.1 MUST boot up!
If not, I don't know further...
Berni-0815 said:
Did you try what I told you in this post?
With that, LineageOS 19.1 MUST boot up!
If not, I don't know further...
Click to expand...
Click to collapse
I did try that as recommended, thanks
I am flashtool-ing back to the stock again, after being again stuck on boot with TWRP inaccessible
I will give it one last go
Thanks, man
How do I buy you a coffee?
That's all really weird; since it works here since years.
From a fresh fully-functional stock install
Following this simple process exactly
Devices with only TWRP.IMG
If your device only has the IMG file, then execute the below command: fastboot flash recovery twrp.img
Now execute the below command to boot your device to the TWRP recovery. fastboot boot twrp.img
Once it boots to TWRP, you could then boot it to the OS, via the Reboot > System option in TWRP.
From here;
https://www.getdroidtips.com/flash-twrp-recovery-android/
After 3. it gets to SONY logo and hangs
Same every time
Obviously not a problem with your or any other custom ROM
The only way out from here is to Flashtool the stock again
Geez
I'm giving up on TWRP and custom ROM
I'll go for the rooted, debloated, degoogled stock as best as I can get it
Thanks v much for the support!
I've NEVER used the command
Code:
fastboot boot twrp.img
I've always flashed TWRP like this:
Shutting down device
Waiting some time
Pressing volume up and plugging usb cable
Enter this command in a terminal window:
Code:
fastboot flash recovery TWRP_3.6.1_9-0-recovery_suzuran_2022-03-09.img
After unplugging the usb cable and waiting some time I rebooted into TWRP by pressing power and volume down simultaneously.
That worked since years flawlessly!
Berni-0815 said:
I've NEVER used the command
Code:
fastboot boot twrp.img
I've always flashed TWRP like this:
Shutting down device
Waiting some time
Pressing volume up and plugging usb cable
Enter this command in a terminal window:
Code:
fastboot flash recovery TWRP_3.6.1_9-0-recovery_suzuran_2022-03-09.img
After unplugging the usb cable and waiting some time I rebooted into TWRP by pressing power and volume down simultaneously.
That worked since years flawlessly!
Click to expand...
Click to collapse
That command is the only way that twrp has loaded for me
Right .. deep breath ... one last go at this using yr suggestion,
thanks
Nope
Same again
All goes as it should
Power and volume down simultaneously
Boots into Android
adb reboot recovery
Also boots into android
If I was now to run
fastboot boot twrp.img
It would run TWRP the one time, but just hang on SONY logo when rebooted
Ho hum.
kaivalyam said:
Power and volume down simultaneously
Boots into Android
Click to expand...
Click to collapse
That SHOULD NOT happen if you've flashed TWRP in the only right way.
I'm sorry, but I don't believe that...
Berni-0815 said:
That SHOULD NOT happen if you've flashed TWRP in the only right way.
I'm sorry, but I don't believe that...
Click to expand...
Click to collapse
Well, its not a particularly complicated process
I have described exactly what I have done
I have done it multiple times
And that is what happens
As I said: I've never seen that and that's not reported very often by other users.
And if, then it has been an error in flashing.
Highly unlikely that you're devices so called FOTA partition is damaged so that the command
Code:
fastboot flash recovery <name of the recovery image>
fails.
Code:
fastboot flash boot <name of the boot image>
flashes the boot partition and that's not the same as the FOTA partition.
I have to believe you but somehow I can't.
I understand
fastboot flash recovery <name of the recovery image>
Doesn't fail exactly ... it runs fine .. no errors
Code:
~/Dev/Z5/twrp/3.6.1$ fastboot flash recovery TWRP_3.6.1_9-0-recovery_suzuran_2022-03-09.img
target reported max download size of 536870912 bytes
sending 'recovery' (22668 KB)...
OKAY [ 0.570s]
writing 'recovery'...
OKAY [ 0.395s]
finished. total time: 0.965s
But then the phone will only boot android
~~~
Unless
I run;
fastboot flash boot <name of the boot image>
Again, runs fine .. no errors
Code:
~/Dev/Z5/twrp/3.6.1$ fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.552s]
booting...
OKAY [ 0.561s]
finished. total time: 1.113s
This boots TWRP but then after that the phone hangs at boot and will neither start Android or TWRP
It is indeed very strange.
Look at your own code:
Code:
~/Dev/Z5/twrp/3.6.1$ fastboot boot twrp.img
downloading 'boot.img'...
From where is boot.img downloaded? And where is it stored internally?
Have you flashed system.img too?
There goes something terribly wrong at your side.
Thanks for your patience
Yes I'm sure you're right, probably user error, although I am having trouble seeing what that is exactly ...
So, using Ubuntu, I am in the directory that contains the twrp.img file (most times I have renamed it this)
Is that correct so far?
From there I run
fastboot flash recovery twrp.img
All good, as above, but TWRP does not load, ever, using buttons or adb, unless I then run
fastboot boot twrp.img
TWRP then runs
But the phone will not boot into anything from there
Yes, I thought that was a little odd ...
"downloading" : I assumed it meant it was transferring the file across, or accessing it, from my pc to the device
"'boot.img" : I assumed fastboot had changed the filename to what it needed it to be ...
Is the problem around this?
You can name the recovery image file as you like it to be named.
Have you disconnected the USB cable after flashing?
Have you waited some time before trying to boot anything?
If you can boot TWRP, you can fetch a LOG file at the "Advanced" menu. Please send me this LOG file via PM (it may contain personell data!).