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!).
Related
Ok so
Rooted
S-off
hboot 1.12.2222
was running Mean-rom 4.4
Then tried to install the new apk fix for ringtones
http://forum.xda-developers.com/showthread.php?t=1900629
Phone rebooted then then continues to be stuck in boot loop.
What I have tried:
Factory reset in bootloader
clear storage in bootloader
reinstall TWRP to get in recovery as if I choose recover in bootloader it just boot loops.
Tried to install the RUU but it can not connect during boot loops and errors out.
Any ideas?
Thanks in advance
Try fastboot wipe recovery then fastboot flash recovery recovery.img, if recovery loops back to bootloader then it's corrupt. Make sure you flash the latest twrp
om4 said:
Try fastboot wipe recovery then fastboot flash recovery recovery.img, if recovery loops back to bootloader then it's corrupt. Make sure you flash the latest twrp
Click to expand...
Click to collapse
All I see in fastboot option on bootloader is
bootloader
reboot
reboot bootloader
powerdown
am I missing something?
Those are fastboot commands, you use the terminal
fastboot wipe recovery
fastboot flash recovery recovery.img
You should be able to boot into recovery afterwards
What terminal? I'm a bit lost here
Do you have adb tools or Android SDK?
C:\android-sdk-windows
Open cmd prompt by opening SDK folder and then hold shift and right click, it will say open cmd prompt or something similar I don't recall if adb is in separate folder but I don't think so. From there you can plug in the phone in fastboot and type fastboot devices, it will tell you if you are connected or not. Download twrp and place it in the same folder. Then you can use the commands I listed earlier
om4 said:
Open cmd prompt by opening SDK folder and then hold shift and right click, it will say open cmd prompt or something similar I don't recall if adb is in separate folder but I don't think so. From there you can plug in the phone in fastboot and type fastboot devices, it will tell you if you are connected or not. Download twrp and place it in the same folder. Then you can use the commands I listed earlier
Click to expand...
Click to collapse
Get an error see attached
Now that I am in fasboot usb on the bootloader the RUU can connect to phone via USB.
If I just flashed that and started all over would that work and do I need to unroot and relock before doing the RUU?
Still not having any luck on terminal so far.
Sorry I was busy arguing with gf, it seems you aren't where you need to be if fastboot isn't recognized, I haven't had access to my own pc in quite a while so I'm having trouble remembering if there is another directory
om4 said:
Sorry I was busy arguing with gf, it seems you aren't where you need to be if fastboot isn't recognized, I haven't had access to my own pc in quite a while so I'm having trouble remembering if there is another directory
Click to expand...
Click to collapse
got fastboot working but get this with your first command
That's because I haven't used wipe in fastboot in quite a while, I'm sure I'm just confused on wipe and erase but you shouldn't need it, the first command should be fastboot erase recovery but like I said you shouldn't really have to, it's just like formatting before flashing the recovery, just fastboot flash recovery openrecovery.img or what ever the name is for the twrp file
Ran
C:\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7356 KB)...
OKAY [ 1.112s]
writing 'recovery'...
OKAY [ 1.796s]
finished. total time: 2.912s
Hit recovery and we we still are in boot loop
Relock bootloader and run ruu fastboot oem lock
copc said:
All I see in fastboot option on bootloader is
bootloader
reboot
reboot bootloader
powerdown
am I missing something?
Click to expand...
Click to collapse
select bootloader the recovery as soon you have recovery up wipe and reflash the rom
HTC EVO LTE
luisrod03 said:
select bootloader the recovery as soon you have recovery up wipe and reflash the rom
HTC EVO LTE
Click to expand...
Click to collapse
Thanks recovery just loops, could never get in.
Ok this is where I am at (see OP)
We tried flashing TWRP and original recovery via ADB
We tried running RUU
I'm still stuck in a boot loop....
I am having a similar problem stuck in bootloader. I relocked to go to the new firmware and now am stuck in the bootloader. I can access adb but can't access recovery. I am now relocked. Can I unlock again with a fastboot command?
If you unlocked manually, HTC sends the unlock code code just use fastboot to flash, if you used regawmod, just run it again. I don't know if regawmod will recognize the phone in boot loader though
RN3P Kenzo, ROM is Global Dev 6.8.18.
I unlocked the bootloader officially (using the code and the MiFlashUnlock tool). I then used ADB to flash Cofface TWRP which did not work. These are the steps I used:
First I booted into fastboot.
Then I did this in Minimal ADB 'fastboot flash recovery twrp.img'.
The message was
sending 'recovery'
OKAY
writing 'recovery'
OKAY
finished.
Next I did 'fastboot reboot'.
Then I tried to get into TWRP recovery using the MIUI update app. Didn't work. Any help? Thanks in advance.
monsieurazizx said:
RN3P Kenzo, ROM is Global Dev 6.8.18.
I unlocked the bootloader officially (using the code and the MiFlashUnlock tool). I then used ADB to flash Cofface TWRP which did not work. These are the steps I used:
First I booted into fastboot.
Then I did this in Minimal ADB 'fastboot flash recovery twrp.img'.
The message was
sending 'recovery'
OKAY
writing 'recovery'
OKAY
finished.
Next I did 'fastboot reboot'.
Then I tried to get into TWRP recovery using the MIUI update app. Didn't work. Any help? Thanks in advance.
Click to expand...
Click to collapse
Try this, "fastboot boot twrp.img" NOT fastboot flash boot, just "fastboot boot twrp.img"
andersonaragao said:
Try this, "fastboot boot twrp.img" NOT fastboot flash boot, just "fastboot boot twrp.img"
Click to expand...
Click to collapse
OK. It boots into TWRP. But my question is, will I have to use "fastboot boot twrp.img" every time to boot into TWRP? That would be a hassle, but if that's the only way, I'll just deal with it.
Thanks though, it was nice to know the recovery image was working.
monsieurazizx said:
OK. It boots into TWRP. But my question is, will I have to use "fastboot boot twrp.img" every time to boot into TWRP? That would be a hassle, but if that's the only way, I'll just deal with it.
Thanks though, it was nice to know the recovery image was working.
Click to expand...
Click to collapse
No. You dont need to fastboot everytime. As you once booted into TWRP from "fastboot boot twrp.img" your recovery is perminantly TWRP. You can boot into by pressing the key combination or from the updater app..
Happy Flashing
Try fastboot reboot recovery but if not boot into recovery don't boot into system and reboot recovery via key combination. If you reboot system stock recovery erase twrp.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
https://twrp.me/devices/xiaomiredminote3.html
"fastboot reboot" hold volume up until you see mi logo
Wipe:
/data
Then flash:
http://forum.xda-developers.com/redmi-note-3/how-to/modified-twrp-deleting-emmcappsboot-t3371667
@Up disables dm-verity and encryption on /data partition[that's why we wipe it inorder to format it].
By SharkcpN(Newbie Guide)
B) Prevent TWRP From Getting Over-written
After the TWRP gets flashed, disconnect the cable from the phone.
Hold power button + volume up buttons till phone gets restarted.
When the Mi Logo shows up, release the power button & keep holding the volume up button.
Release the Volume Up button after TWRP logo shows up.
If the language is in Chinese, select the right box, & select English.
Check the box & swipe to allow modifications.
it worked for me
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?
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.
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..